diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a108f56345a33ab0aa78133f13bf8ebb3fdf129 --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9608830f67684d950f49ee62a9dce4e36d91483dfe1aba812ebe5e01a11fc8c +size 19424 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9ac65c129b62b9d3e5d2d64630b098b0339ceb8 --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27035ce563f35e6062357bbb086222c61ebc150203c76838e8285ae89d13f0e4 +size 103272 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..650d3fcf78fc86f5afc81545a833bf5fdf19a2ce --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b39cde37837c85f3d4f164016bab532a7cc08b1ab22878c1509d85900210ccd +size 63735 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4f3943321f5f56425df896dfe3a5be1e2c3c353 --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8399548f82352dc74600eb622afc9a077d1e63a907dd2bedf13a51505cdbdc6 +size 39174 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3fe5789fbd763c20dea6a6539cf2a525625262a --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00d12552309ba78076d7de68ad47601b75f18ddbebe7fc959304f2f17de2dabc +size 64172 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb2292121800a3214cb6b15c0de3688f5d61b6dd --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73dacb7578d3a1d931f1547884fe57584f6b8655f10499f304c382fe7562ee74 +size 83364 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c601a1d2840cade6064f8d6ce5f476ff64a5e9fd --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d5618f3285ea1171b03f21b24c645c6b5ad2de241cf7f151245ef1a8cbaa8b +size 102707 diff --git a/marked/Q/T-REC-Q.1001-198811-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2dbf74856738cedb8807815ee4d550e3313446d --- /dev/null +++ b/marked/Q/T-REC-Q.1001-198811-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88732ef6985fa71795eb5ceeb83088227bcea9d16685ef8043eafb44ac43f928 +size 68634 diff --git a/marked/Q/T-REC-Q.107bis-199303-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Q/T-REC-Q.107bis-199303-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f07d99edd106c3689e586ee986865d09532a920 --- /dev/null +++ b/marked/Q/T-REC-Q.107bis-199303-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3edf497f6bbb3688cf3697e9eac9ce6cdae1467c25f69ff9ac325e7fb2b8432d +size 28990 diff --git a/marked/Q/T-REC-Q.107bis-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.107bis-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d83486e18f51fde6851e57cca9787b23ab17e752 --- /dev/null +++ b/marked/Q/T-REC-Q.107bis-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23852fa7e2c61a42045960f14dd0fa7ad89fb9b37982f241890afc6caeecbc59 +size 9519 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a1a3c0faaae8ae37f0b761f81764a927ca5026 --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05b7d34c0ec065a059ef8e4594bb1517f0b2a78da5baa5efe8027f66a4e454a6 +size 117787 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0912d8db5e54c8b6533ac5858980bed2e98bb46 --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e20bdb128a4b58e07a99718efd51cadaf68d44962a9735962d93628586e78e40 +size 73451 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a85a2460e63d016dce76e700d414d72694340f9 --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfcb0361c9e43603d6d2bc33d77fa7cbcd9d60584902d76f68994e4dd5ec8922 +size 11005 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3758c7dbe5b0ed1f7522a8c5948039cd10f90f1b --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bbb5aa0f05a424862b999058d0423667f1825cc001aaad3522b0efebe760c42 +size 14155 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c847a01807bf5f0699b4c1585d5f8bf757e82ebe --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4dd83339558a572440ef7d2470638fd8431397a7dccba965166cd4066850d7c +size 130012 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/f6d72d7c790e7f585532140f3971639a_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..279b1bb12accd61c8c9befa336401f8c7b1264dc --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/f6d72d7c790e7f585532140f3971639a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:098dea3994cad7ec6d6487fa7599acb79b14a6cadaf6202801332b2e03853e68 +size 13928 diff --git a/marked/Q/T-REC-Q.1102-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5503fb6a95020619a5b70059decfe1704bc340b --- /dev/null +++ b/marked/Q/T-REC-Q.1102-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fdd4c204206f8e698912d069b47096a1540baaaff184989ba4082c7b39acc32 +size 10649 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2c82e3f373123b504686fecdcd66e63d1797c3c --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3948ad1990424a1a4dff0df7baac0bf62b6648941341637b879e3313929ad0dc +size 48003 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91fbf7c631a944cedd5fd9c4488af8a0a2a14aa4 --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47793fd97159791e1079999e460da9ff1dbed4535d9ff50190ea356d9e67f16b +size 134569 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd802cee85b3f9badd02b574218a99bdc61fca14 --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91dd6332d878828d4d06bfde24b9c548a8951e8220fd7e3ac8cb9786af884336 +size 17774 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..966d6e5771e7fc49033c93c6359443c6f4679954 --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:524393f8503d9b1c6aadc54eb3aee0f7360478a800b995c6e87b6bb98697a928 +size 10828 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8df10c384974aaf91e3868668021f4bb3c4426a --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:942dbb389cd45f5474dce2a9bf3a1c31cca711d35164152ea433d3f7999d9a51 +size 14736 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..872138751949b9812ac8cb363b79deb17041a1da --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4970d39480eb0c4be2bb93773bcbfd906bb16eb584da71e7640b0f5dc7f5d419 +size 164160 diff --git a/marked/Q/T-REC-Q.1103-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e72d220d42be12d1c0d75f2781ce3ae1b85a258 --- /dev/null +++ b/marked/Q/T-REC-Q.1103-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3725adabab63e4aa7b95e288e7ddc7fad5e04e56e746a3852bea0590d028c4e0 +size 11174 diff --git a/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edc38adc374ed94df3a2e91ef67d276fd3982005 --- /dev/null +++ b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:688ff4ea814701171bad94ce5141a808a93a93fc40890db84f80a2d0044199e0 +size 60014 diff --git a/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c520feb5e07beadba6e1c50b72a92db4c613cd3 --- /dev/null +++ b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c912f70637444262a0f4d8b24a21acfe3b3ae0ca86c4792ed9d93f3a5ee75c54 +size 64612 diff --git a/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e74534c6a8a6ccd1cad70141de2dfae5275551d1 --- /dev/null +++ b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:417e492ca52c3a7a2fdb5780d8cb3345949b691a0a6213f5aa8506814e9467d6 +size 76490 diff --git a/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/raw.md b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f79c98b0f45b324005b84cb7ee9e807bbbddf4b9 --- /dev/null +++ b/marked/Q/T-REC-Q.115.0-200212-I_PDF-E/raw.md @@ -0,0 +1,434 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.115.0** + +(12/2002) + +SERIES Q: SWITCHING AND SIGNALLING + +Clauses applicable to ITU-T standard systems – Logic and protocols for the control of signal processing network elements and functions + +--- + +**Protocols for the control of signal processing network elements and functions** + +ITU-T Recommendation Q.115.0 + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|------------------------------------------------------------------------------------------------|---------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| General clauses | Q.100-Q.109 | +| Transmission clauses for signalling | Q.110-Q.114 | +| Logic and protocols for the control of signal processing network elements and functions | Q.115 | +| Abnormal conditions | Q.116-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 | Q.120-Q.139 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 | Q.140-Q.199 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **ITU-T Recommendation Q.115.0** + +# **Protocols for the control of signal processing network elements and functions** + +## **Summary** + +Echo Cancellation and Voice Quality Enhancement have become a necessity not only in Circuit Switched Networks (wired and wireless) but also in Next Generation Networks. Signal processing network elements and functions are provided on a per-call basis to guarantee QoS for voice calls. This Recommendation describes the protocols to control, on a per-call basis, the signal processing functions. The protocols described in this Recommendation include TDM-based as well as IP-based protocol versions for TDM networks and IP networks. + +## **Source** + +ITU-T Recommendation Q.115.0 (2002) was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 December 2002. + +## **Keywords** + +Automatic Level (Gain) Control, Echo cancellation, Echo control, Noise Reduction, Voice Quality Enhancement. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|---------------------------------------------------------------|---| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conceptual model ..... | 2 | +| 6 | Network scenarios ..... | 3 | +| 6.1 | TDM: Standalone SPNE..... | 3 | +| 6.2 | VoIP: SPNE integrated in or external to a media gateway ..... | 4 | +| 7 | Protocols ..... | 5 | +| 7.1 | TDM ..... | 5 | +| 7.2 | VoIP..... | 5 | + + + +# Protocols for the control of signal processing network elements and functions + +# 1 Scope + +Echo Control (e.g., echo cancellation) and Voice Quality Enhancement (e.g., voice enhancement device) have become a necessity not only in Circuit Switched Networks (wired and wireless) but also in Next Generation Networks. Signal processing network elements and functions are provided on a per-call basis to guarantee QoS for voice calls. This Recommendation describes the protocols to control on a per-call basis the signal processing functions. The protocols described in this Recommendation include TDM-based as well as IP-based protocol versions for TDM networks and IP networks. + +The signal processing function specific logic, i.e. the logic that decides on the need for a signal processing function and the number of signal processing functions to be provided for a call, is defined in ITU-T Recs Q.115.x. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation Q.52 (2001), *Signalling between international switching centres and stand-alone echo control devices*. +- [2] ITU-T Recommendation Q.55 (1999), *Signalling between signal processing network equipment (SPNE) and international switching centres (ISC)*. +- [3] ITU-T Recommendation Q.56 (2001), *Signalling between signal processing network equipment (SPNE) and international switching centers over an IP network*. +- [4] ITU-T Recommendation H.248 (2000), *Gateway Control Protocol*. +- [5] ITU-T Recommendation G.173 (1993), *Transmission planning aspects of the speech service in digital public land mobile networks*. + +# 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 signal processing function specific logic:** A functional entity (part of call control) that decides if a signal processing function is required for this call. +- 3.2 signal processing function:** A functional entity; examples are echo cancellation, noise reduction, automatic level (gain) control, etc. +- 3.3 signal processing network element:** A physical entity that contains one or more signal processing functions assigned to one or more E1/T1 facilities. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|-------|---------------------------------------------------------------------------------------| +| CAS | Channel associated signalling | +| CCF | Call Control Function | +| ECD | Echo Control Device | +| ECF | Echo Control Function (echo cancellation, echo suppression) | +| E1 | A transmission link operating at 2048 kbit/s, supporting 30 or 31 64 kbit/s channels. | +| IP | Internet Protocol | +| LAN | Local Area Network | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| QoS | Quality of Service | +| SPF | Signal Processing Function | +| SPFCF | SPF Control Function | +| SPFSF | SPF Switching Function | +| SPFSL | SPF Specific Logic | +| SPNE | Signal Processing Network Element | +| TDM | Time Division Multiplex | +| T1 | A transmission link operating at 1544 kbit/s supporting 24 speech channels. | +| VoIP | Voice over IP | + +# 5 Conceptual model + +For each signal processing function SPF there exists a signal processing function specific logic added to call/bearer control; see Figure 1. Any SPF is provided on a per-call basis. A master slave relation exists between the SPF switching function and the SPF control function. + +![Figure 1/Q.115.0 – Conceptual methodology model. A diagram showing three planes: Functional plane, Physical plane, and VoIP plane. Functional plane contains SPFSF, SPFCF, and CCF/BCF (with SPFSL). Physical plane contains EXCHANGE, SPNE, and MG. VoIP plane contains MGC and SPNE. Connections include IP, TDM, and relationships 'r'. A note indicates SPF may be provided in the MG or a standalone SPNE.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the conceptual methodology model across three planes: + +- Functional plane:** Contains SPFSF, SPFCF, and CCF/BCF (which includes SPFSL). SPFSF and SPFCF are connected by a relationship 'r'. CCF/BCF is connected to SPFSF by a dashed mapping line. +- Physical plane:** Contains EXCHANGE, SPNE, and MG. EXCHANGE is connected to SPNE by a solid TDM line. EXCHANGE is connected to MGC in the VoIP plane by a dashed mapping line. SPNE is connected to MG by a solid IP line. +- VoIP plane:** Contains MGC and SPNE. MGC is connected to MG by a solid IP line. SPNE is connected to MG by a solid TDM line. + +Mapping lines (dashed) connect functional entities to physical entities: SPFSF to EXCHANGE, SPFCF to SPNE, and CCF/BCF to EXCHANGE. A note indicates that SPF may be provided in the MG or in a standalone SPNE. + +**Legend:** + +- Physical /virtual connection +- r Relationship between communicating pairs of functional entities +- - - - Mapping + +Q.115.0\_F01 + +Figure 1/Q.115.0 – Conceptual methodology model. A diagram showing three planes: Functional plane, Physical plane, and VoIP plane. Functional plane contains SPFSF, SPFCF, and CCF/BCF (with SPFSL). Physical plane contains EXCHANGE, SPNE, and MG. VoIP plane contains MGC and SPNE. Connections include IP, TDM, and relationships 'r'. A note indicates SPF may be provided in the MG or a standalone SPNE. + +**Figure 1/Q.115.0 – Conceptual methodology model** + +In the VoIP scenario where the MG controls the SPFs provided in a standalone (external) SPNE, the MG has an application protocol interworking function (H.248 SPNE package ↔ Q.52/Q.55/Q.56). + +# 6 Network scenarios + +## 6.1 TDM: Standalone SPNE + +Echo suppressors and echo cancellers provided as standalone equipment are considered to be a first generation of SPNE. The protocol to control standalone echo control devices is defined in ITU-T Rec. Q.52; see Figure 2. + +A platform providing one or more signal processing functions is referred to as SPNE. The protocols to control standalone SPNEs are defined in ITU-T Recs Q.55 and Q.56; see Figure 2. + +![Figure 2/Q.115.0 – TDM scenarios and the control protocols. The diagram shows two scenarios. The top scenario shows an EXCHANGE connected to an ECD via E1, T1 lines. The EXCHANGE contains a box 'a' (SPFSF) and the ECD contains a box 'b' (SPFCF) within an ECF. A callout box 'Q.52' points to the connection. The bottom scenario shows an EXCHANGE connected to an SPNE via E1, T1 lines. The EXCHANGE contains a box 'a' (SPFSF) and the SPNE contains a box 'b' (SPFCF) within SPFs. A callout box 'Q.55' points to a 'CAS, SS7, LAN' connection between 'a' and the SPNE. Another callout box 'Q.56' points to a connection between the SPNE and an IP network (represented by an oval). A legend at the bottom left defines 'a' as SPFSF and 'b' as SPFCF. The label 'Q.115.0_F02' is in the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Q.115.0\_F02 + +a SPFSF +b SPFCF + +Figure 2/Q.115.0 – TDM scenarios and the control protocols. The diagram shows two scenarios. The top scenario shows an EXCHANGE connected to an ECD via E1, T1 lines. The EXCHANGE contains a box 'a' (SPFSF) and the ECD contains a box 'b' (SPFCF) within an ECF. A callout box 'Q.52' points to the connection. The bottom scenario shows an EXCHANGE connected to an SPNE via E1, T1 lines. The EXCHANGE contains a box 'a' (SPFSF) and the SPNE contains a box 'b' (SPFCF) within SPFs. A callout box 'Q.55' points to a 'CAS, SS7, LAN' connection between 'a' and the SPNE. Another callout box 'Q.56' points to a connection between the SPNE and an IP network (represented by an oval). A legend at the bottom left defines 'a' as SPFSF and 'b' as SPFCF. The label 'Q.115.0\_F02' is in the bottom right. + +**Figure 2/Q.115.0 – TDM scenarios and the control protocols** + +## 6.2 VoIP: SPNE integrated in or external to a media gateway + +H.248 is the media gateway protocol used between a media gateway controller and a media gateway in the decomposed architecture. The H.248 SPNE package defined in this Recommendations allows the control of signal processing functions; see Figure 3. + +![Figure 3/Q.115.0 – VoIP Gateway (decomposed architecture); H.248 SPNE package (as defined in this Recommendation) is the control protocol. The diagram shows a Media Gateway Controller (MGC) connected to two Media Gateways (MG). The top MG is connected to an SPNE unit containing SPFs (Signal Processing Functions) labeled 'a' (SPFSF) and 'b' (SPFCF). The bottom MG is also connected to an SPNE unit with SPFs labeled 'b' (SPFCF). Both MGs are connected to an IP network via routers. The MGC is connected to the top MG via an H.248 SPNE package. The top MG is connected to the bottom MG via a Q.52, Q.55 package. The IP network is shown as a circle containing three routers. A legend indicates: 'a' SPFSF, 'b' SPFCF, and a double-headed arrow for interworking.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Figure 3/Q.115.0 – VoIP Gateway (decomposed architecture); H.248 SPNE package (as defined in this Recommendation) is the control protocol. The diagram shows a Media Gateway Controller (MGC) connected to two Media Gateways (MG). The top MG is connected to an SPNE unit containing SPFs (Signal Processing Functions) labeled 'a' (SPFSF) and 'b' (SPFCF). The bottom MG is also connected to an SPNE unit with SPFs labeled 'b' (SPFCF). Both MGs are connected to an IP network via routers. The MGC is connected to the top MG via an H.248 SPNE package. The top MG is connected to the bottom MG via a Q.52, Q.55 package. The IP network is shown as a circle containing three routers. A legend indicates: 'a' SPFSF, 'b' SPFCF, and a double-headed arrow for interworking. + +**Figure 3/Q.115.0 – VoIP Gateway (decomposed architecture); H.248 SPNE package (as defined in this Recommendation) is the control protocol** + +# 7 Protocols + +## 7.1 TDM + +The protocol to control standalone Echo Control Devices is defined in ITU-T Rec. Q.52. + +The protocols (protocol family, including CAS, SS7 and LAN) to control one or more SPF of a SPNE is defined in ITU-T Rec. Q.55. If a "public" IP network is used for the transport of the control signalling, then ITU-T Rec. Q.56 could be used. + +## 7.2 VoIP + +This clause describes the Signal Processing Network Equipment (SPNE) package for H.248. It allows a Media Gateway Controller to control the SPFs of a SPNE equipment either integrated into or attached to a Media Gateway. The SPNE equipment may include echo cancellation (without non linear processor), automatic level control, noise reduction and frequency equalization. + +### SPNE Control Package + +PackageID: spne, (-----) + +Version: 1 + +Extends: TDM Package (tdmc (0x000d) Version 1 + +This package defines properties and events for SPNE functions controlled by or integrated into a media gateway. Note that echo cancellers associated with media gateways are assumed to be compliant with ITU-T Rec. G.168 as indicated in ITU-T Rec. G.177. + +Logic that determines which SPNE function is enabled or disabled during a call is outside the scope of this Recommendation. + +### 7.2.1 Properties + +#### **Non Linear Processing** + +PropertyID: nlp (0x0003) + +Controls the non-linear processing property of an ECD on the TDM termination. + +Type: enumeration + +Possible Values: + +DISABLE (0x0000) + +ENABLE (0x0001) + +Defined in: LocalControlDescriptor + +Characteristics: Read/Write + +#### **Comfort Noise Injection** + +PropertyID: cni (0x0004) + +This controls the comfort noise injection function of the ECD on the TDM termination. + +Type: enumeration + +Possible Values: + +DISABLE (0x0000) + +ENABLE (0x0001) + +Defined in: LocalControlDescriptor + +Characteristics: Read/Write + +#### **Automatic Level Control** + +PropertyID: alc (0x0005) + +This provides control information for incoming automatic level control on the TDM termination. + +Type: enumeration + +Possible Values: + +DISABLE (0x0000) + +ENABLE TYPE 0 (0x0001) + +ENABLE TYPE 1 (0x0002) + +ENABLE TYPE 2 (0x0003) + +ENABLE TYPE 3 (0x0004) + +Defined in: LocalControlDescriptor + +Characteristics: Read/Write + +#### **Frequency Equalization** + +PropertyID: fe (0x0006) + +This controls the frequency equalization function of a TDM termination. The characteristics of the frequency equalization type is determined and configured by manufacturer and/or carrier. + +Type: enumeration + +Possible Values: + +DISABLE (0x0000) +ENABLE TYPE 0 (0x0001) +ENABLE TYPE 1 (0x0002) +ENABLE TYPE 2 (0x0003) +ENABLE TYPE 3 (0x0004) + +Defined in: LocalControlDescriptor + +Characteristics: Read/Write + +#### **Noise Reduction** + +PropertyID: in-nrd (0x0007) + +This controls the incoming noise reduction function of a TDM termination. The characteristics of the incoming noise reduction function type is determined and configured by manufacturer and/or carrier. + +Type: enumeration + +Possible Values: + +DISABLE INCOMING (0x0000) +ENABLE INCOMING TYPE 0 (0x0001) +ENABLE INCOMING TYPE 1 (0x0002) +ENABLE INCOMING TYPE 2 (0x0003) +ENABLE INCOMING TYPE 3 (0x0004) + +Defined in: LocalControlDescriptor + +Characteristics: Read/Write + +PropertyID: out-nrd (0x0009) + +This controls the outgoing noise reduction function of a TDM termination. The characteristics of the outgoing noise reduction function type is determined and configured by manufacturer and/or carrier. + +Type: enumeration + +Possible Values: + +DISABLE OUTGOING (0x0000) +ENABLE OUTGOING TYPE 0 (0x0001) +ENABLE OUTGOING TYPE 1 (0x0002) +ENABLE OUTGOING TYPE 2 (0x0003) +ENABLE OUTGOING TYPE 3 (0x0004) + +Defined in: LocalControlDescriptor + +Characteristics: Read/Write + +Events: None + +Signals: None + +Statistics: None + +### **7.2.2 Procedures** + +#### **Echo Cancellation** + +When a MGC determines, through Q.115.1 echo control logic, a need to provide an echo control device (ECD) on a connection, it initiates a command to the MG. The MG, upon receipt of a property with the ECD indication, enables the echo control device associated with the specified termination if the value is ENABLE, or disables the echo control device if the value is DISABLE. + +#### **Non Linear Processing** + +Echo cancellers include a function called a non-linear processor (NLP). This operates as a smart attenuator, and eliminates residual echo during periods when only one party is speaking. In some cases the NLP function is automatically enabled when the ECD is enabled, however, in other network configurations, it is beneficial to speech quality to disable the NLP independent of the ECD. A network operator may determine that the NLP should be disabled for certain calls. When a MGC determines a requirement for disabling the NLP associated with a termination, it will send this package to the MG. How the MGC determines the requirement for use of the NLP is outside the scope of this Recommendation. + +#### **Automatic Level Control** + +When a MGC determines a requirement for automatic level control of the media stream, it will send a package to a MG to enable a selected Type ALC associated with the termination. How the MGC determines the requirement for use of the ALC is outside the scope of this Recommendation. + +#### **Frequency Equalization** + +When a MGC determines a requirement for frequency equalization of the media stream, it will send a property to a MG to enable a selected type of FE associated with the termination. How the MGC determines the requirement for use of the FE is outside the scope of this Recommendation. + +#### **Noise Reduction** + +When a MGC determines to insert a Noise Reduction Device/Function to reduce the amount of unwanted noise, it will enable a NRD associated with the termination by sending a property to the MG. How the MGC determines the requirement for use of the NRD is outside the scope of this Recommendation. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37b0cfe33d071d13ba118b1a5906674be8c2a981 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd74ca42acf9ead7ab5db28c41e935c618993b3543d491e1862790328285e249 +size 72298 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b9e09c225c71dac4613d034bf3a397a861b12bf --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:277596830f987ea9f05c37d3dda6822b563a27c5987e12a43f22cc865ab3905a +size 47010 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..992c370341e209b797b60edb3ce3acb0d4a0d330 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d1b8ef6f6b37a3c16b076ed96f824eddd63c3040883fe19d841894ba27b4397 +size 42486 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2c99457776a4e2630f7d0f3774553a960f156b8 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad9c078ce82f5cafca4a16b7d05ef9f55495bc123eff3e17f5a0a66b7a8b94e2 +size 68333 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f414bfcd216f9d5a3d077066d969b202837b8210 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8df9a9a7136b60759126314a39488a13da1f04abee330f270f03c8b665e088 +size 46784 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07882e53216010a60e9a65c2269a1383f90fa8f5 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d55bc1404a00110e016e59b37c568857c51417048eaede96b71d932cccb62e1 +size 8202 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cca63fb1e41d4a7396dff05203d890c1d74a3fd6 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca720aac010de3515d1c9945e65deeb5d9f4b5ad41a91841af94ab3cf57485b6 +size 104206 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbfe5d216e4552e9f4c3869df19923a03960b67e --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092704115199c3ea1f0a2fb70930e715b0b3308f20bce25ea79f3c3f183cdeab +size 107689 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99200cf393c31befd4ccca9ec2ee1d1aef73c3b1 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:739b3b1bf376bffeea183e31ae5c29c7ab6dd34718d03ebb8b9fb129b100ea45 +size 54129 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0963bfed6768c256f1e435dbf4c594ed42f26af8 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78c2232481a21904113f3421f170d2d7727fe26cd1a728f80341711277a8c9bc +size 60628 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfa132a26ee00ed4f6618558a3eb2c283271c9d3 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:346d621728e941bde4a3f1aad24eb73814cd3f1ed1e67053c12409b09dae45b8 +size 65163 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5db6545aedab79741ebae9b27bb363b3_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5db6545aedab79741ebae9b27bb363b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51878e585ff7e08309b152ae8d3c9c9d81893d26 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5db6545aedab79741ebae9b27bb363b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11059c38d030f44cbf5d1fa3eff3cb523e6984b933eaff2b892a9816de3b71c5 +size 65153 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6f3b455da8dc1c09025d06d7ff99608fbce5a9a --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd8ca59fb4383c42da6fe6d5c03e19d8f72330437fc4592b1b3af1a72a26495b +size 112241 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1858f1f0670e15306411bc20280cb9e0daae2872 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ac2e10001f42839a206cfd55cec51076e1baf2fa720dbab002529907056e275 +size 16727 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1733b01fc1cf8d819fe6230dccf64fd0cd908d4 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6fc6955bb35e3c095010b4112bd9b75ad58afd83055b09588ec061ad54497e5 +size 91002 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53fb2aa19492c2287091fd6a3c2835a0a5515cac --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d38ed8f27c5ecd7d10f714e08793098bd93ca97412ca063038d1bc260333158d +size 143526 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed93297a41a9d8dbc5bd4ddc67d571af9714c4bb --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64a6ba6f0bfd64a1f9878ca8a0ab37fdf681cfb2cc36a76cc771471d1075987c +size 120441 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c93286480a98c1273866577342e66465d32032a0 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed54a1c207273a6e7228a2161cf038d9ebd1d9f291bf443346a6381da67bea0d +size 74732 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..558804c3c2ecc6eb69e9759d19873acb6ddf6fd4 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05179ec353c68365f472fe1e44efe2289100dec1837cedacf33b0cd010d9917a +size 90588 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..039d41a5140a62d273f74802d361a9921f8ec82a --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4adf55394520a2da1562d3252f3fc4f99b4a932fe8d83760982e937ddb8411f1 +size 109088 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bc7e3b27aafcf5f11107085df767ebe1b2da114 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ee4780c82e344f7298d9fa6a2793253761898805cd1da535347dc9a572319c6 +size 48316 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3151190f4006f34097cb17fa4d5444ba939a983c --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6222a771d30aab24d7954f48069750dfc1e78a97f90c569a5e43a008a2f8e75f +size 89065 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0170d2e2c9c7d590e1681d32f0120da4166d6502 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:738320a7cc904d2183bce1888e67af137019ad19837afd0e62b3cefbdf7c54d4 +size 55718 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bb40a9f86f8f309eb933c91afa76fa52b94fd5e --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a65382a5ae1db96e4dfbc65468f4e8b24df83acc288942d513c14112bb3935a9 +size 39134 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1964bceeb03148a8f99f839d1f08a55d8eac24e8 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50e875ea0fadcd73be33bb39bb2827f2db45941e40f4e0dc2df9391393d208c4 +size 101043 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88f8b5e04680895d484dec4c076f79d19d397a8f --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bf63ad21197dbe5f078f4073eb7d712427f5ae8bf73cc7e4ad8c1c503af7f8e +size 84937 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1bc333c60d8e070bc7f926c18658b4fc8a866fd --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a484198252ec665820f0d68c9c65bc8b9f1b098f69a1f616c3726241eaa0ae92 +size 35583 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..782dd4894191aa79c0236fdc3e2c7c05aba778a0 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c258182de2e82c5f12ac171adf5e788a23f5a369bf7cd227eca6ab3c5da6dd0 +size 108401 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2e9d415b883fe24e02bd4d885b935097bdfa266 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d30e7b6f1eee68a517c4189a270201e850714c9686743850d54fd2393ee7c1ca +size 103782 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..805b9d6dab9bd44b85e026699061a07946e13743 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4ea651a1441dde00c6981705c99f219e2d228ba817add2a8be66c9bf9cc44d4 +size 81950 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..600f8856d42928aa2b2d535b616563816f87c949 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b5073a7586303552ea8e870bda6992ca483cea9cc79d218efe40d6569f94450 +size 84253 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdefaf7208b5d58378e224f285bc85bc2019796b --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c939bf220c0beb1617e95b292167236ec3c15992a588225c0fbbe28aed2b2008 +size 101558 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d9ad73155743292a83558306ffa5e23607175f7 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b64136e877ff8cf825e6ed3f8a8d06fc093e1136f9a900d1b97c2789b1b23ea4 +size 117951 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0dbbed3268db032c60bae0960ead87a725802eb --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a63da10b652c5f7c1ddad6562bdebd1b631e1bdf560d1bb28c703b9459d95ebd +size 105604 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cf46a14e78b9ab0d66ebbc91cc6109897b96b6c --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:799ec033725a146601350dd2663222a9bdd6acac777fbb47282ac79280c36ee5 +size 98291 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3b6cd893cb1dc3e185507ce619d323aae5cc348 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc382c6ef93456a89ef31e10e994a13481ea6a75ec3aef8c85e96685335990f8 +size 15270 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8947296d397501410635a4dead81341f9113ca0 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d50b4697f69a53a7ad0e2edadee9b9fde572b1ee888e7431bb4a0a2459fe00b6 +size 129767 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..929567bade8718ed7622281a6ef9857f10ef4436 --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a2ce02db9b247d10da696373a63928d38e9d803d65d092c915f24f3f3b39797 +size 119465 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07529d67eb67928fd41859ddb0fd224bc5ae183f --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e86fbe00787afaebd3400231c0e8d96dc1f0926901b6227fd5e1248366d19d0 +size 116895 diff --git a/marked/Q/T-REC-Q.1152-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f7dc56ee73e4b0c87260d762e099af95bb3afeca --- /dev/null +++ b/marked/Q/T-REC-Q.1152-199303-I_PDF-E/raw.md @@ -0,0 +1,2087 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1152** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +# **INTERWORKING WITH SATELLITE MOBILE SYSTEMS** --- + +# **PROCEDURES FOR INTERWORKING BETWEEN INMARSAT AERONAUTICAL MOBILE SATELLITE SYSTEM AND THE INTERNATIONAL PUBLIC SWITCHED TELEPHONE NETWORK/ISDN** + +**ITU-T Recommendation Q.1152** + +(Previously "CCITT Recommendation") + +--- + +## FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.1152 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +## --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------------------------------|-------------| +| 1 Introduction ..... | 1 | +| 2 Conversion of information elements ..... | 1 | +| 2.1 Signalling System R2..... | 1 | +| 2.2 Signalling System No. 7 (TUP) ..... | 4 | +| 2.3 Signalling System No. 5 ..... | 6 | +| 3 Incoming INMARSAT aeronautical logic procedures (air-to-ground calls)..... | 6 | +| 4 Outgoing INMARSAT aeronautical logic procedures (ground-to-air calls) ..... | 16 | +| 5 Interworking of INMARSAT aeronautical signalling system with itself..... | 21 | +| 6 Interworking of incoming INMARSAT aeronautical to Signalling System R2..... | 23 | +| 7 Interworking of Signalling System R2 to outgoing INMARSAT aeronautical ..... | 26 | +| 8 Interworking of incoming INMARSAT aeronautical to Signalling System No. 7 (TUP) ..... | 29 | +| 9 Interworking of Signalling System No. 7 (TUP) to outgoing INMARSAT aeronautical ..... | 29 | +| 10 Interworking of incoming INMARSAT aeronautical to Signalling System No. 5 ..... | 35 | +| 11 Interworking of Signalling System No. 5 to outgoing INMARSAT aeronautical ..... | 35 | + + + +# PROCEDURES FOR INTERWORKING BETWEEN INMARSAT AERONAUTICAL MOBILE SATELLITE SYSTEM AND THE INTERNATIONAL PUBLIC SWITCHED TELEPHONE NETWORK/ISDN + +*(Melbourne, 1988; modified at Helsinki, 1993)* + +## 1 Introduction + +This Recommendation provides the detailed procedures for interworking between the INMARSAT aeronautical system and signalling systems of the public fixed network. For a brief description of the INMARSAT aeronautical system, see Appendix I/Q.1151. + +## 2 Conversion of information elements + +Tables 1 and 2 list the signals of the INMARSAT aeronautical system that are relevant for the purpose of interworking with the PSTN/ISDN. The forward interworking telephone events (FITEs) and backward interworking telephone events (BITEs), as defined in Annex A/Q.601-Q.608, that correspond to each of these signals is also provided in the tables. + +TABLE 1/Q.1152 + +### INMARSAT aeronautical – forward signals + +| FITE No. | Message: information element: value | +|-----------------------------------------------------------------------------------------------------|---------------------------------------------------| +| Ground-to-air calls | | +| 1 | Call announcement: AES id: called terminal | +| 17 | Call announcement: service: telephone | +| 22 | Channel release: Cause: Normal clearing | +| Air-to-ground calls | | +| 17 | Access request: message type: public/crew voice | +| 18 | Access request: message type: crew distress voice | +| 1 | Access request: address digits 0, 1 | +| 1 | Call information: address digits 2 ... 17 | +| 22 | Channel release: Cause: Normal clearing | +| NOTE – Signals required for interworking with Signalling System No. 7 (ISUP) are for further study. | | + +Tables 3 to 18 give the relationship between signals of the fixed network signalling systems and the INMARSAT aeronautical system. + +### 2.1 Signalling System R2 + +**2.1.1** Table 3 gives the relationship between messages in the INMARSAT aeronautical signalling system and forward signals in Signalling System R2 for air-to-ground calls, i.e. interworking of INMARSAT aeronautical to Signalling System R2. + +Table 4 shows the relationship between forward signals in Signalling System R2 and messages in the INMARSAT aeronautical signalling system for ground-to-air calls. In the comment column actions taken by the MSSC are indicated, + +in particular for signals of R2 which have no equivalent message in the INMARSAT aeronautical system. + +The signal numbers for forward signals of Signalling System R2 are those given in Table A.7/Q.601-Q.608. + +TABLE 2/Q.1152 + +### **INMARSAT aeronautical – backward signals** + +| BITE No. | Message: information element: value | +|---------------------|--------------------------------------------------------| +| Ground-to-air-calls | | +| 5 | Test | +| 22 | Connect | +| 29 | Channel release: Cause: Normal clearing | +| 16 | Call attempt result: Cause: User busy | +| 12 | Call attempt result: Cause: No channel available | +| 17 | Call attempt result: Cause: Destination out of service | +| Air-to-ground-calls | | +| 22 | Connect | +| 2 | Call attempt result: Address complete | +| 29 | Channel release: Cause: Normal clearing | +| 20 | Channel release: Cause: Unspecified | +| 16 | Channel release: Cause: User busy | +| 15 | Channel release: Cause: Unassigned number | +| 17 | Channel release: Cause: Destination out of service | +| 12 | Channel release: Cause: No channel available | +| 14 | Channel release: Cause: Invalid number format | + +NOTE – Signals required for interworking with Signalling System No. 7 (ISUP) are for further study. + +TABLE 3/Q.1152 + +### **Conversion of forward signals in the INMARSAT aeronautical signalling system to Signalling System R2 Air-to-ground calls** + +| INMARSAT aeronautical signalling system
Message: information element: value | Signalling System R2
Signal name: information element | Signal No. | +|--------------------------------------------------------------------------------|----------------------------------------------------------|------------| +| Access request: message type | Calling party's category | | +| – public voice | – subscriber/operator without forward transfer facility | 12 | +| – crew voice | – subscriber/operator without forward transfer facility | 12 | +| – crew distress voice | – subscriber/with priority | 14 | +| Access request: address digits 0, 1 | Country code indicator (echo suppressor controls) | 10 | +| Call information: digits 2 to 17 | Address signals/first digit | 1 | +| Test | Not applicable | | +| Channel release: Cause: Normal clearing | Clear forward | 16 | + +NOTE – Signal No. 21, nature of circuit indicator: one satellite circuit in the connection, is generated by the MSSC, if required. + +TABLE 4/Q.1152 + +#### **Conversion of forward signals in Signalling System R2 to INMARSAT aeronautical signalling system Ground-to-air calls** + +| Signal No. | Signalling System R2
Signal name | INMARSAT aeronautical signalling system
Message: information element: value | Comments | +|------------|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------------| +| 1 | Address signals | Call announcement: AES identity, called terminal | | +| 2-6 | Language digit: I-1, ... 5 | | Interpreted by MSSC | +| 7 | Discriminating digit | | Interpreted by MSSC | +| 8 | Country code indicator, outgoing
half suppressor required | | MSSC will insert echo control
device if needed | +| 9 | Country code indicator, no echo
suppressor required | | Interpreted by MSSC | +| 10, 11 | Country code indicator, incoming
half echo suppressor required | | Interpreted by MSSC | +| 12 | Calling party's category, subscriber
or operator without forward transfer
facility | Call announcement
– service: telephone | | +| 13 | Calling party's category, data
transmission control | | Not applicable | +| 14 | Calling party's category, subscriber
with priority | Call announcement
– service: telephone, priority for further
study | | +| 15 | Calling party's category, operator
with forward transfer capability | Call announcement
– service: telephone | | +| 16 | Clear forward | Channel release: Cause: Normal clearing | | +| 17 | Forward transfer | | Not applicable | +| 18 | First digit: I-1, I-2 ... I-10 | | Interpreted by MSSC | +| 19 | Reply to A-14: I-1 ... I-10 | | Not applicable | +| 20 | Reply to first A-13; I-13 | | Not applicable | +| 21 | Reply to first A-13; I-14 | | Not applicable | + +**2.1.2** Table 5 gives the relationship between messages in the INMARSAT aeronautical signalling system and backward signals in Signalling System R2 for ground-to-air calls, i.e. interworking of Signalling System R2 to INMARSAT aeronautical. + +Backward signals in Signalling System R2 generated by the MSSC for unsuccessful ground-to-air calls are given in Table 5 *bis*. These signals are not related to any specific message received from the aircraft earth station. + +TABLE 5/Q.1152 + +#### **Conversion of backward signals in the INMARSAT aeronautical signalling system to Signalling System R2 Ground-to-air-calls** + +| INMARSAT aeronautical signalling system
Message: information element: value | Signalling System R2
Signal name: information element | Signal No. | +|--------------------------------------------------------------------------------|----------------------------------------------------------|------------| +| Test | International, subscriber line free, charge | 13 | +| Connect | Answer signal | 11 | +| Channel release: Cause: Normal clearing | Clear back | 12 | +| Call attempt result: Cause: | | | +| – user busy | Subscriber line busy | 5 | +| – no channel available | Congestion on the national network | 1 | +| – destination out of service | Subscriber line out of order | 10 | +| – others | International; send special info tone | 14 | + +TABLE 5 bis/Q.1152 + +#### **Unsuccessful call events and backward signals in Signalling System R2 Ground-to-air-calls** + +| INMARSAT aeronautical signalling system
Event in INMARSAT system | Signalling System R2
Signal name: information element | Signal No. | +|---------------------------------------------------------------------|----------------------------------------------------------|------------| +| Congestion in MSSC | B4 – Congestion | 6 | +| Incomplete AES number | B5 – Unallocated number | 7 | +| Continuity test failure | B8 – Subscriber line out of order | 10 | +| AES barred for incoming access | B2 – Send special info tone | 4 | +| Called AES not logged on | B2 – Send special info tone | 4 | +| No satellite channel frequency/equipment available | B4 – Congestion | 6 | + +Table 6 gives the relationship between backward signals in Signalling System R2 and messages in the INMARSAT aeronautical signalling system for air-to-ground calls, i.e. interworking of INMARSAT aeronautical to Signalling System R2. The comments column indicates specific actions taken by the MSSC. + +The signal number of backward signals of Signalling System R2 are those given in Table A.11/Q.601-Q.608. + +### 2.2 Signalling System No. 7 (TUP) + +**2.2.1** Tables 7 and 8 are similar to Tables 3 and 4, respectively, and apply to forward signals in Signalling System No. 7 (TUP). + +The signal numbers for forward signals of Signalling System No. 7 (TUP) are those given in Table A.5 bis/Q.601-Q.608. + +TABLE 6/Q.1152 + +### **Conversion of backward signals in Signalling System R2 to INMARSAT aeronautical signalling system Air-to-ground calls** + +| Signal No. | Signalling System R2
Signal name | INMARSAT aeronautical signalling system
Message: information element: value | Comments | +|------------|-------------------------------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------| +| 1 | A4 – Congestion on the national network | Channel release: remote public network,
switching equipment
congestion | | +| 2 | A6 – Address complete, charge, set up,
speech condition | Call attempt
result: address complete | | +| 3 | A15 – Congestion in an international
exchange or at its output | Channel release: international network,
switching equipment
congestion | | +| 4 | B2 – Send special information tone | Channel release: remote public network,
normal – unspecified | | +| 5 | B3 – Subscriber line busy | Channel release: remote public network, user
busy | | +| 6 | B4 – Congestion | Channel release: remote public network,
switching equipment
congestion | | +| 7 | B5 – Unallocated number | Channel release: remote public network,
unassigned number | | +| 8 | B6 – Subscriber line free, charge | Call attempt result: address complete | | +| 9 | B7 – Subscriber line free, no charge | Call attempt result: address complete | No-charge information, used by
MSSC only | +| 10 | B8 – Subscriber line out of order | Channel release: remote public network,
destination out of service | | +| 11 | Answer | Connect | | +| 12 | Clear back | Channel release: Cause: Normal clearing | Clearback
supervision
done by MSSC | +| 13 | B1-B6 – International, subscriber line
free, charge | Call attempt result: address complete | | +| 14 | B9, B10 – International, send special
information tone | Channel release: international network,
normal – unspecified | | +| 15 | B11-B15– Congestion | Channel release: remote public network,
switching equipment
congestion | | + +**2.2.2** Tables 9, 9 *bis* and 10 are similar to Tables 5, 5 *bis* and 6, respectively, and apply to backward signals in Signalling System No. 7 (TUP). + +The signal numbers for backward signals in Signalling System No. 7 (TUP) are those given in Table A.9 *bis*/Q.601-Q.608. + +TABLE 7/Q.1152 + +#### **Conversion of forward signals in INMARSAT aeronautical signalling system to Signalling System No. 7 Air-to-ground calls** + +| INMARSAT aeronautical signalling system
Message: information element: value | Signalling System No. 7
Signal name: information element | Signal No. | +|--------------------------------------------------------------------------------|-------------------------------------------------------------|------------| +| Access request: message type | Calling party's category indicator: | 13 | +| Public voice/ | Ordinary subscriber/ | 13 | +| Crew voice/ | Ordinary subscriber/ | 13 | +| Crew distress voice/ | Subscriber with priority | 14 | +| Access request: address digits 0, 1 | Address signals: Digit 1, 2 ... 0 | 1 | +| | nature of address indicator, international number | 3 | +| Call information: digit 2 to 17 | | | +| Test | Continuity check performed on previous circuit | 22 | +| Channel release: Cause: Normal clearing | Clear forward signal | 16 | + +NOTE – Signal No. 5, nature of circuit indicator, one satellite in connection, is generated by the MSSC. + +### 2.3 Signalling System No. 5 + +**2.3.1** Tables 11 and 12 are similar to Tables 3 and 4, respectively, and apply to forward signals in Signalling System No. 5. + +The signal numbers for forward signals of Signalling System No. 5 are those given in Table A.4/Q.601-Q.608. + +**2.3.2** Tables 13, 13 *bis* and 14 are similar to Tables 5, 5 *bis* and 6, respectively, and apply to backward signals in Signalling System No. 5. + +The signal numbers for backward signals in Signalling System No. 5 are those given in Table A.8/Q.601-Q.608. + +**2.4** The relationship between forward and backward signals of Signalling System No. 7 (ISUP) and messages of the INMARSAT aeronautical signalling system is for further study. + +## 3 Incoming INMARSAT aeronautical logic procedures (air-to-ground calls) + +Figure 1 contains the procedures for the incoming INMARSAT aeronautical signalling system. + +This description only includes those aspects of the INMARSAT aeronautical system which have to be implemented for interworking purposes. Internal procedures, such as those required for setting up and clearing satellite channels are not shown. This also applies to pre-emption procedures for assigning channels to distress calls. + +The following details should be noted: + +**3.1** The access request contains information elements for the required service, and the required network, plus two address digits. For some private networks, and/or subscription services on public networks, this information will be sufficient to determine the complete call routing. In all but the most exceptional cases, it will be enough information to select a circuit for onward routing from the MSSC. + +TABLE 8/Q.1152 + +### **Conversion of forward signals in Signalling System No. 7 TUP to INMARSAT aeronautical signalling system Ground-to-air calls** + +| Signal No. | Signalling System No. 7
Signal name | INMARSAT aeronautical signalling system
Message: information element: value | Comments | +|------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------------------------------------| +| 1 | Address signals | Call announcement: AES ID, called terminal | | +| 2 | Nature of address indicator, national significant number | – | Interpreted by MSSC | +| 3 | Nature of address indicator, international number | – | Interpreted by MSSC | +| 4 | Nature of circuit indicator, no satellite in connection | – | Ignored by MSSC | +| 5 | Nature of circuit indicator, one satellite in connection | – | Ignored by MSSC | +| 6 | Echo suppressor indicator, outgoing half-echo suppressor not included | – | MSSC will insert echo control device if needed | +| 7 | Echo suppressor indicator, outgoing half-echo suppressor included | – | Interpreted by MSSC | +| 8-12 | Calling party's category indicator, language digit | Call announcement
– service: telephone | – | +| 13 | Calling party's category indicator, ordinary calling subscriber | Call announcement
– service: telephone | – | +| 14 | Calling party's category indicator, calling subscriber with priority | Call announcement
– service: telephone, priority for further study | – | +| 15 | Calling party's category indicator, data call | – | Not applicable | +| 16 | Clear forward | Channel release: Cause: Normal clearing | – | +| 17 | Forward transfer | – | Not applicable | +| 18 | Continuity proved | – | Interpreted by MSSC | +| 19 | Continuity check failure | Channel release: Cause: Normal clearing | – | +| 20 | Continuity check not required on this circuit | – | Interpreted by MSSC | +| 21 | Continuity check not required on this circuit | – | Interpreted by MSSC | +| 22 | Continuity check performed on previous circuit | – | Interpreted by MSSC | +| 23 | Service information | – | Interpreted by MSSC | +| 24 | General set-up message | – | Interpreted by MSSC | + +**3.2** The initial analysis of the request checks that the AES is authorized for the service requested and finds a suitable channel and channel unit, on which to service the call. The call is aborted if the AES is not an authorized user of the INMARSAT system. + +**3.3** In the cases where all of the required address information is contained in the access request signal unit, an address message is received by the incoming procedure, once continuity of the assigned satellite channel has been successfully tested. + +TABLE 9/Q.1152 + +### **Conversion of backward signals in INMARSAT aeronautical signalling system to Signalling System No. 7 TUP Ground-to-air calls** + +| INMARSAT aeronautical signalling system
Message: information element: value | Signalling System No. 7
Signal name | Signal No. | +|--------------------------------------------------------------------------------|------------------------------------------------|------------| +| Test | AFC: Address complete, subscriber free, charge | 4 | +| Connect | ANC: Answer, charge | 16 | +| Channel release: Cause: Normal clearing | CLB: Clear back | 19 | +| Call attempt result: Cause: | | | +| – user busy | SGB: Subscriber busy | 12 | +| – no channel available | CGC: Circuit group congestion | 8 | +| – destination out of service | LOS: Line out of service | 13 | +| – others | SST: Send special information tone | 14 | + +TABLE 9 bis/Q.1152 + +#### **Unsuccessful events and backward signals in Signalling System No. 7 Ground-to-air calls** + +| INMARSAT aeronautical signalling system
Event in INMARSAT system | Signalling System No. 7
Signal name | Signal No. | +|---------------------------------------------------------------------|----------------------------------------|------------| +| Congestion in MSSC | SEC: Switching equipment congestion | 7 | +| No satellite channel frequency/equipment available | NNC: National network congestion | 9 | +| Incomplete AES number | ADI: Address incomplete | 10 | +| Continuity test failure | LOS: Line out of service | 13 | +| AES barred for incoming access | SST: Send special information tone | 14 | +| Call AES not logged on | SST: Send special information tone | 14 | + +**3.4** The called address is analysed to verify its integrity. The satellite channel may be cleared at this point, either if the dialled address is incomplete or if the AES goes on-hook. The call may also be aborted if proper credit card data is not received from the AES. + +**3.5** The dialled digits are transferred to the interworking procedure, and the answer signal is awaited. The last digit may be withheld until receipt of credit card information. All successful address complete signals are converted to a call attempt result message, with the cause field set to address complete. + +**3.6** Unsuccessful call event signals (BITes 9-20) are transferred to the AES by the call attempt result message, with the cause field set appropriately. + +**3.7** On receipt of the answer signals, the connect message is sent to the AES. + +**3.8** The call is cleared in the normal way, either on receipt of a release message from the interworking procedure, or an indication of AES on-hook conveyed by means of a channel release message. + +TABLE 10/Q.1152 + +### **Conversion of backward signals in Signalling System No. 7 TUP to INMARSAT aeronautical signalling system Air-to-ground calls** + +| Signal No. | Signalling System No. 7
Signal name | INMARSAT aeronautical signalling system
Message: information element: value | Comments | +|------------|---------------------------------------------------|--------------------------------------------------------------------------------|-----------------------------------------| +| 1 | ADC: Address complete, charge | Call attempt result: Address complete | – | +| 2 | ADN: Address complete, no charge | Call result: Address complete | No-charge information used by MSSC only | +| 3 | ADX: Address complete, coinbox | Call result: Address complete | – | +| 4 | AFC: Address complete, subscriber free, charge | Call result: Address complete | – | +| 5 | AFN: Address complete, subscriber free, no charge | Call result: Address complete | No-charge information used by MSSC only | +| 6 | AFX: Address complete, subscriber free, coinbox | Call result: Address complete | – | +| 7 | SEC: Switching equipment congestion | Channel release: international network, switching equipment congestion | – | +| 8 | CGC: Circuit-group congestion | Call result: international network, no channel available | – | +| 9 | NNC: National network congestion | Call result: remote public network, switching equipment congestion | – | +| 10 | ADI: Address complete | Call result: remote public network, invalid number format | – | +| 11 | UNN: Unallocated number | Call result: remote public network, unassigned number | – | +| 12 | SGB: Subscriber busy | Call result: remote public network, user busy | – | +| 13 | LOS: Line out of service | Call result: remote public network, destination out of service | – | +| 14 | SST: Send special information tone | Call result: international network, normal – unspecified | – | +| 15 | CFL: Call failure | Call result: international network, normal – unspecified | – | +| 16 | ANC: Answer, charge | Connect | – | +| 17 | ANN: Answer, no charge | Connect | No charge information used by MSSC only | +| 18 | RAN: Reanswer | Connect | – | +| 19 | CLB: Clearback | Channel release: Cause: Normal clearing | Clearback supervision done by MSSC | +| 20 | GRQ: General request message | – | Interpreted by MSSC | +| 21 | Call unsuccessful, access barred | Call attempt result: remote public network, normal – unspecified | – | +| 22 | DPN: Call unsuccessful, digital path not provided | – | Not applicable | + +TABLE 11/Q.1152 + +### **Conversion of forward signals in INMARSAT aeronautical signalling system to Signalling System No. 5 Air-to-ground calls** + +| INMARSAT aeronautical signalling system
Message: information element: value | Signalling System No. 5
Signal name | Signal No. | +|--------------------------------------------------------------------------------|----------------------------------------|------------| +| Access request: message type | | | +| – public voice | Discriminating digit 0 | 7 | +| – crew voice | Discriminating digit 0 | 7 | +| – crew distress voice | Discriminating digit 0 | 7 | +| Access request: address digits: 0, 1 | Address digits | 1 | +| Call information: digits 2 to 17 | | | +| Test | Not applicable | – | +| Channel release: Cause: Normal clearing | Clear forward | 10 | + +TABLE 12/Q.1152 + +### **Conversion of forward signals in INMARSAT aeronautical signalling system to Signalling System No. 5 Ground-to-air calls** + +| Signal No. | Signalling System No. 5
Signal name | INMARSAT aeronautical signalling system
Message: information element: value | Comments | +|------------|----------------------------------------|--------------------------------------------------------------------------------|---------------------| +| 1 | Address signals | Call announcement: AES identity,
called terminal | | +| 2-6 | Language digit: 1 ... 5 | – | Interpreted by MSSC | +| 7 | Discriminating digit 0 | Call announcement
– service: telephone | | +| 8 | Start of pulsing signal KP1 | – | Interpreted by MSSC | +| 9 | Start of pulsing signal KP2 | – | Interpreted by MSSC | +| 10 | Clear forward | Channel release: Cause: Normal
clearing | | +| 11 | Forward transfer | – | Not applicable | + +TABLE 13/Q.1152 + +### **Conversion of backward signals in INMARSAT aeronautical signalling system to Signalling System No. 5 Ground-to-air calls** + +| INMARSAT aeronautical signalling system
Message: information element: value | Signalling System No. 5
Signal name | Signal No. | +|--------------------------------------------------------------------------------|----------------------------------------|------------| +| Test | Inform that ST has been sent | 5 | +| Connect | Answer signal | 2 | +| Channel release: Cause: Normal clearing | Clear back | 3 | +| Call attempt result: Cause: | | | +| – user busy | Busy flash signal | 1 | +| – no channel available | Busy flash signal | 1 | +| – destination out of service | Information tone (Note) | – | +| – others | Information tone (Note) | – | + +NOTE – May include appropriate recorded announcement. + +TABLE 13 bis/Q.1152 + +#### **Unsuccessful call events and backward signals in Signalling System No. 5 Ground-to-air calls** + +| INMARSAT aeronautical signalling system
Event in INMARSAT system | Signalling System No. 5
Signal name | Signal No. | +|---------------------------------------------------------------------|----------------------------------------|------------| +| Congestion in MSSC | Busy flash | 1 | +| No satellite channel frequency/equipment available | Busy flash | 1 | +| Incomplete AES number | Information tone (Note) | | +| Continuity test failure | Information tone (Note) | | +| Called AES not logged on | Information tone (Note) | | +| AES barred for incoming access | Information tone (Note) | | + +NOTE – May include appropriate recorded announcement. + +TABLE 14/Q.1152 + +### **Conversion of backward signals in Signalling System No. 7 to INMARSAT aeronautical signalling system Air-to-ground calls** + +| Signal No. | Signalling System No. 5
Signal name | INMARSAT aeronautical signalling system
Message: information element: value | Comments | +|------------|----------------------------------------|--------------------------------------------------------------------------------|---------------------| +| 1 | Busy-flash | Channel release: international network, unspecified | – | +| 2 | Answer | Connect | – | +| 3 | Clear back | Channel release: Cause: Normal clearing | – | +| 4 | Proceed to send | – | Interpreted by MSSC | +| 5 | Inform that ST has been sent | Call attempt result: address complete | | + +![Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls). The process starts at 'Idle' (0), receives a 'Request from AES', stores it, activates a register (SPITE 1), and checks for a channel. If 'AES not OK' or 'No channel', it sets location and cause fields and deactivates the register (SPITE 3) to return to 'Idle'. If 'Channel assigned (SPITE 14)', it sets up a satellite channel and waits for an address (2). From 'Await address', it handles 'Address message' (leading to digit analysis (SPITE 12) and then to connector 1), 'Channel release', 'Continuity failure', or 'Address failure' (leading to register deactivation (SPITE 3) and then to connector 4).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + Idle0([0 Idle]) --> Request[/Request from AES/] + Request --> Store[Store request message] + Store --> Activate[Activate register SPITE 1] + Activate --> Check[/Check AES find channel Note 1/] + Check -- SP --> Await1([1 Await channel]) + Await1 --> AESnotOK[/AES not OK/] + Await1 --> NoChannel[/No channel/] + Await1 --> ChannelAssigned[/Channel assigned SPITE 14/] + AESnotOK -- SP --> SetLoc[Set loc. & cause fields] + NoChannel -- SP --> SetLoc + SetLoc --> CallResult[/Call attempt result/] + CallResult --> Deactivate3[Deactivate register SPITE 3] + Deactivate3 --> Idle0 + ChannelAssigned -- SP --> SetupSat[Setup satellite channel] + SetupSat --> Await2([2 Await address]) + Await2 --> AddressMsg[/Address message/] + AddressMsg --> DigitAnalysis[/Digit analysis SPITE 12 Note 2/] + DigitAnalysis -- SP --> Connector1((1)) + Await2 --> ChannelRelease[/Channel release/] + Await2 --> ContinuityFailure[/Continuity failure/] + Await2 --> AddressFailure[/Address failure/] + AddressFailure -- "2, 5" --> Deactivate3 + Deactivate3 --> Connector4((4)) + +``` + +Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls). The process starts at 'Idle' (0), receives a 'Request from AES', stores it, activates a register (SPITE 1), and checks for a channel. If 'AES not OK' or 'No channel', it sets location and cause fields and deactivates the register (SPITE 3) to return to 'Idle'. If 'Channel assigned (SPITE 14)', it sets up a satellite channel and waits for an address (2). From 'Await address', it handles 'Address message' (leading to digit analysis (SPITE 12) and then to connector 1), 'Channel release', 'Continuity failure', or 'Address failure' (leading to register deactivation (SPITE 3) and then to connector 4). + +## NOTES + +- 1 Analyse for authorized AES ID, availability of service requested, find a suitable satellite channel and channel unit. +- 2 Includes translation of prefixes to the appropriate B-party number, and verification that the number is valid. + +FIGURE 1/Q.1152 (sheet 1 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling + (air-to-ground calls)** + +![Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + 1((1)) --> CreditCard{Credit card?} + CreditCard -- No --> SP1[SP] + CreditCard -- Yes --> CreditCardData{{Credit card data}} + CreditCardData --> SP2[SP] + SP1 --> SP2 + SP2 --> AwaitDigitAnalysis{{Await digit analysis}} + AwaitDigitAnalysis --> CircuitAvailable{{Circuit available +(SPITE 14)}} + AwaitDigitAnalysis --> ChannelRelease{{Channel release}} + AwaitDigitAnalysis --> CallFailure{{Call failure +(SPITE 13, 15-19)}} + CircuitAvailable -- SP --> ActivateInterworking{{Activate interworking procedure}} + ChannelRelease --> 2((2)) + CallFailure -- SP --> 2 + ActivateInterworking --> R((R)) + R -- 3 --> SP3[SP] + SP3 --> SP2 + +``` + +The flowchart illustrates the logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls). It begins at connector 1, leading to a decision diamond 'Credit card?'. If 'No', it goes to a splice point (SP). If 'Yes', it proceeds to a process block 'Credit card data', which also leads to a splice point (SP). Both SP points merge and lead to a wait state 'Await digit analysis'. From this state, three paths emerge: 'Circuit available (SPITE 14)', 'Channel release', and 'Call failure (SPITE 13, 15-19)'. The 'Circuit available' path leads to a process block 'Activate interworking procedure', which then leads to connector R. The 'Channel release' and 'Call failure' paths both lead to connector 2. Connector R leads to connector 3, which then leads to another splice point (SP) that loops back to the merge point before 'Await digit analysis'. Vertical labels 1, 2, and R are on the left margin. A document code 'T1143160-92/d02' is in the bottom right. + +Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls). + +FIGURE 1/Q.1152 (sheet 2 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling + (air-to-ground calls)** + +![Flowchart showing logic procedures for incoming INMARSAT aeronautical signalling. The flow starts at connector 'R 2' leading to a 'Service category?' decision. Paths branch for 'Data (FITE 19)', 'Ordinary' (leading to 'Telephone ordinary (FITE 17)'), and 'Priority' (leading to 'Telephone priority (FITE 18)'). All paths converge at a 'Digit available' decision. If 'No', it exits to connector '4 1, 7'. If 'Yes', it enters a loop: 'Transfer digit (FITE 1)' followed by 'More digits?'. If 'Yes', it loops back to 'Transfer digit'. If 'No', it goes to connector '5' which leads to the 'Await call setup' state. A separate sequence starts at connector '4 1, 7', leading to 'Set loc. & cause fields', 'Channel release', connector '4', 'Await channel cleared' state, 'Channel cleared' input, 'Deassign channel' process, and finally through 'SP' to connector '0' and the 'Idle' state.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + R2((R 2)) --> SC{Service category?} + SC --> Data[Data +(FITE 19)] + SC -- Ordinary --> TO[Telephone +ordinary +(FITE 17)] + SC -- Priority --> TP[Telephone +priority +(FITE 18)] + Data --> DA{Digit +available} + TO --> DA + TP --> DA + DA -- No --> C4_17((4 1, 7)) + DA -- Yes --> TD[/Transfer +digit +(FITE 1)/] + TD --> MD{More digits?} + MD -- Yes --> TD + MD -- No --> C5((5)) + C5 --> ACS([Await +call setup]) + + C4_17 --> SLC[Set loc. & +cause fields] + SLC --> CR[/Channel release/] + CR --> C4((4)) + C4 --> ACC([Await channel cleared]) + ACC --> CC[/Channel cleared/] + CC --> DC[Deassign +channel] + DC -- SP --> C0((0)) + C0 --> Idle([Idle]) + +``` + +T1142370-92/d03 + +Flowchart showing logic procedures for incoming INMARSAT aeronautical signalling. The flow starts at connector 'R 2' leading to a 'Service category?' decision. Paths branch for 'Data (FITE 19)', 'Ordinary' (leading to 'Telephone ordinary (FITE 17)'), and 'Priority' (leading to 'Telephone priority (FITE 18)'). All paths converge at a 'Digit available' decision. If 'No', it exits to connector '4 1, 7'. If 'Yes', it enters a loop: 'Transfer digit (FITE 1)' followed by 'More digits?'. If 'Yes', it loops back to 'Transfer digit'. If 'No', it goes to connector '5' which leads to the 'Await call setup' state. A separate sequence starts at connector '4 1, 7', leading to 'Set loc. & cause fields', 'Channel release', connector '4', 'Await channel cleared' state, 'Channel cleared' input, 'Deassign channel' process, and finally through 'SP' to connector '0' and the 'Idle' state. + +FIGURE 1/Q.1152 (sheet 3 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling +(air-to-ground calls)** + +![Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls) - sheet 4 of 7. The process starts at node 5 'Await call setup'. It branches into two parallel paths: 'Answer (BITE 22, 23)' and 'Address complete (BITE 5-7, 27)'. The 'Answer' path leads to 'Connect', which then leads to node 6 'L'. The 'Address complete' path leads to 'Set loc. & cause fields', which then leads to 'Call attempt result', which also leads to node 6 'L'. A connector 'F 5' is shown at the top right. Vertical lines on the left are labeled 'F' and 'L'. A reference code 'T1143170-92/d04' is at the bottom right.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + 5((5)) --> A[Await call setup] + A --> F5((F 5)) + A --> B[/Answer (BITE 22, 23)/] + A --> C[/Address complete (BITE 5-7, 27)/] + B --> D{Connect} + C --> E[Set loc. & cause fields] + E --> F[/Call attempt result/] + D --> L6((L 6)) + F --> L6 + +``` + +Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls) - sheet 4 of 7. The process starts at node 5 'Await call setup'. It branches into two parallel paths: 'Answer (BITE 22, 23)' and 'Address complete (BITE 5-7, 27)'. The 'Answer' path leads to 'Connect', which then leads to node 6 'L'. The 'Address complete' path leads to 'Set loc. & cause fields', which then leads to 'Call attempt result', which also leads to node 6 'L'. A connector 'F 5' is shown at the top right. Vertical lines on the left are labeled 'F' and 'L'. A reference code 'T1143170-92/d04' is at the bottom right. + +FIGURE 1/Q.1152 (sheet 4 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls)** + +![Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls) - sheet 5 of 7. The process starts at node 4 'F' and ends at node 7 'A'. It branches into four parallel paths: 'Call unsuccessful (BITE 8-20)', 'Channel release', 'Credit card reject', and 'BITE Z'. The 'Call unsuccessful' path leads to node 2 '1'. The 'Channel release' path leads to 'Clear forward (FITE 22)', which then leads to node 2 '1'. The 'Credit card reject' path leads to 'Clear forward (FITE 22)', which then leads to node 2 '1'. The 'BITE Z' path leads directly to node 2 '1'. Vertical lines on the left are labeled 'F, A' and '2'. A reference code 'T1143180-92/d05' is at the bottom right.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` + +graph TD + F4((F 4)) --> A7((A 7)) + F4 --> B[/Call unsuccessful (BITE 8-20)/] + F4 --> C[/Channel release/] + F4 --> D[/Credit card reject/] + F4 --> E[/BITE Z/] + B --> 2_1((2 1)) + C --> F[Clear forward (FITE 22)] + F --> 2_1 + D --> G[Clear forward (FITE 22)] + G --> 2_1 + E --> 2_1 + +``` + +Flowchart for incoming INMARSAT aeronautical signalling (air-to-ground calls) - sheet 5 of 7. The process starts at node 4 'F' and ends at node 7 'A'. It branches into four parallel paths: 'Call unsuccessful (BITE 8-20)', 'Channel release', 'Credit card reject', and 'BITE Z'. The 'Call unsuccessful' path leads to node 2 '1'. The 'Channel release' path leads to 'Clear forward (FITE 22)', which then leads to node 2 '1'. The 'Credit card reject' path leads to 'Clear forward (FITE 22)', which then leads to node 2 '1'. The 'BITE Z' path leads directly to node 2 '1'. Vertical lines on the left are labeled 'F, A' and '2'. A reference code 'T1143180-92/d05' is at the bottom right. + +FIGURE 1/Q.1152 (sheet 5 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls)** + +![Flowchart showing logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls). The flow starts at connector 'L 4', proceeds to 'Setup speech condition (SPITE 4)', then 'Deactivate register (SPITE 3)'. It then enters a 'Connected' state (labeled '6'). From this state, one path leads to connector 'U 7' and another leads to a second 'Connected' state. A feedback loop connects the second 'Connected' state back to the entry point of the first 'Connected' state. The diagram is labeled 'T1143190-92/d06' at the bottom.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +graph TD + L4((L 4)) --> SPITE4[Setup speech condition +(SPITE 4)] + SPITE4 --> SPITE3[Deactivate register +(SPITE 3)] + SPITE3 --> C6{{Connected 6}} + C6 --> U7((U 7)) + C6 --> C10{{Connected}} + C10 --> C6 + +``` + +Flowchart showing logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls). The flow starts at connector 'L 4', proceeds to 'Setup speech condition (SPITE 4)', then 'Deactivate register (SPITE 3)'. It then enters a 'Connected' state (labeled '6'). From this state, one path leads to connector 'U 7' and another leads to a second 'Connected' state. A feedback loop connects the second 'Connected' state back to the entry point of the first 'Connected' state. The diagram is labeled 'T1143190-92/d06' at the bottom. + +FIGURE 1/Q.1152 (sheet 6 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls)** + +## 4 Outgoing INMARSAT aeronautical logic procedures (ground-to-air calls) + +Figure 2 contains the procedures for the outgoing INMARSAT aeronautical signalling system. + +This description only includes the aspects of the INMARSAT aeronautical system which have to be implemented for interworking purposes. Internal procedures, such as those required for setting up and clearing satellite channels are not shown. This also applies to pre-emption procedures for assigning channels to distress calls. + +The following details should be noted: + +**4.1** The outgoing INMARSAT procedure receives the calling party indicator, and address digits from the interworking process. It determines whether the addressed AES is an authorized user and if it is logged on in the same satellite region. BITE 15 is returned to the terrestrial network if the dialled AES number is invalid. + +![Flowchart showing logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls).](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +The flowchart illustrates the logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls). It begins with a vertical timeline on the left marked 'A' at the top, '4' in the middle, and 'U' at the bottom. At the top, a circle labeled 'A' with the number '5' next to it points to a box labeled 'Release incoming side (BITE 29)'. Below this box, a circle labeled '4' with the number '3' next to it points down to a horizontal line. From this line, a circle labeled 'U' with the number '6' next to it points right into a series of five boxes: 'Clear back (BITE 25)', 'Channel release', 'Credit card reject', 'Signalling failure', and 'BITE Z'. Below the 'Credit card reject' box, the letters 'SP' are present. Below the 'Clear back (BITE 25)', 'Channel release', and 'Signalling failure' boxes, there are three boxes labeled 'Clear forward (FITE 22)'. Arrows from these three boxes point down to a horizontal line. From this line, a circle labeled '4' with the number '3' next to it points down to the bottom of the timeline. The text 'T1142380-92/d07' is located in the bottom right corner of the diagram area. + +Flowchart showing logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls). + +FIGURE 1/Q.1152 (sheet 7 of 7) +**Logic procedures for incoming INMARSAT aeronautical signalling (air-to-ground calls)** + +4.2 The MSSC attempts to assign a satellite channel to the call, and tests for continuity of the channel. National network congestion (BITE 12) signal is returned if no channel is available. Appropriate signals are returned to signify continuity failure and AES busy conditions. + +4.3 Answer signal is returned when the connect message is received from the AES. + +4.4 The call is cleared down in the usual manner, on receipt of either clear forward from the interworking process, or channel release from the AES. + +![Flowchart for logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls).](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +graph TD + Idle0([0 +Idle]) --> Activate[/Activate +outgoing +INMARSAT/] + Activate --> AwaitCPCI([1 +Await +CPCI]) + AwaitCPCI --> CPCI1719[/CPCI +(FITE 17-19)/] + AwaitCPCI --> ClearForward1[/Clear +forward +(FITE 22)/] + AwaitCPCI --> FITEZ1[/FITE Z/] + CPCI1719 --> AwaitDigits([2 +Await +digits]) + ClearForward1 --> Idle0_2([0 +Idle]) + FITEZ1 --> Idle0_2 + AwaitDigits --> Digit[/Digit +(FITE 1)/] + AwaitDigits --> ClearForward2[/Clear +forward +(FITE 22)/] + AwaitDigits --> FITEZ2[/FITE Z/] + Digit --> MoreDigits{More +digits?} + ClearForward2 --> Idle0_3([0 +Idle]) + FITEZ2 --> Idle0_3 + MoreDigits -- Yes --> AwaitDigits + MoreDigits -- No --> NumberValid{Number valid?} + NumberValid -- No --> Unalloc[/Unalloc. +number +(BITE 15)/] + NumberValid -- Yes --> FindChannel[/Find +channel/] + Unalloc --> Idle0_4([0 +Idle]) + FindChannel --> AwaitChannel([3 +Await +channel]) + +``` + +The flowchart illustrates the logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). It begins with an 'Idle' state (0), followed by an input/output action 'Activate outgoing INMARSAT', leading to state '1 Await CPCI'. From here, three paths are possible: 'CPCI (FITE 17-19)' leading to state '2 Await digits', or 'Clear forward (FITE 22)' or 'FITE Z' both leading back to an 'Idle' state (0). From '2 Await digits', three paths are possible: 'Digit (FITE 1)' leading to a 'More digits?' decision, or 'Clear forward (FITE 22)' or 'FITE Z' both leading to an 'Idle' state (0). If 'More digits?' is 'Yes', it loops back to '2 Await digits'. If 'No', it proceeds to a 'Number valid?' decision. If 'No', it goes to 'Unalloc. number (BITE 15)' and then to 'Idle' (0). If 'Yes', it goes to 'Find channel' and then to state '3 Await channel'. + +Flowchart for logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). + +T1142390-92/d08 + +NOTE – Number valid? means is the AES in the region of the calling GES; i.e. logged on the same satellite. + +FIGURE 2/Q.1152 (sheet 1 of 4) + +**Logic procedures for outgoing INMARSAT aeronautical signalling +(ground-to-air-calls)** + +![Flowchart showing logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls).](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +graph TD + Start3((3 Await channel)) --> J1(( )) + J1 --> A1{Channel assigned (SPITE 14)} + J1 --> A2{No channel} + J1 --> A3{Clear forward (FITE 22)} + J1 --> A4{FITE Z} + A1 -- SP --> S1{Setup satellite channel} + A2 -- SP --> S2{Channel unavailable (BITE 12)} + A3 --> S3{Deassign channel} + A4 --> S3 + S2 --> S3 + S3 -- SP --> Idle0((0 Idle)) + S1 --> S4((4 Await continuity)) + S4 --> Q3((Q 3)) + Q3 --> S5{Continuity OK} + S5 --> S6{Address complete (BITE 5)} + S6 --> S7((5 Await answer)) + S7 --> T4((T 4)) + T4 --> End4((4 T1143200-92/d09)) + +``` + +The flowchart illustrates the logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). It begins at state 3, 'Await channel', which leads to a decision point. From this point, four paths are possible: 'Channel assigned (SPITE 14)', 'No channel', 'Clear forward (FITE 22)', and 'FITE Z'. The 'Channel assigned' path leads to 'Setup satellite channel', which then leads to state 4, 'Await continuity'. The 'No channel' path leads to 'Channel unavailable (BITE 12)', which then leads to 'Deassign channel'. The 'Clear forward (FITE 22)' and 'FITE Z' paths both lead to 'Deassign channel'. From 'Deassign channel', the path leads to state 0, 'Idle'. From state 4, 'Await continuity', the path leads to a connector 'Q 3', which then leads to 'Continuity OK'. From 'Continuity OK', the path leads to 'Address complete (BITE 5)', which then leads to state 5, 'Await answer'. From state 5, the path leads to a connector 'T 4', which then leads to the end state 4, 'T1143200-92/d09'. + +Flowchart showing logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). + +FIGURE 2/Q.1152 (sheet 2 of 4) +**Logic procedures for outgoing INMARSAT aeronautical signalling + (ground-to-air-calls)** + +![Flowchart showing logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). The process starts at connector 'Q 2', branches through 'Clear forward (FITE 22)', 'AES busy' (leading to 'Subscriber busy (BITE 16)'), 'FITE Z', and 'Continuity failure' (leading to 'Dest. out of service (BITE 17)'). All paths converge at connector '1 4'. The subsequent steps are: 'Set loc. & cause fields', 'Channel release', 'Await channel cleared' (connector '7'), 'Channel cleared', 'Deassign channel', and finally 'Idle' (connector '0'). A 'SP' marker is present between 'Deassign channel' and 'Idle'. A vertical line on the left is labeled 'Q' at the top, '2' near the start, and '1' near the convergence point. A small '4' is near connector '1'.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +graph TD + Q2((Q 2)) --> CF[Clear forward +(FITE 22)] + Q2 --> AB[AES busy] + Q2 --> FZ[FITE Z] + Q2 --> CFail[Continuity failure] + AB --> SB{Subscriber busy +(BITE 16)} + CFail --> DOS{Dest. out of service +(BITE 17)} + CF --> J1((1 4)) + SB --> J1 + FZ --> J1 + DOS --> J1 + J1 --> SL[Set loc. & cause fields] + SL --> CR[Channel release] + CR --> AC{Await channel cleared +7} + AC --> CC[Channel cleared] + CC --> DC{Deassign channel} + DC --> SP[SP] + SP --> IDLE{Idle +0} + +``` + +Flowchart showing logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). The process starts at connector 'Q 2', branches through 'Clear forward (FITE 22)', 'AES busy' (leading to 'Subscriber busy (BITE 16)'), 'FITE Z', and 'Continuity failure' (leading to 'Dest. out of service (BITE 17)'). All paths converge at connector '1 4'. The subsequent steps are: 'Set loc. & cause fields', 'Channel release', 'Await channel cleared' (connector '7'), 'Channel cleared', 'Deassign channel', and finally 'Idle' (connector '0'). A 'SP' marker is present between 'Deassign channel' and 'Idle'. A vertical line on the left is labeled 'Q' at the top, '2' near the start, and '1' near the convergence point. A small '4' is near connector '1'. + +T1142400-92/d10 + +FIGURE 2/Q.1152 (sheet 3 of 4) +**Logic procedures for outgoing INMARSAT aeronautical signalling + (ground-to-air-calls)** + +![Flowchart of logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls).](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +The flowchart illustrates the logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). It is divided into two main sections by a horizontal line, with a vertical timeline on the left indicating time intervals T, 2, 1, and 1,2. + +**Top Section (T to 1):** + +- Starts at point **T** (circle with 'T' and subscript 2). +- Branches into five parallel paths: + - Connect** (parallelogram) → **Answer (BITE 22)** (parallelogram) → **Connected** (oval with subscript 6). + - Clear forward (FITE 22)** (parallelogram). + - FITE Z** (parallelogram). + - AES carrier off** (parallelogram) → **Clear back (BITE 25)** (parallelogram) → point **1** (circle with '1' and subscript 3). + - Channel release** (parallelogram) → point **2** (circle with '2' and subscript 4). +- Arrows from **Clear forward (FITE 22)**, **FITE Z**, and **Clear back (BITE 25)** converge at point **1** (circle with '1' and subscript 3). + +**Bottom Section (1 to 1,2):** + +- From **Connected** (oval with subscript 6), the path branches into three parallel paths: + - FITE Z** (parallelogram). + - Clear forward (FITE 22)** (parallelogram) → point **1** (circle with '1' and subscript 3). + - Channel release** (parallelogram) → point **2** (circle with '2' and subscript 4). +- An arrow from **FITE Z** points to the path between **Clear forward (FITE 22)** and **Channel release**. + +**Other elements:** + +- Point **7** (oval with subscript 7) contains the text "Await channel cleared". +- Text "T1143210-92/d11" is located near point 7. + +Flowchart of logic procedures for outgoing INMARSAT aeronautical signalling (ground-to-air-calls). + +FIGURE 2/Q.1152 (sheet 4 of 4) +**Logic procedures for outgoing INMARSAT aeronautical signalling +(ground-to-air-calls)** + +## 5 Interworking of INMARSAT aeronautical signalling system with itself + +Figure 3 contains the procedures for interworking between the incoming and outgoing procedures of the INMARSAT aeronautical system. These procedures may also apply for interworking between INMARSAT aeronautical and the Standard-A and Standard-B systems. + +The following details should be noted: + +- 5.1 The outgoing INMARSAT aeronautical logic process is activated after receipt of the calling party category information, indicating whether the call is ordinary or priority. +- 5.2 The called party address, excluding the INMARSAT country code, is transferred to the outgoing process. The process returns to idle on receipt of any unsuccessful BITE or the clear forward FITE. +- 5.3 The call is cleared as normal, on either clearforward FITE or clearback BITE signals. +- 5.4 The interworking procedure supervises the answer time (timer t1). The value of the timer is as follows: + $t1 = 2$ to $4$ minutes (as per 4.3.1/Q.118). + +![Flowchart showing the interworking of INMARSAT aeronautical system with itself. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure', state '1 Await CPCI', 'CPCI (FITE 17, 18)', 'Activate outgoing INMARSAT', 'CPCI (FITE 17, 18)', and state '2 Await address complete'. From there, it branches into four paths: 'Address complete (BITE 5)' leading to 'Start t1 (2-4 min)' and state '3 Await answer'; 'Unsuccess. (BITE 12, 16, 17, 20)' leading to state '0 idle'; 'Clear forward (FITE 22)' leading to state '2 Await address complete'; and 'Digit (FITE 1)' leading to a decision 'Country code FITE?'. If 'Yes', it goes to 'Omit country code FITE' and then to state '2 Await address complete'. If 'No', it goes to 'Digit (FITE 1)' and then to state '2 Await address complete'. The diagram is labeled T1155890-93/d12.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +graph TD + 0_Idle([0 Idle]) --> A[Activate interwork procedure] + A --> 1_AwaitCPCI([1 Await CPCI]) + 1_AwaitCPCI --> CPCI1718_1[CPCI (FITE 17, 18)] + CPCI1718_1 --> Outgoing[Activate outgoing INMARSAT] + Outgoing --> CPCI1718_2[CPCI (FITE 17, 18)] + CPCI1718_2 --> 2_AwaitAddrComplete([2 Await address complete]) + 2_AwaitAddrComplete --> AC[Address complete (BITE 5)] + 2_AwaitAddrComplete --> U[Unsuccess. (BITE 12, 16, 17, 20)] + 2_AwaitAddrComplete --> CF[Clear forward (FITE 22)] + 2_AwaitAddrComplete --> D1[Digit (FITE 1)] + AC --> AC_D{{Address complete (BITE 5)}} + U --> U_D{{Unsuccess. (BITE 12, 16, 17, 20)}} + CF --> CF_D{{Clear forward (FITE 22)}} + D1 --> CC{Country code FITE?} + CC -- Yes --> OCF[Omit country code FITE] + CC -- No --> D2[Digit (FITE 1)] + OCF --> 2_AwaitAddrComplete + D2 --> 2_AwaitAddrComplete + AC_D --> T1[Start t1 (2-4 min)] + T1 --> 3_AwaitAnswer([3 Await answer]) + U_D --> 0_Idle2([0 idle]) + CF_D --> 2_AwaitAddrComplete + +``` + +T1155890-93/d12 + +Flowchart showing the interworking of INMARSAT aeronautical system with itself. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure', state '1 Await CPCI', 'CPCI (FITE 17, 18)', 'Activate outgoing INMARSAT', 'CPCI (FITE 17, 18)', and state '2 Await address complete'. From there, it branches into four paths: 'Address complete (BITE 5)' leading to 'Start t1 (2-4 min)' and state '3 Await answer'; 'Unsuccess. (BITE 12, 16, 17, 20)' leading to state '0 idle'; 'Clear forward (FITE 22)' leading to state '2 Await address complete'; and 'Digit (FITE 1)' leading to a decision 'Country code FITE?'. If 'Yes', it goes to 'Omit country code FITE' and then to state '2 Await address complete'. If 'No', it goes to 'Digit (FITE 1)' and then to state '2 Await address complete'. The diagram is labeled T1155890-93/d12. + +FIGURE 3/Q.1152 (sheet 1 of 2) +**Interworking of INMARSAT aeronautical system with itself** + +![Flowchart showing the interworking of INMARSAT aeronautical system with itself. It starts at state '3 Await answer' and branches into four paths: 'Answer (BITE 22)', 'Clear forward (FITE 22)', 'Expiry of t1', and 'Clear back (BITE 25)'. The 'Answer' path leads to 'Stop t1' then 'Answer (BITE 22)' to state '4 Answered'. The 'Clear forward' path leads to 'Stop t1' then 'Clear forward (FITE 22)' to state '0 Idle'. The 'Expiry of t1' path leads to 'Release incoming (BITE 29)' then 'Clear forward (FITE 22)' to state '0 Idle'. The 'Clear back' path leads to 'Stop t1' then 'Clear back (BITE 25)' to state '0 Idle'. From state '4 Answered', it branches to 'Clear forward (FITE 22)' and 'Clear back (BITE 25)', which both lead to 'Clear forward (FITE 22)' and 'Clear back (BITE 25)' respectively, both ending at state '0 Idle'. A small text 'T1155900-93/d13' is present near the bottom right of the diagram.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` +graph TD + 3([3 Await answer]) --- L1[ ] + L1 --- A1>Answer BITE 22] + L1 --- CF1>Clear forward FITE 22] + L1 --- E>Expiry of t1] + L1 --- CB1>Clear back BITE 25] + A1 --> S1[Stop t1] + S1 --> A2{Answer BITE 22} + A2 --> 4([4 Answered]) + CF1 --> S2[Stop t1] + S2 --> CF2{Clear forward FITE 22} + CF2 --> 0_1([0 Idle]) + E --> RI{Release incoming BITE 29} + RI --> CF3{Clear forward FITE 22} + CF3 --> 0_2([0 Idle]) + CB1 --> S3[Stop t1] + S3 --> CB2{Clear back BITE 25} + CB2 --> 0_3([0 Idle]) + 4 --- L2[ ] + L2 --- CF4>Clear forward FITE 22] + L2 --- CB3>Clear back BITE 25] + CF4 --> CF5{Clear forward FITE 22} + CF5 --> 0_4([0 Idle]) + CB3 --> CB4{Clear back BITE 25} + CB4 --> 0_5([0 Idle]) + style L1 width:0px,height:0px + style L2 width:0px,height:0px + T1155900-93/d13 +``` + +Flowchart showing the interworking of INMARSAT aeronautical system with itself. It starts at state '3 Await answer' and branches into four paths: 'Answer (BITE 22)', 'Clear forward (FITE 22)', 'Expiry of t1', and 'Clear back (BITE 25)'. The 'Answer' path leads to 'Stop t1' then 'Answer (BITE 22)' to state '4 Answered'. The 'Clear forward' path leads to 'Stop t1' then 'Clear forward (FITE 22)' to state '0 Idle'. The 'Expiry of t1' path leads to 'Release incoming (BITE 29)' then 'Clear forward (FITE 22)' to state '0 Idle'. The 'Clear back' path leads to 'Stop t1' then 'Clear back (BITE 25)' to state '0 Idle'. From state '4 Answered', it branches to 'Clear forward (FITE 22)' and 'Clear back (BITE 25)', which both lead to 'Clear forward (FITE 22)' and 'Clear back (BITE 25)' respectively, both ending at state '0 Idle'. A small text 'T1155900-93/d13' is present near the bottom right of the diagram. + +FIGURE 3/Q.1152 (sheet 2 of 2) +**Interworking of INMARSAT aeronautical system with itself** + +## 6 Interworking of incoming INMARSAT aeronautical to Signalling System R2 + +6.1 Figure 4 contains the procedures for interworking of INMARSAT aeronautical signalling system to Signalling System R2. + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System R2. The process starts at '0 Idle', followed by 'Activate interwork procedure', then '1 Await CPCI FITE'. It branches into 'FITE 17' and 'FITE 18', then 'Activate outgoing R2'. A decision 'Which CPCI FITE?' leads to 'FITE 16' (path 17) or 'FITE 18' (path 18). Both lead to 'SPITE 22?'. If 'Yes', it goes to 'SPITE 21?'. If 'No', it goes to 'FITE 22'. From 'FITE 22', it goes to 'SPITE 21?'. If 'Yes', it goes to 'FITE 7'. If 'No', it goes to 'FITE 4' or 'FITE 5'. All paths (FITE 7, FITE 8, FITE 4, FITE 5) lead to '2 Await address complete'. A small code 'T1155910-93/d14' is present near the end.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +graph TD + 0((0 Idle)) --> A[/Activate interwork procedure/] + A --> 1((1 Await CPCI FITE)) + 1 --> F17[/FITE 17/] + 1 --> F18[/FITE 18/] + F17 --> B[/Activate outgoing R2/] + F18 --> B + B --> C{Which CPCI FITE?} + C -- 17 --> F16[/FITE 16/] + C -- 18 --> F18b[/FITE 18/] + F16 --> D{SPITE 22?} + F18b --> D + D -- Yes --> E{SPITE 21?} + D -- No --> F22[/FITE 22/] + F22 --> G{SPITE 21?} + G -- Yes --> F7[/FITE 7/] + G -- No --> F4[/FITE 4/] + G -- No --> F5[/FITE 5/] + E -- Yes --> F8[/FITE 8/] + E -- No --> F7 + F4 --> 2((2 Await address complete)) + F5 --> 2 + F7 --> 2 + F8 --> 2 + T1155910-93/d14 + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System R2. The process starts at '0 Idle', followed by 'Activate interwork procedure', then '1 Await CPCI FITE'. It branches into 'FITE 17' and 'FITE 18', then 'Activate outgoing R2'. A decision 'Which CPCI FITE?' leads to 'FITE 16' (path 17) or 'FITE 18' (path 18). Both lead to 'SPITE 22?'. If 'Yes', it goes to 'SPITE 21?'. If 'No', it goes to 'FITE 22'. From 'FITE 22', it goes to 'SPITE 21?'. If 'Yes', it goes to 'FITE 7'. If 'No', it goes to 'FITE 4' or 'FITE 5'. All paths (FITE 7, FITE 8, FITE 4, FITE 5) lead to '2 Await address complete'. A small code 'T1155910-93/d14' is present near the end. + +FIGURE 4/Q.1152 (sheet 1 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System R2** + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System R2. The process starts with 'Await address complete' (2), leading to a sequence of messages: FITE 1, BITE 5, 6, BITE 2, BITE 11-13, 15-17, 20, and FITE 22. A decision 'Country code FITE?' follows. If 'Yes', it leads to 'Start t1 (2-4 min)' and then 'Await answer' (3). If 'No', it leads to 'SPITE 22?'. If 'SPITE 22?' is 'Yes', it leads to 'FITE 1' and back to 'Await address complete' (2). If 'SPITE 22?' is 'No', it leads to 'Omit country code FITE', then 'FITE 1', and back to 'Await address complete' (2). From 'Await answer' (3), the sequence continues with BITE 21, 'Expiry of t1', and FITE 22. 'Expiry of t1' leads to 'BITE 29' and 'Stop t1', which then leads to 'Answered' (4). 'Answered' (4) leads to 'FITE 22' and 'BITE 25'. 'BITE 25' leads to 'Start t2' and then 'Clear back' (5). 'FITE 22' from 'Answered' leads to 'FITE 22' and then 'Idle' (0). 'Start t2' also leads to 'Idle' (0). 'BITE 11-13, 15-17, 20' from the initial sequence leads to 'Idle' (0).](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +graph TD + Start([2 Await address complete]) --> FITE1_1[FITE 1] + Start --> BITE56[BITE 5, 6] + Start --> BITE2[BITE 2] + Start --> BITE1113151720[BITE 11-13, 15-17, 20] + Start --> FITE22_1[FITE 22] + BITE56 --> BITE5[BITE 5] + BITE2 --> BITE27[BITE 27] + BITE1113151720 --> BITE1113151720_2[BITE 11-13, 15-17, 20] + FITE22_1 --> FITE22_2[FITE 22] + BITE5 --> CountryCode{Country code FITE?} + BITE27 --> StartT1[Start t1 +(2-4 min)] + BITE1113151720_2 --> Idle_1([0 Idle]) + FITE22_2 --> FITE22_3[FITE 22] + CountryCode -- Yes --> StartT1 + CountryCode -- No --> SPITE22{SPITE 22?} + SPITE22 -- Yes --> FITE1_2[FITE 1] + SPITE22 -- No --> OmitCountryCode[Omit country code FITE] + FITE1_2 --> Start([2 Await address complete]) + OmitCountryCode --> FITE1_3[FITE 1] + FITE1_3 --> Start([2 Await address complete]) + StartT1 --> AwaitAnswer([3 Await answer]) + AwaitAnswer --> BITE21[BITE 21] + AwaitAnswer --> ExpiryT1[Expiry of t1] + AwaitAnswer --> FITE22_4[FITE 22] + BITE21 --> BITE22[BITE 22] + ExpiryT1 --> BITE29[BITE 29] + ExpiryT1 --> StopT1_1[Stop t1] + FITE22_4 --> FITE22_5[FITE 22] + BITE22 --> StopT1_2[Stop t1] + BITE29 --> Answered([4 Answered]) + StopT1_1 --> FITE22_6[FITE 22] + StopT1_1 --> Idle_2([0 Idle]) + StopT1_2 --> Answered + Answered --> FITE22_7[FITE 22] + Answered --> BITE25[BITE 25] + FITE22_7 --> FITE22_8[FITE 22] + FITE22_8 --> Idle_3([0 Idle]) + BITE25 --> StartT2[Start t2] + StartT2 --> ClearBack([5 Clear back]) + StartT2 --> Idle_4([0 Idle]) + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System R2. The process starts with 'Await address complete' (2), leading to a sequence of messages: FITE 1, BITE 5, 6, BITE 2, BITE 11-13, 15-17, 20, and FITE 22. A decision 'Country code FITE?' follows. If 'Yes', it leads to 'Start t1 (2-4 min)' and then 'Await answer' (3). If 'No', it leads to 'SPITE 22?'. If 'SPITE 22?' is 'Yes', it leads to 'FITE 1' and back to 'Await address complete' (2). If 'SPITE 22?' is 'No', it leads to 'Omit country code FITE', then 'FITE 1', and back to 'Await address complete' (2). From 'Await answer' (3), the sequence continues with BITE 21, 'Expiry of t1', and FITE 22. 'Expiry of t1' leads to 'BITE 29' and 'Stop t1', which then leads to 'Answered' (4). 'Answered' (4) leads to 'FITE 22' and 'BITE 25'. 'BITE 25' leads to 'Start t2' and then 'Clear back' (5). 'FITE 22' from 'Answered' leads to 'FITE 22' and then 'Idle' (0). 'Start t2' also leads to 'Idle' (0). 'BITE 11-13, 15-17, 20' from the initial sequence leads to 'Idle' (0). + +T1155920-93/d15 + +FIGURE 4/Q.1152 (sheet 2 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System R2** + +![Flowchart illustrating the interworking of INMARSAT aeronautical system to Signalling System R2. The process starts at state 5 (Clear back), which branches into three parallel paths: BITE 21, FITE 22, and Expiry of t2. BITE 21 leads to Stop t2, which then leads to state 4 (Answered). FITE 22 leads to Stop t2, which then leads to FITE 22, which then leads to state 0 (Idle). Expiry of t2 leads to BITE 25, which then leads to FITE 22, which then leads to state 0 (Idle).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +graph TD + 5((5 Clear back)) --> BITE21[BITE 21] + 5 --> FITE22_1[FITE 22] + 5 --> Expiry[Expiry of t2] + BITE21 --> StopT2_1[Stop t2] + FITE22_1 --> StopT2_2[Stop t2] + Expiry --> BITE25[BITE 25] + StopT2_1 --> 4((4 Answered)) + StopT2_2 --> FITE22_2[FITE 22] + BITE25 --> FITE22_2 + FITE22_2 --> 0((0 Idle)) + +``` + +T1155930-93/d 16 + +Flowchart illustrating the interworking of INMARSAT aeronautical system to Signalling System R2. The process starts at state 5 (Clear back), which branches into three parallel paths: BITE 21, FITE 22, and Expiry of t2. BITE 21 leads to Stop t2, which then leads to state 4 (Answered). FITE 22 leads to Stop t2, which then leads to FITE 22, which then leads to state 0 (Idle). Expiry of t2 leads to BITE 25, which then leads to FITE 22, which then leads to state 0 (Idle). + +FIGURE 4/Q.1152 (sheet 3 of 3) +**Interworking of INMARSAT aeronautical system + to Signalling System R2** + +6.2 The interworking procedure supervises the answer time and the clearback time, with timers t1 and t2 respectively. The values of the timers are as follows: + +t1 = 2 to 4 minutes (as per 4.3.1/Q.118) + +t2 = 1 to 2 minutes (as per 4.3.2/Q.118). + +## 7 Interworking of Signalling System R2 to outgoing INMARSAT aeronautical + +7.1 Figure 5 contains the procedures for interworking of Signalling System R2 to INMARSAT aeronautical signalling system. + +7.2 The ringing tone towards the calling subscriber of the fixed network is initiated by the interworking procedure. The tone should have characteristics in accordance with Recommendation Q.35. + +![Flowchart showing the interworking of Signalling System R2 to INMARSAT aeronautical system. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure' and 'Activate outgoing INMARSAT' to state '1 Await CPCI FITE'. It then branches through FITE 14, 16, 18, and 22, followed by FITE 17, 17, 18, and 22 respectively, leading to state '2 Await digits'. From there, it branches through FITE 1 and FITE 22. FITE 1 leads to a decision 'Country code FITE?'. If 'Yes', it goes to state '3 Await address complete'. If 'No', it goes through FITE 1 to another decision 'Last digit?'. If 'Yes', it goes to state '3 Await address complete'. If 'No', it goes to state '2 Await digits'. FITE 22 leads to another FITE 22 block, which then leads to state '0 Idle'. A reference 'T1 155940-93/d17' is noted near the bottom right.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +graph TD + Idle0_1((0 Idle)) --> A[Activate interwork procedure] + A --> B[Activate outgoing INMARSAT] + B --> AwaitCPCI((1 Await CPCI FITE)) + AwaitCPCI --> FITE14[/FITE 14/] + AwaitCPCI --> FITE16[/FITE 16/] + AwaitCPCI --> FITE18_1[/FITE 18/] + AwaitCPCI --> FITE22_1[/FITE 22/] + FITE14 --> FITE17_1[/FITE 17/] + FITE16 --> FITE17_2[/FITE 17/] + FITE18_1 --> FITE18_2[/FITE 18/] + FITE22_1 --> FITE22_2[/FITE 22/] + FITE17_1 --> AwaitDigits2((2 Await digits)) + FITE17_2 --> AwaitDigits2 + FITE18_2 --> AwaitDigits2 + FITE22_2 --> Idle0_2((0 Idle)) + AwaitDigits2 --> FITE1_1[/FITE 1/] + AwaitDigits2 --> FITE22_3[/FITE 22/] + FITE1_1 --> CountryCode{Country code FITE?} + CountryCode -- Yes --> AwaitAddress((3 Await address complete)) + CountryCode -- No --> FITE1_2[/FITE 1/] + FITE1_2 --> LastDigit{Last digit?} + LastDigit -- Yes --> AwaitAddress + LastDigit -- No --> AwaitDigits2 + FITE22_3 --> FITE22_4[/FITE 22/] + FITE22_4 --> Idle0_3((0 Idle)) + T1_155940_93_d17[T1 155940-93/d17] + +``` + +Flowchart showing the interworking of Signalling System R2 to INMARSAT aeronautical system. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure' and 'Activate outgoing INMARSAT' to state '1 Await CPCI FITE'. It then branches through FITE 14, 16, 18, and 22, followed by FITE 17, 17, 18, and 22 respectively, leading to state '2 Await digits'. From there, it branches through FITE 1 and FITE 22. FITE 1 leads to a decision 'Country code FITE?'. If 'Yes', it goes to state '3 Await address complete'. If 'No', it goes through FITE 1 to another decision 'Last digit?'. If 'Yes', it goes to state '3 Await address complete'. If 'No', it goes to state '2 Await digits'. FITE 22 leads to another FITE 22 block, which then leads to state '0 Idle'. A reference 'T1 155940-93/d17' is noted near the bottom right. + +FIGURE 5/Q.1152 (sheet 1 of 2) +**Interworking of Signalling System R2 to INMARSAT aeronautical system** + +![Flowchart showing the interworking of Signalling System R2 to INMARSAT aeronautical system. The process starts at state 3 (Await address complete) and branches into two paths. The left path involves BITE 12, 15-17, 20 and FITE 22 leading to state 0 (Idle). The right path involves BITE 5, SPITE 6 (Ring tone), state 4 (Await answer), BITE 22, FITE 22, BITE 21, FITE 22, SPITE 7 (Ring tone), state 5 (Answered), BITE 25, FITE 22, BITE 25, FITE 22, and finally state 0 (Idle). A reference code T1155950-93/d18 is present near the end of the right path.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +graph TD + S3((3 Await address complete)) --> B12_15_17_20_1[BITE 12, 15-17, 20] + S3 --> F22_1[FITE 22] + S3 --> B5_1[BITE 5] + B12_15_17_20_1 --> B12_15_17_20_2{BITE 12, 15-17, 20} + F22_1 --> F22_2{FITE 22} + B5_1 --> B5_2{BITE 5} + B12_15_17_20_2 --> S0_1((0 Idle)) + F22_2 --> S0_1 + B5_2 --> SPITE6[SPITE 6 Ring tone] + SPITE6 --> S4((4 Await answer)) + S4 --> B22_1[BITE 22] + S4 --> F22_3[FITE 22] + B22_1 --> B21{BITE 21} + F22_3 --> F22_4{FITE 22} + B21 --> SPITE7[SPITE 7 Ring tone] + F22_4 --> S0_2((0 Idle)) + SPITE7 --> S5((5 Answered)) + S5 --> B25_1[BITE 25] + S5 --> F22_5[FITE 22] + B25_1 --> B25_2{BITE 25} + F22_5 --> F22_6{FITE 22} + B25_2 --> S0_3((0 Idle)) + F22_6 --> S0_3 + T1155950-93/d18 + +``` + +Flowchart showing the interworking of Signalling System R2 to INMARSAT aeronautical system. The process starts at state 3 (Await address complete) and branches into two paths. The left path involves BITE 12, 15-17, 20 and FITE 22 leading to state 0 (Idle). The right path involves BITE 5, SPITE 6 (Ring tone), state 4 (Await answer), BITE 22, FITE 22, BITE 21, FITE 22, SPITE 7 (Ring tone), state 5 (Answered), BITE 25, FITE 22, BITE 25, FITE 22, and finally state 0 (Idle). A reference code T1155950-93/d18 is present near the end of the right path. + +FIGURE 5/Q.1152 (sheet 2 of 2) +**Interworking of Signalling System R2 to INMARSAT aeronautical system** + +## **8 Interworking of incoming INMARSAT aeronautical to Signalling System No. 7 (TUP)** + +Figure 6 contains the procedures for interworking of INMARSAT aeronautical signalling system to Signalling System No. 7 (TUP). + +The following details should be noted: + +**8.1** The outgoing Signalling System No. 7 (TUP) is activated only after receipt of calling party category information. + +**8.2** Signals to inform whether continuity checking is required on the terrestrial link, whether an incoming half-echo suppressor should be inserted, and whether country code digits will be sent along with the called party address, are sent to the ISC. The ISC is also informed that continuity has been proven on the satellite link. + +**8.3** All address-complete backward signals are transferred through to the outgoing aeronautical procedure. The charge related information is interpreted and used by the MSSC for billing purposes, and a simple address complete message is sent to the AES. + +**8.4** All unsuccessful call indications received from the ISC are relayed to the INMARSAT system, by means of the call attempt result message with the cause value set appropriately. + +**8.5** Charge information contained in the answer message is again used by the MSSC for billing purposes. + +**8.6** Answer and clearback supervision is done by the MSSC with timers t1 and t2 respectively. The values of the timers are as follows: + +t1 = 2 to 4 minutes (as per 4.3.1/Q.118) + +t2 = 1 to 2 minutes (as per 4.3.2/Q.118). + +## **9 Interworking of Signalling System No. 7 (TUP) to outgoing INMARSAT aeronautical** + +Figure 7 contains the procedures for interworking of Signalling System No. 7 (TUP) to INMARSAT aeronautical signalling system. + +The following details should be noted: + +**9.1** Calling party category information indicating the nature and priority of the call, is transferred through to the aeronautical system. The operator language indicator is interpreted and used by the MSSC. + +**9.2** The entire called party address, except the country code digits, are transferred through to the aeronautical system. The outgoing aeronautical logic process determines the validity of the addressed AES, and returns an unsuccessful call indication if necessary. + +**9.3** The call may also be aborted if: + +- no satellite voice channels are available; +- the addressed AES subscriber is busy; +- the continuity check is unsuccessful. + +**9.4** The MSSC returns audible ring tone, as per provisions in Recommendation Q.35, to the terrestrial network. The tone is applied on receipt of the address complete message from the AES, and removed upon receipt of the connect message. + +Connector reference + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP. The flow starts at state '0 Idle', proceeds through 'Activate interwork procedure', 'Await CPCI FITE', 'FITE 17, 18', 'Activate outgoing No. 7 TUP', 'FITE 17, 18', then a decision 'SPITE 36?'. If 'Yes', it goes to 'FITE 26'; if 'No', it goes to 'FITE 25'. Both lead to 'FITE 24' then 'FITE 21', ending at connector '1'. A second connector '1' leads to decision 'SPITE 22?'. If 'Transit', it goes to 'FITE 3'; if 'Terminal', it goes to 'FITE 2'. Both lead to decision 'SPITE 21?'. If 'Req.', it goes to 'FITE 5'; if 'Not req.', it goes to 'FITE 4'. Both lead to state '2 Await address complete'.](399a5af4f606059626c92c92279d54b7_img.jpg) + +``` +graph TD; subgraph Sheet1 [Sheet 1]; 0_0((0 Idle)); 0_0 --> 0_1[/Activate interwork procedure/]; 0_1 --> 0_2((1 Await CPCI FITE)); 0_2 --> 0_3[/FITE 17, 18/]; 0_3 --> 0_4[/Activate outgoing No. 7 TUP/]; 0_4 --> 0_5[/FITE 17, 18/]; 0_5 --> 0_6{SPITE 36?}; 0_6 -- Yes --> 0_7[/FITE 26/]; 0_6 -- No --> 0_8[/FITE 25/]; 0_7 --> 0_9[/FITE 24/]; 0_8 --> 0_9; 0_9 --> 0_10[/FITE 21/]; 0_10 --> 0_11((1)); end; subgraph Sheet2 [Sheet 2]; 1_0((1)); 1_0 --> 1_1{SPITE 22?}; 1_1 -- Transit --> 1_2[/FITE 3/]; 1_1 -- Terminal --> 1_3[/FITE 2/]; 1_2 --> 1_4{SPITE 21?}; 1_3 --> 1_4; 1_4 -- Req. --> 1_5[/FITE 5/]; 1_4 -- Not req. --> 1_6[/FITE 4/]; 1_5 --> 1_7((2 Await address complete)); 1_6 --> 1_7; end; 0_11 -- Connector reference --> 1_0; +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP. The flow starts at state '0 Idle', proceeds through 'Activate interwork procedure', 'Await CPCI FITE', 'FITE 17, 18', 'Activate outgoing No. 7 TUP', 'FITE 17, 18', then a decision 'SPITE 36?'. If 'Yes', it goes to 'FITE 26'; if 'No', it goes to 'FITE 25'. Both lead to 'FITE 24' then 'FITE 21', ending at connector '1'. A second connector '1' leads to decision 'SPITE 22?'. If 'Transit', it goes to 'FITE 3'; if 'Terminal', it goes to 'FITE 2'. Both lead to decision 'SPITE 21?'. If 'Req.', it goes to 'FITE 5'; if 'Not req.', it goes to 'FITE 4'. Both lead to state '2 Await address complete'. + +T1155960-93/d19 + +FIGURE 6/Q.1152 (sheet 1 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP** + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP. The process starts with 'Await address complete' (2) leading to connector 'A'. From 'A', it branches into four parallel paths: 1) FITE 1 -> Country code FITE? (Yes leads to SPITE 22?, No leads to FITE 1) -> SPITE 22? (Transit leads to FITE 1, Terminal leads to Omit country code FITE) -> FITE 1 -> Await address complete (2). 2) BITE 2, 3, 4 -> BITE 27 -> Start t1 (2-4 min) -> Await answer (3). 3) BITE 5-7 -> BITE 5-7. 4) BITE 31 -> SPITE 48 -> FITE 31 -> Await address complete (2). All four paths converge to connector 'A'. From 'A', the flow goes to BITE 9, 10, 12, 14-17, 19, 20, 35, 36 -> FITE 22 -> BITE 9, 10, 12, 14-17, 19, 20, 35, 36 -> FITE 22 -> Idle (0).](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +Connector reference + +``` + +graph TD + Start([2 Await address complete]) --> A((A)) + A --> FITE1_1{{FITE 1}} + A --> BITE234{{BITE 2, 3, 4}} + A --> BITE57_1{{BITE 5-7}} + A --> BITE31{{BITE 31}} + FITE1_1 --> CC{Country code FITE?} + CC -- Yes --> SPITE22{SPITE 22?} + CC -- No --> FITE1_2{{FITE 1}} + SPITE22 -- Transit --> FITE1_2 + SPITE22 -- Terminal --> Omit[Omit country code FITE] + Omit --> FITE1_2 + FITE1_2 --> Start2([2 Await address complete]) + BITE234 --> BITE27{{BITE 27}} + BITE27 --> StartT1{{Start t1 (2-4 min)}} + StartT1 --> Start3([3 Await answer]) + BITE57_1 --> BITE57_2{{BITE 5-7}} + BITE31 --> SPITE48{{SPITE 48}} + SPITE48 --> FITE31{{FITE 31}} + FITE31 --> Start4([2 Await address complete]) + Start2 --> A + Start3 --> A + BITE57_2 --> A + Start4 --> A + A --> BITE910[{{BITE 9, 10, 12, 14-17, 19, 20, 35, 36}}] + BITE910 --> FITE22_1{{FITE 22}} + FITE22_1 --> BITE910_2[{{BITE 9, 10, 12, 14-17, 19, 20, 35, 36}}] + BITE910_2 --> FITE22_2{{FITE 22}} + FITE22_2 --> Idle([0 Idle]) + T1155970-93/d20 + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP. The process starts with 'Await address complete' (2) leading to connector 'A'. From 'A', it branches into four parallel paths: 1) FITE 1 -> Country code FITE? (Yes leads to SPITE 22?, No leads to FITE 1) -> SPITE 22? (Transit leads to FITE 1, Terminal leads to Omit country code FITE) -> FITE 1 -> Await address complete (2). 2) BITE 2, 3, 4 -> BITE 27 -> Start t1 (2-4 min) -> Await answer (3). 3) BITE 5-7 -> BITE 5-7. 4) BITE 31 -> SPITE 48 -> FITE 31 -> Await address complete (2). All four paths converge to connector 'A'. From 'A', the flow goes to BITE 9, 10, 12, 14-17, 19, 20, 35, 36 -> FITE 22 -> BITE 9, 10, 12, 14-17, 19, 20, 35, 36 -> FITE 22 -> Idle (0). + +FIGURE 6/Q.1152 (sheet 2 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP** + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP. The diagram starts at state '3 Await answer' and branches based on events: BITE 22, 23; Expiry of t1; FITE 22; and BITE 10, 12, 19. It includes intermediate states like '4 Answered', '5 Clear back', and '0 Idle', and transitions like 'Stop t1', 'Start t2 (1-2 min)', and 'Stop t2'.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 3 : Await answer + 3 --> BITE_22_23 : BITE 22, 23 + 3 --> Expiry_of_t1 : Expiry of t1 + 3 --> FITE_22 : FITE 22 + 3 --> BITE_10_12_19 : BITE 10, 12, 19 + BITE_22_23 --> BITE_22 : BITE 22 + Expiry_of_t1 --> BITE_29 : BITE 29 + FITE_22 --> Stop_t1 : Stop t1 + BITE_10_12_19 --> BITE_29 : BITE 29 + BITE_22 --> Stop_t1 : Stop t1 + Stop_t1 --> 4 : Answered + BITE_29 --> FITE_22 : FITE 22 + FITE_22 --> 0 : Idle + 4 --> BITE_25 : BITE 25 + 4 --> FITE_22 : FITE 22 + BITE_25 --> Start_t2 : Start t2 (1-2 min) + FITE_22 --> FITE_22 : FITE 22 + Start_t2 --> 5 : Clear back + FITE_22 --> 0 : Idle + 5 --> FITE_22 : FITE 22 + 5 --> Expiry_of_t2 : Expiry of t2 + 5 --> BITE_24 : BITE 24 + FITE_22 --> Stop_t2 : Stop t2 + Expiry_of_t2 --> BITE_25 : BITE 25 + BITE_24 --> Stop_t2 : Stop t2 + Stop_t2 --> 4 : Answered + BITE_25 --> FITE_22 : FITE 22 + FITE_22 --> 0 : Idle + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP. The diagram starts at state '3 Await answer' and branches based on events: BITE 22, 23; Expiry of t1; FITE 22; and BITE 10, 12, 19. It includes intermediate states like '4 Answered', '5 Clear back', and '0 Idle', and transitions like 'Stop t1', 'Start t2 (1-2 min)', and 'Stop t2'. + +T1155980-93/d21 + +FIGURE 6/Q.1152 (sheet 3 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System No. 7 TUP** + +![Flowchart showing the interworking of Signalling System No. 7 TUP to INMARSAT aeronautical system. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure' to state '1 Await CPCI FITE'. From there, it branches into three paths: 'FITE 17, 18' leading to 'Activate outgoing INMARSAT' then 'FITE 17, 18'; 'FITE 22' leading to state '0 Idle'; and 'FITE 30' leading to state '1 Await CPCI FITE'. All three paths converge to state '2 Await continuity'. From '2 Await continuity', it branches into 'FITE 1', 'FITE 25', 'FITE 24', and 'FITE 22'. 'FITE 1', 'FITE 25', and 'FITE 24' lead to a decision 'Any FITE 1 stored?'. If 'No', it goes to state '3 Await address complete'. If 'Yes', it goes to a decision 'Country code FITE?'. If 'Yes', it goes to 'Omit country code FITE' then to 'FITE 1' leading to connector '2' (reference 1). If 'No', it goes to 'FITE 1' leading to connector '2' (reference 1). 'FITE 22' leads to 'FITE 22' then to state '0 Idle'. A separate loop starts at connector '2', goes to decision 'Last digit?'. If 'No', it goes to connector '3' (reference 1). If 'Yes', it goes to state '3 Await address complete'. A small diagram on the right shows connector '3' leading to state '3 Await address complete'. A text label 'T1155990-93/d22' is at the bottom right.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +Connector reference + +``` + +graph TD + Idle0_1([0 Idle]) --> ActInt[Activate interwork procedure] + ActInt --> AwaitCPCI1([1 Await CPCI FITE]) + AwaitCPCI1 --> FITE1718_1[/FITE 17, 18/] + AwaitCPCI1 --> FITE22_1[/FITE 22/] + AwaitCPCI1 --> FITE30[/FITE 30/] + FITE1718_1 --> ActOut[Activate outgoing INMARSAT] + ActOut --> FITE1718_2[/FITE 17, 18/] + FITE22_1 --> Idle0_2([0 Idle]) + FITE30 --> AwaitCPCI2([1 Await CPCI FITE]) + FITE1718_2 --> AwaitCont([2 Await continuity]) + FITE22_1 --> FITE22_2[/FITE 22/] + FITE30 --> AwaitCont + AwaitCont --> FITE1[/FITE 1/] + AwaitCont --> FITE25[/FITE 25/] + AwaitCont --> FITE24[/FITE 24/] + AwaitCont --> FITE22_3[/FITE 22/] + FITE1 --> AnyFITE1{Any FITE 1 stored?} + FITE25 --> AnyFITE1 + FITE24 --> AnyFITE1 + FITE22_3 --> FITE22_4[/FITE 22/] + FITE22_4 --> Idle0_3([0 Idle]) + AnyFITE1 -- No --> AwaitAddrComp3([3 Await address complete]) + AnyFITE1 -- Yes --> CountryCode{Country code FITE?} + CountryCode -- Yes --> Omit[Omit country code FITE] + Omit --> FITE1_2[/FITE 1/] + CountryCode -- No --> FITE1_2 + FITE1_2 --> Connector2_1((2 1)) + Connector2_1 --> Idle0_1 + Connector2_2((2)) --> LastDigit{Last digit?} + LastDigit -- No --> Connector3_1((3 1)) + LastDigit -- Yes --> AwaitAddrComp2([3 Await address complete]) + Connector3_2((3)) --> AwaitAddrComp3 + T115599093d22[T1155990-93/d22] + +``` + +Flowchart showing the interworking of Signalling System No. 7 TUP to INMARSAT aeronautical system. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure' to state '1 Await CPCI FITE'. From there, it branches into three paths: 'FITE 17, 18' leading to 'Activate outgoing INMARSAT' then 'FITE 17, 18'; 'FITE 22' leading to state '0 Idle'; and 'FITE 30' leading to state '1 Await CPCI FITE'. All three paths converge to state '2 Await continuity'. From '2 Await continuity', it branches into 'FITE 1', 'FITE 25', 'FITE 24', and 'FITE 22'. 'FITE 1', 'FITE 25', and 'FITE 24' lead to a decision 'Any FITE 1 stored?'. If 'No', it goes to state '3 Await address complete'. If 'Yes', it goes to a decision 'Country code FITE?'. If 'Yes', it goes to 'Omit country code FITE' then to 'FITE 1' leading to connector '2' (reference 1). If 'No', it goes to 'FITE 1' leading to connector '2' (reference 1). 'FITE 22' leads to 'FITE 22' then to state '0 Idle'. A separate loop starts at connector '2', goes to decision 'Last digit?'. If 'No', it goes to connector '3' (reference 1). If 'Yes', it goes to state '3 Await address complete'. A small diagram on the right shows connector '3' leading to state '3 Await address complete'. A text label 'T1155990-93/d22' is at the bottom right. + +FIGURE 7/Q.1152 (sheet 1 of 2) +**Interworking of Signalling System No. 7 TUP to INMARSAT aeronautical system** + +Connector reference + +![State transition diagram for the interworking of Signalling System No. 7 TUP to INMARSAT aeronautical system. The diagram shows three main call flow paths starting from 'Await address complete' (3). Path 1 (BITE 5) leads to 'SPITE 6 Ring tone' -> 'Await answer' (4) -> 'SPITE 7 Ring tone' -> 'Answered' (5) -> 'Idle' (0). Path 2 (BITE 12, 15-17, 20) leads to 'Idle' (0). Path 3 (FITE 31) leads to 'Await address complete' (3). Connector reference 1 is shown on the left side of the diagram.](7f5df81190b8dc50dad2604562ae0715_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S3_1: 3 Await address complete + S3_1 --> BITE5: BITE 5 + BITE5 --> BITE5_in: BITE 5 + BITE5_in --> SPITE6: SPITE 6 Ring tone + SPITE6 --> S4: 4 Await answer + S4 --> BITE22_1: BITE 22 + BITE22_1 --> BITE22_in: BITE 22 + BITE22_in --> SPITE7: SPITE 7 Ring tone + SPITE7 --> S5: 5 Answered + S5 --> BITE25: BITE 25 + BITE25 --> BITE25_in: BITE 25 + BITE25_in --> Idle_0_1: 0 Idle + + S3_1 --> FITE1: FITE 1 + FITE1 --> S1: 1 + + S3_1 --> BITE12: BITE 12, 15-17, 20 + BITE12 --> BITE12_in: BITE 12, 15-17, 20 + BITE12_in --> Idle_0_2: 0 Idle + + S3_1 --> FITE22_1: FITE 22 + FITE22_1 --> FITE22_in: FITE 22 + FITE22_in --> Idle_0_2 + + S3_1 --> FITE31: FITE 31 + FITE31 --> S3_2: 3 Await address complete + S3_2 --> T1156000-93/d23: T1156000-93/d23 + +``` + +State transition diagram for the interworking of Signalling System No. 7 TUP to INMARSAT aeronautical system. The diagram shows three main call flow paths starting from 'Await address complete' (3). Path 1 (BITE 5) leads to 'SPITE 6 Ring tone' -> 'Await answer' (4) -> 'SPITE 7 Ring tone' -> 'Answered' (5) -> 'Idle' (0). Path 2 (BITE 12, 15-17, 20) leads to 'Idle' (0). Path 3 (FITE 31) leads to 'Await address complete' (3). Connector reference 1 is shown on the left side of the diagram. + +FIGURE 7/Q.1152 (sheet 2 of 2) + +### Interworking of Signalling System No. 7 TUP to INMARSAT aeronautical system + +## 10 Interworking of incoming INMARSAT aeronautical to Signalling System No. 5 + +Figure 8 contains the procedures for interworking of INMARSAT aeronautical signalling system to Signalling System No. 5. + +**10.1** The outgoing Signalling System No. 5 procedure is activated after receipt of the calling party category information, in the access request message from the AES. + +**10.2** Either KP2 or KP1 signal is sent by the MSSC, depending on whether the country code is to be outpulsed or not, respectively. + +**10.3** The artificial “send-finished” signal, received from the outgoing Signalling System No. 5 procedure, is interpreted as an address complete condition to convey back to the AES. + +**10.4** The “busy-flash” signal (unsuccessful call) received from the terrestrial network is transferred to the AES by means of the call attempt result message. + +**10.5** Answer and clearback timeout supervision is done by the MSSC, with timers t1 and t2, respectively. The values of the timers are as follows: + +t1 = 2 to 4 minutes (as per 4.3.1/Q.118) + +t2 = 1 to 2 minutes (as per 4.3.2/Q.118). + +## 11 Interworking of Signalling System No. 5 to outgoing INMARSAT aeronautical + +Figure 9 contains the procedures for interworking of Signalling System No. 5 INMARSAT aeronautical signalling system. + +The following details should be noted: + +**11.1** The KP2 or KP1 signal is received from the MSSC, depending on whether the country code is to be expected along with the called party address or not, respectively. + +**11.2** The “busy-flash” signal is sent to the ISC if the call cannot be completed for any of the following reasons: + +- called AES subscriber is busy; +- no satellite channel is available; +- the continuity check is unsuccessful. + +The special information tone is sent back to the ISC, if the call is unsuccessful for any other reasons. + +**11.3** Answer and clearback signals received from the AES are conveyed through to the terrestrial network as soon as they are received, and there is no timeout supervision required. + +*Addendum* – A recent change in the INMARSAT signalling system definition allows cause information to be carried in the channel release signal, thereby making it unnecessary to send the call attempt result signal for unsuccessful calls. The interworking procedures in this Recommendation do not reflect this change. + +**12** Figure 10 contains the procedures for the interworking of Signalling System No. 7 (ISUP) to the INMARSAT aeronautical signalling system. + +**13** Figures 11, 12 and 13 contain the procedures for the interworking of INMARSAT aeronautical signalling system to Signalling System No. 7. + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 5. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure', 'Await CPCI FITE', and various FITE and BITE messages. It includes decision points for 'SPITE 22?' and 'Country code FITE?'. The flow ends at state '0 Idle' via connector '1'.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +Connector reference + +``` + +graph TD + 0_Idle([0 Idle]) --> Act_Interwork[Activate interwork procedure] + Act_Interwork --> 1_Await_CPCI([1 Await CPCI FITE]) + 1_Await_CPCI --> FITE_17_18[FITE 17 | FITE 18] + FITE_17_18 --> Act_Outgoing[Activate outgoing No. 5] + Act_Outgoing --> FITE_17[FITE 17] + FITE_17 --> SPITE_22_1{SPITE 22?} + SPITE_22_1 -- No --> FITE_2[FITE 2] + SPITE_22_1 -- Yes --> FITE_3[FITE 3] + FITE_2 --> 2_Await_Address_1([2 Await address complete]) + FITE_3 --> 2_Await_Address_1 + 2_Await_Address_1 --> FITE_1_BITE_27_BITE_8_FITE_22_1[FITE 1 | BITE 27 | BITE 8 | FITE 22] + FITE_1 --> 2_1((2)) + BITE_27 --> BITE_27_2[BITE 27] + BITE_8 --> BITE_8_2[BITE 8] + FITE_22 --> FITE_22_2[FITE 22] + BITE_27_2 --> 1_2((1)) + BITE_8_2 --> 0_Idle_2([0 Idle]) + FITE_22_2 --> T1156010-93/d24 + T1156010-93/d24 --> 1((1)) + 1 --> 2((2)) + 2 --> Country_Code{Country code FITE?} + Country_Code -- Yes --> FITE_1_2[FITE 1] + Country_Code -- No --> SPITE_22_2{SPITE 22?} + SPITE_22_2 -- Yes --> FITE_1_2 + SPITE_22_2 -- No --> Omit_Country[Omit country code FITE] + Omit_Country --> 2_Await_Address_2([2 Await address complete]) + FITE_1_2 --> 2_Await_Address_2 + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 5. The process starts at state '0 Idle', proceeds through 'Activate interwork procedure', 'Await CPCI FITE', and various FITE and BITE messages. It includes decision points for 'SPITE 22?' and 'Country code FITE?'. The flow ends at state '0 Idle' via connector '1'. + +FIGURE 8/Q.1152 (sheet 1 of 3) + +### Interworking of INMARSAT aeronautical system to Signalling System No. 5 + +Connector reference + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 5. The process starts at connector 1, proceeds through various signaling states (Await answer, BITE 22, FITE 22, Expiry t1, BITE 8, Stop t1, BITE 29, Answered, Idle, Start t3, Await clear forward, BITE 25, Start t2, Clearance) and ends at connector 0 (Idle).](70a863dc6cd47bac82c12162a9479aac_img.jpg) + +``` + +graph TD + 1((1)) --> Start_t1[Start t1 +(2-4 min)] + Start_t1 --> 3((3 +Await answer)) + 3 --> BITE_22_1[BITE 22] + 3 --> FITE_22_1[FITE 22] + 3 --> Expiry_t1[Expiry t1] + 3 --> BITE_8_1[BITE 8] + BITE_22_1 --> BITE_22_2[BITE 22] + FITE_22_1 --> Stop_t1_1[Stop t1] + Expiry_t1 --> BITE_29[BITE 29] + BITE_8_1 --> BITE_8_2[BITE 8] + BITE_22_2 --> Stop_t1_2[Stop t1] + Stop_t1_1 --> FITE_22_2[FITE 22] + BITE_29 --> FITE_22_3[FITE 22] + BITE_8_2 --> Stop_t1_3[Stop t1] + Stop_t1_2 --> 4((4 +Answered)) + FITE_22_2 --> 0_1((0 +Idle)) + FITE_22_3 --> 0_1 + Stop_t1_3 --> Start_t3[Start t3 +(20-30 s)] + Start_t3 --> 6((6 +Await clear forward)) + 6 --> FITE_22_4[FITE 22] + 6 --> Expiry_t3[Expiry of t3] + FITE_22_4 --> Stop_t3[Stop t3] + Expiry_t3 --> BITE_25[BITE 25] + Stop_t3 --> 0_2((0 +Idle)) + BITE_25 --> 0_2 + 4 --> BITE_25_1[BITE 25] + 4 --> FITE_22_5[FITE 22] + BITE_25_1 --> Start_t2[Start t2 +(1-2 min)] + FITE_22_5 --> FITE_22_6[FITE 22] + Start_t2 --> 5((5 +Clearance)) + FITE_22_6 --> 0_3((0 +Idle)) + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 5. The process starts at connector 1, proceeds through various signaling states (Await answer, BITE 22, FITE 22, Expiry t1, BITE 8, Stop t1, BITE 29, Answered, Idle, Start t3, Await clear forward, BITE 25, Start t2, Clearance) and ends at connector 0 (Idle). + +T1156020-93/d25 + +FIGURE 8/Q.1152 (sheet 2 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System No. 5** + +![Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 5. The process starts at state 5 (Clearance) and branches into three parallel paths: FITE 22, Expiry of t2, and BITE 22. FITE 22 leads to Stop t2, which then leads to FITE 22, which finally leads to state 0 (Idle). Expiry of t2 leads to BITE 25. BITE 22 leads to Stop t2, which then leads to state 4 (Answered). A small note 'T1 156030-93/d26' is present below state 4.](0b7849dae424b0dd33e6386d2384643a_img.jpg) + +``` + +graph TD + 5((5 Clearance)) --> FITE22_1[FITE 22] + 5 --> Expiry[Expiry of t2] + 5 --> BITE22[BITE 22] + FITE22_1 --> StopT2_1[Stop t2] + Expiry --> BITE25[BITE 25] + BITE22 --> StopT2_2[Stop t2] + StopT2_1 --> FITE22_2[FITE 22] + StopT2_2 --> 4((4 Answered)) + FITE22_2 --> 0((0 Idle)) + T1_156030_93_d26[T1 156030-93/d26] + +``` + +Flowchart showing the interworking of INMARSAT aeronautical system to Signalling System No. 5. The process starts at state 5 (Clearance) and branches into three parallel paths: FITE 22, Expiry of t2, and BITE 22. FITE 22 leads to Stop t2, which then leads to FITE 22, which finally leads to state 0 (Idle). Expiry of t2 leads to BITE 25. BITE 22 leads to Stop t2, which then leads to state 4 (Answered). A small note 'T1 156030-93/d26' is present below state 4. + +FIGURE 8/Q.1152 (sheet 3 of 3) +**Interworking of INMARSAT aeronautical system to Signalling System No. 5** + +Connector reference + +![Flowchart showing the interworking of Signalling System No. 5 to INMARSAT aeronautical system. The process starts at an 'Idle' state (Connector 0), proceeds through 'Activate interwork procedure', then to 'Await CPCI FITE' (Connector 1). It then branches into three paths: FITE 9-13, 17 (leading to 'Activate outgoing INMARSAT' and then FITE 17), FITE 22 (leading to 'Idle' state at Connector 0), and FITE 1 (leading to 'Await CPCI FITE' at Connector 1). From FITE 17, the flow goes to a decision 'More digits?'. If 'No', it goes to 'Await ST signal' (Connector 2). If 'Yes', it goes to 'Country code FITE?'. If 'No' to 'Country code FITE?', it goes to FITE 1, which leads to a connector (1) and then to another FITE 1. If 'Yes' to 'Country code FITE?', it goes to 'ST FITE?'. If 'No' to 'ST FITE?', it goes to 'Await address complete' (Connector 3). If 'Yes' to 'ST FITE?', it goes to 'Await address complete' (Connector 3). From 'Await ST signal' (Connector 2), the flow branches to FITE 1, FITE 22, and BITE 12. FITE 1 leads to connector (1). FITE 22 leads to FITE 22, which leads to BITE 8. BITE 12 leads to BITE 8. Both BITE 8 and FITE 22 lead to the final 'Idle' state (Connector 0). Connector references 1 and 2 are marked on the left side of the diagram.](bb4d2112ed07e2031c92fbff3494af9f_img.jpg) + +``` + +graph TD + Idle0_1([0 Idle]) --> ActInt[Activate interwork procedure] + ActInt --> AwaitCPCI1_1([1 Await CPCI FITE]) + AwaitCPCI1_1 --> FITE91317[/FITE 9-13, 17/] + AwaitCPCI1_1 --> FITE22_1[/FITE 22/] + AwaitCPCI1_1 --> FITE1_1[/FITE 1/] + FITE91317 --> ActOut[Activate outgoing INMARSAT] + ActOut --> FITE17[/FITE 17/] + FITE22_1 --> Idle0_2([0 Idle]) + FITE1_1 --> AwaitCPCI1_2([1 Await CPCI FITE]) + FITE17 --> MoreDigits{More digits?} + MoreDigits -- No --> AwaitST2_1([2 Await ST signal]) + MoreDigits -- Yes --> CountryCode{Country code FITE?} + CountryCode -- No --> FITE1_2[/FITE 1/] + CountryCode -- Yes --> STFITE{ST FITE?} + FITE1_2 --> C1((1)) + C1 --> FITE1_3[/FITE 1/] + FITE1_3 --> C1_2((1)) + STFITE -- No --> AwaitAddr3_1([3 Await address complete]) + STFITE -- Yes --> AwaitAddr3_2([3 Await address complete]) + AwaitST2_1 --> FITE1_4[/FITE 1/] + AwaitST2_1 --> FITE22_2[/FITE 22/] + AwaitST2_1 --> BITE12[/BITE 12/] + FITE1_4 --> C1_3((1)) + FITE22_2 --> FITE22_3[/FITE 22/] + BITE12 --> BITE8[/BITE 8/] + FITE22_3 --> BITE8 + BITE8 --> Idle0_3([0 Idle]) + T1142410-92/d27 + +``` + +Flowchart showing the interworking of Signalling System No. 5 to INMARSAT aeronautical system. The process starts at an 'Idle' state (Connector 0), proceeds through 'Activate interwork procedure', then to 'Await CPCI FITE' (Connector 1). It then branches into three paths: FITE 9-13, 17 (leading to 'Activate outgoing INMARSAT' and then FITE 17), FITE 22 (leading to 'Idle' state at Connector 0), and FITE 1 (leading to 'Await CPCI FITE' at Connector 1). From FITE 17, the flow goes to a decision 'More digits?'. If 'No', it goes to 'Await ST signal' (Connector 2). If 'Yes', it goes to 'Country code FITE?'. If 'No' to 'Country code FITE?', it goes to FITE 1, which leads to a connector (1) and then to another FITE 1. If 'Yes' to 'Country code FITE?', it goes to 'ST FITE?'. If 'No' to 'ST FITE?', it goes to 'Await address complete' (Connector 3). If 'Yes' to 'ST FITE?', it goes to 'Await address complete' (Connector 3). From 'Await ST signal' (Connector 2), the flow branches to FITE 1, FITE 22, and BITE 12. FITE 1 leads to connector (1). FITE 22 leads to FITE 22, which leads to BITE 8. BITE 12 leads to BITE 8. Both BITE 8 and FITE 22 lead to the final 'Idle' state (Connector 0). Connector references 1 and 2 are marked on the left side of the diagram. + +FIGURE 9/Q.1152 (sheet 1 of 2) +**Interworking of Signalling System No. 5 to INMARSAT aeronautical system** + +![State transition diagram for the interworking of Signalling System No. 5 to INMARSAT aeronautical system. The diagram shows three main state transition paths starting from state 3 (Await address complete), state 4 (Await answer), and state 5 (Answered). Each path involves a series of transitions between states labeled with BITE, SPITE, and FITE messages, eventually leading to the Idle state (state 0).](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S3: 3 Await address complete + S3 --> B5: BITE 5 + S3 --> B12_15_16: BITE 12, 15, 16 + S3 --> B17_20: BITE 17, 20 + S3 --> F22_1: FITE 22 + B5 --> SP6_Ring: SPITE 6 Ring tone + B12_15_16 --> B8: BITE 8 + B17_20 --> B28: BITE 28 + F22_1 --> F22_2: FITE 22 + SP6_Ring --> B27: BITE 27 + B8 --> SP6_SI: SPITE 6 SI tone + B28 --> SP6_SI + F22_2 --> S0_1: 0 Idle + B27 --> S4: 4 Await answer + S4 --> B22_1: BITE 22 + S4 --> F22_3: FITE 22 + B22_1 --> B22_2: BITE 22 + F22_3 --> F22_4: FITE 22 + B22_2 --> SP7_Ring: SPITE 7 Ring tone + F22_4 --> S0_2: 0 Idle + SP7_Ring --> S5: 5 Answered + S5 --> F22_5: FITE 22 + S5 --> B25_1: BITE 25 + F22_5 --> F22_6: FITE 22 + B25_1 --> B25_2: BITE 25 + F22_6 --> S0_3: 0 Idle + B25_2 --> S0_3 + +``` + +T1142420-92/d28 + +State transition diagram for the interworking of Signalling System No. 5 to INMARSAT aeronautical system. The diagram shows three main state transition paths starting from state 3 (Await address complete), state 4 (Await answer), and state 5 (Answered). Each path involves a series of transitions between states labeled with BITE, SPITE, and FITE messages, eventually leading to the Idle state (state 0). + +FIGURE 9/Q.1152 (sheet 2 of 2) +**Interworking of Signalling System No. 5 + to INMARSAT aeronautical system** + +![State transition diagram showing six states (00 to 05) in a linear sequence. State 00 is Idle, 01 is Wait for call set-up information, 02 is Await continuity, 03 is Wait for address complete, 04 is Wait for answer, and 05 is Answered. Transitions are shown between consecutive states, and a feedback loop exists from state 05 back to state 00. A reference code T1142430-92/d29 is present below the diagram.](e8e818455bb0d1a6153299a388b94868_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 00 + 00 --> 01 + 01 --> 02 + 02 --> 03 + 03 --> 04 + 04 --> 05 + 05 --> 00 + +``` + +T1142430-92/d29 + +State transition diagram showing six states (00 to 05) in a linear sequence. State 00 is Idle, 01 is Wait for call set-up information, 02 is Await continuity, 03 is Wait for address complete, 04 is Wait for answer, and 05 is Answered. Transitions are shown between consecutive states, and a feedback loop exists from state 05 back to state 00. A reference code T1142430-92/d29 is present below the diagram. + +| State number | State description | Sheet reference | +|--------------|----------------------------------|-----------------| +| 00 | Idle | 1 | +| 01 | Wait for call set-up information | 1 | +| 02 | Await continuity | 2 | +| 03 | Wait for address complete | 3 | +| 04 | Wait for answer | 4 | +| 05 | Answered | 4 | + +FIGURE 10/Q.1152 + +**State overview diagram for interworking of Signalling +System No. 7 ISUP to INMARSAT-Aero** + +![Flowchart showing the interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero. The process starts with 'Idle' (00), followed by 'Activate No. 7 ISUP INMARSAT-Aero', then 'Wait for call set-up information' (01). It then branches into 'FITE A' and 'FITE Z'. 'FITE A' leads to 'SPITE 53' and 'Store protocol control indicator'. 'FITE Z' leads to 'Idle' (00). Both paths lead to a decision 'Can service be provided?'. If 'No', it goes to 'BITE Z' and then 'Idle' (00). If 'Yes', it goes to another decision 'User-user service?'. If 'Yes', it goes to 'Ignore parameter'. If 'No', it goes directly to connector '2'. Both 'Ignore parameter' and the 'No' path lead to connector '2'. Connector reference '2' is on the left. A label 'T1142440-92/d30' is near the bottom right.](0a42e05c07941450f34e4f7117725834_img.jpg) + +``` + +graph TD + Idle00_1([00 Idle]) --> Activate[Activate No. 7 ISUP INMARSAT-Aero] + Activate --> Wait01([01 Wait for call set-up information]) + Wait01 --> FITE_A[/FITE A/] + Wait01 --> FITE_Z[/FITE Z/] + FITE_A --> SPITE_53[SPITE 53] + SPITE_53 --> Store[Store protocol control indicator] + FITE_Z --> Idle00_2([00 Idle]) + Store --> CanService{Can service be provided?} + CanService -- No --> BITE_Z[/BITE Z/] + BITE_Z --> Idle00_3([00 Idle]) + CanService -- Yes --> UserUser{User-user service?} + UserUser -- Yes --> Ignore[Ignore parameter] + UserUser -- No --> Connector2((2)) + Ignore --> Connector2 + Connector2 --- Ref2[2] + T1142440_92_d30[T1142440-92/d30] + +``` + +Flowchart showing the interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero. The process starts with 'Idle' (00), followed by 'Activate No. 7 ISUP INMARSAT-Aero', then 'Wait for call set-up information' (01). It then branches into 'FITE A' and 'FITE Z'. 'FITE A' leads to 'SPITE 53' and 'Store protocol control indicator'. 'FITE Z' leads to 'Idle' (00). Both paths lead to a decision 'Can service be provided?'. If 'No', it goes to 'BITE Z' and then 'Idle' (00). If 'Yes', it goes to another decision 'User-user service?'. If 'Yes', it goes to 'Ignore parameter'. If 'No', it goes directly to connector '2'. Both 'Ignore parameter' and the 'No' path lead to connector '2'. Connector reference '2' is on the left. A label 'T1142440-92/d30' is near the bottom right. + +FIGURE 11/Q.1152 (sheet 1 of 4) +**Interworking of Signalling System No. 7 (ISUP) + to INMARSAT-Aero** + +Connector reference + +![Flowchart showing interworking of Signalling System NO.7 (ISUP) to INMARSAT-Aero. It starts with connector 1, followed by 'Activate outgoing INMARSAT-Aero', a 'Which category?' decision leading to FITE 18, 18, or 19. These lead to a 'Wait continuity' state (02), then to FITE 1, 24, 25, or Z. FITE 24 leads to connector 2. FITE Z leads to another FITE Z state and then an 'Idle' state (00). Connector reference 2 is on the left.](5db6545aedab79741ebae9b27bb363b3_img.jpg) + +``` +graph TD; C1((1)) --> A[Activate outgoing INMARSAT-Aero]; A --> W{Which category?}; W --> F18_1[FITE 18]; W --> F18_2[FITE 18]; W --> F19[FITE 19]; F18_1 --> WC((02 Wait continuity)); F18_2 --> WC; F19 --> WC; WC --> F1_1[FITE 1]; WC --> F24[FITE 24]; WC --> F25[FITE 25]; WC --> FZ_1[FITE Z]; F1_1 --> C2((2)); F24 --> C2; F25 --> C2; FZ_1 --> FZ_2[FITE Z]; FZ_2 --> IDLE((00 Idle)); +``` + +Flowchart showing interworking of Signalling System NO.7 (ISUP) to INMARSAT-Aero. It starts with connector 1, followed by 'Activate outgoing INMARSAT-Aero', a 'Which category?' decision leading to FITE 18, 18, or 19. These lead to a 'Wait continuity' state (02), then to FITE 1, 24, 25, or Z. FITE 24 leads to connector 2. FITE Z leads to another FITE Z state and then an 'Idle' state (00). Connector reference 2 is on the left. + +FIGURE 11/Q.1152 (sheet 2 of 4) +Interworking of Signalling System NO.7 (ISUP) to INMARSAT-Aero + +![Flowchart for Interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero. The process starts at connector 2, checks for more FITE 1, then checks if a country code FITE. If no country code FITE, it sends FITE 1. If it is a last digit, it waits for address complete. Then it branches into four paths: BITE 5 (sending SPITE 53 and BITE X to connector 3), FITE 1 (to connector 4), BITE 12, 15, 16, 17 (sending SPITE 53 and BITE Z to connector 00), and FITE Z (to connector 00).](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +Connector reference + +``` + +graph TD + Start((2)) --> Q1{Any more FITE 1?} + Q1 -- No --> Wait[03 Wait for address complete] + Q1 -- Yes --> Q2{Country code FITE?} + Q2 -- No --> FITE1_1[/FITE 1/] + Q2 -- Yes --> Omit[Omit country code FITE] + Omit --> Q3{Last digit?} + FITE1_1 --> Q3 + Q3 -- No --> Start + Q3 -- Yes --> Wait + Wait --> BITE5[/BITE 5/] + Wait --> FITE1_2[/FITE 1/] + Wait --> BITE12_15_16_17[/BITE 12, 15, 16, 17/] + Wait --> FITEZ_1[/FITE Z/] + BITE5 --> SPITE53_15[SPITE 53 (see Table 15)] + SPITE53_15 --> BITE_X[/BITE X/] + BITE_X --> End3((3)) + FITE1_2 --> End4((4)) + BITE12_15_16_17 --> SPITE53_16[SPITE 53 (see Table 16)] + SPITE53_16 --> BITE_Z[/BITE Z/] + FITEZ_1 --> FITEZ_2[/FITE Z/] + BITE_Z --> End00((00)) + FITEZ_2 --> End00 + +``` + +2 + +4 + +4 + +3 + +T1142460-92/d32 + +Flowchart for Interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero. The process starts at connector 2, checks for more FITE 1, then checks if a country code FITE. If no country code FITE, it sends FITE 1. If it is a last digit, it waits for address complete. Then it branches into four paths: BITE 5 (sending SPITE 53 and BITE X to connector 3), FITE 1 (to connector 4), BITE 12, 15, 16, 17 (sending SPITE 53 and BITE Z to connector 00), and FITE Z (to connector 00). + +FIGURE 11/Q.1152 (sheet 3 of 4) +**Interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero** + +Connector reference + +![Flowchart showing the interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero. The process starts at connector reference 3, goes through 'Wait for answer' (04), then branches into BITE 22, FITE Z, and BITE 25. BITE 22 leads to SPITE 53 (see Table 17) then BITE Y to 'Answered' (05). FITE Z leads to another FITE Z then to 'Idle' (00). BITE 25 leads to SPITE 53 (see Table 16) then BITE Z to 'Idle' (00). From 'Answered' (05), it branches to FITE Z and BITE 25. FITE Z leads to another FITE Z then to 'Idle' (00). BITE 25 leads to SPITE 53 then BITE Z to 'Idle' (00).](ae0a735d106290c594b0bafb1f5e72e7_img.jpg) + +``` +graph TD; Start((3)) --> Wait[04 Wait for answer]; Wait --> BITE22[BITE 22]; Wait --> FITEZ1[FITE Z]; Wait --> BITE25[BITE 25]; BITE22 --> SPITE53_17[SPITE 53 (see Table 17)]; SPITE53_17 --> BITEY[BITE Y]; BITEY --> Answered[05 Answered]; FITEZ1 --> FITEZ2[FITE Z]; FITEZ2 --> Idle1[00 Idle]; BITE25 --> SPITE53_16[SPITE 53 (see Table 16)]; SPITE53_16 --> BITEZ1[BITE Z]; BITEZ1 --> Idle2[00 Idle]; Answered --> FITEZ3[FITE Z]; Answered --> BITE25_2[BITE 25]; FITEZ3 --> FITEZ4[FITE Z]; FITEZ4 --> Idle3[00 Idle]; BITE25_2 --> SPITE53_2[SPITE 53]; SPITE53_2 --> BITEZ2[BITE Z]; BITEZ2 --> Idle4[00 Idle]; +``` + +Flowchart showing the interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero. The process starts at connector reference 3, goes through 'Wait for answer' (04), then branches into BITE 22, FITE Z, and BITE 25. BITE 22 leads to SPITE 53 (see Table 17) then BITE Y to 'Answered' (05). FITE Z leads to another FITE Z then to 'Idle' (00). BITE 25 leads to SPITE 53 (see Table 16) then BITE Z to 'Idle' (00). From 'Answered' (05), it branches to FITE Z and BITE 25. FITE Z leads to another FITE Z then to 'Idle' (00). BITE 25 leads to SPITE 53 then BITE Z to 'Idle' (00). + +T1142470-92/d33 + +FIGURE 11/Q.1152 (sheet 4 of 4) +Interworking of Signalling System No. 7 (ISUP) to INMARSAT-Aero + +![State overview diagram showing six states (00 to 05) with transitions. State 00 is Idle, 01 is Wait for CPCI FITE, 02 is Await for address complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear back. Transitions are: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05. There are also transitions from 01, 02, 03, and 04 back to 00. A transition from 02 to 04 is also shown. A label 'T1142480-92/d34' is present below the diagram.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 00 + 00 --> 01 + 01 --> 00 + 01 --> 02 + 02 --> 00 + 02 --> 03 + 02 --> 04 + 03 --> 00 + 03 --> 04 + 04 --> 00 + 04 --> 05 + +``` + +T1142480-92/d34 + +State overview diagram showing six states (00 to 05) with transitions. State 00 is Idle, 01 is Wait for CPCI FITE, 02 is Await for address complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear back. Transitions are: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05. There are also transitions from 01, 02, 03, and 04 back to 00. A transition from 02 to 04 is also shown. A label 'T1142480-92/d34' is present below the diagram. + +| State number | State description | Sheet reference | +|--------------|----------------------------|-----------------| +| 00 | Idle | 1 | +| 01 | Wait for CPCI FITE | 1 | +| 02 | Await for address complete | 2 | +| 03 | Wait for answer | 3 | +| 04 | Answered | 4 | +| 05 | Clear back | 4 | + +FIGURE 12/Q.1152 +**State overview diagram for interworking of INMARSAT-Aero + to Signalling System No. 7 ISUP** + +Connector reference + +![Flowchart showing the interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP). The process starts with 'Idle' (00), followed by 'Activate INMARSAT- Aero No. 7 (ISUP)', then 'Wait for CPCI FITE' (01). It then branches into 'FITE 17, 18, 19' and 'FITE 22'. 'FITE 17, 18, 19' leads to 'Activate outgoing No. 7 (ISUP)', which leads to 'SPITE 52', then 'FITE A (see Table 18)', then 'FITE 24', and finally to connector '1'. 'FITE 22' leads to 'Idle' (00). Connector reference '1' is on the left, and connector reference '2' is at the bottom next to connector '1'. The diagram is labeled T1142490-92/d35.](3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg) + +``` +graph TD; Idle1([00 Idle]) --> Act1[/Activate INMARSAT- Aero No. 7 (ISUP)/]; Act1 --> Wait1([01 Wait for CPCI FITE]); Wait1 --> FITE1719[/FITE 17, 18, 19/]; Wait1 --> FITE22[/FITE 22/]; FITE1719 --> ActOut[/Activate outgoing No. 7 (ISUP)/]; ActOut --> SPITE52[SPITE 52]; SPITE52 --> FITEA[/FITE A (see Table 18)/]; FITEA --> FITE24[/FITE 24/]; FITE24 --> C1((1)); FITE22 --> Idle2([00 Idle]); +``` + +Flowchart showing the interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP). The process starts with 'Idle' (00), followed by 'Activate INMARSAT- Aero No. 7 (ISUP)', then 'Wait for CPCI FITE' (01). It then branches into 'FITE 17, 18, 19' and 'FITE 22'. 'FITE 17, 18, 19' leads to 'Activate outgoing No. 7 (ISUP)', which leads to 'SPITE 52', then 'FITE A (see Table 18)', then 'FITE 24', and finally to connector '1'. 'FITE 22' leads to 'Idle' (00). Connector reference '1' is on the left, and connector reference '2' is at the bottom next to connector '1'. The diagram is labeled T1142490-92/d35. + +FIGURE 13/Q.1152 (sheet 1 of 5) +**Interworking of INMARSAT-Aero to +Signalling System No. 7 (ISUP)** + +![Flowchart showing the interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP). The process starts at connector 1, proceeds to 'Wait for address complete', then branches into three paths: BITE X, BITE Z, and BITE 48. BITE X leads to SPITE 53 (see Table 19) and BITE n, ending at connector 2. BITE Z leads to BITE Z and Idle, ending at connector 2. BITE 48 leads to SPITE 53 (see Table 21), BITE J, and BITE k, ending at connector 3. Connector 3 also leads back to connector S.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +Connector reference + +``` + +graph TD + 1((1)) -- "1, 3X2" --> W[02 Wait for address complete] + W --> S((S)) + W --> BX[BITE X] + W --> BZ1[BITE Z] + W --> B48[BITE 48] + BX --> SP19[SPITE 53 +(see Table 19)] + SP19 --> BN[BITE n] + BN --> T1[Start t1 +2-4 min.] + T1 --> 2((2)) + 2 -- "4" --> 2 + BZ1 --> BZ2[BITE Z] + BZ2 --> ID[00 Idle] + ID --> 2 + B48 --> SP21[SPITE 53 +(see Table 21)] + SP21 --> BJ[BITE J] + BJ --> BK[BITE k] + BK --> 3((3)) + 3 -- "3" --> 3 + 3 --> S + +``` + +1 + +S + +2, 3 + +1, 3X2 + +02 + +Wait for address complete + +S + +3 + +BITE X + +BITE Z + +BITE 48 + +SPITE 53 (see Table 19) + +SPITE 53 (see Table 21) + +BITE n + +BITE Z + +BITE J + +Start t1 2-4 min. + +00 + +Idle + +BITE k + +2 + +4 + +3 + +3 + +T1142500-92/d36 + +Flowchart showing the interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP). The process starts at connector 1, proceeds to 'Wait for address complete', then branches into three paths: BITE X, BITE Z, and BITE 48. BITE X leads to SPITE 53 (see Table 19) and BITE n, ending at connector 2. BITE Z leads to BITE Z and Idle, ending at connector 2. BITE 48 leads to SPITE 53 (see Table 21), BITE J, and BITE k, ending at connector 3. Connector 3 also leads back to connector S. + +FIGURE 13/Q.1152 (sheet 2 of 5) +**Interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP)** + +![Flowchart showing the interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP).](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +``` + +graph TD + Start((S)) -- 2 --> F1_1[/FITE 1/] + Start -- 2 --> F22[/FITE 22/] + Start -- 2 --> B30[/BITE 30/] + + F1_1 --> CC{Country +code FITE?} + CC -- No --> SP22{SPITE 22?} + CC -- Yes --> SP22 + + SP22 -- No --> M00[00] --> Idle([Idle]) + SP22 -- Yes --> Omit[Omit +country +Code FITE] + Omit --> F1_2[/FITE 1/] + F1_2 --> C1((1)) + C1 --- N1[2] + + F22 --> FZ[/FITE Z/] + FZ -.- Note[see Note] + FZ --> M00 + + B30 --> C2((1)) + C2 --- N2[2] + + subgraph Margin + S_marg[S] + L1_top[1] + L1_bot[1] + end + + T1143220-92/d37 + +``` + +Flowchart showing the interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP). + +NOTE – In principle, FITE 22 should result in cause 16. However, in the case where FITE 22 results from a time out expiry cause 127 should be sent. + +FIGURE 13/Q.1152 (sheet 3 of 5) +**Interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP)** + + + +![State transition diagram for INMARSAT-Aero to ISUP interworking. The diagram shows states (ovals) and transitions (arrows). States include Clearback (05), FITE 22, t2-bar, BITE 24, Stop t2, BITE 25, FITE Z, and Idle (00). Transitions include Clearback to FITE 22, t2-bar, and BITE 24; FITE 22 to Stop t2; t2-bar to BITE 25; BITE 24 to Stop t2; Stop t2 to FITE Z; BITE 25 to FITE Z; and FITE Z to Idle. External connector references 4 and 3 are shown at the top and bottom right.](89f8aefc01866631793087542316cef2_img.jpg) + +Connector reference + +``` + +stateDiagram-v2 + [*] --> Clearback : 4 + Clearback --> FITE 22 + Clearback --> t2_bar : t2-bar + Clearback --> BITE 24 + FITE 22 --> Stop_t2_1 : Stop t2 + t2_bar --> BITE 25 + BITE 24 --> Stop_t2_2 : Stop t2 + Stop_t2_1 --> FITE_Z : FITE Z + BITE 25 --> FITE_Z + Stop_t2_2 --> [*] : 3 + FITE_Z --> Idle : 00 + +``` + +T1142520-92/d39 + +State transition diagram for INMARSAT-Aero to ISUP interworking. The diagram shows states (ovals) and transitions (arrows). States include Clearback (05), FITE 22, t2-bar, BITE 24, Stop t2, BITE 25, FITE Z, and Idle (00). Transitions include Clearback to FITE 22, t2-bar, and BITE 24; FITE 22 to Stop t2; t2-bar to BITE 25; BITE 24 to Stop t2; Stop t2 to FITE Z; BITE 25 to FITE Z; and FITE Z to Idle. External connector references 4 and 3 are shown at the top and bottom right. + +FIGURE 13/Q.1152 (sheet 5 of 5) +**Interworking of INMARSAT-Aero to Signalling System No. 7 (ISUP)** + +TABLE 15/Q.1152 + +| | Received BITES | +|---------------------------------|----------------| +| Backward call indicators in ACM | 5 | +| Charging indicator | 10 | +| Called party's status | 01 | +| Called party's category | 00 | +| Interworking indicator | 1 | + +TABLE 16/Q.1152 + +| Received BITES
(Release) | Cause sent | Location | +|-----------------------------|------------|----------| +| 12 | 34 | 1010 | +| 15 | 1 | 1010 | +| 16 | 17 | 1010 | +| 17 | 27 | 1010 | +| 25 | 16 | 1010 | + +TABLE 17/Q.1152 + +| | +|----------------------------------------------------| +| Backward call indicators in ANM | +| ANM without backward call indicators is to be sent | + +TABLE 18/Q.1152 + +#### **FITE A construction – Interworking of INMARSAT-Aero to ISUP** + +| | | | +|----------------------------------------|----------------|--------------------------------| +| Calling Party'S Category (CPC) | Received FITE | CPC | +| | 17
18
19 | 1010
1011
1100 | +| Continuity Check Indicator (CCH) | SPITE 36 | CCH | +| | Yes
No | 01
00 | +| Nature of Address Indicator (NAI) | SPITE 22 | NAI | +| | Yes
No | 100
011 | +| Satellite Indicator (SI) | SI = 1 | | +| Echo Control Indicator (ECI) | SPITE 21 | ECI | +| | Yes
No | 1
0 | +| Transmission Medium Requirements (TMR) | Received FITE | TMR | +| | 17
18
19 | 11
11
For further study | +| Closed user group interlock code | SPITE 51 | | +| | Yes
No | –
Set CUG
interlock code | + +TABLE 19/Q.1152 + +##### **Bite X analysis – Interworking of INMARSAT-Aero to ISUP** + +| Received BITE X | | | BITE n to be sent | +|-----------------|----|-----|-------------------| +| CH | ST | CAT | | +| 00 | 00 | 00 | BITE 27 | +| 00 | 00 | 01 | BITE 27 | +| 00 | 00 | 10 | BITE 27 | +| 00 | 01 | 00 | BITE 5 | +| 00 | 01 | 01 | BITE 5 | +| 00 | 01 | 10 | BITE 7 | +| 01 | 00 | 00 | BITE 27 | +| 01 | 00 | 01 | BITE 27 | +| 01 | 00 | 10 | BITE 27 | +| 01 | 01 | 00 | BITE 6 | +| 01 | 01 | 01 | BITE 6 | +| 01 | 01 | 10 | BITE 7 | +| 10 | 00 | 00 | BITE 27 | +| 10 | 00 | 01 | BITE 27 | +| 10 | 00 | 10 | BITE 27 | +| 10 | 01 | 00 | BITE 5 | +| 10 | 01 | 01 | BITE 5 | +| 10 | 01 | 10 | BITE 7 | + +CH Charge indicator +ST Called party's status indicator +CAT Called party's category indicator + +TABLE 20/Q.1152 + +##### **Bite Y analysis – Interworking of INMARSAT-Aero to ISUP** + +| Received BITE Y | BITE to be sent | +|-----------------|-----------------| +| CH | | +| – | BITE 22 | +| 00 | BITE 22 | +| 01 | BITE 23 | +| 10 | BITE 22 | + +CH Charge indicator + +TABLE 21/Q.1152 + +#### **CONNECT analysis – Interworking of INMARSAT-Aero to ISUP** + +| Received CONNECT fields | | | BITE j | BITE k | +|-------------------------|----|-----|---------|---------| +| CH | ST | CAT | | | +| 00 | 00 | 00 | BITE 27 | BITE 22 | +| 00 | 00 | 01 | BITE 27 | BITE 22 | +| 00 | 00 | 10 | BITE 27 | BITE 22 | +| 00 | 01 | 00 | BITE 5 | BITE 22 | +| 00 | 01 | 01 | BITE 5 | BITE 22 | +| 00 | 01 | 10 | BITE 7 | BITE 22 | +| 01 | 00 | 00 | BITE 27 | BITE 23 | +| 01 | 00 | 01 | BITE 27 | BITE 23 | +| 01 | 00 | 10 | BITE 27 | BITE 23 | +| 01 | 01 | 00 | BITE 6 | BITE 23 | +| 01 | 01 | 01 | BITE 6 | BITE 23 | +| 01 | 01 | 10 | BITE 7 | BITE 23 | +| 10 | 00 | 00 | BITE 27 | BITE 22 | +| 10 | 00 | 01 | BITE 27 | BITE 22 | +| 10 | 00 | 10 | BITE 27 | BITE 22 | +| 10 | 01 | 00 | BITE 5 | BITE 22 | +| 10 | 01 | 01 | BITE 5 | BITE 22 | +| 10 | 01 | 10 | BITE 7 | BITE 22 | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dadba845dc75c3c0dc13323643e4cc7aa77618ee --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:763504eea0996cfc68294f64c0fd91fad77b4c6261ee8c46028cd112ec1f02a4 +size 8295 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a3bb2868c0c069b986ad4407345956aa12d3ffd --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f120eabffe96af3f0b4f8739242a76c9cde225a1b5d06cbd391bae037121286c +size 57811 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fc11c8c8b95a7476223b0f239314c4f19535bdd --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15fadad459659361ac319abf586abe28465c696e7381bd31f95e308aa9cd9d71 +size 150863 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c87aec8af4aaebc9f9fde72c235adac32b56380 --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5ca5ac133865d0953b30611f9f1b765d4c23d62443f6093beb5d42feeac59b2 +size 100958 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65f44ee9e69e17c2f9fa3915a7e91042548b3097 --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b0985223b401c14746d7ed30ab9f327240164d22956833d64a04b22e439f8fb +size 109447 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f651623956961712d43c71a32967ab0c8dd47ece --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e67ce1aa07221a004a4f15001abec58c30c71256a09f12e91962f49be367f051 +size 33835 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc0dd64744010a2597262474096ba0a08df95e6b --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a257874a4c94ba0f24c9126c9e559458c04227e49544f8960675d7c1fd8be90f +size 83121 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b100dddac43f80b94a741604db467d5ee8940987 --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11cab5bddd4ad2e9f88626c555ac3a66318ba7f6b2f5cb4aa2792a15bd1708ba +size 19528 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaa8d025b5f724b35f8045b7f9b836f6ec1d0fb0 --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd11bb9963d76cc1732454de25ec62a07b47e8da5c2d81bc8728c93304df9238 +size 30348 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de9272702287e8ec0871a7e83a253de4662c17a7 --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3faec314041ef3936422004a69b4143f24042ee46c857516d3a27c6775dac715 +size 16737 diff --git a/marked/Q/T-REC-Q.1204-199303-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bfcf4e7cf182a0619b474148306409c7df4fd68 --- /dev/null +++ b/marked/Q/T-REC-Q.1204-199303-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ce53fc5138c6d499e5f7bbe4d7068030d547ca85006105e45265a46de1d6cf5 +size 17053 diff --git a/marked/Q/T-REC-Q.1211-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7622fc758cbc32d08f2c838921cadd831be4fc18 --- /dev/null +++ b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b9d5c20618a2684d4a01ddbc4aa514e91412d732141c26511676988073ba06c +size 8198 diff --git a/marked/Q/T-REC-Q.1211-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..571edce4e596785be207292a1d1b52c29f011632 --- /dev/null +++ b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00552a4b62ac81d6ae7cad8db20bae10f7747250c4993589214b66b0b0b0ac85 +size 93114 diff --git a/marked/Q/T-REC-Q.1211-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..727d76733c644768bcf1ad2150ffdf8832db20a7 --- /dev/null +++ b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee5abca8edb01c9cd5cbc26fda865ad7462cbfa97a64889ec735947616f73590 +size 42977 diff --git a/marked/Q/T-REC-Q.1211-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b62b0b1c0874747873a715cdd8e13a580ab3a06 --- /dev/null +++ b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db9391605e5d0ff92d02b42428d060158d8ed370d67f250235135ead717512a3 +size 43511 diff --git a/marked/Q/T-REC-Q.1211-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b7cda8c33f86b00f66c9475d3abbeb47aa5e05 --- /dev/null +++ b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b5f8e7983c4cf42e84b4eb249a31def35e6958f5e6cc371c3bb7738b089bbe5 +size 64682 diff --git a/marked/Q/T-REC-Q.1211-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b70baf53fd3d2a2a37c3b7f84a3c6b39773f7b6f --- /dev/null +++ b/marked/Q/T-REC-Q.1211-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0be094f266a82e7d139d7a18eaf0d1f3addc2f2544c7561f683fa466e6f3f531 +size 59887 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..414891ee28e5e50095ffec4b4ab397658fe5ea23 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe6ae4983374c2416cb7aa7b20b682f899f675cc8cdc2286f8332a0e13128413 +size 20430 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/0977b81510f7649846289ee785d20e74_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/0977b81510f7649846289ee785d20e74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56287f987f55e5eb5ff182b4c9c2a04e6babb541 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/0977b81510f7649846289ee785d20e74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fefb8deedb089b2e086659ffefb0f08395bddffa9fd574e6672f2c3666942eb +size 27443 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ff4c2c7726366aac70d38559a0b10ef4dd0bfe --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f355308f7ac1a3bb6d42bdc74f074c1b0d656c6fc455aab4599c12f1d1556274 +size 20636 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1c9860dc453fb9bf264aae9b1d2111ba9cfd8fd --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bc7258f5365d89c6bd03a9429b8bdc6484a515cf4e89ced1a1914fc86a5ff9f +size 22824 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2cfa50e2788c5d1cd39193b1a4ff0eaf5c7cdf6 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23c67596e3c9c62cec51c855165e4e166084c5c33a581cbecb5fc2b13bdb7d0d +size 17187 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31fc1fc2798375070e87409ba3ca5989b2557849 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be8fc7613476751cb71176bd62aa88b879640389ef6af3464b78db8e5cf52118 +size 8279 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2dbb82b6f7861d74fecdb500d8fc0b3a9a2f51cd --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea21d45ae31a7a663099a6990229e5ced8188c5a02c6de675ff4b204a973974c +size 18540 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bd6becc94b42429c925fb827cdcc6724a29d611 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623220569f0299ee3000dcdd00a5e7a9e391e03df51080c5c8e514e5f7d5acc8 +size 31488 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54b51949b962ece0a4e35cfd550954ba08dad237 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac46cf0682875f0e7813488d65d11f04571783206ad01db0015f34dad9584611 +size 30485 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5388ec0eba08c86ca7e05c4b03bcc620f5b0e86 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3d8b55d77f3302a0c5ee26051e2b84547815e2028d0235e2f758c0ba1cd0d4e +size 41497 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9a321e9d3d4628e7ab2975ea2a8cb6054b22ea6 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9897a320d68284e7f9666851e90f24e3b11f3fe55686c6282fa6965abbf5347 +size 18536 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67cb6258e0981079fb3366ba55c49735384bc41b --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b702d38da9641c7fb955acf8d1130eeaf4aa2b1aafc72fa33ff78fe060774fb +size 27368 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea342aabbcf86c8f184f93f0aad8bb19266bec19 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:163f495eb704cf3f70763b674ac5efecd80b292ccff76cbb074c40ab43f11776 +size 25385 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ef78ee2c4368baf44456cb1bb3690e933e0939c --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e93897d6384d1d6abeacfc63f0db0be02a535c0c1a661b2b8b84263f33841d65 +size 23370 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d4536afc9d1da1410f4fa872c45345cdb23c231 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d87e93fd2af3f7247fc5cd0e65f126421c338ab7693795b1038143e2eb97bcbb +size 132778 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/d999c095be67473b31693fab5e475f01_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/d999c095be67473b31693fab5e475f01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc00ff052e444db3a84f4c660a0b525ef403a27 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/d999c095be67473b31693fab5e475f01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf31758703e9ed4e16974a8dab53276312e29ceda23e93dfcfa6a2817beaff05 +size 32967 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/e38206fcefa2045af01d494b2956775a_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/e38206fcefa2045af01d494b2956775a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..439d812f4797e4fb4c4f3565860c332c939efe87 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/e38206fcefa2045af01d494b2956775a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:527459bf882c18bcac84678fe3d23cee9c4c594f85c7bf7bc4e14b6c3661981b +size 23635 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eab2f3e61f4306dd564f57be78673db70812170e --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f71740e83bf7b3f10be98b1dcbddb7b09602f0f65259d899cbeb054ac7a6a317 +size 29518 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a195b645a03c0c8330d1fe39cb245c357e1f7d0a --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d02e53470871c9252306369aab70d64ad82001bd6d8ff242ce31f26ef126a91a +size 71277 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..003f2a7c095b1574e0cfc46b744a5ab8de39ff23 --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5ba3991856e65829d29709637cb509fb6e95b93abbaeba2dc1ac921b203171d +size 19159 diff --git a/marked/Q/T-REC-Q.1213-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b17bd311b7ed0093b38e3428e788b3f428059d6d --- /dev/null +++ b/marked/Q/T-REC-Q.1213-199510-I_PDF-E/raw.md @@ -0,0 +1,2064 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1213** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/95) + +**INTELLIGENT NETWORK** + +--- + +**GLOBAL FUNCTIONAL PLANE +FOR INTELLIGENT NETWORK CS-1** + +**ITU-T Recommendation Q.1213** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation Q.1213 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | | Page | +|------|-------------------------------------------------------------------|-------------| +| 1 | General ..... | 1 | +| 2 | Scope of IN global functional plane for capability set 1 ..... | 1 | +| 3 | References ..... | 1 | +| 4 | IN CS-1 global functional plane modelling ..... | 2 | +| 4.1 | Role of SIBs in the global functional plane ..... | 2 | +| 4.2 | Additional characteristics of a IN CS-1 SIB ..... | 2 | +| 4.3 | IN CS-1 global functional plane model ..... | 2 | +| 4.4 | Terminology ..... | 2 | +| 5 | IN CS-1 Service Independent Building Blocks (SIBs) ..... | 3 | +| 5.1 | Data parameters for SIBs ..... | 3 | +| 5.2 | Method to describe IN CS-1 SIBs ..... | 4 | +| 5.3 | ALGORITHM ..... | 6 | +| 5.4 | AUTHENTICATE ..... | 7 | +| 5.5 | CHARGE ..... | 9 | +| 5.6 | COMPARE ..... | 12 | +| 5.7 | DISTRIBUTION ..... | 13 | +| 5.8 | LIMIT ..... | 15 | +| 5.9 | LOG CALL INFORMATION ..... | 17 | +| 5.10 | QUEUE ..... | 19 | +| 5.11 | SCREEN ..... | 21 | +| 5.12 | SERVICE DATA MANAGEMENT ..... | 23 | +| 5.13 | STATUS NOTIFICATION ..... | 26 | +| 5.14 | TRANSLATE ..... | 29 | +| 5.15 | USER INTERACTION ..... | 31 | +| 5.16 | VERIFY ..... | 33 | +| 6 | Basic call process ..... | 35 | +| 6.1 | General ..... | 35 | +| 6.2 | Points of initiation and points of return ..... | 36 | +| 6.3 | BCP stage 1 description ..... | 37 | +| 7 | Global service logic ..... | 38 | +| 7.1 | Relationship between GSL and BCP ..... | 39 | +| 7.2 | Relationship between global service logic and SIBs ..... | 39 | +| 8 | Mapping of the service plane to the global functional plane ..... | 40 | + +# **SUMMARY** + +IN capability set 1 (IN CS-1) is the first standardized stage of the intelligent network as an architectural concept for the creation and provision of telecommunication services. This Recommendation provides the Intelligent Network (IN) Global Functional Plane (GFP) architecture for IN capability set 1 (IN CS-1). This Recommendation defines the IN GFP for IN CS-1 based on the general framework for IN GFP provided in Recommendation Q.1203, consistent with the scope of IN CS-1 defined in Recommendation Q.1211. + +This Recommendation defines: + +- the IN GFP model for IN CS-1; +- identifications and definition of the 15 IN CS-1 service independent building-blocks (SIBs), including the Basic Call Process (BCP) specialized SIB; +- the use of global service logic in IN CS-1. + +Companion Recommendations include the Q.1200 and Q.1210 Series Recommendations. + +# GLOBAL FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 + +(Helsinki, 1993; modified in 1995) + +# 1 General + +The concepts for the Intelligent Network (IN) are embodied in the Intelligent Network Conceptual Model (INCM) as described in associated Recommendations I.312/Q.1201 [1]. The Global Functional Plane (GFP) of the INCM is described in associated Recommendations I.329/Q.1203 [2]. + +# 2 Scope of IN global functional plane for capability set 1 + +IN Capability Set 1 (IN CS-1) is the first standardized stage of the intelligent network as an architectural concept for the creation and provision of telecommunication services. This Recommendation provides the functional characteristics of the GFP associated specifically with IN CS-1. General GFP aspects are addressed in associated Recommendations I.312/Q.1201 [1] and I.329/Q.1203 [2]. + +The following functional characteristics are specific to IN CS-1 and are addressed in this Recommendation: + +- IN CS-1 GFP Modelling (see clause 4). +- IN CS-1 SIBs (see clause 5). + +For IN CS-1, 14 Service Independent Building Blocks (SIBs) are specified (not including the BCP SIB discussed below). These represent the minimum set of SIBs required to define the IN CS-1 targeted services, identified in Recommendation Q.1211 [3]. + +- BCP SIB (see clause 6). + +For IN CS-1 the basic call process has been defined as a specialized SIB which provides the basic call capabilities. Nine Points of Initiation (POIs) for Global Service Logic (GSL) interfaces have been specified. In addition, six Points of Return (PORs) for GSL interfaces have been specified. + +- Plane-to-plane mapping (see clause 8). + +The relationships between the service plane and the GFP are specified for IN CS-1. + +- For IN CS-1, network time is assumed to be available to all SIBs in the GFP and it does not have to be passed through call instance data. +- Stage 1 SDL diagrams are provided for IN CS-1 SIBs only where the SDLs clarify the understanding of the SIB operation. + +# 3 References + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation I.312/Q.1201 (1992), *Principles of intelligent network architecture*. +- [2] CCITT Recommendation I.329/Q.1203 (1992), *Intelligent network global functional plane architecture*. + +- [3] ITU-T Recommendation Q.1211 (1993), *Introduction to intelligent network capability set 1*. +- [4] ITU-T Recommendation Q.1290 (1993), *Glossary of terms used in the definition of intelligent networks*. +- [5] CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*. +- [6] ITU-T Recommendation Z.100 (1993), *CCITT specification and description language (SDL)*. +- [7] ITU-T Recommendation Q.931 (1993), *Digital subscriber Signalling System No. 1 (DSS 1) – ISDN user-network interface layer 3 specification for basic call control*. + +# 4 IN CS-1 global functional plane modelling + +## 4.1 Role of SIBs in the global functional plane + +SIBs are abstract representations of network capabilities that exist in an IN structured network. Their definition enforces the concept of service and technology independence by decoupling the services from the technology on which services are provided. The 14 SIBs defined in this Recommendation identify the network capabilities which will be available to service designers in a CS-1 IN structured network. Their use will provide valuable insight on how service creation will be facilitated in CS-n Recommendations. + +## 4.2 Additional characteristics of a IN CS-1 SIB + +Data required by each SIB is defined by SIB support data parameters and call instance data parameters. + +SIBs are global in nature and their location need not be considered as the whole network is regarded as a single entity in the GFP. + +## 4.3 IN CS-1 global functional plane model + +The INCM described in Recommendation I.312/Q.1201 [1] models the GFP as shown in Figure 1. Normal or non-IN supported services are processed within the BCP. When an IN supported service is to be invoked, its GSL is launched at the POI by triggering mechanism from the BCP. The global functional plane models the network from a global, or a network wide, point of view. Contained in this view is the BCP SIB, including IN CS-1 POIs and PORs, the IN CS-1 SIBs, and the GSL, which describes how SIBs are chained together to describe service features. + +This Recommendation specifies how the model can be used to fully define IN CS-1 service features in the GFP. + +## 4.4 Terminology + +The following terminology used in this Recommendation, is more fully defined in Recommendation Q.1290 [4]: + +| | | +|-------|----------------------------------| +| CID | Call Instance Data | +| CIDFP | Call Instance Data Field Pointer | +| CLI | Calling Line Identification | +| SSD | Service Support Data | + +![Diagram of the Global functional plane model. A large parallelogram labeled 'GSL' contains a rectangle labeled 'BCP' on the left and three ovals labeled 'SIB 1', 'SIB 2', and 'SIB n' on the right. An arrow labeled 'POI' points from the BCP to the SIBs, and an arrow labeled 'POR' points from the SIBs back to the BCP. The text 'T1135970-91/d01' is in the bottom right corner.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Diagram of the Global functional plane model. A large parallelogram labeled 'GSL' contains a rectangle labeled 'BCP' on the left and three ovals labeled 'SIB 1', 'SIB 2', and 'SIB n' on the right. An arrow labeled 'POI' points from the BCP to the SIBs, and an arrow labeled 'POR' points from the SIBs back to the BCP. The text 'T1135970-91/d01' is in the bottom right corner. + +FIGURE 1/Q.1213 +**Global functional plane model** + +# 5 IN CS-1 Service Independent Building Blocks (SIBs) + +The following list of SIBs have been identified as required to support the list of targeted IN CS-1 services and service features identified in Recommendation Q.1211 [3]: + +- ALGORITHM +- AUTHENTICATE +- CHARGE +- COMPARE +- DISTRIBUTION +- LIMIT +- LOG CALL INFORMATION +- QUEUE +- SCREEN +- SERVICE DATA MANAGEMENT +- STATUS NOTIFICATION +- TRANSLATE +- USER INTERACTION +- VERIFY + +The stage 1 SIB descriptions that follow reflect the understanding of the logical function of each SIB in its role of supporting IN CS-1 services and service features. The BCP, which is viewed as a specialized SIB, is described in clause 6. + +An explanation of the format of the stage 1 SIB descriptions is outlined below. + +## 5.1 Data parameters for SIBs + +By definition, SIBs are independent of the service/SF they are used to represent. They have no knowledge about previous or subsequent SIBs which are used to describe the service feature. + +In order to describe service features with these generic SIBs, some elements of service dependence is needed. Service dependence can be described using data parameters which enable a SIB to be tailored to perform the desired functionality. Data parameters are specified independently for each SIB and are made available to the SIB through global service logic. + +Two types of data parameters are required for each SIB, dynamic parameters called Call Instance Data (CID) and static parameters called Service Support Data (SSD). + +### 5.1.1 Call Instance Data (CID) + +Call instance data defines dynamic parameters whose value will change with each call instance. They are used to specify subscriber specific details like calling or called line information. This data can be: + +- made available from the BCP SIB (e.g. Calling Line Identification); +- generated by a SIB (e.g. a translated number); or +- entered by the subscriber (e.g. a dialled number or a PIN code). + +Associated with each CID value is a logical name which is referred to as the CID Field Pointer (CIDFP). If a SIB requires CID to perform its function, there will be an associated CIDFP assigned through SSD (refer to 5.1.2). For instance, the TRANSLATE SIB's CID which defines what is to be translated is called Information. The TRANSLATE SIB's SSD parameter which defines where this data can be found is CIDFP-Filter Value(s). + +Since the CID value can vary with each call instance, service features can be written with data flexibility. In the above TRANSLATE SIB example, one service feature may require translation of a calling number, while another service feature will require translation of the called number. In both cases, the data required by the SIB is specified by the information Calling Line Identity (CLI), but the CIDFP-Filter Value(s) changes. In the first service feature, the value of CIDFP-Filter Value(s) is set to CLI, while the second service feature sets the value of CIDFP-Filter Value(s) to Called Number. + +Once a CIDFP has been specified for a service feature, it can be referenced by subsequent SIBs, and the CID value can be made available to all subsequent SIBs in the SIB chain. This CIDFP is said to be fixed for that service and is constant for all instances of that service. The actual value of the CID changes for each call instance of that service feature. + +### 5.1.2 Service Support Data (SSD) + +Service support data defines data parameters required by a SIB which are specific to the service feature description. When a SIB is included in the GSL of a service description, the GSL will specify the SSD values for the SIB. SSD consists of: + +#### i) Fixed parameters + +These are data parameters whose values are fixed for all call instances. For instance, the “File Indicator” SSD for the TRANSLATE SIB needs to be specified uniquely for each occurrence of that SIB in a given service feature. The “File Indicator” SSD value is then said to be fixed, as its value is determined by the service/SF description, not by the call instance. + +If a service/SF is described using multiple occurrences of the same SIB, then fixed SSD parameters are defined uniquely for each occurrence. + +#### ii) Field pointers + +Field pointers identify which CID is required by the SIB, and in doing so provide a logical location for that data. They are signified by “CIDFP-xxxx”, where “xxxx” names the data required. For instance, “CIDFP-Filter Value(s)” for the TRANSLATE SIB will specify which CID element is to be translated. + +If more than one CID is required by a SIB to perform its function, then the SSD data parameters will contain multiple field pointers. + +## 5.2 Method to describe IN CS-1 SIBs + +The following template applies to characterize and describe the SIBs. + +### 5.2.1 Definition + +Prose description of the SIB from the service creation point of view. + +### 5.2.2 Operation + +Description of actions performed by the SIB. The operations section expands on the definition, to allow the reader to clearly understand the operation that this SIB is intended to perform. + +### 5.2.3 Potential service applications + +Service examples of where this SIB can be used. + +### 5.2.4 Input + +Input to each SIB is specified as three distinct elements: + +- one logical start; +- Service Support Data which defines parameters which are specified by the service description; +- Call Instance Data which are specific to that call instance. + +### 5.2.5 Output + +Output from each SIB is specified as two distinct elements: + +- one or more logical end; +- call instance data which defines data parameters specific to that call instance which results from the execution of that SIB and are required by other SIBs or the BCP to complete the call service instance. + +### 5.2.6 Graphic representation + +A graphic representation is used to describe input, operations and output of the SIB and is illustrated in Figure 2. Each SIB is characterized by having one logical start and one or more logical ends. These logic flows are shown by the solid arrows on the left and right of the diagram. Each logic flow is specified above each arrow. SSD parameters are identified by the dashed arrow at the top of the diagram and are specified beside the dashed arrow. Similarly, CID parameters are specified below the diagram. Input CID parameters are separated from the output parameters. + +![Diagram of an IN CS-1 SIB showing inputs and outputs.](2ba086df3506f81bae3a9b53725dcfea_img.jpg) + +The diagram shows a central rectangular box labeled 'SIB'. To its left, a solid arrow labeled 'Logic start' points into the box. To its right, three solid arrows labeled 'Logic end' point out of the box. Above the box, a dashed arrow labeled 'SSD' points down into the box, with the text 'SSD parameters' to its right. Below the box, a dashed arrow labeled 'CID' points down away from the box, with 'CID input parameters' to its left and 'CID output parameters' to its right. The text 'T1814200-91/d02' is located at the bottom right of the diagram. + +Diagram of an IN CS-1 SIB showing inputs and outputs. + +FIGURE 2/Q.1213 +Graphical representation of IN CS-1 SIB + +### 5.2.7 SDL diagram + +This diagram gives a graphic representation of the stage 1 description of the SIB using SDL macro diagrams (see Recommendation Z.100 [6]). + +## **5.3 ALGORITHM** + +### **5.3.1 Definition** + +Applies a mathematical algorithm to data to produce a data result. + +### **5.3.2 Operation** + +This SIB takes a specified call instance data and applies the specified mathematical algorithm to it to produce the corresponding data result. + +It can be used to implement a simple arithmetic operation as incrementing a counter. + +### **5.3.3 Potential service applications** + +- Mass calling; +- Televoting. + +### **5.3.4 Input** + +#### **5.3.4.1 Logical start** + +Indicates the logical start of execution for the SIB. + +#### **5.3.4.2 Service support data** + +- Type +Specifies the type of algorithm for this SIB. Two algorithms have been identified for IN CS-1: + - a) increment; + - b) decrement. +- Value +Specifies the amount to be used when applying the SIB (e.g. 1, 2, etc.). +- CIDFP-Data +This CID field pointer specifies the call instance data to which the algorithm is to be applied. +- CIDFP-Error +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### **5.3.4.3 Call instance data** + +- Data +The identifier is the data associated with the CIDFP-Data upon which algorithm is to be applied. + +### **5.3.5 Output** + +#### **5.3.5.1 Logical end** + +- Success; +- Error. + +#### **5.3.5.2 Call instance data** + +- Data +Contains the resultant value after the SIB has completed. + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for ALGORITHM: + +- a) invalid type; +- b) invalid value. + +### 5.3.6 Graphical representation + +See Figure 3. + +![Diagram of the ALGORITHM SIB graphical representation. A central box labeled 'ALGORITHM' has an input arrow from the left labeled 'Data'. Above the box, a dashed arrow labeled 'SSD' points down, with a list of fields: 'Type', 'Value', 'CIDFP - Data', and 'CIDFP - Error'. Below the box, a dashed arrow labeled 'CID' points down, with a list of fields: 'Data' and 'Error cause'. To the right of the box, two arrows point out: 'Success' and 'Error'. The diagram is labeled 'T1175130-95/d03' at the bottom right.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Diagram of the ALGORITHM SIB graphical representation. A central box labeled 'ALGORITHM' has an input arrow from the left labeled 'Data'. Above the box, a dashed arrow labeled 'SSD' points down, with a list of fields: 'Type', 'Value', 'CIDFP - Data', and 'CIDFP - Error'. Below the box, a dashed arrow labeled 'CID' points down, with a list of fields: 'Data' and 'Error cause'. To the right of the box, two arrows point out: 'Success' and 'Error'. The diagram is labeled 'T1175130-95/d03' at the bottom right. + +FIGURE 3/Q.1213 +ALGORITHM SIB + +## 5.4 AUTHENTICATE + +### 5.4.1 Definition + +Provides authentication functionality for a service. + +### 5.4.2 Operation + +This SIB provides an authentication function to establish an authorized relationship between the service logic and a database on behalf of a user. + +The authentication function can be either simple authentication or externally defined. + +### 5.4.3 Potential service applications + +- All services. + +### 5.4.4 Input + +#### 5.4.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.4.4.2 Service support data + +- Authenticate Name (optional) + +This SSD field is only used if SSD Authenticate Mechanism ID has value “Simple”. The Authenticate Name is used to identify the location of the object containing the Authenticate Password attribute in order to set up an Authorized Relationship. A “null” in this SSD field indicates that the Authenticate Name can vary and its value must be provided through call instance data. + +- Authenticate Password (optional) + +This SSD field is only used if SSD Authenticate Mechanism ID has value “Simple”. The Authenticate Password provides the data to be matched in the Authenticate Name object in order to set up an Authorized Relationship. A “null” in this SSD field indicates that the Authenticate Name can vary and its value must be provided through call instance data. + +- Authenticate Mechanism Id + +The Authenticate Mechanism Id identifies the authentication mechanism which is to be used to establish the Authorized Relationship. It may take one of the following values: + +- None, which implies that no authentication is performed. +- Simple, which implies that simple authentication is performed. +- External, which implies that an externally defined authentication is performed. + +- CIDFP – Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +- CIDFP – Authorized Relationship Id + +This CID field pointer specifies where in output call instance data the Authorized Relationship Id will be written. + +- CIDFP – Authenticate Name + +This CID Field Pointer specifies which call instance data is to be used as the Authenticate Name. + +- CIDFP – Authenticate Password + +This CID Field Pointer specifies which call instance data is to be used as the Authenticate Password. + +#### 5.4.4.3 Call instance data + +- Authenticate Name (optional) + +This CID field is only used if SSD Authenticate Mechanism Id has value “Simple” and SSD Authenticate Name has value “null”. The Authenticate Name is used to identify the location of the object containing the Authenticate Password attribute in order to set up an Authorized Relationship. + +- Authenticate Password (optional) + +This CID field is only used if SSD Authenticate Mechanism ID has value “Simple” and SSD Authenticate Name has value “null”. The Authenticate Password provides the data to be matched in the Authenticate Name object in order to set up an Authorized Relationship. + +NOTE – When Authenticate Name and Authenticate Password are supplied as input CID, the SSD parameters Authenticate Name and Authenticate Password are not used. + +### 5.4.5 Output + +#### 5.4.5.1 Logical end + +- Success (Authentication successful); +- Error. + +#### 5.4.5.2 Call instance data + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. + +- Authorized Relationship Id + +The Authorized Relationship Id provides the identity of the established Authorized Relationship through which operations can be applied. + +### 5.4.6 Graphical representation + +See Figure 4. + +![Diagram of the AUTHENTICATE SIB (Service Information Block) showing its inputs and outputs.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +The diagram illustrates the AUTHENTICATE SIB. A central rectangular box is labeled "AUTHENTICATE". Above the box, a dashed vertical line labeled "SSD" points down to the top edge, with associated parameters: "Authenticate Name", "Authenticate Password", "Authenticate mechanism Id", "CIDFP - Error", and "CIDFP - Relationship Id". To the left of the box, a solid horizontal arrow points into the box. Below the box, a dashed vertical line labeled "CID" points up to the bottom edge, with associated parameters: "Authenticate Name" and "Authenticate Password". To the right of the box, two solid horizontal arrows point outwards, labeled "Success" and "Error". Below the "Error" arrow, a dashed vertical line points down from the bottom edge, with associated parameters: "Error cause" and "Relationship Id". At the bottom right of the diagram, the text "T1175140-95/d04" is present. + +Diagram of the AUTHENTICATE SIB (Service Information Block) showing its inputs and outputs. + +FIGURE 4/Q.1213 +**AUTHENTICATE SIB** + +## 5.5 CHARGE + +### 5.5.1 Definition + +Determine special charging treatment for the call, where special refers to any charging in addition to that normally performed by the basic call process. + +In general, this involves identifying: + +- the resources for which charging is to occur; +- to where the charges are to be directed. + +It should be noted that this SIB is not responsible for the subscriber billing process. + +### 5.5.2 Operation + +The charging information output by this SIB must be compatible with the charging and billing system of the network operator or service provider. However, this SIB does not define the format of the output nor does it identify all the types of information that an Administration will require for charging. Generation of bills will often be done off-line by the Administration's existing billing system. + +The CHARGE SIB is used for specific resource charging and may be invoked several times in one service/service feature instance. + +Different simultaneous or consecutive call instances may charge the same account. + +Typical resources for which charging can occur are: + +- circuit-mode bearers; +- packet or messages; +- SRF resources, e.g. announcements, voice message storage, etc.; +- SCF usage (in units). + +Typically, charging may be directed towards: + +- a) the account identified by the CLI; +- b) the account identified by the called number (either the dialled number or the destination number); +- c) an account or credit card identified by the collected user information; +- d) the calling user's exchange accumulator; +- e) a payphone. + +### 5.5.3 Potential service application + +- Any service which requires specific IN charging. + +### 5.5.4 Input + +#### 5.5.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.5.4.2 Service support data + +- number of accounts to charge; +- Account. + +Each account is specified by two parameters, as follows: + +- a) Number + +Specifies one of the following: + +- 1) CIDFP-Line + +This CID field pointer specifies which call instance data is to be used as the line number to charge. + +- 2) CIDFP-Account + +This CID field pointer specifies which call instance data is to be used as the account number to charge. + +- 3) Fixed account + +Specifies an account number which is fixed for all call instances. + +- b) Per cent (%) + +Specifies the allocation of the total charge for this account. The sum of all allocations must equal 100%. + +- Resource type + +Specifies the resource to be charged for (e.g. bearer type, announcement, SCF usage, etc.). + +- Units + +Specifies a premium value for the specified resource type. + +- Service/service feature identifier + +Specifies the service/service feature for which charging is to be applied. + +- CIDFP-Pulse + +This CID field pointer specifies which call instance data is used to identify pulse metering on the calling line. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.5.4.3 Call instance data + +- Line(s) +Specifies a line number for charging. This can be the calling line, the dialled number or a destination number. +- Account(s) +Specifies an account number for charging. This is an account number which was entered during the call such as a credit card or a calling card number. +- Pulse metering +When specified, indicates that pulse metering is associated with the calling line. + +### 5.5.5 Output + +#### 5.5.5.1 Logical end + +- 1) Success; +- 2) Error. + +#### 5.5.5.2 Call instance data + +- Error cause +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for CHARGE: + - a) invalid account to charge; + - b) invalid percentage allocation (> 100, < 0); + - c) invalid sum of percentage allocations (not equal to 100); + - d) invalid service/service feature; + - e) invalid resource; + - f) invalid units; + - g) system fault - unable to write record. + +### 5.5.6 Graphical representation + +See Figure 5. + +![Diagram of the CHARGE SIB (Service Information Block) showing inputs, outputs, and associated data fields.](a7c51c18111139f9aca2805114108565_img.jpg) + +The diagram illustrates the CHARGE SIB. A central rectangular box is labeled "CHARGE". + +- An unlabeled arrow points into the box from the left. +- A dashed arrow points from the top of the box to a list of data fields: "# of Accounts", "Account", "Resource type", "Units", "Service/Service feature ID", "CIDFP – Pulse", and "CIDFP – Error". This list is preceded by the label "SSD". +- An arrow points from the right side of the box to the label "Success". +- An arrow points from the right side of the box to the label "Error". +- A dashed arrow points from the bottom of the box to the label "Error cause". +- A dashed arrow points from the label "CID" to the bottom of the box. +- A dashed arrow points from a group of labels ("Line(s)", "Account(s)", "Pulse metering") to the bottom of the box. +- The text "T1175150-95/d05" is located at the bottom right of the diagram. + +Diagram of the CHARGE SIB (Service Information Block) showing inputs, outputs, and associated data fields. + +FIGURE 5/Q.1213 +**CHARGE SIB** + +## 5.6 COMPARE + +### 5.6.1 Definition + +Performs a comparison of an identifier against a specified reference value. Three results are possible: + +- identifier is GREATER THAN the value; +- identifier is LESS THAN the value; +- identifier is EQUAL TO the value. + +### 5.6.2 Operation + +This SIB compares an identifier to a specified reference value. One of three logical ends will result from this operation (e.g. <, >, or =). Other logical ends can be formulated by combining two of the logical ends together (e.g. <, >, <=, or =>). + +It can be used for: + +- a) Comparing an identifier to a specified reference value. For instance, for checking that the current number of calls is less than the maximum number authorized. +- b) For checking the relationship of current network time to a customer specified time to perform time dependent decision. The comparison may be done on Time of Day (TOD), Day of Week (DOW), or Day of Year (DOY). The reference value is then the customer specified TOD, DOW or DOY. + +### 5.6.3 Potential service applications + +- Time dependent routing; +- CCBS. + +### 5.6.4 Input + +#### 5.6.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.6.4.2 Service support data + +- Comparison type + +Specifies the type of comparison to be performed. The following types have been identified: + +- a) Identifier value – Compare the identifier against the reference value. +- b) Time – Compare network time to the reference value. Network time is specified as: + - 1) time of day; + - 2) day of week; or + - 3) day of year. + +- CIDFP-Data + +This CID field pointer specifies which call instance data is to be used as the identifier. + +- Reference value + +Specifies the value against which the comparison will be made. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.6.4.3 Call instance data + +- Data +Specifies the data associated with the CIDFP-Data (see SSD) which is to be compared to the reference value. + +### 5.6.5 Output + +#### 5.6.5.1 Logical end + +- GREATER THAN the value; +- LESS THAN the value; +- EQUAL TO the value; +- Error. + +#### 5.6.5.2 Call instance data + +- Error cause +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for COMPARE: + - a) invalid identifier; + - b) invalid reference value. + +### 5.6.6 Graphical representation + +See Figure 6 + +![Diagram of the COMPARE SIB showing inputs (SSD, Data, CID) and outputs (Greater than, Less than, Equal to, Error, Error cause).](29f586959675cafdf81cf934954908eb_img.jpg) + +The diagram illustrates the COMPARE SIB as a central rectangular block. It has three input arrows on the left: a solid arrow from the left pointing to the block, a dashed arrow from the bottom labeled 'Data', and a dashed arrow from the bottom labeled 'CID'. Above the block, a dashed arrow labeled 'SSD' points down to a list of parameters: 'Comparison type', 'Reference value', 'CIDFP - Data', and 'CIDFP - Error'. To the right of the block, four solid arrows point outwards, labeled 'Greater than', 'Less than', 'Equal to', and 'Error'. Below the block, a dashed arrow labeled 'Error cause' points down to the text 'T1175160-95/d06'. + +Diagram of the COMPARE SIB showing inputs (SSD, Data, CID) and outputs (Greater than, Less than, Equal to, Error, Error cause). + +FIGURE 6/Q.1213 +**COMPARE SIB** + +## 5.7 DISTRIBUTION + +### 5.7.1 Definition + +Distribute calls to different logical ends of the SIB based on user specified parameters. + +### 5.7.2 Operation + +This SIB distributes calls to its different logical ends based on a user identified algorithm. For example, calls could be distributed based on a percentage allocated to each logical end. + +### 5.7.3 Potential service applications + +- mass calling; +- televoting; +- freephone. + +### 5.7.4 Input + +#### 5.7.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.7.4.2 Service support data + +- Algorithm type + - a) percentage; + - b) sequential; + - c) time of day; + - d) day of week. + +NOTE 1– Hierarchical call distribution may be realized through the use of multiple instances of the DISTRIBUTION SIB in conjunction with the STATUS NOTIFICATION SIB. + +- Number of logical ends + +NOTE 2 – Unlike most SSD, change of this value will effect the structure of the GSL this SIB is contained in. + +- Algorithm parameters + +If Type = percentage + +- For each logical end + - percentage (sum over all paths must equal 100). + +If Type = sequential + +- None + +If Type = time of day + +- For each logical end + - begin time associated with this logical end; + - end time associated with this logical end. + +All 24 hours of the day must be accounted for, with no overlap of time across logical ends. + +If Type = day of week + +- For each logical end + - all days of the week to be associated with this logical end. + +All days of the week must be accounted for. No day may be associated with more than one logical end. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.7.4.3 Call instance data + +- None + +### 5.7.5 Output + +#### 5.7.5.1 Logical end + +- 1 +- 2 +- ... +- N [where N = number of logical ends (item 1 of input SSD)] +- Error + +#### 5.7.5.2 Call instance data + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for DISTRIBUTION: + +- a) invalid type; +- b) invalid percentage allocation (> 100, < 0); +- c) invalid sum of percentage allocations (not equal to 100); +- d) invalid number of logical ends; +- e) missing time period; +- f) overlap of the time across logical ends; +- g) missing days; +- h) overlap of days across logical ends. + +### 5.7.6 Graphical representation + +See Figure 7. + +![Diagram of the DISTRIBUTION SIB. A central box labeled 'DISTRIBUTION' has an input arrow from the left. Above it, a dashed arrow labeled 'SSD' points down, with associated text: 'Algorithm type', 'Number of logical ends', 'Algorithm parameters', and 'CIDFP - Error'. Below it, a dashed arrow points down to 'T1136010-91/d07', with 'Error cause' and 'CID' labels nearby. To the right, three output arrows are labeled '1', '2', and 'n'.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +Diagram of the DISTRIBUTION SIB. A central box labeled 'DISTRIBUTION' has an input arrow from the left. Above it, a dashed arrow labeled 'SSD' points down, with associated text: 'Algorithm type', 'Number of logical ends', 'Algorithm parameters', and 'CIDFP - Error'. Below it, a dashed arrow points down to 'T1136010-91/d07', with 'Error cause' and 'CID' labels nearby. To the right, three output arrows are labeled '1', '2', and 'n'. + +FIGURE 7/Q.1213 +**DISTRIBUTION SIB** + +## 5.8 LIMIT + +### 5.8.1 Definition + +Limit the number of calls related to IN provided service features. Such limiting will be based on user specified parameters. + +NOTE – This SIB is not used for network congestion management functions. + +### 5.8.2 Operation + +This SIB may be used to pass all or a fraction of all calls related to IN provided service features. + +For example, calls may be passed: + +- for a specific duration (which may be infinite) at specific intervals; +- according to a counting algorithm (e.g. pass N calls out of P). + +The LIMIT SIB in conjunction with other SIBs (e.g. COMPARE) can provide the required functionality for time dependent call limiting (e.g. TOD). + +### 5.8.3 Potential service applications + +- mass calling; +- televoting; +- freephone. + +### 5.8.4 Input + +#### 5.8.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.8.4.2 Service support data + +- Type + +Specifies the type of limiting to be performed. The following types have been identified: + +- a) pass calls for (S) seconds out of every (Q) seconds; +- b) pass (N) calls out of (P) calls. + +- Parameters + +Specifies the parameters associated with the SSD type selected above: + +- 1) S duration; +- 2) Q interval; +- 3) P counter interval; +- 4) N number of calls. + +- CIDFP-File + +This CID field pointer specifies where the current limit count is located. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.8.4.3 Call instance data + +- File + +Identifies the data associated with CIDFP-File which specifies the current count of calls. + +### 5.8.5 Output + +#### 5.8.5.1 Logical end + +- pass; +- no pass; +- error. + +#### 5.8.5.2 Call instance data + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for LIMIT: + +- a) invalid type; +- b) invalid parameter. + +### 5.8.6 Graphical representation + +See Figure 8. + +![Diagram of LIMIT SIB graphical representation](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +The diagram shows a central rectangular box labeled "LIMIT". An arrow points into the box from the left. Above the box, a dashed arrow points down to it, labeled "SSD" at the top and "Type Parameters CIDFP – File CIDFP – Error" next to it. Below the box, a dashed arrow points down from it, labeled "Error cause" at the top and "CID" next to it. To the right of the box, three arrows point outwards, labeled "Pass", "No pass", and "Error" from top to bottom. At the bottom left, a dashed arrow points up to the box, labeled "File" at the top. At the bottom right, the text "T1175170-95/d08" is present. + +Diagram of LIMIT SIB graphical representation + +FIGURE 8/Q.1213 + +#### LIMIT SIB + +## 5.9 LOG CALL INFORMATION + +### 5.9.1 Definition + +Log detailed information for each call into a file. The collected information may be used by management services (e.g. statistics, etc.) and not by call-related services. + +### 5.9.2 Operation + +This SIB logs (or writes) call related information to a specified file. The type of call-related information to be logged will be identified by service support data. Each instance of this SIB will cause the recording of the specified CID information. + +### 5.9.3 Potential service applications + +- All services. + +### 5.9.4 Input + +#### 5.9.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.9.4.2 Service support data + +##### – CIDFP-Data + +These CID field pointers specify which call instance data are to be used as identifiers. CIDFP-Data can include: + +- a) call attempt time; +- b) call stop time; +- c) call connect time; +- d) dialled number; +- e) destination number; +- f) additional dialled number (e.g. credit card number, etc.); +- g) calling line identification; +- h) time in queue; +- i) bearer capability; +- j) error causes; +- k) any other CID. + +##### – Log file name + +Specifies the log file object where the value of the identifier is to be logged. + +##### – CIDFP - Authorized Relationship Id + +This CID field pointer specifies which call instance data is to be used as the Authorized Relationship Id. + +##### – CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.9.4.3 Call instance data + +##### – Data + +Specifies the data associated with the CIDFP-Data (see SSD) which is to be logged. + +##### – Authorized Relationship Id + +The Authorized Relationship Id provides the identity of the established Authorized Relationship through which the operations can be applied. + +### 5.9.5 Output + +#### 5.9.5.1 Logical end + +- Success (information written); +- Error. + +#### 5.9.5.2 Call instance data + +##### – Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for LOG CALL INFORMATION: + +- invalid identifier; +- invalid log file indicator. + +### 5.9.6 Graphical representation + +See Figure 9. + +![Diagram of LOG CALL INFO SIB. A central box labeled 'LOG CALL INFO.' has an input arrow from the left. Above it, 'SSD' points to it with a list: 'Log file name', 'CIDFP - Data', 'CIDFP - Error', 'CIDFP - Authorized Relationship Id'. Below it, 'Data' and 'Authorized Relationship Id' point to it. To the right, 'Success' and 'Error' point away from it. Below the box, 'CID' points to it, and 'Error cause' and 'T1175180-95/d09' point away from it.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +graph TD + SSD[SSD] -- "Log file name +CIDFP - Data +CIDFP - Error +CIDFP - Authorized Relationship Id" --> LCI[LOG CALL INFO.] + Input(( )) --> LCI + LCI --> Success[Success] + LCI --> Error[Error] + Data[Data] --> LCI + ARID[Authorized Relationship Id] --> LCI + CID[CID] --> LCI + LCI --> EC[Error cause] + LCI --> T117518095d09[T1175180-95/d09] + +``` + +Diagram of LOG CALL INFO SIB. A central box labeled 'LOG CALL INFO.' has an input arrow from the left. Above it, 'SSD' points to it with a list: 'Log file name', 'CIDFP - Data', 'CIDFP - Error', 'CIDFP - Authorized Relationship Id'. Below it, 'Data' and 'Authorized Relationship Id' point to it. To the right, 'Success' and 'Error' point away from it. Below the box, 'CID' points to it, and 'Error cause' and 'T1175180-95/d09' point away from it. + +FIGURE 9/Q.1213 +**LOG CALL INFO SIB** + +## 5.10 QUEUE + +### 5.10.1 Definition + +Provide sequencing of IN calls to be completed to a called party. + +### 5.10.2 Operation + +This SIB provides all the processing needed to provide queueing for a call, and will specifically: + +- pass the call if resources are available; +- queue the call; +- optionally play announcements to caller on queue; +- when resources become available, dequeue the call. + +### 5.10.3 Potential service application + +- All IN services which use call queueing service feature. + +### 5.10.4 Input + +#### 5.10.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.10.4.2 Service support data + +- Max active + Specifies the maximum number of active calls allowed for the resource. +- Max number + Specifies the maximum number of calls allowed on queue at a given time. +- Max time + Specifies the maximum time the call may remain on the queue. + +##### – Announcement parameters + +Specify the control values for announcements. The control values which can be specified are: + +- Announcement ID: specifies which announcement is to be sent; the Announcement ID could be “null” to signify that no announcement is to be sent. +- Repetition requested: specifies if the announcement is to be repeated; +- Repetition interval: specifies the delay period in seconds between repetitions; +- Maximum repetitions: specifies the maximum number of times the announcement will be repeated. + +##### – CIDFP-Call + +This CID field pointer specifies which call instance data identifies the specific call. + +##### – CIDFP-Resource + +This CID field pointer specifies which call instance data identifies the resource. + +##### – CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.10.4.3 Call instance data + +##### – Call reference + +Identifies the specific call which is a candidate for queueing. + +##### – Resource + +Specifies the data associated with the CIDFP-Resource which identifies the resource for which the call will be queued. + +### 5.10.5 Output + +#### 5.10.5.1 Logical end + +- 1) Resource available; +- 2) Call party abandon; +- 3) Queue timer expiry; +- 4) Queue full; +- 5) Error. + +#### 5.10.5.2 Call instance data + +##### – Time spent in queue + +Identifies the total time that a particular call was queued. + +##### – Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for QUEUE: + +- a) invalid Max active; +- b) invalid Max number; +- c) invalid Max time; +- d) invalid announcement parameters; +- e) invalid call reference. + +### 5.10.6 Graphical representation + +See Figures 10 and 11. + +![Diagram of the Queue SIB (Service Information Block) structure. A central box labeled 'Queue' has several input and output arrows. Inputs include: SSD (top, dashed arrow), Call reference Resource (left, dashed arrow), and CID (bottom, dashed arrow). Outputs include: Max active, Max number, Max time, Announcement parameter, CIDFP - Resource, CIDFP - Error (all from SSD, dashed arrow); Resource available, Call party abandon, Q timer expiry, Q full, Error (all from the right side, solid arrows); and Time spent on queue, Error cause (from the bottom, dashed arrow). A reference code T1175190-95/d10 is shown at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Diagram of the Queue SIB (Service Information Block) structure. A central box labeled 'Queue' has several input and output arrows. Inputs include: SSD (top, dashed arrow), Call reference Resource (left, dashed arrow), and CID (bottom, dashed arrow). Outputs include: Max active, Max number, Max time, Announcement parameter, CIDFP - Resource, CIDFP - Error (all from SSD, dashed arrow); Resource available, Call party abandon, Q timer expiry, Q full, Error (all from the right side, solid arrows); and Time spent on queue, Error cause (from the bottom, dashed arrow). A reference code T1175190-95/d10 is shown at the bottom right. + +FIGURE 10/Q.1213 + +#### **QUEUE SIB** + +## **5.11 SCREEN** + +### **5.11.1 Definition** + +Perform a comparison of an identifier against a list to determine whether the identifier has been found in the list. + +### **5.11.2 Operation** + +This SIB takes the appropriate identifier and determines whether or not it is contained within the list identified by the SIB support data. A “Match” condition results if the identifier has been found on the list. + +Examples using the SCREEN SIB are: + +- for verifying a user ID or PIN; +- for terminating or originating call screening based on a network address. + +Multiple instances of the SCREEN SIB, in conjunction with other SIBs, like TRANSLATE and COMPARE, may result in more complex screening capabilities. + +### **5.11.3 Potential service applications** + +- Selective call forward on busy/don’t answer; +- Originating call screening; +- Terminating call screening; +- Security screening; +- Account card calling; +- Credit card calling. + +### **5.11.4 Input** + +#### **5.11.4.1 Logical start** + +Indicates the logical start of execution for the SIB. + +![Flowchart for QUEUE SIB stage 1. The process starts with 'Logical start' leading to 'Input parameters valid?'. If 'No', it goes to 'No error'. If 'Yes', it checks 'Maximum allowed' (Usage count exceeded?). If 'Yes', it checks 'Mat Q size' (Q count exceeded?). If 'Yes', it goes to 'Q full'. If 'No', it proceeds through 'Q call', 'Start Q timer', 'Increment Q count', 'Optimal' (Play announcement), and 'Request notifications abandon' to a 'Wait' state. From 'Wait', three paths emerge: 'Time expired' (leading to 'Dequeue call', 'Decrement Q count', 'Cancel announcement', and 'Q timer expired'), 'Abandon' (leading to 'Dequeue call', 'Decrement Q count', 'Cancel announcement', and 'Call party abandon'), and 'Resource free' (leading to 'Dequeue call', 'Decrement Q count', 'Cancel announcement', and then looping back to 'Usage count exceeded?'). A side path from 'Usage count exceeded?' (No) leads to 'Inc. usage counter' and 'Request discount notification or perform status notification', which then loops back to 'Usage count exceeded?'. A 'Resource available' label is near the notification block. A dashed line from 'Wait' to 'Resource free' is labeled 'Determined by discount notification or status notification'. The code 'T1176190-95/d11' is at the bottom right.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +graph TD + Start([Logical start]) --> Valid{Input parameters valid?} + Valid -- No --> NoError[No error] + Valid -- Yes --> MaxAllowed{Maximum allowed} + MaxAllowed -- Yes --> MatQSize{Mat Q size} + MatQSize -- Yes --> QFull[Q full] + MatQSize -- No --> QCall[Q call] + QCall --> StartQTimer[Start Q timer] + StartQTimer --> IncrementQCount[Increment Q count] + IncrementQCount --> Optimal[Optimal] + Optimal --> PlayAnnouncement[Play announcement] + PlayAnnouncement --> RequestNotificationsAbandon[Request notifications abandon] + RequestNotificationsAbandon --> Wait([Wait]) + MaxAllowed -- No --> IncUsageCounter[Inc. usage counter] + IncUsageCounter --> RequestDiscount[Request discount notification or perform status notification] + RequestDiscount --> MaxAllowed + RequestDiscount --> ResourceAvailable[Resource available] + Wait --> TimeExpired{Time expired} + Wait --> Abandon{Abandon} + Wait --> ResourceFree{Resource free} + TimeExpired --> DequeueCall1[Dequeue call] + DequeueCall1 --> DecrementQCount1[Decrement Q count] + DecrementQCount1 --> CancelAnnouncement1[Cancel announcement] + CancelAnnouncement1 --> QTimerExpired[Q timer expired] + Abandon --> DequeueCall2[Dequeue call] + DequeueCall2 --> DecrementQCount2[Decrement Q count] + DecrementQCount2 --> CancelAnnouncement2[Cancel announcement] + CancelAnnouncement2 --> CallPartyAbandon[Call party abandon] + ResourceFree --> DequeueCall3[Dequeue call] + DequeueCall3 --> DecrementQCount3[Decrement Q count] + DecrementQCount3 --> CancelAnnouncement3[Cancel announcement] + CancelAnnouncement3 --> MaxAllowed + Note1[Determined by discount notification or status notification] -.-> ResourceFree + +``` + +Flowchart for QUEUE SIB stage 1. The process starts with 'Logical start' leading to 'Input parameters valid?'. If 'No', it goes to 'No error'. If 'Yes', it checks 'Maximum allowed' (Usage count exceeded?). If 'Yes', it checks 'Mat Q size' (Q count exceeded?). If 'Yes', it goes to 'Q full'. If 'No', it proceeds through 'Q call', 'Start Q timer', 'Increment Q count', 'Optimal' (Play announcement), and 'Request notifications abandon' to a 'Wait' state. From 'Wait', three paths emerge: 'Time expired' (leading to 'Dequeue call', 'Decrement Q count', 'Cancel announcement', and 'Q timer expired'), 'Abandon' (leading to 'Dequeue call', 'Decrement Q count', 'Cancel announcement', and 'Call party abandon'), and 'Resource free' (leading to 'Dequeue call', 'Decrement Q count', 'Cancel announcement', and then looping back to 'Usage count exceeded?'). A side path from 'Usage count exceeded?' (No) leads to 'Inc. usage counter' and 'Request discount notification or perform status notification', which then loops back to 'Usage count exceeded?'. A 'Resource available' label is near the notification block. A dashed line from 'Wait' to 'Resource free' is labeled 'Determined by discount notification or status notification'. The code 'T1176190-95/d11' is at the bottom right. + +FIGURE 11/Q.1213 +QUEUE SIB stage 1 + +#### 5.11.4.2 Service support data + +- Screen list name + +The screen list name identifies the screen data object to be used. + +- Screen list Filter + +The Screen list Filter identifies the attributes and filter tests to be applied to the attributes in the screen data object. The attribute values are stored in the CIDFP – Screen pointers. + +- CIDFP-Data + +This CID field pointer(s) specifies which call instance data is to be used as the identifier(s). + +- CIDFP - Authorized Relationship Id + +This CID field pointer specifies which call instance data is to be used as the Authorized Relationship Id. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.11.4.3 Call instance data + +- Data + +The Data CID is the attributes values associated with the CIDFP-Data (see SSD) which is to be filtered against the screen data object. + +- Authorized Relationship Id + +The Authorized Relationship Id provides the identity of the established Authorized Relationship through which the operations can be applied. + +### 5.11.5 Output + +#### 5.11.5.1 Logical end + +- Match [= on the list]. + +- CIDFP – Authorized Relationship Id + +This CID field pointer specifies which call instance data is to be used as the Authorized Relationship Id. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.11.5.2 Call instance data + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for SCREEN: + +- a) invalid identifier; +- b) invalid screen list. + +### 5.11.6 Graphical representation + +See Figure 12. + +## 5.12 SERVICE DATA MANAGEMENT + +### 5.12.1 Definition + +Enables end user specific data to be replaced, retrieved, incremented, or decremented. + +![Diagram of the SCREEN SIB (Service Information Block) showing its inputs, outputs, and internal structure.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +The diagram illustrates the SCREEN SIB. At the top, a list of parameters is shown under the heading 'SSD': + + +- Screen list name +- Screen list filter +- CIDFP – Authorized Relationship Id +- CIDFP – Data +- CIDFP – Error + + An arrow points from this list down to a central rectangular box labeled 'SCREEN'. To the left of this box, an arrow points into it, and below it, another arrow points into it from the text 'Data Authorized Relationship Id'. To the right of the 'SCREEN' box, three arrows point outwards to the labels 'Match', 'No match', and 'Error'. Below the 'SCREEN' box, an arrow points down to the text 'Error cause'. At the very bottom, the text 'T1181620-96/d12' is shown. To the left of the bottom arrow, the text 'Data Authorized Relationship Id' is present. Below the 'SCREEN' box, there is also a label 'CID' with an arrow pointing up to the box from below. + +Diagram of the SCREEN SIB (Service Information Block) showing its inputs, outputs, and internal structure. + +FIGURE 12/Q.1213 + +#### **SCREEN SIB** + +### 5.12.2 Operation + +This SIB performs the appropriate actions, i.e. replace, retrieve, increment, or decrement information stored within the network. For example, this SIB could be used to retrieve or replace a customer's call forwarding number. + +### 5.12.3 Potential service application + +- Call forwarding; +- Customer profile management. + +### 5.12.4 Input + +#### 5.12.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.12.4.2 Service support data + +- Object name + +Specifies the subscriber data object to be used. + +- Action + +Specifies the operation to be performed on the subscriber data. The following actions are allowed: + +- a) Replace – Replace the existing data element in the subscriber file specified by the element indicator with new data specified by the information value. +- b) Retrieve – Copy the data element specified by the element indicator and place it in the output CID called data retrieved. +- c) Increment – Increase the value of the data element in the subscriber file specified by the element indicator by the amount indicated by the Inc/Dec value. +- d) Decrement – Decrease the value of the data element in the subscriber file specified by the element indicator by the amount indicated by the Inc/Dec value. + +- e) SetToDefault – Reset the value of the data attribute in the subscriber data object to its default value. + - f) addObject – Add a new data object into the database. In this case the Attribute indicator must contain all of the object attributes which are required to correctly initialize the data object. + - g) removeObject – Remove a data object from the database. +- Attribute indicator + +Specifies the data attribute in the subscriber data object upon which the action is to be performed. This optional data parameter is only required when the field to be acted upon is constant for all call instances (e.g. changing a call forwarding number). A “null” in this SSD field indicates that the attribute indicator can vary and its value must be provided through call instance data. + - Inc/Dec value + +Specifies the amount by which the attribute indicator is to be incremented or decremented. + - CIDFP-Info + +This CID field pointer specifies which call instance data is to be used as the information value. + - CIDFP-Attribute + +This CID field pointer specifies which call instance data is to be used as the attribute indicator. If the attribute indicator is to be specified by the SSD, then this CID field pointer will not be used by the SIB. + - CIDFP-Retrieve + +This CID field pointer specifies where in call instance data the retrieved data element is to be written. + - CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.12.4.3 Call instance data + +- Information value + +Specifies the new value for the subscriber attribute data. This data is passed to this SIB from the user interaction SIB using the output CID parameter called collected data. +- Attribute indicator + +Specifies the data attribute in the subscriber data object upon which the action is to be performed. +- Authorized Relationship Id + +The Authorized Relationship Id provides the identity of the established Authorized Relationship through which the operations can be applied. + +### 5.12.5 Output + +#### 5.12.5.1 Logical end + +- Success (record written or retrieved); +- Error. + +#### 5.12.5.2 Call instance data + +- Retrieved Value(s) + +Specifies the data attribute(s) values retrieved. + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for SERVICE DATA MANAGEMENT: + +- invalid object indicator; +- invalid action; +- invalid attribute indicator; +- invalid information value; +- invalid Inc/Dec value. + +### 5.12.6 Graphical representation + +See Figure 13. + +![Diagram of SERVICE DATA MANAGEMENT SIB showing inputs and outputs.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +The diagram illustrates the SERVICE DATA MANAGEMENT SIB. A central rectangular box is labeled "SERVICE DATA MANAGEMENT". + +- A solid horizontal arrow points into the box from the left. +- A dashed vertical arrow points into the box from the top, labeled "SSD". To the right of this arrow is a list of parameters: OBJECT NAME, Action, ATTRIBUTE, CIDFP – Info, CIDFP – ATTRIBUTE, CIDFP – Retrieve, CIDFP – AUTHORIZED RELATIONSHIP ID, and CIDFP – Error. +- A dashed vertical arrow points out of the box from the bottom, labeled "CID". To the right of this arrow is a list of parameters: RETRIEVED VALUE and ERROR CAUSE. Below this list is the text "T1181630-96/d13". +- A dashed vertical arrow points into the box from the bottom left, labeled "Information value", "ATTRIBUTE INDICATOR", and "AUTHORIZED RELATIONSHIP ID". +- Two solid horizontal arrows point out of the box to the right, labeled "Success" and "Error". + +Diagram of SERVICE DATA MANAGEMENT SIB showing inputs and outputs. + +FIGURE 13/Q.1213 +SERVICE DATA MANAGEMENT SIB + +## 5.13 STATUS NOTIFICATION + +### 5.13.1 Definition + +Provide the capability of inquiring about the status and/or status changes of network resources. + +### 5.13.2 Operation + +There are four types of status notification requests: + +- Poll resource status – Return the current status of the resource. +- Wait for status – Wait until the resource assumes the desired status unless the resource is already in the desired status. +- Initiate continuous monitor – Monitor and record the changes in busy/idle status; subsequent monitor – Return all the changes in status for the resource or other events as required. +- Cancel continuous monitor. + +“Poll resource status” status notification could be used to determine if the destination address is busy or idle. In the busy case, “Wait for status” status notification could be used to notify service logic when the destination address becomes idle. “Initiate continuous monitor” status notification could be needed to create a resource history file. + +### 5.13.3 Potential service applications + +- CCBS; +- call distribution; +- freephone; +- call transfer. + +### 5.13.4 Input + +#### 5.13.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.13.4.2 Service support data + +- Type + +Specifies the type of operation for this SIB. Four types have been identified: + +- a) poll resource status; +- b) wait for status; +- c) initiate continuous monitor; +- d) cancel continuous monitor. + +- Resource + +Specifies the particular entity to be monitored. The following resources can be monitored: + +- 1) lines; +- 2) trunks. + +- Timer + +Specifies the maximum amount of time to monitor the resource. If the value of timer is “null” no time limit is specified. This SSD is not used if the type is set to “poll resource status” or “cancel continuous monitor”. + +- Status notification file name + +Specifies the file object where the current resource status is to be logged. If a “null” value is specified, the resource status will not be logged. This SSD is not used if type is set to “cancel continuous monitor”. + +- Resource status + +Specifies the desired status of the resource being monitored. This SSD is only used when the type is set to “wait for status”. Valid resource status’s are: + +- a) busy; +- b) idle. + +- CIDFP-Status + +This CID field pointer specifies where in call instance data the resultant status of the resource is to be written. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.13.4.3 Call instance data + +- None. + +### 5.13.5 Output + +#### 5.13.5.1 Logical end + +- Success + - Poll resource status – Present status returned. + - Wait for status – Line or resource has assumed the given status. + - Initiate continuous monitor – Continuous monitor initiated. + - Cancel continuous monitor – Continuous monitor terminated. +- Timer expiry (only used with “wait for status”). +- Error. + +#### 5.13.5.2 Call instance data + +- Status + +Specifies the current status of the resource. + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for STATUS NOTIFICATION: + +- a) invalid type; +- b) invalid resource; +- c) invalid timer; +- d) invalid file indicator; +- e) invalid resource status. + +### 5.13.6 Graphical representation + +See Figure 14. + +![Diagram of STATUS NOTIFICATION SIB showing inputs (SSD, CID) and outputs (Success, Timer expiry, Error, Status, Error cause).](0977b81510f7649846289ee785d20e74_img.jpg) + +The diagram illustrates the STATUS NOTIFICATION SIB. A central rectangular box is labeled "STATUS NOTIFICATION". To its left, an arrow points into the box. Above the box, a dashed vertical line labeled "SSD" at the top points down to the box. To the right of this line, a list of parameters is shown: Type, Resource, Resource status, Timer duration, Status notification file indicator, CIDFP – Status, and CIDFP – Error. Below the box, a dashed vertical line points down to the text "T1136080-91/d14". To the left of this line is the label "CID". To the right of the line, the labels "Status" and "Error cause" are present. From the right side of the box, three arrows point outwards to the labels "Success", "Timer expiry", and "Error". + +Diagram of STATUS NOTIFICATION SIB showing inputs (SSD, CID) and outputs (Success, Timer expiry, Error, Status, Error cause). + +FIGURE 14/Q.1213 +STATUS NOTIFICATION SIB + +## **5.14 TRANSLATE** + +### **5.14.1 Definition** + +Determines output information from input information. + +### **5.14.2 Operation** + +This SIB translates input information and provides output information, based on the various other input parameters. Parameters provided identify which file should be scanned for the translation. Translation can be based on either input information only, or on input information and the CLI. + +For example, this SIB could be used for modifying input information (for instance, dialled digits) into a standard numbering plan upon which network routing is based. + +In conjunction with other SIBs, like COMPARE, the TRANSLATE SIB can provide the required functionality for time dependant routing. + +### **5.14.3 Potential service applications** + +- Freephone; +- User-defined routing; +- VPN; +- UPT; +- Abbreviated dialling; +- Selective call forwarding on busy/don't answer; +- Call forwarding; +- Call transfer. + +### **5.14.4 Input** + +#### **5.14.4.1 Logical start** + +Indicates the logical start of execution for the SIB. + +#### **5.14.4.2 Service support data** + +- Object Name + +Specifies where the translation data object is located. + +- Translate Filter + +The Translate Filter identifies the attributes and filter tests to be applied to the attributes in the translate data object. The attribute values are stored in the CIDFP – Filter Value(s) pointers. + +- Translated Attribute + +Specifies which object attribute(s) is to be returned to Translated data value(s). + +- CIDFP-Filter Value(s) + +This CID field pointer(s) specifies which call instance data is to be used as the information. + +- CIDFP-Translated Data + +This CID field pointer specifies where in call instance data that the translated data attribute value is to be written. + +- CIDFP - Authorized Relationship Id + +This CID field pointer specifies which call instance data is to be used as the Authorized Relationship Id. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.14.4.3 Call instance data + +- Filter Value(s) + +Specifies the translate filter data value(s) to be used. Stored in CIDFP - Filter Value(s). + +- Authorized Relationship Id + +The Authorized Relationship Id provides the identity of the established Authorized Relationship through which the operations can be applied. + +### 5.14.5 Output + +#### 5.14.5.1 Logical end + +- Success; +- Error. + +#### 5.14.5.2 Call instance data + +- Translated data + +Specifies the data element(s) resulting from the translation. + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for TRANSLATE: + +- invalid type; +- invalid file indicator; +- invalid information; +- translation not available. + +### 5.14.6 Graphical representation + +See Figure 15. + +![Figure 15: TRANSLATE SIB graphical representation. The diagram shows a central 'TRANSLATE' block. Above it, an 'SSD' (Service Selection Data) block lists parameters: object name, Translate filter, Translated Attribute, CIDFP - Filter Value(s), CIDFP - Translated Data, CIDFP - Authorized Relationship Id, and CIDFP - Error. A dashed arrow points from the SSD to the TRANSLATE block. To the left of the block, an arrow points into it, and below it, a dashed arrow points into it labeled 'Filter value(s)' and 'Authorized Relationship Id'. To the right of the block, two arrows point out: 'Success' and 'Error'. Below the block, a dashed arrow points out labeled 'Translated data' and 'Error cause'. At the bottom center, 'CID' is written. At the bottom right, 'T1175200-95/d15' is written.](d999c095be67473b31693fab5e475f01_img.jpg) + +Figure 15: TRANSLATE SIB graphical representation. The diagram shows a central 'TRANSLATE' block. Above it, an 'SSD' (Service Selection Data) block lists parameters: object name, Translate filter, Translated Attribute, CIDFP - Filter Value(s), CIDFP - Translated Data, CIDFP - Authorized Relationship Id, and CIDFP - Error. A dashed arrow points from the SSD to the TRANSLATE block. To the left of the block, an arrow points into it, and below it, a dashed arrow points into it labeled 'Filter value(s)' and 'Authorized Relationship Id'. To the right of the block, two arrows point out: 'Success' and 'Error'. Below the block, a dashed arrow points out labeled 'Translated data' and 'Error cause'. At the bottom center, 'CID' is written. At the bottom right, 'T1175200-95/d15' is written. + +FIGURE 15/Q.1213 +**TRANSLATE SIB** + +## 5.15 USER INTERACTION + +### 5.15.1 Definition + +Allows information to be exchanged between the network and a call party, where a call party can be either a calling or a called party. + +### 5.15.2 Operation + +This SIB provides a call party with information (e.g. announcements) and/or collects information from a call party. + +The announcements can be, for example: + +- DTMF tones; +- a customized or generic audio message; +- network progression tones (e.g. dial tone, busy tone, etc.). + +The collected information can be, for example: + +- DTMF tones; +- audio; +- IA5 string text. + +This SIB provides the specified announcement (which may be null) to the user. Depending on the repetition type (i.e. count, time), the message is repeated until the repetition number or time is reached. + +Expected user input may be null. Assuming it is not null and user interruptibility is allowed, the message is stopped upon initial input by the user. If user interruptibility is not allowed or the message (or message sequence) is completed with no input from the user, the first input should be received within the initial response time after the message (or message sequence) is terminated, otherwise an error condition results. + +User input is considered complete when the maximum number of characters has been reached, or an end delineator character is received, or the inter-digit timer has been exceeded. + +The stage 2 SDL representation of this SIB may be helpful in understanding its operation. Refer to 5.2.12/Q.1214. + +### 5.15.3 Potential service applications + +- Most IN CS-1 services will require user interaction. + +### 5.15.4 Input + +#### 5.15.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.15.4.2 Service support data + +- Announcement parameters + +Specify the following control values for announcements: + +##### a) Announcement ID + +Specifies which announcement is to be sent. The Announcement ID could be “null” to signify that no announcement is to be sent. + +##### b) Repetition requested + +Specifies if the announcement is to be repeated. + +##### c) Repetition interval + +Specifies the delay period in seconds between repetitions. + +##### d) Maximum repetitions + +Specifies the maximum number of times the announcement will be repeated. + +- e) Duration + +Specifies the maximum length of time the announcement will be played. +- Collect information parameters + +Specify the control values for user entered information. + + - 1) User interruptibility + +Specifies if an announcement can be interrupted by the call party entering information (yes or no). + - 2) Voice feedback + +Specifies if the user is given a vocalization of the users input. + - 3) Type + +Specifies the expected form of the user entered information. The following forms can be identified: + + - i) DTMF; + - ii) audio; + - iii) IA5 string; + - iv) null (where null signifies that no data is to be collected). + - 4) Maximum number of characters + +Specifies the maximum number of characters to collect, ( $> = 0$ , where 0 identifies non-character input). + - 5) Minimum number of characters + +Specifies the minimum number of characters to collect, ( $< =$ the maximum, $> = 0$ , where 0 identifies non-character input). + - 6) Initial input waiting timer + +Specifies the maximum time to wait for beginning of call party's response. + - 7) Inter-character waiting timer + +Specifies the maximum time to wait after a pause by the call party. + - 8) End delineator + +Specifies special character(s) signifying the end of an input. If this parameter is “null”, no delineator is specified. +- CIDFP-Call\_Party + +This CID field pointer specifies which call instance data is to be used to identify the call party. +- CIDFP-Collected + +This CID field pointer specifies where in output call instance data that the call party entered data is to be written. +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.15.4.3 Call instance data + +- Call party identifier + +Specifies the data associated with the CIDFP-Call\_Party which identifies the call party exchanging information with the network. + +### 5.15.5 Output + +#### 5.15.5.1 Logical end + +- Success; +- error. + +#### 5.15.5.2 Call instance data + +- Collected data + +Specifies the data collected by the network from the call party. + +- Error cause + +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for USER INTERACTION: + +- call abandon; +- collection time out (no input received); +- incorrect number of digits received; +- announcement resource unavailable; +- data collection resource unavailable; +- invalid announcement ID; +- invalid call party; +- inconsistent timer setting; +- call status incompatible with playing of announcements; +- call status incompatible with collecting information. + +### 5.15.6 Graphical representation + +See Figure 16. + +![Diagram of User Interaction SIB (SIB 16) showing the flow of information between the SSD (Switching System Data) and the UI (User Interface).](e38206fcefa2045af01d494b2956775a_img.jpg) + +The diagram illustrates the interaction between the SSD (Switching System Data) and the UI (User Interface). The SSD provides 'Announcement parameters', 'Collect info parameters', and 'CIDFP' (Call party, Collected, Error) to the UI. The UI outputs 'Success' and 'Error'. The UI also receives 'Call party id.' from the SSD and provides 'Collected data' and 'Error cause' back to the SSD. The diagram is labeled 'T1136100-91/d16' and 'CID'. + +Diagram of User Interaction SIB (SIB 16) showing the flow of information between the SSD (Switching System Data) and the UI (User Interface). + +FIGURE 16/Q.1213 +USER INTERACTION SIB + +## 5.16 VERIFY + +### 5.16.1 Definition + +Provide confirmation that information received is syntactically consistent with the expected form of such information. + +### 5.16.2 Operation + +Information is compared with the format expected for the data. The VERIFY SIB normally follows the USER INTERACTION SIB when information has been collected from a call party. + +The service support data identifies the type of data format. This SIB compares the input data to that expected format. + +This SIB may, for example, be used when there is a need to verify the syntax of information. This could be: + +- a user identification; +- a network address; +- any extra dialogue such as PIN code dialling or answer to a call prompt. + +### 5.16.3 Potential service applications + +- Freephone; +- selective call forwarding; +- UPT; +- televoting. + +### 5.16.4 Input + +#### 5.16.4.1 Logical start + +Indicates the logical start of execution for the SIB. + +#### 5.16.4.2 Service support data + +- Maximum number of characters + +Specifies the maximum number of characters allowed. + +- Minimum number of characters + +Specifies the minimum number of characters allowed. + +- Format + +Format specifies the expected syntax of the data being verified. The format is specified using “code” characters. The following “codes” have been identified: + +- 1) x Any character; +- 2) L Any letter; +- 3) A Upper case letters only; +- 4) a Lower case letters only; +- 5) D Any digit (0-9) or delineator (#, \*); +- 6) N Any digit (0-9); +- 7) n Any digit except 0 (1-9); +- 8) [x] Optional character, where x represents any of the specified “codes”; +- 9) \x\ Specific character(s) required (e.g. \01\ indicated that either a 0 or a 1 must be present at that designated position in the data being verified). + +For example, the format “NNNN\c” would indicate that a PIN code of 2387c would pass syntax verification, while 2387d would fail. + +- CIDFP-Data + +This CID field pointer specifies which call instance data is to be used as the identifier to be verified. + +- CIDFP-Error + +This CID field pointer specifies where in output call instance data the error cause will be written. + +#### 5.16.4.3 Call instance data + +- Data +Specifies the data associated with the CIDFP-Data which is to be verified. + +### 5.16.5 Output + +#### 5.16.5.1 Logical end + +- Pass; +- Fail; +- Error. + +#### 5.16.5.2 Call instance data + +- Error cause +Identifies the specific condition which caused an error during the operation of the SIB. The following errors have been identified for VERIFY: + - a) invalid format; + - b) invalid identifier; + - c) inconsistent Max/Min number of characters specified. + +### 5.16.6 Graphical representation + +See Figure 17. + +![Diagram of VERIFY SIB process showing inputs (SSD, Data, CID) and outputs (Pass, Fail, Error, Error cause).](24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg) + +The diagram illustrates the VERIFY SIB process. A central rectangular box is labeled 'VERIFY'. Above the box, a list of parameters under the heading 'SSD' is shown: 'Maximum number', 'Minimum number', 'Format', 'CIDFP – Data', and 'CIDFP – Error'. An arrow points from this list down into the top of the 'VERIFY' box. To the left of the box, an arrow points into it, labeled 'Data' below it. Below the box, a dashed line labeled 'CID' points up into the bottom of the box. To the right of the box, three arrows point out to the labels 'Pass', 'Fail', and 'Error'. Below the box, a dashed line labeled 'Error cause' points down from the bottom of the box. At the bottom right of the diagram, the text 'T1175210-95/d17' is present. + +Diagram of VERIFY SIB process showing inputs (SSD, Data, CID) and outputs (Pass, Fail, Error, Error cause). + +FIGURE 17/Q.1213 +**VERIFY SIB** + +# 6 Basic call process + +## 6.1 General + +The Basic Call Process (BCP) has been defined in 4.0/I.329/Q.1203 [2] as a specialized SIB which provides the basic call capabilities. + +These capabilities enable the use of GSL as well as other SIBs to completely describe IN CS-1 services and service features. + +It is not necessary or intended to fully model the BCP on the GFP in IN CS-1, but rather to insure that the functionality of the BCP that is required on the GFP in conjunction with SIBs be available to fully support IN CS-1 services/service features. + +## **6.2 Points of initiation and points of return** + +The BCP functional interfaces to the global service logic in the GFP are described as Points of Initiation (POI) and Points of Return (POR). These are defined in 4.2/I.329/Q.1203. + +IN CS-1 service flexibility is provided by defining specific POI and POR interfaces between the BCP and GSL. This flexibility allows a chain of SIBs to represent different services based on the launching POI and the returning POR. + +For example, a SIB chain which screens a network address against a list could represent an originating call screening service if the address analysed POI launches the chain. However, if the prepared to complete call POI was used to launch the same chain, a terminating call screening service could result. + +Furthermore, using the screening example from above, different services can result based upon which POR is used to complete the chain. If a “Match” logic end of the SCREEN SIB, is followed by a proceed with new data POR, a call is allowed to complete and this is an example of positive screening. However, negative screening, or call blocking, can be done with the same SIB chain by having the “Match” followed by a clear call POR. + +### **6.2.1 List of POIs** + +The following set of POIs has been identified for IN CS-1. + +#### **Call originated** + +This POI identifies that the user has made a service request without yet specifying a destination address (e.g. off-hook but before dialling). + +#### **Address collected** + +This POI identifies that the address input has been received from the user. + +#### **Address analysed** + +This POI identifies that the address input has been analysed to determine characteristics of the address (e.g. freephone number). + +#### **Prepared to complete call** + +This POI identifies that the network is prepared to attempt completion of the call to the terminating party. + +#### **Busy** + +This POI identifies that the call is destined for a user who is currently busy. + +#### **No answer** + +This POI identifies that the call has been offered to a user who has not answered. + +#### **Call acceptance** + +This POI identifies that the call is active but the connection between the calling and called parties is not established (e.g. called party off-hook but no switch-through). + +#### **Active state** + +This POI identifies that the call is active and the connection between the calling and called parties is established. + +#### **End of call** + +This POI identifies that a call party has disconnected. + +### **6.2.2 List of PORs** + +The following set of PORs has been identified for IN CS-1. + +#### **Continue with existing data** + +This POR identifies that the BCP should continue call processing with no modification. + +#### **Proceed with new data** + +This POR identifies that the BCP should proceed with call processing with only a data modification. + +#### **Handle as transit** + +This POR identifies that the BCP should treat the call as if it had just arrived. + +#### **Clear call** + +This POR identifies that the BCP should clear the call. + +#### **Enable call party handling** + +This POR identifies that the BCP should perform functions to enable call control for individual call parties. + +The use of this POR and the definition of any additional SIBs needed to support call party handling, are for further study. + +#### **Initiate call** + +This POR identifies that the call should be initiated. This may be independent of an existing call, or may be in the context of an existing call. + +## **6.3 BCP stage 1 description** + +### **6.3.1 Definition** + +This specialized SIB allows access to IN services/service features represented through the use of chains of SIBs and global service logic. The interface points between this SIB and GSL are described as POIs and PORs. + +### **6.3.2 Operation** + +The BCP contains a set of armed POIs, and if during the processing of a call, one of these POIs is encountered, a chain of SIB is executed through global service logic. + +When the chain of SIB terminates, call processing may be influenced according to the specified POR. + +NOTE – Non-IN supported services are processed in the BCP and no GSL processing is required. + +### **6.3.3 Potential service applications** + +- All IN CS-1 services. + +### **6.3.4 Output** + +Specifies the POI and data parameters which are passed to GSL. + +#### **6.3.4.1 Logical output** + +Initiate global service logic from a specified POI. + +#### **6.3.4.2 Service support data** + +- Set of POIs + +Specifies the points in the BCP where IN service logic processing can occur for a given service. + +- CIDFP-CLI + +This CID field pointer specifies which call instance data is to be used as the CLI. + +- CIDFP-Category +This CID field pointer specifies which call instance data is to be used as the CLI category data. +- CIDFP-Dialled +This CID field pointer specifies which call instance data is to be used as the dialled number. +- CIDFP-Destination +This CID field pointer specifies which call instance data is to be used as the destination number. +- CIDFP-Call reference +This CID field pointer specifies which call instance data identifies the call reference. +- CIDFP-Bearer +This CID field pointer specifies which call instance data is to be used as the CLI bearer capability. + +#### 6.3.4.3 Call instance data + +- Calling line identity +Specifies the network address from which the call in progress originated. +- Calling line category +Specifies the characteristics of CLI (e.g. payphone, operator, etc.). +- Dialled number +Specifies the number(s) dialled by the caller. +- Destination number +Specifies the number(s) dialled by the caller (the destination number although originally the same as the dialled number, may be modified through IN service processing). +- Call reference +Identifies a specific call. +- Bearer capabilities +Specifies the ISDN bearer capabilities (see Recommendation Q.931 [7]) requested by the caller. + +### 6.3.5 Input + +#### 6.3.5.1 Logical input + +Resume BCP at the point specified by the GSL specified POR. + +#### 6.3.5.2 Call instance data + +- Destination number +Specifies a network address to which the call in progress is to be connected. For instance, a chain of SIBs may be used to create a destination number which differs from the dialled number. + +### 6.3.6 Graphical representation + +See Figure 18. + +# 7 Global service logic + +Global Service Logic (GSL) is the “glue” that describes the order in which SIBs can be chained together to accomplish services. + +![Diagram of the Basic call process SIB (BCP). A central box labeled 'BCP' contains 'POI' on the left and 'POR' on the right. Above the box, 'SSD' and 'Set of POIs' are listed, with 'CIDFP' parameters (CLI, Category, Dialled, Destination, Bearer, Error) also shown. An arrow points from this list to the 'POI' inside the box. To the right, 'CID' and 'Destination Number' are listed, with an arrow pointing to the 'POR' inside the box. Below the box, 'CID' parameters (Call reference, Calling line identity, Calling line category, Dialled number, Destination number, Bearer capability, Error cause) are listed. The diagram is labeled 'T1136140-91/d18'.](798679874d1c29f8343506a156c79d7e_img.jpg) + +Diagram of the Basic call process SIB (BCP). A central box labeled 'BCP' contains 'POI' on the left and 'POR' on the right. Above the box, 'SSD' and 'Set of POIs' are listed, with 'CIDFP' parameters (CLI, Category, Dialled, Destination, Bearer, Error) also shown. An arrow points from this list to the 'POI' inside the box. To the right, 'CID' and 'Destination Number' are listed, with an arrow pointing to the 'POR' inside the box. Below the box, 'CID' parameters (Call reference, Calling line identity, Calling line category, Dialled number, Destination number, Bearer capability, Error cause) are listed. The diagram is labeled 'T1136140-91/d18'. + +FIGURE 18/Q.1213 +**Basic call process SIB** + +For a given IN CS-1 services/service feature, global service logic is used to describe: + +- i) A specific POI which will define the functional launching point from the BCP to the SIB chain. Refer to 6.2.1 for a list of IN CS-1 POIs. +- ii) A specific set of PORs where the SIB chain can logically return to the BCP. Refer to 6.2.2 for a list of IN CS-1 PORs. +- iii) The pattern and order of SIBs which are to be chained together. This pattern begins at the POI defined in i) and ends at the set of PORs defined by ii). Refer to clause 5 for a list of IN CS-1 SIBs. +- iv) Data parameters (SSD and CID) for each SIB in the SIB chain. + +## 7.1 Relationship between GSL and BCP + +Global service logic on the global functional plane views basic call process as a single resource. Based upon such a view of IN services, the following are identified as necessary interactions between global service logic and BCP, for example: + +*Communications from BCP to GSL:* + +- i) *Logical start for SIB chains* – Which is represented by POIs. +- ii) *Data* – Which is represented by call instance data, which is required by SIB chains for processing IN service features. Examples of specific call instance data which the BCP may be responsible for, could include calling line identity and dialled number. + +*Communications from GSL to BCP:* + +- i) *Logical termination for SIB chains* – Which is represented by PORs. +- ii) *Data* – Which is represented by call instance data that have been defined by one or more SIBs on a SIB chain. An example of such a call instance data could be a destination number. GSL ensures that all relevant CID is maintained throughout multiple SIB chains until termination of each call instance. + +## 7.2 Relationship between global service logic and SIBs + +The remaining components of GSL needed to define a service/SF, are the collection of SIBs (including their service support and call instance data), and the topology of their interconnection (to each other and to the POIs and PORs of the BCP). This specifies the functionality required to support the service/SF and the sequence of occurrence of this functionality. + +# 8 Mapping of the service plane to the global functional plane + +Referring to Figure 19 in the GFP, non-IN services are processed through the basic call process. When an IN Service Feature (SF) is to be evoked, it is initiated by a triggering mechanism from the basic call process. The chain “link” pattern which describes the SF, must then be obtained by the global service logic in order to process the SF. As new SFs are designed their SIB descriptions must be made available to the global service logic. + +![Diagram showing the mapping of service features to the global functional plane. It includes two chains of SIBs (SIB 1-6) and a table defining the links between them.](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) + +The diagram illustrates the mapping of service features to the global functional plane. At the top, two chains of Service Information Blocks (SIBs) are shown. Chain No. 1 consists of SIB 1, SIB 2, SIB 3, and SIB 6, with POI entering SIB 1 and POR exiting SIB 6. Chain No. 2 consists of SIB 4 and SIB 5, with POI entering SIB 4 and POR exiting SIB 5. A branching arrow points from SIB 2 in Chain No. 1 to SIB 4 in Chain No. 2. Below this, a box labeled 'Basic call process' is connected to a box labeled 'SF representation in GSL'. Arrows labeled POI and POR connect these two boxes. A callout box titled '(SF No. xyz)' contains a table defining the links between SIBs. + +| SIB | From | To | +|-------------|------|-----| +| | BCP | 1 | +| | 1 | 2 | +| Chain No. 1 | 2 | 3 | +| | 3 | 6 | +| | 6 | BCP | +| Chain No. 2 | 2 | 4 | +| | 4 | 5 | +| | 5 | BCP | + +T18 12470-91/d19 + +Diagram showing the mapping of service features to the global functional plane. It includes two chains of SIBs (SIB 1-6) and a table defining the links between them. + +FIGURE 19/Q.1213 +Global functional plane blueprint of a service feature \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1222-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1222-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36a32fb27730598abaef54b051cf1fffedc17599 --- /dev/null +++ b/marked/Q/T-REC-Q.1222-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c315972c25456ec61dce423cf7bdb17e9326e1a8465e66d166c5dfadaf26aa35 +size 8270 diff --git a/marked/Q/T-REC-Q.1222-199709-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.1222-199709-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4953e2123e431470211e41b34ad8833ec2b04b5e --- /dev/null +++ b/marked/Q/T-REC-Q.1222-199709-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0ca7badd3b87e479f9ce8247dc8ba0b3343b1271032fff10014938e31d746fc +size 42141 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e80f81a7ef30fa4b403137c16cfe906e6fde3d2 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a884e9cb4733ab8f76ff98e9e0242350daa96b47987838f54e8de51e33592ee4 +size 24173 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb3e41c6c48f974af2c457744dc5cff2535c68b1 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc7ab29ecc27279c3ba41c941a07c85c2d291f4347372f46bb970503b2ad4c93 +size 20899 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1fafba4c85a7a3a964bb9b5475e9343dcf0bf2a --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9138c536c1860fb01ababdb6f8476397c8d400e97886ca5ac6fc49affffb171c +size 26622 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1f914de725f1b6b69e361359cf46376ef304ecd --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12bd811d9759074e178bcbea3f0b2a261c42f9e3bd3beba56ce3614d16511918 +size 49350 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15f23490d16a731d18e011126b55f790ac27c286 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a1f28fc37fc1032ebcd104c02bdf4f7a9c9b5eb3cc135b2cf35fef0c6cc1dde +size 40446 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec593e2cc4ee8e70a79ec16029a273038813efd5 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a36a4b7bd8bff27bc3d8701b59c307cf750c17501ce59f5240abdfd62ac1cfa +size 9961 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3f3bbf61ae84db638105ba5550fe049c20f751b --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eb3de11dbab9975832afed48f2d29ced80079b0c8247aedfabb92fa663f7d88 +size 11230 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7004ef6e343d2f95028c7b3a6d7385ac9741929d --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7edae0f3434e0523e187ca30ade7025dc218b48220dd5f736feb2a2cb5fce0d1 +size 30342 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53b271c2397870a45923c8745409a867d76c29fb --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8659f171a9491d242dfd89a1c90c6ef0719b5a0e44e7590ad95b25aa343dba69 +size 8450 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/144e1d61e8738b22dcf4a683f869ac6f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/144e1d61e8738b22dcf4a683f869ac6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80250b5413a111e01d2994171c8a71fd051f7013 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/144e1d61e8738b22dcf4a683f869ac6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:780f0992ff8dabff8d06ae76c2311681a2c012f0ff15c62ecc4c3cbead0071df +size 7408 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c43abfbdff14454e4084086b10cbfb37bc8c0ae --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cdc83481006a8340f9d8af812b4c4a9bd107af48f8e4fc3e40faf96894f2e19 +size 39967 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/19d7a7ce68d3e9036613910b761c4b24_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/19d7a7ce68d3e9036613910b761c4b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c371c85f51dbef435dd268a1dceaf178908b5eaa --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/19d7a7ce68d3e9036613910b761c4b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:287c31c26be37efc347c8067459ef318d7b853fcd5804f70b90b98fe969c17ce +size 15844 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc80aac471ecbac2f7b8838cd2a041a4d840ae74 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dc2f3e436ffa28ebb083cf769e072e43d5e9c56b855f69a64f3d06dd7aa177d +size 9406 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/257c8341b41f1f4a287f27d33227974c_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/257c8341b41f1f4a287f27d33227974c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc75bb97c44b34863cbf32fdcf33acf417228e85 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/257c8341b41f1f4a287f27d33227974c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af75a08baa76078b6d0affd333a23b5baf5fb7f85be772b8f5fa24fc9af34361 +size 28106 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa432c668c646fe0e938daf7a2bec3c8f824358a --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ef0b02272cf96c2acbe8b67e8ea9f798da45efee45bb0fade8743793fcd874e +size 16926 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd505d23e3b2ee43658297797d372701655802ce --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afae721a32877e66363373aebede9a082e3b4803c947b67f9ed164e36aebbb5b +size 26534 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1861996959db7de032b417f0a49fb0644a02878d --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46d3d23e6ca730903d361a2cc413aaa53048312e7cfc75908d567527e21dfb22 +size 39495 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55c47c07859fcf4ebe49196f13a80c274498eefb --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13aaf4665af44af468f9db334008328aa2b2f18767b55f7bcd14a528cf68be71 +size 25411 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af4907f573b8e3995122d6ed2ac85c157b35da29 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04b29ca620041c645025310b345f29ab5831faada884b3e73636d66e9dbb3576 +size 101720 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e0dfaa5e40642984c1b6b142779096b4a11bd75 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dcc2b87de894a2b9fd0a13f3d480cc32df77405d59369089b71f7f60e17f40f +size 133668 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..032996997976cfc76768347cad3c82f26b7b13fd --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:538209eeb181b36b6d1848a4ad7267c6799f803a8a42c00e023a8455b63746f3 +size 8046 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..303304f273d47d71a2643e750cdae34fd30f8119 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6453843b3c6fd39e5e25f8611d51d57eabd222e2c2ff0ea4abf6597fa8192381 +size 8522 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ede9ffe068b18eb41847e329ad33bfc26d76b68 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e68751982e882873d3ba0ca4f7db8fc453b1d74a4dfa9cff81d01090912e660 +size 7602 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0e53da2cb16a30f01e23643e588360c27d9694d --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11401ef4b53efb0af93bde498105e54e4e8995e1662ef480dc26a9b183f0fa15 +size 9438 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/44ffa7f0e6419d046ab4fed0faaf7738_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/44ffa7f0e6419d046ab4fed0faaf7738_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be0ee8c3caeca3babb6c019a35c9c9f7b60bc44f --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/44ffa7f0e6419d046ab4fed0faaf7738_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2be6e4534445ad5baca7b714f5d79a64d608550f521da1312744f7491f89edc3 +size 26522 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4540c7355b250cb891be0b54b0ba25c7_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4540c7355b250cb891be0b54b0ba25c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb3a177b95e94ec279b6a744bd65eb8a0a77c825 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4540c7355b250cb891be0b54b0ba25c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8972aac3711a9234caaf137a78a2d5efe3041db815e9ed30d4f9bd5455c651f4 +size 30435 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4801e73fa692059f2ca78196e6e907be_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4801e73fa692059f2ca78196e6e907be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2b8865b8c1e70226d06e8fb2e3bd3e0c1999b67 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4801e73fa692059f2ca78196e6e907be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f0a5cb02765c8b2bdaf73e1033448f353a4f5ea12d3ade07859d3b39969915 +size 26696 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef21e09c8544ee4a852ddd190cf01ae02851774 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:473616ef7c10eed1d0f7196cfdd7a7c7025627fc64a77d30b93d818667926548 +size 25101 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6525df23e805c6edce243a1b2a2a085bba5f24e4 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a50492fac3626b2ff0940a644d71b14b7b489e56e67a293fdfad8c616e763c41 +size 7337 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b38f53becca5e7f8fa4744500b75e66dd9b0cf3 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d11c63313eda1bf9c1307cab0fe43d0a1965d617ab45f5ca4111afa9029dd04 +size 35806 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f30701758699bf36ba4a4741199223f66adc5bab --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2082a9d98b3a9f317a7a975aa026f67683497d8a4a7dee83cadf1b7b5c9938c7 +size 7115 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/64544fbada794f3cdf4f78f5d83613e4_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/64544fbada794f3cdf4f78f5d83613e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4609a9a632815d5c850a4e3962beb35dc450fba3 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/64544fbada794f3cdf4f78f5d83613e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cf0c71bbc742700ca273811c0af7313649fbe2ec84eb3aabdaa3aea2e9d9716 +size 11968 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/677bcb564410628b8b966ad87b394888_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/677bcb564410628b8b966ad87b394888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20158ce5053cb1222076e3e326884580e36e6d32 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/677bcb564410628b8b966ad87b394888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10bfae9f523f5f93515776be114a42c9b98c00f15b540745187a66782a424764 +size 11915 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/6cc85a2b62fd8a2a3faab29730f20e81_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/6cc85a2b62fd8a2a3faab29730f20e81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80ed7bd6fc4c8b6c3e9c1db9bb890695d7bf9c1a --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/6cc85a2b62fd8a2a3faab29730f20e81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:763aac83aae8dca384491361574f5a30227a78f8409e1d8f5103c00baebd47a4 +size 23367 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f5188f22ec45816170b99db9d4cefc35012de11 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8641f5711ca9193f2cb7c7689cb4598938c9e6932244093f12a9645b308fe6f5 +size 29182 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/7136ef99edf9289cc069898bd584d3aa_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/7136ef99edf9289cc069898bd584d3aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e3813d317797cee7d7c84cd0844c389b978cb55 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/7136ef99edf9289cc069898bd584d3aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:550f279b1da5077ea364a71c024128b704086eea23fd96c7fe6b97a794c72c29 +size 6434 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f4c61d8be85033819fa6b9a8ea7b7011ac5949 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c7752b3452ed38f58c516608d24f40d2b0c92040405478209d44aba0f001f14 +size 30321 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8db4732bcce5a584c4bdf2a2cd43a9f45ceba11f --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29392df9be5c582fbc9805935cd73c08ab595b56448be1f5b507dd0eee555f81 +size 101124 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33fbd1be478747c326a299d9bc957c9389ce0605 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0b0739bf668f9e767081fae8ba7042f003f6a8395b53b8ad0c16b1d082b16d1 +size 25215 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e67f17fa4a91082ab62164536862f9217a2782b --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb3006740fc0a47a60fb8c152a91863b6af9469447a300f3a9b8693bf6526114 +size 7254 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb645b65393c273f8712bc290a9bbbfffab5a5f6 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b498e50a1f2d2e1a2faf310f14c1f9e8b10f8498763ed5015df5b5e405c9896b +size 11641 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d39cb566688c49fce1e3eb435b2b13755b30b8d --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bed8a60d5557d289cc66db2ca75301598bd8227fec05a194f29a7272fd55787 +size 72012 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad8bab077298369f047af03971419e4e80d24fa7 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5aa7716639a58c264db1b8a3b132e337e32cda05b8db18e20c96bcdf3b7b829a +size 10293 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d178f4a1d1825673d9e21555c1ca5066ebdd4b2 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2c37bedfdc914472dd09568d0cdbf1084976362f5c993abda3c5ef2a79115ff +size 6759 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9f36c6b324a774daa4b7534c22acd4b85d11046 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a0b8e2b1f8a69892cb020772d13a6ce4bced896947739c7191e0c51e756fd9d +size 32538 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b60f017acac2f85adcfd13cde1a4192c_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b60f017acac2f85adcfd13cde1a4192c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf9f2520fc9bae57db341c872eacf355967e0144 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b60f017acac2f85adcfd13cde1a4192c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:747f90757404c4e2cf6b2e348cd6cba4e0094e5b1e23e0d42cbff8c9ee25b200 +size 30791 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8167d000d3ee2cbfc08811f574067ee4d05b62c8 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6060b13fffc94810e0d026c99bacbe1d76d7ab88ad0b0ba544d8f1697251d2d2 +size 41412 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef1e3b4282f315cc975e525388e08bc4c1d6b9d9 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a090cec7fdb9de6bbad62b1574b2cd9753fc262f232e7d94ab14ff8491b4007 +size 29104 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b81579496ec150959b9993b6968dc24a0c9e9c9d --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb750d22f9c63f15428cabea8ac305e78ffb0ec779da63655dcbe5ce3d6450f2 +size 21103 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faf5bbefdd1e8b2e31332ad0819f5843caec92dd --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:621445767f86d7d3ff190f0d44dd4476f0705c694b56b6c7518edba454b1adb0 +size 29280 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e6eb176c85cd67c8290464b4c941bca761db29e --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3747729de67b718c064bd8e750e8d24ce8b750b0c83f8276552f26d8956c09a +size 5757 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bf44be18eae0974bc9a4931ed4cbfeb92800c4f --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e179b246ea11ce3724042e32f652b7a19abb7da294dedfa54d3fdb1b89f28b8f +size 87524 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbad87979014d2b50709bb039aa8e67b057a0b97 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:848f2f2e43c1302d58e35d894c2815b66e44211ef6463a8688d7f37baf44c804 +size 52304 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/d9cfc30025244dcd75766061f27ee09f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d7fc0b86f736c75ad16b3cfb56b4e581edb7061 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/d9cfc30025244dcd75766061f27ee09f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fd9ae688e7bdb10294adae5587ee7fe95003b26ae0132b090727abc64d9ed3f +size 33503 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/dae88eec6d1005984029b794ff8b7a9e_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/dae88eec6d1005984029b794ff8b7a9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..514a26ae55c505d445fb9f3b7f1a4b5d73c1beb4 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/dae88eec6d1005984029b794ff8b7a9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b6b70c04dc9c25fd3b3cc1c26571c89ee6492dfccd33add8a359fa2da0e5a0d +size 24044 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/dde1a42ca58cd189901556a0cbfe7d57_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/dde1a42ca58cd189901556a0cbfe7d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09052bcf6a87430fe799e5bbcf7d856c225256d8 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/dde1a42ca58cd189901556a0cbfe7d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ad23b2e86142e70d7caec95cf1c991b0a47bed7c4429579ae0a3656f45de667 +size 23914 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/e38f0349f1b6094626cbfeab7105f029_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/e38f0349f1b6094626cbfeab7105f029_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcd927f225bc219ade61b279381bc5f45d0c0b81 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/e38f0349f1b6094626cbfeab7105f029_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0b35a86a96ee7baf67467690257493006affc3216edf1411b4d557205477fd0 +size 25501 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/e776395ba1d4a6d568f08b406d784abd_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/e776395ba1d4a6d568f08b406d784abd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dc4a639279c26b14640572595aa0868640f7be2 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/e776395ba1d4a6d568f08b406d784abd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ce5de1ecee89910eb2aec92027bca29a7b28194622931c7f1c4093ed99dd05a +size 38810 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2000af489e27590c1319aac56189eaa2f2d227ee --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b78b9d4df7a6ef82b8d6d4747c5f4d19b833cdff72cc8cf36e2d90f8f3ba60aa +size 48270 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bec592ad01a46ab9dffff27b19d2c6b732918a2 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5ab647903a992929f281907b08d84be6c2959eab9b6c40a1b43e14176c614d8 +size 49908 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5230c65079d60b9422b0d338de82b0eb23b8e78e --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec2d2467fa4d7893366699470ab991560c701749d8fc25c1ffa6036ad76f49e6 +size 22014 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79d695d11956236e97e8a279caf80fe8c7690342 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77dc06ae4e985984a4da281eb76ffea844902266672290ebdbf4f22187976dc +size 28342 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1a043ede993a03f143b9a54c802d437d3c59dc2 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:296d5648a13aca589a4b7c22d5ef878bfc5f5ac8fc82367350b4837641fe4a27 +size 53406 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f65418d8fb0f84f6664b38cb7f361518f94a8e75 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdb8624020fd8ecc2a4ec48d2c0601dd2e2137556f183bed7993e3c839e9ae76 +size 30319 diff --git a/marked/Q/T-REC-Q.1223-199709-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45c07df523ebf69566500250018198d9ff88de98 --- /dev/null +++ b/marked/Q/T-REC-Q.1223-199709-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:672843ddb6faa241dc57ff13bdc91797e2329a596593f2fbe15e9e0f801074e9 +size 25817 diff --git a/marked/Q/T-REC-Q.1225-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1225-199709-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6a53b67001f0da2b5613c0891d5e21077a5dc12a --- /dev/null +++ b/marked/Q/T-REC-Q.1225-199709-I_PDF-E/raw.md @@ -0,0 +1,495 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1225** + +(09/97) + +SERIES Q: SWITCHING AND SIGNALLING +Intelligent Network + +--- + +**Physical plane for Intelligent Network Capability +Set 2** + +ITU-T Recommendation Q.1225 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| Interworking with Standard-A INMARSAT system | Q.1100–Q.1109 | +| Interworking with Standard-B INMARSAT system | Q.1110–Q.1149 | +| Interworking with the INMARSAT aeronautical mobile-satellite system | Q.1150–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **ITU-T RECOMMENDATION Q.1225** + +# **PHYSICAL PLANE FOR INTELLIGENT NETWORK CAPABILITY SET 2** + +## **Summary** + +This Recommendation describes the physical plane of the Intelligent Network (IN) architecture for CS-2. The physical plane identifies different Physical Entities (PEs), the allocation of functional entities to PEs, and the interfaces between the PEs. + +Companion Recommendations include the Q.120x- and Q.122x-Series Recommendations. + +## **Source** + +ITU-T Recommendation Q.1225 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|--------|---------------------------------------------------------------------|----| +| 1 | General ..... | 1 | +| 2 | Requirements and assumptions ..... | 2 | +| 2.1 | Requirements..... | 2 | +| 2.2 | Assumptions ..... | 3 | +| 3 | Physical Entities (PEs) ..... | 3 | +| 4 | Mapping requirements..... | 5 | +| 5 | Mapping the distributed functional plane to the physical plane..... | 5 | +| 5.1 | Mapping of functional entities to physical entities..... | 5 | +| 5.2 | Mapping of FE-FE relationships to PE-PE relationships..... | 6 | +| 5.3 | Selection of underlying protocol platforms..... | 7 | +| 5.3.1 | SCP-SSP interface..... | 7 | +| 5.3.2 | AD-SSP interface ..... | 8 | +| 5.3.3 | IP-SSP interface ..... | 8 | +| 5.3.4 | SN-SSP interface..... | 8 | +| 5.3.5 | SCP-IP interface..... | 8 | +| 5.3.6 | AD-IP interface ..... | 8 | +| 5.3.7 | SCP-SDP interface..... | 8 | +| 5.3.8 | User interfaces..... | 8 | +| 5.3.9 | Enhanced ISDN CPE-CUSP interface ..... | 9 | +| 5.3.10 | AD-CUSP interface..... | 10 | + + + +# Recommendation Q.1225 + +# PHYSICAL PLANE FOR INTELLIGENT NETWORK CAPABILITY SET 2 + +*(Geneva, 1997)* + +# 1 General + +This Recommendation describes the physical plane of the Intelligent Network (IN) architecture for CS-2. General IN physical plane information is contained in Recommendation Q.1205. + +The physical plane of the IN conceptual model identifies the different physical entities and the interfaces between these entities. + +The physical plane architecture should be consistent with the IN conceptual model. The IN conceptual model is a tool that can be used to design the IN architecture to meet the following main objectives: + +- service implementation independence; +- network implementation independence; +- vendor and technology independence. + +The I.130 stage 3 service description methodology may be used (which includes the functional specification of the node and detailed description of the protocol between the nodes) in developing the physical plane architecture. + +The following is the list of abbreviations used in this Recommendation: + +| | | +|----------|--------------------------------------------------| +| AD | Adjunct | +| BRI | Basic Rate Interface | +| CCAF | Call Control Agent Function | +| CCF | Call Control Function | +| CS | Capability Set | +| CUSF | Call-Unrelated Service Function | +| DSS | Digital Signalling System | +| INAP | Intelligent Network Application Protocol | +| IP | Intelligent Peripheral | +| ISDN | Integrated Services Digital Network | +| ISDN-CPE | ISDN Customer Premises Equipment | +| ISUP | ISDN User Part (Protocol) | +| NAP | Network Access Point | +| NCP | Network Control Point | +| N-ISDN | Narrow-band Integrated Services Digital Networks | +| PBX | Private Branch Exchange | +| PRI | (ISDN) Primary Rate Interface | + +| | | +|----------|---------------------------------------| +| SCCP | Signalling Connection Control Part | +| SCEF | Service Creation Environment Function | +| SCF | Service Control Function | +| SCP | Service Control Point | +| SCUAF | Service Control User Agent Function | +| SDF | Service Data Function | +| SDP | Service Data Point | +| SMF | Service Management Function | +| SMP | Service Management Point | +| SN | Service Node | +| SRF | Specialized Resource Function | +| SS No. 7 | Signalling System No. 7 | +| SSCP | Service Switching and Control Point | +| SSF | Service Switching Function | +| SSP | Service Switching Point | +| TMN | Telecommunications Management Network | + +## 2 Requirements and assumptions + +### 2.1 Requirements + +The key requirements of the physical plane architecture are as follows: + +- the functional entities in the CS-2 distributed functional plane can be mapped onto the CS-2 physical entities; however, there is no present need to describe (or map to Physical Plane) the IN Management aspects; +- one or more functional entities may be mapped onto the same physical entity; +- one functional entity cannot be split between two physical entities (i.e. the functional entity is mapped entirely within a single physical entity); +- duplicate instances of a functional entity can be mapped to different physical entities, though not to the same physical entity; +- physical entities can be grouped to form a physical architecture; +- the physical entities may offer standard interfaces; +- vendors must be able to develop physical entities based on the mapping of functional entities and the standard interfaces; +- vendors must be able to support mature technologies and new technologies as they become available; and +- the Telecommunications Management Network (TMN) represents the system or systems associated with management of IN. As such, it is not restrained to any single physical implementation but may be implemented by distributing its functionality to one or more physical entities. This requirement is reflected in Figure 1/Q.1215 by means of the "TMN Cloud". + +### 2.2 Assumptions + +The following assumptions are made for the development of the physical plane architecture: + +- The IN conceptual model is used as a tool to develop the IN physical architecture. +- Existing and new technologies can be used to develop the physical entities. +- The specification of functional entities in the distributed functional plane and standard interfaces in the physical plane support network vendor independence and service independence. +- For CS-2, a sufficient number of interfaces are identified for support of services. Service creation and OAM functions are not addressed. + +## 3 Physical Entities (PEs) + +This clause describes a selection of PEs to support IN CS-2. That selection is not intended to preclude or disallow the application of any other IN PE to support CS-2. + +### a) Service Switching Point (SSP) + +In addition to providing users with access to the network (if the SSP is a local exchange) and performing any necessary switching functionality, the SSP allows access to the set of IN capabilities. The SSP contains detection capability to detect requests for IN-based services. It also contains capabilities to communicate with other PE(s) containing a Service Control Function (SCF), such as a Service Control Point (SCP), and to respond to instructions from the other PE. Functionally, an SSP contains a Call Control Function (CCF), a Service Switching Function (SSF), and, if the SSP is a local exchange, a Call Control Agent Function (CCAF). It also may optionally contain a Service Control Function (SCF), and/or a Specialized Resource Function (SRF), and/or a Service Data Function (SDF). The SSP may provide IN-based services to users connected to subtending Network Access Points. + +### b) Network Access Point (NAP) + +A NAP is a PE that includes only the CCAF and CCF functional entities. It may also be present in the network. The NAP supports early and ubiquitous deployment of IN-based services. This NAP cannot communicate with an SCF, but it has the ability to determine when IN processing is required. It must send calls requiring IN processing to an SSP. + +### c) Service Control Point (SCP) + +The SCP contains the Service Logic Programs (SLPs) and data that are used to provide IN-based services. The SCP is connected to SSPs by a signalling network. Multiple SCPs may contain the same SLPs and data to improve service reliability and to facilitate load sharing between SCPs. Functionally, an SCP contains an SCF and it may contain an SDF. The SCP can access data in an SDP either directly or through a signalling network. The SDP may be in the same network as the SCP, or in another network. The SCP can be connected to SSPs, and optionally to IPs, through the signalling network. The SCP can also be connected to an IP via an SSP relay function. + +### d) Adjunct (AD) + +The AD is functionally equivalent to an SCP (i.e. it contains the same functional entities) but it is directly connected to an SSP. Communication between an AD and an SSP is supported by a high-speed interface. This arrangement may result in differing performance characteristics for an AD and an SCP. The application layer messages are identical in content to those carried by the signalling network to an SCP. + +An AD may be connected to more than one SSP and an SSP may be connected to more than one Adjunct. + +### **e) Intelligent Peripheral (IP)** + +The IP provides resources such as customized and concatenated voice announcements, voice recognition, and Dual Tone Multi-Frequencies (DTMF) digit collection, and contains switching matrix to connect users to these resources. The IP supports flexible information interactions between a user and the network, and may contain service-specific user interaction scripts, which allow user interactions to be grouped. Functionally, the IP contains the SRF. The IP may directly connect to one or more SSPs, and/or may connect to the signalling network. + +In the ISDN stimulus protocol environment, the IP will also provide resources such as customized and concatenated Information Display and Digit collection, out of channel, and it contains the necessary coordination and multiplexing to connect users to these resources. + +An SCP or AD can request an SSP to connect a user to a resource located in an IP that is connected to the SSP from which the service request is detected. An SCP or AD can also request the SSP to connect a user to a resource located in an IP that is connected to another SSP. + +### **f) Service Node (SN)** + +The SN can control IN-based services and engage in flexible information interactions with users. The SN communicates directly with one or more SSPs, each with a point-to-point signalling and transport connection. Functionally, the SN contains an SCF, SDF, SRF, and an SSF/CCF. This SSF/CCF is closely coupled to the SCF within the SN, and is not accessible by external SCFs. + +In a manner similar to an AD, the SCF in an SN receives messages from the SSP, executes SLPs, and sends messages to the SSP. SLPs in an SN may be developed by the same service creation environment used to develop SLPs for SCPs and ADs. The SRF in an SN enables the SN to interact with users in a manner similar to an IP. An SCF can request the SSF to connect a user to a resource located in an SN that is connected to the SSP from which the service request is detected. An SCF can also request the SSP to connect a user to a resource located in an SN that is connected to another SSP. + +### **g) Service Switching and Control Point (SSCP)** + +The SSCP is a combined SCP and SSP in a single node. Functionally, it contains an SCF, SDF, CCAF, CCF, and SSF. The connection between the SCF/SDF functions and the CCAF/CCF/SSF functions is proprietary and closely coupled, but it provides the same service capability as an SSP and SCP separately. + +This node may also contain SRF functional capabilities (i.e. SRF as an optional capability). + +The interfaces between the SSCP and other PEs are the same as the interfaces between the SSP and other PEs, and therefore will not be explicitly stated. + +### **h) Service Data Point (SDP)** + +The SDP contains the customer and network data which is accessed during the execution of a service. Functionally, the SDP contains an SDF. + +### **i) Enhanced ISDN Customer Premises Equipment (Enhanced ISDN CPE)** + +Recommendation I.112 defines the ISDN CPE as "a node that provides the functions necessary for the operation of the access protocols by the user". Functionally, the ISDN CPE can contain the SCUAF (for the bearer-unrelated interactions), the CCAF, and the IAF. + +### **j) Call-Unrelated Service Point (CUSP)** + +The CUSP provides a point of protocol interworking for Call Unrelated User Interaction. It establishes and releases call-unrelated associations between the user and the SCP or AD, carries out protocol adaptation between ROSE APDUs and TCAP transactions, and monitors the integrity of the association. + +## **4 Mapping requirements** + +- Physical plane architecture requirements listed in 2.1 should be met. +- Functional entities should be mapped to physical entities in a manner which will support the identified benchmark CS-2 services. +- Functional entity to physical entity mapping must allow efficient implementation in existing physical entities. +- Functional entity to physical entity mapping must allow for standard communications between network functions via service independent interfaces. + +## **5 Mapping the distributed functional plane to the physical plane** + +### **5.1 Mapping of functional entities to physical entities** + +This subclause gives a mapping of functional entities into physical entities for CS-2, and describes the reference points between the PEs. In so doing, an appropriate distribution of functionality for CS-2 is identified, and functional interfaces suitable for standardization are highlighted. The PEs described in this subclause are for illustrative purposes only, and do not imply the only possible mapping of functionality for CS-2. + +This subclause describes a flexible physical architecture made up of several PEs. Each PE contains one or more functional entities, which define its IN functionality. PEs included in the physical architecture shown in Figure 1 are Service Switching Point (SSP), Network Access Point (NAP), Service Control Point (SCP), Intelligent Peripheral (IP), Adjunct (AD), Service Switching and Control Point (SSCP), Service Data Point (SDP), ISDN Customer Premises Equipment (ISDN CPE), and Services Node (SN). + +Typical scenarios of functional entity mapping to physical entity are shown in Table 1. + +**Table 1/Q.1225 – Typical scenarios of FE to PE mapping** + +| PEs | FEs | | | | | | | | +|-------------|-------------|-----------------|------|-------|-----|------|-----|-----| +| | SCF | SSF-CCF | CCAF | SCUAF | SDF | CUSF | SRF | IAF | +| SCP | C | – | – | – | O | – | – | – | +| SN | C | C | O | – | C | C | C | – | +| AD | C | – | – | – | C | – | – | – | +| SSP | O | C | O | – | O | C | O | – | +| IP | – | – | – | – | – | – | C | – | +| SDP | – | – | – | – | C | – | – | – | +| SSCP | C | C | – | – | C | – | O | – | +| NAP | – | C
(CCF only) | – | – | – | – | – | – | +| ISDN
CPE | – | – | O | C | – | – | – | O | +| CUSP | – | C
(CCF only) | – | – | – | C | – | – | +| C | Core | | | | | | | | +| O | Optional | | | | | | | | +| – | Not allowed | | | | | | | | + +There is no intention that the table should disallow any other combination of functional entities that would result in a PE not shown in the table. + +The above mappings are shown in Figure 1. Each PE has certain functional entities mapped into it. The solid lines on the figure show transport paths that may exist between the PEs, and the dotted lines show signalling paths that can carry application layer messages for IN-based services. + +### 5.2 Mapping of FE-FE relationships to PE-PE relationships + +The FE-FE interfaces that fall within the scope of CS-2 are: + +- 1) SSF-SCF; +- 2) SCF-SDF; +- 3) SCF-SSF; +- 4) SDF-SDF; +- 5) CUSF-SCF +- 6) SCUAF-CUSF; and +- 7) SCF-SRF. + +A mapping to the PE-PE interfaces is provided in Table 2. + +Table 2 is not meant to be an exhaustive list of all possible PE-PE relationships that may be covered by the CS-2 Recommendations. + +**Table 2/Q.1225 – FE-FE relationships to PE-PE relationships** + +| FE-FE | PE-PE | +|--------------|-------------------------------| +| SSF-SCF | SSP-SCP
SSP-AD
SSP-SN | +| SCF-SDF | SSP-SCP
SCP-SDP | +| SCF-SRF | SCP-IP
SCP-SSP-IP
AD-IP | +| IAF-SCF | ISDN CPE-SCP
(via Switch) | +| SCUAF-CUSF | ISDN CPE-SSP | +| SDF-SDF | SDP-SDP | +| SCF-SCF | SCP-SCP | + +### **5.3 Selection of underlying protocol platforms** + +This subclause describes the candidate interfaces for CS-2 between the elements of the physical architecture. The interfaces are identified below. + +- SCP-SSP; +- AD-SSP; +- IP-SSP; +- SN-SSP; +- SCP-IP; +- ISDN CPE-SSP; +- SCP-SCP; +- SDP-SDP; +- AD-IP; and +- SCP-SDP. + +Existing lower-layer protocols are proposed for these candidate interfaces to carry the application layer messages required by IN-based services. As such, the focus of the standardization effort for CS-2 is on the application layer protocols. At the application layer, the message sent that the different interfaces carry should reflect the same semantic content, even though the application layer messages may be encoded or formatted differently. For example, the messages between the SSF in an SSP and the SCF in an SCP, AD or SN should contain the same information. The following subclauses give some proposed protocols for use on these interfaces. + +#### **5.3.1 SCP-SSP interface** + +The proposed underlying protocol platform for the interface between an SCP and an SSP is Transaction Capabilities Application Part (TCAP) on Signalling Connection Control Part (SCCP)/Message Transfer Part (MTP) of SS No. 7. + +#### **5.3.2 AD-SSP interface** + +The proposed underlying protocol platform for the AD-SSP interface is TCAP. The physical interface has not been specified, but a number of alternative standard protocols could be used. + +#### **5.3.3 IP-SSP interface** + +This interface is used for communications between an IP and an SSP as well as for communication between an IP and an SCP which is being relayed through an SSP. + +The proposed underlying protocol platform for the interface between an IP and an SSP is ISDN Basic Rate Interface (BRI), Primary Rate Interface (PRI) (or both), or SS No. 7. + +If a BRI or PRI is used, the ISDN D-channel connecting an IP to an SSP carries application layer information between an SCF and an SRF, and supports the setup of B-channel connections to the IP. Information passed from an SCF to an SRF (e.g. announcement number and number of digits to collect) and vice versa (e.g. collected information and billing measurements) is embedded in the facility information element. The facility information element can be carried by some Q.931 messages, such as SETUP and DISCONNECT. The facility information element can also be carried by the FACILITY message of Recommendation Q.931. This possibility provides for the flexibility to convey application layer information without affecting the call connection establishment. + +#### **5.3.4 SN-SSP interface** + +The proposed underlying protocol platform for the interface between an SN and an SSP is ISDN Basic Rate Interface (BRI), Primary Rate Interface (PRI) (or both). An SN and an SSP exchange application layer messages over an ISDN D-channel using the common element procedures of Recommendation Q.932. This communication may occur on a separate D-channel from the channel that carries the common element procedure messages. Figure 1 shows the case where these channels are separate. + +#### **5.3.5 SCP-IP interface** + +The proposed underlying protocol platform for an interface between an SCP and an IP is Transaction Capabilities Application Part (TCAP) on signalling connection control part (SCCP)/MTP of SS No. 7. + +#### **5.3.6 AD-IP interface** + +The proposed underlying protocol platform between an AD and an IP is TCAP. The physical interface has not been specified, but a number of alternative standard protocols could be used. + +#### **5.3.7 SCP-SDP interface** + +The proposed underlying protocol platform for the interface between an SCP and an SDP is Transaction Capabilities Application Part (TCAP) in Signalling Connection Control Part (SCCP)/MTP of SS No. 7. For SDPs outside the network (e.g. credit card validation database at credit card company) an interworking unit can be used which is inside the network and performs translation of SS No. 7 TCAP to a public or private data transfer protocol (e.g. X.25). + +#### **5.3.8 User interfaces** + +A user is an entity external to the IN that uses IN capabilities. IN users may employ the access interfaces described below to invoke various IN service capabilities. For example, users can affect the routing of a call, send and receive information from the network, screen calls, and update service parameters. Users are served by existing network interfaces. + +It is important to ensure that IN should continue to support existing services and capabilities. In addition, the current restrictions imposed by each of the interface technologies described below must be considered when deploying IN-based services. For example, calling party information may or may not be available at a given interface and, therefore, may or may not be provided to the SCF. + +End users use analogue interface signalling, or ISDN access signalling arrangements. IN user-network interactions include providing stimuli, such as off-hook or DTMF digit signalling, which determine further IN action. + +Out-of-band (i.e. D-channel) signalling provides ISDN users with additional capabilities for accessing potential IN-based services. When originating a call, an ISDN user identifies the bearer capability to be associated with the call. IN service logic can use this information to determine how the call should be handled (e.g. how to route the call). + +The interface between the ISDN CPE and SSP is supported by DSS 1 protocols. + +NOTE – The interface between the ISDN CPE and NAP is left for further study. + +#### **5.3.9 Enhanced ISDN CPE-CUSP interface** + +The CPE protocol based on Generic or Flexible Functional Protocols can make use of extensions to use ROSE APDUs to interact with the Call-Unrelated Service Point in the Out Channel Call-Unrelated User Interaction mode. + +In the case where the Functional Protocol is provided from a Smart Card or PBX, user interaction may exist, which utilizes the CUSP to use an association between the CPE and the SCP. In principle, the CUSP is required to map the ROSE APDU into the TCAP/SCCP protocol elements. The SCUAF and IAF are examples of CPE intelligence, which, for the purpose of Physical Plane mapping may be seen as equivalent options. + +#### 5.3.10 AD-CUSP interface + +![Diagram of Physical plane architecture for CS-2 showing various network entities and their interconnections.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +Interfaces: + SCP-SSP      SCP-SDP + AD-SSP      Enhanced ISDN +               CPE-CUSP + IP-SSP       AD-IP + SN-SSP      CUSP-AD + +The diagram illustrates the physical plane architecture for CS-2. At the top, an SCP (Service Control Point) containing SCF (Service Control Function) and SDF (Service Data Function) and an SDP (Service Data Point) containing SDF are connected to a central 'SS No. 7 network' oval. The SDP has a dashed line pointing to 'To other SCPs and/or SDPs in this or another network'. Below the SS No. 7 network, several entities are connected via dashed lines (signalling) and solid lines (transport): + +- An IP (Intelligent Peripheral) containing SRF (Specialized Resource Function). +- A SN (Service Node) containing CUSF (Call-Unrelated Service Function), SCF, CCF (Call Control Function), SSF (Service Switching Function), SDF, and SRF. +- An AD (Adjunct) containing SCF and SDF. +- An SSP (Service Switching Point) containing SCFa), SRF, CUSF, CCF, SSF, SDFa), and CCAF (Call Control Agent Function). It is connected to a laptop icon. +- A NAP (Network Access Point) containing CCF and CCAF, connected to a laptop icon. +- An ISDN CPE (ISDN Customer Premises Equipment) containing IAF (ISDN Access Function), SCUAF (Service Control User Agent Function), and CCAF. +- A CUSP (Call-Unrelated Service Point) containing CUSF and CCF. + +All these entities are interconnected by dashed lines representing signalling paths. A large dashed box at the bottom right, labeled 'Telecommunications Management Network (TMN)', has arrows pointing 'To all PEs' (Physical Entities). A legend at the bottom left defines the line types: solid for Transport, dashed for Signalling, and oval for Optional FE. A footnote 'a) An SSCP PE includes the SCF and SDF FEs as core elements.' is provided. A reference code 'T1185420-97' is in the bottom right corner. + +a) An SSCP PE includes the SCF and SDF FEs as core elements. + +— Transport + - - - Signalling + ( ) Optional FE + +**Physical Entities (PEs)** + AD      Adjunct + IP      Intelligent Peripheral + SSP    Service Switching Point + SCP    Service Control Point + SN     Service Node + NAP    Network Access Point + SDP    Service Data Point + SSCP   Service Switching and Control Point + ISDN CPE ISDN Customer Premises Equipment + CUSP   Call-Unrelated Service Point + +**Functional Entities (FEs)** + CCF    Call Control Function + CCAF   Call Control Agent Function + SCF    Service Control Function + SDF    Service Data Function + SRF    Specialized Resource Function + SSF    Service Switching Function + CUSF   Call-Unrelated Service Function + SCUAF   Service Control User Agent Function + +To all PEs + Telecommunications Management Network (TMN) + T1185420-97 + +Diagram of Physical plane architecture for CS-2 showing various network entities and their interconnections. + +**Figure 1/Q.1225 – Physical plane architecture for CS-2** + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1601-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1601-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d91127678c1d2a02944ce8a3b6689fc8594d1629 --- /dev/null +++ b/marked/Q/T-REC-Q.1601-199912-I_PDF-E/raw.md @@ -0,0 +1,2048 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1601** + +(12/1999) + +SERIES Q: SWITCHING AND SIGNALLING +Intelligent Network + +--- + +**Signalling System No. 7 – Interaction between +N-ISDN and INAP CS-2** + +ITU-T Recommendation Q.1601 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Signalling System No. 7 – Interaction between N-ISDN and INAP CS-2** + +## **Summary** + +This ITU-T Recommendation specifies procedures in order to provide interaction between N-ISDN and INAP CS-2/CS-3, i.e. to support IN services in an ISDN environment. This ITU-T Recommendation only considers the case where the SSP is located at a transit level. As a consequence, this could lead to limitations for ISDN supplementary services. + +The interaction between other signalling systems and INAP can be found by consulting the relevant interworking Recommendation to the N-ISDN in combination with the N-ISDN/INAP interaction Recommendation. + +## **Source** + +ITU-T Recommendation Q.1601 was prepared by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 3 December 1999. + +## **Keywords** + +INAP, ISUP, SS7, SSP. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|--------|----------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | ITU-T terms and definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Description..... | 4 | +| 6.1 | Establishment of Bearer related connections..... | 4 | +| 6.2 | Establishment of bearer unrelated connections..... | 10 | +| 7 | Operational requirements..... | 10 | +| 8 | Coding requirements..... | 10 | +| 8.1 | Messages..... | 10 | +| 8.2 | Parameters..... | 10 | +| 8.2.1 | Call diversion treatment indicators parameter..... | 10 | +| 8.2.2 | Called IN number parameter..... | 10 | +| 8.2.3 | Call offering treatment indicators parameter..... | 10 | +| 8.2.4 | Charged party identification parameter ..... | 10 | +| 8.2.5 | Conference treatment indicators parameter ..... | 10 | +| 8.2.6 | Correlation id parameter ..... | 11 | +| 8.2.7 | Display information parameter ..... | 11 | +| 8.2.8 | SCF id parameter ..... | 11 | +| 8.2.9 | UID action indicators parameter..... | 11 | +| 8.2.10 | UID capability indicators parameter..... | 11 | +| 8.2.11 | Original called IN number parameter ..... | 11 | +| 9 | State definitions ..... | 11 | +| 10 | Signalling procedures..... | 11 | +| 10.1 | Bearer related connections ..... | 11 | +| 10.1.1 | IN basic call ..... | 11 | +| 10.1.2 | IN call with SCP request to collect further digits ..... | 17 | +| 10.1.3 | Detection Point processing ..... | 18 | +| 10.1.4 | Setup of an IN call to destination B..... | 20 | +| 10.1.5 | User interactive dialogue (in-band) ..... | 23 | +| 10.1.6 | Call gapping..... | 28 | +| 10.1.7 | Service filtering ..... | 29 | +| 10.1.8 | SCP initiated call ..... | 29 | +| 10.1.9 | GVNS ..... | 31 | + +| | Page | +|---------------------------------------------------------------------------------------------------------------------------|-------------| +| 10.1.10 Actions to be performed in local exchanges..... | 32 | +| 10.1.11 Actions in an intermediate exchange..... | 33 | +| 10.1.12 Actions in international gateway exchanges..... | 34 | +| 10.2 Bearer unrelated connections..... | 34 | +| 11 Interaction with other networks ..... | 34 | +| 12 Interaction between IN basic call and ISDN supplementary services..... | 34 | +| 12.1 Call diversion..... | 36 | +| 12.1.1 Actions in the service switching point..... | 36 | +| 12.1.2 Actions in the destination local exchange ..... | 36 | +| 12.2 Calling line identification presentation/restriction..... | 37 | +| 12.2.1 Actions in the service switching point..... | 37 | +| 12.3 Completion of calls service..... | 37 | +| 12.3.1 Completion of calls to busy subscriber..... | 37 | +| 12.3.2 Completion of calls on no reply..... | 37 | +| 12.4 Conference ..... | 37 | +| 12.4.1 Actions in the originating or destination local exchange..... | 37 | +| 12.5 Connected line identification presentation/restriction ..... | 37 | +| 12.5.1 Actions in the service switching point..... | 37 | +| 12.6 Explicit call transfer..... | 38 | +| 12.6.1 Actions in the service switching point..... | 38 | +| 12.7 Malicious call identification ..... | 38 | +| 12.7.1 Actions in the service switching point..... | 38 | +| 12.7.2 Actions in the destination local exchange ..... | 38 | +| 12.8 Three party ..... | 39 | +| 12.8.1 Actions in the originating or destination local exchange..... | 39 | +| 13 Interactions between IN services ..... | 39 | +| 14 Parameter values (timers) ..... | 39 | +| Annex A – Signalling flows..... | 40 | +| Appendix I – Coding of the compatibility information for the parameters ..... | 46 | +| Appendix II – Contents of the INAP serviceInteractionIndicatorsTwo..... | 47 | +| Appendix III – Limitations for ISUP basic call procedures and supplementary services for different types of IN calls..... | 49 | + +# **Signalling System No. 7 – Interaction between N-ISDN and INAP CS-2** + +# 1 Scope + +This ITU-T Recommendation specifies the interaction between the N-ISDN and INAP CS-2/CS-3. + +For the purpose of this ITU-T Recommendation the interface INAP CS-2 between SSP and SCP is regarded as being an intranetwork interface. + +The following topics being part of INAP CS-3 are considered in addition. + +- "Carrier" parameter on INAP in the InitialDP and InitiateCallAttempt operation. +- Connected line identification restriction for the called IN number. +- Setting of the "charge indicator". +- Mapping of the calling geodetic location parameter. + +The interaction between other signalling systems and INAP can be found by consulting the relevant interworking Recommendation to the N-ISDN in combination with the N-ISDN/INAP interaction Recommendation. + +This ITU-T Recommendation specifies procedures in order to provide interaction between N-ISDN and INAP, i.e. to support IN services in an ISDN environment. In addition new protocol elements for the ISUP are defined in this ITU-T Recommendation in order to satisfy IN specific requirements. Based on the protocol inherent compatibility mechanism a stepwise upgrade of the ISUP functionality is possible. However, the new function is only available for an IN call, if supported in any of the affected exchanges. + +This ITU-T Recommendation only considers the case where the SSP is located at a transit level. As a consequence this could lead to limitations for ISDN supplementary services. + +This ITU-T Recommendation does not specify enhancements to the DSS1 protocol, which may be needed due to additional ISUP functions or IN requirements, respectively. + +The main subjects of this interaction specification are the following: + +- description of specific call control functions for IN calls; +- impacts on the ISUP basic call and the ISDN supplementary services for IN calls; +- enhancement of the ISUP protocol due to IN specific requirements. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN.* +- [2] ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs.* +- [3] ITU-T Recommendation I.210 (1993), *Principles of telecommunication services supported by an ISDN and the means to describe them.* + +- [4] ITU-T Recommendation Q.1224 (1997), *Distributed functional plane for intelligent network Capability Set 2.* +- [5] ITU-T Recommendation Q.1228 (1997), *Interface Recommendation for intelligent network Capability Set 2.* +- [6] ITU-T Recommendation Q.1290 (1993), *Glossary of terms used in the definition of intelligent networks.* +- [7] ITU-T Recommendation Q.731 (1993), *Stage 3 description for number identification supplementary services using Signalling System No. 7.* +- [8] ITU-T Recommendation Q.732.2-5 (1999), *Stage 3 description for call offering supplementary services using Signalling System No. 7: Call diversion services.* +- [9] ITU-T Recommendation Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes.* +- [10] ITU-T Recommendation Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures.* +- [11] ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control.* + +# 3 ITU-T terms and definitions + +This Recommendation defines the following terms: + +- **Integrated Services Digital Network (ISDN)**: see ITU-T Recommendation I.112 [2]. +- **Service; telecommunication service**: see ITU-T Recommendation I.112 [2]. +- **Supplementary service**: see ITU-T Recommendation I.210 [3]. +- **Call Control Function (CCF)**: see 3.3/Q.1224 [4]. +- **Service Control Function (SCF)**: see 3.3/Q.1224 [4]. +- **Service Switching Function (SSF)**: see 3.3/Q.1224 [4]. +- **Specialized Resource Function (SRF)**: see 3.3/Q.1224 [4]. + +# 4 Abbreviations + +This ITU-T Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------------------| +| ACM | Address Complete Message (ISUP) | +| ANM | Answer Message (ISUP) | +| ATP | Access Transport parameter (ISUP) | +| CCSS | Call completion Service Setup | +| CON | Connect Message (ISUP) | +| CPG | Call Progress Message (ISUP) | +| DLE | Destination Local Exchange | +| DP | Detection Point | +| DSS1 | Digital Subscriber Signalling System No. 1 | +| EDP-N | Event Detection Point – Notification | +| EDP-R | Event Detection Point – Request | + +| | | +|------|------------------------------------------| +| FAR | Facility Request Message (ISUP) | +| FOT | Forward Transfer Message (ISUP) | +| FRJ | Facility Reject (ISUP) | +| GVNS | Global virtual network service | +| IAM | Initial Address Message (ISUP) | +| IDR | Identification Request Message (ISUP) | +| IE | Information element | +| IN | Intelligent Network | +| INAP | Intelligent Network Application Protocol | +| IP | Intelligent Peripheral | +| IRS | Identification Response Message (ISUP) | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| OLE | Originating Local Exchange | +| PRI | Pre-release Information message (ISUP) | +| REL | Release Message (ISUP) | +| RES | Resume Message (ISUP) | +| RLC | Release Complete Message (ISUP) | +| SCP | Service Control Point | +| SGM | Segmentation Message (ISUP) | +| SS | Signalling System | +| SSP | Service Switching Point | +| SUS | Suspend Message (ISUP) | +| TMR | Transmission Medium Requirement | +| TNS | Transit Network Selection (ISUP) | + +# 5 Conventions + +The name of each element of the following class of terms is capitalized and capital letter within that term can possibly occur: + +- operations. + +Example: ContinueWithArgument operation. + +The name of each element of the following class of terms is not capitalized and capital letter within that term can possibly occur: + +- parameters within operations. + +Example: calledPartyNumber. + +# 6 Description + +## 6.1 Establishment of Bearer related connections + +ITU-T Recommendation Q.1224 [4] provides a distributed functional plane architecture for IN Capability Set 2 (CS-2). Interactions between the following functional entities (FEs) are relevant for this ITU-T Recommendation: + +- Call Control Function (CCF). +- Service Switching Function (SSF). +- Service Control Function (SCF). +- Specialized Resource Function (SRF). + +The functional entities can be implemented in one or more network elements, called physical entities. The service control point (SCP) is the physical entity in the intelligent network, that implements the SCF. The CCF and SSF are realized in the service switching point (SSP) and the SRF is realized in the intelligent peripheral (IP). + +The SSF contains the capabilities beyond those that are needed for basic call control. Consequently, this ITU-T Recommendation concentrates on the actions that are performed in the CCF. + +Figure 1 illustrates in a simplified manner a signalling configuration which is to be considered in this ITU-T Recommendation. In the configuration it is assumed that SRF support is not needed. The network signalling system used for call setup is the ITU-T ISUP [10]. The interface between SSF and SCF is the ITU-T INAP [5]. + +![Diagram of signalling configuration for an IN call without SRF support. It shows a Service Control Point (SCP) containing a Service Control Function (SCF) connected via an INAP interface to a Service Switching Point (SSP). The SSP contains a Service Switching Function (SSF) and a Call Control Function (CCF). The CCF is connected via an ISUP interface to an Access Signalling OLE (Office Line Equipment) on the left, which is connected to a telephone. The CCF is also connected via an ISUP interface to an Access Signalling DLE (Data Link Equipment) on the right, which is connected to another telephone. The diagram is labeled T11103720-99.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The diagram illustrates a signalling configuration for an IN call without SRF support. At the top, a box labeled 'SCP' contains a smaller box labeled 'SCF'. A vertical line labeled 'INAP' connects the 'SCF' box to a box below it labeled 'SSP'. The 'SSP' box contains two stacked boxes: 'SSF' on top and 'CCF' on the bottom. From the 'CCF' box, a horizontal line labeled 'ISUP' extends to the left to a box labeled 'OLE'. From the 'OLE' box, a dashed line labeled 'Access Signalling' connects to a telephone icon. Another horizontal line labeled 'ISUP' extends from the 'CCF' box to the right to a box labeled 'DLE'. From the 'DLE' box, a dashed line labeled 'Access Signalling' connects to another telephone icon. The text 'T11103720-99' is located in the bottom right corner of the diagram area. + +Diagram of signalling configuration for an IN call without SRF support. It shows a Service Control Point (SCP) containing a Service Control Function (SCF) connected via an INAP interface to a Service Switching Point (SSP). The SSP contains a Service Switching Function (SSF) and a Call Control Function (CCF). The CCF is connected via an ISUP interface to an Access Signalling OLE (Office Line Equipment) on the left, which is connected to a telephone. The CCF is also connected via an ISUP interface to an Access Signalling DLE (Data Link Equipment) on the right, which is connected to another telephone. The diagram is labeled T11103720-99. + +Figure 1/Q.1601 – Signalling configuration for an IN call without SRF support + +The interaction between ISUP and INAP takes place in the CCF and SSF. The following main subjects have to be considered in this area: + +- detection point processing in the CCF; +- receipt of INAP operations in the SSF. + +### Detection point processing + +The provision of detection points (DPs) is required in the ISUP basic call handling in order to access IN functionality and to allow IN service logic influence the processing of IN calls. The detection points (DPs) indicate points in call (PICs) at which transfer of control can occur. If a DP is recognized an operation from the SSF to the SCF will be sent. Thus the communication towards the SCP is performed. The DPs defined in [4] are listed in Table 1. + +The column "Support" indicates whether the DP is supported with the ITU-T ISUP [10]. + +**Table 1/Q.1601 – List of Detection Points** + +| Detection Points for the originating side | Support | Detection Points for the terminating side | Support | +|--------------------------------------------------|-------------------|--------------------------------------------------|-------------------| +| OA
Origination_Attempt | No impact on ISUP | TA
Terminating_Attempt | No impact on ISUP | +| OAA
Origination_Attempt_Authorized | No impact on ISUP | TAA
Terminating_Attempt_Authorized | No impact on ISUP | +| CI
Collected_Information | Yes | | | +| AI
Analysed_Information | Yes | | | +| RSF
Route_Select_Failure | Yes | | | +| OCPB
O_Called_Party_Busy | Yes | TB
T_Busy | Yes | +| | | FSA
Facility_Selected_and_Available | For further study | +| OTS
O_Term_Seized | Yes | CA
Call_Accepted | Yes | +| ONA
O_No_Answer | Yes | TNA
T_No_Answer | Yes | +| OAns
O_Answer | Yes | TAns
T_Answer | Yes | +| OMC
O_Mid_Call | For further study | TMC
T_Mid_Call | For further study | +| OS
O_Suspend | Yes | TS
T_Suspend | Yes | +| ORA
O_Re_Answer | Yes | TRA
T_Re_Answer | Yes | +| OD
O_Disconnect | Yes | TD
T_Disconnect | Yes | +| OAb
O_Abandon | Yes | Tab
T_Abandon | Yes | + +### Receipt of INAP operations + +Table 2 below lists the INAP operations with direction SCF-SSF and indicates which operation will influence the ISUP call handling. + +**Table 2/Q.1601 – INAP operations (direction: SCF-SSF)** + +| Operation | Influence on ISUP call handling | Reference | +|------------------------------------------|----------------------------------------|-----------------------------------------------------------------------| +| ActivateServiceFiltering | Yes | Subclause 10.1.7 (Service filtering) | +| ActivityTest | No | | +| AnalyseInformation | For further study (Note) | | +| ApplyCharging | No | | +| AuthorizeTermination | For further study (Note) | | +| CallGap | Yes | Subclause 10.1.6 (Call gapping) | +| CallInformationRequest | No | | +| Cancel | No | | +| CancelStatusReportRequest | For further study (Note) | | +| CollectInformation | Yes | Subclause 10.1.2 (IN call with SCP request to collect further digits) | +| Connect | Yes | Subclause 10.1.1.1.1.1 (Connect operation) | +| Continue | Yes | Subclause 10.1.1.1.1.2 (Continue operation) | +| ContinueWithArgument | Yes | Subclause 10.1.1.1.1.3 (ContinueWithArgument operation) | +| ConnectToResource | Yes | Subclause 10.1.5.1 (SSP supports requested IP capabilities) | +| CreateCallSegmentAssociation | No | | +| DisconnectForwardConnection | Yes | Subclause 10.1.5.2 (Assist method – procedure in the initiating SSP) | +| DisconnectForwardConnection WithArgument | Yes | Subclause 10.1.5.2 (Assist method – procedure in the initiating SSP) | +| DisconnectLeg | For further study (Note) | | +| EstablishTemporaryConnection | Yes | Subclause 10.1.5.2 (Assist method – procedure in the initiating SSP) | +| FurnishChargingInformation | No | | +| HoldCallInNetwork | For further study (Note) | | +| InitiateCallAttempt | Yes | Subclause 10.1.8 (SCP initiated call) | +| ManageTriggerData | No | | +| MergeCallSegments | For further study (Note) | | +| MoveCallSegments | For further study (Note) | | +| MoveLeg | For further study (Note) | | + +**Table 2/Q.1601 – INAP operations (direction: SCF-SSF) (concluded)** + +| Operation | Influence on ISUP call handling | Reference | +|-----------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------| +| Reconnect | For further study (Note) | | +| ReleaseCall | Yes | Subclause 10.1.1.4 (ReleaseCall operation) | +| RequestCurrentStatusReport | For further study (Note) | | +| RequestEveryStatusChangeReport | For further study (Note) | | +| RequestFirstStatusMatchReport | For further study (Note) | | +| RequestNotificationChargingEvent | Yes | The treatment is national network specific and not described further within this ITU-T Recommendation | +| RequestReportBCSMEVENT | Yes | Subclause 10.1.3 (Detection Point processing) | +| RequestReportFacilityEvent | No | | +| RequestReportUTSI | No | | +| ResetTimer | No | | +| SelectFacility | For further study (Note) | | +| SendFacilityInformation | No | | +| SelectRoute | For further study (Note) | | +| SendSTUI | For further study (Note) | | +| SplitLeg | For further study (Note) | | +| SendChargingInformation | Yes | Subclause 10.1.1.1.2 (SendChargingInformation operation) | +| NOTE – More information can be found in references [4] and [5]. | | | + +### **Support of the SCF-SRF relationship** + +In the ITU-T INAP standard a number of scenarios for support of the SCF, SSF, and SRF functional entities as physical entities have been identified. The scenarios differ in the method to support the SCF-SRF relationship and are explained in Table 1 and Figures 2 to 6 of the ITU-T INAP [5]. Table 3 below summarizes these configurations and indicates whether the scenario can be supported with the current ISDN User Part Version [10] and the extensions made in this ITU-T Recommendation. + +**Table 3/Q.1601 – Scenarios for support of the SCF-SRF relationship** + +| Type of signalling system between SSF/CCF and SRF | Method to support SCF-SRF relationship | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| | Direct TCAP link | Relay via SSP | +| ISUP | Supported
(see Figure 3) | Not supported (Note)
NOTE – Transport of additional information in ISUP would be needed. | +| DSS1 (Note) or implementation dependent
NOTE – Extensions to the DSS1 protocol may be required, but this is outside the scope of this ITU-T Recommendation. | Supported (Note)
NOTE – The scenarios can be supported from the viewpoint of this ITU-T Recommendation. No additional information and no additional procedures are required than for the ISUP as signalling system between SSF/CCF and SRF. | | + +The following figures provide in a simplified manner some signalling configurations for IN calls needing an IP for user interaction. The figures are only included to ease the understanding and should not be seen as an exhaustive representation of the various physical scenarios. + +In Figure 2 the IP is either integrated into the SSP, or directly attached to the SSP, that is interacting with the SCP. Whether the SRF-SCF INAP operations are relayed via the SSP or are directly exchanged between IP and SCP is not relevant for this ITU-T Recommendation. However, in the figure only the scenario is shown, where a relay via SSP is applied. The procedure for this scenario is described in 10.1.5.1 (SSP supports requested IP capabilities) and a typical arrow diagram is given in Figure A.3. + +![Diagram showing the connection to integrated or external IP with SSP relay of IP operations. It illustrates the flow of signalling from an OLE (Access Signalling) through an SSP (containing SSF and CCF) to an SCP (containing SCF) and an IP (containing SRF).](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates a signalling configuration. On the left, an icon of a telephone handset is labeled 'Access Signalling', connected to a box labeled 'OLE'. A solid line labeled 'ISUP' connects the 'OLE' box to a large box labeled 'SSP'. Inside the 'SSP' box, there are two stacked boxes: 'SSF' on top and 'CCF' on the bottom. A solid line labeled 'INAP' connects the 'SSF' box to a box labeled 'SCP' above it. Inside the 'SCP' box, there is a box labeled 'SCF'. A dashed line labeled 'DSS1 or implementation dependent interface' connects the 'CCF' box in the 'SSP' to a box labeled 'IP' on the right. Inside the 'IP' box, there is a box labeled 'SRF'. A small text 'T11103730-99' is in the bottom right corner. + +Diagram showing the connection to integrated or external IP with SSP relay of IP operations. It illustrates the flow of signalling from an OLE (Access Signalling) through an SSP (containing SSF and CCF) to an SCP (containing SCF) and an IP (containing SRF). + +**Figure 2/Q.1601 – Connection to integrated or external IP with SSP relay of IP operations** + +In Figure 3 the IP is connected to the SSP via ISUP. The SRF-SCF INAP operations are directly exchanged between IP and SCP. + +On completion of the user interaction, control is returned to the initiating SSP. This procedure is called the "Assist" method. The procedure for this scenario is described in 10.1.5.2 (Assist method – procedure in the initiating SSP). The procedure between the SCP and the IP has no impact on the ISUP protocol and is outside the scope of this ITU-T Recommendation. More information can be found in [5]. A typical arrow diagram is given in Figure A.5. + +![Diagram of External IP connected via ISUP; direct TCAP link between SRF and SCF ('Assist' method).](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +The diagram illustrates a network architecture for the "Assist" method. On the left, a telephone icon is connected to an "OLE" (Office Line Equipment) block via a dashed line labeled "Access Signalling". The "OLE" block is connected to an "SSP" (Service Switching Point) block via a solid line labeled "ISUP". The "SSP" block contains two internal components: "SSF" (Service Switching Function) and "CCF" (Control Center Function). The "SSF" is connected to an "SCP" (Service Control Point) block above it via a solid line labeled "INAP". The "CCF" is connected to an "IP" (Intelligent Peripheral) block to the right via a solid line labeled "ISUP". The "IP" block contains an "SRF" (Service Resource Function) component. A solid line labeled "INAP" connects the "SRF" to the "SCF" (Service Control Function) component inside the "SCP" block. The reference code "T11103740-99" is located at the bottom right of the diagram. + +Diagram of External IP connected via ISUP; direct TCAP link between SRF and SCF ('Assist' method). + +**Figure 3/Q.1601 – External IP connected via ISUP; direct TCAP link between SRF and SCF ("Assist" method)** + +NOTE – This method may be used in some networks. However, problems are identified regarding network integrity aspects and standardized solutions of the ISUP signalling for this type of interface. + +In Figure 4 the IP is integrated into another SSP (assisting SSP), than the one that is interacting with the SCP (initiating SSP). Whether the SRF-SCF INAP operations are relayed via the SSP or are directly exchanged between IP and SCP is not relevant for this ITU-T Recommendation. However, in the figure only the scenario is shown, where a relay via SSP is applied. + +On completion of the user interaction, control is returned to the initiating SSP. This procedure is called the "Assist" method. The procedure for this scenario is described in 10.1.5.2 (Assist method – procedure in the initiating SSP) and 10.1.5.4 (Assist/Hand-off method – procedure in the assisting SSP). Typical arrow diagrams are given in Figures A.5 and A.6. + +If the control of the call is retained in the assisting SSP, the "Hand-off" method is applied. This scenario is not explicitly shown in a figure. The procedure for this scenario is described in 10.1.5.3 (Hand-off method – procedure in the initiating SSP) and a typical arrow diagram is given in Figure A.7. + +![Diagram of Figure 4/Q.1601 showing the 'Assist' method for IP attachment to an assisting SSP. The diagram shows an OLE (Office Line Equipment) connected via Access Signalling to an SSP. The SSP contains SSF and CCF components. The CCF is connected to another SSP via ISUP. This second SSP also contains SSF and CCF components. The CCF of the second SSP is connected to an IP (IP) via a DSS1 or implement. dependent interface. The IP is connected to an SRF (Service Resource Function). The first SSP's CCF is connected to an SCP (Service Control Point) via INAP. The SCP contains an SCF (Service Control Function) component. The SCF is connected to the second SSP's CCF via INAP. The diagram is labeled T11103750-99.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Diagram of Figure 4/Q.1601 showing the 'Assist' method for IP attachment to an assisting SSP. The diagram shows an OLE (Office Line Equipment) connected via Access Signalling to an SSP. The SSP contains SSF and CCF components. The CCF is connected to another SSP via ISUP. This second SSP also contains SSF and CCF components. The CCF of the second SSP is connected to an IP (IP) via a DSS1 or implement. dependent interface. The IP is connected to an SRF (Service Resource Function). The first SSP's CCF is connected to an SCP (Service Control Point) via INAP. The SCP contains an SCF (Service Control Function) component. The SCF is connected to the second SSP's CCF via INAP. The diagram is labeled T11103750-99. + +Figure 4/Q.1601 – IP attached to an assisting SSP ("Assist" method) + +## 6.2 Establishment of bearer unrelated connections + +For further study. + +# 7 Operational requirements + +Not applicable. + +# 8 Coding requirements + +## 8.1 Messages + +None. + +## 8.2 Parameters + +### 8.2.1 Call diversion treatment indicators parameter + +The format of the call diversion treatment indicators parameter is defined in Q.763 [9]. + +### 8.2.2 Called IN number parameter + +The format of the called IN number parameter is defined in Q.763 [9]. + +### 8.2.3 Call offering treatment indicators parameter + +The format of the call offering treatment indicators parameter is defined in Q.763 [9]. + +### 8.2.4 Charged party identification parameter + +The format of the charged party identification parameter is defined in Q.763 [9]. + +### 8.2.5 Conference treatment indicators parameter + +The format of the conference treatment indicators parameter is defined in Q.763 [9]. + +### **8.2.6 Correlation id parameter** + +The format of the correlation id parameter is defined in Q.763 [9]. + +### **8.2.7 Display information parameter** + +The format of the display information parameter is defined in Q.763 [9]. + +### **8.2.8 SCF id parameter** + +The format of the SCF id parameter is defined in Q.763 [9]. + +### **8.2.9 UID action indicators parameter** + +The format of the UID action indicators parameter is defined in Q.763 [9]. + +### **8.2.10 UID capability indicators parameter** + +The format of the UID capability indicators parameter is defined in Q.763 [9]. + +### **8.2.11 Original called IN number parameter** + +The format of the called IN number parameter is defined in Q.763 [9]. + +# **9 State definitions** + +No specific state definitions are required. + +# **10 Signalling procedures** + +## **10.1 Bearer related connections** + +### **10.1.1 IN basic call** + +For this ITU-T Recommendation, an "IN basic call" is considered as: + +- a normal ISUP basic call invoking IN functionality in the SSP; +- that no DPs are armed dynamically in the request mode; +- that no user interaction is needed. + +For an IN basic call, the normal ISUP basic call procedures are applicable as described in [10] for national intermediate exchanges unless indicated otherwise in the subclauses below. + +#### **10.1.1.1 Successful call setup** + +##### **10.1.1.1.1 Forward address signalling** + +If an IAM is received in a SSP and the call is recognized as IN call, i.e. by detecting a DP as TDP-R [see 10.1.3 (Detection Point processing)], an InitialDP operation or a DP specific operation for a TDP-R is sent from the SSF to the SCF. If the IAM had been segmented the remainder of the call setup information is awaited [see 10.1.1.1.7 (Simple segmentation)]. The mapping of parameters is shown in Table 4. + +**Table 4/Q.1601 – Mapping of parameters from IAM to InitialDP** + +| ISUP message
IAM (Note 1) | INAP operation
InitialDP | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| Called party number | calledPartyNumber | +| Calling party number | callingPartyNumber | +| Calling party subaddress IE contained in access transport | callingPartySubaddress | +| Calling party's category | callingPartysCategory | +| Location number | locationNumber | +| Original called number | originalCalledPartyID | +| User teleservice information (1st priority)
High layer compatibility IE contained in access transport (2nd priority) (Note 2) | highLayerCompatibility | +| Generic number "additional calling party number" | additionalCallingPartyNumber | +| Forward call indicators | forwardCallIndicators | +| User service information prime (1st priority)
User service information (2nd priority)
or
TMR (Note 3) | bearerCapability | +| Redirecting number | redirectingPartyID | +| Redirection information | redirectionInformation | +| CCSS with "CCSS call indicator" | cCSS | +| Access Transport | iSDNAccessRelatedInformation | +| Generic Number | genericNumbers | +| TNS | carrier (Note 4) | +| Calling geodetic location | callingGeodeticLocation | +| NOTE 1 – Optional parameters may be absent, i.e. they are only mapped, if these parameters are available at the DP. | | +| NOTE 2 – If two high layer compatibility information elements are contained in the access transport parameter, then the second information element, carrying the preferred HLC, is mapped to the INAP highLayerCompatibility parameter. | | +| NOTE 3 – The choice whether to use the user service information or the TMR is network option. | | +| NOTE 4 – The first octet, the carrier selection field, is coded to "no indication". The following octets are populated with the contents of the TNS parameter received. | | + +###### **10.1.1.1.1.1 Connect operation** + +On receipt of a Connect operation from the SCP the actions described in 2.1.1.2/Q.764 [10] will be performed. For routing of the call the called party number is derived from the destinationRoutingAddress [see Table 5 (Mapping of parameters from Connect to IAM)]. + +If no cutAndPaste parameter is received in the Connect operation, an ACM message is sent to the preceding exchange. The ACM shall contain the corresponding ISUP parameters, if a serviceInteractionIndicatorsTwo parameter was received in the Connect operation (see below). Other optional parameter will not be sent. The backward call indicators parameter in the ACM is encoded as follows: + +| | | +|-----------------------------------|----------------------------------------------------| +| Charge indicator: | see 10.1.1.1.2 (SendChargingInformation operation) | +| Called party's status indicator: | 00 (no indication) | +| Called party's category: | 00 (no indication) | +| End-to-end method indicator: | 00 (no end-to-end method available) | +| Interworking indicator: | 0 (no interworking encountered) | +| End-to-end information indicator: | 0 (no end-to-end information available) | +| ISDN User Part indicator: | 1 (ISDN User Part used all the way) | +| Holding indicator: | national matter | +| ISDN access indicator: | 1 (terminating access ISDN) | +| Echo Control device indicator: | see 2.7.2.1.2/Q.764 [10] | +| SCCP method indicator: | 00 (no indication) | + +NOTE – As a network operator option, the sending of the ACM message may be postponed to a later stage during call setup. + +Table 5 illustrates the mapping of parameters received in the Connect operation to parameters sent in the IAM message to the succeeding exchange. Parameters which were received in the IAM and are not replaced by parameters of the Connect operation are treated according to the normal procedures. + +On sending of the IAM the awaiting address complete timer T7 is started. If timer T7 expires, the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +**Table 5/Q.1601 – Mapping of parameters from Connect to IAM** + +| INAP operation | ISUP message | +|------------------------------------|------------------------------------------------------------------------| +| Connect (Note 1) | IAM | +| destinationRoutingAddress (Note 2) | Called party number (Note 3) | +| callingPartyNumber | (Note 4) | +| serviceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| originalCalledPartyID | Original called number | +| callingPartysCategory | Calling party's category | +| redirectingPartyID | Redirecting number | +| redirectionInformation | Redirection information | +| isdnAccessRelated Information | ATP (Note 5) | +| forwardCallIndicators | Forward call indicators | +| genericNumbers | Generic Number (Note 4) | +| Carrier | TNS (Note 6) | + +**Table 5/Q.1601 – Mapping of parameters from Connect to IAM (concluded)** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1 – Optional parameters may be absent, i.e. they are only mapped, if received. | +| NOTE 2 – The Connect operation sent by the SCF to the SSF may contain a list of up to three destination routing addresses, following processing by the SSF only one of these addresses will be passed to ISUP. | +| NOTE 3 – The treatment of the called party number in the case the cutAndPaste parameter is present in the Connect operation is described in 3.3.16/Q.1228 [5]. | +| NOTE 4 – The mapping of this parameter must not compromise the existing services supported by ISUP (MCID, CLIP, etc.). | +| NOTE 5 – Due to the end to end significance of the ATP DSS1 information elements only the "called party subaddress" and "calling party subaddress" contained in the "isdnAccessRelatedInformation" are mapped to the "called party subaddress" and "calling party subaddress" of the ATP. Other information elements are copied from the ATP received on the incoming ISUP. The mapping of these information elements must not compromise the existing services supported by ISUP (CLIP, etc.). | +| NOTE 6 – The carrier selection field received in the Carrier parameter is not mapped. The octets following to the carrier selection field are as a national option mapped to the TNS parameter or not mapped. | + +###### **10.1.1.1.1.2 Continue operation** + +On receipt of a Continue operation from the SCP, call processing is resumed and the call setup will be performed as described in 2.1.2.2/Q.764 [10]. + +###### **10.1.1.1.1.3 ContinueWithArgument operation** + +On receipt of a ContinueWithArgument operation from the SCP, call processing is resumed and the call setup will be performed as described in 2.1.2.2/Q.764 [10]. + +In addition, the following parameter received from the SCP in the ContinueWithArgument operation will be sent in the IAM by the SSP as shown in Table 6. + +Parameters which were received in the IAM and are not replaced by parameters of the ContinueWithArgument operation are treated according to the normal procedures. + +**Table 6/Q.1601 – Mapping of parameters from ContinueWithArgument to IAM** + +| INAP operation | ISUP message | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------| +| ContinueWithArgument (Note) | IAM | +| ServiceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| NOTE – Optional parameters may be absent, i.e. they are only mapped, if received. | | + +###### **10.1.1.1.1.4 Mapping of the INAP serviceInteractionIndicatorsTwo** + +The INAP serviceInteractionIndicatorsTwo parameter contains information that is: + +- only of local significance, i.e. to be treated in the SSP; +- relevant for the originating local exchange; or +- relevant for the destination local exchange. + +NOTE – In the context of IN CS-2 the serviceInteractionIndicatorsTwo is used. However the serviceInteractionIndicators may also be received, but the mapping of the serviceInteractionIndicators is network-operator specific. + +Table 7 describes the mapping from the INAP to the ISUP with regard to the serviceInteractionIndicatorsTwo. + +Furthermore for the IN basic, call the following rules shall apply: + +- a) If in the INAP serviceInteractionIndicatorsTwo parameter a value has been received indicated as default in Table 7, then this value is mapped to the value "no indication" in the appropriate ISUP parameter. +- b) An ISUP parameter is only included in a message, if the parameter contents is unequal zero. + +**Table 7/Q.1601 – Mapping of the INAP serviceInteractionIndicatorsTwo** + +| INAP
serviceInteractionIndicatorsTwo | ISUP parameter in | | +|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ACM/CPG/CON/ANM | IAM | +| Call to be diverted indicator:
– call diversion allowed (default);
– call diversion not allowed. | – | Call diversion treatment indicators parameter
Call to be diverted indicator:
– no indication;
– call diversion allowed;
– call diversion not allowed. | +| Call to be offered indicator:
– call offering not allowed (default);
– call offering allowed. | – | Call offering treatment indicators parameter
Call to be offered indicator:
– no indication;
– call offering not allowed;
– call offering allowed. | +| Conference at DLE accept. ind.:
– accept conference request (default);
– reject conference request. | – | Conference treatment indicators parameter
Conference acceptance ind.:
– no indication;
– accept conference request;
– reject conference request. | +| Conference at OLE accept. ind.:
– accept conference request (default);
– reject conference request. | Conference treatment indicators parameter
Conference acceptance ind.:
– no indication;
– accept conference request;
– reject conference request. | – | + +If multiple IN services are invoked for a call, then the serviceInteractionIndicatorsTwo received via the INAP may conflict with the received ISUP parameters transferring service interaction information. In this case the ISUP parameters to be sent in forward and backward direction shall transfer the most stringent condition, i.e. the non-default value (refer to Appendix II). + +###### **10.1.1.1.1.4.1 Interworking with an ISUP not supporting the parameters** + +No specific action is required. If the parameters cannot be transferred to the local exchanges, the behaviour in these exchanges for IN calls is the same as for normal ISDN calls, i.e. no IN controlled treatment of features is possible. + +##### **10.1.1.1.2 SendChargingInformation operation** + +The following mapping is not intended for freephone services but for supporting reverse charging on a per call basis. + +The presence of the noCharge parameter in the SendChargingInformation operation indicates that no charge should be applied to the A-party. + +If the partyToCharge parameter (also of the sendChargingInformation [SCI] operation) indicates the B-party then the noCharge parameter, if present, should be ignored. + +If the SCI operation is received by ISUP after call setup, then the noCharge parameter, if present, should be ignored. + +If the noCharge parameter is determined not be ignored, then this parameter should be mapped to the "Charge indicator" within the next backward signalling message which includes the backward call indicators parameter. + +This mapping does not exclude a different mapping in a specific national network. + +##### **10.1.1.1.3 Address complete or connect message** + +The procedures as described in 2.1.4.2/Q.764 [10] are applicable with the following exceptions: + +Upon receipt of an ACM or CON message the awaiting address complete timer T7 is stopped. If an ACM message is received the awaiting answer timer T9 is started. + +If an ACM message has not been sent, the received message is passed on. The message shall contain the corresponding ISUP parameters, if a serviceInteractionIndicatorsTwo parameter was received in the Connect operation [see 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo)]. + +If an ACM message has already been sent, a received ACM message is mapped to a CPG message and a received CON message to an ANM message, respectively. The mapping of parameters will be performed as described in the Call Diversion stage 3n description (see [8]). + +##### **10.1.1.1.4 Information message (national option)** + +The procedure as described in 2.1.6/Q.764 [10] is applicable. If call setup information is missing an INR message should be sent by the SSP before the InitialDP operation is sent to the SCP. + +##### **10.1.1.1.5 Answer message** + +Upon receipt of an ANM message the awaiting answer timer T9 is stopped and the actions described in 2.1.7/Q.764 [10] are performed. + +##### **10.1.1.1.6 Continuity check** + +If an IAM is received indicating that either a continuity check is requested or is performed on a previous circuit, the normal procedures as described in 2.1.8/Q.764 [10] are applicable. The sending of the InitialDP operation is delayed until a COT message indicating "successful" is received. + +If the continuity check fails, no relationship between SSF and SCF will be established. + +##### **10.1.1.1.7 Simple segmentation** + +With regard to the simple segmentation procedure the SSP behaves like a local exchange. Consequently, items d), e), f) of 2.1.12/Q.764 [10] are applicable. + +##### **10.1.1.1.8 Pre-release Information message** + +Upon receipt of a PRI message by a SSP, the received information is stored and processed upon receipt of the associated release message as specified in ITU-T Q.764. + +When the SSP detects that additional information is to be sent at release time, this information is sent in a PRI message immediately prior to the REL message. + +#### **10.1.1.2 Normal call release** + +The CCF part of the SSP releases the call as described in item b) of 2.3.1/Q.764 [10]. For the SSF part of the SSP the general rules described in 3.1.1.5/Q.1228 [5] are applicable. + +#### **10.1.1.3 Suspend, resume** + +Upon receipt of a SUS message with the indication "network initiated" the timer $T_{SUS}$ is started to ensure that a RES message with the indication "network initiated" or a REL message is received. The received SUS message is not passed on. If the timer $T_{SUS}$ expires, the procedures described in 2.4.3/Q.764 [10] apply. The value of timer $T_{SUS}$ depends on the time limits received in serviceInteractionIndicatorsTwo parameter. + +#### **10.1.1.4 ReleaseCall operation** + +Upon receipt of the ReleaseCall operation, the SSP sends REL messages in both directions. The cause indicators parameter contains the releaseCallArg parameter of the ReleaseCall operation. If no releaseCallArg was present, cause value #31 is sent. Furthermore the normal procedures as described 2.3.3/Q.764 [10] are applicable. + +#### **10.1.1.5 Transfer of the called IN number and original called IN number** + +In all cases the calledPartyNumber parameter sent in the InitialDP operation is transferred in the called IN number parameter to the succeeding exchange. + +The address presentation restricted indicator of the Called IN number parameter is set according to the called IN number presentation restricted indicator received in the INAP serviceInteractionIndicatorsTwo parameter. + +If the Called IN Number parameter had been received from the preceding exchange, but no Original Called IN Number was received, the contents of the received Called IN Number is transferred unchanged in the Original Called IN number parameter. + +If an Original Called IN Number is received, it is passed on unchanged. + +##### **10.1.1.5.1 Interworking with an ISUP not supporting the called IN number or the original called IN number parameter** + +No specific action is required. + +#### **10.1.1.6 Abnormal conditions** + +##### **10.1.1.6.1 General requirements on receipt of unrecognized signalling information messages and parameters** + +With regard to the handling of unrecognized signalling information, a SSP behaves like a type A exchange. + +NOTE – In the future this limit may be relaxed. + +### **10.1.2 IN call with SCP request to collect further digits** + +After sending the InitialDP operation to the SCP, a RequestReportBCSMEVENT operation to arm DP CI accompanied by a CollectInformation operation may be received from the SCP (see 3.3.15/Q.1228 [5]). In this case the specified number of digits will be collected in the SSP. Encountering DP CI, i.e. the specified number of digits has been received, will result in sending an EventReportBCSM operation or a CollectedInformation operation, respectively, to the SCP. + +In addition to 10.1.1.5, the digits sent to the SCP in the EventReportBCSM operation or the CollectedInformation operation shall be taken into account when constructing the called IN number parameter. + +There is no further impact on the ISUP protocol and the call handling will continue as described in 10.1.1 (IN basic call), unless a further RequestReportBCSMEVENT operation to arm DP CI accompanied by a CollectInformation operation is received from the SCP. In this case the procedure described above is repeated. + +### 10.1.3 Detection Point processing + +#### 10.1.3.1 General + +The SCF uses the RequestReportBCSMEVENT operation to request the SSF to monitor for call-related events. The monitor mode is indicated in the operation as either "interrupted" or "notifyAndContinue". + +In the "notifyAndContinue" mode the event is reported as EDP-N (notification mode) in the EventReportBCSM operation or a DP specific operation, respectively, to the SCF and normal call processing continues as described in 10.1.1 (IN basic call). + +In the "interrupted" mode the event is reported as EDP-R (request mode) in the EventReportBCSM operation or a DP specific operation, respectively, and the SSF will wait for instructions from the SCF. See Table 8. + +**Table 8/Q.1601 – Event Detection Points** + +| DP | DP encountered on ... | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CI | See 10.1.2 (IN call with SCP request to collect further digits). | +| OTS, CA | Receipt of an ACM or CPG message with an alerting indication. | +| RSF | National network specific. | +| OCPB, TB | Receipt of a REL message with cause value #17 (user busy) (Note). | +| ONA, TNA | Expiry of timer $T_{NoReply}$ . | +| OAns, TAns | Receipt of an ANM or CON message. | +| OS, TS | Receipt of a SUS message with the indication "network initiated". | +| ORA, TRA | Receipt of a RES message with the indication "network initiated". | +| OD, TD | a) Receipt of a REL message with cause value #16 (normal call clearing) in the active phase of a call (Note).
b) Expiry of timer $T_{SUS}$ . | +| OAb, Tab | Receipt of a REL message with cause value #16 (normal call clearing) from a preceding exchange before the call is answered (Note). | +| NOTE – These are examples of correspondence between cause values and DPs. The network operator shall have the possibility to define the complete mapping between cause values and DPs. It should be noted that any operator defined mapping may contradict those defined in future IN Capability Sets. | | + +In the following, the differences in call processing for IN calls with dynamically armed detection points compared to the procedures described in 10.1.1 (IN basic call) and 10.1.4 (Setup of an IN call to destination B) are listed. + +##### 10.1.3.1.1 Address complete message + +On receipt of a ACM message without a cause parameter, the timer $T_{NoReply}$ is started if either DP ONA or TNA has been armed by the SCF. + +##### **10.1.3.1.2 Answer or connect message** + +The timer $T_{\text{NoReply}}$ is stopped, if applicable. + +##### **10.1.3.1.3 Release message** + +If a REL is received from either the preceding or succeeding exchange and corresponds to a DP armed as EDP-N (notification mode), the CCF part of the SSP releases the call like an ordinary transit exchange. For the SSF part of the SSP the general rules described in 3.1.1.5/Q.1228 [5] are applicable. + +If a REL is received from the preceding exchange and corresponds to a DP armed as EDP-R (request mode), the CCF part of the SSP releases the call like an ordinary transit exchange. For the SSF part of the SSP the general rules described in 3.1.1.5/Q.1228 [5] are applicable. + +If a REL is received from the succeeding exchange and corresponds to a DP armed as EDP-R (request mode), the CCF part of the SSP releases the outgoing leg of the connection and holds the incoming leg. For the SSF part of the SSP the general rules described in 3.1.1.5/Q.1228 [5] are applicable. The call processing is suspended and the SSP waits for SCP instructions. + +#### **10.1.3.2 Actions to be performed in case of DPs armed in the request mode (except for DP Collect information)** + +##### **10.1.3.2.1 Storage and release of initial address information** + +Initial address information is not released from memory on receipt of an ACM message. + +NOTE – Memory capacity in the exchange may limit the use of services requiring the storage of initial address information. + +##### **10.1.3.2.2 Signalling procedures for connection type allowing fallback** + +If: + +- a) an IAM was received with the TMR value set to "64 kbit/s unrestricted preferred"; +- b) no fallback has already been performed, + +then on receipt of the Connect operation a fallback is performed as described in 2.5.1.2.2 and 2.5.2.2.2/Q.764 [10]. + +##### **10.1.3.2.3 Impact on supplementary services** + +###### **10.1.3.2.3.1 User-to-user signalling** + +###### **10.1.3.2.3.1.1 User-to-user signalling, service 1** + +If user-to-user service 1 is implicitly requested, the user-to-user information parameter will be discarded from the IAM message and the user-to-user indicators parameter indicating "user-to-user information discarded by the network" is sent in the ACM message, + +If the user-to-user service 1 was explicitly requested as "not essential", the user-to-user indicators parameter will be discarded from the IAM and service 1 will be indicated as "not provided" in the ACM. + +If the user-to-user service 1 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.3.2.3.1.2 User-to-user signalling, service 2** + +If the user-to-user service 2 was explicitly requested as "not essential", the user-to-user indicators parameter will be discarded from the IAM and service 2 will be indicated as "not provided" in the ACM. + +If the user-to-user service 2 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.3.2.3.1.3 User-to-user signalling, service 3** + +###### a) *Service request during call setup* + +If the user-to-user service 3 was explicitly requested as "not essential", the user-to-user indicators parameter will be discarded from the IAM and service 3 will be indicated as "not provided" in the ACM. + +If the user-to-user service 3 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### b) *Service request after call setup* + +A FRQ with facility indicators set to "user-to-user service" and the user-to-user indicators parameter (containing the relevant service 3 information) will be responded by a FRJ message indicating "not provided" for service 3 in the user-to-user indicators. + +### **10.1.4 Setup of an IN call to destination B** + +This subclause describes the setup of an IN call to destination B after a user interactive dialogue has been performed or after the SSF has reported an EDP-R in the EventReportBCSM operation or a DP specific operation, respectively, to the SCF. In these situations, the call setup differs from the normal call setup for the "IN basic call". + +#### **10.1.4.1 Successful call setup** + +##### **10.1.4.1.1 Forward address signalling** + +###### **10.1.4.1.1.1 Connect operation** + +On receipt of the Connect operation the actions described in 10.1.1.1.1.1 (Connect operation) are performed with the following exceptions: + +- a) An ACM message is sent towards the originating local exchange, if not already sent before. +- b) Throughconnection is performed as described in item d) of 2.1.1.1/Q.764 [10]. + +##### **10.1.4.1.2 Mapping of the INAP serviceInteractionIndicatorsTwo** + +The SCF logic may generate new service interaction information for the call. + +In this case the indicators of the INAP serviceInteractionIndicatorsTwo parameter relevant for the forward direction, i.e. to be mapped into the IAM, are treated as described in 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo). + +The handling of the indicators relevant for the backward direction is however different: + +- The indicators contained in the received INAP serviceInteractionIndicatorsTwo parameter are compared one by one against the indicators that are stored in the SSP, i.e. that have been received in an earlier INAP operation. +- If the received value of an indicator differs from the one that is stored in the SSP, then this indicator is mapped to the corresponding value in the appropriate ISUP parameter. +- If the received value of an indicator is equal to the one that is stored in the SSP, then this indicator is mapped to the value "no indication" in the appropriate ISUP parameter. + +If for the call no new service interaction information was received, then the exchange will apply the information that is stored, i.e. the forward indicators sent in the IAM are the same as for the previous connection, backward indicators need not be sent. + +##### 10.1.4.1.3 Sending of backward messages + +If backward messages have already been sent to preceding exchanges, it may be required: + +- a) to map a received message into another message; or +- b) to generate another message instead of the message, that would normally be generated. + +Table 9 describes which message is to be sent in the different cases. + +**Table 9/Q.1601 – Sending of backward messages** + +| Message received or message to be sent, respectively →

↓ Messages already sent | ACM | CPG
"alerting" or "in-band information or an ..." | CPG
"progress" | CON | ANM | +|---------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------|-------------------|--------------------------------|-------------------------| +| ACM/CON not sent | ACM (Note 1) | Not relevant | Not relevant | CON (Note 1) | Not relevant | +| ACM sent, ANM not sent | CPG (Note 1) | CPG | CPG | ANM (Note 1) | ANM | +| ANM/CON sent for previous connection, but ANM/CON not received for actual connection | CPG "progress" (Notes 1 and 2) | CPG "progress" (Note 2) | CPG "progress" | CPG "progress" (Notes 1 and 2) | CPG "progress" (Note 2) | +| ANM/CON sent for previous connection and ANM/CON received for actual connection | Not relevant | Not relevant | CPG "progress" | Not relevant | Not relevant | + +NOTE 1 – If a serviceInteractionIndicatorsTwo parameter was provided in the INAP operation, this message carries the corresponding ISUP parameters, if applicable. + +NOTE 2 – An originating local exchange conforming to [10] will discard this CPG message since no generic notification parameter is contained in the message. + +##### 10.1.4.1.4 Address complete message + +Upon receipt of an ACM message the following actions shall be performed: + +- a) The awaiting address complete timer T7 is stopped. +- b) If an UID action indicators parameter indicating "stop or do not start T9", then the SSP shall not start/shall stop timer T9 and shall start timer TUID, else timer T9 is started or restarted, respectively. +- c) If an UID action indicators parameter indicating "through-connect in both directions", the SSP shall through-connect the transmission path in both directions (if not already connected). + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). If the ACM contains an UID action indicators parameter, then the parameter shall be passed on transparently to preceding exchanges, unless an ANM has already been sent. + +##### **10.1.4.1.5 Call Progress message (Basic call)** + +Upon receipt of a CPG message the following actions shall be performed: + +- a) If an UID action indicators parameter indicating "stop or do not start T9", then SSP shall not start/shall stop timer T9 and shall start timer $T_{UID}$ . +- b) If an UID action indicators parameter indicating "through-connect in both directions", the SSP shall through-connect the transmission path in both directions (if not already connected). + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). If the CPG contains an UID action indicators parameter, then the parameter shall be passed on transparently to preceding exchanges, unless an ANM message has already been sent. + +##### **10.1.4.1.6 Connect message** + +Upon receipt of a CON message the awaiting address complete timer T7 is stopped and the transmission path is throughconnected in forward direction, if not already connected. + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). + +##### **10.1.4.1.7 Answer message** + +Upon receipt of an ANM message the awaiting answer timer T9 or the timer $T_{UID}$ , respectively, is stopped and the transmission path is throughconnected in forward direction, if not already connected. + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). + +#### **10.1.4.2 Timer $T_{UID}$ expiry** + +If $T_{UID}$ expires, the call is released using cause value #31 (normal, unspecified). + +#### **10.1.4.3 Abnormal conditions** + +##### **10.1.4.3.1 Handling of unexpected messages** + +The procedures described in 2.9.5.1/Q.764 [10] are applicable with the following exceptions: + +- a) If an ACM message has already been sent for the incoming leg of the call, but an ACM has not been received for the outgoing leg of the call, then + - i) a CPG received in forward direction shall be discarded, i.e. the message is not treated as an unexpected message; + - ii) an unrecognized message received in forward direction shall not be passed on and the procedure described in item xi) of 2.9.5.2/Q.764 [10] shall be applied. +- b) If an ANM message has already been sent for the incoming leg of the call, but an ANM has not been received for the outgoing leg of the call, then the following messages received in forward direction shall be discarded, i.e. the messages are not treated as unexpected messages: SUS, RES, FAR and FOT. + +#### **10.1.4.4 Impact on supplementary services** + +##### **10.1.4.4.1 Call hold** + +On receipt of a CPG message with the generic notification indicator set to "remote hold", a note in memory shall be set. The note shall be reset on receipt of a CPG message with the generic notification indicator set to "remote retrieval". + +If the note is set on receipt of a connect operation, then an artificial CPG message with the generic notification indicator set to "remote retrieval" shall be generated. + +##### **10.1.4.4.2 Malicious call identification** + +On receipt of an IDR message two cases exist: + +- a) If an IDR or an ANM was already sent to the preceding exchange, then the IDR message is not passed on and is immediately responded by an IRS message. +- b) If an IDR was not sent to the preceding exchange, then the IDR message is passed on transparently towards the originating local exchange. + +If bit A of the MCID request indicators was set to 1, then in addition to the normal procedure the service switching point includes the charged party identification parameter, if available, into the IRS message. + +### **10.1.5 User interactive dialogue (in-band)** + +If in response to the InitialDP operation, the EventReportBCSM operation or a DP specific operation, a ConnectToResource or EstablishTemporaryConnection operation is received from the SCF, then the incoming call shall be connected to a physical entity containing the SRF, i.e. intelligent peripheral (IP). In case of ConnectToResource the SSP, that interacts with the SCP, supports the requested IP capabilities and the IP is therefore either integrated or co-located in the SSP. In case of EstablishTemporaryConnection the IP is available in another network element. Consequently, the Assist method is applied. + +#### **10.1.5.1 SSP supports requested IP capabilities** + +##### **10.1.5.1.1 Successful call setup** + +###### **10.1.5.1.1.1 Forward address signalling** + +###### **10.1.5.1.1.1.1 ConnectToResource operation** + +On receipt of the ConnectToResource operation the IP is connected to the incoming call, if the TMR value received in the IAM message is set to either "speech" or "3.1 kHz audio" or "64 kbit/s unrestricted preferred". For the latter case see also 10.1.3.2.2 (Signalling procedures for connection type allowing fallback). If other TMR values are received, the call is released using cause value #65. + +###### **10.1.5.1.1.1.2 Address complete message or call progress message** + +An ACM message containing an optional backward call indicators parameter indicating "in-band information or an appropriate pattern is now available" is sent. The backward call indicators parameter in the ACM is encoded as described in 10.1.1 (IN basic call). + +Depending on the contents of the INAP serviceInteractionIndicatorsTwo and capabilities of the preceding exchanges, the UID action indicators parameter may be included in the ACM: + +###### **a) *Through-connection instruction*** + +If the bothway through-connect indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "required" and if an UID capability indicators parameter was received with bit A coded 1 (through-connection modification possible) in the IAM, then the UID action indicators parameter shall be included into the ACM message with bit A coded (through-connect in both directions). + +###### **b) *T9 timer instruction*** + +If the dialogue duration indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "long duration" and if an UID capability indicators parameter was received with bit B coded 1 (stopping of timer possible) in the IAM, then an + +UID action indicators parameter shall be included into the ACM with bit B coded 1 (stop or do not start T9). + +If backward messages have already been sent to preceding exchange, then instead of ACM a CPG message is sent. This is described in 10.1.4.1.3 (Sending of backward messages). The CPG message shall contain the UID action indicators parameter as described above for the ACM message. + +###### **10.1.5.1.1.3 Answer message** + +When the IP answers, the sending of an ANM message depends on the following conditions: + +- a) If the bothway through-connect indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "required" and if a through-connection capability indicator set to "through-connection modification possible" was not received in the IAM, then an ANM message is sent. +- b) If the dialogue duration indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "long duration" and if a T9 timer indicator set to "stopping of timer possible" was not received in the IAM, then an ANM message is sent. + +If backward messages have already been sent to the preceding exchange, then instead of ANM a different message may be sent. This is described in 10.1.4.1.3 (Sending of backward messages). + +NOTE – The sending of an ANM message may also be required, if a chargeable announcement is to be connected. However, charging aspects are outside the scope of this ITU-T Recommendation. + +##### **10.1.5.1.2 Storage and release of initial address information** + +Initial address information is retained in memory to allow a call setup to a new destination after disconnecting the IP. + +NOTE – Memory capacity in the exchange may limit the use of services requiring the storage of initial address information. + +##### **10.1.5.1.3 Signalling procedures for connection type allowing fallback** + +If: + +- a) the TMR value received in the IAM is set to "64 kbit/s unrestricted preferred"; +- b) no fallback has already been performed; +- c) an ANM message is to be sent, i.e. the bothway throughconnect indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "required", + +then on receipt of the ConnectToResource operation a fallback is performed as described in 2.5.1.2.2 and 2.5.2.2.2 of Q.764 [10]. + +##### **10.1.5.1.4 DisconnectForwardConnection operation** + +When the DisconnectForwardConnection operation is received, the IP will be disconnected. + +##### **10.1.5.1.5 Impact on supplementary services** + +###### **10.1.5.1.5.1 Connected line identification presentation** + +The following text is only applicable, if an ANM message is to be sent for the IP connection and if an ANM message was not sent before. + +If the connected line identity was requested by the calling user, the SSP behaves as follows: + +If "no impact" was received in the INAP serviceInteractionIndicatorsTwo (connected number treatment indicator), then two cases exist: + +- a) If a connected number is available for the IP, then the procedure as described in 5.5.2.5/Q.731 [7] will be performed. +- b) If a connected number is not available for the IP, then the SSP sends a connected number parameter in the ANM message encoded as follows: + +| | | +|--------------------------------------------|-------------------------------------------| +| nature of address indicator: | 0000000 | +| numbering plan indicator: | 000 | +| address presentation restricted indicator: | 10 (address not available) | +| screening indicator: | 11 (network provided), no address signals | + +If "presentation restricted" was received in the INAP serviceInteractionIndicatorsTwo (connected number treatment indicator), then two cases exist: + +- a) If a connected number is available for the IP, then the procedure as described in 6.5.2.5/Q.731 [7] will be performed. +- b) If a connected number is not available for the IP, then the SSP sends a connected number parameter in the ANM message encoded as shown in item b) above. + +If "present called IN number" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) A connected number parameter is generated as follows: + +| | | +|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| nature of address indicator and numbering plan indicator are encoded as received in the called party number of the IAM message, | | +| address presentation restricted indicator: | 00 (presentation allowed); | +| address signals: | as received in called party number or subsequent number parameters, respectively, until ACM message was sent. | +- b) A generic number parameter "additional connected number" is not sent. + +###### **10.1.5.1.5.2 User-to-user signalling** + +The text in the following three subclauses is only applicable, if an ANM message is to be sent for the IP connection and if an ANM message was not sent before. + +###### **10.1.5.1.5.2.1 User-to-user signalling, service 1** + +If user-to-user service 1 is implicitly requested, the user-to-user information parameter will be discarded from the IAM message and the user-to-user indicators parameter indicating "user-to-user information discarded by the network" is sent in the ACM message. + +If the user-to-user service 1 was explicitly requested as "not essential", the user-to-user indicators parameter will be discarded from the IAM and service 1 will be indicated as "not provided" in the ACM. + +If the user-to-user service 1 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.5.1.5.2.2 User-to-user signalling, service 2** + +If the user-to-user service 2 was explicitly requested as "not essential", the user-to-user indicators parameter will be discarded from the IAM and service 2 will be indicated as "not provided" in the ACM. + +If the user-to-user service 2 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### 10.1.5.1.5.2.3 User-to-user signalling, service 3 + +###### a) *Service request during call setup* + +If the user-to-user service 3 was explicitly requested as "not essential", the user-to-user indicators parameter will be discarded from the IAM and service 3 will be indicated as "not provided" in the ACM. + +If the user-to-user service 3 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### b) *Service request after call setup* + +A FRQ with facility indicators set to "user-to-user service" and the user-to-user indicators parameter (containing the relevant service 3 information) will be responded by a FRJ message indicating "not provided" for service 3 in the user-to-user indicators. + +#### 10.1.5.2 Assist method – procedure in the initiating SSP + +##### 10.1.5.2.1 Successful call setup + +###### 10.1.5.2.1.1 Forward address signalling + +###### 10.1.5.2.1.1.1 EstablishTemporaryConnection operation + +On receipt of the EstablishTemporaryConnection operation from the SCP a connection to an external IP will be established, if the TMR value received in the IAM message is set to either "speech" or "3.1 kHz audio" or "64 kbit/s unrestricted preferred". For the latter case see also 10.1.3.2.2 (Signalling procedures for connection type allowing fallback). If other TMR values are received, the call is released using cause value #65. + +The IAM message for setup of the temporary connection is newly generated as in an originating local exchange. + +For routing of the call the called party number is derived from the assistingSSPIPRoutingAddress. + +Table 10 illustrates the mapping of parameters received in the EstablishTemporaryConnection operation to parameters sent in the IAM message. + +**Table 10/Q.1601 – Mapping of parameters from EstablishTemporaryConnection to IAM** + +| INAP operation | ISUP message | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------| +| EstablishTemporaryConnection (Note) | IAM | +| assistingSSPIPRoutingAddress | Called party number | +| serviceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| correlationID | Correlation id | +| scfID | SCF id | +| NOTE – Optional parameters may be absent, i.e. they are only mapped, if received. | | + +Except the called party number parameter the remaining mandatory parameters of the IAM message are set as follows: + +###### a) *Nature of connection indicators:* + +| | | +|--------------------------------|------------------| +| Satellite indicator: | set as in an OLE | +| Continuity check indicator: | set as in an OLE | +| Echo control device indicator: | set as in an OLE | + +###### b) *Forward call indicators:* + +| | | +|----------------------------------------|------------------------------------------| +| National/international call indicator: | set as in an OLE | +| End-to-end method indicator: | 00 (no end-to-end method available) | +| Interworking indicator: | 0 (no interworking encountered) | +| End-to-end information indicator: | 0 (no end-to-end information available) | +| ISDN user part indicator: | 1 (ISDN user part used all the way) | +| ISDN user part preference indicator: | 10 (ISDN user part required all the way) | +| ISDN access indicator: | 0 (originating access non-ISDN) | +| SCCP method indicator: | 00 (no indication) | + +###### c) *Calling party's category:* + +00001010 (ordinary subscriber). + +###### d) *Transmission medium requirement:* + +00000011 (3.1 kHz audio). + +Besides the parameters listed in Table 10 (Mapping of parameters from EstablishTemporaryConnection to IAM), the IAM contains the following optional parameters: + +- propagation delay counter (set as in an OLE); +- hop counter (set as in an OLE). + +On sending of the IAM an ACM message is sent to the preceding exchange encoded as described in 10.1.1 (IN basic call), and the awaiting address complete timer T7 is started. If timer T7 expires, the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +###### **10.1.5.2.1.1.2 Interworking with an ISUP not supporting the Correlation Id and SCF Id parameters** + +If the parameters cannot be transferred to the assisting SSP, the setup of the connection will fail. + +###### **10.1.5.2.1.2 Address complete message** + +Refer to 10.1.4.1.4 (Address complete message). + +###### **10.1.5.2.1.3 Call Progress message (Basic call)** + +Refer to 10.1.4.1.5 (Call Progress message (Basic call)). + +###### **10.1.5.2.1.4 Connect message** + +Refer to 10.1.4.1.6 (Connect message). + +###### **10.1.5.2.1.5 Answer message** + +Refer to 10.1.4.1.7 (Answer message). + +##### **10.1.5.2.2 Storage and release of initial address information** + +In the initiating SSP initial address information is retained to allow a call setup to a new destination after disconnecting the IP. + +NOTE – Memory capacity in the exchange may limit the use of services requiring the storage of initial address information. + +##### **10.1.5.2.3 DisconnectForwardConnection operation** + +When the DisconnectForwardConnection operation is received from the SCP, the normal release procedures are applied for the outgoing circuit. The REL message sent in forward direction contains cause value #31. + +##### **10.1.5.2.4 DisconnectForwardConnectionWithArgument operation** + +When the DisconnectForwardConnectionWithArgument operation is received from the SCP, the normal release procedures are applied for the outgoing circuit. The REL message sent in forward direction contains cause value #31. + +##### **10.1.5.2.5 Abnormal conditions** + +###### **10.1.5.2.5.1 Handling of unexpected messages** + +Refer to 10.1.4.3.1 (Handling of unexpected messages). + +##### **10.1.5.2.6 Impact on supplementary services** + +The actions as described in 10.1.4.4 (Impact on supplementary services) are applicable. + +#### **10.1.5.3 Hand-off method – procedure in the initiating SSP** + +On receipt of a Connect operation from the SCP, the actions described in 10.1.1 (IN basic call) or in subclause 10.1.4 (Setup of an IN call to destination B) will be performed. The INAP correlationID and scfID parameters are mapped to the corresponding ISUP parameters in the IAM message. + +#### **10.1.5.4 Assist/Hand-off method – procedure in the assisting SSP** + +##### **10.1.5.4.1 Successful call setup** + +###### **10.1.5.4.1.1 Forward address signalling** + +If an IAM is received in a SSP and the call is recognized as a call which is to be routed to an IP, an AssistReqInstructions operation is sent from the SSF to the SCF. The mapping of parameters is shown in Table 11. + +**Table 11/Q.1601 – Mapping of parameters from IAM to AssistRequestInstruction** + +| ISUP message | INAP operation | +|---------------------|---------------------------------| +| IAM | AssistRequestInstruction | +| Correlation id | correlationID | + +###### **10.1.5.4.1.1.1 ConnectToResource operation** + +The procedure to be performed after receipt of the ConnectToResource operation is identical to the procedure described in 10.1.5.1 (SSP supports requested IP capabilities). + +### **10.1.6 Call gapping** + +When receiving the CallGap operation, the SSF reduces the rate at which specific service requests are sent to the SCF. The detailed procedure is described in 7.3.6/Q.1228 [5]. + +If the call is to be gapped and the gapTreatment parameter was present in the CallGap operation, then: + +- a) If the "informationToSend" indicates announcement or tone, then the ACM message contains an optional backward call indicators parameter indicating "in-band information or an appropriate pattern is now available". + +After the calling user has received the "informationToSend" the call is released and the cause indicators parameter contains the releaseCause parameter of the CallGap operation. If no releaseCause was present, cause value #31 is sent. + +- b) If the "informationToSend" indicates display information, then the call is released and a display information parameter is included in the REL message. The cause indicators parameter contains the releaseCause parameter of the CallGap operation. If no releaseCause was present, cause value #31 is sent. + +If the gapTreatment is not present in the CallGap operation, the SSF will use a default treatment depending on network-operator implementation. + +### **10.1.7 Service filtering** + +When receiving the ActivateServiceFiltering operation, the SSF handles calls which are to be filtered in a specified manner without request for instructions to the SCF. The detailed procedure is described in 7.3.1/Q.1228 [5]. + +- a) If a call is to be filtered and the "informationToSend" indicates announcement or tone, then an ACM message is sent to the preceding exchange with an optional backward call indicators parameter indicating "in-band information or an appropriate pattern is now available". In the case of a chargeable in-band information an ANM is sent in addition. + +After the calling user has received the "informationToSend" the call is released and the cause indicators parameter contains the releaseCause parameter of the ServiceFiltering operation. If no releaseCause was present, cause value #31 is sent. + +- b) If a call is to be filtered and the "informationToSend" indicates display information, then: + - if the "informationToSend" is free of charge, the call is released and a display information parameter is included in the REL message. The cause indicators parameter contains the releaseCause parameter of the ServiceFiltering operation. If no releaseCause was present, cause value #31 is sent; + - if the "informationToSend" is not free of charge, an ANM message containing the display information parameter is sent. Then the call is released and the cause indicators parameter contains the releaseCause parameter of the ServiceFiltering operation. If no releaseCause was present, cause value #31 is sent. + +#### **10.1.7.1 Impact on supplementary services** + +##### **10.1.7.1.1 Closed user group** + +If the call is a CUG call with outgoing access not allowed, then the "informationToSend" is not provided and the call is released using cause value #29 with diagnostics. The diagnostics field contains the CUG interlock code parameter name. + +### **10.1.8 SCP initiated call** + +For a SCP initiated call the SSP behaves like an originating local exchange with the exception that no information is received/sent from/to the access protocol. The call setup information needed for the generation of the IAM message is partly provided with the InitiateCallAttempt operation. The remaining mandatory fields of the IAM message are supplied with default values. This is described in the subclauses below. + +#### **10.1.8.1 Successful call setup** + +##### **10.1.8.1.1 Forward address signalling** + +On receipt of an InitiateCallAttempt operation from the SCP the contents are stored and call processing is suspended. + +###### 10.1.8.1.1.1 Continue operation + +The actions described in 2.1.1.1/Q.764 [10] will be performed. For routing of the call the called party number is derived from the destinationRoutingAddress [see Table 12 (Mapping of parameters from InitiateCallAttempt to IAM)]. + +Table 12 illustrates the mapping of parameters received in the InitiateCallAttempt operation to parameters sent in the IAM message. + +**Table 12/Q.1601 – Mapping of parameters from InitiateCallAttempt to IAM** + +| INAP operation | ISUP message | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| InitiateCallAttempt (Note 1) | IAM | +| destinationRoutingAddress | Called party number | +| callingPartyNumber | Calling party number | +| serviceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| carrier | TNS (Note 2) | +| NOTE 1 – Optional parameters may be absent, i.e. they are only mapped, if received. | | +| NOTE 2 – The carrier selection field received in the Carrier parameter is not mapped. The octets following to the carrier selection field are as a national option mapped to the TNS parameter or not mapped. | | + +Except the called party number parameter the remaining mandatory parameters of the IAM message are set as follows: + +- a) *Nature of connection indicators:* + - Satellite indicator: set as in an OLE + - Continuity check indicator: set as in an OLE + - Echo control device indicator: set as in an OLE +- b) *Forward call indicators:* + - National/international call indicator: set as in an OLE + - End-to-end method indicator: 00 (no end-to-end method available) + - Interworking indicator: 0 (no interworking encountered) + - End-to-end information indicator: 0 (no end-to-end information available) + - ISDN user part indicator: 1 (ISDN user part used all the way) + - ISDN user part preference indicator: 00 (ISDN user part preferred all the way) + - ISDN access indicator: 0 (originating access non-ISDN) + - SCCP method indicator: 00 (no indication) +- c) *Calling party's category:* +00001010 (ordinary subscriber). +- d) *Transmission medium requirement:* +00000011 (3.1 kHz audio). + +Besides the parameters listed in Table 12, the IAM contains the following optional parameters: + +- propagation delay counter (set as in an OLE); +- hop counter (set as in an OLE). + +### 10.1.9 GVNS + +This subclause describes the setup of an GVNS call. In this situation, the call setup differs from the normal call setup for the "IN basic call". + +#### 10.1.9.1 Procedure in the SSP providing the GVNS access function + +In addition to the description given in 10.1.1 (IN basic call), the following actions are to be performed. + +When receiving the Connect or the ContinueWithArgument Operation with the forwardGVNS parameter, the SSP maps it to the ISUP parameter "Forward GVNS" in IAM in addition to the mapping given in 10.1.1 (IN basic call) according to Table 13. + +**Table 13/Q.1601 – GVNS Mapping of parameters from Connect/ContinueWithArgument to IAM** + +| INAP operation | ISUP message | +|-------------------------------------|---------------------| +| Connect/ContinueWithArgument | IAM | +| ForwardGVNS | Forward GVNS | + +On receipt of ANM/CON the received ISUP parameter "Backward GVNS" parameter is mapped to ERB "backwardGVNS" parameter on INAP (if armed) according to Table 14. + +**Table 14/Q.1601 – GVNS Mapping of parameters from ANM/CON to ERB** + +| ISUP message | INAP operation | +|---------------------|------------------------| +| ANM/CON | EventReportBCSM | +| Backward GVNS | backwardGVNS | + +In addition the SSP discards the "backward GVNS" parameter received in ANM/CON. + +On receipt of ANM/CON the Backward GVNS parameter is mapped to the backwardGVNS parameter of the EventReportBCSM operation, if applicable. + +#### 10.1.9.2 Procedure in the SSP providing the originating GVNS routing function + +In addition to the description given in 10.1.1 (IN basic call), the following actions are to be performed. + +When receiving the IAM, the actions described in 10.1.1 (IN basic call) are performed. In addition to the mapping given there, the following mapping is applied (see Table 15): + +**Table 15/Q.1601 – GVNS mapping of parameters from IAM to InitialDP** + +| ISUP message | INAP operation | +|---------------------|-----------------------| +| IAM | InitialDP | +| Forward GVNS | forwardGVNS | + +When receiving the Connect or the ContinueWithArgument Operation with the forwardGVNS parameter, the SSP maps it to the ISUP parameter "Forward GVNS" in IAM in addition to the mapping given in 10.1.1 (IN basic call) according to Table 16. + +**Table 16/Q.1601 – GVNS Mapping of parameters from +Connect/ContinueWithArgument to IAM** + +| INAP operation | ISUP message | +|-------------------------------------|---------------------| +| Connect/ContinueWithArgument | IAM | +| forwardGVNS | Forward GVNS | + +#### **10.1.9.3 Procedure in the SSP providing the terminating GVNS routing function** + +In addition to the description given in 10.1.1 (IN basic call), the following actions are to be performed. + +When receiving the IAM, the actions described in 10.1.1 (IN basic call) are performed. In addition to the mapping given there, the following mapping is applied (see Table 17): + +**Table 17/Q.1601 – GVNS Mapping of parameters from IAM to InitialDP** + +| ISUP message | INAP operation | +|---------------------|-----------------------| +| IAM | InitialDP | +| Forward GVNS | forwardGVNS | + +When receiving the Connect or the ContinueWithArgument Operation with the backwardGVNS parameter, the SSP maps it to the ISUP parameter "Backward GVNS" in ANM/CON according to Table 18 in addition to the actions described in 10.1.1 (IN basic call). + +**Table 18/Q.1601 – GVNS mapping of parameters from Connect/ +ContinueWithArgument to ANM/CON** + +| INAP operation | ISUP message | +|-------------------------------------|---------------------| +| Connect/ContinueWithArgument | ANM/CON | +| BackwardGVNS | Backward GVNS | + +The Forward GVNS parameter received in IAM is discarded. + +### **10.1.10 Actions to be performed in local exchanges** + +#### **10.1.10.1 Actions in the originating local exchange** + +For an IN basic call the normal ISUP basic call procedures are applicable as described in [10] for originating local exchanges unless indicated otherwise in the subclauses below. + +##### **10.1.10.1.1 Successful call setup** + +###### **10.1.10.1.1.1 Forward address signalling** + +If the exchange has the capability to through-connect the transmission path in both directions upon receipt of the UID action indicators parameter with bit A coded 1, then the exchange shall send the UID capability indicators parameter in the IAM message with bit A coded 1. + +If the exchange has the capability to stop or not to start timer T9 upon receipt of the UID action indicators parameter with bit B coded 1, then the exchange shall send the UID capability indicators parameter in the IAM message bit B coded 1. + +###### **10.1.10.1.1.2 Address complete, call progress, connect or answer message** + +Upon receipt of an ACM or CPG message with the UID action indicators parameter indicating "through-connect in both directions" (bit A coded 1), the local exchange shall through-connect the transmission path in both directions, if not already connected. + +Upon receipt of an ACM or CPG message with the UID action indicators parameter indicating "stop or do not start T9 timer" (bit B coded 1), the local exchange shall not start/shall stop timer T9 and shall start timer $T_{UID}$ to guard the connection. If $T_{UID}$ was already running upon receipt of the UID action indicators parameter with bit B coded 1, then $T_{UID}$ shall be restarted. + +Upon receipt of an ANM or CON message, the local exchange shall stop T9 or $T_{UID}$ , if running. + +If $T_{UID}$ expires, see 10.1.4.2 (Timer $T_{UID}$ expiry). + +If received in these messages, the conference treatment indicators parameter shall be stored in the exchange. If the parameter has already been stored, then the stored information will be overwritten. The application of this parameter is described in clause 12 (Interaction between IN basic call and ISDN supplementary services). + +#### **10.1.10.2 Actions in the destination local exchange** + +##### **10.1.10.2.1 Successful call setup** + +###### **10.1.10.2.1.1 Forward address signalling** + +If received in the IAM message, the following parameters shall be stored: conference treatment indicators, call diversion treatment indicators, called IN number. + +The application of these parameters is described in clause 12 (Interaction between IN basic call and ISDN supplementary services). + +###### **10.1.10.2.1.1.1 Preventing of call offering for calls not routed via IN at a destination access** + +Upon receipt of an IAM for an access which is marked as "prevent call offering for non-authorized calls" the following actions are performed: + +- If the IAM contains the call to be offered indicator set to "call offering allowed" in the call offering treatment indicators parameter field, the call will be setup as described in 2.1.1.6/Q.764 [10]. +- If the IAM contains either the call to be offered indicator set to "call offering not allowed" in the call offering treatment indicators parameter field or no call offering treatment parameter field at all, the call will be released using cause value #21 (call rejected) without diagnostics in the REL message. + +NOTE – If the functionality required for this procedure is not implemented in the DLE the call to be offered indicator will be regarded as an unknown parameter value and treated as described in 2.9.5.3.3/Q.764 [10]. The compatibility information for the call offering treatment indicators parameter field is given in Appendix I. + +### **10.1.11 Actions in an intermediate exchange** + +#### **10.1.11.1 In an intermediate exchange not starting timer T9** + +An intermediate exchange not starting timer T9 shall not modify the UID capability and UID action indicators parameters, these two parameters shall be passed on transparently. + +#### **10.1.11.2 In an intermediate exchange starting timer T9** + +On receipt of the UID capability parameter, the intermediate exchange shall pass it on transparently to the succeeding exchange, if it has the capability to stop or not to start T9 timer upon receipt of the + +UID action indicators parameter with bit B coded 1. Otherwise, the bit B of the UID capability parameter shall be set to 0. + +On receipt of the UID action indicators parameter indicating "stop or do not start T9 timer" (bit B coded 1), the intermediate exchange shall not start/shall stop timer T9 and shall start timer $T_{UID}$ to guard the connection. If $T_{UID}$ was already running upon receipt of the UID action indicators parameter with bit B coded 1, then $T_{UID}$ shall be restarted. + +The UID action indicators parameter shall be passed on transparently to the preceding exchange. + +Upon receipt of an ANM or CON message, the intermediate exchange shall stop T9 or $T_{UID}$ , if running. + +If $T_{UID}$ expires, see 10.1.4.2 (Timer $T_{UID}$ expiry). + +### **10.1.12 Actions in international gateway exchanges** + +The UID action indicators and UID capability indicators parameters are only sent across the international interface if a bilateral agreement between both network operators exists. + +## **10.2 Bearer unrelated connections** + +For further study. + +# **11 Interaction with other networks** + +For further study. + +# **12 Interaction between IN basic call and ISDN supplementary services** + +The description in this clause assumes that the SCF controls IN service(s) dependent on whether ISDN supplementary services are influenced for a call. + +An overview on the interactions between IN services and ISDN supplementary services is given in Table 19. + +The second column of the table marked "possibly impacted by IN services" identifies the ISDN supplementary services for which SCF control is needed. As a consequence, indications "impact/no impact" are required for these supplementary services which are to be sent via the INAP in an appropriate operation (see Appendix II). The third column contains the reference to the subclause describing the action to be taken in case of "impact". The fourth column identifies the exchange where the action is to be performed. In the case the affected exchange is not the SSP itself, a new instruction indicator is needed which is to be transferred in an ISUP message to the originating or destination local exchange, or both respectively. + +**Table 19/Q.1601 – Interactions between IN basic call and ISDN supplementary services** + +| ISDN Supplementary service | ISUP protocol possibly impacted by IN services | if impacted by IN service(s) the following action will be performed | Affected exchange | +|-----------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------------------------------------|-------------------| +| Advice of charge at call setup | No | | | +| Advice of charge during the call | No | | | +| Advice of charge at the end of the call | No | | | +| Call deflection | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Call forwarding busy | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Call forwarding reply | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Call forwarding unconditional | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Calling line identification presentation
Calling line identification restriction | Yes | See 12.2 (Calling line identification presentation/restriction) | SSP | +| Call hold | No | | | +| Call waiting | No | | | +| Closed user group | No | | | +| Completion of calls to busy subscriber | Yes | See 12.3 (Completion of calls service) | SSP | +| Completion of calls on no reply | Yes | See 12.3 (Completion of calls service) | SSP | +| Add-on conference call | Yes | See 12.4 (Conference) | OLE/DLE | +| Connected line identification presentation
Connected line identification restriction | Yes | See 12.5 (Connected line identification presentation/restriction) | SSP | +| Direct-dialling-in | No | | | +| Explicit call transfer | Yes | See 12.6 (Explicit call transfer) | SSP | +| GVNS | No | | | +| International telecommunication charge card | No | | | +| Malicious call identification | Yes | See 12.7 (Malicious call identification) | SSP/DLE | +| Meet-me conference | No | | | +| Multilevel precedence and pre-emption | No | | | +| Multiple subscriber number | No | | | +| Reverse charging | Yes | National network specific | | +| Subaddressing | No | | | +| Terminal portability | No | | | + +**Table 19/Q.1601 – Interactions between IN basic call and ISDN supplementary services +(concluded)** + +| ISDN Supplementary service | ISUP protocol possibly impacted by IN services | if impacted by IN service(s) the following action will be performed | Affected exchange | +|---------------------------------|------------------------------------------------|---------------------------------------------------------------------|-------------------| +| Three party | Yes | See 12.8 (Three party) | OLE/DLE | +| User-to-user service 1 implicit | No | | | +| User-to-user service 1 explicit | No | | | +| User-to-user service 2 explicit | No | | | +| User-to-user service 3 explicit | No | | | + +## 12.1 Call diversion + +### 12.1.1 Actions in the service switching point + +If "suppress information" was received in the INAP serviceInteractionIndicatorsTwo (call diversion notification treatment indicator), then the following parameters shall be discarded, if received: + +- a) generic notification indicator parameter with "call is diverting"; +- b) call diversion information parameter; +- c) redirection number parameter; +- d) redirection number restriction parameter. + +### 12.1.2 Actions in the destination local exchange + +#### 12.1.2.1 Call forwarding unconditional + +Call forwarding unconditional activated by the ISDN subscriber is suppressed, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). The call is offered to the subscriber. + +#### 12.1.2.2 Call forwarding busy + +Call forwarding busy activated by the ISDN subscriber is not performed, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). The call is released using the appropriate cause in the REL message. + +#### 12.1.2.3 Call forwarding no reply + +Call forwarding on reply activated by the ISDN subscriber is not performed, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). Call offering to the subscriber continues. + +#### 12.1.2.4 Call deflection + +Call deflection requested by the ISDN subscriber is rejected, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). Call offering to the subscriber continues. + +## **12.2 Calling line identification presentation/restriction** + +### **12.2.1 Actions in the service switching point** + +If a callingPartyNumber parameter or GenericNumbers parameter has been received in the Connect operation, then the mapping of these parameters must not compromise existing services supported by ISUP [refer to Table 5 (Mapping of parameters from Connect to IAM)]. + +## **12.3 Completion of calls service** + +### **12.3.1 Completion of calls to busy subscriber** + +#### **12.3.1.1 Actions in the service switching point** + +If "reject call completion request" was received in the INAP serviceInteractionIndicator parameter (call completion treatment indicator), then in a received REL message a "CCBS possible" in the diagnostics field of the cause indicators is replaced with "CCBS not possible". + +### **12.3.2 Completion of calls on no reply** + +#### **12.3.2.1 Actions in the service switching point** + +If "reject call completion request" was received in the INAP serviceInteractionIndicator parameter (call completion treatment indicator), then in a received ACM (subscriber free) or CPG (alerting) message a "CCNR possible" in the CCNR Possible indicator parameter is replaced with "CCNR not possible". + +## **12.4 Conference** + +### **12.4.1 Actions in the originating or destination local exchange** + +A request from an ISDN subscriber to add a call to a conference is rejected, if "reject conference request" was received in the conference treatment indicators (conference acceptance indicator). + +If "reject conference request" is received in the conference treatment indicators (conference acceptance indicator) for a call which is part of a conference call, then this IN call is cleared. + +## **12.5 Connected line identification presentation/restriction** + +### **12.5.1 Actions in the service switching point** + +If "no impact" was received in the INAP serviceInteractionIndicatorsTwo (connected number treatment indicator), then a connected number parameter and a generic number parameter "additional connected number" are passed on unchanged. + +If "presentation restricted" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ANM or CON message, the address presentation restricted indicator is set to "presentation restricted". +- b) If a generic number parameter "additional connected number" has been received in the ANM or CON message, the address presentation restricted indicator is set to "presentation restricted". +- c) If a redirection number parameter has been received, a redirection number restriction parameter is sent in the ANM message with bits AB set to "presentation restricted". + +If "present called IN number" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ANM or CON message, the connected number parameter is modified as follows: + +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the IAM message; + +address presentation restricted indicator: 00 (presentation allowed); + +address signals: as received in the called party number and possible subsequent number parameters, until the ACM message was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable. +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +If "present called IN number restricted" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ANM or CON message, the connected number parameter is modified as follows: + +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the IAM message; + +address presentation restricted indicator: 01 (presentation restricted); + +address signals: as received in the called party number and possible subsequent number parameters, until the ACM message was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable. +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +## 12.6 Explicit call transfer + +### 12.6.1 Actions in the service switching point + +If "suppress information" was received in the INAP serviceInteractionIndicatorsTwo (call transfer notification treatment indicator), then the following parameter shall be discarded, if received: + +- a) generic notification indicator parameter with either "call transfer, alerting" or "call transfer, active"; +- b) call transfer number parameter. + +## 12.7 Malicious call identification + +### 12.7.1 Actions in the service switching point + +The service switching point shall pass a received IDR message transparently to the preceding exchange. The subsequent IRS message is passed transparently to the succeeding exchange. If bit A of the MCID request indicators was set to 1, then in addition to the normal procedure the service switching point shall include the charged party identification parameter, if available, into the IRS message. + +### 12.7.2 Actions in the destination local exchange + +If the MCID supplementary service is invoked by the called user, the registration of call information is extended by the registration of the called IN number and the charged party identification, if these parameters were received in the IAM or IRS message, respectively. + +## 12.8 Three party + +### 12.8.1 Actions in the originating or destination local exchange + +A request from an ISDN subscriber to establish a three-way conference is rejected, if for one call or both, respectively, "reject conference request" was received in the conference treatment indicators (conference acceptance indicator). + +If "reject conference request" is received in the conference treatment indicators (conference acceptance indicator) for a call which is part of a three-party call, then this IN call is cleared. + +# 13 Interactions between IN services + +Although the INAP [5] only supports a single point of control, i.e. one CCF/SSF combination interacts with only one SCF, it may happen, that multiple IN services are invoked for a call, if IN triggering occurs in different SSPs (see Figure 5). + +![Diagram showing a configuration with two SSPs involved in a call. Two Subscriber Station Packages (SSP) are shown, each containing a Service Switching Function (SSF) and a Control Center Function (CCF). Each SSP is connected to a Service Control Point (SCP) via an INAP link. The CCFs are connected via ISUP links. The left CCF is connected to an Originating Local Exchange (OLE) which is connected to a telephone via Access Signalling. The right CCF is connected to an OLE which is connected to a telephone via Access Signalling. The two CCFs are also connected to each other via an ISUP link. The diagram is labeled T11103760-99.](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +The diagram illustrates a network configuration for a three-party call involving two Subscriber Station Packages (SSPs). On the left, a telephone is connected to an Originating Local Exchange (OLE) through 'Access Signalling'. The OLE is connected to the first SSP via an ISUP link. Inside this SSP, the CCF (Control Center Function) is connected to the SSF (Service Switching Function). The SSF is connected to an SCP (Service Control Point) via an INAP link. The CCF of the first SSP is also connected to the CCF of the second SSP via another ISUP link. The second SSP has a similar internal structure with its own SSF and CCF, and its CCF is connected to its own SCP via an INAP link. The CCF of the second SSP is connected to another OLE, which is in turn connected to a second telephone through 'Access Signalling'. The diagram is labeled 'T11103760-99'. + +Diagram showing a configuration with two SSPs involved in a call. Two Subscriber Station Packages (SSP) are shown, each containing a Service Switching Function (SSF) and a Control Center Function (CCF). Each SSP is connected to a Service Control Point (SCP) via an INAP link. The CCFs are connected via ISUP links. The left CCF is connected to an Originating Local Exchange (OLE) which is connected to a telephone via Access Signalling. The right CCF is connected to an OLE which is connected to a telephone via Access Signalling. The two CCFs are also connected to each other via an ISUP link. The diagram is labeled T11103760-99. + +Figure 5/Q.1601 – Configuration with two SSPs involved in the call + +No signalling is provided in the ITU-T INAP (CS-2) and ISUP to support interactions between IN services. This topic will be discussed in future capability sets. + +# 14 Parameter values (timers) + +See Table 20. + +**Table 20/Q.1601 – ISUP timers for the SSP** + +| Symbol | Time-out value | Cause for initiation | Normal termination | At expiry | Reference | +|----------------------|----------------|-------------------------------------------------------------------|------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------| +| T SUS | SCF controlled | When SUS "network initiated" message is received | At receipt of RES "network initiated" or REL message | Initiate release procedure or inform SCF | Subclause 10.1.1.3 (Suspend, resume)
Subclause 10.1.3 (Detection Point processing) | +| T NoReply | SCF controlled | At receipt of ACM when DP ONA or TNA has been armed. (Note) | At receipt of ANM or REL message | Inform SCF | | +| T UID | 30 minutes | At receipt of UID action indicators parameter with bit B set to 1 | At receipt of ANM message | Initiate release procedure | Subclause 10.1.4.2 (Timer T UID expiry) | + +NOTE – Except for receipt of ACM with cause parameter. + +# ANNEX A + +## Signalling flows + +This annex contains arrow diagrams showing different types of IN calls. In case of discrepancies between the flows contained in this annex and the text in the main part of this ITU-T Recommendation, the text takes precedence. The signal flows on the access protocol are also indicated, but in a simplified manner for illustrative purposes only. + +The following abbreviations and notations are used in Figures A.1 to A.7: + +| | | +|-----------------|--------------------------------------------| +| A-SSP | Assisting SSP | +| AssReqInstr | AssistRequestInstruction operation | +| (DPx) | arm DP x | +| DPx ! | DP x encountered | +| DFC | DisconnectForwardConnection | +| CTR | ConnectToResource operation | +| EstTempConn | EstablishTemporaryConnection operation | +| I-SSP | Initiating SSP | +| P&C | PromptAndCollectUserInfo operation | +| ReqReportBCSMEv | RequestReportBCSMEEvent operation | +| ⊗ | Switchpath completed in backward direction | +| ⊕ | Switchpath completed in forward direction | +| ⊕ | Switchpath completed in both directions | +| ⊗ | Release switchpath | + +![Sequence diagram of IN basic call between User A, OLE, SSP, SCP, DLE, and User B. The diagram shows the flow of signaling messages like SETUP, IAM, ACM, CPG, ANM, and CONNECT between the entities.](c1df61cc3717e878a48e530218403403_img.jpg) + +``` + +sequenceDiagram + participant User A + participant OLE + participant SSP + participant SCP + participant DLE + participant User B + + Note left of OLE: (X) + User A->>OLE: + OLE-->>User A: + OLE->>SSP: IAM + SSP->>SCP: InitialDP + SCP-->>SSP: Connect + Note left of SSP: (X) + SSP->>OLE: ACM (no indication) + OLE->>SSP: CPG (alerting) + SSP->>SCP: IAM + Note left of DLE: (X) + SSP->>DLE: ACM (subscriber free) + DLE->>User B: + User B-->>DLE: + DLE->>User B: + User B-->>DLE: + Note left of DLE: (X) + DLE->>SSP: ANM + SSP->>OLE: ANM + OLE-->>User A: + OLE-->>User A: + +``` + +Sequence diagram of IN basic call between User A, OLE, SSP, SCP, DLE, and User B. The diagram shows the flow of signaling messages like SETUP, IAM, ACM, CPG, ANM, and CONNECT between the entities. + +T11103770-99 + +Figure A.1/Q.1601 – IN basic call + +![Sequence diagram for IN call with SCP request to collect further digits. Lifelines: User A, OLE, SSP, SCP, DLE, User B. The diagram shows the interaction between a user and a network element (OLE) which then interacts with a switching system (SSP) and a service control point (SCP) to collect digits before connecting to another user (User B) via a data link element (DLE).](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +sequenceDiagram + participant User A + participant OLE + participant SSP + participant SCP + participant DLE + participant User B + + Note left of User A: + User A->>OLE: + OLE-->>User A: + Note left of OLE: (X) + OLE->>SSP: IAM + SSP->>SCP: InitialDP + Note left of SSP: (DP 2) + SCP->>SSP: ReqRepBCSMEv + Note left of SSP: (DP 2) + SSP->>SCP: CollectInfo + Note left of OLE: + OLE->>SSP: SAM + Note left of OLE: + OLE->>SSP: SAM + Note left of SSP: (DP 2) + SSP->>SCP: EventRepBCSM + Note left of SSP: (DP 2) + SSP->>SCP: Connect + Note left of OLE: (X) + OLE->>SSP: ACM + Note left of OLE: (no indication) + Note left of SSP: (X) + SSP->>DLE: IAM + Note left of DLE: + DLE->>User B: + User B-->>DLE: + DLE-->>User B: + Note left of DLE: (subscriber free) + DLE->>SSP: ACM + Note left of SSP: (subscriber free) + DLE-->>User B: + Note left of DLE: (X) + DLE->>SSP: ANM + Note left of SSP: (alerting) + SSP->>OLE: CPG + Note left of OLE: (alerting) + OLE-->>User A: + Note left of OLE: (X) + OLE-->>User A: + +``` + +Sequence diagram for IN call with SCP request to collect further digits. Lifelines: User A, OLE, SSP, SCP, DLE, User B. The diagram shows the interaction between a user and a network element (OLE) which then interacts with a switching system (SSP) and a service control point (SCP) to collect digits before connecting to another user (User B) via a data link element (DLE). + +T11103780-99 + +Figure A.2/Q.1601 – IN call with SCP request to collect further digits + + + +![Sequence diagram for IN call with user interactive dialogue (in-band). Lifelines: User A, OLE, SSP, SCP. The diagram shows the flow of messages between these entities, including setup, progress, and connect phases, with a user interactive dialogue block.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +``` + +sequenceDiagram + participant User A + participant OLE + participant SSP + participant SCP + + Note right of OLE: T7 + Note right of OLE: T9 + + User A->>OLE: + OLE-->>User A: + OLE->>SSP: IAM + SSP->>SCP: InitialDP + SCP-->>SSP: CTR/P&C + SSP-->>OLE: ACM + Note right of OLE: (no indication, in-band info) + OLE-->>User A: (p.i.#8) + SSP-->>OLE: ANM + OLE-->>User A: + + Note over User A, OLE, SSP: User interactive dialogue + + SSP->>SCP: Result: P&C + SCP-->>SSP: DFC/Connect + SSP-->>OLE: IAM + Note right of OLE: T7 + Note right of OLE: T9 + SSP-->>OLE: ACM + Note right of OLE: (subscriber free) + SSP-->>OLE: ANM + SSP-->>OLE: CPG (progress) + SSP-->>OLE: CPG (progress) + +``` + +The sequence diagram illustrates the interaction for an IN call with user interactive dialogue (in-band). The lifelines are User A, OLE, SSP, and SCP. The process begins with User A sending a message to OLE, which responds with . OLE then sends an IAM message to SSP. SSP forwards InitialDP to SCP, which returns CTR/P&C. SSP sends ACM to OLE, noting "no indication, in-band info". OLE sends (p.i.#8) to User A. SSP sends ANM to OLE, which then sends to User A. A "User interactive dialogue" block occurs. SSP sends Result: P&C to SCP, which returns DFC/Connect. SSP sends IAM to OLE. SSP then sends ACM to OLE, noting "(subscriber free)". SSP sends ANM to OLE. Finally, SSP sends two CPG (progress) messages to OLE. Timing constraints T7 and T9 are indicated on the OLE lifeline. + +Sequence diagram for IN call with user interactive dialogue (in-band). Lifelines: User A, OLE, SSP, SCP. The diagram shows the flow of messages between these entities, including setup, progress, and connect phases, with a user interactive dialogue block. + +T11103800-99 + +**Figure A.4/Q.1601 – IN call with user interactive dialogue (in-band) SSP supports requested IP capabilities OLE does not support UID capabilities** + +![Sequence diagram for Figure A.5/Q.1601 showing the procedure in initiating SSP. Lifelines: I-SSP and SCP. The sequence starts with an external IAM to I-SSP. I-SSP sends InitialIDP to SCP, which responds with EstTempConn. I-SSP then sends an internal IAM (with Scf ID and Correlation ID) to the right. The right side returns ACM, CPG, and ANM messages. I-SSP receives DFC/Connect from the right and sends a REL message. A note indicates that other operations may be received instead of Connect. The diagram is labeled T11103810-99.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +``` + +sequenceDiagram + participant External + participant I-SSP + participant SCP + External->>I-SSP: IAM + I-SSP->>SCP: InitialIDP + SCP-->>I-SSP: EstTempConn + I-SSP->>External: ACM (no indication) + Note right of I-SSP: (Note) + I-SSP->>External: IAM (Scf ID and Correlation ID) + External-->>I-SSP: ACM + External-->>I-SSP: CPG + External-->>I-SSP: ANM + External-->>I-SSP: DFC/Connect + Note right of I-SSP: (Note) + I-SSP->>External: REL + Note right of I-SSP: T11103810-99 + +``` + +Sequence diagram for Figure A.5/Q.1601 showing the procedure in initiating SSP. Lifelines: I-SSP and SCP. The sequence starts with an external IAM to I-SSP. I-SSP sends InitialIDP to SCP, which responds with EstTempConn. I-SSP then sends an internal IAM (with Scf ID and Correlation ID) to the right. The right side returns ACM, CPG, and ANM messages. I-SSP receives DFC/Connect from the right and sends a REL message. A note indicates that other operations may be received instead of Connect. The diagram is labeled T11103810-99. + +NOTE – Instead of Connect other operations may be received. If Connect is received, a normal call setup as shown in Figure A.3 will be performed. + +**Figure A.5/Q.1601 – IN call with user interactive dialogue (in-band) +Assist method; procedure in initiating SSP** + +![Sequence diagram for Figure A.6/Q.1601 showing the procedure in assisting SSP. Lifelines: A-SSP and SCP. The sequence starts with an external IAM (with Scf ID and Correlation ID) to A-SSP. A-SSP sends AssReqInstr to SCP, which responds with CTR/P&C. A-SSP then sends ACM (no indication) and ANM messages to the left. A 'User interactive dialogue' block occurs between A-SSP and the left. A-SSP sends a REL message to the left and receives a RLC message. A-SSP then sends a Result: P&C message to SCP. The diagram is labeled T11103820-99.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant External + participant A-SSP + participant SCP + External->>A-SSP: IAM (Scf ID and Correlation ID) + A-SSP->>SCP: AssReqInstr + SCP-->>A-SSP: CTR/P&C + A-SSP->>External: ACM (no indication) + A-SSP->>External: ANM + Note left of A-SSP: User interactive dialogue + A-SSP->>External: REL + External-->>A-SSP: RLC + A-SSP->>SCP: Result: P&C + Note right of A-SSP: T11103820-99 + +``` + +Sequence diagram for Figure A.6/Q.1601 showing the procedure in assisting SSP. Lifelines: A-SSP and SCP. The sequence starts with an external IAM (with Scf ID and Correlation ID) to A-SSP. A-SSP sends AssReqInstr to SCP, which responds with CTR/P&C. A-SSP then sends ACM (no indication) and ANM messages to the left. A 'User interactive dialogue' block occurs between A-SSP and the left. A-SSP sends a REL message to the left and receives a RLC message. A-SSP then sends a Result: P&C message to SCP. The diagram is labeled T11103820-99. + +**Figure A.6/Q.1601 – IN call with user interactive dialogue (in-band) +Assist method; procedure in assisting SSP** + +![Sequence diagram showing the interaction between an I-SSP and an SCP for an IN call with user interactive dialogue (in-band) hand-off method. The diagram shows the procedure in the initiating SSP. Messages include IAM, InitialDP, Connect (Scf ID and CorrelationID), ACM (no indication), CPG, and ANM. The I-SSP sends an IAM to the SCP, which responds with InitialDP. The I-SSP then sends a Connect message to the SCP, which responds with Connect (Scf ID and CorrelationID). The I-SSP then sends an ACM (no indication) to the CPG, which responds with CPG. The I-SSP then sends an ANM to the CPG, which responds with ANM.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +``` + +sequenceDiagram + participant External + participant I-SSP + participant SCP + External->>I-SSP: IAM + I-SSP->>SCP: InitialDP + SCP-->>I-SSP: Connect (Scf ID and CorrelationID) + I-SSP->>External: ACM (no indication) + I-SSP->>CPG: CPG + CPG-->>I-SSP: CPG + I-SSP->>ANM: ANM + ANM-->>I-SSP: ANM + +``` + +T11103830-99 + +Sequence diagram showing the interaction between an I-SSP and an SCP for an IN call with user interactive dialogue (in-band) hand-off method. The diagram shows the procedure in the initiating SSP. Messages include IAM, InitialDP, Connect (Scf ID and CorrelationID), ACM (no indication), CPG, and ANM. The I-SSP sends an IAM to the SCP, which responds with InitialDP. The I-SSP then sends a Connect message to the SCP, which responds with Connect (Scf ID and CorrelationID). The I-SSP then sends an ACM (no indication) to the CPG, which responds with CPG. The I-SSP then sends an ANM to the CPG, which responds with ANM. + +**Figure A.7/Q.1601 – IN call with user interactive dialogue (in-band) +Hand-off method; procedure in initiating SSP** + +# APPENDIX I + +## Coding of the compatibility information for the parameters + +See Table I.1. + +**Table I.1/Q.1601 – Coding of the instruction indicators** + +Default = 0 value for the subfield. + +| Parameter | Pass on not possible indicator | Discard parameter indicator | Discard message indicator | Send notification indicator | Release call indicator | Transit at intermediate exchange indicator | Broadband/narrow-band interworking indicator | +|--------------------------------------------|--------------------------------|-----------------------------|---------------------------|-----------------------------|------------------------|--------------------------------------------|----------------------------------------------| +| Call diversion treatment indicators | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Called IN number | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Call offering treatment indicators | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Charged party identification | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Conference treatment indicators | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | + +**Table I.1/Q.1601 – Coding of the instruction indicators (concluded)** + +Default = 0 value for the subfield. + +| Parameter | Pass on not possible indicator | Discard parameter indicator | Discard message indicator | Send notification indicator | Release call indicator | Transit at intermediate exchange indicator | Broadband/narrow-band interworking indicator | +|----------------------------------|---------------------------------------|------------------------------------|----------------------------------|------------------------------------|-------------------------------|---------------------------------------------------|-----------------------------------------------------| +| Correlation id | Release call | Default | Default | Default | Release call | Transit interpretation | Pass on | +| Display information | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| SCF id | Release call | Default | Default | Default | Release call | Transit interpretation | Pass on | +| UID action indicators | Discard parameter | Discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| UID capability indicators | Discard parameter | Discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Original Called IN number | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | + +# **APPENDIX II** + +## **Contents of the INAP serviceInteractionIndicatorsTwo** + +The appendix contains a list of indicators which are to be transferred in the serviceInteractionIndicatorsTwo via the INAP in order to allow the SCF to control the network behaviour for IN calls. This appendix should be considered as a proposal for the INAP to transfer this type of information and not as a requirement for the detailed encoding of the serviceInteractionIndicatorsTwo. See Tables II.1 and II.2. + +**Table II.1/Q.1601 – Basic call related control information** + +| Control information | Values | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| Call to be offered indicator. |
  • – Call offering allowed
  • – Call offering not allowed (default)
| +| Time limits for timer T SUS . |
  • – As in Q.764 for timer T6
  • – 4-10 s
  • – 0 s (default)
| +| Bothway throughconnect indicator.
NOTE 1 – The indicator should be set to "required" in the ConnectToResource or EstablishTemporaryConnection operation, if user interaction has to be performed. If an announcement is to be connected or in other operations the indicator should be set to "not required". |
  • – Required (default)
  • – Not required
| +| Called IN number presentation restricted indicator. |
  • – Presentation allowed
  • – Presentation not allowed (default)
| +| User interactive dialogue duration indicator
NOTE 2 – The indicator should be set to "long duration" in the ConnectToResource or EstablishTemporaryConnection operation, if the user interaction may last longer than 90 seconds. Otherwise the indicator should be set to "short duration". |
  • – Long duration (default)
  • – Short duration
| + +**Table II.2/Q.1601 – Supplementary service related control information** + +| Control information | Values | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call to be diverted indicator |
  • – Call diversion allowed (default)
  • – Call diversion not allowed
| +| Conference at DLE acceptance indicator |
  • – Accept conference request (default)
  • – Reject conference request
| +| Conference at OLE acceptance indicator |
  • – Accept conference request (default)
  • – Reject conference request
| +| Connected number treatment indicator |
  • – No impact
  • – Set "presentation restricted"
  • – Present called IN number (default)
| +| Call transfer notification treatment indicator |
  • – No impact (default)
  • – Suppress information
| +| Call diversion notification treatment indicator |
  • – No impact (default)
  • – Suppress information
| +| Call completion treatment indicator |
  • – Reject call completion request
  • – Accept call completion request (default)
| + +# APPENDIX III + +## Limitations for ISUP basic call procedures and supplementary services for different types of IN calls + +The appendix provides an overview on the limitations for ISUP basic call procedures and supplementary services for different types of IN calls. + +The CCBS supplementary service is in general not available for IN calls that require translation of the called party number. Additional limitations are listed in Table III.1. + +**Table III.1/Q.1601 – Limitations for ISUP basic call procedures and supplementary services** + +| Type of IN call →
↓
ISUP feature | IN call with DPs armed in the request mode (except DP CI) | IP connection without sending of ANM | IP connection with sending of ANM | IN call setup after an ANM was sent for a previous connection | +|-----------------------------------------------|-----------------------------------------------------------|--------------------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Basic call | | | | | +| Access delivery information | | | | Not supported | +| Connection types allowing fallback capability | Not supported | Not supported | Not supported | Not supported | +| Propagation delay determination | | | | In the OLE only the accumulated delay from the OLE to the first answered destination is available. | +| Supplementary Services | | | | | +| Call diversion | | | | The OLE does not receive the following parameters: call diversion information, generic notification indicator, redirection number and redirection number restriction indicator. | +| Call waiting | | | | The generic notification indicator cannot be delivered to the calling user. | +| COLP | | | | The connected number and generic number received from the destination local exchange cannot be delivered to the calling user. | + +**Table III.1/Q.1601 – Limitations for ISUP basic call procedures +and supplementary services (*concluded*)** + +| Type of IN call →
↓
ISUP feature | IN call with DPs armed in the request mode (except DP CI) | IP connection without sending of ANM | IP connection with sending of ANM | IN call setup after an ANM was sent for a previous connection | +|----------------------------------------|-----------------------------------------------------------|--------------------------------------|-----------------------------------|---------------------------------------------------------------| +| UUS1 implicit | Not supported | | Not supported | | +| UUS1 explicit | Not supported | | Not supported | | +| UUS2 explicit | Not supported | | Not supported | | +| UUS3 explicit | Not supported | | Not supported | | + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1708-200810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1708-200810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0141e9f4ebd088f2d51654cf964299a97d21ac27 --- /dev/null +++ b/marked/Q/T-REC-Q.1708-200810-I_PDF-E/raw.md @@ -0,0 +1,624 @@ + + +**ITU-T** + +**Q.1708/Y.2805** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/2008) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS +AND NEXT-GENERATION NETWORKS + +Next Generation Networks – Generalized mobility + +# --- Framework of location management for NGN + +Recommendation ITU-T Q.1708/Y.2805 + +## ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T Q.1708/Y.2805** + +# **Framework of location management for NGN** + +## **Summary** + +Recommendation ITU-T Q.1708/Y.2805 specifies the framework of IP-based location management for next generation networks. The location management is responsible for mapping among user identifier and location identifiers of the user equipment. This Recommendation describes the design considerations, functional architecture, and information flows for the location management function. + +## **Source** + +Recommendation ITU-T Q.1708/Y.2805 was approved on 14 October 2008 by ITU-T Study Group 19 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Location management, NGN. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined in [ITU-T Q.1707]..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Design considerations..... | 3 | +| 5.1 MM identifiers..... | 3 | +| 5.2 LM operations ..... | 4 | +| 5.3 LM for data packet delivery ..... | 5 | +| 6 Functional reference architecture ..... | 5 | +| 6.1 Functional entities ..... | 5 | +| 6.2 Reference points ..... | 6 | +| 7 Information flows for non-roaming UE..... | 8 | +| 7.1 Host-based LM ..... | 8 | +| 7.2 Network-based LM..... | 9 | +| 8 Information flows for roaming UE..... | 10 | +| 8.1 Host-based LM ..... | 11 | +| 8.2 Network-based LM..... | 12 | +| Bibliography..... | 13 | + +# Introduction + +This Recommendation describes the framework of mobility management (MM) for next generation networks (NGN). This work has been motivated from the observation that NGN continues to evolve towards the convergence of fixed and wireless/mobile networks, and thus mobility management is an essential functionality needed to provide seamless mobility to NGN users and services. + +This Recommendation is a part of the MM framework for NGN. The MM framework will be designed with a series of Recommendations, rather than a single Recommendation, as a suite of the framework of mobility management for NGN. The design of the MM framework includes a variety of technical issues to be addressed. Those design issues are associated with a wide variety of mobility scenarios and protocols. The MM framework Recommendations are: + +- Recommendation Q.1707/Y.2804: Generic framework of mobility management for next generation networks; +- Recommendation Q.1708/Y.2805: Framework of location management for NGN; +- Recommendation Q.1709/Y.2806: Framework of handover control for NGN; + +## Recommendation ITU-T Q.1708/Y.2805 + +# Framework of location management for NGN + +# 1 Scope + +This Recommendation describes the framework of IP-based location management (LM) for NGN, which includes design considerations, functional architecture, and information flows for location management. This Recommendation focuses on terminal mobility when mobile terminals move around and change their IP addresses in the NGN. This Recommendation also focuses on the mobility management (MM) schemes that operate in the network or IP layers, whereas the issues on the mobility support in the service stratum will be addressed in another Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.1706] Recommendation ITU-T Q.1706/Y.2801 (2006), *Mobility management requirements for NGN*. +- [ITU-T Q.1707] Recommendation ITU-T Q.1707/Y.2804 (2008), *Generic framework of mobility management for next generation networks*. +- [ITU-T Q.1709] Recommendation ITU-T Q.1709/Y.2806 (2008), *Framework of handover control for NGN*. +- [ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN*. +- [ITU-T Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for Next Generation Networks*. +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. +- [ITU-T Y.2014] Recommendation ITU-T Y.2014 (2008), *Network attachment control functions in next generation networks*. +- [ITU-T Y.2091] Recommendation ITU-T Y.2091 (2007), *Terms and definitions for next generation networks*. +- [ITU-T Y.2111] Recommendation ITU-T Y.2111 (2006), *Resource and admission control functions in next generation networks*. + +# 3 Definitions + +## 3.1 Terms defined in [ITU-T Q.1707] + +This Recommendation uses the following terms defined in [ITU-T Q.1707]: + +**3.1.1 location identifier (LID):** A topological location identifier of a UE. An IP address can be used as a location identifier. Refer also to [ITU-T Y.2091]. + +**3.1.2 user identifier (UID):** A series of digits, characters and symbols or any other form of data that are used to identify a subscriber (user) or user equipment in the NGN. Refer also to [ITU-T Y.2091]. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 persistent LID (PLID):** A LID that does not change even when a mobile user equipment (MUE) moves across different access networks or IP subnets. + +**3.2.2 temporary LID (TLID):** A LID that changes when a mobile user equipment (MUE) moves across different access networks or IP subnets. + +**3.2.3 LID binding update (LBU):** An operation of location management to manage the mapping between persistent LIDs (PLIDs) and temporary LIDs (TLIDs). + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|--------|--------------------------------------------------| +| ALM | Access Location Management | +| ALM-FE | Access Location Management Functional Entity | +| CLM | Central Location Management | +| CLM-FE | Central Location Management Functional Entity | +| CoA | Care of Address | +| CUE | Corresponding User Equipment | +| DHCP | Dynamic Host Configuration Protocol | +| FE | Functional Entity | +| FRA | Functional Requirements and Architecture for NGN | +| HCF | Handover Control Function | +| HoA | Home Address | +| HSDPA | High Speed Downlink Packet Access | +| ID | Identifier | +| IMSI | International Mobile Subscriber Identifier | +| IP | Internet Protocol | +| L3 | Layer 3 | +| LBU | LID Binding Update | +| LID | Location Identifier | +| LM | Location Management | +| LMF | Location Management Function | +| LM-FE | Location Management FE | +| MIP | Mobile IP | +| MIPv6 | Mobile IPv6 | +| MM | Mobility Management | + +| | | +|-------|-------------------------------------------------| +| MMCF | Mobility Management Control Function | +| MUE | Mobile User Equipment | +| NACF | Network Attachment Control Function | +| NAI | Network Access Identifier | +| NGN | Next Generation Network | +| PLID | Persistent LID | +| RACF | Resource Admission Control Function | +| TF | Transport Function | +| TLID | Temporary LID | +| UE | User Equipment | +| UID | User Identifier | +| URI | Uniform Resource Identifier | +| Wi-Fi | Wireless Fidelity | +| WiMAX | Worldwide interoperability for Microwave Access | + +# 5 Design considerations + +## 5.1 MM identifiers + +The identifiers for MM can be classified into user ID (UID) and location ID (LID). The location ID can be further classified into persistent LID (PLID) and temporary LID (TLID). + +### 5.1.1 User identifier (UID) + +A UID represents a user or UE in the NGN. The UID can be in a variety of formats such as uniform resource identifier (URI), network access identifier (NAI), international mobile subscriber identifier (IMSI), etc. In this Recommendation, it is assumed that a UID is given to a user that has subscribed to the NGN mobility service. + +### 5.1.2 Location identifier (LID) + +The location management (LM) functionality is used to keep track of mobile user equipments (UEs) in the network by identifying and maintaining the location information of the concerned mobile UEs. Such location information or location identifier (LID) is classified into 'physical' LID and 'logical' LID. The physical LID represents the geographical location of the mobile UE. The logical LID includes an IP address for routing/forwarding IP packets to the mobile UE in the network. + +This Recommendation does not consider the physical or geographical LID. This Recommendation considers only the logical LID, and focuses on the use of the IP address as LID. From the point of view of IP-based LM, a logical LID, or IP address, can be further classified into persistent LIDs (PLIDs) and temporary LIDs (TLIDs). + +### 5.1.3 Persistent LID (PLID) + +A typical example of PLID is the home address (HoA), which is defined in the mobile IP (MIP). When a mobile UE (MUE) is connected to the network at the initial power-on, a PLID should be statically or dynamically allocated to the MUE. + +In order to support session continuity of MUEs, the PLID may not be changed, even if an MUE moves into another IP subnet. In this sense, this LID is called 'persistent'. In some cases, however, a + +PLID may be newly configured, for example, when the MUE is reconnected to the network after a failure or power-off, or when it enters a new local domain in a localized MM scheme. + +### 5.1.4 Temporary LID (TLID) + +A typical example of TLID is the care-of address (CoA) of MIP. When an MUE moves into another IP subnet, it will obtain a new TLID, as seen in the example of MIPv6 CoA. + +In host-based LM, a TLID should be dynamically allocated to the MUE, possibly through DHCP. In network-based LM, an IP address of the concerned access router may be used as TLID of an MUE. + +## 5.2 LM operations + +IP-based LM is used to manage the mappings between UID and PLID, and between PLID and TLID for each MUE. In this respect, LM operations consist of: + +- UID binding operation for mapping between UID and PLID; +- LID binding operation for mapping between PLID and TLID. + +This Recommendation focuses on the LID binding operation. + +On the other hand, it is noted that paging management is one of the essential functionalities that can be used with location management. However, the IP-based paging function is for further study. The paging function is outside the scope of this Recommendation. + +### 5.2.1 UID binding operation + +The UID binding operation is used to manage the mapping between the UID and the PLID for each mobile UE. A UID is assigned to an NGN user on the subscription basis, whereas a PLID represents an IP address. + +The UID binding information should be registered when an MUE gets a PLID. Such information will be updated if the PLID is re-configured by the MUE. It is noted that UID binding operation schemes are quite dependent on the type of UID associated with the user (e.g., URI, IMSI, or UE identifier, etc.). This implies that there may be a variety of schemes or scenarios for UID binding management. This Recommendation does not deal with the details of UID binding management schemes. + +### 5.2.2 LID binding operation + +The LID binding operation is used to manage the mapping between PLID and TLID for each mobile UE. The LID binding update (LBU) operation will be used for LID binding management. This Recommendation focuses on the LID binding operation, rather than on the UID binding operation. + +When an MUE is initially connected to the network, an 'initial' LBU operation is performed. In host-based LM, when the MUE gets a TLID from the network, it should register its TLID with the LM-related functional entity. In network-based LM, in which the IP address of a network agent is used as TLID, the LBU operation will be performed by the corresponding LM-related functional entity in the network. Each time an MUE moves into a new IP subnet and thus its TLID changes, the LBU is performed. + +### 5.2.3 Consideration of multiple interfaces + +An MUE may have multiple PLIDs when an MUE gets access to the different NGN service providers in which the mobility services are offered to the MUE. An MUE may also have multiple TLIDs. For example, one TLID per each interface may be allocated to an MUE with multiple interfaces, which allows the MUE to use various types of network interfaces to maintain a wide area + +network connectivity. Note that an MUE may have one TLID even when it has multiple PLIDs and also may have one PLID even when it has multiple TLIDs. + +If multiple PLIDs are allocated to an MUE, the LBU operation for each PLID may be performed with different CLM-FE. In addition, if multiple TLIDs are allocated to an MUE, the LID binding operation should be able to bind multiple TLIDs to each PLID. + +As a typical example, an MUE with multiple interfaces may have one PLID and multiple TLIDs, one TLID per interface. When the MUE is initially connected to an access network through one of its interfaces, its PLID is bound to a TLID for the interface. Then, if there is another available interface for the MUE, the MUE may also be connected to an access network through that interface and its PLID is also bound to the TLID of the interface. Note that when another TLID is bound to a PLID, the existing TLIDs bound to the PLID should not be overwritten. In addition, there should be a proper mechanism to revoke the binding between PLID and TLID. The detailed architecture and signalling flow are out of scope of this Recommendation and are for further study. + +### **5.2.4 Dynamic assignment of LM functional entity** + +The dynamic assignment mechanism of the LM functional entity (LM-FE) may be supported during the location registration according to the requirements of load balancing, administrative policies and so on. If an LBU request (LBU\_Request) to a location management functional entity is responded to by an LBU response (LBU\_Response) with failure notification or redirection information, an LBU\_Request to the other location management functional entity will be tried. + +## **5.3 LM for data packet delivery** + +For data packet delivery or call/session establishment between corresponding UE (CUE) and MUE, the current location information of the MUE needs to be identified. The LM or LM-related functional entity will be used to provide the location information of MUE for data packet delivery or call/session establishment. + +The detailed scheme of data packet delivery or session establishment may depend on the associated service control functions or mechanisms (e.g., with or without the session setup signalling). By this, there may be a variety of operational scenarios for finding the location information of MUE (e.g., PLID or TLID) via interworking between the LM-related functional entity and the service control function. The details of the scenarios for data packet delivery or session establishment are outside the scope of this Recommendation. + +This Recommendation focuses on the functional architecture and information flows only for the LBU operation in terms of LM functionality. + +# **6 Functional reference architecture** + +## **6.1 Functional entities** + +As described in [ITU-T Q.1707], the MM control function (MMCF) consists of the location management function (LMF) and the handover control function (HCF). The LMF can be achieved with the following functional entities (FEs): + +- Access LM-FE (ALM-FE); +- Central LM-FE (CLM-FE). + +These are the logical FEs defined for location management. These FEs may be located on a single physical entity, or may be implemented into one or more physical FEs. From the NGN-FRA point of view, an LM-FE may be further divided into one or more FEs, but that is outside the scope of this Recommendation. + +Figure 6-1 shows the architectural model of the LM function with the related LM-FEs. + +![Functional architecture of location management diagram](007b053fe94a8348f75128a584503fd0_img.jpg) + +The diagram illustrates the functional architecture of location management. It features a central 'Transport control function' block containing nested 'MMCF' and 'LMF' components. Inside the 'LMF' block, there is a hierarchy of 'CLM-FE' and 'ALM-FE' (with 'ALM-FE' nested under 'CLM-FE'), which interacts with an 'HCF' block. Below the 'LMF' block are 'NACF' and 'RACF' blocks. At the bottom of the central structure is a 'Transport function' block. To the left, a 'UE' (User Equipment) block contains an 'LMF' component connected to the 'Transport function'. To the right, an 'Other NGN' block also contains an 'LMF' component connected to the 'Transport function'. A legend at the bottom indicates that dashed lines represent 'Control flow' and solid lines represent 'Media flow'. The reference label 'Q.1708/Y.2805(08)\_F6-1' is located in the bottom right corner of the diagram area. + +Functional architecture of location management diagram + +**Figure 6-1 – Functional architecture of location management** + +As described in the figure, a UE may perform its own LMF function with the LM-FEs of the network in the host-based LM scheme. The LM-FEs in the network are organized into a two-level hierarchy of ALM-FE and CLM-FE. Each LM-FE performs the LBU operation for location management. + +In terms of MM, the LM-FEs can interact with the handover control function (HCF). Moreover, each LM-FE may have interaction with the following NGN functions: + +- Network Attachment Control Function (NACF); +- Resource Admission Control Function (RACF); +- Transport Function (TF). + +### 6.1.1 ALM-FE + +The ALM-FE is responsible for: + +- LBU operation with MUE and CLM-FE in host-based LM; +- LBU operation with CLM-FE in network-based LM. + +### 6.1.2 CLM-FE + +The CLM-FE is responsible for: + +- LBU operation with MUE and ALM-FE in host-based LM; +- LBU operation with ALM-FE in network-based LM. + +## 6.2 Reference points + +This clause identifies the reference points or interfaces used to describe the information flows for LM. + +### 6.2.1 Non-roaming case + +In the non-roaming case, the reference points for LM operations ( $L_{UA}$ , $L_{AC}$ , $L_{UC}$ ) are shown in Figure 6-2. + +![Diagram of reference points for LM in the non-roaming case](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +The diagram shows three stacked rectangular blocks representing network elements: CLM-FE at the top, ALM-FE in the middle, and UE at the bottom. A vertical line connects CLM-FE and ALM-FE, with a horizontal tick mark labeled $L_{AC}$ . Another vertical line connects ALM-FE and UE, with a horizontal tick mark labeled $L_{UA}$ . A curved line on the left side connects CLM-FE and UE, with a horizontal tick mark labeled $L_{UC}$ . Below the diagram is the text 'Q.1708/Y.2805(08)\_F6-2'. + +Diagram of reference points for LM in the non-roaming case + +**Figure 6-2 – Reference points for LM in the non-roaming case** + +In the non-roaming case, the LM scenarios can be classified as follows: + +- Host-based LM with ALM-FE +- Host-based LM without ALM-FE +- Network-based LM + +In the case of host-based LM using ALM-FE, two reference points are used: $L_{UA}$ between UE and ALM-FE, and $L_{AC}$ between ALM-FE and CLM-FE. In the case of host-based LM without ALM-FE, the reference point $L_{UC}$ between UE and CLM-FE is used. In the case of network-based LM, the reference point $L_{AC}$ between ALM-FE and CLM-FE is used. + +### 6.2.2 Roaming case + +In the roaming case, this Recommendation assumes that a roaming agreement has already been made between a home NGN provider and a visited NGN provider. The issues on authentication and authorization for roaming are outside the scope of this Recommendation. + +The reference points for LM operations in the roaming case ( $L_{UA}$ , $L_{AC}$ , $L_{UC}$ ) are shown in Figure 6-3. + +![Diagram of reference points for LM in the roaming case](2e399449b7f62d40167a65ca88888917_img.jpg) + +The diagram is split by a vertical dashed line into two sections: 'Visited NGN' on the left and 'Home NGN' on the right. In the Visited NGN section, there are three stacked rectangular blocks: ALM-FE at the top, UE in the middle, and another UE at the bottom. A vertical line connects the top ALM-FE and the middle UE, with a horizontal tick mark labeled $L_{UA}$ . A diagonal line connects the top ALM-FE to the CLM-FE block in the Home NGN section, with a horizontal tick mark labeled $L_{AC}$ . A diagonal line connects the bottom UE to the CLM-FE block, with a horizontal tick mark labeled $L_{UC}$ . The CLM-FE block is located in the Home NGN section. Below the diagram is the text 'Q.1708/Y.2805(08)\_F6-3'. + +Diagram of reference points for LM in the roaming case + +**Figure 6-3 – Reference points for LM in the roaming case** + +In the roaming case, the LM scenarios can be classified as follows: + +- Host-based LM with visited ALM-FE +- Host-based LM without visited ALM-FE +- Network-based LM + +In the case of host-based LM using the visited ALM-FE, the two reference points used are: $L_{UA}$ between roaming UE and visited ALM-FE, and $L_{AC}$ between visited ALM-FE and home CLM-FE. + +In the case of host-based LM without visited ALM-FE, the reference point $L_{UC}$ between roaming UE and home CLM-FE is used. + +In the case of network-based LM, the reference point $L_{AC}$ between visited ALM-FE and home CLM-FE is used. + +# 7 Information flows for non-roaming UE + +An MUE or ALM-FE starts the initial LBU procedure when it is initially attached to its home network. There are two architectures for describing the procedure, as follows. + +- Host-based location management + +An MUE starts performing the initial LBU procedure by exchanging LID binding update (LBU) messages with CLM-FE directly or via ALM-FE. + +- Network-based location management + +The ALM-FE that detects an MUE's attachment starts performing the initial LBU procedure by exchanging LBU messages with the CLM-FE in the home network. + +Note that this initial LBU procedure may be omitted depending on where the MUE is initially attached in the host-based location management. For example, when the MUE's PLID such as the HoA in MIP is topologically correct in respect to its access network, the MUE does not need to proceed with the initial LBU procedure. The initial LBU procedure also needs a data path setup procedure which may require HCF functions. The data path setup procedure is the same as in the handover case, which is described in [ITU-T Q.1709] in detail. Therefore, this Recommendation focuses on the location management procedure itself. + +## 7.1 Host-based LM + +When an MUE is attached to an access network, the MUE performs the initial LBU procedure in the host-based location management architecture. As shown in Figure 7-1, the host-based location management in the non-roaming case is using the interaction among MUE, ALM-FE and CLM-FE in a home network. After a successful LBU procedure, the relevant LMF entity will maintain the mapping between PLID and TLID. + +![Diagram of Host-based LBU architecture in the non-roaming case. A 'Home network' box contains a 'CLM-FE' at the top, a group of 'ALM-FE' boxes in the middle (indicated by '...'), and an 'MUE' at the bottom. Double-headed arrows connect the CLM-FE to the ALM-FE group, and the ALM-FE group to the MUE. A curved arrow on the left side of the box points from the MUE directly to the CLM-FE. A small label 'Q.1708/Y.2805(08)_F7-1' is at the bottom right of the diagram.](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +Home network + +CLM-FE + +ALM-FE ... ALM-FE + +MUE + +Q.1708/Y.2805(08)\_F7-1 + +Diagram of Host-based LBU architecture in the non-roaming case. A 'Home network' box contains a 'CLM-FE' at the top, a group of 'ALM-FE' boxes in the middle (indicated by '...'), and an 'MUE' at the bottom. Double-headed arrows connect the CLM-FE to the ALM-FE group, and the ALM-FE group to the MUE. A curved arrow on the left side of the box points from the MUE directly to the CLM-FE. A small label 'Q.1708/Y.2805(08)\_F7-1' is at the bottom right of the diagram. + +**Figure 7-1 – Host-based LBU architecture in the non-roaming case** + +Figures 7-2 and 7-3 show the information flow for the initial host-based LBU procedure in the non-roaming case. The MUE attached to its home network initially starts the initial LBU procedure with the CLM-FE by exchanging LBU messages directly or via an ALM-FE. Figures 7-2 and 7-3 are the LBU procedures with and without ALM-FE involvement, respectively. If an ALM-FE is involved, the ALM-FE may act as a proxy for the CLM-FE. When the CLM-FE receives the initial LBU\_Request message, it will respond with an LBU\_Response message to the MUE directly or via + +the ALM-FE. The LBU\_Response message may indicate whether the registration is successful or not. The reasons for failure of the registration may be various, which may include the overload condition of the CLM-FE or administration policies. In case of registration failure, the CLM-FE may respond with additional information such as redirection indication and a new CLM-FE information for the redirection, which makes the MUE re-initiate the LBU procedure with the new CLM-FE. If the LBU\_Response message is received with only redirection indication and without a new CLM-FE information, the MUE may try another candidate CLM-FE from the list of candidate CLM-FEs that the MUE maintains. + +![Sequence diagram for Figure 7-2: Host-based initial LBU procedure with ALM-FE in the non-roaming case. The diagram shows three entities: MUE, ALM-FE (Home network), and CLM-FE (Home network). The MUE sends a message to the ALM-FE, which then sends an 'Initial LBU' message to the CLM-FE. A return message is shown from the ALM-FE back to the MUE. The diagram is labeled Q.1708/Y.2805(08)_F7-2.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +Sequence diagram for Figure 7-2: Host-based initial LBU procedure with ALM-FE in the non-roaming case. The diagram shows three entities: MUE, ALM-FE (Home network), and CLM-FE (Home network). The MUE sends a message to the ALM-FE, which then sends an 'Initial LBU' message to the CLM-FE. A return message is shown from the ALM-FE back to the MUE. The diagram is labeled Q.1708/Y.2805(08)\_F7-2. + +**Figure 7-2 – Host-based initial LBU procedure with ALM-FE in the non-roaming case** + +![Sequence diagram for Figure 7-3: Host-based initial LBU procedure without ALM-FE in the non-roaming case. The diagram shows three entities: MUE, ALM-FE (Home network), and CLM-FE (Home network). The MUE sends a message directly to the CLM-FE, labeled 'Initial LBU'. A return message is shown from the CLM-FE back to the MUE. The diagram is labeled Q.1708/Y.2805(08)_F7-3.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Sequence diagram for Figure 7-3: Host-based initial LBU procedure without ALM-FE in the non-roaming case. The diagram shows three entities: MUE, ALM-FE (Home network), and CLM-FE (Home network). The MUE sends a message directly to the CLM-FE, labeled 'Initial LBU'. A return message is shown from the CLM-FE back to the MUE. The diagram is labeled Q.1708/Y.2805(08)\_F7-3. + +**Figure 7-3 – Host-based initial LBU procedure without ALM-FE in the non-roaming case** + +If the MUE has multiple interfaces such as Wi-Fi, HSDPA, WiMAX, etc., and multiple TLIDs are allocated to each interface, it may perform multiple LBU procedures with the CLM-FE, and then the LID binding operation might bind multiple TLIDs to a PLID. In addition, if multiple PLIDs are allocated to the MUE, it may perform multiple LBU procedures with multiple CLM-FEs for each PLID. + +## 7.2 Network-based LM + +When an MUE is attached to an access network, the ALM-FE that detects the MUE's attachment performs the initial LBU procedure in the network-based LM. As shown in Figure 7-4, the network-based location management in the non-roaming case is based on the interaction between ALM-FE and CLM-FE. After a successful LBU procedure, the relevant LM-FE will maintain the mapping information between TLID and PLID. + +![Diagram for Figure 7-4: Network-based LBU architecture in the non-roaming case. A box labeled 'Home network' contains a 'CLM-FE' at the top, connected by a double-headed arrow to a group of 'ALM-FE' units (indicated by 'ALM-FE ... ALM-FE'). Below the 'Home network' box is a separate box labeled 'MUE'. The diagram is labeled Q.1708/Y.2805(08)_F7-4.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +Diagram for Figure 7-4: Network-based LBU architecture in the non-roaming case. A box labeled 'Home network' contains a 'CLM-FE' at the top, connected by a double-headed arrow to a group of 'ALM-FE' units (indicated by 'ALM-FE ... ALM-FE'). Below the 'Home network' box is a separate box labeled 'MUE'. The diagram is labeled Q.1708/Y.2805(08)\_F7-4. + +**Figure 7-4 – Network-based LBU architecture in the non-roaming case** + +Figure 7-5 shows the information flow for the initial network-based LBU procedure in the non-roaming case. An ALM-FE that detects an MUE's initial attachment starts the initial LBU procedure with CLM-FE by exchanging LBU messages. When the CLM-FE receives the initial LBU\_Request message from the ALM-FE, it will respond with an LBU\_Response message to the ALM-FE. The LBU\_Response message indicates whether the registration is successful or not. The reasons for failure may be various, which include the overload condition of the CLM-FE and administration policies. In case of registration failure, the CLM-FE may respond with additional information such as redirection indication and new CLM-FE information for the redirection, which makes the ALM-FE re-initiate the LBU procedure with the new CLM-FE. If the LBU\_Response message is received with only redirection indication and without new CLM-FE information, the ALM-FE may try another candidate CLM-FE from the list of candidate CLM-FEs that the ALM-FE maintains. + +![Sequence diagram showing the network-based initial LBU procedure in the non-roaming case. The diagram features three vertical lifelines: MUE, ALM-FE (Home network), and CLM-FE (Home network). A horizontal arrow labeled 'Initial LBU' points from the ALM-FE to the CLM-FE. A return arrow points from the CLM-FE back to the ALM-FE. The text 'Q.1708/Y.2805(08)_F7-5' is located at the bottom right of the diagram.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +Sequence diagram showing the network-based initial LBU procedure in the non-roaming case. The diagram features three vertical lifelines: MUE, ALM-FE (Home network), and CLM-FE (Home network). A horizontal arrow labeled 'Initial LBU' points from the ALM-FE to the CLM-FE. A return arrow points from the CLM-FE back to the ALM-FE. The text 'Q.1708/Y.2805(08)\_F7-5' is located at the bottom right of the diagram. + +**Figure 7-5 – Network-based initial LBU procedure in the non-roaming case** + +If the MUE has multiple interfaces such as Wi-Fi, HSDPA, WiMAX, etc., and each interface is attached to different ALM-FEs, each ALM-FE may perform its own LBU procedure with the same CLM-FE, and then the LID binding operation may bind multiple TLIDs to a PLID. On the other hand, if multiple PLIDs are allocated to the MUE, it may perform multiple LBU procedures with the respective CLM-FEs for each PLID or multiple LBU procedures with the same CLM-FE to create multiple mappings of TLID and PLID in the CLM-FE. + +# 8 Information flows for roaming UE + +When an MUE roams to a visited network, there are two possible scenarios from the IP address allocation point of view. First, a new IP address may be allocated, regardless of which IP address was allocated to the MUE in its home network. That is, a new PLID can be allocated to the MUE in the visited network. On the other hand, the PLID will be maintained as the same one, and only a new TLID is allocated to the MUE. This Recommendation focuses only in the case where the PLID is maintained and a new TLID is allocated, when an MUE is attached to a visited network. + +An MUE or ALM-FE starts the initial LBU procedure when it attaches to a visited network. As in the non-roaming case, there are two architectures to perform the procedure: + +- Host-based location management + +An MUE starts performing the initial LBU procedure by exchanging LBU messages with the home CLM-FE directly or via the visited ALM-FE. + +- Network-based location management + +The visited ALM-FE that detects an MUE's attachment starts performing the initial LBU procedure by exchanging the LBU messages with the home CLM-FE in the MUE's home network. + +Differently from the non-roaming case, the initial LBU procedure cannot be omitted for host-based location management in the roaming case since the MUE's PLID will never be topologically correct in respect to its access network, in the roaming case. As mentioned in the roaming case, the data path setup procedure is described in detail in [ITU-T Q.1709]. + +## 8.1 Host-based LM + +When an MUE is attached to an access network in a visited NGN, the MUE performs the initial LBU procedure, in the host-based location management architecture. As shown in Figure 8-1, the host-based location management is using the interaction among MUE, visited ALM-FE and home CLM-FE. After a successful LBU procedure, the relevant LMF entity will maintain the mapping between PLID and TLID. + +![Figure 8-1: Host-based LBU architecture in the roaming case. The diagram shows two network boxes: 'Home network' and 'Visited network'. Inside 'Home network' are 'CLM-FE' and 'ALM-FE' (with an ellipsis). Inside 'Visited network' are 'CLM-FE' and 'ALM-FE' (with an ellipsis). Below 'Visited network' is 'MUE'. Arrows show connections: MUE to ALM-FE in Visited network, ALM-FE in Visited network to CLM-FE in Visited network, ALM-FE in Visited network to CLM-FE in Home network, and MUE to CLM-FE in Home network. A label 'Q.1708/Y.2805(08)_F8-1' is at the bottom right.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +Figure 8-1: Host-based LBU architecture in the roaming case. The diagram shows two network boxes: 'Home network' and 'Visited network'. Inside 'Home network' are 'CLM-FE' and 'ALM-FE' (with an ellipsis). Inside 'Visited network' are 'CLM-FE' and 'ALM-FE' (with an ellipsis). Below 'Visited network' is 'MUE'. Arrows show connections: MUE to ALM-FE in Visited network, ALM-FE in Visited network to CLM-FE in Visited network, ALM-FE in Visited network to CLM-FE in Home network, and MUE to CLM-FE in Home network. A label 'Q.1708/Y.2805(08)\_F8-1' is at the bottom right. + +**Figure 8-1 – Host-based LBU architecture in the roaming case** + +Figures 8-2 and 8-3 show the information flow for the initial host-based LBU procedure, in the roaming case. The MUE that is attached initially to a visited network starts the initial LBU procedure with its home CLM-FE, by exchanging LBU messages directly or via a visited ALM-FE. Figures 8-2 and 8-3 describe the LBU procedures with and without the visited ALM-FE involvement, respectively. If a visited ALM-FE is involved, the ALM-FE may act as a proxy for the home CLM-FE. When the home CLM-FE receives the initial LBU\_Request message, it will respond with an LBU\_Response message to the MUE directly or via a visited ALM-FE. The LBU\_Response message may indicate whether the registration is successful or not. The failure reasons for the registration may be diverse, and may range from an overload condition of the CLM-FE to administration policies. In case of registration failure, the CLM-FE may respond with additional information such as redirection indication and new CLM-FE information for the redirection, which makes the MUE re-initiate the LBU procedure with the new CLM-FE. If the LBU\_Response message is received with only redirection indication and without new CLM-FE information, the MUE may try another candidate CLM-FE from the list of candidate CLM-FEs that the MUE maintains. + +![Figure 8-2: Host-based LBU procedure with visited ALM-FE in the roaming case. This sequence diagram shows three entities: 'MUE', 'ALM-FE (Visited network)', and 'CLM-FE (Home network)'. A solid arrow labeled 'Initial LBU' goes from MUE to ALM-FE. A dashed arrow goes from ALM-FE to CLM-FE. A solid arrow goes from CLM-FE back to ALM-FE. A dashed arrow goes from ALM-FE back to MUE. A label 'Q.1708/Y.2805(08)_F8-2' is at the bottom right.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +Figure 8-2: Host-based LBU procedure with visited ALM-FE in the roaming case. This sequence diagram shows three entities: 'MUE', 'ALM-FE (Visited network)', and 'CLM-FE (Home network)'. A solid arrow labeled 'Initial LBU' goes from MUE to ALM-FE. A dashed arrow goes from ALM-FE to CLM-FE. A solid arrow goes from CLM-FE back to ALM-FE. A dashed arrow goes from ALM-FE back to MUE. A label 'Q.1708/Y.2805(08)\_F8-2' is at the bottom right. + +**Figure 8-2 – Host-based LBU procedure with visited ALM-FE in the roaming case** + +![Figure 8-3: Host-based LBU procedure without visited ALM-FE in the roaming case. This sequence diagram shows three entities: 'MUE', 'ALM-FE (Visited network)', and 'CLM-FE (Home network)'. A solid arrow labeled 'Initial LBU' goes from MUE directly to CLM-FE. A dashed arrow goes from CLM-FE back to MUE. A label 'Q.1708/Y.2805(08)_F8-3' is at the bottom right.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +Figure 8-3: Host-based LBU procedure without visited ALM-FE in the roaming case. This sequence diagram shows three entities: 'MUE', 'ALM-FE (Visited network)', and 'CLM-FE (Home network)'. A solid arrow labeled 'Initial LBU' goes from MUE directly to CLM-FE. A dashed arrow goes from CLM-FE back to MUE. A label 'Q.1708/Y.2805(08)\_F8-3' is at the bottom right. + +**Figure 8-3 – Host-based LBU procedure without visited ALM-FE in the roaming case** + +As in the non-roaming case, the LID binding operation may bind multiple TLIDs to a PLID for MUEs with multiple interfaces such as Wi-Fi, HSDPA, WiMAX, etc., and an MUE may perform multiple LBU procedures with multiple CLM-FEs for each PLID, or multiple LBU procedures with the same CLM-FE, to create multiple bindings of TLID and PLID in the CLM-FE. + +## 8.2 Network-based LM + +When an MUE is attached to an access network in a visited NGN, the visited ALM-FE that detects the MUE's attachment performs the initial LBU procedure in the network-based location management architecture. + +As shown in Figure 8-4, the network-based location management is based on interaction between visited ALM-FEs and the home CLM-FE. After a successful LBU procedure, the relevant LM-FE will maintain the mapping between PLID and TLID. + +![Figure 8-4: Network-based LBU architecture in the roaming case. The diagram shows two network boxes: 'Home network' and 'Visited network'. The 'Home network' box contains a 'CLM-FE' at the top and two 'ALM-FE' boxes at the bottom, separated by an ellipsis. The 'Visited network' box also contains a 'CLM-FE' at the top and two 'ALM-FE' boxes at the bottom, separated by an ellipsis. A double-headed arrow connects the 'CLM-FE' in the 'Home network' to the 'ALM-FE' in the 'Visited network'. Below the 'Visited network' box is a 'MUE' box. A small text label 'Q.1708/Y.2805(08)_F8-4' is located to the right of the 'MUE' box.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +Figure 8-4: Network-based LBU architecture in the roaming case. The diagram shows two network boxes: 'Home network' and 'Visited network'. The 'Home network' box contains a 'CLM-FE' at the top and two 'ALM-FE' boxes at the bottom, separated by an ellipsis. The 'Visited network' box also contains a 'CLM-FE' at the top and two 'ALM-FE' boxes at the bottom, separated by an ellipsis. A double-headed arrow connects the 'CLM-FE' in the 'Home network' to the 'ALM-FE' in the 'Visited network'. Below the 'Visited network' box is a 'MUE' box. A small text label 'Q.1708/Y.2805(08)\_F8-4' is located to the right of the 'MUE' box. + +**Figure 8-4 – Network-based LBU architecture in the roaming case** + +Figure 8-5 shows the information flow for the initial network-based LBU procedure in the roaming case. A visited ALM-FE that detects an MUE's initial attachment starts the initial LBU procedure with the MUE's home CLM-FE by exchanging LBU messages. When the home CLM-FE receives the initial LBU\_Request message from the visited ALM-FE, it will respond with an LBU\_Response message to the visited ALM-FE. The LBU\_Response message may indicate whether the registration is successful or not. The failure reasons for the registration may be diverse, and ranged from an overload condition of the CLM-FE to administration policies. In case of registration failure, the CLM-FE may respond with additional information such as redirection indication and new CLM-FE information for the redirection, which makes the ALM-FE re-initiate the LBU procedure with the new CLM-FE. If the LBU\_Response message is received with only redirection indication and without new CLM-FE information, the ALM-FE may try another candidate CLM-FE from the CLM-FE list that the ALM-FE maintains. + +![Figure 8-5: Network-based initial LBU procedure in the roaming case. This is a sequence diagram with three vertical lifelines: 'MUE', 'ALM-FE (Visited network)', and 'CLM-FE (Home network)'. A horizontal arrow labeled 'Initial LBU' points from the 'ALM-FE' to the 'CLM-FE'. A small text label 'Q.1708/Y.2805(08)_F8-5' is located at the bottom right of the diagram.](77464a47f104d0d647b2414591137b64_img.jpg) + +Figure 8-5: Network-based initial LBU procedure in the roaming case. This is a sequence diagram with three vertical lifelines: 'MUE', 'ALM-FE (Visited network)', and 'CLM-FE (Home network)'. A horizontal arrow labeled 'Initial LBU' points from the 'ALM-FE' to the 'CLM-FE'. A small text label 'Q.1708/Y.2805(08)\_F8-5' is located at the bottom right of the diagram. + +**Figure 8-5 – Network-based initial LBU procedure in the roaming case** + +As in the non-roaming case, the LID binding operation may bind multiple TLIDs to a PLID for MUEs with multiple interfaces such as Wi-Fi, HSDPA, WiMAX, etc., and the ALM-FEs may also perform LBU procedures with multiple CLM-FEs for each PLID or multiple LBU procedures with the same CLM-FE to create multiple mappings of TLID and PLID in the CLM-FE. + +# Bibliography + +- [b-ITU-T Q.1701] Recommendation ITU-T Q.1701 (1999), *Framework for IMT-2000 networks*. +- [b-ITU-T Q.1702] Recommendation ITU-T Q.1702 (2002), *Long-term vision of network aspects for systems beyond IMT-2000*. +- [b-ITU-T Q.1711] Recommendation ITU-T Q.1711 (1999), *Network functional model for IMT-2000*. +- [b-ITU-T Q.1721] Recommendation ITU-T Q.1721 (2000), *Information flows for IMT-2000 capability set 1*. +- [b-ITU-T Q.1741.3] Recommendation ITU-T Q.1741.3 (2003), *IMT-2000 references to release 5 of GSM evolved UMTS core network*. +- [b-ITU-T Q.1742.3] Recommendation ITU-T Q.1742.3 (2004), *IMT-2000 references (approved as of 30 June 2003) to ANSI-41 evolved core network with cdma2000 access network*. +- [b-ITU-T Q.1761] Recommendation ITU-T Q.1761 (2004), *Principles and requirements for convergence of fixed and existing IMT-2000 systems*. +- [b-ITU-T Q.Sup52] Supplement 52 to ITU-T Q-series Recommendations (2004), *NNI mobility management requirements for systems beyond IMT-2000*. +- [b-ITU-R M.687-2] Recommendation ITU-R M.687-2 (1997), *International Mobile Telecommunications-2000 (IMT-2000)*. +- [b-ITU-R M.1034-1] Recommendation ITU-R M.1034-1 (1997), *Requirements for the radio interface(s) for International Mobile Telecommunications-2000 (IMT-2000)*. +- [b-ITU-R M.1168] Recommendation ITU-R M.1168 (1995), *Framework of International Mobile Telecommunications-2000 (IMT-2000)*. +- [b-ITU-R M.1224] Recommendation ITU-R M.1224 (1997), *Vocabulary of terms for Mobile Telecommunications-2000 (IMT-2000)*. +- [b-IETF RFC 3344] IETF RFC 3344 (2002), *IP mobility support for IPv4*. +<>. +- [b-IETF RFC 3775] IETF RFC 3775 (2004), *Mobility support in IPv6*. +<> +- [b-IETF RFC 4830] IETF RFC 4830 (2007), *Problem Statement for Network-based Localized Mobility Management (NETLMM)*. +<> +- [b-IETF RFC 4831] IETF RFC 4831 (2007), *Goals for Network-based Localized Mobility Management (NETLMM)*. +<> +- [b-IETF RFC 5213] IETF RFC 5213 (2008), *Proxy Mobile IPv6* +<> + + + +## ITU-T Y-SERIES RECOMMENDATIONS + +# GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS + +## GLOBAL INFORMATION INFRASTRUCTURE + +| | | +|-------------------------------------------|-------------| +| General | Y.100–Y.199 | +| Services, applications and middleware | Y.200–Y.299 | +| Network aspects | Y.300–Y.399 | +| Interfaces and protocols | Y.400–Y.499 | +| Numbering, addressing and naming | Y.500–Y.599 | +| Operation, administration and maintenance | Y.600–Y.699 | +| Security | Y.700–Y.799 | +| Performances | Y.800–Y.899 | + +## INTERNET PROTOCOL ASPECTS + +| | | +|--------------------------------------------------------------------|---------------| +| General | Y.1000–Y.1099 | +| Services and applications | Y.1100–Y.1199 | +| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 | +| Transport | Y.1300–Y.1399 | +| Interworking | Y.1400–Y.1499 | +| Quality of service and network performance | Y.1500–Y.1599 | +| Signalling | Y.1600–Y.1699 | +| Operation, administration and maintenance | Y.1700–Y.1799 | +| Charging | Y.1800–Y.1899 | + +## NEXT GENERATION NETWORKS + +| | | +|-------------------------------------------------------------------|----------------------| +| Frameworks and functional architecture models | Y.2000–Y.2099 | +| Quality of Service and performance | Y.2100–Y.2199 | +| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 | +| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 | +| Numbering, naming and addressing | Y.2300–Y.2399 | +| Network management | Y.2400–Y.2499 | +| Network control architectures and protocols | Y.2500–Y.2599 | +| Security | Y.2700–Y.2799 | +| Generalized mobility | Y.2800–Y.2899 | + +For further details, please refer to the list of ITU-T Recommendations. + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa3c5c6b5312287dace25a92984513ec05015eef --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:753d3ac4ff01c19f610c5767036f09ef2a1ba0d846fcc1c88967bc9d7eb6127d +size 27769 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0144f1cf8f725b5402627e6b9d7a6c7125c849c9 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdfc6b6b79ed985ea01fce579eb1c8ef1d2067c02c5db07a406c03a57adcf2ea +size 98419 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e6e1ba456f8ec48b91796b18b11260ca0aeefdc --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5567ed4f084e3f85b1a4b29cb08069e7b249fb5f2ececbaf8c6f13c26e4179b8 +size 74895 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24f81e40130ce91d77a1fd6f225407bec692c6af --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfcd9b6abeb12f9533991227c47d81f0aee325c5b21f4811f199ff4240c6a2c7 +size 52764 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4542261e5d8b7aea395c608acbcbc88d8d6d4ece --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d145a5d7ddc4e650134323ad45becf662b5803dedaee7147cd061355c76566b8 +size 251827 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f803c5c5c526911ac87dd3d8e705e774f467063 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdacf4e59f676cc4b8bdbae820948fe10d5a07686f60e80156e9ec9227acd86c +size 11807 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7aa4f7d56a1ffea02f346c47ea33227e34d5706 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f54cb93fd493813db3df4d1b38665c74219aae1a0e66d46913e457c93daaaaa +size 8275 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de139aa156f9613d576b67110cbb3883de0f1c7a --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a06482546945f350774a6dba775ba7f14d46dd6a9b09bb9c7d538689c80be48b +size 29109 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24e342c8bbbe0a715c5956586f12ba0f61783f66 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31d8fe162b07b7d2f2e59d27c5f2439e75660e23933fd0bc00fdbc46b00766a6 +size 10603 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16da1445ef4dc338125a40f66bded6cc44eb3187 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9a1e5447c71109d28647bb3bd62ce1ad5da5e82eeae5dc565b860aa249f5cd7 +size 76128 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a8c11a98498098c6e3c74185d945fcab2c150e0 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:244f1830f7bc4075cedc212aaf577016a06beca99da8c6d8347761efe6ccb4ef +size 61747 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bad3dc664864157a78c67b12ad691dcc9f79866b --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09765e400f933e91226b30eb14fed7cfe3c3f96782ceb3d1047b9ce9c4864981 +size 258857 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/42c65f5cb106938992fc73c05c8713d2_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/42c65f5cb106938992fc73c05c8713d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d786af371fe52dae0441a66ec0f5e8eef0cf4c36 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/42c65f5cb106938992fc73c05c8713d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c309252f9d730a0cee7b8c9265b32ec04cb2f0fbd41243f371c5cedb428eff6c +size 11324 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be6c58472bd19a8931147a2902a3b534df6886b4 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b79000d2b6be7b85e5020503fc256819379d10fded9d6ff08a42777b7acfa06d +size 55032 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5593facb376cb360bd4b0960b2911b3e_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5593facb376cb360bd4b0960b2911b3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3373d26e322a17277344757c11a05b28b93fe617 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5593facb376cb360bd4b0960b2911b3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d61d293b7afd04ed9e614a5593d1ed8964c42e782eb52ce990ff37a1863eacbd +size 12567 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..843a037fbbd507dbf2893c95fd391eb5e2eca398 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd55cc67e3412a69ea3f0b9406dfaab63b99daf94ab8b2ba3cddc630b36e3a3c +size 13982 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c72e08399ed35bf1c9ae2cea297276b2eb5075c --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1f3c7c8c7377817bf0f9f9ed97658bb6339de53c21a55fc1b63e5e304ba4b4b +size 65216 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fbef3f2671b436ad928b770b4f111d355e5a749 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5ce2a11813022961f4011b59e7df6f524c390e660d769b8ba64e455e4b8e3af +size 35593 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2162a2ea01e133ab5a2a89b2ea0bf370cc005e2 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48084bbe6037f376042ad287dc88c7ad459bf67d86e3f7ece69701dd4c70929e +size 36788 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4350731c317ac218cdd80e3885c68cdbc7e36455 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:263bc4b398b072d2c6f3a686230e38ba66792b03730bf0424874e54dbade78c6 +size 42144 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f2e8e441ca0a559340f2f0bade38067d3fae38 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dae0c0c3d0593bd2ee73e15b196a991f3269a2355cd68377865ef98b150257a9 +size 25757 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94c6a63bd8a90988d56d5396a184aac9a2cf91d1 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05fa098419bd4afbe78085e687d739f766fcee8f4171d8ec09aaf7a84960a894 +size 120390 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70f0b2322b0ab332050566892fe3f9a5c3c0be0b --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0ba74971749086339ef936b74ce1c503b33369f830b121f20bed8a281061074 +size 19351 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..040d2abce5f2bd079bcbaa030e9831d569e193c8 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d89e9233fd70f643ca1ade83f0086675640e530f7b4cee867b53b91f87f4b49 +size 37272 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f649f104f2a5d74c896177ab055eca29e933f62 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:166e8997a14027a9e18379494cfe7e6e14b7497050d5aa30657d15f2f79d5d80 +size 50924 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/d4ed35f72863013455b8f015e0f2e47e_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/d4ed35f72863013455b8f015e0f2e47e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73b6af06e63e46b78b31a9380b09e3aa9f8cfe69 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/d4ed35f72863013455b8f015e0f2e47e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbc70ff2ea6627a9c7e04c8eb955b9527eb5fb5b7586b31ecd0a2d80f127f4c2 +size 27296 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00077f3a4d9e4958af6046a9dd0d53c592f00a4c --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63b6ce601e33fa0a5a7e93b0bf0468c6440ee9b3eb8ed9a8d891236a1b8e403b +size 12819 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bce04e4c1903cb108ac0eb54e2546eddc274750 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7e2c3a7579761df3513d79a88a7304574b6bde16e0c28f576bfd1529416ca35 +size 27128 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49248d3e33a92fb455045f0276dc7be291c981e6 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73fb0c497213dfbd1765056a6037520abd7dffeea382abc49f45ac0fa38f4564 +size 57054 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df81f4b9bb79a2cce484e9fe2b9658e6ea922daa --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5384d89a6f87ba9cbc7764ffe55dd770d4639e12dd776512c140c8723b1dc49 +size 31381 diff --git a/marked/Q/T-REC-Q.1711-199903-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..94b0782ed51fc17d4d1e0f72157500ddc8d06f62 --- /dev/null +++ b/marked/Q/T-REC-Q.1711-199903-I_PDF-E/raw.md @@ -0,0 +1,2072 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1711** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/99) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**Network functional model for IMT-2000** + +ITU-T Recommendation Q.1711 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|-----------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **NETWORK FUNCTIONAL MODEL FOR IMT-2000** + +## **Summary** + +This Recommendation identifies network and terminal functions that are specific for the support of IMT-2000 services, as specified in the Recommendation on the Framework for IMT-2000 Networks (Recommendation Q.1701). These functions together with other, more conventional network functions are then grouped into functional entities in a generic functional model. In the functional model, the relationships among functional entities and groups are shown. + +The functional model is mapped onto a generic network reference model to illustrate possible groupings of functional entities into physical collections of entities. + +Based on the functional model, global roaming requirements and network interconnection scenarios are described. + +This Recommendation forms the basis for the development of information flows and the definition of functional entity actions and the development of signalling requirements for the various interfaces identified in Recommendation Q.1701. + +## **Source** + +ITU-T Recommendation Q.1711 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 15th of March 1999. + +## **Keywords** + +Functional architecture, Functional entity (FE), Global roaming, Handover, IMT-2000, Mobility management, Physical reference model, Virtual home environment (VHE) + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1999 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +| | | Page | +|-------|-----------------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Abbreviations and Definitions ..... | 2 | +| 3.1 | Abbreviations..... | 2 | +| 3.2 | Definitions ..... | 4 | +| 4 | IMT-2000 Specific Functions ..... | 7 | +| 4.1 | Functions related to overall system access control ..... | 8 | +| 4.2 | Functions related to radio resource management and control..... | 9 | +| 4.2.1 | Synchronization control..... | 9 | +| 4.2.2 | Functions related to access radio link control..... | 9 | +| 4.2.3 | Functions related to RF power control management..... | 9 | +| 4.2.4 | Functions related to random access ..... | 10 | +| 4.2.5 | Functions related to radio resource request acceptability ..... | 10 | +| 4.3 | Functions related to channel coding ..... | 10 | +| 4.4 | Functions related to handover..... | 11 | +| 4.5 | Functions related to location management & geographic position finding ..... | 12 | +| 4.5.1 | Functions related to terminal paging ..... | 12 | +| 4.5.2 | Functions related to location data management, registration and
deregistration ..... | 12 | +| 4.5.3 | Functions related to geographic position finding ..... | 14 | +| 4.6 | Functions related to mobile call handling (including routing)..... | 14 | +| 4.6.1 | Common functions ..... | 14 | +| 4.6.2 | Functions specific to routing of circuit-switched mobile calls..... | 15 | +| 4.6.3 | Functions related to routing and addressing of IMT-2000 packet data
services ..... | 15 | +| 4.6.4 | Functions related to handling of multimedia calls..... | 16 | +| 4.6.5 | Management of both circuit-switched and packet-switched
communications..... | 16 | +| 4.7 | Functions related to data coding & compression..... | 16 | +| 4.8 | Functions related to network intelligence and service control..... | 16 | +| 4.8.1 | Functions supporting UPT users..... | 16 | +| 4.8.2 | Functions related to service portability..... | 16 | +| 4.8.3 | Functions supporting supplementary services ..... | 17 | +| 4.8.4 | Functions related to support of the Virtual Home Environment ..... | 17 | +| 4.8.5 | Functions related to support of IN ..... | 17 | +| 4.9 | Additional functions related to global roaming ..... | 18 | + +| | Page | +|------------------------------------------------------------------------------------|-------------| +| 4.10 Functions related to user privacy & network security..... | 19 | +| 4.10.1 Functions related to ciphering ..... | 19 | +| 4.10.2 Functions related to authentication..... | 19 | +| 4.10.3 Functions related to network fraud/abuse control ..... | 20 | +| 4.10.4 Functions related to identity management ..... | 20 | +| 4.11 Functions related to support of emergency services ..... | 20 | +| 4.12 Functions related to charging..... | 20 | +| 4.13 Functions supporting IMT-2000 users..... | 21 | +| 4.14 Functions related to subscriber data management ..... | 21 | +| 4.14.1 Functions related to managing data in Serving networks ..... | 21 | +| 4.14.2 Functions related to fault recovery of subscriber data ..... | 21 | +| 4.14.3 Functions related to subscriber control of supplementary services data..... | 22 | +| 4.15 Functions related to messaging service management ..... | 22 | +| 4.16 Functions related to software configurable terminals ..... | 22 | +| 5 The IMT-2000 Functional Models..... | 23 | +| 5.1 Modelling principles ..... | 24 | +| 5.2 The complete functional models..... | 24 | +| 5.3 Radio access control related Functional Entities ..... | 26 | +| 5.4 Communication and service control related Functional Entities ..... | 31 | +| 5.4.1 Functional Entities on the network side of the radio interface ..... | 32 | +| 5.4.2 Functional Entities on the mobile side of the radio interface ..... | 38 | +| 5.4.3 Packet data services control related Functional Entities..... | 40 | +| 6 Network Reference Model..... | 42 | +| 6.1 A generic reference model ..... | 43 | +| 6.2 Network reference points ..... | 46 | +| 7 Global Roaming and Interworking Scenarios ..... | 48 | +| 7.1 Introduction..... | 48 | +| 7.2 Global roaming ..... | 48 | +| 7.2.1 General..... | 48 | +| 7.2.2 Interconnections..... | 48 | +| 7.3 Internet (Internet Protocol) interworking ..... | 56 | + +# Introduction + +IMT-2000 systems are intended to provide telecommunication services to mobile and fixed users via a wireless link, covering a wide range of user sectors (e.g. public, private, business, residential, local loop, etc.), radio technologies and coverage (cellular, satellite, cordless, etc.) and accommodating a wide range of user equipment (e.g. personal pocket terminals, vehicle mounted terminals, special mobile terminals, standard PSTN/ISDN terminal equipment connected to the mobile terminal, etc.). ITU-R Recommendation M.816-1 [2] and Recommendation F.115 [4] discuss the services in more detail. Recommendation Q.1701 [9] (Framework for IMT-2000 Networks) provides an overall view of the system architecture and service/network capabilities to be supported by IMT-2000 systems. + +One of the key service objectives of IMT-2000 is to enable the provision of multimedia services (in circuit and packet-mode operation). Requirements for network functions must therefore take into account the support of multimedia services. IMT-2000 radio resources must be shared among circuit mode (voice and data) services and other mode services (e.g. packet data transfer mode). + +In addition, IMT-2000 systems should support global roaming and the Virtual Home Environment concept, i.e. the user will be provided with a comprehensive set of services and features which have the same look and feel whether they are used in the Home or Visited network. The establishment of this concept realises that service provision and network operation may be separated, allowing services to be offered by organisations not explicitly being network operators. The users of these services "roam" in networks and access these services as and where commercial relationships allow it. + +A number of different radio environments are involved, covering indoor "pico" cells with very high overall system capacity all the way through large outdoor terrestrial cells to satellite coverage. A major focus of the ITU standards work on IMT-2000 systems is to maximise the commonality among the various radio interfaces involved in order to simplify the task of building multi-mode mobile terminals covering more than one radio environment. A unified support of these various radio interfaces by the backbone network is therefore important. As a consequence of these requirements, a key characteristic of the modelling approach followed in this Recommendation is the following: functions which are dependent on radio access technology are identified and separated from functions which are not dependent on radio access technology. Thus, as much as possible of the network has been defined independently from the radio access technology. + +The concept of IMT-2000 Family of Systems (as outlined in Recommendation Q.1701) allows multiplicity of family members. Family members therefore have the option to selectively implement only those functions which are needed to support the services they choose to offer. + +IMT-2000 may be implemented as a stand alone network with gateways and interworking units towards the supporting networks, in particular PSTN, ISDN, Packet-Data Networks (e.g. Internet) and B-ISDN (Broadband ISDN). This is comparable to the current implementations of public land mobile networks and it is also a solution in cases where the fixed network and the radio network are operated by different operators. However, IMT-2000 may also be integrated with the fixed networks. In this case, the functionality required to support specific radio network requirements, e.g. location registration, paging and handover, is an integral part of the fixed network. Such integration will be more and more feasible with the development of IN and exchanges for ISDN and B-ISDN. In such an integrated case, the base stations may be connected directly to a local exchange which can support IMT-2000 traffic by locally integrated functions and by accessing functions in other network elements. + +With the new mobile radio technologies there is a potential of wireless systems providing cost effective and flexible access to the global telecommunication networks as an alternative for local loop wiring. An objective is to allow for small and simple start-up systems, that can be readily expanded in capacity and can evolve in functionality as required. In a more general way, + +IMT-2000 radio interfaces will be applied to fixed services in all types of environment, i.e. urban, rural and remote as represented in ITU-R Recommendation M.819-2 [3]. It should also be possible to use an IMT-2000 radio connection for a residential cordless telephone application. Although IMT-2000 systems are intended primarily for public access, provision of IMT-2000 services in connection with private networks must be considered, e.g. the connection of a mobile PBX or LAN (e.g. on board a ship or train) to the public networks or the use of personal pocket terminals as extensions to a PBX. Public radio access to a PBX should also be considered (e.g. hotels, hospitals, etc.). + +The network functional model developed for IMT-2000 is intended to be flexible enough to cover all these application scenarios and at the same time meet all requirements outlined in Recommendation Q.1701. + +# **NETWORK FUNCTIONAL MODEL FOR IMT-2000** + +*(Geneva, 1999)* + +# **1 Scope** + +The purpose of this Recommendation is to identify network functions which are specific to IMT-2000 systems (Capability Set 1) and to define a Functional Model which will form the basis for the development of information flows and the definition of functional entity actions. + +Clause 4 describes the network functions which are required for the support of IMT-2000 specific network capabilities. + +Clause 5 defines the generic Functional Model for IMT-2000 systems. + +Clause 6 describes the IMT-2000 network references model(s) and identifies physical reference points. + +Clause 7 describes some network interconnection scenarios to support global roaming and Internet interworking. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-R Recommendation M.687-2 (1997), *International Mobile Telecommunications-2000 (IMT-2000)*. +- [2] ITU-R Recommendation M.816-1 (1997), *Framework for services supported on International Mobile Telecommunications-2000 (IMT-2000)*. +- [3] ITU-R Recommendation M.819-2 (1997), *International Mobile Telecommunications-2000 (IMT-2000) for developing countries*. +- [4] ITU-T Recommendation F.115 (1995), *Service objectives and principles for future public land mobile telecommunication systems (FPLMTS)*. +- [5] CCITT Recommendation Q.1001 (1988), *General aspects of public land mobile networks*. +- [6] ITU-T Recommendation Q.1290 (1998), *Glossary of terms used in the definition of intelligent networks*. +- [7] ITU-T Recommendation Q.1224 (1997), *Distributed functional plane for intelligent network Capability Set 2*. +- [8] ITU-T Recommendation Q.1541 (1998), *UPT stage 2 for Service Set 1 on INCSI – Procedures for universal personal telecommunication functional modelling and information flows*. +- [9] ITU-T Recommendation Q.1701 (1999), *Framework for IMT-2000 networks*. + +# **3 Abbreviations and Definitions** + +## **3.1 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-------|-----------------------------------------| +| AC | Authentication Centre | +| ADDS | Application Data Delivery Service | +| AMF | Authentication Management Function | +| AMSC | Anchor Mobile Switching Centre | +| ARF | Access link Relay Function | +| BS | Base Station | +| CCAF' | Call Control Agent Function (enhanced) | +| CCF | Call Control Function | +| CCF' | Call Control Function (enhanced) | +| CN | Core Network | +| CnCAF | Connection Control Agent Function | +| CnCF | Connection Control Function | +| CS | Capability Set | +| DFP | Distributed Functional Plane | +| DMSC | Drift Mobile Switching Centre | +| FE | Functional Entity | +| GII | Global Information Infrastructure | +| GLR | Gateway Location Register | +| GMSC | Gateway Mobile Switching Centre | +| GPCF | Geographic Position Control Function | +| GPF | Geographic Position Function | +| GPS | Global Positioning System | +| HLR | Home Location Register | +| ICMP | Internet Control Message Protocol | +| ID | Identity | +| IMUI | International Mobile User Identity | +| IN | Intelligent Network | +| IP | Intelligent Peripheral | +| LMF | Location Management Function | +| MCF | Mobile Control Function | +| MGPF | Mobile Geographic Position Function | +| MMI | Man-Machine Interface | +| MRTR | Mobile Radio Transmission and Reception | + +| | | +|-------|----------------------------------------------| +| MSC | Mobile Switching Centre | +| MT | Mobile Terminal | +| NNI | Network to Network Interface | +| PDGN | Packet Data Gateway Node | +| PDN | Public Data Network | +| PDSN | Packet Data Serving Node | +| PIN | Personal Identification Number | +| PSCAF | Packet Service Control Agent Function | +| PSCF | Packet Service Control Function | +| PSGCF | Packet Service Gateway Control Function | +| QoS | Quality of Service | +| RACAF | Radio Access Control Agent Function | +| RACF | Radio Access Control Function | +| RAN | Radio Access Network | +| RF | Radio Frequency | +| RFTR | Radio Frequency Transmission and Reception | +| RNC | Radio Network Controller | +| SACF | Service Access Control Function | +| SCEF | Service Creation Environment Function | +| SCF | Service Control Function | +| SCP | Service Control Point | +| SDF | Service Data Function | +| SDP | Service Data Point | +| SIBF | System access Information Broadcast Function | +| SLP | Service Logic Program | +| SMAF | Service Management Agent Function | +| SMF | Service Management Function | +| SMS | Short Message Service | +| SNCF | Satellite Network Control Function | +| SRF | Specialized Resource Function | +| SS | Supplementary Service | +| SSD | Shared Secret Data | +| SSF | Service Switching Function | +| SSP | Service Switching Point | +| TMN | Telecommunications Management Network | +| Tx | Transit Exchange | + +| | | +|------|-----------------------------------------| +| UIM | User Identity Module | +| UIMF | User Identification Management Function | +| UPT | Universal Personal Telecommunications | +| VHE | Virtual Home Environment | +| VLR | Visitor Location Register | + +## 3.2 Definitions + +For the definition of cellular terms (e.g. MSC, cell, base station, etc.), reference is made to Recommendation Q.1001 [5]. Cellular terms to be referred are as follows: + +MSC, HLR, VLR, Cell, Location area, and Base station. + +For the definition of Framework of IMT-2000 Networks related terms, reference is made to Recommendation Q.1701 [9]. Related terms to be referred are as follows: + +UIM, MT, RAN, CN, and NNI. + +![Diagram showing the physical interfaces of an IMT-2000 family member system. The diagram shows a sequence of components: UIM, MT, RAN, CN, and CN. The interfaces between them are labeled: UIM-MT Interface, MT-RAN Interface, RAN-CN Interface, and NNI. An arrow points from the final CN component to the text 'Core networks of other IMT-2000 family members'. A small code 'T1199390-98' is also present.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +graph LR + UIM[UIM] ---|UIM-MT Interface| MT[MT] + MT ---|MT-RAN Interface| RAN[RAN] + RAN ---|RAN-CN Interface| CN1[CN] + CN1 ---|NNI| CN2[CN] + CN2 -->|T1199390-98| Core[Core networks of other IMT-2000 family members] + +``` + +Diagram showing the physical interfaces of an IMT-2000 family member system. The diagram shows a sequence of components: UIM, MT, RAN, CN, and CN. The interfaces between them are labeled: UIM-MT Interface, MT-RAN Interface, RAN-CN Interface, and NNI. An arrow points from the final CN component to the text 'Core networks of other IMT-2000 family members'. A small code 'T1199390-98' is also present. + +**Figure 3-1/Q.1711 – Physical interfaces of an IMT-2000 family member system** + +The following definitions are based on Recommendation Q.1290 [6] and have been modified for use in this Recommendation: + +**3.2.1 Call control:** The set of functions used to process a call, i.e. service negotiation, set-up, modification and release of single or multiple-connection calls, used in conjunction with the service request from the user. There may be zero, one or several connections established for one call. + +**3.2.2 Connection:** An end-to-end association of transmission channels or circuits, switching and other functional units set up to provide a means for a transfer of information between two or more points in a telecommunications network. A connection is composed of several connection links. There are one or more connections for each media component of a call. + +**3.2.3 Connection control:** The set of functions used for setting up, maintaining and releasing a communication path between two or more users or a user and a network entity, e.g. a dual tone multi-frequency receiver. + +**3.2.4 Connection link:** A part of a connection between a pair of connection control functions which control it. A union of connection links forms a connection. + +In addition, the following terms have been defined for use in this Recommendation: + +**3.2.5 Access link:** Aggregation of all logical channels for the support of a connection link between the Mobile Terminal (MT) and the Core Network (CN) via the Radio Access Network (RAN) (see Figure 3-2 ). + +**3.2.6 Access radio link:** The portion of access link which is supported by radio (see Figure 3-2). + +- 3.2.7 Aggregated radio channel:** The aggregated, multiplexed information bitstream that is carried over the radio interface as a single physical entity for a single mobile terminal. +- 3.2.8 Association between an IMT-2000 terminal/user and the network (Terminal/User Association):** Association between an IMT-2000 terminal/user and the network is a logical relation between the IMT-2000 terminal/user and the network which is used by the network to identify a certain IMT-2000 terminal/user from all the IMT-2000 terminals/users having control relationships with it. The association is established when the IMT-2000 terminal/user originates the first call (i.e. outgoing call at idle state) or signalling connection or when the network originates the first call to the IMT-2000 terminal/user (i.e. incoming call at idle state). In the latter case, the association is established by a paging procedure. The association is kept active until all the calls and connections on the terminal are released. +- 3.2.9 Authentication data:** Set of data related to authentication. They include authentication parameters and authentication information. +- 3.2.10 Authentication parameter:** A secret data prepared for individual user authentication. A typical permanent user secret data is a user authentication key. A session user secret data may be used as an authentication parameter, referred to as shared secret data (SSD). +- 3.2.11 Authentication information:** Information which is used for user authentication. In a challenge-response based authentication mechanism, typical authentication information is a set of challenge, response and ciphering key, referred to as a triplet. +- 3.2.12 Bearer:** The communication path between two adjacent nodes which is associated with one connection. +- 3.2.13 Bearer control:** Supports the control of network resources on a network link by network link scale (i.e. node to node) to support the end to end carriage of information. +- 3.2.14 BS approach link:** The portion of access link which is not the access radio link (see Figure 3-2). +- 3.2.15 Call:** An end-to-end logical relationship between two or more parties, established on behalf of an initiating party, associated with a service invocation. +- 3.2.16 Camp on cell:** The mobile terminal has completed the cell selection/re-selection process and has chosen a cell, from which it plans to receive available services. The network may not be aware of the existence of the mobile terminal within the chosen cell. +- 3.2.17 Diversity convergence point:** The merging point of more than one physical bit streams into a logical information stream, using diversity technique (see Figure 3-2). +- 3.2.18 Diversity handover:** Diversity handover is a type of handover that makes use of macro-diversity techniques. +- 3.2.19 Diversity link:** Aggregation of diversity paths between two corresponding diversity convergence points. One or more diversity paths compose a diversity link (see Figure 3-2). +- 3.2.20 Diversity path:** A connection of link elements between two corresponding diversity convergence points is called a diversity path. A diversity path constitutes one branch of a diversity link. Using diversity technique, diversity paths may be combined to form a diversity path (see Figure 3-2). +- 3.2.21 Diversity branch:** Diverging path of a link spreading from the diversity point (see Figure 3-2). +- 3.2.22 Global roaming (general):** Global roaming refers to the ability to roam between one IMT-2000 system and any other IMT-2000 systems. + +**3.2.23 Global roaming routing/addressing:** The ability of the network to address and route communications and services to roaming IMT-2000 users rather than to a geographic location or a physical device. + +**3.2.24 Global roaming service portability:** The ability of the network to allow subscribers to access customized communications services anywhere, in accordance with his/her service profile, within and between IMT-2000 systems. + +**3.2.25 Global roaming UIM portability:** The ability of a user to transfer her/his identity between IMT-2000 mobile terminals. + +**3.2.26 Global roaming terminal mobility:** Terminal Mobility is the ability of a terminal to access telecommunications services from different locations and while in motion, and the capability of the network to identify and locate that terminal on its associated User Identity Module (UIM). + +**3.2.27 Global roaming user profile accessibility/transportability:** The ability of the network to readily access, transfer/download, and modify, the user's service profile from anywhere, subject to business and security considerations. + +**3.2.28 Handover branch:** Branch of an access radio link participating in a handover (see Figure 3-3). + +**3.2.29 Handover path:** A sequence of link elements participating in a handover (see Figure 3-3). + +**3.2.30 Link element:** A logical channel between two adjacent functional nodes (see Figure 3-2). + +**3.2.31 Logical radio channel:** A logical radio channel is an information stream dedicated to the transmission of a certain type of information, e.g. signalling data or user data. Multiple logical channels can be mapped onto a single physical radio channel. One logical channel can also be mapped or duplicated on multiple physical radio channels. + +**3.2.32 Macro-diversity:** Macro-diversity is a family of diversity techniques where diversity is provided by using multiple physical channels forming, in the general case, a point-to-multipoint (multiple base stations) RF connection in the up-link and a multipoint-to-point connection in the down-link carrying a single data transmission (which is combined at the receiving end). The links from/to the multiple base stations (i.e. the branches of the BS approach link) are also combined in the fixed part of the network. Such techniques include base station diversity, diversity handover, simulcast, etc. + +**3.2.33 Physical radio channel:** A radio communication path defined in frequency, code and/or time, which is established for a given period of time. Multiple physical radio channels can be mapped onto a single radio frequency channel. One physical radio channel can also be mapped or duplicated on multiple radio frequency channels. + +**3.2.34 Radio frequency channel:** A radio frequency (RF) channel represents a specified portion of the RF spectrum with a defined bandwidth and a carrier frequency and is capable of carrying information over the radio interface. + +**3.2.35 Radio resource:** A portion of spectrum available in a limited geographical area (cell). This portion of spectrum can be further divided into radio frequency channels. + +![Diagram of MT-RAN/CN access related communication elements.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +This diagram illustrates the network architecture for MT-RAN/CN access related communication. It is divided into two main components: a Mobile Terminal on the left and a RAN/CN on the right. Inside the Mobile Terminal, a 'functional node' (represented by a triangle) is connected to a 'Link Element' (represented by a square). This square is labeled as a 'Diversity Convergence Point'. An 'Access Radio Link' connects this point to a 'functional node' inside the RAN/CN. Within the RAN/CN, this 'functional node' is connected to another 'Link Element' (square), which is also a 'Diversity Convergence Point'. A 'Diversity Path' is shown as a dashed line between the two 'functional nodes' (circles). A 'Diversity Branch' is indicated by a dashed line from the second 'functional node' to the second 'Link Element'. A 'BS Approach Link' is shown as a solid line from the first 'functional node' to the second 'functional node'. At the bottom, a horizontal double-headed arrow labeled 'Diversity Link' spans between the two 'Diversity Convergence Points', and another horizontal double-headed arrow labeled 'Access Link' spans between the Mobile Terminal and the RAN/CN. The diagram is labeled 'T1199400-98' in the bottom right corner. + +Diagram of MT-RAN/CN access related communication elements. + +**Figure 3-2/Q.1711 – Naming of the elements associated with the MT-RAN/CN access related communication** + +![Diagram of elements associated with diversity handover.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +This diagram illustrates the network architecture for diversity handover. It consists of a Mobile Terminal on the left and a RAN/CN on the right. Inside the Mobile Terminal, a 'functional node' (triangle) is connected to a 'Link Element' (square). A 'Handover Path' is shown as a dashed line from this 'Link Element' to a 'functional node' (circle) inside the RAN/CN. Inside the RAN/CN, this 'functional node' is connected to another 'Link Element' (square), which is connected to a second 'functional node' (circle). A 'Handover Branch' is indicated by a dashed line from the first 'functional node' to the second 'functional node'. The diagram is labeled 'T1199410-98' in the bottom right corner. + +Diagram of elements associated with diversity handover. + +**Figure 3-3/Q.1711 – Naming of elements associated with diversity handover** + +# 4 IMT-2000 Specific Functions + +This clause identifies some of the network functions that are needed to support IMT-2000 CS1 capabilities. The functions are grouped according to their relationships to overall service and network capabilities. Family members have the option to selectively implement only those functions that are needed to support the services they choose to offer. + +## 4.1 Functions related to overall system access control + +System access is the means by which an IMT-2000 user is connected to IMT-2000 in order to use IMT-2000 services and/or facilities. System access may start from either the mobile side, e.g. a mobile originated call, or the network side, e.g. a mobile terminated call. + +**System access information broadcasting:** This function provides the mobile terminal with information which may include access rights, network identification, frequency bands used, configuration of logical channels, etc. This information enables the mobile terminal to configure itself so that it can camp on a cell, register, and initiate and receive calls. + +**System access information monitoring and analysis:** This function monitors and analyses system access related information transmitted from the network to one or more mobile terminals. The functionality required for analysing this information resides in the mobile terminal. + +The purpose of the monitoring process is to determine which networks, network operators, and/or service providers are available, and what service capabilities they support. Monitoring the system access information forms the basis for the analysis related to which cell a mobile terminal shall camp on, and which physical radio channel(s) it will occupy once engaged in dedicated communications. Monitoring for relevant parameters implies that the mobile terminal must be able to scan IMT-2000 frequency bands for necessary information. + +Once the mobile terminal has gathered system access related information, the information is analysed to determine which cell the mobile terminal should camp on. + +Selection of service provider, network and network operator is governed by user's choice, i.e. by subscription or by real-time choice according to, for instance, service capabilities, charges, access rights, etc. + +Since several network operators may share the same infrastructure, the selection of network operator and selection of network are logically distinct processes. + +The *System access information monitoring and analysis* function generates appropriate control information to ensure that the mobile terminal camps on a suitable cell, belonging to a suitable network or network operator, where the user has access to the services subscribed to. + +**Cell selection in idle mode:** This function is performed in idle mode only. It controls the tracking of the active cell by the mobile terminal. Based on the selection of network operator made by the *System access information monitoring and analysis* function and based on the radio channel measurements of the appropriate physical channels and broadcast control channels of the available cells, the mobile terminal selects a cell to camp on (the active cell). The mobile terminal will scan and decode the appropriate logical channels at this cell, and also access the network (whenever appropriate) via this cell. + +It may be necessary to select a new active cell, e.g. if the mobile terminal moves, or if the radio channel performance degrades below an acceptable threshold. Therefore, the mobile terminal may require knowledge of broadcast channels of surrounding cells, at least such knowledge may simplify the scanning process. + +Acquisition and selection of surrounding cells involves scanning and decoding the appropriate physical channels and relevant control channels of neighbouring cells within the same network as the currently active cell. + +**Cell selection in packet data transfer mode:** When a mobile terminal is engaged in a packet data transaction but not engaged in a circuit-switched connection, it is in packet data transfer mode. + +The *Cell selection in packet data transfer mode* function enables the mobile terminal to select the best cell to use in establishing a communication path. This involves the measurement and evaluation + +of signal quality from neighbouring cells, as well as the detection and avoidance of congestion within candidate cells which the mobile terminal may use. + +## 4.2 Functions related to radio resource management and control + +Radio resource management is concerned with the allocation and maintenance of physical channels. Logical channels are logical paths to support specific access radio link. IMT-2000 radio resources must be shared between circuit mode (voice and data) services and other modes of services (e.g. packet data transfer mode). + +### 4.2.1 Synchronization control + +This function evaluates the information provided by the *System access information monitoring and analysis* and ensures correct synchronization of the mobile terminal with the network. + +### 4.2.2 Functions related to access radio link control + +**Access radio link set-up and release:** This function is responsible for the control of connection element set-up and release of the access radio link. The purposes of this function are + +- a) to participate in the processing of an end-to-end connection set-up and release which will be activated by a request from other functional entities at call set-up/release; and +- b) to manage and maintain the access radio link after an end-to-end connection has been established. (It may also be invoked to cater for in-call service modification or at handover execution.) + +**Reservation and release of physical radio channels:** This function consists of translating the access radio link set-up or release requests into physical radio channel requests, reserving or releasing the corresponding physical radio channels and acknowledging this reservation/release to the requesting entity. Acceptability of such physical radio channel requests is determined by the *Radio resource request acceptability judgement* function. + +This function may also perform physical channel reservation and release in the case of a handover. Moreover, the amount of radio resource required may change during a call, due to service requests from the user or macro-diversity requests. Therefore, this function must also be capable of dynamically reserving or releasing physical channels during a call. + +**Allocation and de-allocation of physical radio channels:** This function is responsible, once physical radio channels have been reserved, for actual physical radio channel usage, allocating or de-allocating the corresponding physical radio channels for information transfer. + +**Packet data transfer over radio function:** This function provides packet data transfer capability across the IMT-2000 radio interface. This function includes procedures which: + +- a) provide packet access control over radio channels; +- b) provide packet multiplexing over common physical radio channels; +- c) provide packet discrimination within the mobile terminal; +- d) provide error detection and correction; +- e) provide flow control procedures; +- f) provide load balancing across RF channels. + +### 4.2.3 Functions related to RF power control management + +**RF power control:** In order to minimise the level of interference (and thereby maximise the re-use of radio spectrum), it is important that the radio transmission power is not higher than what is required for the requested service quality. Based on assessments of radio channel quality, this + +function controls the level of the transmitted power from the mobile terminal as well as the base station. + +**RF power setting:** This function adjusts the output power of a radio transmitter according to control information from the *RF power control* function. The function forms an inherent part of any power control scheme, whether closed or open loop. + +### 4.2.4 Functions related to random access + +**Random access initiation:** This function is used by a mobile terminal when it accesses the network. Due to the multiple access nature of the radio interface (many mobile terminals attempting to access common resources in an independent and random way), a specific random access procedure may have to be used when the mobile terminal accesses the network for the setting up of a connection or other applications. This function will start this procedure when required. + +**Random access detection and handling:** This function in the network detects the random access initiation attempt by the mobile terminal and responds appropriately. The handling of the random access may include procedures for a possible resolution of colliding attempts, etc. The successful result will be the generation of a request for allocation of appropriate resources for the requesting mobile terminal. + +### 4.2.5 Functions related to radio resource request acceptability + +**Radio resource request acceptability information setting:** This function sets and updates the information on possibility of radio resource allocation based on the radio resource availability in a cell. This information is used by the *Radio resource request acceptability judgement* function. + +**Radio resource request acceptability information broadcasting:** This function broadcasts, in a cell, the radio resource request acceptability information obtained from the *Radio resource request acceptability information setting* function. + +**Radio resource request acceptability judgement:** This function can be implemented in the network as well as in mobile terminals. In the network, this function judges the possibility of radio resource allocation upon each request of such a resource based on the radio resource request acceptability information obtained from the *Radio resource request acceptability information setting* function. In the mobile terminal, this function judges the radio resource request acceptability information broadcast by the *Radio resource request acceptability information broadcasting* function. Based on the result, this function permits the initiation of service request from the mobile terminal which requires radio resources (e.g. call origination) only when positive result is obtained from the judgement. + +## 4.3 Functions related to channel coding + +**Radio channel source and error protection coding and decoding:** This function is to protect data from transmission errors on the radio channels by attached specific coding. Major coding schemes include: + +- a) Convolutional code which is used for both error detecting and correcting; +- b) Cyclic Redundancy Check which is used only for error detecting; +- c) Interleave which is used for error protecting. + +The coding is performed independently of the content or meaning of the data. + +## 4.4 Functions related to handover + +**Radio channel quality estimation:** This function performs measurements on radio channels (current and surrounding cells) and translates these measurements into radio channel quality estimates. Measurements may include: + +- a) received signal strengths (current and surrounding cells); +- b) estimated bit error ratios; +- c) estimation of propagation environments (e.g. high-speed, low-speed, satellite, etc.); +- d) transmission range (e.g. through timing information); +- e) Doppler spread; +- f) synchronization status. + +In order for these measurements and the subsequent analysis to be meaningful, some association between the measurements and the channels to which they relate should be made in the analysis. Such association may include the use of identifiers for the network, the base station, the cell (base station sector) and/or the radio channel. + +**Cell selection in dedicated mode:** When a mobile terminal is engaged in a circuit-switched connection, it is in dedicated mode. When a mobile terminal is in dedicated mode, it may additionally be engaged in a packet data transaction. + +The *Cell selection in dedicated mode* function enables the mobile terminal to select the preferred cell to which a circuit-switched connection may be accessed or handed over. The cell is selected from a candidate list which the network sends to the mobile terminal. The function involves the measurement and evaluation of signal quality from neighbouring cells, as well as the detection and avoidance of congestion within candidate cells to which access or handover may be requested. + +**Quality of service assessment:** This function assesses the overall quality of service. This may take into account radio channel quality estimates (including estimates from surrounding cells), packet throughput, delay, and other quality of service metrics. The overall quality of service is compared with requested limits and with estimates from surrounding cells. Depending on the outcome of this comparison, the *Resource re-allocation* function, the *Macro-diversity control* function or the *Handover execution* function may be activated. + +**Resource reallocation:** A network always monitors the status of how the resources are used. When a network detects the insufficiency of available resources, it may perform inter or intra cell handover sequence, or reallocation of other resources being used in order to get different available resources. + +#### Handover decision + +- **initiated by the terminal:** This function results from the *Quality of service assessment* function and generates a request for new resources. In this case the terminal uses a resource reallocation or handover strategy to select new resources. When required, it may also request that the network combine the diversity paths. +- **initiated by the network:** This function results from the *Quality of service assessment* function or the *Resource reallocation* function and generates a request for different resources. In this case the network uses a resource reallocation or handover strategy to select new resources and coordinates assignment of the new resource. When required, it may also request that the terminal combine the diversity paths. + +**Macro-diversity control:** Upon request from the *Handover decision* function or the *Quality of service assessment* function, this function controls the duplication/replication of information streams to receive/transmit the same information through multiple physical radio channels (possibly in different cells) from/towards a single mobile terminal. + +This function also controls the combining of information streams generated by a single source, but conveyed via several diversity sub-links. The *Macro diversity control* function controls macro-diversity execution (i.e. distribution and combination of the information stream) which is located at the two endpoints of the connection link on which macro-diversity is applied. Such points exist both in the network and in the mobile terminal. + +**Handover execution:** This function is in control of the actual handing over of the communication path. It comprises two sub-processes: handover resource reservation and handover path switching. The handover resource reservation process will reserve and activate the new radio and wireline resources that are required for the handover. When the new resources are successfully reserved and activated, the handover path switching process will perform the final switching from the old to the new resources, including any intermediate path combination required, e.g. handover branch addition and handover branch deletion in the diversity handover case. + +**Handover completion:** This function will free up any resources that are no longer needed. A re-routing of the call may also be triggered in order to optimize the new connection. + +**Handover trigger:** This function identifies cells that may be added or deleted from the access link. This information is used by the *Handover decision* function. + +## 4.5 Functions related to location management & geographic position finding + +### 4.5.1 Functions related to terminal paging + +Terminal paging is a feature by which the mobile terminal is finally located within its current cell for the establishment of a network initiated (mobile terminated) connection to the terminal for the purpose of signalling, or packet delivery. In case of packet delivery, terminal paging may transfer user data. + +**Paging decision and control:** This function will initiate identification of the location area of the mobile terminal and its status (e.g. busy, idle, registered active). Paging of the mobile terminal may or may not be performed depending on the mobile terminal status [e.g. if the mobile is already active (in a call or exchanging packets), paging may not be needed] or other factors decided by the network operator of the serving system where the mobile is located (e.g. network management conditions such as no available channels, emergency conditions). The *Paging decision and control* function will also process the paging response from the mobile terminal. + +**Paging execution:** This function will execute the terminal paging within its area of responsibility (e.g. group of cells), based on information received from the *Paging decision and control* function. The execution includes identification of radio cells in which paging is broadcast. It may involve repetitions of the paging. + +**Paging detection:** This function detects the paging and processes the mobile terminal response to the page in the mobile terminal. + +### 4.5.2 Functions related to location data management, registration and deregistration + +#### 4.5.2.1 Location data management + +Location data management is a grouping of features/functions necessary to enable the network to locate a mobile terminal in order to establish a connection or to deliver packets to it. The location information may be provided with different accuracy, depending on the current mode of operation of the terminal (active circuit-switched connection, stand-by packet-data connection, etc.). + +**Location data management initiation:** By assessing the result of *System access information monitoring and analysis* function and/or taking into account location management status, this function will request location management related service features (e.g. terminal location updating, + +detach, attach) toward the network. This function may also request the features periodically or on demand of the network. + +**Location data management:** This function controls procedures of the location management related service features. The procedures include updates of location information and/or MT status information (i.e. whether terminal is reachable or not) in data base. This includes updating of old and new location data storage entities as well as initiating the erasure of location data from storage entities that are no longer needed. This function may also enable the network to initiate location management related service features to update its data base. + +To categorise how the network recognises the mobile terminal location, several location management states may be introduced, for example: + +Location unknown states: the network has no knowledge about mobile terminal location. + +Location known states: the network has some kind of knowledge about mobile terminal location. In this state, different accuracy of mobile terminal location could exist. + +Accuracy of mobile terminal location: to categorise how precise the mobile terminal location of "Location known" state is recognised by the network, several kinds of location accuracy may be introduced, for example: + +Location area accuracy: the accuracy is composed of multiple cell areas that would be sufficient to perform terminal paging to locate the mobile terminal. + +Cell area accuracy: the accuracy is composed of a single cell or a limited number of cells through which the terminal communicates with the network. + +In case of different operation modes (i.e. circuit-switched operation and packet-data operation) of a terminal, mobile terminal location may be recognised with different accuracy independently for each operation mode. To reduce the network load due to location updates, in the case of parallel operation of circuit-switched and packet-data communication, location update information is shared. + +**Terminal initiated location update** is a function by which a mobile terminal will notify a network of its existence and of its location within the network and by which the location information of the terminal within the network is continuously updated when required. It is normally used when a terminal first appears in a network domain or when no previous location details are known (e.g. after terminal or network failure) or when the terminal moves into a new location area or when the terminal has not interacted with the network within a period of time. + +**Network initiated location update** is a function by which the network requests a terminal to identify itself to the network and thus its location within the network can be established. This is normally used when a terminal has not interacted with the network within a period of time and the network wants to determine if the terminal is still reachable or not. + +#### **4.5.2.2 Location registration for call and service delivery** + +Location update of terminal location in the Serving network is updating the Home network mobility functions of the location of the terminal for routing of incoming calls. The internetwork signalling capability allows a service provider and a Serving network operator to communicate both the capabilities of the Serving network and the service capabilities of the subscriber in order to enable service transparency. + +Service profile downloading from the Home network to the Serving network includes some of the following possible location registration scenarios: + +For IMT-2000 standardized services, the following approaches may be considered: + +- a) the Home network downloads the subscriber profile to the Visited network; the profile will be used by the Visited network for the originating communication service, without requesting further information, other than (maybe) authentication information, to the Home network; +- b) the Home network does not download the subscriber profile to the Visited network; for originating communication service, the Visited network will request instructions to the Home network. + +For non-IMT-2000 standardized services, the following approaches may be considered: + +- c) in association with case a) above, the Home network downloads a VHE subscription information to the Visited network as part of the service subscriber profile; originating and/or terminating communication service will cause the Visited network to contact the Home network for instructions; +- d) in association with case b) above, the Home network does not download any information to the Visited network to indicate VHE subscription information; as in case c) above, originating and/or terminating communication service causes the Visited network to contact the Home network to request instructions. + +From the location registration procedure it is possible to invoke IN services and the location registration procedure can be modified according to the service logic of the invoked IN services. + +#### 4.5.2.3 IMT-2000 subscriber de-registration + +An IMT-2000 subscriber may explicitly de-register or leave the task of de-registration to the network (implicit de-registration). When an IMT-2000 subscriber leaves a system, its associated profile may also be removed through either explicit or implicit de-registration. + +### 4.5.3 Functions related to geographic position finding + +**Geographic position determination:** This function will enable the IMT-2000 network and/or the mobile terminals to compute the geographical position of mobile terminals based on dynamic information (e.g. characteristics of the RF signals received such as timing, signal strength, angle of incidence) and prior knowledge of relevant information (e.g. stored information such as time reference, geographic position of the network elements, etc.). Both the IMT-2000 network and the mobile terminals may have the capability to effect the characteristics of the RF signals in a manner that will improve the quality of the reception such that meaningful results can be obtained. + +**Geographic position notification:** This function will enable the IMT-2000 network and/or the mobile terminals to notify interested and authorised functional entities of the network or mobile terminals of the geographical position of a mobile terminal, once this position has been determined. + +## 4.6 Functions related to mobile call handling (including routing) + +### 4.6.1 Common functions + +**Service feature analysis:** This function will check whether the requested service is compatible with the current subscription. It may also include compatibility checking of the requested service against the capabilities of the terminal. + +**Provision of terminal capability information:** This function will provide the necessary information (terminal capabilities) required by the network to identify what functions and features are supported by this terminal. + +**Negotiation of data rates and quality of service:** Various data rates should be available to the user depending on the environment in which the user is operating. The environments and data rates are provided in ITU-R Recommendation M.816-1, Framework for Services Supported on IMT-2000 [2]. + +Negotiation for the data rate and quality of service to be used between the user and the network needs to be possible. The negotiation may be at the beginning of the call/packet data instance and/or at subsequent points in the call/packet data instance depending on current network conditions and user environment. + +The interchange between user and network may be comprised of asymmetric data rates. The values of these rates may be part of the negotiation procedures. + +**Access Restrictions:** In principle, it is assumed that a subscriber can access IMT-2000 services through diverse access networks. However, access limitations shall be possible according to subscription options and authorisation. Access restrictions may also be imposed by the Serving (Visited) network because of network conditions or other reasons. + +### 4.6.2 Functions specific to routing of circuit-switched mobile calls + +**Request routing information:** For mobile terminated calls, this function will request the *Routing information handling* function for relevant routing information. + +**Routing information handling:** For mobile terminated calls, this function will provide the network with relevant routing information for the call to be established. Service capabilities can be stored as dynamic data in the network derived from end-to-end negotiation obtained at call set-up. Terminal capabilities could be obtained at service and user registration. Bandwidth and QoS modification on demand is an advanced technical requirement. + +NOTE – The routing information may point to a final routing address or to an entity which will provide further routing information. In the latter case, this entity may trigger paging decision and control. + +### 4.6.3 Functions related to routing and addressing of IMT-2000 packet data services + +#### 4.6.3.1 Functions related to routing of packet-data mobile communication service + +This function supports routing of packet-data communication service. The communication service may be provided by one of the following methods, during a mobile service instance: + +##### a) dial-up manner request and routing + +This method allows the user to establish an on-demand communication path of choice. When the user requests the establishment of this on-demand communication path, the user supplies the packet handler "address" as destination address information. Then the network makes routing for the service according to the supplied destination address in an ordinary telephony manner (i.e. call set-up and establishment). The release of this communication path will be via an ordinary telephony service release request (i.e. call release). + +##### b) service subscription based request and routing + +This method allows the user to specify the packet handling function of choice at the time of service subscription with the home IMT-2000 family member. When the user initiates a mobile service instance with an IMT-2000 family member, the communication service (e.g. context association) between the mobile terminal and the specified packet handling function will be established. The release of this communication path occurs at the termination of the mobile service instance. + +#### 4.6.3.2 Functions related to types for connections and address management of mobile data packets + +IMT-2000 supports point-to-point services (e.g. connectionless and connection-oriented) and point-to-multipoint services (e.g. group call and multicast services). + +Functions shall include dynamic and static address management, support of Internet Control Message Protocol (ICMP) messaging, packet filtering and data privacy. + +### 4.6.4 Functions related to handling of multimedia calls + +The functions to support multimedia in IMT-2000 are the ability to provide bearers with flexible quality of service and the ability to provide parallel calls and point-to-multipoint calls. The flexible quality of service allows the user to modify the quality of service during an on-going call as required by the used applications. The flexible quality of service ensures that the requirements of all media types can be fulfilled. The parallel calls can be used to transfer different media components in different calls. Point-to-multipoint calls can be used, for example, for multimedia distribution services. Coordination and synchronization of different media components can be done by end system applications, which are outside the scope of this Recommendation. + +### 4.6.5 Management of both circuit-switched and packet-switched communications + +This function supports circuit-switched and packet-switched communication paths simultaneously. + +## 4.7 Functions related to data coding & compression + +**Data coding:** This function indicates voice coding or compression of image data. The coding depends on the content or meaning of the data. + +**Signalling compression function:** The *Signalling compression* function will optimize the use of radio path capacity by transmitting as little of the signalling as possible while at the same time preserving the information contained within it. + +**Data compression:** The data compression function will optimize the use of the radio path by transmitting as few information bits as necessary to accurately represent the network protocol packet contents, e.g. V.42 *bis* data compression. + +## 4.8 Functions related to network intelligence and service control + +### 4.8.1 Functions supporting UPT users + +This function provides the ability to access telecommunication services at any terminal (not limited to IMT-2000 systems) on the basis of a personal identifier (e.g. the UPT number). This function involves the network capability to locate the terminal associated with the user for the purposes of addressing, routing, and charging of the UPT user for calls. Detailed functions and their allocation to each Functional Entity (FE) for IN-based UPT services are described in Recommendation Q.1541 [8]. + +### 4.8.2 Functions related to service portability + +Service portability is the capability of the network to provide a particular set of services/features from any user access point within an IMT-2000 environment and according to the user's requests. From the subscriber's perspective, the service portability is the ability of users to have transparent access to a set of their subscribed services when roaming. + +The service portability feature of the global roaming uses the "Virtual Home Environment" concepts or standardized supplementary services (see 7.2.2.5). + +### 4.8.3 Functions supporting supplementary services + +The optional supplementary services are associated with an IMT-2000 service subscriber upon specific subscription. + +### 4.8.4 Functions related to support of the Virtual Home Environment + +The Virtual Home Environment (VHE) capability is an integrated network capability that provides operator specific services that are accessible by the user even when this user is roaming outside the Home network. + +The following functions are identified to support the provisioning of VHE supplementary services: + +- **Provisioning of VHE specific service profiles:** This function is required to ensure that the Visited network receives the appropriate information to invoke the VHE supplementary services. The VHE service profiles are part of the IMT-2000 subscriber profiles. It contains the trigger information that has to be exchanged between the Home network and the Visited (Serving) network. +- **Dynamic arming of triggers within the switching network:** This function is required to activate the VHE triggers including the trigger profile (e.g. trigger conditions, information, etc.). The arming of these VHE triggers can be activated by a request from the Home network or service provider. +- **Downloading VHE trigger profiles to the Visited network:** This function is required to reduce the unnecessary signalling between the Home network and Visited network. The VHE trigger profile is downloaded towards the Visited network together with the IMT-2000 subscriber profile. +- **Service logic execution (Home network capability):** This function requires an agreement between the Home network and Visited network for the Home network to execute service logic from the Home network to control the Visited network resources. IN supported capabilities must be compatible between the two networks. +- **Service logic execution (Visited network capability):** This function requires an agreed upon application execution environment to execute distributed service logic from the Home network within the Visited network. +- **Service addressing (Visited network capability):** This function is required to allow the Visited network to address specific service control functions. This is used to request the initiation of a VHE context between the Visited network and the Home network. +- **Security and screening functions (Visited network to Home network):** These functions are required to enable the networks to verify each other's identity and bind the context between the networks for the execution of the VHE services. + +### 4.8.5 Functions related to support of IN + +One mechanism for providing services in IMT-2000 is use of Intelligent Network (IN) capabilities. + +Mobile originated calls, mobile terminated calls, mobility registration and authentication activities and call unrelated activities can trigger IN procedures in the IMT-2000 network. Operator specific services can be implemented based on these generic service events. + +The functions related to IN capabilities are associated with the provisioning of IN services. + +The following functions are identified: + +- **Service logic execution:** This function executes service logic instances that are requested by the network on behalf of the user. + +- **Service/User data manipulation:** This function stores, retrieves or performs any other service data management activities. +- **Handling specialized resources:** This function interacts with the user by means of dedicated messages, such as text message, announcements, voice mail messages, etc. These kind of capabilities are supported by IN platforms. +- **Service logic triggering:** This function enables efficient interaction between the service logic and the call (un)related process that invoked that service. +- **Any time interrogation:** This function enables the service logic instance to retrieve the mobility management related information, such as location information and subscriber status information. + +The details of these functions are described in the IN series of ITU-T Recommendations. + +## 4.9 Additional functions related to global roaming + +The functions in this subclause are used to support global roaming in addition to other functions described. + +For IMT-2000 CS1, two alternatives for global roaming are envisaged: + +- 1) Roaming of UIM and MT (terminal mobility): a UIM provided by the Home network is used with an MT available in the Home network and the Visited network. +- 2) Roaming of UIM (UIM portability): a UIM provided by the Home network is used with an MT available by the Visited network. + +Figure 4-1 depicts the above two global roaming alternatives. + +![Diagram of UIM and MT global roaming architecture showing IMT-2000 Family Member A (Visited Environment) and IMT-2000 Family Member B (Home Environment).](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +The diagram illustrates the architecture for UIM and MT global roaming. It is divided into two main environments: IMT-2000 Family Member A (Visited Environment) and IMT-2000 Family Member B (Home Environment). + +**IMT-2000 Family Member A (Visited Environment):** This environment contains two main components: + + +- Home Network provided:** A box containing a **UIM** and an **MT**. A label "Compatible with Home and Visited Networks" is placed above the MT. +- Visited Network:** A box containing a **RAN** (Radio Access Network) and a **CN** (Core Network). + + Interfaces are shown between the UIM and MT (labeled **UIM-MT**), between the MT and RAN (labeled **MT-RAN**), and between the CN and the Home Network (labeled **NNI**). + +**IMT-2000 Family Member B (Home Environment):** This environment contains a **Home Network** box with a **CN** (Core Network). + +A horizontal line connects the CN in the Visited Network to the CN in the Home Network, passing through the NNI interface. + +Below the diagram, a note states: "UIM-MT, MT-RAN and NNI are IMT-2000 interfaces". + +A small code "T1199420-98" is visible in the bottom right corner of the diagram area. + +Diagram of UIM and MT global roaming architecture showing IMT-2000 Family Member A (Visited Environment) and IMT-2000 Family Member B (Home Environment). + +**Figure 4-1a/Q.1711 – UIM and MT global roaming** + +![Diagram of UIM global roaming architecture showing IMT-2000 Family Member A (Visited Environment) and IMT-2000 Family Member B (Home Environment).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +The diagram illustrates the architecture for UIM global roaming between two IMT-2000 Family Members, A and B. + +- IMT-2000 Family Member A (Visited Environment):** This environment contains a "Home Network provided" with a UIM (User Identity Module). It also contains a "Visited Network" which is "Compatible with visited Networks" and consists of an MT (Mobile Terminal), RAN (Radio Access Network), and CN (Core Network). The UIM is connected to the MT via the **UIM-MT** interface. +- IMT-2000 Family Member B (Home Environment):** This environment contains a "Home Network" with a CN (Core Network). +- Interconnections:** The CN in Member A's Visited Network is connected to the CN in Member B's Home Network via the **NNI** (Network-to-Network Interface). +- Reference:** The diagram is labeled with the reference code T1199430-98. + +UIM-MT and NNI are IMT-2000 interfaces + +Diagram of UIM global roaming architecture showing IMT-2000 Family Member A (Visited Environment) and IMT-2000 Family Member B (Home Environment). + +**Figure 4-1b/Q.1711 – UIM global roaming** + +Selection of service providers allows mobile terminals to roam between networks supported by the same or different service providers/operators. This may include the use of mechanisms to preferentially select certain service providers/operators where multiple service providers/operators provide coverage in the same area. + +Functions related to interworking includes the mechanisms to provide, for example, charging, fraud, and problem resolution. These mechanisms may be used in "real time" cases. + +## **4.10 Functions related to user privacy & network security** + +### **4.10.1 Functions related to ciphering** + +**Confidentiality control:** This function provides the necessary information (keys or other parameters to calculate the keys) required for the physical radio channel ciphering and deciphering. Due to the fact that an operator may not wish to disclose the security algorithms used to other operators, the confidentiality control should be regarded as a centralised function. The confidentiality control is closely related to the authentication mechanisms. + +**Physical radio channel ciphering:** This function is a pure computation function whereby the radio transmitted data can be protected against a non-authorised third-party. Ciphering may be based on the usage of a session-dependent key, derived through signalling and/or session dependent information. + +**Physical radio channel deciphering:** This function is a pure computation function which is used to restore the original information from the ciphered information. The deciphering function is the complement function of the ciphering function, based on the same ciphering key. + +**Ciphering execution control:** This function will deliver ciphering information and trigger ciphering and deciphering on the physical radio channel. Ciphering information will be obtained from the *Confidentiality control* function. + +### **4.10.2 Functions related to authentication** + +**Authentication data management:** This function controls and manages the authentication data which include authentication parameters and authentication information required in the network. + +**User authentication processing:** Based on parameters received from the *Authentication data management* function, this function will initiate and control the user authentication procedure and process the results. Mutual authentication supports functions for the verification between networks (including service providers) and users (including User Identity Modules). This includes the function for a network to verify the user, (i.e. the network determines if the user is indeed who the user claims + +to be) and the function for users to verify the network (i.e. the user determines if the network is indeed the network it states to be). + +From the user authentication procedure it is possible to invoke IN services and the user authentication procedure can be modified according to the service logic of the invoked IN services. This capability does not include the generation of authentication parameters (e.g. triplets). + +### **4.10.3 Functions related to network fraud/abuse control** + +Functions in the IMT-2000 Network have the capability to provide necessary information for fraud control, the monitored events being typically call addressing information, geographic position, subscriber identity, network element address information and supplementary service invocation events. + +Determining whether fraud or abuse is taking place may involve a combination of real time call, mobility and service processing, and non-real time analysis of such processing across multiple instances of calls and service invocations. + +Security mechanisms protect the IMT-2000 user, service provider, and network operator from fraudulent use of the system, and maximise their privacy. + +### **4.10.4 Functions related to identity management** + +Identity management is a grouping of functions to prevent a permanent user identity from eavesdropping over radio interface to keep confidentiality of the identity. Temporary user identity is used to make network access instead of permanent user identity. This consists of functions to: + +- a) assign a temporary user identity to a mobile terminal in case of network access with a permanent user identity; +- b) update a temporary user identity assigned to a mobile terminal in case of network access with a temporary user identity or validity time-out; +- c) inquire a mobile terminal about its permanent user identity in the case where a received temporary user identity is unknown, both in a Visited network domain and another network domain which assigned the temporary user identity; +- d) retrieve a permanent user identity from another network domain in the case where a received temporary user identity is unknown in a Visited network domain but is known in another network domain which assigned the temporary user identity. + +## **4.11 Functions related to support of emergency services** + +**Identification of emergency services calls:** This function will handle the tasks of recognising calls to emergency services by end users (calls originated from emergency services personnel to the end users may be treated as normal call processing). + +**Emergency services calls handling:** This function will enable the IMT-2000 network to provide priority access to identified emergency services calls, override the normal access and charging procedures and provide the emergency services providers with enhanced capabilities (e.g. call back) and information (e.g. location or geographic position) about the user of such services. + +## **4.12 Functions related to charging** + +**Circuit-switched information generation:** At each relevant entity, this function will collect information relevant for charging at call setup, during the call and at call release. The information is sent to the *Charging processing* function. Relevant information for charging may include such parameters as: duration of call, time dependent charging rate, access charge rate, bandwidth used, invoked service instances, and registration charge rate. + +**Packet data information generation:** At each relevant entity, this function will collect information relevant for charging at registration or attach, packet transfer, and at deregistration or detach. The information is sent to the *Charging processing* function. Relevant information may include such parameters as: number of packets exchanged, packet data rate or bandwidth used, average packet size, total bytes exchanged, access charge rate and registration charge rate. + +**Charging processing:** This function will process the information received from the charging *information generation* function(s) and provide the billing and accounting functions with relevant parameters. + +## 4.13 Functions supporting IMT-2000 users + +UIM portability is an integral capability within the IMT-2000 networks that supports mobility of UIM devices among the IMT-2000 terminals. In this context, UIM portability requires a physical separated device from the terminal. Therefore, this capability is an optional capability since IMT-2000 supports a physical separated UIM as well as an integrated UIM within the terminal. + +**IMT-2000 personal mobility** is a function which enables a user to transfer her/his identity between IMT-2000 mobile terminals. It is implicit in this definition that the IMT-2000 personal mobility is to access the telecommunication services delineated in the user's service profile, on any IMT-2000 mobile terminal. Every IMT-2000 user has a User Identity Module (UIM) which can interface and be associated with any IMT-2000 terminal. + +## 4.14 Functions related to subscriber data management + +### 4.14.1 Functions related to managing data in Serving networks + +Managing subscriber data within Serving networks includes the capability to update or delete certain subscriber data within the Serving network. This could be requested on the following occasions: + +- the operator has changed the subscription of one or more supplementary services, basic services or data of a subscriber; +- the operator has applied, changed or removed operator-determined call barring; +- the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; +- the operator has withdrawn the subscription of one or more supplementary services. + +The following functions are required: + +**Insert subscriber data:** This function updates certain subscriber data within the Serving network. It can change the subscriber data associated with the subscriber's bearer services (e.g. speech, data, etc.), tele-services (e.g. facsimile, speech, etc.), supplementary services, VHE services, regional subscription, etc. + +**Delete subscriber data:** This function deletes certain subscriber data within the Serving network. The possible effects of this function are: deletion of basic services, deletion of supplementary services or deletion of VHE services. + +### 4.14.2 Functions related to fault recovery of subscriber data + +Fault recovery will enable the recovery from faulty situations, such as invalid subscriber data or missing location data within the Home or Serving network. Two functions are required: + +**Reset:** This function is used to indicate to a list of Serving networks that a failure has occurred within the Home network. + +**Restore data:** This function is used to indicate that the subscriber information associated with the provided IMUI is not available or not valid when the Home network requests routing information (i.e. roaming numbers). The indication is from the Serving network towards the Home network. + +### 4.14.3 Functions related to subscriber control of supplementary services data + +Supplementary service (SS) control enables the network operator, on behalf of the subscriber, or the subscriber directly, to control the supplementary service. The following functions are required: + +**SS data handling:** This function updates, retrieves or erases the SS data. The subscriber can initiate the SS data update or erasure. The retrieval of the SS data can also be requested by the Serving network when it detects that the SS requested by the subscriber requires interrogation on its data. + +**SS activation:** This function activates or deactivates the SS upon requests from the subscriber. + +**SS password protection:** this function is required to protect the subscriber-controlled operations on the SS. This includes the registration of a (new) password upon request of the subscriber. + +**SS subscriber data:** This function is required to exchange subscriber data between the subscriber and the network (Home or Serving). This could be initiated by the subscriber or by the network (i.e. Home or Serving). + +**SS invocation:** This function invokes the subscriber-requested SS. + +## 4.15 Functions related to messaging service management + +Short Message Service (SMS) provides a means of sending messages of limited size to and from the mobile terminal. The provision of SMS makes use of a message centre which acts as a store and forward centre for short messages. + +Application Data Delivery Service (ADDS) provides general purpose wireless data delivery. It delivers application/teleservice messages between service users and utilises the message centre to store and forward messages. + +**Message delivery:** This function delivers the message towards the mobile terminal. This includes the retrieval of the routing information, forwarding the message from the message centre to the Serving network and finally delivering the message towards the mobile terminal. + +**Message handling:** This function receives the message from the mobile terminal and forwards this message to the message centre for storage and subsequent delivery. + +**Message alerting:** This function alerts the Home network that a message was stored at the message centre for a mobile terminal. A "message waiting indication" will be sent to the mobile terminal when it becomes reachable again. + +## 4.16 Functions related to software configurable terminals + +The software configurable terminals capability provides the mechanisms which allow applications to interact and operate with any MT. The applications and related data can permanently reside within the UIM, the MT, or an external device or can be downloaded by the Core Network. + +**Capability profile exchange:** This function provides a mechanism for the MT, the UIM and the Core Network to exchange service capability information. For example, the following types of exchanges may occur: + +- MT services capability may be provided to the UIM or Core Network; +- UIM services capability may be provided to the MT or Core Network; +- Core Network services capabilities may be provided to the UIM. + +**Application data transfer:** This function provides a mechanism for the MT, the UIM and the Core Network to exchange applications and associated data. For example, the following types of exchanges may occur: + +- MT data may be provided to the UIM or Core Network; +- UIM data and applications may be provided to the MT or Core Network; +- Core Network data and applications may be provided to the UIM or MT. + +**Proactive applications:** This function gives a mechanism whereby applications can initiate actions to be taken by the MT. These applications may reside in the UIM, MT or an external device or may be downloaded from the Core Network. Examples of these actions include: + +- display text from the UIM or Core Network to the MT; +- send a short message; +- set up a voice call to a number held by the UIM, MT or an external device; +- set up a data call to a number with bearer capabilities held by the UIM, MT or an external device; +- send a supplementary service control or service data; +- play tones in earpiece; +- initiate a dialogue with the user; +- provide local information from the MT to the UIM or to the Core Network; +- provide help information on each command involved in the dialogue with the user. + +**Screening service by UIM:** This function allows that when this screening service is activated by the UIM, all dialled digit strings, supplementary service control service data are first passed to the UIM before the MT sets up the call, the supplementary service operation or the service data operation. The UIM has the ability to allow, bar or modify the call, the supplementary service operation or the service data operation. For example, a call request can be replaced by a supplementary service operation or a service data operation, and vice-versa. + +**Security:** This function allows that applications, designed with the features in this capability, can be used to ensure data confidentiality, data integrity, and data sender validation, or any subset of these. + +# 5 The IMT-2000 Functional Models + +The functional model described here contains all functions necessary for supporting all capabilities specified by CS1 of Recommendation Q.1701. Family members have the option to selectively implement only those functions which are needed to support the services they choose to offer. + +In the IMT-2000 functional model, the functions required for IMT-2000 service support have been grouped into Functional Entities (FEs) and the functional relationships between these FEs have been indicated. Since there are two possible approaches to the allocation of call control and connection control related functionality, two alternatives are identified: Alternative 1 with integrated call control and connection control FEs and Alternative 2 with separated call control and connection control FEs. This results in two slightly different functional models. + +Besides the above-mentioned two alternatives, the model has been developed to be non-service specific as well as non-environment specific. It is mainly functional and does not imply any limitations regarding physical implementations or distribution of functions onto physical configurations. In addition, the model should allow modularised development to facilitate evolution to support further advanced end-to-end services. + +## 5.1 Modelling principles + +The same basic modelling principles, as used for IN DFP modelling, have been used. Subclause 5.3 describes FEs which are dependent on the transmission technology. They are specific to the radio access control. Subclause 5.4 describes FEs which are independent of the transmission technology. They specify communication and service control. + +Furthermore, a mapping of the FEs to the subsystems UIM, MT, RAN and CN is also shown in the models to reflect the applicability of the IMT-2000 Family of Systems concept. In the functional models in the current Recommendation Q.1711, the allocation of FEs to the RAN and CN subsystems is preliminary. The final allocation of FEs to these subsystems will be addressed at a later stage. The interfaces between these four subsystems are shown as vertical lines. Thus the model supports the interfaces that are defined according to Recommendation Q.1701. + +A separation has been made between the communications and service control and the radio access control. + +A distinction has been made between IMT-2000 basic capabilities (e.g. basic calls and basic mobility management) and IMT-2000 IN capabilities (IN capabilities triggered by e.g. basic call and mobility events). + +## 5.2 The complete functional models + +The complete functional models for IMT-2000, one for Alternative 1 (i.e. integrated call control and connection control FEs) and one for Alternative 2 (i.e. separated call control and connection control FEs), are shown in Figures 5-1a and 5-1b. + +The distribution of functions to the Functional Entities is described in the following subclauses. + +The radio access control related FEs and the communication and service control related FEs are described in different subclauses. + +![Functional model diagram for IMT-2000 showing UIM, MT, RAN, and CN subsystems and their interconnections.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +The diagram illustrates the functional model for IMT-2000, organized into four vertical columns representing different subsystems: UIM, MT, RAN, and CN. A horizontal dashed line separates the top section, labeled 'Communication and Service Control', from the bottom section, labeled 'Radio Access Control'. + +- UIM (User Interface Module):** Contains the UIMF (User Interface Function) node. +- MT (Mobile Terminal):** Contains nodes MGPF, PSCAF, CCAF', MCF, RACAF, and MRTR. +- RAN (Radio Access Network):** Contains nodes GPF, SNCF, SIBF, RACF, ARF, and RFTR. +- CN (Core Network):** Contains nodes GPCF, PSGCF, PSCF, LMF, AMF, SDF, SCF, SRF, CCF'/SSF, and SACF. + +Key connections include: + +- UIMF connects to MGPF and MCF. +- MGPF connects to GPCF and PSCAF. +- PSCAF connects to PSCF and GPF. +- CCAF' connects to CCF'/SSF. +- MCF connects to RACAF and GPF. +- RACAF connects to MRTR and RACF. +- MRTR connects to RFTR. +- GPCF connects to PSGCF and LMF. +- PSGCF connects to PSCF. +- PSCF connects to LMF and SACF. +- LMF connects to AMF, SCF, and SACF. +- AMF connects to SDF. +- SCF connects to SRF and CCF'/SSF. +- SACF connects to CCF'/SSF, RACF, and GPF. +- RACF connects to SNCF, SIBF, ARF, and RFTR. +- ARF is shown twice, once in RAN and once in CN, connected to RACF and SACF respectively. + +T1199440-98 + +Functional model diagram for IMT-2000 showing UIM, MT, RAN, and CN subsystems and their interconnections. + +NOTE 1 – There are two alternate ways of supporting triggers for mobility management (i.e. location management or user authentication) related IN services. The triggers can be placed either in the LMF and AMF or in the SACF. + +NOTE 2 – The ARF FE has to be mapped to both the RAN and the CN subsystems, since a branch of a BS approach link can be set up via the RAN or via the CN. + +**Figure 5-1a/Q.1711 – The IMT-2000 functional model +Alternative 1: Integrated call control and connection control FEs** + +![Figure 5-1b/Q.1711 – The IMT-2000 functional model. This diagram illustrates the functional architecture of IMT-2000, divided into four vertical domains: UIM, MT, RAN, and CN. A horizontal dashed line separates the 'Communication and Service Control' layer (top) from the 'Radio Access Control' layer (bottom). In the UIM domain, UIMF connects to MGPF, PSCAF, CCAF', CnCAF, and MCF. MGPF connects to GPCF in the CN domain. PSCAF connects to PSCF in the CN domain. CCAF' connects to CnCAF in the MT domain. CnCAF connects to CnCF in the RAN domain. MCF connects to RACAF in the MT domain. In the MT domain, RACAF connects to MRTR and RACF. MRTR connects to RFTR in the RAN domain. RACF connects to GPF, SNCF, SIBF, and ARF. GPF connects to SACF in the CN domain. SNCF connects to SACF. SIBF connects to SACF. ARF connects to SACF. In the CN domain, GPCF connects to PSGCF and LMF. PSGCF connects to LMF. LMF connects to AMF, SCF, and SACF. AMF connects to SDF. SCF connects to SRF and CCF/SSF. CCF/SSF connects to CnCF. SACF connects to CnCF. The diagram is labeled T1199450-98.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Figure 5-1b/Q.1711 – The IMT-2000 functional model. This diagram illustrates the functional architecture of IMT-2000, divided into four vertical domains: UIM, MT, RAN, and CN. A horizontal dashed line separates the 'Communication and Service Control' layer (top) from the 'Radio Access Control' layer (bottom). In the UIM domain, UIMF connects to MGPF, PSCAF, CCAF', CnCAF, and MCF. MGPF connects to GPCF in the CN domain. PSCAF connects to PSCF in the CN domain. CCAF' connects to CnCAF in the MT domain. CnCAF connects to CnCF in the RAN domain. MCF connects to RACAF in the MT domain. In the MT domain, RACAF connects to MRTR and RACF. MRTR connects to RFTR in the RAN domain. RACF connects to GPF, SNCF, SIBF, and ARF. GPF connects to SACF in the CN domain. SNCF connects to SACF. SIBF connects to SACF. ARF connects to SACF. In the CN domain, GPCF connects to PSGCF and LMF. PSGCF connects to LMF. LMF connects to AMF, SCF, and SACF. AMF connects to SDF. SCF connects to SRF and CCF/SSF. CCF/SSF connects to CnCF. SACF connects to CnCF. The diagram is labeled T1199450-98. + +NOTE 1 – There are two alternate ways of supporting triggers for mobility management (i.e. location management or user authentication) related IN services. The triggers can be placed either in the LMF and AMF or in the SACF. + +NOTE 2 – The ARF FE has to be mapped to both the RAN and the CN subsystems, since a branch of a BS approach link can be set up via the RAN or via the CN. + +**Figure 5-1b/Q.1711 – The IMT-2000 functional model +Alternative 2: Separated call control and connection control FEs** + +## 5.3 Radio access control related Functional Entities + +The radio access control related FEs are in charge of controlling access links. This also includes the management and control of radio resources (e.g. selection and reservation of radio resources, radio channel and radio environment supervision, handover initiation, radio channel activation, handover execution, etc.). These FEs also handle some functions related to geographic position finding. These FEs represent the functionality performed by the radio access subsystem. + +The radio access control related FEs and their functional relationships are shown in Figure 5-2. + +![Diagram of radio resource control functional entities across MT, RAN, and CN subsystems.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +The diagram illustrates the functional entities within the MT (Mobile Terminal), RAN (Radio Access Network), and CN (Core Network) subsystems, separated by vertical lines representing interfaces. + +- MT Subsystem:** Contains RACAF and MRTR. RACAF is connected to MRTR and to the RAN interface. +- RAN Subsystem:** Contains GPF, SIBF, SNCF, RACF, ARF, and RFTR. + - GPF, SIBF, and SNCF are connected to RACF. + - RACF is connected to ARF and RFTR. + - RFTR is connected to the MT interface and the CN interface. +- CN Subsystem:** Contains ARF. ARF is connected to the RAN interface. + +T1199460-98 + +Diagram of radio resource control functional entities across MT, RAN, and CN subsystems. + +NOTE – The ARF FE has to be mapped to both the RAN and the CN subsystems, since a branch of a BS approach link can be set up via the RAN or via the CN. + +**Figure 5-2/Q.1711 – The radio resource control Functional Entities** + +The functions are distributed as follows: + +**RACF – Radio Access Control Function:** This FE handles the overall control of the association and access link(s) between a mobile terminal and the network. In general it includes functions to: + +- a) interact with the SACF to set up and release access links; +- b) interact with the ARF and/or another RACF for the setup and release of a branch of BS approach link and access radio link; +- c) interact with the RFTR to set up, maintain, modify, and release a branch of a BS approach link and associated access radio link; +- d) interact with the RACAF for the allocation and reallocation of physical (radio) channel(s) for a branch of an access radio link; +- e) interact with the RFTR and SACF for the establishment of a signalling connection; +- f) perform handover decision (quality of service assessment based on radio channel quality estimations, including surrounding cells); +- g) perform handover decision (initiated by the network side to reallocate the resources); +- h) execute handover; +- i) complete handover; +- j) control the interconnection of branches of a BS approach link and the macro-diversity execution in handover when the macro-diversity point is located in the RACF; +- k) execute terminal paging according to the request from the SACF or PSCF (for packet data); +- l) determine and keep track of the position of a mobile terminal based on radio-environment-specific parameters (e.g. identification of the cell used by a terminal to access the network); +- m) map radio-environment-specific location information (such as cell ID) onto radio-environment-independent location information; +- n) provide terminal location information to the SACF and PSCF with the required accuracy; +- o) select and reserve radio resources for the execution of handover, initiated by the RACF itself or on request from the SACF; +- p) perform RF power control; + +- q) set service acceptability information (this function has to be included in either the RACF or the RFTR); +- r) judge service acceptability (this function has to be included in either the RACF or the RFTR); +- s) interact with the RFTR to coordinate the measurements necessary to determine the geographic position of a mobile terminal, or modify the transmitted RF signals to enable the mobile terminal to perform such measurements; +- t) forward the result of the geographic position measurements to the GPF; +- u) interact with the PSCF to initiate and control the dynamic allocation of radio resources for the transport of data packets across the radio interface; +- v) interact with the SACF or PSCF for ciphering execution control when ciphering is performed by radio access control related FEs; +- w) interact with the ARF to provide the capability to route to a BS approach link; +- x) interact with the SNCF to dynamically control the configuration of radio network resources (for satellite networks); +- y) schedule delivery of messages received from the SACF; +- z) perform delivery of messages (this function may be in either the SIBF or the RACF); +- aa) interact with the SACF for managing selection of global random challenge values when the global challenge scheme is used; +- bb) interact with the SIBF to provide global random challenge values for broadcast when the global challenge scheme is used. + +**RACAF – Radio Access Control Agent Function:** This FE handles the mobile side of the association and access link control between the mobile terminal and the network. In general it includes the following functions to: + +- a) interact with the RACF for the allocation and reallocation of physical radio channel(s) for a branch of an access radio link; +- b) interact with the MRTR, MCF, and (for Alternative 2) the CnCAF to set up, maintain, modify, and release an access radio link; +- c) perform handover decision (if mobile directed handover); +- d) detect paging; +- e) interact with the MCF or PSCAF (for packet data) for indication of paging; +- f) perform system access information monitoring and analysis based on information broadcast by the SIBF; +- g) trigger (or initiate) handover; +- h) perform RF power control; +- i) judge service acceptability; +- j) interact with the MCF for ciphering execution control when ciphering is performed by radio access control related FEs; +- k) control measurements of the quality of radio channels in neighbouring cells; +- l) interact with the MRTR to perform the measurements necessary to determine the geographic position of a mobile terminal, or modify the transmitted RF signals to enable the network to perform such measurements; +- m) forward the result of the geographic position measurements to the MGPF; + +- n) dynamically allocate radio resources for the transport of data packets across the radio interface; +- o) Interact with the MRTR for cell selection in idle mode. + +**RFTR – Radio Frequency Transmission and Reception:** This FE controls the interconnection and adaptation of the access radio link corresponding to the BS approach link. This includes radio channel error protection coding and decoding. It includes functions to: + +- a) interact with the RACF to set up, maintain, modify and release a branch of a BS approach link and associated branch of an access radio link; +- b) maintain the state of an access radio link between the mobile terminal and the network; +- c) cipher and decipher the radio channel when ciphering is performed by radio access control related FEs; +- d) estimate the quality of radio channels; +- e) set the RF power; +- f) interact with the MRTR and RACF for the establishment of a signalling connection (i.e. random access detection and handling); +- g) maintain the state of a signalling connection; +- h) control the interconnection of branches of an access radio link and the macro-diversity in handover (when the macro-diversity point is located in the RFTR); +- i) set service acceptability information (this function has to be included in either the RFTR or the RACF); +- j) judge service acceptability (this function has to be included in either the RFTR or the RACF); +- k) perform the measurements necessary to determine the geographic position of a mobile terminal, or modify the transmitted RF signals to enable the mobile terminal to perform such measurements; +- l) forward the results of the measurements necessary to determine the geographic position of a mobile terminal to the RACF. + +**MRTR – Mobile Radio Transmission and Reception:** This FE controls the interconnection and adaptation of the access radio link to the rest of the mobile terminal. This includes radio channel error protection coding and decoding. It includes functions to: + +- a) interact with the RACAF to set up, maintain, modify and release a branch of an access radio link; +- b) maintain the state of an access radio link as perceived by this FE; +- c) cipher and decipher the radio channel when ciphering is performed by radio access control related FEs; +- d) estimate the quality of radio channels in the active cell and in neighbouring cells (if mobile directed or mobile assisted handover is used); +- e) set the RF power; +- f) interact with the RACAF for cell selection in idle mode; +- g) interact with the RACAF for the reception of random access initiation request, and for the indication of the completion of the procedure; +- h) interact with the RFTR for random access initiation; +- i) maintain the state of a signalling connection; + +- j) perform the measurements necessary to determine the geographic position of a mobile terminal, or modify the transmitted RF signals to enable the network to perform such measurements; +- k) forward the results of the measurements necessary to determine the geographic position of a mobile terminal to the RACAF. + +**ARF – Access link Relay Function:** This FE handles the overall control for the transit of a branch of the BS approach link between two instances of the RACF. It includes functions to: + +- a) interact with the RACF or another ARF to set up and release a branch of a BS approach link; +- b) control the transmission resources to provide the requested bearer capability; +- c) interact with the RACF to obtain routing instructions for a branch of a BS approach link; +- d) maintain the state of a branch of a BS approach link. + +**SIBF – System access Information Broadcast Function:** This FE handles the overall control of system access information broadcasting. The information to be broadcast may be made available to the FE via an operation and maintenance function. It includes functions to: + +- a) perform system access information broadcasting; +- b) perform service access permission information broadcasting; +- c) perform delivery of messages (this function may be in either the SIBF or the RACF); +- d) broadcast to the RACAF the information necessary to perform system access information monitoring and analysis; +- e) interact with the RACF for broadcasting the global random challenge value when the global challenge scheme is used. + +**SNCF – Satellite Network Control Function:** This FE dynamically controls the configuration of radio network resources, in response to demands for connections to and from mobile terminals. In particular, in satellite networks, optimal use of scarce communication resources requires this dynamic behaviour. In other kinds of networks this FE may not be required. The SNCF includes functions to: + +- a) interact with the RACF and SACF to establish and release associations between feeder links (to and from the Core Network) and radio channels; +- b) interact with the RACF to manage the way in which the radio channels are targeted, for example to satellite spot beams; +- c) establish and release associations between various bearer channels at the satellite, for example in support of direct terminal-terminal calls, which do not transit the Core Network. + +**GPF – Geographic Position Function:** This FE handles the tasks associated with geographic positioning in the radio access side. It includes functions to: + +- a) receive requests from the GPCF or MGPF to perform the steps needed to determine the geographic position of mobile terminals; +- b) interact with the RACF to perform the necessary RF measurements or to modify the transmitted RF signals to enable the mobile terminal to perform such measurements; +- c) interact with the MGPF to synchronize with the mobile terminal to perform necessary RF measurements or modify transmitted RF signals to enable the GPF to perform such measurements; +- d) receive relevant information (measurements, position data, timestamps, etc.) from the RACF or from the MGPF and perform some of the necessary computations to determine the geographic coordinates of the mobile terminal; + +- e) send the result to the requesting party (the GPCF or MGPF). + +## 5.4 Communication and service control related Functional Entities + +The communication and service control related functional entities are in charge of the overall access, service, call, and connection control. Two functional models are shown to reflect the option of having the call and connection controls integrated or separated. These FEs represent the functionality performed by the UIM, Mobile Terminal and Core Network subsystems. + +The Functional Entities and their functional interrelations are shown in Figures 5-3a and 5-3b. + +The figures show the interconnections between the IMT-2000 specific FEs and the FEs that are defined for IN. Although not shown in the figure, it is assumed that Service Management functionality are included in the same way as for IN (SMF, SMAF, SCEF Functional Entities). + +![Diagram showing functional entities (UIMF, MGPF, PSCAF, CCAF, MCF, GPCF, PSGCF, PSCF, LMF, AMF, SDF, SCF, SRF, CCF/SSF, SACF) across four domains: UIM, MT, RAN, and CN. The diagram illustrates the interconnections between these entities, with UIMF connected to MGPF, PSCAF, CCAF, and MCF in the MT domain, and SACF connected to GPCF, PSGCF, PSCF, LMF, AMF, SDF, SCF, SRF, and CCF/SSF in the CN domain.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +The diagram illustrates the functional entities and their interconnections across four domains: UIM, MT, RAN, and CN. The entities are represented by ovals, and the domains are represented by vertical lines. + +- UIM (User Interface Module):** Contains the UIMF (User Interface Management Function) entity. +- MT (Mobile Terminal):** Contains the MGPF (Mobile Gateway Function), PSCAF (Packet Switched Call Admission Function), CCAF (Circuit Switched Call Admission Function), and MCF (Mobile Communication Function) entities. +- RAN (Radio Access Network):** This domain is shown as a vertical line separating the MT and CN domains. +- CN (Core Network):** Contains the GPCF (Gateway Packet Control Function), PSGCF (Packet Switched Gateway Control Function), PSCF (Packet Switched Control Function), LMF (Location Management Function), AMF (Access Management Function), SDF (Service Data Function), SCF (Service Control Function), SRF (Service Resource Function), CCF/SSF (Circuit Switched Control/Service Switching Function), and SACF (Service Access Function) entities. + +Interconnections are shown as horizontal lines between entities in adjacent domains and as internal connections within the CN domain. + +Diagram showing functional entities (UIMF, MGPF, PSCAF, CCAF, MCF, GPCF, PSGCF, PSCF, LMF, AMF, SDF, SCF, SRF, CCF/SSF, SACF) across four domains: UIM, MT, RAN, and CN. The diagram illustrates the interconnections between these entities, with UIMF connected to MGPF, PSCAF, CCAF, and MCF in the MT domain, and SACF connected to GPCF, PSGCF, PSCF, LMF, AMF, SDF, SCF, SRF, and CCF/SSF in the CN domain. + +T1199470-98 + +NOTE – There are two alternate ways of supporting triggers for mobility management (i.e. location management or user authentication) related IN services. The triggers can be placed either in the LMF and the AMF or in the SACF. + +**Figure 5-3a/Q.1711 – Communication and service control related Functional Entities +Alternative 1: integrated call control and connection control FEs** + +![Diagram of communication and service control related functional entities across four domains: UIM, MT, RAN, and CN. The diagram shows various functional entities (FEs) and their interconnections. In the UIM domain, UIMF is connected to MGPF, PSCAF, CCAF', CnCAF, and MCF. In the MT domain, MGPF, PSCAF, CCAF', CnCAF, and MCF are shown. In the RAN domain, CnCF is shown. In the CN domain, GPCF, PSGCF, PSCF, AMF, LMF, SDF, SCF, SRF, CCF'/SSF, and CnCF are shown. Connections include horizontal lines between UIM and MT, MT and RAN, and RAN and CN. Vertical lines connect UIMF to MT entities and CN entities. Horizontal lines also connect MT entities to CN entities (e.g., MGPF to GPCF, PSCAF to PSCF, CCAF' to CCF'/SSF, CnCAF to CnCF, MCF to SACF). SACF is connected to LMF, SCF, and CnCF. SCF is connected to AMF, SDF, SRF, CCF'/SSF, and CnCF. AMF is connected to GPCF, PSGCF, and LMF. LMF is connected to GPCF, PSGCF, PSCF, AMF, SCF, and SACF.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +Diagram of communication and service control related functional entities across four domains: UIM, MT, RAN, and CN. The diagram shows various functional entities (FEs) and their interconnections. In the UIM domain, UIMF is connected to MGPF, PSCAF, CCAF', CnCAF, and MCF. In the MT domain, MGPF, PSCAF, CCAF', CnCAF, and MCF are shown. In the RAN domain, CnCF is shown. In the CN domain, GPCF, PSGCF, PSCF, AMF, LMF, SDF, SCF, SRF, CCF'/SSF, and CnCF are shown. Connections include horizontal lines between UIM and MT, MT and RAN, and RAN and CN. Vertical lines connect UIMF to MT entities and CN entities. Horizontal lines also connect MT entities to CN entities (e.g., MGPF to GPCF, PSCAF to PSCF, CCAF' to CCF'/SSF, CnCAF to CnCF, MCF to SACF). SACF is connected to LMF, SCF, and CnCF. SCF is connected to AMF, SDF, SRF, CCF'/SSF, and CnCF. AMF is connected to GPCF, PSGCF, and LMF. LMF is connected to GPCF, PSGCF, PSCF, AMF, SCF, and SACF. + +NOTE – There are two alternate ways of supporting triggers for mobility management (i.e. location management or user authentication) related IN services. The triggers can be placed either in the LMF and AMF or in the SACF. + +**Figure 5-3b/Q.1711 – Communication and service control related Functional Entities +Alternative 2: separated call control and connection control FEs** + +The distribution of functions onto functional entities is given in the following subclauses. + +### 5.4.1 Functional Entities on the network side of the radio interface + +This subclause describes the communication and service control related FEs in the Core Network subsystem. + +**SDF – Service Data Function:** This FE is defined in Recommendation Q.1224 (IN CS-2) [7], however, it has been enhanced for mobile communications. It handles storage and access to service and network related data and provides consistency checks on data. It hides from the SCF the real data implementation and provides a logical data view to the SCF. It includes functions to: + +- store service data, (e.g. service profile, multimedia attributes); +- check data consistency; +- manage application data (e.g. create, administer, provision, etc.); +- generate and manage user service related data; +- interact with other SDFs to exchange service data. + +**SCF – Service Control Function:** This FE contains the overall IN service control functionality in the IMT-2000. Service logic can be triggered by call processing, mobility management, or non-call associated events. The SCF interacts with other FEs to access additional logic or to obtain information (service, user or network data) required to process a service logic instance. It includes functions to: + +- interact with either the AMF and LMF or the SACF to provide mobility management (e.g. location management and user authentication) related IN services. This capability does not include the triggering of IN services from the authentication data (e.g. triplet) generation process; +- interact with the SACF to provide call unrelated IN services; +- interact with the CCF'/SSF to provide call related IN services; +- interact with the SRF to provide specialized resources for IN services; + +- e) interact with the SDF to manage and update service data; +- f) interact with other SCFs for secured data acquisition and manipulation, distributed service control and unsolicited service notifications, if necessary; +- g) interact with the user for session control and access control for connection's services (including packet services), using call unrelated transparent user to service interactive operations; +- h) interact with proactive applications within terminal- or user- agents; +- i) process application data (e.g. initiates data download, SMS, ADDS); +- j) interact with the LMF to obtain terminal and user information (e.g. location information, subscriber status information); +- k) interact with the UIMF for service data/logic transfer and service profile modification, utilising the relationship with the SACF or PSCF. + +**SRF – Specialized Resource Function:** This FE is defined in IN Capability Set documents. It provides the specialized resources required for the execution of IN provided services (e.g. digit receivers, announcements, conference bridges), mobile multimedia services, application data delivery services, and packet data transfer services. It includes functions to: + +- a) interact with the SCF, CCF'/SSF, and the CnCF (Alternative 2) to provide specialized resources for IN services; +- b) provide the logic and processing capability to receive/send and convert information or application data received/sent from users; +- c) provide functionality to terminate and manage bearer connections to the specialized resources. + +**SMF – Service Management Function:** This FE is defined in Recommendation Q.1224 (IN CS-2) [7], however, it has been enhanced for mobile communications. It consists of a number of IN SMF functions. These functions can be grouped into the following five categories: + +- 1) Service Deployment Functions; +- 2) Service Provisioning Functions; +- 3) Service Operation Control Functions; +- 4) Billing Functions; +- 5) Service Monitoring Functions. + +(see Recommendation Q.1224 for further details). + +**SSF – Service Switching Function:** This FE is defined in Recommendation Q.1224 (IN CS-2) [7], however, it has been enhanced for mobile communications. The SSF is associated with the CCF'. It provides the set of functions required for the interaction between the CCF' and SCF. It includes functions to: + +- a) interact with the CCF' and SCF to provide IN services; +- b) manage the signalling between the CCF' and SCF; +- c) modify functions in the CCF' as required to process requests for IN provided service usage under the control of the SCF. + +The connection control function can be either contained in the call control Functional Entity or a separate Functional Entity. The CCF' functionality is mostly the same in either case, however, the differences are noted below the CCF' FE description. + +**CCF' – Call Control Function (enhanced):** The definition of this FE is based on the Call Control Function defined in Recommendation Q.1224 (IN CS-2) [7], however, it has been enhanced for mobile communications. It provides call/connection processing control. It includes functions to: + +- a) interact with the CCAF' or other CCF's/CCFs to establish, maintain and release call instances; +- b) establish and manage the relationship between the CCAF' Functional Entities involved in a call and/or connection instance (e.g. supervises the overall perspective of the call and/or connection instance); +- c) provide trigger mechanisms for mobile originated calls and mobile terminated calls to access IN functionality (e.g. passes events to the SSF); +- d) interact with the SACF for the setup and release of an access link; +- e) interact with the SRF in support of IN services; +- f) interact with the LMF to receive routing and profile information for mobile calls. + +#### *Alternative 1: Integrated Call Control and Connection Control Functions* + +When call and connection control are integrated, the CCF' includes the following additional function to: + +- g1) control the bearer connection elements in the network in order to provide the bearer capabilities requested, including the following functionality: + - establishment, maintenance and release of bearer connections in the network, including bearers to the SRF for IN services, + - cooperation with the peer CCF' in order to establish, maintain and release bearer control associations. + +#### *Alternative 2: Separated Call Control and Connection Control Functions* + +When call and connection control are separated, the CCF' includes the following additional function to: + +- g2) interact with the CnCF to establish, modify and release a connection of a call. + +**CnCF – Connection Control Function:** This FE provides connection processing control. It includes functions to: + +- a) interact with the CCF', CnCAF, or other CnCFs to establish, maintain, modify and release connection instances; +- b) establish and manage the relationship between the CnCAF Functional Entities involved in a connection (e.g. supervises the overall perspective of the connection instance); +- c) controls the bearers in the network in order to provide the bearer capabilities requested, including the following functionality: + - establishment, maintenance and release of bearers in the network, including bearers to the SRF for IN services; + - cooperation with the peer CnCF in order to establish, maintain and release bearer control associations. + +For simplification purposes, the LMF is shown containing data and mobility management functions and the AMF is shown containing data and authentication functions. However, the functions may be identified separately and different relationships may be used for interconnections purposes. + +**LMF – Location Management Function:** This FE contains the basic terminal mobility logic. It supports location management, mobility management, activation status management, and identity management. The LMF interacts with other FEs to access additional logic or share information + +(e.g. user or network data). It also handles storage and access to subscriber mobility data. It includes functions to: + +- a) interact with the CCF/SSF, SACF, and other LMF FEs to provide routing information for the establishment of calls; + - b) interact with the CCF/SSF to provide profile information including service capability (e.g. protocol, bearer) information; + - c) interact with the AMF which provides user authentication processing; + - d) interact with the SACF to send authentication related requests from the AMF; + - e) interact with the SACF for basic mobility management (e.g. location and MT status management, identity management); + - f) interact with the SCF to provide location management related IN services (this function can be provided by either the LMF or the SACF); + - g) interact with the SACF to provide the paging strategy; + - h) interact with the SCF to provide location and subscriber status information; + - i) perform location and MT status management (e.g. attach, detach); + - j) perform identity management; + - k) manage, update, and transfer data (e.g. subscriber profile data, trigger profile data); + - l) perform user verification (e.g. PIN verification for access to subscriber data); + - m) identify radio-environment-independent terminal location information (e.g. in terms of a geographic area); + - n) modify the location management procedures as required to process requests for IN provided usage under the control of the SCF (this function can be provided by either the LMF or the SACF); + - o) store subscriber identity, subscriber profile, and mobility related data, e.g. + - location information, + - active/inactive status, + - subscriber identity data, + - supplementary service profile (e.g. call barring, call waiting), + - trigger profile list; + - p) manage temporary routing numbers for use by roamers (this function has to be in either the LMF or the SACF); + - q) manage, update, and transfer relevant packet data services information (e.g. packet data service profile); +- NOTE – This is primarily associated with the Home LMF. +- r) check data consistency; + - s) interact with another LMF to manage the subscriber information; + - t) interact with another LMF to ensure subscriber information integrity (e.g. fault restoration); + - u) interact with another LMF or the SACF to control the supplementary services (SS) (e.g. activate/deactivate, update/retrieve/erase the SS information, register a subscriber provided password, handle the subscriber SS data); + +- v) interact with a message centre (e.g. the SCF1) to provide the messaging services (e.g. SMS, ADDS) based on MT availability; +- w) interact with the SACF to deliver messages; +- x) interact with the PSCF for accessing and updating subscriber-related data and updating packet service and routing information; +- y) interact with the PSGCF for updates of packet service and routing information (this function can be provided by either the LMF or the PSCF); +- z) interact with the GPCF to indicate the general area where RF control messages may be sent to mobile terminals. + +**AMF – Authentication Management Function:** This FE handles storage and access to authentication data. It also provides the authentication function and confidentiality control. It includes functions to: + +- a) store authentication data (e.g. triplets, user authentication keys, security related parameters); +- b) generate authentication information (e.g. generation of triplets, unique authentication challenge); +- c) check the validity of received authentication data; +- d) check data consistency; +- e) perform user authentication; +- f) perform confidentiality control; +- g) manage, update, and share authentication parameters; +- h) perform confidentiality control, user authentication, and parameter update for packet data services (this capability can be in either the LMF or the PSCF); +- i) interact with the SCF to provide user authentication related IN services. This capability does not include the triggering of IN services from the authentication data (e.g. triplet) generation processes (this capability can be provided by either the AMF or the SACF); +- j) modify the user authentication procedures (excluding the generation of authentication data e.g. triplets) as required to process requests for IN provided usage under the control of the SCF (this capability can be provided by either the AMF or the SACF); +- k) interact with the UIMF for user authentication purposes (excluding the generation of authentication data e.g. triplets), utilising the relationship with the LMF. + +**SACF – Service Access Control Function:** This FE provides both call-related and call-unrelated processing and control (e.g. in relation to mobility management). It includes functions to: + +- a) interact with the MCF for the establishment and release of both call-related and call-unrelated association between an IMT-2000 terminal/user and the network; +- b) interact with the LMF to provide routing information for the establishment of calls and basic mobility management functionality (e.g. location and MT status management, identity management); +- c) interact with the SCF to provide mobility management (e.g. location management and user authentication) related IN services. This capability does not include the triggering of IN services from the authentication data (e.g. triplet) generation processes (this capability can be provided by either the AMF and LMF or the SACF); +- d) interact with the SCF to provide call-unrelated IN services; + +--- + +1 This message centre does not have to be mapped to an IN platform. + +- e) interact with the RACF to identify radio-environment-independent terminal location information across one or more RACFs; +- f) interact with the CCF'/SSF and RACF for the setup and release of an access link (the SACF may simply transfer requests between the CCF'/SSF and RACF); +- g) interact with the RACF for the setup and release of a branch of a BS approach link when the macro-diversity point is located in the SACF; +- h) control the interconnection of branches of an access link and the macro-diversity execution in handover for cases when the macro-diversity point is located in the SACF; +- i) interact with the MCF to detect and handle paging response; +- j) interact with RACFs to request paging execution; +- k) interact with the RACF for ciphering execution control (including ciphering information delivering and triggering); +- l) interact with the LMF to provide the paging strategy; +- m) interact with the RACF to support location-based services dependent on location information across RACFs; +- n) manage temporary routing numbers for use by roamers (this function must be in either the LMF or the SACF); +- o) interact with the LMF to control supplementary services (SS) (e.g. activate/deactivate, update/retrieve/erase the SS information, register a subscriber provided password, handle the subscriber SS data or to invoke the SS); +- p) modify the location management procedures and user authentication procedures as required to process requests for IN-provided usage under the control of the SCF (this capability can be provided by either the AMF and LMF or the SACF); +- q) interact with the RACF and LMF for delivery of messages; +- r) interact with the RACF and LMF for managing the global random challenge activities when global challenge scheme is used; +- s) interact with the MCF and LMF for managing unique authentication challenge activities when unique challenge scheme is used. + +**GPCF – Geographic Position Control Function:** This FE provides the overall control for the geographic position finding function on the network side. It includes functionality to: + +- a) receive requests from the network or from its peer entity on the mobile side (i.e. the MGPF) to determine the geographic position of a mobile terminal; +- b) establish, maintain and release a service instance for a geographic positioning request; +- c) interact with the LMF to identify the general area where RF control messages may be sent to mobile terminals; +- d) interact with the GPF to instruct it to perform the necessary RF measurements or to modify the transmitted RF signals to enable the mobile terminal to perform such measurements; +- e) interact with the MGPF to request that the mobile terminal performs necessary RF measurements or that it modifies its transmitted RF signals to enable the GPF to perform such measurements; +- f) receive relevant information (measurements, position data, timestamps, partial computations, etc.) from the GPF or from the MGPF on the mobile side and perform the necessary final computation to determine the geographic coordinates of the Mobile Terminal; +- g) send the results to the requesting party. + +### 5.4.2 Functional Entities on the mobile side of the radio interface + +This subclause describes the communication and service control related FEs in the UIM and Mobile Terminal subsystems. + +**MCF – Mobile Control Function:** This FE provides the overall service access control logic and processing at the mobile side of the radio interface. Specifically, it interacts with the network for mobility management. It includes functions to: + +- a) interact with the SACF for the establishment and release of the association between a mobile terminal and the network; +- b) interact with the SACF to initiate location and MT status management; +- c) detect user's need to interact with call-unrelated service features for personal mobility features; +- d) relay indications relating to service access to the user/terminal functional entities as required; +- e) interact with the RACAF to setup, maintain, modify, and release a signalling connection; +- f) interact with the CCAF' (Alternative 1) and the CnCAF (Alternative 2) to setup, maintain, modify, and release an access channel; +- g) interact with the UIMF to retrieve user identification information, location management related information (e.g. location area identity), security and privacy related information (e.g. temporary mobile user identity); +- h) interact with the UIMF to exchange application information with the applications that are allocated within the UIMF, MCF, or an external device; +- i) interact with the SACF and RACAF to handle paging; +- j) interact with the SCF (utilising the relationship with the SACF) for service control purposes, for example to download and store service logic and application data (this can also be done by the UIMF); +- k) interact with the SACF for managing unique authentication challenge activities when unique challenge scheme is used; +- l) interact with the RACAF for ciphering execution control when ciphering is performed by radio access control related FEs; +- m) interact with the UIMF to perform serving system selection; +- n) maintain service capability (e.g. protocol, bearer) information for the mobile terminal. + +**UIMF – User Identification Management Function:** This FE provides the means to identify both the IMT-2000 user and the mobile terminal to the network and/or to the service provider, and contains processing capability for authentication and service handling in the UIM. It includes functions to: + +- a) store IMT-2000 user-related information such as IMT-2000 user identification information both to identify the IMT-2000 user and to address the mobile terminal, location management-related information and security and privacy related information; +- b) interact with the MCF to provide IMT-2000 user identification information, location management-related information (e.g. location area identity), security and privacy related information (e.g. temporary mobile user identity); +- c) interact with the MCF to exchange application information with the applications that are allocated within the MCF, UIMF, or an external device; +- d) interact with the MCF to provide serving system selection information based on e.g. location area identity, service availability, and service preferences; + +- e) interact with the AMF (utilising the relationship with the MCF or PSCAF) for IMT-2000 user authentication and ciphering key generation (e.g. calculation of authentication response and generation of ciphering key); +- f) perform and control authentication of the network to the user in case of mutual authentication, and update authentication parameters in the UIM in interaction with the AMF, utilising the relationship with the MCF or PSCAF; +- g) interact with the SCF to exchange application information, utilising the relationship with the MCF or PSCAF, for example to support proactive applications; +- h) store, process and/or work with the Man-Machine Interface (MMI) functionality in the MT to display application data or other types of data downloaded from the network or loaded into the UIMF by other means; +- i) execute service logic required to handle service attempts in the UIM, both related to a call and not related to a call. + +The connection control agent function may be either contained in the call control agent Functional Entity or a separate Functional Entity. The CCAF' functionality is mostly the same in either case, however, the differences are noted below the CCAF' FE description. + +**CCAF' – Call Control Agent Function (enhanced):** The definition of this FE is based on the Call Control Agent Function defined in Recommendation Q.1224 (IN CS-2) [7], however, it has been enhanced for mobile communications. It provides service access for users and may also provide integrated call/connection control. It is the interface between user and network call control functions. It includes functions to: + +- a) interact with the CCF' and MCF to establish, maintain, or release a call or other service instance; +- b) provide for user access, interacting with the user to establish, maintain, modify and release a call or other service instance; +- c) relay information between the user and the CCF'; +- d) maintain call/service state information. + +#### *Alternative 1: Integrated Call Control and Connection Control Functions* + +When call and connection control agent functions are integrated, the CCAF' includes the following additional function: + +- e1) control bearer connection elements with the CCF' to provide the bearer capabilities requested, including the functionality for the establishment, maintenance and release of bearer connections and bearer control associations. + +#### *Alternative 2: Separated Call Control and Connection Control Functions* + +When call and connection control agent functions are separated, the CCAF' includes the following additional function: + +- e2) Interact with CnCAF to setup, maintain, modify, and release connections. + +**CnCAF – Connection Control Agent Function:** This FE provides connection control functions for users. It is the interface between the Call Control Agent Function (CCAF') and the Radio Access Control Agent function (RACAF). It includes functions to: + +- a) interact with the CCAF', MCF, and CnCF to establish, maintain, modify and release connections; +- b) relay information between the CnCF and CCAF'; +- c) maintain connection state information; + +- d) interact with the RACAF or MCF to setup, maintain, modify, or release a connection. + +**MGPF – Mobile Geographic Position Function:** This FE provides the overall control for the geographic position finding function on the mobile terminal side. It includes functionality to: + +- a) provide for user access, interacting with the user to establish, maintain, modify and release a service instance; +- b) access the service providing capabilities of the GPCF, using service requests for the establishment, maintenance and release of a service instance; +- c) receive requests from the mobile terminal user or from its peer entity on the network side (i.e. the GPCF) to initiate an action for determining the geographic position of the mobile terminal; +- d) if an independent way of assessing the mobile terminal's position is available (e.g. a GPS receiver), determine the position based on the provided input and make the result available to the requesting party; +- e) interact with the RACAF to perform the necessary RF measurements or to modify the transmitted RF signals to enable the network side to perform such measurements; +- f) interact with the GPF to request that the network side performs necessary RF measurements or that it modifies its transmitted RF signals to enable the mobile terminal to perform such measurements; +- g) interact with the UIMF in support of user identification, authentication and privacy; +- h) receive relevant information (measurements, position data, timestamps, etc.) from the radio receiver on the mobile side or from the GPF on the network side and, either forward the data to the GPCF, or, if possible, perform the necessary computations to determine the geographic coordinates of the mobile terminal; +- i) present the results to the mobile terminal user or send them to the GPCF. + +### 5.4.3 Packet data services control related Functional Entities + +This subclause refers to the Functional Entities needed to support the context-based routing for packet data services. The functionality of the packet data services control is in charge of the overall context access and service control. The functions are grouped into Functional Entities (FE). The Functional Entities and their functional interrelations are shown in Figure 5-4. + +![Diagram of packet data service-related Functional Entities (FEs) across four domains: UIM, MT, RAN, and CN. UIM contains UIMF*. MT contains PSCAF. RAN is empty. CN contains PSGCF, PSCF, AMF*, LMF*, and SCF*. Lines connect UIMF* to PSCAF, PSCAF to PSCF, and PSCF to PSGCF, AMF*, LMF*, and SCF*.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg) + +``` + +graph LR + subgraph UIM + UIMF*((UIMF*)) + end + subgraph MT + PSCAF((PSCAF)) + end + subgraph RAN + end + subgraph CN + PSGCF((PSGCF)) + PSCF((PSCF)) + AMF*[(AMF*)] + LMF*[(LMF*)] + SCF*[(SCF*)] + end + UIMF* --- PSCAF + PSCAF --- PSCF + PSCF --- PSGCF + PSCF --- AMF* + PSCF --- LMF* + PSCF --- SCF* + +``` + +Diagram of packet data service-related Functional Entities (FEs) across four domains: UIM, MT, RAN, and CN. UIM contains UIMF\*. MT contains PSCAF. RAN is empty. CN contains PSGCF, PSCF, AMF\*, LMF\*, and SCF\*. Lines connect UIMF\* to PSCAF, PSCAF to PSCF, and PSCF to PSGCF, AMF\*, LMF\*, and SCF\*. + +\* For a description of these FEs please see sections 5.4.1 and 5.4.2. + +**Figure 5-4/Q.1711 – The packet data service-related FEs** + +#### 5.4.3.1 Functional Entities on the network side of the radio interface + +**PSCF – Packet Service Control Function:** This FE provides the packet service control functionality in the IMT-2000 Core Network. It includes functionality to: + +- a) control a packet service by interacting with the PSCAF in establishing and maintaining: + - a packet data service context associated with a mobile terminal to enable the support of a specific packet data protocol (e.g. Internet Protocol), + - a packet data routing context associated with a mobile terminal to enable routing of packets to and from a mobile terminal and between mobile terminals; +- b) interact with the PSGCF for: + - provision of updates on the packet data service and routing context associated with a mobile terminal (this function can be provided by either the LMF or the PSCF), + - user data transfer between external packet data networks and the mobile terminal; +- c) interact with the AMF for authentication purposes; +- d) perform confidentiality control, user authentication, and parameter update for packet data services (this capability can be in either the LMF or the PSCF); +- e) interact with the LMF for: + - accessing and updating subscriber-related data (e.g. subscriber service profiles), + - updating packet service and routing information (e.g. packet data services information and location information); +- f) interact with the SCF to support the transfer of information between the SCF and UIMF; +- g) interact with the PSCAF as the mobile counter-part of the PSCF for control of user data transfer across the radio interface, including support for sleep mode and priority access; +- h) interact with the RACF to initiate the dynamic allocation of radio resources for the transport of data packets across the radio interface; +- i) interact with the RACF for ciphering execution control (including ciphering information delivering and triggering); +- j) control packet-data bearers to transport data packets within the fixed network part and interact with the appropriate Functional Entities; +- k) perform location management for the mobile terminal, including: + - identification of radio-environment-independent terminal location information (in terms of a geographic area) provided by the RACF, + - detection and handling of paging responses, if needed, + - interaction with RACFs for the request of paging execution, if needed, and + - to update the packet data routing context, if necessary; +- l) route and relay packets to and from a mobile terminal according to the packet data service context and the associated quality of service classes. + +**PSGCF – Packet Service Gateway Control Function:** This FE provides the packet service gateway control functionality in the IMT-2000 Core Network. It includes functionality to: + +- a) route and relay data packets transparently between other packet data networks and the PSCF according to the packet service and routing context associated with a mobile terminal; +- b) interact with the PSCF for updates of packet service and routing contexts; + +- c) interact with other packet data networks, such as to provide routing address to external packet data networks (such as Internet Protocol or X.25) to allow them to address a mobile terminal (e.g. an Internet Protocol address for Internet Protocol-based networks) or to provide route optimisation messages to an external packet data network; +- d) control packet-data bearers for the transport of data packets between the PSGCF and PSCF; +- e) interact with the LMF for updates of packet service and routing information (e.g. packet data services information and location information). + +#### 5.4.3.2 Functional Entities on the mobile side of the radio interface + +**PSCAF – Packet Service Control Agent Function:** This FE provides the packet service control agent functionality in the IMT-2000 mobile terminal. It includes functionality to: + +- a) interact with the PSCF to control the transport of data packets across the radio interface according to the chosen packet service including support for sleep mode and priority access; +- b) provide location management information to the PSCF; +- c) interact with the RACAF to initiate and control the dynamic allocation of radio resources for the transport of data packets across the radio interface; +- d) interact with the UIMF and PSCF for support of authentication and service control handling; +- e) relay indications relating to packet data service access to other user/terminal Functional Entities as required. + +# 6 Network Reference Model + +This subclause shows a possible grouping of Functional Entities into physical collections of functions and the physical relationships between those collections that may be realised for IMT-2000. This specific configuration alternative is not the only configuration possible. It is possible to construct other physical and network configuration scenarios for IMT-2000 deployments, including those noted in ITU-R Recommendations M.687-2 [1], M.816-1 [2], and Recommendation Q.1701 [9]: + +- Satellite: + - Passive mode; + - Switching in the sky. +- Cellular. +- Cordless: + - Public network – private users; + - Public network – public access; + - Private network – private users; + - Private network – public access; + - Residential. +- High bit rate access – line of sight: + - Office – indoor; + - Wireless local loop – outdoor. + +## 6.1 A generic reference model + +Figure 6-1 is a generic figure to illustrate possible groupings of Functional Entities into physical collections of functions and the physical interface relationships between those collections (i.e. reference points) that may be realised for IMT-2000. Note that the Network-to-Network Interface (NNI) is not shown as a single interface, since all the interfaces across Core Network boundaries together constitute the NNI. + +The following is a list of physical groupings shown in Figure 6-1: + +AC      Authentication Centre +BS      Base Station +DMSC   Drift MSC +GLR    Gateway Location Register +GMSC   Gateway MSC +HLR    Home Location Register +IP       Intelligent Peripheral +MSC    Mobile Switching Centre +MT      Mobile Terminal +PDGN   Packet Data Gateway Node +PDSN   Packet Data Serving Node +RNC    Radio Network Controller +SCP    Service Control Point +SDP    Service Data Point +Tx      Transit Exchange +UIM    User Identity Module +VLR    Visitor Location Register + +![Figure 6-1a/Q.1711 – Generic reference model for IMT-2000 Alternative 1: Integrated call control and connection control FEs. The diagram shows the architecture of a mobile network with three main domains: UIM (User Identity Module), MT (Mobile Terminal), and CN (Core Network), connected via RAN (Radio Access Network).](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +The diagram illustrates the generic reference model for IMT-2000 Alternative 1, showing the integration of call control and connection control functions across different network layers. + +- UIM (User Identity Module):** Contains the UIMF (User Identity Module Function). It connects to the MT via the UIM-MT Interface. +- MT (Mobile Terminal):** Contains several functional elements: + - PSCAF (Packet Switched Call Admission Function) + - CCAF (Circuit Switched Call Admission Function) + - MCF (Mobility Control Function) and MGPF (Mobility Management Function) + - RACAF (Radio Access Control Function) and MRTR (Mobile Radio Termination) + It connects to the RAN via the MT-RAN Interface. +- RAN (Radio Access Network):** Consists of BS (Base Station) and RNC (Radio Network Controller) units. + - BS:** Contains RFTR (Radio Frequency Transmission/Reception) and SIBF (System Information Broadcast Function). + - RNC:** Contains SNCF (Session Network Control Function), GPF (Gateway Function), RACF (Radio Access Control Function), and ARF (Access Router Function). There are two RNC units shown. + The RAN connects to the CN via the RAN-CN Interface. +- CN (Core Network):** Contains various network elements and their interconnections: + - AC (Access Controller):** Contains AMFh (Access Management Function - home). + - HLR (Home Location Register):** Contains LMFh (Location Management Function - home). + - VLR/GLR (Visited Location Register / Gateway Location Register):** Contains LMFh, AMFv (Access Management Function - visited), and LMFv (Location Management Function - visited). + - MSC (Mobile Switching Center):** Contains CCF'/SSF (Call Control Function / Service Switching Function), GPCF (Gateway Policy Control Function), ARF, and SACF (Service Access Control Function). + - DMSC (Data MSC):** Contains ARF. + - PDSN (Packet Data Serving Node):** Contains PSCF (Packet Switched Call Function) and GPCF. + - SDP (Service Data Point):** Contains SDF (Service Data Function). + - SCF (Service Control Function):** Contains SDF. + - GMSC (Gateway MSC):** Contains CCF'/SSF. + - IP (IP Router):** Contains SRF (Specialized Resource Function). + - PDGN (Packet Data Gateway Node):** Contains PSGCF (Packet Switched Gateway Control Function). + The CN connects to external networks via the NNI (Network-to-Network Interface). + +Functional elements are interconnected by solid and dashed lines, representing different types of signaling and data flows. On the right side, brackets indicate the typical network elements associated with each layer or function group, such as SCP, SDP, VLR/GLR, MSC/GMSC, PDSN, AC, HLR, IP, Tx, and PDGN. + +Figure 6-1a/Q.1711 – Generic reference model for IMT-2000 Alternative 1: Integrated call control and connection control FEs. The diagram shows the architecture of a mobile network with three main domains: UIM (User Identity Module), MT (Mobile Terminal), and CN (Core Network), connected via RAN (Radio Access Network). + +**Figure 6-1a/Q.1711 – Generic reference model for IMT-2000 +Alternative 1: Integrated call control and connection control FEs** + +![Figure 6-1b/Q.1711 – Generic reference model for IMT-2000. Alternative 2: Separated call control and connection control FEs. The diagram shows the architecture of a mobile network with three main vertical domains: UIM (User Interface Module), MT (Mobile Terminal), and CN (Core Network), connected by RAN (Radio Access Network).](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +The diagram illustrates the generic reference model for IMT-2000, Alternative 2, showing separated call control and connection control FEs. It is organized into three main vertical domains: UIM (User Interface Module), MT (Mobile Terminal), and CN (Core Network), connected by RAN (Radio Access Network). + +- UIM (User Interface Module):** Contains a UIMF (User Interface Function). +- MT (Mobile Terminal):** Contains PSCAF, CCAF, CnCAF, MCF, MGPF, RACAF, and MRTR. +- RAN (Radio Access Network):** Contains BS (Base Station) with RFTR and SIBF, and RNC (Radio Network Controller) with SNCF, CnCF, GPF, RACF, and ARF. The RAN is connected to the MT via the MT-RAN Interface and to the CN via the RAN-CN Interface. +- CN (Core Network):** Contains several functional blocks: + - AC (Access Controller):** Contains AMFh. + - HLR (Home Location Register):** Contains LMFh. + - VLR/GLR (Visitor Location Register/Guest Location Register):** Contains LMFh, AMFv, and LMFv. + - MSC (Mobile Switching Center):** Contains CCF/SSF, CnCF, GPCF, SACF, and ARF. + - DMSC (Data MSC):** Contains ARF. + - PDSN (Packet Data Serving Network):** Contains PSCF and GPCF. + - SDP (Service Data Point):** Contains SDF. + - SCF (Service Control Function):** Contains SDF. + - GMSC (Gateway MSC):** Contains CCF/SSF and CnCF. + - IP (IP Gateway):** Contains SRF. + - PDGN (Packet Data Gateway):** Contains PSGCF. + +Interfaces and Connections: + +- UIM-MT Interface:** Between UIM and MT. +- MT-RAN Interface:** Between MT and RAN. +- RAN-CN Interface:** Between RAN and CN. +- NNI (Network-to-Network Interface):** At the bottom of the CN domain. + +External connections on the right side of the CN domain: + +- SCP (Service Control Point) +- SDP/SCP +- VLR/GLR/SCP/ MSC/GMSC/ PDSN +- AC/SDP/SCP/HLR/VLR/GLR/IP/MSC/GMSC +- HLR/VLR/GLR/SCP +- Tx/ MSC/HLR/SCP/IP +- Tx/ GMSC/HLR/IP/SCP +- MSC/GMSC/SCP +- PDSN +- PDGN/HLR + +T1199510-98 + +Figure 6-1b/Q.1711 – Generic reference model for IMT-2000. Alternative 2: Separated call control and connection control FEs. The diagram shows the architecture of a mobile network with three main vertical domains: UIM (User Interface Module), MT (Mobile Terminal), and CN (Core Network), connected by RAN (Radio Access Network). + +Figure 6-1b/Q.1711 – Generic reference model for IMT-2000 + Alternative 2: Separated call control and connection control FEs + +NOTE 1 – The GLR is an optional node between the VLR and the HLR, which may be used to optimize the handling of subscriber location data across network boundaries. In the case a subscriber is roaming outside the Home IMT-2000 network the GLR plays the role of an HLR towards the VLR and the role of a VLR towards the HLR. The GLR handles any location change between different VLR service areas in the Visited network without involving the HLR. The GLR is not involved when the subscriber is roaming within its Home IMT-2000 network. + +NOTE 2 – The GMSC can be placed in any network. In the case where a GLR is not used, the GMSC contacts the HLR for routing information. The call is then routed to the visited MSC. In the case where a GLR is used, two possible alternatives can be used: 1) the GMSC in the Interrogating network contacts the HLR for routing information to the Visited network's GMSC. After connecting the call to the Visited network, the GMSC in the Visited network contacts the GLR for routing information to the visited MSC. The call is then routed to visited MSC. 2) the GMSC contacts the HLR for routing information. The call is then routed directly to the visited MSC. + +## 6.2 Network reference points + +![Figure 6-2/Q.1711 – Reference points in IMT-2000 reference model. This diagram illustrates the network architecture and reference points for IMT-2000. On the left, a UIM (User Identity Module) is connected to an MT (Mobile Terminal) via reference point H. The MT is connected to a BS (Base Station) via reference point U. The BS is connected to an RNC (Radio Network Controller) via reference point Q. This RNC is connected to a PDG (Packet Data Gateway) via reference point N, to a PDSN (Packet Data Serving Node) via reference point M, and to an MSC (Mobile Switching Center) via reference point P. The PDSN is also connected to a PDGN (Packet Data Network Gateway) via reference point V1, to a VLR/GLR (Visited Location Register/Gateway Location Register) via reference point V2, and to an HLR (Home Location Register) via reference point V3. The PDGN is connected to another VLR/GLR via reference point V4. The HLR is connected to an AC (Authentication Center) via reference point F, to a GMSC (Gateway MSC) via reference point I5, and to an SCP (Service Control Point) via reference point I3. The MSC is connected to a DMSC (DMSC) via reference point E1, to a VLR/GLR via reference point B1, to a GMSC via reference point E2, and to an IP (IP Gateway) via reference point G1. The DMSC is connected to another VLR/GLR via reference point C2. The second VLR/GLR is connected to the HLR via reference point D1 and to another GMSC via reference point B2. The IP is connected to the SCP via reference point J. The SCP is connected to another SCP via reference point S and to an SDP (Service Data Point) via reference point K. The second SDP is connected to another SDP via reference point W. Other reference points shown include L, R, G2, I1, I2, I4, and I6.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Figure 6-2/Q.1711 – Reference points in IMT-2000 reference model. This diagram illustrates the network architecture and reference points for IMT-2000. On the left, a UIM (User Identity Module) is connected to an MT (Mobile Terminal) via reference point H. The MT is connected to a BS (Base Station) via reference point U. The BS is connected to an RNC (Radio Network Controller) via reference point Q. This RNC is connected to a PDG (Packet Data Gateway) via reference point N, to a PDSN (Packet Data Serving Node) via reference point M, and to an MSC (Mobile Switching Center) via reference point P. The PDSN is also connected to a PDGN (Packet Data Network Gateway) via reference point V1, to a VLR/GLR (Visited Location Register/Gateway Location Register) via reference point V2, and to an HLR (Home Location Register) via reference point V3. The PDGN is connected to another VLR/GLR via reference point V4. The HLR is connected to an AC (Authentication Center) via reference point F, to a GMSC (Gateway MSC) via reference point I5, and to an SCP (Service Control Point) via reference point I3. The MSC is connected to a DMSC (DMSC) via reference point E1, to a VLR/GLR via reference point B1, to a GMSC via reference point E2, and to an IP (IP Gateway) via reference point G1. The DMSC is connected to another VLR/GLR via reference point C2. The second VLR/GLR is connected to the HLR via reference point D1 and to another GMSC via reference point B2. The IP is connected to the SCP via reference point J. The SCP is connected to another SCP via reference point S and to an SDP (Service Data Point) via reference point K. The second SDP is connected to another SDP via reference point W. Other reference points shown include L, R, G2, I1, I2, I4, and I6. + +Figure 6-2/Q.1711 – Reference points in IMT-2000 reference model + +**Table 6-1/Q.1711 – Names of Reference Points** + +| Reference Point | Interface | +|------------------------|-------------------| +| B1 | MSC – VLR/GLR | +| B2 | GMSC – VLR/GLR | +| C1 | GMSC – HLR | +| C2 | MSC – HLR | +| D1 | VLR/GLR – HLR | +| D2 | VLR/GLR – VLR/GLR | +| E1 | MSC – DMSC | +| E2 | MSC – GMSC | +| E3 | GMSC – GMSC | +| F | HLR – AC | +| G1 | MSC – IP | +| G2 | GMSC – IP | +| H | MT – UIM | +| I1 | MSC – SCP | +| I2 | GMSC – SCP | +| I3 | SCP-HLR | +| I4 | SCP-VLR/GLR | +| I5 | SCP-AC | +| I6 | SCP-PDSN | +| J | SCP – IP | +| K | SCP – SDP | +| L | RNC-DMSC | +| M | PDSN-RNC | +| N | PDSN-PDGN | +| P | MSC – RNC | +| Q | RNC – BS | +| R | RNC – RNC | +| S | SCP – SCP | +| U | BS – MT | +| V1 | PDSN – HLR | +| V2 | PDGN – HLR | +| V3 | PDSN – VLR/GLR | +| V4 | PDGN – VLR/GLR | +| W | SDP – SDP | + +# 7 Global Roaming and Interworking Scenarios + +## 7.1 Introduction + +An essential service requirement of IMT-2000 is that IMT-2000 users should be able to use their equipment and subscriptions in different family member networks, and to establish calls and connections between networks of different operators. To support this service requirement, interconnection between different IMT-2000 family member networks is required. + +Network interworking is required whenever an IMT-2000 network and any other network are involved in the execution of a service request. An IMT-2000 network should therefore be able to interwork with a wide range of existing and future partner networks and services such as other mobile networks, the Internet, ISDN, B-ISDN, PSTN, UPT, PDN, GII, etc. + +## 7.2 Global roaming + +### 7.2.1 General + +The types of networks that are required to support NNI interconnections are as follows: + +- a) **Home network** is the IMT-2000 network which is related by subscription to the IMT-2000 user. It permanently holds location and service profile information related to the IMT-2000 user. +- b) **Supporting network** is the network which provides support for a variety of services including, but not limited to, service logic programs and service-related data for IN supplementary services provided to IMT-2000 users. +- c) **Visited (Serving) network** is the IMT-2000 network where an active IMT-2000 user is being served. +- d) **Interrogating network** is the network from which a routing data retrieval request is sent to the Home network of the called IMT-2000 user. +- e) **Destination network** is the network to which an outgoing call from an IMT-2000 user is destined. +- f) **Previously Visited network** is the network where an IMT-2000 user was served before entering the Visited (Serving) network. + +All the above mentioned networks are logical networks. Some or all of them can, for a specific traffic case, be the same physical network. + +### 7.2.2 Interconnections + +Interconnection between different IMT-2000 family member networks is required for the following purposes: + +- a) Establishment of calls and connections between different IMT-2000 family member networks (this includes calls by and to roaming users). +- b) Transfer/retrieval of user and location data of roaming users (e.g. for location management procedures: location update, location registration, location cancellation). +- c) Transfer of call detail records/charging related information of roaming users. +- d) Support for a Virtual Home Environment. +- e) Security monitoring to protect the internal network signalling, including policing of procedures, protocol stack termination, and interworking with internationally recognised signalling systems. This may be coupled with mutual authentication. + +- f) Transparent exchange of packet data between different IMT-2000 family member networks (this includes packets originated by and destined to roaming users). +- g) Network interconnections to support the interaction between the UIM and *home* SCF. + +The network interconnection requirements for each of these purposes are treated in the following subclauses. + +#### 7.2.2.1 Establishment of calls and connections between IMT-2000 networks + +For the establishment of calls and connections, interconnection between the call/connection control functions in different IMT-2000 networks is required. In addition, interconnection between IMT-2000 networks and networks for fixed communication is required. + +Due to the mobility of the user, retrieval of location/routing data may be required prior to or during call set-up. The network interconnection required for this is treated separately in the next subclause. + +Figure 7-1 shows the network interconnection on a call control level. In the mobile originating case, the calls are established from the Visited network to any Destination network. In the mobile terminating case, the calls are established from the Interrogating network to the Visited network, however, one or more intermediate networks may be present, for instance if the Interrogating and Visited networks are not adjacent. + +![Diagram of network interconnection at call control level. A Visited network (CCFv/SSFv) and an Interrogating network (CCFi/SSFi) are connected via an NNI. The diagram is labeled T1199530-98.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +The diagram shows two ovals representing network functions: 'CCFv/SSFv' on the left and 'CCFi/SSFi' on the right. Above the left oval is the text 'Visited network'. Above the right oval is the text 'Interrogating network'. A horizontal line connects the two ovals, and a vertical line intersects this horizontal line at its center. Below the intersection is the label 'NNI'. To the right of the 'NNI' label is the text 'T1199530-98'. + +Diagram of network interconnection at call control level. A Visited network (CCFv/SSFv) and an Interrogating network (CCFi/SSFi) are connected via an NNI. The diagram is labeled T1199530-98. + +NOTE – In some cases, the Interrogating network could be the Home network. + +**Figure 7-1/Q.1711 – Network interconnection at call control level** + +For Alternative 2 of subclause 5.4 (Separated Call Control and Connection Control), a functional relationship between CnCFs is also needed. Similar to the call control level, different instances of the Connection Control Function are possible: the function resides in the *interrogating* CnCF (CnCFi) or in the *visited* CnCF (CnCFv). Figure 7-2 shows this interconnection. + +![Diagram of network interconnection at connection control level. A Visited network (CnCFv) and an Interrogating network (CnCFi) are connected via an NNI. The diagram is labeled T1199540-98.](42c65f5cb106938992fc73c05c8713d2_img.jpg) + +The diagram shows two ovals representing network functions: 'CnCFv' on the left and 'CnCFi' on the right. Above the left oval is the text 'Visited network'. Above the right oval is the text 'Interrogating network'. A horizontal line connects the two ovals, and a vertical line intersects this horizontal line at its center. Below the intersection is the label 'NNI'. To the right of the 'NNI' label is the text 'T1199540-98'. + +Diagram of network interconnection at connection control level. A Visited network (CnCFv) and an Interrogating network (CnCFi) are connected via an NNI. The diagram is labeled T1199540-98. + +NOTE – In some cases, the Interrogating network could be the Home network. + +**Figure 7-2/Q.1711 – Network interconnection at connection control level** + +#### 7.2.2.2 Transfer and retrieval of user and location data + +Between IMT-2000 networks, user profile data and location (routing) data are separated from normal call control. This supports the mobility aspect: user data can be transferred to and location data retrieved from a Serving network, enabling quicker call set-up, and user and location data can be retrieved independently of call control. + +##### A) LMFv (Visited network) – LMFh (Home network) – Relationship + +![Diagram showing the network interconnection between a Visited network (LMFv) and a Home network (LMFh) via an NNI interface.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +The diagram illustrates the interconnection between a Visited network and a Home network. On the left, an oval labeled 'LMFv' is positioned below the text 'Visited network'. On the right, an oval labeled 'LMFh' is positioned below the text 'Home network'. A horizontal line connects the two ovals, and a vertical line intersects this horizontal line at its center. The label 'NNI' is placed below the intersection point. In the bottom right corner, the text 'T1199550-98' is present. + +Diagram showing the network interconnection between a Visited network (LMFv) and a Home network (LMFh) via an NNI interface. + +Figure 7-3/Q.1711 – Network interconnection for transfer of user data + +Figure 7-3 shows an interconnection between a *home* LMF (suffix 'h') and a *visited* LMF (suffix 'v'). This type of interconnection is used in the following procedures: + +###### *Location registration/updating* + +The transfer and retrieval of location data is performed between the LMF in the Home network (LMFh) and the LMF in the Visited network (LMFv). + +###### *Transfer or retrieval of trigger/service profile data* + +The transfer and retrieval of trigger/service profile data is performed between the LMFh and the LMFv at location registration, when changes are made, or at the request of the home or visited system. + +###### *Retrieval of location and user data* + +The relationship between the home and visited LMFs may also be used for retrieval of previous location and user data (e.g. authentication data) in case an IMT-2000 user leaves the area controlled by the previously visited LMF. + +###### *Updating of user data* + +The updating of user data is performed between the LMFh and LMFv when profile changes are made, or at the request of the visited system, e.g.: + +- User identity data (e.g. IMUI); +- VHE-related data; +- Standardized service data. + +##### B) LMFvn (New Visited network) – LMFvp (Previously Visited network) – Relationship + +![Diagram showing the network interconnection between a New Visited network (LMFvn) and a Previously Visited network (LMFvp) via an NNI interface.](5593facb376cb360bd4b0960b2911b3e_img.jpg) + +The diagram illustrates the interconnection between a New Visited network and a Previously Visited network. On the left, an oval labeled 'LMFvn' is positioned below the text 'New Visited network'. On the right, an oval labeled 'LMFvp' is positioned below the text 'Previously Visited network'. A horizontal line connects the two ovals, and a vertical line intersects this horizontal line at its center. The label 'NNI' is placed below the intersection point. In the bottom right corner, the text 'T1199560-98' is present. + +Diagram showing the network interconnection between a New Visited network (LMFvn) and a Previously Visited network (LMFvp) via an NNI interface. + +Figure 7-4/Q.1711 – Network interconnection for retrieval of user data + +Figure 7-4 shows a network interconnection between the *previously visited* LMF (suffix 'vp') and the *new visited* LMF (suffix 'vn'). This type of interconnection may be used for the following procedure: + +###### *Location updating* + +The transfer and retrieval of user information (e.g. IMUI and authentication data) from the LMFvp is performed when the user has roamed into an area controlled by the LMFvn. + +NOTE – By retrieving user information from the LMFvp using the temporary identity, user integrity can be maintained. The alternative is also supported, meaning that the mobile terminal is requested to provide the full identity in clear text after which user information can be retrieved from the Home network using the relationship illustrated in Figure 7-3. + +##### **C) LMFvp (Previously Visited network) – LMFh (Home network) – Relationship** + +![Diagram showing the interconnection between a Previously Visited network (LMFvp) and a Home network (LMFh) via an NNI interface. The diagram includes labels 'Previously Visited network', 'Home network', 'LMFvp', 'LMFh', 'NNI', and 'T1199570-98'.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +The diagram illustrates a network interconnection between two entities: 'Previously Visited network' (containing LMFvp) and 'Home network' (containing LMFh). They are connected by a horizontal line representing an NNI (Network-to-Network Interface). The label 'NNI' is placed below the connection line. The identifier 'T1199570-98' is shown in the bottom right corner. + +Diagram showing the interconnection between a Previously Visited network (LMFvp) and a Home network (LMFh) via an NNI interface. The diagram includes labels 'Previously Visited network', 'Home network', 'LMFvp', 'LMFh', 'NNI', and 'T1199570-98'. + +**Figure 7-5/Q.1711 – Network interconnection for location cancellation** + +Figure 7-5 shows an interconnection between a *previously visited* LMF (suffix 'vp') and a *home* LMF (suffix 'h'). This type of interconnection is used in the following procedures: + +###### *Location and user data cancellation* + +The purpose of this process is to delete a subscriber's record (location and user data) from a previous LMF after he has registered with a new LMF. The procedure may also be used if the subscriber's record is to be deleted for other operator determined purposes, e.g. withdrawal of subscription, imposition of roaming restrictions or modifications to the subscription which result in roaming restrictions. Location cancellation can be used to enforce location updating including updating of subscriber data in the LMF at the next subscriber access. + +#### **7.2.2.3 Retrieval of user data for routing of calls** + +![Diagram showing the network interconnection for retrieval of data for routing calls. It includes three networks: Interrogating Network (with CCFi/SSFi, LMFi, SCFi), Home Network (with LMFh), and Visited Network (with LMFv). Connections are shown via NNI interfaces.](d4ed35f72863013455b8f015e0f2e47e_img.jpg) + +This diagram shows the network architecture for data retrieval. On the left, the 'Interrogating Network' contains three functional blocks: 'CCFi/SSFi', 'LMFi', and 'SCFi'. These are connected to a central 'Home Network' which contains 'LMFh'. The 'Interrogating Network' and 'Home Network' are separated by an 'NNI' interface. The 'Home Network' is further connected to a 'Visited Network' (containing 'LMFv') via another 'NNI' interface. The identifier 'T1199580-98' is located in the bottom right corner. + +Diagram showing the network interconnection for retrieval of data for routing calls. It includes three networks: Interrogating Network (with CCFi/SSFi, LMFi, SCFi), Home Network (with LMFh), and Visited Network (with LMFv). Connections are shown via NNI interfaces. + +**Figure 7-6/Q.1711 – Network interconnection for retrieval of data for routing calls** + +Figure 7-6 shows network interconnections between the *interrogating* LMF, CCF'/SSF, and SCF (suffix 'i'), the *home* LMF (suffix 'h'), and the *visited* LMF (suffix 'v') that are required for retrieval of routing and user data. Retrieval of routing and user data is necessary in the case of establishment of incoming calls to IMT-2000 users. This type of interconnection is used for the following: + +- 1) The LMFi, CCFi/SSFi, or SCFi may retrieve routing data from the LMFh. The LMFh may also provide trigger information to arm terminating triggers for the called party within the Interrogating network. +- 2) The LMFh retrieves more detailed routing information from the LMFv to be passed to the LMFi, CCFi/SSFi, or SCFi. + +#### 7.2.2.4 Transfer of call detail records + +Transfer of call detail records of users that roam outside their Home IMT-2000 network is required for: + +- a) Charging users for calls made in Visited networks; +- b) Reimbursement of visited operators by the home operator for calls made by the home operator's customers in the visited operators' networks. + +Transfer of call detail records is done at a TMN level. It is not discussed in detail here. + +#### 7.2.2.5 Virtual Home Environment + +The VHE is a capability whereby a user is offered the same service experience in a Visited network as in one's home system. The establishment of this concept realises that service provision and network operation may be separated, allowing services to be offered by networks other than those providing the home or visited call processing capabilities. + +NOTE – The degree to which the VHE matches the actual home environment may be subject to, for example, the degree of cooperation between the Visited network and Home or Supporting networks, their relative technical capabilities and the compatibility of the user terminal. + +##### 7.2.2.5.1 Virtual Home Environment capabilities + +The Virtual Home Environment supports: + +- **Service transparency** between different IMT-2000 networks. +- **Transparent execution** of the "*Virtual Home Environment*" service features: the VHE service features are used by the mobile operators to provide more functionality to the mobile users than basic mobility. The services may be executed without necessary sharing of service and subscriber information to the visited mobile operator (except roaming agreements). +- **Customised services**: the means for network operators, service providers and users to define their own specific features/services. +- **A personalised service set** with user personalisation of features/services. +- **Service level**: It is desirable that the roaming mobile users will experience the same service level as within their Home networks (the Virtual Home Environment concept). Therefore, it is desirable that the services are provided transparently by the Visited networks. +- **Provisioning of subscriber specific services**: The mobile users may have custom demands for functionality from their home service providers. The Virtual Home Environment intends to make management access to customised services available to the mobile users when roaming. +- **Limited network load**: The current mobile networks already contain a considerable signalling load to handle a mobile call. This signalling is required to maintain the mobility information of the mobile subscriber up to date. Therefore, the signalling load of new + +features must be limited as much as possible to ensure that the mobile network will not overload its signalling capacity. + +- **Activation of mobile-related call events** +- **Performing charging activities:** The VHE may be able to exchange charging parameters between the home service provider and Serving (Visited) network. This exchange is required to have service capabilities such as advice of charge. +- **Performing in-band user interaction:** The VHE shall provide the capabilities to order the playing of announcements and tones towards calling/called subscribers during the call-setup, call disconnection, unsuccessful call establishment, and incoming call procedures. +- **Allowing subscriber interaction:** The subscriber should have control capabilities to activate/register/invoke supplementary services. The VHE should be able to add functionality to these supplementary service control mechanisms. +- **Interaction with the supplementary services:** The mobile network's ability to provide interaction with a number of supplementary services needs to be considered. + +##### 7.2.2.5.2 Virtual Home Environment scenarios + +In this Recommendation two VHE scenarios are identified and described from their inter-networking implications perspectives and the location of the service control functionality. The Direct Home Command scenario, shown in Figure 7-7 and the Relay Service Control scenario shown in Figure 7-8, illustrate how the Virtual Home Environment concept can be supported. The Direct Home Command scenario may utilise the same IN procedures as in the transparent Relay Service Control. + +**Direct Home Command:** This scenario calls for invocation of service logic to query for instruction/information to the SCFsn. In this scenario the pre-arrangement between the Supporting and the Home networks or between the Supporting and the Visited networks may need screening capabilities of triggering invocation. + +![Diagram of VHE scenario: Direct Home Command. It shows three network domains: Home Network, Supporting/Home Network, and Serving Network. The Home Network contains AMF and LMFh. The Supporting/Home Network contains SCFsn/h. The Serving Network contains LMFv, SACF, and CCFv/SSFv. Connections are shown between AMF and SCFsn/h, LMFh and SCFsn/h, SCFsn/h and LMFv, SCFsn/h and SACF, and SCFsn/h and CCFv/SSFv. Vertical lines labeled NNI separate the networks. A small code T1199590-98 is in the bottom right.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +``` + +graph LR + subgraph Home_Network [Home Network] + AMF((AMF)) + LMFh((LMFh)) + end + subgraph Supporting_Home_Network [Supporting/Home Network] + SCFsn_h((SCFsn/h)) + end + subgraph Serving_Network [Serving Network] + LMFv((LMFv)) + SACF((SACF)) + CCFv_SSFv((CCFv/SSFv)) + end + AMF --- SCFsn_h + LMFh --- SCFsn_h + SCFsn_h --- LMFv + SCFsn_h --- SACF + SCFsn_h --- CCFv_SSFv + NNI1[NNI] + NNI2[NNI] + T1199590_98[T1199590-98] + +``` + +Diagram of VHE scenario: Direct Home Command. It shows three network domains: Home Network, Supporting/Home Network, and Serving Network. The Home Network contains AMF and LMFh. The Supporting/Home Network contains SCFsn/h. The Serving Network contains LMFv, SACF, and CCFv/SSFv. Connections are shown between AMF and SCFsn/h, LMFh and SCFsn/h, SCFsn/h and LMFv, SCFsn/h and SACF, and SCFsn/h and CCFv/SSFv. Vertical lines labeled NNI separate the networks. A small code T1199590-98 is in the bottom right. + +**Figure 7-7/Q.1711 – VHE scenario: Direct Home Command** + +**Relay Service Control:** This scenario calls for the invocation of the service logic via the SCFh or SCFv to query for instruction/information from the SCFsn. In this scenario the pre-arrangement between the Supporting and the Home networks or between the Supporting and the Visited networks ranges from relaying, to security/screening capabilities, to shared service logic. + +![Diagram of VHE scenario: Relay Service Control Mobility management triggers from Home network. It shows a Home Network on the left containing LMFh, SCFh, and AMF. A vertical line labeled NNI separates it from a Supporting Network on the right containing SCFsn. Connections: LMFh to SCFh, AMF to SCFh, SCFh to NNI, NNI to SCFsn. Reference T1199600-98.](7e14467740b2570a44379b347a697921_img.jpg) + +Diagram of VHE scenario: Relay Service Control Mobility management triggers from Home network. It shows a Home Network on the left containing LMFh, SCFh, and AMF. A vertical line labeled NNI separates it from a Supporting Network on the right containing SCFsn. Connections: LMFh to SCFh, AMF to SCFh, SCFh to NNI, NNI to SCFsn. Reference T1199600-98. + +**Figure 7-8a/Q.1711 – VHE scenario: Relay Service Control +Mobility management triggers from Home network** + +![Diagram of VHE scenario: Relay Service Control Call-related, call-unrelated, and mobility management triggers from Visited network. It shows three network areas: Home Network (left) with LMFh; Supporting/Home Network (middle) with SCFsn/h; and Serving Network (right) with LMFv, SCFv, CCFv/SSF, and SACF. Connections: LMFh to NNI, NNI to SCFsn/h, SCFsn/h to NNI, NNI to SCFv, SCFv to LMFv, SCFv to SACF, SCFv to CCFv/SSF. Reference T1199610-98.](fed4a04822c24fb22cca3a14f4ddae83_img.jpg) + +Diagram of VHE scenario: Relay Service Control Call-related, call-unrelated, and mobility management triggers from Visited network. It shows three network areas: Home Network (left) with LMFh; Supporting/Home Network (middle) with SCFsn/h; and Serving Network (right) with LMFv, SCFv, CCFv/SSF, and SACF. Connections: LMFh to NNI, NNI to SCFsn/h, SCFsn/h to NNI, NNI to SCFv, SCFv to LMFv, SCFv to SACF, SCFv to CCFv/SSF. Reference T1199610-98. + +**Figure 7-8b/Q.1711 – VHE scenario: Relay Service Control +Call-related, call-unrelated, and mobility management triggers from Visited network** + +#### 7.2.2.6 Obtaining and transferring fraud/abuse control related data + +Fraud/Abuse Control may be executed by a Service Logic Program (SLP) at an SCF. Events of interest may be reported to the SCF from the CCF'/SSF, LMF, AMF, or SACF. Figures 7-7 and 7-8 show the interconnections across the NNI which can be used for this event reporting. The triggers in the invoking FEs may be armed by the subscriber's profile or by the provisioning process for the FE. + +When events of interest occur, they would be reported to the SLP interested in them. This SLP may be constructed to deal with certain real time events only, or monitor events across multiple calls to look for patterns, or both. + +When a subscriber roams, the reporting of information for the events of interest would be handled by collecting the information in the Visited network and transferring it to the Home network as it is being obtained. + +#### 7.2.2.7 Network Interconnection for Packet Data Services + +Figure 7-9 shows network interconnections between the PSGCF of IMT-2000 family network A and the PSCF of IMT-2000 family network B. + +![Diagram of network interconnection for packet data services. It shows two IMT-2000 Family Networks, 'a' and 'b', connected via an NNI (Network Network Interface). Network 'a' contains a PSGCFa component, and Network 'b' contains a PSCFb component. The two components are connected to each other through the NNI. A reference code 'T1199620-98' is shown below the diagram.](5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg) + +Diagram of network interconnection for packet data services. It shows two IMT-2000 Family Networks, 'a' and 'b', connected via an NNI (Network Network Interface). Network 'a' contains a PSGCFa component, and Network 'b' contains a PSCFb component. The two components are connected to each other through the NNI. A reference code 'T1199620-98' is shown below the diagram. + +**Figure 7-9/Q.1711 – Network interconnection for packet data services** + +The PSCF interacts with the PSGCF for: + +- the provision of updates of the packet data service and routing context associated with a mobile terminal, and +- user data transfer between external packet data networks and the mobile terminal. + +The PSGCF: + +- routes and relays data packets transparently between other packet data networks and the PSCF according to the packet service and routing context associated with a mobile terminal; +- interacts with the Packet Service Control Function (PSCF) for updates of packet service and routing contexts; +- interacts with other packet data networks to provide a routing address to external packet data networks (such as Internet Protocol or X.25) to allow them to address a mobile terminal (e.g. an Internet Protocol address for Internet Protocol-based networks) or to provide route optimisation messages to an external packet data network controlling packet-data bearers to transport data packets between the PSGCF and PSCF. + +#### **7.2.2.8 Network interconnections to support the interaction between UIM and Home SCF** + +The interaction between the UIMF and *home* SCF for service control purposes will be supported across network boundaries. In this case the SACF or PSCF of the Serving network as well as the MCF or PSCAF support the transparent exchange of information between the SCFh and UIMF, for example to download and store service programs and/or application data. + +![Diagram showing network interconnections for UIMF-SCFh relationships. It is divided into four vertical sections: Home/Supporting Network, Serving Network, Mobile Terminal, and UIM. In the Home/Supporting Network is the SCFh component. In the Serving Network are the SACF and PSCF components. In the Mobile Terminal are the MCF and PSCAF components. In the UIM is the UIMF component. Connections are shown between SCFh and SACF, SCFh and PSCF, SACF and MCF, PSCF and PSCAF, MCF and UIMF, and PSCAF and UIMF. A reference code 'T1199630-98' is shown below the diagram.](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +Diagram showing network interconnections for UIMF-SCFh relationships. It is divided into four vertical sections: Home/Supporting Network, Serving Network, Mobile Terminal, and UIM. In the Home/Supporting Network is the SCFh component. In the Serving Network are the SACF and PSCF components. In the Mobile Terminal are the MCF and PSCAF components. In the UIM is the UIMF component. Connections are shown between SCFh and SACF, SCFh and PSCF, SACF and MCF, PSCF and PSCAF, MCF and UIMF, and PSCAF and UIMF. A reference code 'T1199630-98' is shown below the diagram. + +**Figure 7-10/Q.1711 – Network interconnections: UIMF-SCFh relationships** + +## 7.3 Internet (Internet Protocol) interworking + +Seamless packet data services and Internet access for IMT-2000 users require network interconnection and interworking of IMT-2000 family members. + +The following requirements should be supported by IMT-2000 systems for Internet access: + +- IMT-2000 packet data services should support mobile nodes regardless of whether their Internet Protocol addresses are assigned statically or dynamically. +- In particular, peer-to-peer communication of packet data users and mobile servers should be supported in either case. + +Two scenarios illustrate access to the Internet from IMT-2000 networks. First, suppose a user starts a data session in a Visited network with a static (or dynamic) Internet Protocol address assigned by the Home network, as shown in Figure 7-11a. Registration is done by the LMFv and LMFh or by the PSCFv and LMFh (i.e. the VLR and HLR or the PDSN and HLR). Authentication is done by the AMF or PSCFv (i.e. the AC or PDSN). The LMF, AMF and PSCF may contain additional subscriber information such as service profiles. Internet Protocol packets destined to the user's Internet Protocol address are forwarded by the PSGCFh to the PSCFv, according to a routing context associated with the mobile terminal maintained in the PSGCFh. The routing context is established during the data user registration, and updated between the PSCFv and PSGCFh. In the reverse direction, the PSCFv may similarly transfer Internet Protocol packets to the PSGCFh, based on the routing context maintained by the PSCFv; the PSGCFh in turn passes on the packets to the final destination on the Internet. In this case, the extra step of transfer from the PSCFv to the PSGCFh may be required for reasons such as compatibility with *ingress* filtering operations (filtering based on packet's source Internet Protocol address) of firewalls or routers. In cases where such considerations are not a concern, the PSCFv may transfer packets to the Internet directly through the PSGCFv. + +![Network interconnection scenario I diagram showing Visited and Home IMT-2000 networks connected via NNI interfaces. Visited network includes AMFv, LMFv, PSCFv, and RACF. Home network includes AMFh, LMFh, and PSGCFh connected to Internet/PDN.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +``` +graph LR + subgraph Visited_Network [Visited IMT-2000 Network] + AMFv((AMFv)) + LMFv((LMFv)) + PSCFv((PSCFv)) + RACF((RACF)) + end + + subgraph Home_Network [Home IMT-2000 Network] + AMFh((AMFh)) + LMFh((LMFh)) + PSGCFh((PSGCFh)) + end + + Internet[Internet/PDN] + + AMFv --- LMFv + LMFv --- PSCFv + PSCFv --- RACF + + AMFh --- LMFh + LMFh --- PSGCFh + PSGCFh --- Internet + + LMFv -- NNI --- LMFh + PSCFv -- NNI --- LMFh + PSCFv -- NNI --- PSGCFh +``` + +Network interconnection scenario I diagram showing Visited and Home IMT-2000 networks connected via NNI interfaces. Visited network includes AMFv, LMFv, PSCFv, and RACF. Home network includes AMFh, LMFh, and PSGCFh connected to Internet/PDN. + +**Figure 7-11a/Q.1711 – Network interconnection scenario I for IMT-2000 packet data services: Using Internet Protocol addresses (either static or dynamic) assigned by the Home network** + +If the user drifts to a new Visited network (i.e. moves from one Core Network to another), the routing context maintained in the PSGCFh is updated and Internet Protocol packets are forwarded by the PSGCFh directly to the PSCFvn (new Visited network), as shown in Figure 7-11b. In the reverse direction, the PSCFvn may transfer Internet Protocol packets to the PSGCFh as discussed in the previous paragraph. + +![Figure 7-11b/Q.1711 – Scenario I continuation. This diagram shows network interconnections between three IMT-2000 networks: 'Previously Visited IMT-2000 Network' (top left), 'Home IMT-2000 Network' (top right), and 'New Visited IMT-2000 Network' (bottom). The 'Previously Visited' network contains AMFvp, LMFvp, PSCFvp, and RACF. The 'Home' network contains AMFh, LMFh, and PSGCFh. The 'New Visited' network contains PSCFvn, LMFvn, AMFvn, and RACF. Connections include NNI (Network-to-Network Interfaces) between AMFvp and AMFh, LMFvp and LMFh, PSCFvp and PSGCFh, and PSCFvn and LMFvn. A thick line connects PSCFvp to PSGCFh. An arrow points from PSGCFh to 'Internet/PDN'. A reference code 'T1199650-98' is in the bottom right.](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +Figure 7-11b/Q.1711 – Scenario I continuation. This diagram shows network interconnections between three IMT-2000 networks: 'Previously Visited IMT-2000 Network' (top left), 'Home IMT-2000 Network' (top right), and 'New Visited IMT-2000 Network' (bottom). The 'Previously Visited' network contains AMFvp, LMFvp, PSCFvp, and RACF. The 'Home' network contains AMFh, LMFh, and PSGCFh. The 'New Visited' network contains PSCFvn, LMFvn, AMFvn, and RACF. Connections include NNI (Network-to-Network Interfaces) between AMFvp and AMFh, LMFvp and LMFh, PSCFvp and PSGCFh, and PSCFvn and LMFvn. A thick line connects PSCFvp to PSGCFh. An arrow points from PSGCFh to 'Internet/PDN'. A reference code 'T1199650-98' is in the bottom right. + +**Figure 7-11b/Q.1711 – Scenario I continuation** + +For the second scenario, suppose a user starts a data session in a Visited network with a local Internet Protocol address assigned dynamically by the Visited network on a per-session basis, as shown in Figure 7-12a. The use of a dynamic Internet Protocol address local to the Visited network allows efficient local processing and routing, and conserves Internet Protocol addresses. Registration and authentication are as in the previous scenario. Access to and from the Internet is directly through the Visited network using the PSGCFv, without an extra step of Internet Protocol forwarding across the CN boundary as required in the previous scenario. + +![Figure 7-12a/Q.1711 – Network interconnection scenario II for IMT-2000 packet data services: Using temporary Internet Protocol addresses assigned dynamically by the Visited network. This diagram shows connections between a 'Visited IMT-2000 Network' (left) and a 'Home IMT-2000 Network' (right). The 'Visited' network contains AMFv, LMFv, PSCFv, PSGCFv, and RACF. The 'Home' network contains AMFh and LMFh. NNIs are shown between AMFv and AMFh, and LMFv and LMFh. A thick line connects PSCFv to PSGCFv. An arrow points from PSGCFv to 'Internet/PDN'. A reference code 'T1199660-98' is in the bottom right.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Figure 7-12a/Q.1711 – Network interconnection scenario II for IMT-2000 packet data services: Using temporary Internet Protocol addresses assigned dynamically by the Visited network. This diagram shows connections between a 'Visited IMT-2000 Network' (left) and a 'Home IMT-2000 Network' (right). The 'Visited' network contains AMFv, LMFv, PSCFv, PSGCFv, and RACF. The 'Home' network contains AMFh and LMFh. NNIs are shown between AMFv and AMFh, and LMFv and LMFh. A thick line connects PSCFv to PSGCFv. An arrow points from PSGCFv to 'Internet/PDN'. A reference code 'T1199660-98' is in the bottom right. + +**Figure 7-12a/Q.1711 – Network interconnection scenario II for IMT-2000 packet data services: Using temporary Internet Protocol addresses assigned dynamically by the Visited network** + +As the user drifts to a new Visited network (i.e. moves from one Core Network to another), Internet Protocol forwarding across the CN boundary between the PSGCFvp (previous Visited network) and the PSCFvn (new Visited network) may occur; this is shown in Figure 7-12b. Note that the LMFvn may retrieve user information directly from the LMFvp rather than from the LMFh, as discussed in Figure 7-4. + +![Network diagram showing Scenario II continuation with Previously Visited IMT-2000 Network, Home IMT-2000 Network, and New Visited IMT-2000 Network connected via NNI interfaces to the Internet/PDN.](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +The diagram illustrates a network architecture for Scenario II continuation, involving three main network entities and their interconnections: + +- Previously Visited IMT-2000 Network:** Contains functional blocks AMFvp, LMFvp, PSCFvp, PSGCFvp, and RACF. AMFvp and LMFvp are connected. LMFvp connects to PSCFvp via an NNI interface. PSCFvp is connected to PSGCFvp and RACF. PSGCFvp connects to the Internet/PDN via an NNI interface. +- Home IMT-2000 Network:** Contains functional blocks AMFh, LMFh, PSCFvn, LMFvn, AMFvn, and RACF. AMFh and LMFh are connected. LMFh connects to PSCFvn via an NNI interface. PSCFvn is connected to LMFvn and RACF. LMFvn is connected to AMFvn. There is also an NNI interface between LMFh and the Internet/PDN. +- New Visited IMT-2000 Network:** Contains functional blocks PSCFvn, LMFvn, AMFvn, and RACF. These are connected similarly to the Home network: PSCFvn to LMFvn and RACF, and LMFvn to AMFvn. +- Internet/PDN:** The central external network. It receives connections from PSGCFvp (Previously Visited), LMFh (Home), and PSCFvn (New Visited) via NNI interfaces. + +Additional labels include 'T1199670-98' near the bottom right of the diagram. + +Network diagram showing Scenario II continuation with Previously Visited IMT-2000 Network, Home IMT-2000 Network, and New Visited IMT-2000 Network connected via NNI interfaces to the Internet/PDN. + +**Figure 7-12b/Q.1711 – Scenario II continuation** + +# ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression: definitions, symbols, classification +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Overall network operation, telephone service, service operation and human factors +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media, digital systems and networks +- Series H Audiovisual and multimedia systems +- Series I Integrated services digital network +- Series J Transmission of television, sound programme and other multimedia signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits +- Series N Maintenance: international sound programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality, telephone installations, local line networks +- Series Q Switching and signalling** +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminals for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communications +- Series Y Global information infrastructure and Internet protocol aspects +- Series Z Languages and general software aspects for telecommunication systems \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1742.1-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1742.1-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.1-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/Q/T-REC-Q.1742.1-200212-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.1742.1-200212-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60031e51ea8d20a07b503f35a46108812d5f7726 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.1-200212-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19a4fcda8e23cd24519ed25a5fef31293a48b85d72486cfe5038e191ee7a7e5c +size 236060 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b50dc75709c9ec73b4542e255f4eec7fbd4a43b2 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f939d1b50a60b6dfd54db2bf9ae7d5c3c68f2667484e4507970bae2174a7f7 +size 204124 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ab61e8a77fa8a03c2221747d2e13c8b7f52133b --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d260628f955e3b06c0ae0ca4c08ec4875ebc613b313f42c09f5628a62af5b9d +size 177803 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c481eb8c01ef8a59b149f0724e51a02046668973 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bd8ab65e76b2872c2b9979fb6ca431289e99c44e6c0b947c45340620f7cb07b +size 83100 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8f95d509173ad0b9b40de9920487ac9de0038e5 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7afb673136b6d3920c61747c883c6ddff2f2ddc85c74aea6a4cd70f6af6a4389 +size 106873 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16bd9d15ee70d311809759d8240985e234a37ce0 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:578a8ff12b2a82f136d119bd8bf4d2f94152e4766ae9db8bf91cb697497b9c75 +size 160656 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4d6100f9dbe550b9c01815967f7553476a09d5c --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a747c4211dfbf2bc8701af0a89d50bbf4b27965e460eb5d8c1db7fb07293cafe +size 49649 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1b70d8513c85dac2714c8e300b118df8283deb0 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781810498d30616a66111f3ac4caace35b24fe782d9e797b344c8ffdc87730eb +size 193740 diff --git a/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..11b2785f6f0fbbfa639e8642c908191dcf934632 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.7-200810-I_PDF-E/raw.md @@ -0,0 +1,5946 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1742.7** + +(10/2008) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**IMT-2000 References (approved as of +30 June 2008) to ANSI-41 evolved Core +Network with cdma2000 Access Network** + +Recommendation ITU-T Q.1742.7 + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T Q.1742.7** + +## **IMT-2000 References (approved as of 30 June 2008) to ANSI-41 evolved Core Network with cdma2000 Access Network** + +## **Summary** + +Recommendation ITU-T Q.1742.7 associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 30 June 2008 for the IMT-2000 Family Member "ANSI-41 evolved Core Network with cdma2000 Access Network." + +3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.1. 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.2. 3GPP2 specifications that were approved as of 30 June 2003 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.3. 3GPP2 specifications that were approved as of 30 June 2004 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.4. 3GPP2 specifications that were approved as of 31 December 2005 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.5. 3GPP2 specifications that were approved as of 31 December 2006 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.6. The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in Recommendation ITU-R M.1457-6. The associations for other IMT-2000 Family Members are identified in the ITU-T Q.174x-series Recommendation. + +This Recommendation combines and associates the regional standards for the core network of this IMT-2000 Family Member into a global Recommendation. + +## **Source** + +Recommendation ITU-T Q.1742.7 was approved on 14 October 2008 by ITU-T Study Group 19 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +ANSI-41, cdma2000, Core Network, IMT-2000, third generation system. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|------|---------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Introduction ..... | 9 | +| 6 | Basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member..... | 10 | +| 7 | Network Entities ..... | 17 | +| 7.1 | Authentication, Authorization and Accounting (AAA) ..... | 17 | +| 7.2 | Authentication Centre (AC) ..... | 17 | +| 7.3 | Call Data Collection Point (CDCP)..... | 17 | +| 7.4 | Call Data Generation Point (CDGP) ..... | 18 | +| 7.5 | Call Data Information Source (CDIS)..... | 18 | +| 7.6 | Call Data Rating Point (CDRP)..... | 18 | +| 7.7 | Collection Function (CF) – [Intercept]..... | 18 | +| 7.8 | Coordinate Routing Data Base (CRDB)..... | 18 | +| 7.9 | Customer Service Centre (CSC)..... | 18 | +| 7.10 | Delivery Function (DF) – [Intercept] ..... | 18 | +| 7.11 | Equipment Identity Register (EIR)..... | 19 | +| 7.12 | evolved Packet Data Interworking Function (ePDIF) ..... | 19 | +| 7.13 | Home Agent (HA) ..... | 19 | +| 7.14 | Home Location Register (HLR) ..... | 19 | +| 7.15 | Intelligent Peripheral (IP) ..... | 19 | +| 7.16 | Intercept Access Point (IAP) ..... | 19 | +| 7.17 | Interworking Function (IWF) ..... | 19 | +| 7.18 | IP Services ..... | 19 | +| 7.19 | Local Position Determining Entity (LPDE) ..... | 20 | +| 7.20 | Managed Wireless Network Entity (MWNE) ..... | 20 | +| 7.21 | Message Centre (MC)..... | 20 | +| 7.22 | Mobile Position Centre (MPC)..... | 20 | +| 7.23 | Mobile Switching Centre (MSC)..... | 20 | +| 7.24 | Number Portability DataBase (NPDB) ..... | 20 | +| 7.25 | Over-The-Air Service Provisioning Function (OTAF) ..... | 20 | +| 7.26 | Packet Data Network (PDN) ..... | 20 | +| 7.27 | Packet Data Serving Node (PDSN) ..... | 20 | +| 7.28 | Position Determining Entity (PDE)..... | 20 | +| 7.29 | Service Control Point (SCP)..... | 21 | +| 7.30 | Service Node (SN)..... | 21 | + +| | | | +|------|---------------------------------------------------------------|----| +| 7.31 | Short Message Entity (SME)..... | 21 | +| 7.32 | Visitor Location Register (VLR)..... | 21 | +| 7.33 | Voice Message Centre (VMS)..... | 21 | +| 7.34 | Wireless Network Entity (WNE)..... | 21 | +| 7.35 | Access Gateway (AGW) ..... | 21 | +| 7.36 | Access Terminal (AT) ..... | 21 | +| 7.37 | Application Server..... | 21 | +| 7.38 | Authentication, Authorization and Accounting (AAA) ..... | 21 | +| 7.39 | Border Router (BR) ..... | 22 | +| 7.40 | Breakout Gateway Control Function (BGCF)..... | 22 | +| 7.41 | Call Session Control Function (CSCF) ..... | 22 | +| 7.42 | Databases (DB)..... | 22 | +| 7.43 | evolved Base Station (eBS) ..... | 22 | +| 7.44 | IP Multimedia Client ..... | 22 | +| 7.45 | IP Network..... | 22 | +| 7.46 | Local Mobility Anchor (LMA) ..... | 22 | +| 7.47 | Media Gateway (MGW)..... | 22 | +| 7.48 | Media Gateway Control Function (MGCF) ..... | 23 | +| 7.49 | Media Resource Function Controller (MRFC)..... | 23 | +| 7.50 | Media Resource Function Processor (MRFP)..... | 23 | +| 7.51 | Mobile IP Home Agent (HA) ..... | 23 | +| 7.52 | Mobile Station (MS)..... | 23 | +| 7.53 | non-3GPP2 System..... | 23 | +| 7.54 | OSA Service Capability Server (OSA-SCS)..... | 23 | +| 7.55 | Policy Decision Function (PDF) ..... | 24 | +| 7.56 | Position Determining Entity (PDE)..... | 24 | +| 7.57 | Position Server..... | 24 | +| 7.58 | Public Switched Telephone Network (PSTN)..... | 24 | +| 7.59 | Proxy Mobile Agent (PMA) or Mobile Access Gateway (MAG) ..... | 24 | +| 7.60 | Policy and Charging Rules Function (PCRF) ..... | 24 | +| 7.61 | Session Reference Network Controller (SRNC) ..... | 24 | +| 8 | Reference Points ..... | 24 | +| 8.1 | Reference Point B..... | 24 | +| 8.2 | Reference Point C..... | 24 | +| 8.3 | Reference Point D..... | 24 | +| 8.4 | Reference Point d ..... | 24 | +| 8.5 | Reference Point D 1 ..... | 25 | +| 8.6 | Reference Point D i ..... | 25 | +| 8.7 | Reference Point E ..... | 25 | +| 8.8 | Reference Point E 3 ..... | 25 | + +| | Page | +|--------------------------------------------|------| +| 8.9 Reference Point E 5 ..... | 25 | +| 8.10 Reference Point E 9 ..... | 25 | +| 8.11 Reference Point E 11 ..... | 25 | +| 8.12 Reference Point E 12 ..... | 25 | +| 8.13 Reference Point e..... | 25 | +| 8.14 Reference Point F ..... | 25 | +| 8.15 Reference Point G..... | 25 | +| 8.16 Reference Point H..... | 25 | +| 8.17 Reference Point I ..... | 25 | +| 8.18 Reference Point J..... | 25 | +| 8.19 Reference Point K..... | 26 | +| 8.20 Reference Point L ..... | 26 | +| 8.21 Reference Point M 1 ..... | 26 | +| 8.22 Reference Point M 2 ..... | 26 | +| 8.23 Reference Point M 3 ..... | 26 | +| 8.24 Reference Point N..... | 26 | +| 8.25 Reference Point N 1 ..... | 26 | +| 8.26 Reference Point O 1 ..... | 26 | +| 8.27 Reference Point O 2 ..... | 26 | +| 8.28 Reference Point P i ..... | 26 | +| 8.29 Reference Point Q..... | 26 | +| 8.30 Reference Point Q 1 ..... | 26 | +| 8.31 Reference Point T 1 ..... | 26 | +| 8.32 Reference Point T 2 ..... | 26 | +| 8.33 Reference Point T 3 ..... | 27 | +| 8.34 Reference Point T 4 ..... | 27 | +| 8.35 Reference Point T 5 ..... | 27 | +| 8.36 Reference Point T 6 ..... | 27 | +| 8.37 Reference Point T 7 ..... | 27 | +| 8.38 Reference Point T 8 ..... | 27 | +| 8.39 Reference Point T 9 ..... | 27 | +| 8.40 Reference Point V..... | 27 | +| 8.41 Reference Point X..... | 27 | +| 8.42 Reference Point Y..... | 27 | +| 8.43 Reference Point Z..... | 27 | +| 8.44 Reference Point Z 1 ..... | 27 | +| 8.45 Reference Point Z 2 ..... | 27 | +| 8.46 Reference Point Z 3 ..... | 27 | +| 8.47 Reference Point 1 ..... | 28 | +| 8.48 Reference Point 2 ..... | 28 | + +| | Page | +|-----------------------------------|------| +| 8.49 Reference Point 3 ..... | 28 | +| 8.50 Reference Point 4 ..... | 28 | +| 8.51 Reference Point 5/Mk..... | 28 | +| 8.52 Reference Point 6 ..... | 28 | +| 8.53 Reference Point 7 ..... | 28 | +| 8.54 Reference Point 8/OSA ..... | 28 | +| 8.55 Reference Point 9/Mi..... | 28 | +| 8.56 Reference Point 10 ..... | 28 | +| 8.57 Reference Point 11/Sh ..... | 28 | +| 8.58 Reference Point 12/ISC ..... | 29 | +| 8.59 Reference Point 13 ..... | 29 | +| 8.60 Reference Point 14 ..... | 29 | +| 8.61 Reference Point 15 ..... | 29 | +| 8.62 Reference Point 16/Cx..... | 29 | +| 8.63 Reference Point 17/Mg..... | 29 | +| 8.64 Reference Point 18 ..... | 29 | +| 8.65 Reference Point 19 ..... | 29 | +| 8.66 Reference Point 20 ..... | 29 | +| 8.67 Reference Point 21 ..... | 29 | +| 8.68 Reference Point 22 ..... | 29 | +| 8.69 Reference Point 23 ..... | 29 | +| 8.70 Reference Point 24/Mr ..... | 30 | +| 8.71 Reference Point 25/Mp..... | 30 | +| 8.72 Reference Point 26/PSTN..... | 30 | +| 8.73 Reference Point 27 ..... | 30 | +| 8.74 Reference Point 28/Go ..... | 30 | +| 8.75 Reference Point 29 ..... | 30 | +| 8.76 Reference Point 30/Mc ..... | 30 | +| 8.77 Reference Point 31 ..... | 30 | +| 8.78 Reference Point 32/Mb..... | 30 | +| 8.79 Reference Point 33/Mb..... | 30 | +| 8.80 Reference Point 34/Mb..... | 30 | +| 8.81 Reference Point 35 ..... | 30 | +| 8.82 Reference Point 36/Mb..... | 31 | +| 8.83 Reference Point 37/Mb..... | 31 | +| 8.84 Reference Point 38/Mb..... | 31 | +| 8.85 Reference Point 39 ..... | 31 | +| 8.86 Reference Point 40/Mb..... | 31 | +| 8.87 Reference Point 41 ..... | 31 | +| 8.88 Reference Point 42/Mb..... | 31 | + +| | | | +|-------|-----------------------------------------|----| +| 8.89 | Reference Point 43/Mb..... | 31 | +| 8.90 | Reference Point 44/Mb..... | 31 | +| 8.91 | Reference Point 45/Mb..... | 31 | +| 8.92 | Reference Point 46/Mb..... | 31 | +| 8.93 | Reference Point 47 ..... | 31 | +| 8.94 | Reference Point 48 ..... | 32 | +| 8.95 | Reference Point 49/(Mj)..... | 32 | +| 8.96 | Reference Point 50 ..... | 32 | +| 8.97 | Reference Point U1..... | 32 | +| 8.98 | Reference Point U2..... | 32 | +| 8.99 | Reference Point U3..... | 32 | +| 8.100 | Reference Point U4..... | 32 | +| 8.101 | Reference Point U6..... | 32 | +| 8.102 | Reference Point U14..... | 32 | +| 8.103 | Reference Point U15..... | 32 | +| 8.104 | Reference Point U15'..... | 32 | +| 8.105 | Reference Point U16..... | 32 | +| 8.106 | Reference Point U17..... | 33 | +| 8.107 | Reference Point U18..... | 33 | +| 8.108 | Reference Point U19..... | 33 | +| 8.109 | Reference Point U20..... | 33 | +| 8.110 | Reference Point U21..... | 33 | +| 8.111 | Reference Point U22..... | 33 | +| 8.112 | Reference Point U23..... | 33 | +| 8.113 | Reference Point U24..... | 33 | +| 8.114 | Reference Point U25..... | 33 | +| 8.115 | Reference Point U26..... | 34 | +| 8.116 | Reference Point U27..... | 34 | +| 8.117 | Reference Point U28..... | 34 | +| 8.118 | Reference Point U29..... | 34 | +| 8.119 | Reference Point U30..... | 34 | +| 8.120 | Reference Point U31..... | 34 | +| 8.121 | Reference Point U32..... | 34 | +| 8.122 | Reference Point UMB-AI..... | 34 | +| 9 | Technical specifications structure..... | 34 | + +| | Page | +|-------------------------------------------------------|------| +| 10 Technical Specifications..... | 35 | +| 10.1 A Series RAN Specifications ..... | 35 | +| 10.2 Intersystem Specifications..... | 35 | +| 10.3 Packet Data Specifications ..... | 46 | +| 10.4 Services and system aspects specifications ..... | 46 | +| 10.5 Core Network Specifications..... | 113 | + +# **Recommendation ITU-T Q.1742.7** + +## **IMT-2000 References (approved as of 30 June 2008) to ANSI-41 evolved Core Network with cdma2000 Access Network** + +## **1 Scope** + +This Recommendation identifies the IMT-2000 Family Member; "ANSI-41 evolved Core Network with cdma2000 Access Network." This set of referenced specifications includes those 3GPP2 specifications that were approved as of 30 June 2008. + +The Core Network interfaces identified in this Recommendation and the radio interfaces and radio access network interfaces identified in Recommendation ITU-R M.1457 [1] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 Family Member. + +It is the intent of the ITU-T that the references in this Recommendation are only to specifications that specify the network aspects of this IMT-2000 family member. In the event that a referenced specification also includes material that specifies any of the radio aspects of this IMT-2000 family member, Recommendation ITU-R M.1457 [1], shall take precedence. + +NOTE – The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T Recommendations has not been applied. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] Recommendation ITU-R M.1457 (2001): Detailed specifications of the radio interfaces of international mobile telecommunications-2000 (IMT-2000) +- [2] ANSI; TIA/EIA 41D (1997): Cellular Radiotelecommunications Intersystem Operations (ANSI/TIA/EIA-41-D-97) +- [3] ANSI; TIA/EIA 95 (1999): Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems (ANSI/TIA/EIA-95-B-99) +- [4] ANSI; TIA/EIA 124 (2001): Wireless Radio Telecommunications Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (ANSI/124-D-2001) +- [5] ANSI; TIA/EIA 136 (2001): TDMA Cellular PCS (ANSI/TIA/EIA-136, Rev C-2001) +- [6] ANSI; TIA/EIA 553A (1999): Mobile Station – Base Station Compatibility Standard (ANSI TIA/EIA-553-A-99) +- [7] ANSI; TIA/EIA 664A (2000): Cellular Features Description (ANSI/TIA/EIA-664-A-2000) +- [8] TIA Specification IS-91 (1999): Base Station – Mobile Station Compatibility Specification for 800 MHz Cellular, Auxiliary, and Residential Services (TIA/EIA/IS-91-A) +- [9] TIA Specification IS-2000 (2000): CDMA 2000 Series (TIA/EIA/IS-2000 Series Revision A) + +- [10] TIA Specification IS-2001-A (2001): Interoperability Specifications (IOS) for cdma2000 Access Network Interfaces (TIA/EIA/IS-2001-A) +- [11] TIA Specification TSB-29D (2000): International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41 +- [12a] CWTS; CWTS-MC-S.R0005-B (2002): Network Reference Model for cdma2000 Spread Spectrum Systems +- [12b] TIA; TSB100-A (2001): Wireless Network Reference Model +- [12c] TTA; TTAE.3G-S.R0005-B (2001): 3GPP2 Network Reference Model for cdma2000 Spread Spectrum Systems +- [12d] TTC; TS-3GB-S.R0005-Bv1.0 (2001): Network Reference Model for cdma2000 Spread Spectrum Systems +- [13a] CWTS; CWTS-MC-N.S0037 (2002) IP Network Architecture Model for cdma2000 Spread Spectrum Systems +- [13b] TTA; TTAT.3G-S.R0037-0v2.0 (2003) IP Network Architecture Model for cdma2000 Spread Spectrum Systems +- [13c] TTC; TS-3GB-S.R0037-0v2.0 (2002) IP Network Architecture Model for cdma2000 Spread Spectrum Systems +- [14] TIA/EIA TSB29-E (2002) International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41 +- [15] TIA/EIA/IS-826 (2003) TIA/EIA-41-D Based Pre-Paid Charging Enhancements for Circuit Switched Data and Short Message (2003) + +## 3 Definitions + +This Recommendation defines the following terms: + +**Active:** The MS is available for call delivery. This state is maintained by the MSC, the VLR and the HLR. (See also Available, Inactive and Unavailable.) + +**Access Denial Call Treatment:** A tone, announcement, or call redirection applied as appropriate. + +**Access Network:** Network that connects access technologies (such as a Radio Access Network) to the core network. + +**Adjunct MSC:** A Mobile Switching Centre (MSC) that is providing adjunct services such as voice response, voice recognition, DTMF tone detection, voice message storage, etc. + +**Anchor MSC:** The Mobile Switching Centre (MSC), that is the first to assign a traffic channel to a call on origination or termination is called the Anchor MSC. For the duration of this call, this MSC shall be the anchor (fixed) point in the event that the Mobile Station (MS) should be handed off to other MSCs. + +**Authentication:** The act of verifying the identity of an entity (e.g., a user, device). + +**Available:** The MS can accept a call delivery (i.e., the MS is in a known location and it is in a state able to accept call deliveries). The availability of a MS to accept a call delivery is maintained only by the MSC. (See also Active, Inactive and Unavailable.) + +**Base Transceiver Station:** A piece of radio access network equipment that contains the radios and serves a geographic area. + +**Call Delivery:** The process by which calls directed to the cellular subscriber are delivered to the subscriber while roaming in a visited system. + +**Call Delivery Method:** Method by which a call is delivered to a subscriber in MSC-V. + +**Call Disconnect:** The process of requesting the release of a connection between two or more network addresses. + +**Call Release:** The process of relinquishing the facilities and circuits used for a call. + +**Call Termination:** The process of connecting a subscriber to an incoming call. + +**Candidate MSC:** This term is used during the handoff measurement request by the current serving MSC to reference the MSC that is being requested to provide its best CELL ID and SIGNAL QUALITY values. + +**Cell Site:** The physical location of a cell's radio equipment and supporting systems. This term is also used to refer to the equipment located at the cell site. + +**Clearinghouse:** A service used for the exchange and management of information. + +**Data Communications:** The digital transmission of information (other than voice). + +**Dialogue:** A user interaction sequence composed of tones and announcements that may gather information. + +**Gateway MSC:** See MSC-G. + +**Home System:** The system which is transmitting the System Identifier (SID) (refer to *EIA/TIA-553*) which is recognized by the MS as the "Home" SID. + +**Inactive:** The MS is not available for call delivery. The MS may not be registered. The MS may be registered, but is out of radio contact (e.g., missing autonomous registrations) or is intentionally inaccessible for periods of time (e.g., slotted mode, paging frame class, or sleep mode). An inactive MS may accept SMS message deliveries. This state is maintained by the MSC, the VLR and the HLR. (See also Active, Available, and Unavailable.) + +**Market Identification (MarketID):** A unique market identifier that is specified by the service provider (e.g., FCC assigned SID, CIBERNET assigned BID – see *TIA/EIA TSB29*). + +**Mobile Assisted Handoff (MAHO):** A process where handoff measurements are done by the MS under the control of the MSC and Base Station. The MSC and Base Station retain the control over when the handoff actually occurs. + +**Mobility:** The ability to access services from any point in the network. The degree of service availability may depend on the access network capabilities, as well as any service level agreements between the user's home network and the visited network. Types of mobility include personal mobility, service mobility, and terminal mobility. + +**Mobility Management:** The set of functions used to manage a mobile user accessing a network other than that user's home network. These functions include communication with the home network for purposes of authentication, authorization, location updating and download of user information. + +**MSC-G:** An MSC that is capable of the Intersystem procedures, defined in this Recommendation, between entities in the network reference model so as to provide service. + +**MSC-H:** The "home" MSC of an MS which is broadcasting the SID that is recorded in the MS's Security and Identification memory, and to which the MS's Directory Number is assigned. + +**MSC-V:** A "visited" MSC in whose service area a roamer is operating. + +**Network Reference Model:** The functional entities and the associated interface reference points that may logically comprise a cellular network. (See clause 6.) + +**Number Portability:** A mechanism that allows a user to retain the same directory number, regardless of the subscribed-to service provider. Number portability may be limited to specific + +geographical areas. In the context of the All-IP network, the term "number portability" refers specifically to ITU-T E.164 numbers used for telephony. + +**Originating MSC:** The MSC-H or MSC-G that initiates the call delivery procedures defined in this Recommendation. + +**Originating SMS supplementary service:** Services or features that affect SMS message originations and are requested on a per message basis as supported by a particular teleservice, for example, delayed delivery, or message distribution to a list of destinations. + +**Personal Mobility:** The ability of users to change their association with one or more terminals at any point and time. The user should continue to receive subscribed and otherwise authorized services as supported by the current MS and access network. + +**Personalized Services:** Services that need access to the subscriber profile and/or are dependent on the overall call/session state (of the user) for reasons of service interaction. An example: a call termination service such as TTA/EIA-41's "Call Forward on Busy". + +**Protocol Extension:** A mechanism provided to allow systems with a common bilateral agreement to extend the *TTA/EIA-41* protocol. There is a range of reserved Error Codes, Operation Codes, Parameter Identifiers (in addition to PRIVATE Parameter Identifiers), and ranges of values in enumerated parameter types and data fields. The only mechanism to resolve conflicting uses of protocol extension is to standardize their usage. The Protocol Extension mechanism is used at the risk of the implementation. Protocol Extensions should not be used unless the message recipient is known to support them. + +**Radio Access Network:** The network that connects radio base stations to the core network. The RAN provides and maintains radio-specific functions, which may be unique to a given radio access technology, that allow users to access the core network. + +**Registered:** The HLR has a pointer to a system serving an MS. A registered MS may be active or inactive. + +**Registration:** The procedure by which a MS becomes listed as being present in the service area of an MSC. + +**Remote Feature Control Port (RFC Port):** A terminating directory number supporting service profile modification. + +**Roamer Port:** A terminating directory number supporting call delivery to mobile stations. + +**Roamer Service Profile:** The specific set of features, capabilities and/or operating restrictions, other than financial accountability, associated with the subscriber. + +**Roamer Validation:** That aspect of roamer service qualification dealing with financial accountability. Also, the general procedure by which a roamer's financial accountability is established. + +**Roaming:** Action whereby users access services while outside of their subscribed home network. + +**Service Qualification:** The service capabilities, features and privileges to which an MS is entitled. Also, the general procedure by which such service capabilities, features, and privileges become established in an MSC. + +**Serving MSC:** The MSC which currently has the MS obtaining service at one of its cell sites within its coverage area. + +**Signaling:** The information exchanged between the mobile station and the network, or within the network, for the purposes of service provision (e.g., connection establishment). + +**Switch Number (SWNO):** A number uniquely identifying a particular switch (i.e., a group of cell sites and the associated switch resources) within a group of switches associated with a common MarketID. + +**Target MSC:** The MSC which was selected from the candidate list as having the cell site with the best signal quality value for the MS during the location request function. + +**Temporary Local Directory Number (TLDN):** A network address temporarily assigned for call setup. + +**Terminating SMS supplementary service:** Services or features that affect SMS message terminations, for example, screening, forwarding, delivery to an MS, delayed delivery while roaming, or distribution to a group based upon a destination address. + +**Termination Address:** One or more digits, as determined by the Home System, which identify the Terminating Party. This could include Speed Call Codes (when supported by the Home Service Provider), other Mobile Telephone Numbers or any valid World Telephone Number. + +**Traffic:** Information generated by the subscriber that is transported on the network (i.e., user voice or data). + +**Unavailable:** The MS cannot accept a normal call delivery (i.e., the MS is in an unknown location or it is in a state unable to accept call deliveries). The availability of an MS to accept a call delivery is maintained only by the MSC. (See also Active, Available, and Inactive.) + +**Unregistered:** A state where the MS is unavailable for any type of termination event and the HLR pointer is not directed to any visited system. + +**Visited Network:** The visited network is a carrier's network where a subscriber currently is roaming. The term visited network is more business significant, than geographically significant. + +**Visited System:** From the MS's perspective, a system which is transmitting a SID which is not recognized by the MS as the "Home" SID. From a network perspective, the system in which an MS is currently registered. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------| +| $\mu$ | Microsecond ( $10^{-6}$ second) | +| 3G | Third Generation | +| 3GPP2 | Third Generation Partnership Project (ANSI driven) | +| AAA | Authentication, Authorization, and Accounting | +| AC | Authentication Centre | +| ADDS | Application Data Delivery Service | +| ADPCM | Adaptive Differential Pulse Code Modulation | +| ADS | Asynchronous Data Service | +| AGW | Access GateWay | +| AH | Answer Hold | +| AMPS | Advanced Mobile Phone System | +| ANSI | American National Standards Institute | +| AOC | Advice of Charge | + +| | | +|-------|--------------------------------------------------------| +| API | Application Programming Interface | +| ARIB | Association of Radio Industries and Businesses (Japan) | +| AS | Application Server | +| BCMCS | Broadcast-Multicast Services | +| BCSMs | Basic Call State Models | +| BS | Base Station | +| BSC | Base Station Controller | +| BTS | Basic Transceiver System | +| CAN | Converged Access Network | +| CCF | Call Control Function | +| CDCP | Call Data Collection Point | +| CDGP | Call Data Generation Point | +| CDIS | Call Data Information Source | +| CDMA | Code Division Multiple Access | +| CDRP | Call Data Rating Point | +| CMIP | Client Mobile IP | +| CN | Core Network | +| CNAP | Calling Name Presentation | +| CNAR | Calling Name Restriction | +| CNIP | Calling Number Identification Presentation | +| CSC | Customer Service Centre | +| CSCF | Call Session Control Functions | +| CWTS | China Wireless Telecommunication Standard Group | +| DCCH | Dedicated Control Channel | +| DFP | Distributed Functional Plane | +| DMH | Data Message Handler | +| DP | Detection Point | +| DP | Data Privacy | +| DSA | Data Subscriber Authentication | +| DTMF | Dual Tone Multi-Frequency | +| E2E | End-to-End | +| eBS | evolved Base Station | +| EIA | Electronics Industry Association | +| EIR | Equipment Identity Register | +| EMS | Enhanced Message Service | +| ESN | Electronic Serial Number | +| ESP | Encapsulating Security Payload | + +| | | +|----------|------------------------------------------------------------------------------| +| FCC | Federal Communications Commission | +| FFMA | File Format for Multimedia Services | +| FPH | FreePhone | +| FPLMTS | Future Public Land Mobile Telecommunications Systems – now IMT-2000 | +| GECO | Global ECO (Emergency Call Origination) | +| GSM | Formerly: Group Special Mobile, Now: Global System For Mobile Communications | +| HA | Home Agent | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| IM | IP Multimedia Call Model | +| IMS | IP Multimedia core network Subsystem | +| IMSI | International Mobile Subscriber Identity | +| IMT | International Mobile Telecommunications | +| IMT-2000 | International Mobile Telecommunications – 2000 | +| IOTA | IP Over-the-Air | +| IOTA HCM | Internet based Over-the-Air Handset Configuration Management | +| IP | Internet Protocol | +| IP | Intelligent Peripheral | +| IPE | In Path Equipment | +| IS | Interim Standard | +| ISDN | Integrated Services Digital Network | +| ISIM | IP multimedia Services Identity Module | +| ISLP | InterSystem Link Protocol | +| IWF | InterWorking Function | +| LBSS | Location Based Services System | +| LMA | Local Mobility Agent | +| LMSD | Legacy Mobile Station Domain | +| MAP | Mobile Application Part | +| MC | Multi-Carrier | +| MC | Message Centre | +| MDN | Mobile Directory Number | +| MEID | Mobile Equipment Identifier | +| MGW | Media Gateway | +| MHz | Megahertz ( $10^6$ Hertz) | +| MM | Multimedia Message | +| MMS | Multimedia Messaging Service | + +| | | +|--------|----------------------------------------------------------| +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MSID | Mobile Station Identifier | +| NAM | Number Assignment Module | +| NAMPS | Narrowband Advanced Mobile Phone Service | +| NDSS | Network Directed System Selection | +| NRM | Network Reference Model | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OSA | Open Service Access | +| OTAF | Over the-Air Function | +| OTAPA | Over-the-Air Parameter Administration | +| OTASP | Over-the-Air Service Provisioning | +| PCF | Packet Control Function | +| PCS | Personal Communications Service | +| PCS | Personal Communications System | +| PDE | Positioning Determining Entity | +| PDS | Packet Data Surveillance | +| PDSN | Packet Data Serving Node | +| PL | Preferred Language | +| PMIP | Proxy Mobile IP | +| PN | Project Number | +| PPC | Pre-Paid Charging | +| PPP | Point-to-Point Protocol | +| PRC | Premium Rate Charging | +| RAN | Radio Access Network | +| RUAC | Rejection of Undesired Annoying Calls | +| R-UIIM | Removable User Identity Module | +| SC | Subscriber Confidentially | +| SCF | Selective Call Forwarding | +| SCF | Session Control Function | +| SCP | Service Control Point | +| SCS | Service Capability Server | +| SDO | Standards Development Organization | +| SDP | Session Description Protocol | +| SID | System Identifier | +| SIP | Session Initiation Protocol | +| SME | Short Message Entity | + +| | | +|------|---------------------------------------------------| +| SMS | Service Management System | +| SMS | Short Message Service | +| SMTP | Simple Mail Transfer Protocol | +| SN | Service Node | +| SRG | System Release Guide | +| SRNC | Session Reference Network Controller | +| SS7 | Signaling System 7 | +| SSF | Service Switching Function | +| SSG | Special Study Group | +| TFO | Tandem Free Operation | +| TrFO | Transcoder Free Operation | +| TIA | Telecommunications Industry Association | +| TMSI | Temporary Mobile Station Identification | +| TRAU | Transcoder and Rate Adaptor Unit | +| TSB | Telecommunications Systems Bulletin | +| TTA | Telecommunications Technology Association (Korea) | +| TTC | Telecommunication Technology Committee (Japan) | +| UICC | Universal Integrated Circuit Card | +| UIM | User Identity Module | +| UMB | Ultra Mobile Broadband | +| USCF | User Selective Call Forwarding | +| VASP | Value-Added Service Provider | +| VLR | Visitor Location Register | +| WIN | Wireless Intelligent Network | +| WLL | Wireless Local Loop | +| WNP | Wireless Number Portability | + +## 5 Introduction + +The Core Network for cdma2000 is based on an evolved ANSI-41 2nd generation mobile system. The core network technical specifications have been developed in a third generation partnership project (approved in 3GPP2 as of 30 June 2008) and transposed to the involved regional Standards Development Organizations (SDOs). The system will support different applications ranging from narrow-band to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements. + +The Core Network interfaces identified in this Recommendation and the radio interfaces and radio access network interfaces identified in Recommendation ITU-R M.1457 [1] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 Family Member. + +The descriptions in clauses 6, 7, and 8 and the descriptions of the Technical Specifications listed in clause 10 are for informative purposes only. Normative information is in the tables for the respective specification. + +## **6 Basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member** + +The basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member includes a circuit-based and packet-based core network and an all-IP multimedia domain. + +The following text is based on reference [12 a-d] clause 2.1. + +Figure 6-1 presents the network entities and associated reference points that comprise the ANSI-41 evolved Core Network with cdma2000 Access Network. The network entities are represented by squares, triangles and rounded corner rectangles; circles represent the reference points. The network reference model in this Recommendation is the compilation of several reference models currently in use. + +- The network reference model is a functional block diagram. +- A network entity represents a group of functions, not a physical device. For example, a Mobile Switching Centre (MSC) is a physical device; it comprises frames, shelves, circuit packs, etc. The physical device may comprise a single network entity such as the MSC, or it may comprise some combination such as the MSC, the Visitor Location Register (VLR), the Home Location Register (HLR), and the Authentication Centre (AC). The physical realization is an implementation issue; a manufacturer may choose any physical implementation of network entities, either individually or in combination, as long as the implementation meets the functional requirements. Sometimes, for practical reasons, the functional network entity is a physical device. The Mobile Station (MS) is an excellent example. +- A reference point is a conceptual point that divides two groups of functions. It is not necessarily a physical interface. A reference point only becomes a physical interface when the network entities on either side of it are contained in different physical devices. +- A "Collective Entity" contains encompassed network entities that are an instance of the collective. +- A "Composite Entity" contains encompassed network entities that are part of the composite. + +![Figure 6-1: ANSI-41 evolved Core Network with cdma2000 Access Network Reference Model. The diagram shows a complex network architecture with various entities and interfaces. On the left, a Mobile Station (MS) contains a Mobile Equipment (ME) with MT0, MT1, and MT2, and a UIM. The ME connects to the network via interfaces TE1, TE2, and Rm. The MS also connects to a Vehicle via interface Uv. The network itself is divided into several functional blocks: a Core Network (dashed box) containing IP, SCP, SN, NPDB, LPDE, VMS, EIR, BS (BTS and BSC), MSC, MC, HLR, VLR, PCF, SME, AC, OTAF, PDSN, AAA, HA, MPC, PDE, and WNE; an All-IP Multimedia Domain (MMD) containing CDIS, IAP, CDGP, CDCP, DF, CF, and CRDB; and various external interfaces including PSTN (W, DCE, Rv, TE2), PDN (Rv, TE2), ISDN (S, TE1), CSC, TA (R, TE2), IWF, and ESME. Reference points are labeled with letters (A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, X, Y, Z) and subscripts (1-12). A 'Key' at the bottom left defines the symbols for Specific Network Entity, Composite Entity, Collective Entity, Interface Reference Point, Interface to another instance of same network entity, and Line intersection.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 6-1: ANSI-41 evolved Core Network with cdma2000 Access Network Reference Model. The diagram shows a complex network architecture with various entities and interfaces. On the left, a Mobile Station (MS) contains a Mobile Equipment (ME) with MT0, MT1, and MT2, and a UIM. The ME connects to the network via interfaces TE1, TE2, and Rm. The MS also connects to a Vehicle via interface Uv. The network itself is divided into several functional blocks: a Core Network (dashed box) containing IP, SCP, SN, NPDB, LPDE, VMS, EIR, BS (BTS and BSC), MSC, MC, HLR, VLR, PCF, SME, AC, OTAF, PDSN, AAA, HA, MPC, PDE, and WNE; an All-IP Multimedia Domain (MMD) containing CDIS, IAP, CDGP, CDCP, DF, CF, and CRDB; and various external interfaces including PSTN (W, DCE, Rv, TE2), PDN (Rv, TE2), ISDN (S, TE1), CSC, TA (R, TE2), IWF, and ESME. Reference points are labeled with letters (A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, X, Y, Z) and subscripts (1-12). A 'Key' at the bottom left defines the symbols for Specific Network Entity, Composite Entity, Collective Entity, Interface Reference Point, Interface to another instance of same network entity, and Line intersection. + +Q.1742.7(08)\_F6-1 + +**Figure 6-1 – ANSI-41 evolved Core Network with cdma2000 Access Network Reference Model** + +The basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member also includes an all-IP multimedia domain. The following text is based on reference [13 a-c] clause 2.1. + +**All-IP MMD Core Network Architecture:** + +Figure 6-2 presents the core network entities and associated reference points that comprise the MMD (Multimedia Domain) of the wireless All-IP Network Architecture Model. The network + +entities are represented by squares and rectangles; the interfaces between network entities are reference points identified by numbers. Figure 6-2 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE 1 – In Figure 6-2, the network elements and reference points highlighted in "blue" identify the "IP MMD Core Network". + +![Figure 6-2 – ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model. The diagram shows a complex network architecture with various entities and interfaces. Entities include Databases (EIR, DST, Subscription Profile, Network policy rules, ...), OSA Application server, SIP Application server, Position server, AAA, Call session control function, Breakout gateway control function, Policy decision function, Position determining entity, Media resource function controller, Media gateway control function, cdma2000 access network (BTS, BSC/RNC + PCF, MM), Other access networks, Mobile station, Access gateway, FA / Attendant, Media resource function processor, Mobile IP home agent, Media gateway, Border router, PSTN, and IP Network. Interfaces are labeled with numbers and letters (e.g., 11/Sh, 12/ISC, 16/Cx, 24/Mr, 25/Mp, 32/Mb, 33/Mb, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh, 8/OSA, 12/ISC, 5/Mk, 9/Mi, 49/Mj, 17/Mg, 28/Go, 26/PSTN, 30/Mc).](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +The diagram illustrates the ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model. It shows the following components and interfaces: + +- Databases:** EIR, DST, Subscription Profile, Network policy rules, ... (Interfaces: 11, 2, 3, 4, 7) +- OSA Application server** (Interface: 8/OSA) +- SIP Application server** (Interfaces: 12/ISC, 5/Mk) +- OSA Service capability server** (Interfaces: 10, 11/Sh, 12/ISC) +- Breakout gateway control function** (Interfaces: 9/Mi, 49/Mj) +- Position server** (Interfaces: 15, 18, 19, 20) +- AAA** (Interfaces: 16/Cx, 21, 22) +- Call session control function** (Interfaces: 23, 24/Mr, 17/Mg) +- Policy decision function** (Interfaces: 28/Go, 29) +- Position determining entity** (Interface: 18) +- Media resource function controller** (Interface: 25/Mp) +- Media gateway control function** (Interface: 26/PSTN) +- cdma2000 access network:** + - BTS (Interface: 31) + - BSC/RNC + PCF (Interfaces: 31, 35) + - MM (Interface: 35) +- Other access networks** (Interface: 35) +- Mobile station** (Interface: 47) +- Access gateway** (Interface: 31) +- FA / Attendant** (Interfaces: 32/Mb, 33/Mb, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, hh) +- Media resource function processor** (Interfaces: 32/Mb, 33/Mb, 36/Mb, 37/Mb) +- Mobile IP home agent** (Interfaces: 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb) +- Media gateway** (Interfaces: 26/PSTN, 30/Mc, 38/Mb, 40/Mb) +- Border router** (Interfaces: 46/Mb, 34/Mb) +- PSTN** (Interface: 26/PSTN) +- IP Network** (Interface: 46/Mb) + +Figure 6-2 – ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model. The diagram shows a complex network architecture with various entities and interfaces. Entities include Databases (EIR, DST, Subscription Profile, Network policy rules, ...), OSA Application server, SIP Application server, Position server, AAA, Call session control function, Breakout gateway control function, Policy decision function, Position determining entity, Media resource function controller, Media gateway control function, cdma2000 access network (BTS, BSC/RNC + PCF, MM), Other access networks, Mobile station, Access gateway, FA / Attendant, Media resource function processor, Mobile IP home agent, Media gateway, Border router, PSTN, and IP Network. Interfaces are labeled with numbers and letters (e.g., 11/Sh, 12/ISC, 16/Cx, 24/Mr, 25/Mp, 32/Mb, 33/Mb, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh, 8/OSA, 12/ISC, 5/Mk, 9/Mi, 49/Mj, 17/Mg, 28/Go, 26/PSTN, 30/Mc). + +Q.1742.7(08)\_F6-2 + +**Figure 6-2 – ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model** + +The MMD of the All-IP Network offers both general packet data support and multi-media session capabilities. The multi-media session capabilities are built on top of the general packet data support capabilities. The general packet data capabilities may be deployed without the multi-media session capabilities. Some network entities are common to providing both capabilities. + +Figure 6-3 shows the entities that comprise the general packet data support portion of the MMD core network. These are known collectively as the Packet Data Subsystem (PDS). Figure 6-3 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE 2 – In Figure 6-3, the network elements and reference points highlighted in "blue" identify the "Packet Data Subsystem". + +![Figure 6-3: ANSI-41 evolved Core Network with cdma2000 Access Network Packet Data Subsystem Core Network Architecture Model. The diagram illustrates a complex network architecture with various functional entities and reference points. Key components include: +- Databases: EIR, DSI, Subscription Profile, Network Policy Rules, etc. (enclosed in a dashed blue box). +- Application Servers: Application server, SIP Application server, OSA Service capability server. +- Control Functions: Call session control function, Policy decision function (blue), Breakout gateway control function. +- Media Entities: Media resource function controller, Media resource function processor, Media gateway control function, Media gateway. +- Core Network Elements: AAA (blue), Access gateway (blue), FA / Attendant (blue), Mobile IP home agent (blue), Border router (blue), Position server, Position determining entity. +- Access Networks: cdma2000 access network (containing BTS, BSC/RNC + PCF, MM), Other access networks. +- External Networks: PSTN, IP network. +- Mobile Station: Connected via reference point 47. +Reference points are numbered 1 through 50, some with alphanumeric labels like 11/Sh, 12/ISC, 16/Cx, 17/Mg, 24/Mr, 28/Go, 30/Mc, 32/Mb, etc. Blue lines and boxes indicate the IP Multimedia Session Subsystem (IMS) components.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Figure 6-3: ANSI-41 evolved Core Network with cdma2000 Access Network Packet Data Subsystem Core Network Architecture Model. The diagram illustrates a complex network architecture with various functional entities and reference points. Key components include: +- Databases: EIR, DSI, Subscription Profile, Network Policy Rules, etc. (enclosed in a dashed blue box). +- Application Servers: Application server, SIP Application server, OSA Service capability server. +- Control Functions: Call session control function, Policy decision function (blue), Breakout gateway control function. +- Media Entities: Media resource function controller, Media resource function processor, Media gateway control function, Media gateway. +- Core Network Elements: AAA (blue), Access gateway (blue), FA / Attendant (blue), Mobile IP home agent (blue), Border router (blue), Position server, Position determining entity. +- Access Networks: cdma2000 access network (containing BTS, BSC/RNC + PCF, MM), Other access networks. +- External Networks: PSTN, IP network. +- Mobile Station: Connected via reference point 47. +Reference points are numbered 1 through 50, some with alphanumeric labels like 11/Sh, 12/ISC, 16/Cx, 17/Mg, 24/Mr, 28/Go, 30/Mc, 32/Mb, etc. Blue lines and boxes indicate the IP Multimedia Session Subsystem (IMS) components. + +**Figure 6-3 – ANSI-41 evolved Core Network with cdma2000 Access Network +Packet Data Subsystem Core Network Architecture Model** + +Figure 6-4 shows the entities that comprise the multimedia session capabilities of an All-IP network. These entities are known collectively as the IP Multimedia Session Subsystem (IMS). Figure 6-4 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE 3 – In Figure 6-4, the "IP Multimedia Session Subsystem" is identified by the network elements and reference points highlighted in "blue". + +![Figure 6-4: ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem Core Network Architecture Model. This is a complex architectural diagram showing the interconnections between various network elements. At the top, a 'Databases' box contains EIR, DSI, Subscription Profile, Network Policy Rules, and others. Below it, an 'OSA Application server' and 'SIP Application server' are shown. The central part of the diagram features a 'Position server', 'Position determining entity', 'AAA', 'OSA Service capability server', 'Call session control function', 'Policy decision function', 'Breakout gateway control function', 'Media resource function controller', 'Media resource function processor', 'Media gateway control function', and 'Media gateway'. These are interconnected with various reference points labeled with numbers and letters (e.g., 1, 2, 3, 4, 5/Mk, 6, 7, 8/OSA, 9/Mi, 10, 11/Sh, 12/ISC, 13, 14, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN1, 27, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 39, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh). On the left, a 'cdma2000 access network' box contains 'BTS', 'BSC/RNC + PCF', and 'MM'. Below it are 'Other access networks' and a 'Mobile station'. On the right, an 'Access gateway', 'FA / Attendant', 'Mobile IP home agent', and 'Border router' are shown. At the bottom right, 'PSTN' and 'IP Network' clouds are connected to the 'Border router'. The diagram is labeled 'Q.1742.7(08)_F6-4' at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Figure 6-4: ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem Core Network Architecture Model. This is a complex architectural diagram showing the interconnections between various network elements. At the top, a 'Databases' box contains EIR, DSI, Subscription Profile, Network Policy Rules, and others. Below it, an 'OSA Application server' and 'SIP Application server' are shown. The central part of the diagram features a 'Position server', 'Position determining entity', 'AAA', 'OSA Service capability server', 'Call session control function', 'Policy decision function', 'Breakout gateway control function', 'Media resource function controller', 'Media resource function processor', 'Media gateway control function', and 'Media gateway'. These are interconnected with various reference points labeled with numbers and letters (e.g., 1, 2, 3, 4, 5/Mk, 6, 7, 8/OSA, 9/Mi, 10, 11/Sh, 12/ISC, 13, 14, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN1, 27, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 39, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh). On the left, a 'cdma2000 access network' box contains 'BTS', 'BSC/RNC + PCF', and 'MM'. Below it are 'Other access networks' and a 'Mobile station'. On the right, an 'Access gateway', 'FA / Attendant', 'Mobile IP home agent', and 'Border router' are shown. At the bottom right, 'PSTN' and 'IP Network' clouds are connected to the 'Border router'. The diagram is labeled 'Q.1742.7(08)\_F6-4' at the bottom right. + +**Figure 6-4 – ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem Core Network Architecture Model** + +The session control functions within the IMS are logically interconnected in various ways in the session scenarios. Figure 6-5 identifies the reference points within the IMS between these session control entities. In many cases there are dual labels for these reference points either of which may be used in the applicable specifications. + +![Figure 6-5: Session Control Reference Model diagram showing the interaction between an IP Multimedia client, (Proxy) Call session control function, (Interrogating) Call session control function, (Serving) Call session control function, Media gateway control function, and Breakout gateway control function with various interfaces labeled like hh/Gm, dd/Mw, ff/Mw, 17/Mg, 9/Mi, 49/Mj, and 5/Mk.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +This diagram illustrates the Session Control Reference Model. It features several functional blocks connected by interfaces: + +- An **IP Multimedia client** (dashed box) connects to a **(Proxy) Call session control function** (dashed box) via the **hh/Gm** interface. +- The **(Proxy) Call session control function** connects to an **(Interrogating) Call session control function** via the **dd/Mw** interface. +- The **(Interrogating) Call session control function** connects to a **(Serving) Call session control function** via the **ff/Mw** interface. +- Both the **(Interrogating)** and **(Serving) Call session control functions** connect to a **Media gateway control function** via the **17/Mg** interface. +- The **(Serving) Call session control function** also connects to a **Breakout gateway control function** via the **9/Mi** interface. +- The **Media gateway control function** connects to another **Breakout gateway control function** via the **49/Mj** interface. +- There is also a connection between the two **Breakout gateway control functions** via the **5/Mk** interface. + +The diagram is labeled with **Q.1742.7(08)\_F6-5** in the bottom right corner. + +Figure 6-5: Session Control Reference Model diagram showing the interaction between an IP Multimedia client, (Proxy) Call session control function, (Interrogating) Call session control function, (Serving) Call session control function, Media gateway control function, and Breakout gateway control function with various interfaces labeled like hh/Gm, dd/Mw, ff/Mw, 17/Mg, 9/Mi, 49/Mj, and 5/Mk. + +**Figure 6-5 – Session Control Reference Model** + +Figure 6-6 shows the network reference model for the Converged Access Network (CAN) for the non-roaming case. This system supports access via the Ultra Mobile Broadband (UMB) air interface. + +![Figure 6-6: Converged Access Network Reference Model, non-Roaming diagram showing various network elements like AT, eBS, SRNC, HRPD AN, srv-AGW (MAG), anc-AGW (FA/LMA/MAG), PDSN, ePDIF, HA (LMA), PCRF, IP services (AF), VAAA, BAAA, and HAAA with interfaces labeled U1 through U29 and A10/A11.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +This diagram shows the network reference model for the Converged Access Network (CAN) for the non-roaming case. Key components and interfaces include: + +- An **AT** (Access Terminal) connects to an **eBS** (evolved Base Station) via the **UMB-AI** interface. +- The **eBS** connects to a **srv-AGW (MAG)** via the **U1** interface. +- The **eBS** also connects to an **SRNC** via the **U3** interface. +- The **SRNC** connects to the **srv-AGW (MAG)** via the **U2** interface. +- The **SRNC** connects to an **HRPD AN** via the **U4** interface. +- The **srv-AGW (MAG)** connects to an **anc-AGW (FA/LMA/MAG)** via the **U15' PMIP** interface. +- The **anc-AGW (FA/LMA/MAG)** connects to a **PDSN** via the **U19** interface. +- The **anc-AGW (FA/LMA/MAG)** connects to a **HA (LMA)** via the **U29** interface. +- The **anc-AGW (FA/LMA/MAG)** connects to **IP services (AF)** via the **U23** interface. +- The **anc-AGW (FA/LMA/MAG)** connects to a **PCRF** via the **U16 PMIP/CMIP** interface. +- The **anc-AGW (FA/LMA/MAG)** connects to a **VAAA** via the **U14** interface. +- The **HA (LMA)** connects to a **PCRF** via the **U20** interface. +- The **HA (LMA)** connects to a **Trusted Non-3 GPP2 system** via the **U17a** interface. +- The **HA (LMA)** connects to an **ePDIF** via the **U17b** interface. +- The **HA (LMA)** connects to a **BAAA** via the **U22a** interface. +- The **HA (LMA)** connects to an **HAAA** via the **U22b** interface. +- The **PDSN** connects to an **HRPD AN** via the **A10/A11** interface. +- The **PDSN** connects to an **ePDIF** via the **U21** interface. +- The **ePDIF** connects to an **Untrusted Non-3 GPP2 system** via the **U21** interface. + +The diagram is labeled with **Q.1742.7(08)\_F6-6** in the bottom right corner. + +Figure 6-6: Converged Access Network Reference Model, non-Roaming diagram showing various network elements like AT, eBS, SRNC, HRPD AN, srv-AGW (MAG), anc-AGW (FA/LMA/MAG), PDSN, ePDIF, HA (LMA), PCRF, IP services (AF), VAAA, BAAA, and HAAA with interfaces labeled U1 through U29 and A10/A11. + +**Figure 6-6 – Converged Access Network Reference Model, non-Roaming** + +Figure 6-7 shows the network reference model for the Converged Access Network (CAN) for the roaming case. + +![Figure 6-7 – Converged Access Network Reference Model – Roaming. This diagram illustrates the network architecture for roaming, divided into a 'Visited network' and a 'Home network' by a dashed vertical line. On the left (Visited network), entities include AT (connected to eBS via UMB-AI), HRPD-AN, eBS (with U3), SRNC (with U2, U4), AGW (FA/MAG) (with U14, U26 PMIP, U28), Trusted non-3 GPP2 system (with U19a, U24a), ePDIF (with U21), Untrusted non-3 GPP2 system (with U21), LMA (with U23), V-PCRF (with U18, U24c), and PDSN (with U22a, U22b, A10/A11). On the right (Home network), entities include BAAA, HAAA, IP services (AF) (cloud), HA (with U31, U27 CMIP, U20, U29 CMIP, U25a, U25b), H-PCRF (with U20), and ePDIF (with U25b). Various interfaces are labeled: U1, U2, U3, U4, U6, U14, U18, U19a, U19b, U19c, U20, U21, U22a, U22b, U23, U24a, U24b, U24c, U25a, U25b, U26 PMIP, U27 CMIP, U28, U29 CMIP, U30, U31, U32, and Tx. A reference code 'Q.1742.7(08)_F6-7' is at the bottom right.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +Figure 6-7 – Converged Access Network Reference Model – Roaming. This diagram illustrates the network architecture for roaming, divided into a 'Visited network' and a 'Home network' by a dashed vertical line. On the left (Visited network), entities include AT (connected to eBS via UMB-AI), HRPD-AN, eBS (with U3), SRNC (with U2, U4), AGW (FA/MAG) (with U14, U26 PMIP, U28), Trusted non-3 GPP2 system (with U19a, U24a), ePDIF (with U21), Untrusted non-3 GPP2 system (with U21), LMA (with U23), V-PCRF (with U18, U24c), and PDSN (with U22a, U22b, A10/A11). On the right (Home network), entities include BAAA, HAAA, IP services (AF) (cloud), HA (with U31, U27 CMIP, U20, U29 CMIP, U25a, U25b), H-PCRF (with U20), and ePDIF (with U25b). Various interfaces are labeled: U1, U2, U3, U4, U6, U14, U18, U19a, U19b, U19c, U20, U21, U22a, U22b, U23, U24a, U24b, U24c, U25a, U25b, U26 PMIP, U27 CMIP, U28, U29 CMIP, U30, U31, U32, and Tx. A reference code 'Q.1742.7(08)\_F6-7' is at the bottom right. + +**Figure 6-7 – Converged Access Network Reference Model – Roaming** + +## 7 Network Entities + +### 7.1 Authentication, Authorization and Accounting (AAA) + +The AAA is an entity that provides IP based Authentication, authorization, and Accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions. + +- The Authentication Function provides Authentication of users. +- The Authorization Function of AAA provides authorization of service requests based on subscriber profiles, and network policy. It also generates keys required for establishing security associations between PDSNs in access provider networks and HAs in home IP networks. + +The Accounting Function gathers accounting data concerning the services used by individual subscribers. + +### 7.2 Authentication Centre (AC) + +The AC is an entity that manages the authentication information related to the MS. The AC may, or may not be located within, and be indistinguishable from an HLR. An AC may serve more than one HLR. + +### 7.3 Call Data Collection Point (CDCP) + +The CDCP is the entity that collects the call detail information. + +### **7.4 Call Data Generation Point (CDGP)** + +The CDGP is an entity which provides call detail information to the CDCP [in ANSI-124 format]. This may be the entity that converts call detail information from a proprietary format into a standard format. All information from the CDGP to the CDCP must be in this standard format. + +### **7.5 Call Data Information Source (CDIS)** + +The CDIS is an entity that can be the source of call detail information. This information may be in proprietary format. It is not required to be in the standard format. + +### **7.6 Call Data Rating Point (CDRP)** + +The CDRP is the entity that takes the unrated call detail information and applies the applicable charge and tax related information. The charge and tax information is added using the standard format. + +### **7.7 Collection Function (CF) – [Intercept]** + +The CF is an entity that is responsible for collecting intercepted communications for a lawfully authorized law enforcement agency. + +The CFs typically include: + +- the ability to receive and process call contents information for each intercept subject; +- the ability to receive information regarding each intercept subject (e.g., call associated or non-call associated) from the Delivery function and process it. + +### **7.8 Coordinate Routing Data Base (CRDB)** + +The CRDB is an entity that stores information to translate a given position expressed as a latitude and longitude to a string of digits. + +### **7.9 Customer Service Centre (CSC)** + +The CSC is an entity where service provider representatives receive telephone calls from customers wishing to subscribe to initial wireless service or request a change in the customer's existing service. The CSC interfaces proprietarily with the OTAF to perform network and MS related changes necessary to complete the service provisioning request. + +### **7.10 Delivery Function (DF) – [Intercept]** + +The DF is an entity that is responsible for delivering intercepted communications to one or more collection functions. + +The DFs typically include: + +- The ability to accept call contents for each intercept subject over one or more channels from each Access function. +- The ability to deliver call contents for each intercept subject over one or more channels to a Collection function as authorized for each law enforcement agency. +- The ability to accept information over one or more data channels and combine that information into a single data flow for each intercept subject. +- The ability to filter or select information on an intercept subject before delivery to a Collection function as authorized for a particular law enforcement agency. +- The optional ability to detect audio in-band DTMF digits for translation and delivery to a Collection function as authorized for a particular law enforcement agency. + +- The ability to duplicate and deliver information on the intercept subject to one or more Collection functions as authorized for each law enforcement agency. +- The ability to provide security to restrict access. + +### **7.11 Equipment Identity Register (EIR)** + +The EIR is an entity that is the register to which user equipment identity may be assigned for record purposes. The nature, purpose, and utilization of this information is an area for further study. + +### **7.12 evolved Packet Data Interworking Function (ePDIF)** + +The evolved Packet Data Interworking Function (ePDIF) is an Interworking function for connectivity between a 3GPP2 network and an untrusted non-3GPP2 network (for example, WiFi AP). + +### **7.13 Home Agent (HA)** + +The HA is an entity that: + +- Authenticates Mobile IP registrations from the MS. +- Redirects packets to the foreign agent component of the PDSN, and optionally receives and routes reverse packets from the foreign agent component of the PDSN. +- May establish, maintain and terminate secure communications to the PDSN. +- Receives provisioning information from the AAA Function for users. +- May assign a dynamic home IP address. + +Depending on the architectural configuration, the HA may include the Local Mobility Agent (LMA). + +### **7.14 Home Location Register (HLR)** + +The HLR is the location register to which a user identity is assigned for record purposes such as subscriber information (e.g., Electronic Serial Number (ESN), Mobile Directory Number (MDN), Profile Information, Current Location, Authorization Period). + +### **7.15 Intelligent Peripheral (IP)** + +The IP is an entity that performs specialized resource functions such as playing announcements, collecting digits, performing speech-to-text or text-to-speech conversion, recording and storing voice messages, facsimile services, data services, etc. + +### **7.16 Intercept Access Point (IAP)** + +The IAP is an entity that provides access to the communications to, or from, the equipment, facilities, or services of an intercept subject. + +### **7.17 Interworking Function (IWF)** + +The IWF is an entity that provides information conversion for one or more WNEs. An IWF may have an interface to a single WNE providing conversion services. An IWF may augment an identified interface between two WNEs, providing conversion services to both WNEs. + +### **7.18 IP Services** + +IP Services comprise any IP-based services provided by the operator or 3rd party. This may be part of the Internet or a closed network. + +### **7.19 Local Position Determining Entity (LPDE)** + +The LPDE facilitates the determination of the position or geographical location of a wireless terminal. Each LPDE supports one or more position determining technologies. Multiple LPDEs using the same technology may serve the coverage area of a Mobile Position Centre (MPC) and the multiple LPDEs each using a different technology may serve the same coverage area of an MPC. Local PDEs (LPDEs) reside at the Base Station (BS). + +### **7.20 Managed Wireless Network Entity (MWNE)** + +A MWNE (within the Collective Entity) or any specific network entity having Operation System wireless management needs, including another Operations System. + +### **7.21 Message Centre (MC)** + +The MC is an entity that stores and forwards short messages. The MC may also provide supplementary services for Short Message Service (SMS). + +### **7.22 Mobile Position Centre (MPC)** + +The MPC selects a PDE to determine the position of a mobile station. The MPC may restrict access to position information (e.g., require that the MS be engaged in an emergency call or only release position information to authorized network entities). + +### **7.23 Mobile Switching Centre (MSC)** + +The MSC switches circuit mode MS originated or MS terminated traffic. An MSC is usually connected to at least one BS. It may connect to the other public networks (PSTN, ISDN, etc.), other MSCs in the same network, or MSCs in different networks. The MSC may store information to support these capabilities. + +### **7.24 Number Portability DataBase (NPDB)** + +The NPDB is an entity which provides portability information for portable Directory Numbers. + +### **7.25 Over-The-Air Service Provisioning Function (OTAF)** + +The OTAF is an entity that interfaces proprietarily to CSCs to support service provisioning activities. The OTAF interfaces with the MSC to send MS orders necessary to complete service provisioning requests. + +### **7.26 Packet Data Network (PDN)** + +A PDN, such as the Internet, provides a packet data transport mechanism between processing network entities capable of using such services. + +### **7.27 Packet Data Serving Node (PDSN)** + +The PDSN routes MS-originated or MS-terminated packet data traffic. The PDSN establishes, maintains, and terminates link layer sessions to MSs. The PDSN may interface to one or more MSs and may interface to one or more PDNs. + +### **7.28 Position Determining Entity (PDE)** + +A PDE facilitates determination of the position or geographical location of a wireless terminal. Each PDE supports one or more position determining technologies. Multiple PDEs using the same technology may serve the coverage area of a Mobile Position Centre (MPC) and the multiple PDEs each using a different technology may serve the same coverage area of an MPC. + +### **7.29 Service Control Point (SCP)** + +The SCP is an entity that acts as a real-time database and transaction processing system that provides service control and service data functionality. + +### **7.30 Service Node (SN)** + +The SN is an entity that provides service control, service data, specialized resources and call control functions to support bearer-related services. + +### **7.31 Short Message Entity (SME)** + +The SME is an entity that composes and decomposes short messages. A SME may, or may not be located within, and be indistinguishable from, an HLR, MC, VLR, MS, or MSC. + +### **7.32 Visitor Location Register (VLR)** + +The VLR is the location register other than the HLR used by an MSC to retrieve information for handling of calls to or from a visiting subscriber. The VLR may, or may not be located within, and be indistinguishable from an MSC. The VLR may serve more than one MSC. + +### **7.33 Voice Message Centre (VMS)** + +A VMS stores received voice messages, data messages, e.g., email, or both message types and supports a method to retrieve previously stored messages. A VMS may also support (on a Directory Number basis) notification of the presence of stored messages and notification of a change in the number of voice messages, data messages, or both message types that are waiting retrieval. + +### **7.34 Wireless Network Entity (WNE)** + +A Network Entity in the wireless Collective Entity. + +The remaining text in this clause is based on reference [13 a-c] clause 2.1. + +### **7.35 Access Gateway (AGW)** + +The Access Gateway (AGW) is an entity that provides the user's "point of IP connectivity" to the network. That is, the AGW is in effect the first-hop router for the mobile terminal. The AGW performs layer 3 services and above, including hot-lining, accounting, policy enforcement, etc. + +### **7.36 Access Terminal (AT)** + +The access terminal is the subscriber device supported by the network. + +### **7.37 Application Server** + +Application Servers provide value-added network-based services for wireless subscribers. These services may be accessed via the OSA Service Capability Server (OSA-SCS) or accessed directly from the user's mobile station via other network entities, by-passing the OSA-SCS. + +### **7.38 Authentication, Authorization and Accounting (AAA)** + +The AAA is an entity that provides IP-based Authentication, authorization, and Accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions. + +- The Authentication Function is an entity that provides Authentication of terminal devices and subscribers. + +- The Authorization Function of AAA provides authorization of requests for services and/or bandwidth, etc. and has access to the Policy Repository, the Directory Services, Subscriber Profiles, and the Device Register. +- The Accounting Function gathers data concerning the services, QoS, and multimedia resources requested and used by individual subscribers. + +### **7.39 Border Router (BR)** + +The BR connects the Core Network with peer networks (e.g., other service providers, corporate networks, Internet). The BR performs IP packet routing, exterior gateway routing protocols, and policing of incoming and outgoing traffic, ensuring traffic complies with defined Service Level Agreements established with peer networks. The BR may intercept any QoS allocation request, and issue a request to the Policy Decision Function (PDF), which shall verify that the requested inbound and/or outbound QoS is available. A successful response from the PDF may cause the BR to forward the bandwidth allocation request to its final destination. + +### **7.40 Breakout Gateway Control Function (BGCF)** + +The BGCF selects the network in which PSTN breakout is to occur and, within the network where the breakout is to occur, selects the MGCF. + +### **7.41 Call Session Control Function (CSCF)** + +The CSCF establishes, monitors, supports, releases Multimedia sessions, and manages the user's service interactions. + +### **7.42 Databases (DB)** + +The information in the core network DBs may include but is not limited to EIR, Dynamic Subscriber Information, Network Policy Rules and Subscriber Profile data. + +### **7.43 evolved Base Station (eBS)** + +The evolved base Station (eBS) provides the over-the-air signaling and user data transport that is used by the AT for connectivity to the radio access network. + +### **7.44 IP Multimedia Client** + +The IP Multimedia Client communicates with Application Servers, P-CSCFs, and other IP Multimedia Clients. The IP Multimedia Client is an application that resides in the MS. + +### **7.45 IP Network** + +The IP network corresponds to IP-based packet data networks that provide a transport mechanism between the core network and external IP networks. IP Network represents packet networks connected to the core network including the public Internet, private IP backbone networks and private IP networks such as corporate Intranets. + +### **7.46 Local Mobility Anchor (LMA)** + +The Local Mobility Anchor is the home agent for the mobile node in the Proxy Mobile IPv6 domain. It is the topological anchor point for the mobile node's home prefix and is the entity that manages the mobile node's reachability state. + +### **7.47 Media Gateway (MGW)** + +The MGW provides an interface between the packet environment of the Core Network and the circuit switched environment of the PSTN for bearer traffic, when equipped with circuit + +capabilities. The MGW may provide vocoding and/or transcoding functions to the bearer traffic. The MGW may also provide modem functions to convert digital byte streams to and from audio modem tones placed on circuits, and may provide the capability to terminate PPP (Point-to-Point Protocol) connections. It also provides policy enforcement relative to its activities and resources. + +### **7.48 Media Gateway Control Function (MGCF)** + +The MGCF provides the ability to control a Media Gateway through standardized interfaces. Such control includes allocation and deallocation of resources of the Media Gateway, as well as modification of the usage of those resources. + +### **7.49 Media Resource Function Controller (MRFC)** + +The MRFC, in conjunction with the MRFP, provides a set of resources within the core network that are useful in supporting services to subscribers. The MRFC, in conjunction with the MRFP, provides multi-way conference bridges, announcement playback services, tone playback services, etc. + +### **7.50 Media Resource Function Processor (MRFP)** + +The MRFP, in conjunction with the controlling entity, provides multi-way conference bridges, announcement playback services, tone playback services, etc. + +### **7.51 Mobile IP Home Agent (HA)** + +The HA provides two major functions: registering the current point of attachment of the user, and forwarding of IP packets to and from the current point of attachment (IPv4 Care of Address [CoA] and/or IPv6 Co-located CoA) of the user. The HA accepts registration requests using the Mobile IP protocol and uses the information in those requests to update internal information about the current point of attachment of the user, i.e., the current IP address to be used to transmit and receive IP packets to and from that user. The HA interacts with the AAA to receive Mobile IP registration requests that have been authenticated, and to return Mobile IP registration responses. The HA also interacts with the Access Gateway to receive subsequent Mobile IP registration requests. The HA may interact with several network entities in performing its work of forwarding IP packets to the current point of attachment of the user. + +### **7.52 Mobile Station (MS)** + +The MS is a wireless terminal used by subscribers to access the Legacy MS Domain or the IP Multimedia Domain services over a radio interface. MSs include portable units (e.g., hand-held units), units installed in vehicles, and somewhat paradoxically, fixed location MSs. The MS is the interface equipment used to terminate the radio path at the subscriber. A MS is a ME with a programmed UIM. + +### **7.53 non-3GPP2 System** + +A non-3GPP2 System may be trusted or untrusted. The AT accesses an operator's network via an ePDIF if the access network is untrusted, and the AT accesses an operator's network directly (i.e., without an ePDIF) if the access network is trusted. + +### **7.54 OSA Service Capability Server (OSA-SCS)** + +The OSA-SCS provides access to network resources needed during service application execution. The interface towards the Application Server uses application programming interfaces such as Open Service Architecture (OSA). The interfaces towards other network entities use the relevant protocols. + +### **7.55 Policy Decision Function (PDF)** + +The PDF provides management of core network QoS resources within its own core network necessary to support services to network users. It communicates with the Access Gateway to provide authorization of resource allocations. The PDF makes policy decisions with regard to use of core network QoS resources within its own network, including consideration of Service Level Agreements (SLAs [Note, the maintenance of SLAs is for further study.]). QoS policy information for network resource utilization may be forwarded to and cached by the PDF. + +### **7.56 Position Determining Entity (PDE)** + +The PDE communicates with the Position Server to determine the precise geographic position of the MS based on input data provided by the Position Server. + +### **7.57 Position Server** + +The Position Server provides geographic position information to requesting entities. + +### **7.58 Public Switched Telephone Network (PSTN)** + +The PSTN is defined in accordance with the appropriate applicable national and regional standards. + +### **7.59 Proxy Mobile Agent (PMA) or Mobile Access Gateway (MAG)** + +The Proxy mobile agent (or mobile access gateway) is a function that manages the mobility-related signaling for a mobile node that is attached to its access link. It is responsible for tracking the mobile node's attachment to the link and for signaling the mobile node's local mobility anchor. PMA is PMIP4 term and MAG is PMIP6 term. + +### **7.60 Policy and Charging Rules Function (PCRF)** + +The PCRF provides rules to the AGW over the U23 reference point for Quality of Service and charging control. + +### **7.61 Session Reference Network Controller (SRNC)** + +The Session Reference Network Controller (SRNC) is responsible for maintaining the session reference with the AT. The SRNC is also responsible for supporting idle state management of the AT, and providing paging control functions when the AT is idle. The SRNC contains a Session Anchor Access Network Route Instance (ANRI) for each AT it is supporting. + +## **8 Reference Points** + +The following text is based on reference [12 a-d] clause 2.1.2. + +### **8.1 Reference Point B** + +Reference Point B is the interface between the MSC and the VLR. + +### **8.2 Reference Point C** + +Reference Point C is the interface between the MSC and the HLR. + +### **8.3 Reference Point D** + +Reference Point D is the interface between the VLR and HLR. + +### **8.4 Reference Point d** + +Reference Point d is the interface between an IAP and the DF. + +### **8.5 Reference Point D1** + +Reference Point D1 is the interface between the OTAF and the VLR. + +### **8.6 Reference Point Di** + +Reference Point Di is the interface between: + +- The IP and the ISDN +- The IWF and the ISDN +- The MSC and the ISDN [ESBE] +- The SN and the ISDN + +### **8.7 Reference Point E** + +Reference Point E is the interface between the MSC and MSC. + +### **8.8 Reference Point E3** + +Reference Point E3 is the interface between the MPC and the MSC. + +### **8.9 Reference Point E5** + +Reference Point E5 is the interface between the MPC and the PDE. + +### **8.10 Reference Point E9** + +Reference Point E9 is the interface between the MPC and the SCP. + +### **8.11 Reference Point E11** + +Reference Point E11 is the interface between the CRDB and the MPC. + +### **8.12 Reference Point E12** + +Reference Point E12 is the interface between the MSC and the PDE. + +### **8.13 Reference Point e** + +Reference Point e is the interface between the CF and the DF. + +### **8.14 Reference Point F** + +Reference Point F is the interface between the MSC and the EIR. + +### **8.15 Reference Point G** + +Reference Point G is the interface between the VLR and the VLR. + +### **8.16 Reference Point H** + +Reference Point H is the interface between the HLR and the AC. + +### **8.17 Reference Point I** + +Reference Point I is the interface between the CDIS and the CDGP. + +### **8.18 Reference Point J** + +Reference Point J is the interface between the CDGP and the CDCP. + +### **8.19 Reference Point K** + +Reference Point K is the interface between the CDGP and the CDRP. + +### **8.20 Reference Point L** + +Reserved. + +### **8.21 Reference Point M1** + +Reference Point M1 is the interface between the SME and the MC. + +### **8.22 Reference Point M2** + +Reference Point M2 is the MC to MC interface. + +### **8.23 Reference Point M3** + +Reference Point M3 is the SME to SME interface. + +### **8.24 Reference Point N** + +Reference Point N is the interface between the HLR and the MC. + +### **8.25 Reference Point N1** + +Reference Point N1 is the interface between the HLR and the OTAF. + +### **8.26 Reference Point O1** + +Reference Point O1 is the interface between an MWNE and the OSF. + +### **8.27 Reference Point O2** + +Reference Point O2 is the interface between an OSF and the OSF. + +### **8.28 Reference Point Pi** + +Reference Point Pi is the interface between: + +- The AAA and the AAA, +- The AAA and the PDN, +- The IWF and the PDN, +- The MSC and the PDN, plus +- The PDSN and the PDN. + +### **8.29 Reference Point Q** + +Reference Point Q is the interface between the MC and the MSC. + +### **8.30 Reference Point Q1** + +Reference Point Q1 is the interface between the MSC and the OTAF. + +### **8.31 Reference Point T1** + +Reference Point T1 is the interface between the MSC and the SCP. + +### **8.32 Reference Point T2** + +Reference Point T2 is the interface between the HLR and the SCP. + +### **8.33 Reference Point T3** + +Reference Point T3 is the interface between the IP and the SCP. + +### **8.34 Reference Point T4** + +Reference Point T4 is the interface between the HLR and the SN. + +### **8.35 Reference Point T5** + +Reference Point T5 is the interface between the IP and the MSC. + +### **8.36 Reference Point T6** + +Reference Point T6 is the interface between the MSC and the SN. + +### **8.37 Reference Point T7** + +Reference Point T7 is the interface between the SCP and the SN. + +### **8.38 Reference Point T8** + +Reference Point T8 is the interface between the SCP and the SCP. + +### **8.39 Reference Point T9** + +Reference Point T9 is the interface between the HLR and the IP. + +### **8.40 Reference Point V** + +Reference Point V is the interface between the OTAF and the OTAF. + +### **8.41 Reference Point X** + +Reference Point X is the interface between the CSC and the OTAF. + +### **8.42 Reference Point Y** + +Reference Point Y is the interface between a Wireless Network Entity (WNE) and the IWF. + +### **8.43 Reference Point Z** + +Reference Point Z is the interface between the MSC and the NPDB. + +### **8.44 Reference Point Z1** + +Reference Point Z1 is the interface between the MSC and the VMS. + +### **8.45 Reference Point Z2** + +Reference Point Z2 is the interface between the HLR and the VMS. + +### **8.46 Reference Point Z3** + +Reference Point Z3 is the interface between the MC and the VMS + +The remaining text in this clause is based on reference [13 a-c] clause 2.1. + +An interface exists when two Network Entities are interconnected through exactly one signalling or bearer stream Reference Point. The Reference Points and their associated Network Entities are: + +### **8.47 Reference Point 1** + +Reference Point 1 is the signaling interface between the Databases and the Position Server [Multimedia Domain only]. + +### **8.48 Reference Point 2** + +Reference Point 2 is the signaling interface between the Databases and the cdma2000 Access Network. + +### **8.49 Reference Point 3** + +Reference Point 3 is the signaling interface between the Databases and the Policy Decision Function [Multimedia Domain only]. + +### **8.50 Reference Point 4** + +Reference Point 4 is the signaling interface between the Databases and the AAA. + +### **8.51 Reference Point 5/Mk** + +Reference Point 5/Mk is the signaling interface between Breakout Gateway Control Functions [Multimedia Domain only]. + +### **8.52 Reference Point 6** + +Reference Point 6 is the signaling interface between the Databases and the Legacy MS Domain Support [Legacy MS Domain only]. + +### **8.53 Reference Point 7** + +Reference Point 7 is the signaling interface between the OSA Service Capability Server and the Databases. + +### **8.54 Reference Point 8/OSA** + +Reference Point 8/OSA is the signaling interface between the OSA Application Server and the OSA Service Capability Server. Reference Point 8/OSA may employ interfacing techniques that support a wide spectrum of capabilities, ranging from secure (e.g., application programming interfaces such as Parlay, used for un-trusted parties) to non-secure (e.g., used for trusted parties). + +### **8.55 Reference Point 9/Mi** + +Reference Point 9/Mi is the signaling interface between the Visited Network's BGCF and the Home Service Network's Serving-CSCF. + +### **8.56 Reference Point 10** + +Reference Point 10 is the signaling interface between the Position Server and the OSA Service Capability Server [Multimedia Domain only]. + +### **8.57 Reference Point 11/Sh** + +Reference Point 11/Sh is the signaling interface between the SIP Application Server and the AAA and between the OSA Service Capability Server and the AAA for user's service authentication and/or authorization, and for retrieving information from the MMD database [Multimedia Domain only]. + +### **8.58 Reference Point 12/ISC** + +Reference Point 12/ISC is the signaling interface between the SIP Application Server and Call Session Control Function and between the OSA Service Capability Server and the Call Session Control Function for service control [Multimedia Domain only]. + +### **8.59 Reference Point 13** + +Reference Point 13 is the signaling interface between the Legacy MS Domain Support and the PSTN [Legacy MS Domain only]. + +### **8.60 Reference Point 14** + +Reference Point 14 is the signaling interface between the Legacy MS Domain Support and the MAP (TIA/EIA-41 & GSM) [Legacy MS Domain only]. + +### **8.61 Reference Point 15** + +Reference Point 15 is the signaling interface between the Position Server and AAA. + +### **8.62 Reference Point 16/Cx** + +Reference Point 16/Cx is the signaling interface between the AAA and the Call Session Control Function [Multimedia Domain only]. + +### **8.63 Reference Point 17/Mg** + +Reference Point 17/Mg is the signaling interface between the Call Session Control Function and the Media Gateway Control Function [Multimedia Domain only]. + +### **8.64 Reference Point 18** + +Reference Point 18 is the signaling interface between the Position Server and the Position Determining Entity. + +### **8.65 Reference Point 19** + +Reference Point 19 is the signaling interface between the Position Server and the Access Gateway [Multimedia Domain only]. + +### **8.66 Reference Point 20** + +Reference Point 20 is the signaling interface between the AAA and the cdma2000 Access Network [Multimedia Domain only]. + +### **8.67 Reference Point 21** + +Reference Point 21 is the signaling interface between the AAA and Access Gateway. + +### **8.68 Reference Point 22** + +Reference Point 22 is the signaling interface between the AAA and the Mobile IP Home Agent. + +### **8.69 Reference Point 23** + +Reference Point 23 is the signaling interface between the AAA and the Policy Decision Function [Multimedia Domain only]. + +### **8.70 Reference Point 24/Mr** + +Reference Point 24/Mr is the signaling interface between the Call Session Control Function and the Media Resource Function Controller [Multimedia Domain only]. + +### **8.71 Reference Point 25/Mp** + +Reference Point 25/Mp is the signaling interface between the Media Resource Function Controller and the Media Resource Function Processor. + +### **8.72 Reference Point 26/PSTN** + +Reference Point 26/PSTN is the signaling interface between the Media Gateway Control Function and the PSTN [Multimedia Domain only]. + +### **8.73 Reference Point 27** + +Reference Point 27 is the bearer stream interface between the cdma2000 Access Network and the Media Gateway [Legacy MS Domain only]. + +### **8.74 Reference Point 28/Go** + +Reference Point 28/Go is the signaling interface between the Policy Decision Function and Access Gateway. + +### **8.75 Reference Point 29** + +Reference Point 29 is the signaling interface between Policy Decision Function and the Border Router. + +### **8.76 Reference Point 30/Mc** + +Reference Point 30/Mc is the signaling interface between the Media Gateway Control Function and the Media Gateway [Multimedia Domain only]. + +### **8.77 Reference Point 31** + +Reference Point 31 is the bearer stream interface between cdma2000 Access Network and the Access Gateway. + +### **8.78 Reference Point 32/Mb** + +Reference Point 32/Mb is the bearer stream interface between the Access Gateway and the Media Resource Function Processor [Multimedia Domain only]. + +### **8.79 Reference Point 33/Mb** + +Reference Point 33/Mb is the bearer stream interface between the Media Resource Function Processor and the Media Gateway. + +### **8.80 Reference Point 34/Mb** + +Reference Point 34/Mb is the bearer stream interface between the Media Gateway and the PSTN. + +### **8.81 Reference Point 35** + +Reference Point 35 is the signaling interface between the cdma2000 Access Network and the Access Gateway. + +### **8.82 Reference Point 36/Mb** + +Reference Point 36/Mb is the bearer stream interface between the Access Gateway and the Media Gateway [Multimedia Domain only]. + +### **8.83 Reference Point 37/Mb** + +Reference Point 37/Mb is the bearer stream interface between the Media Resource Function Processor and the Mobile IP Home Agent [Multimedia Domain only]. + +### **8.84 Reference Point 38/Mb** + +Reference Point 38/Mb is the bearer stream interface between the Media Gateway and the Mobile IP Home Agent [Multimedia Domain only]. + +### **8.85 Reference Point 39** + +Reference Point 39 is the signaling interface between the Media Gateway and the Legacy MS Domain Support [Legacy MS Domain only]. + +### **8.86 Reference Point 40/Mb** + +Reference Point 40/Mb is the bearer streams interface between the Media Gateway and the Border Router. + +### **8.87 Reference Point 41** + +Reference Point 41 is the signaling interface between the Access Gateway and the Mobile IP Home Agent. + +### **8.88 Reference Point 42/Mb** + +Reference Point 42/Mb is the bearer streams interface between the Media Resource Function Processor and the Border Router. + +### **8.89 Reference Point 43/Mb** + +Reference Point 43/Mb is the bearer streams interface between the Access Gateway and the Mobile IP Home Agent. + +### **8.90 Reference Point 44/Mb** + +Reference Point 44/Mb is the bearer stream interface between the Mobile IP Home Agent and the Border Router. + +### **8.91 Reference Point 45/Mb** + +Reference Point 45/Mb is the bearer stream interface between the Access Gateway and the Border Router. + +### **8.92 Reference Point 46/Mb** + +Reference Point 46/Mb is the bearer stream interface between the Border Router and the IP Network. + +### **8.93 Reference Point 47** + +Reference Point 47 is the Radio Link (air interface) between the Mobile Station and the cdma2000 Access Network. + +### **8.94 Reference Point 48** + +Reference Point 48 is the signaling interface between the cdma2000 Access Network and the Legacy MS Domain Support [Legacy MS Domain only]. + +### **8.95 Reference Point 49/(Mj)** + +Reference Point 49/(Mj) is the signaling interface between the Breakout Gateway Control Function and the Media Gateway Control Function [Multimedia Domain only]. + +### **8.96 Reference Point 50** + +Reference Point 50 is the signaling interface between the Policy Decision Function and the P-CSCF [Multimedia Domain only]. + +### **8.97 Reference Point U1** + +Reference Point U1 carries control and bearer information between evolved Base Station (eBS) and the Access GateWay (AGW). The U1 reference point includes interfaces for bearer transport (user data and signaling), QoS, and accounting. + +### **8.98 Reference Point U2** + +Reference Point U2 provides interfaces for carrying control information between the eBS and the SRNC. + +### **8.99 Reference Point U3** + +Reference Point U3 carries control and bearer information between eBSs. + +### **8.100 Reference Point U4** + +Reference Point U4 carries control information between SRNCs. + +### **8.101 Reference Point U6** + +Reference Point U6 connects the SRNC to the AGW. + +### **8.102 Reference Point U14** + +Reference Point U14 connects the anc-AGW or AGW with the AAA infrastructure via the Visited AAA server (VAAA). This reference point implements a signaling protocol to support user authentication, authorization and accounting. + +### **8.103 Reference Point U15** + +Reference Point U15 carries control and bearer information between srv-AGW. U15 reference point provides local mobility based on PMIP. + +### **8.104 Reference Point U15'** + +Reference Point U15' carries control and bearer information between two AGWs: the Serving AGW (srv-AGW) and the Anchor AGW (anc-AGW). This reference point is not exposed if the srv-AGW and anc-AGW are collocated. This reference point also carries policy information. + +### **8.105 Reference Point U16** + +Reference Point U16 carries control and bearer information between the AGW and the Home Agent (HA), and supports bearer transport and signaling for mobility. + +### **8.106 Reference Point U17** + +Reference Point U17 carries control and bearer information between the 3GPP2 network and a non-3GPP2 network. The U17a reference point carries control and bearer information between the 3GPP2 network and a trusted non-3GPP2 network (e.g., 3GPP SAE/LTE or WiMAX). The U17b reference point carries control and bearer information between the 3GPP2 network and an untrusted non-3GPP2 network via the ePDIF (e.g., a WiFi network). + +### **8.107 Reference Point U18** + +Reference Point U18 carries control information between a Visited PCRF (V-PCRF) and a Home PCRF (H-PCRF) in order to transfer policy and charging rules between domains. + +### **8.108 Reference Point U19** + +Reference Point U19 carries control and bearer (optional) information between the AGW and the trusted non-3GPP2 System (U19a), and between the AGW and the ePDIF (U19b), and between the anc-AGW/AGW and the PDSN (U19/U19c). The U19 reference point supports fast/seamless handoff between a CAN and another system. + +### **8.109 Reference Point U20** + +Reference Point U20 connects the HA and the PCRF, and allows (QoS) policy and charging information to be conveyed to the HA. + +### **8.110 Reference Point U21** + +Reference Point U21 connects the ePDIF to an untrusted non-3GPP2 access network. + +### **8.111 Reference Point U22** + +Reference Point U22 provides two separate interfaces: U22a and U22b. The U22a reference point connects the PDSN to a trusted non-3GPP2 network. For this connection the ePDIF is not required to be on the data path. The U22b reference point, however, carries control and bearer information between the PDSN and an untrusted non-3GPP2 network. For this connection the ePDIF is required to be on the data path. + +### **8.112 Reference Point U23** + +Reference Point U23 carries control information from the (QoS) Policy and Charging Rules Function (PCRF) to the anc-AGW/AGW. + +### **8.113 Reference Point U24** + +Reference Point U24 carries control and bearer information between an LMA and another system. The U24 reference point carries control and bearer information with PMIP between the LMA and the trusted non-3GPP2 System (U24a), and between the LMA and the ePDIF (U24b), and between the LMA and the PDSN (U24c). The U24 reference point supports handoff between a CAN and another system. + +### **8.114 Reference Point U25** + +Reference Point U25 carries control and bearer information with CMIP between the HA and the trusted non-3GPP2 System (U25a), and between the HA and the ePDIF (U25b). The U25 reference point supports handoff between a CAN and another system. + +### **8.115 Reference Point U26** + +Reference Point U26 carries control and bearer information with PMIP between the LMA and the AGW and supports handoff between AGWs. + +### **8.116 Reference Point U27** + +Reference Point U27 carries control and bearer information with CMIP between the HA and the AGW and supports handoff between AGWs. + +### **8.117 Reference Point U28** + +Reference Point U28 carries control and bearer (optional) information between the AGWs and supports fast inter-AGW handoff. + +### **8.118 Reference Point U29** + +Reference Point U29 carries control and bearer information between the HA and the PDSN. The U29 reference point carries CMIP and PMIP for the split AGW architectures. The U29 reference point carries CMIP for the single AGW architecture. + +### **8.119 Reference Point U30** + +Reference Point U30 carries IP traffic between the AGW and the IP Services network. + +### **8.120 Reference Point U31** + +Reference Point U31 carries IP traffic between the HA and the IP Services network. + +### **8.121 Reference Point U32** + +Reference Point U32 carries IP traffic between the LMA and the IP Services network. + +### **8.122 Reference Point UMB-AI** + +Reference Point UMB-AI (Air Interface) carries control and bearer information between the AT and the eBS. + +# **9 Technical specifications structure** + +This clause provides an overview of the specifications for this IMT-2000 Family member based on ANSI-41 evolved Core Network with cdma2000 Access Network. Details for these specifications may be found in clause 10. + +The following text describes the numbering scheme for the specifications and reports for the 3GPP2 3rd Generation Mobile System. + +The 3GPP2 document-numbering scheme is indicated as follows: + +A.Bcccc-w-x version y.z + +Where: + +- 1) A denotes the TSG (A, C, N, P, S) which developed the specification where: + - TSG-A develops RAN (i.e., A-interface) specifications + - TSG-C develops air interface specifications + - TSG-N develops intersystem interface specifications + - TSG-P develops packet data specifications + +- TSG-S develops service and system aspects specifications including Stage 1 requirements descriptions and OAM&P specifications +- 2) B denotes project, report, specification (P, R, S). + - 3) cccc denotes a four (4) digit number which identifies the specific specification + - 4) w denotes revision + - 0 is the first release (0th revision), + - A is the first revision, + - and so on + - 5) x denotes whether this is the prime revision or an addendum + - 0 is the prime revision, and is used when the document is first created + - 1 is the first addendum + - 2 is the second addendum + - and so on + - 6) y is the "point release" indicator – 0 is used when the document is first created; the number is incremented whenever approved for publishing by the plenary of a TSG (e.g., 1 is the first approval by the plenary for publishing). + - 7) z is an internal edit level. The internal edit level z, is always reset to 0 when the document is approved by the applicable plenary. It is incremented by the entity (e.g., working group) that is developing the document for each new edit release. + +NOTE 1 – If the designator w and the designator x are both equal to 0, then neither designator needs to be included. + +NOTE 2 – The document reference section does not need to include "version y.z" unless specifically needed to resolve a technical incompatibility that would exist. + +# 10 Technical Specifications + +All dates in the tables of clause 10 are formatted day-month-year. If no day is shown for the document, then the format is -month-year.1 + +### 10.1 A Series RAN Specifications + +The 3GPP2 A Series RAN specifications are outside of the scope of this Recommendation. The radio access network to core network interface specifications for the cdma2000 (ANSI-41 evolved core network with cdma2000 access network) system family will be referenced in a new issue of Recommendation ITU-R M.1457. + +### 10.2 Intersystem Specifications + +#### 10.2.1 N.S0003-0 v.1.0 User Identity Module (April 2001) + +This standard defines the enhancements required for the support of mobile stations equipped with User Identification Modules (UIM). The UIM provides functionality to certain types of mobile stations to enable them to operate in the wireless network. + +1 Note on nomenclature of TTA documents: before TTA was accredited, documents were created under EIA. After TTA was accredited as a standards development organization, documents were named beginning with TTA/EIA. TTA documents can now stand by themselves, so since 2000, documents are now titled TTA only. The IS was an interim standard valid for 3 years and that naming system is no longer used for new documents. + +This document defines requirements for the wireless network to support operation of UIM equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of mobile stations operating in the TTA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations. + +The UIM can be in one of two forms, as either integrated within the mobile or removable that can be inserted or removed from the mobile equipment. This document addresses Removable UIM (R-UIM) only. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0003-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-808 | | Published | --12-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0003 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0003.zip | +| TTC | TS-3GB-N.S0003v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0003-v10.pdf | + +### 10.2.2 N.S0004-0 v 1.0 WIN Phase 2 (April 2001) + +- Triggers for Preferred Language +- Advice of Charge – Rejection of Undesired Annoying Calls +- Premium Rate Charging +- Freephone + +Premium Rate Charging (PRC), Freephone (FPH) and Advice of Charging (AOC) are charging related services that provide a set of advanced wireless charging capabilities. Rejection of Undesired Annoying Calls (RUAC) is a screening service that blocks undesired annoying calls to the subscriber. Enhanced Preferred Language (EPL) uses Wireless Intelligent Network (WIN) capabilities to provide announcements to the subscriber in the subscriber's preferred language. This specification presents a recommended plan for the implementation of WIN capabilities that support these features. The WIN capabilities are for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0004-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-848 | | Published | --12-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0004 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0004.zip | +| TTC | TS-3GB-N.S0004-0V1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0004-0v10.pdf | + +### 10.2.3 N.S0005-0 Version 1.0 Cellular Radiotelecommunications Intersystem Operations (no date) + +(O) The purpose of this document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | YDT 1031-1999 | 1.0 | Published | -12-1999 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-41-D | | Published | --12-1997 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0005 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0005.zip | + +#### 10.2.4 N.S0006 Version 1.0.0 PCS Multi-band Based on IS-41-C Revision: 0 (28 January 2000) + +3GPP2 document was withdrawn. + +#### 10.2.5 N.S0008 Version 1.0 Circuit Mode Services (no date) + +This Standard presents a recommended plan for the implementation of Uniform Features for use in the Cellular Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +Services: + +- Asynchronous Data Service (ADS) +- Data Privacy (DP) +- Group 3 Facsimile Service (G3 Fax) +- Service Negotiation (SN) +- Mobile Termination Functions + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0008 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-737 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0008 V1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0008v1.0.pdf | +| TTC | JP-3GB-N.S0008 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0008.pdf | + +#### 10.2.6 N.S0009-0 Version 1.0 IMSI (no date) + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-751 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0009 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0009.zip | +| TTC | JP-3GB-N.S0009 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0009.pdf | + +### 10.2.7 N.S0010-0 Version 1.0 Advanced features in Wideband Spread Spectrum Systems (no date) + +For this revision of this Standard, the advanced CDMA features include: Network Directed System Selection (NDSS) and Subscriber Confidentiality (SC) supported by TMSI. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0010-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-735 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0010 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0010-0v1.0.pdf | +| TTC | JP-3GB-N.S0010-0 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0010.pdf | + +### 10.2.8 N.S0011-0 Version 1.0 OTASP and OTAPA (no date) + +This document presents recommendations for supporting the Over-The-Air "Service Provisioning" (OTASP) and "Parameter Administration" (OTAPA) capability. + +Specifically, this document includes Stage-1 recommendations for OTASP Subscriber Feature and OTAPA Network Feature Descriptions. It also provides intersystem operation recommendations for supporting the OTASP & OTAPA capability for the CDMA and TDMA air interfaces, with Stage-2 operations and scenarios, Stage-3 operations and parameter definitions plus Stage-3 procedures. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0011-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-725-A | | Published | --07-1999 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0011 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0011.zip | +| TTC | JP-3GB.N.S0011 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0011.pdf | + +### 10.2.9 N.S0012-0 CNAP/CNAR Revision: 0 (28 January 2000) + +This document presents a recommended plan for the implementation of Calling Name Presentation (CNAP) and Calling Name Restriction (CNAR) for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0012-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-764 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0012 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0012.zip | +| TTC | JP-3GB-N.S0012 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0012.pdf | + +### 10.2.10 N.S0013-0 Version 1.0 WIN Phase 1 (no date) + +The Wireless Intelligent Network (WIN) is a network which supports the use of intelligent network capabilities to provide seamless terminal services, personal mobility services and advanced network services in mobile environment. + +This document presents a recommended plan for the implementation of the Wireless Intelligent Network (WIN) for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------|---------|------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0013-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-771
TIA/EIA/IS-771-1 | | Published
Published | --07-1999
--08-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0013 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0013.zip | +| TTC | JP-3GB-N.S0013 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0013.pdf | + +### 10.2.11 N.S0014-0 Version 1.0 Authentication Enhancements (no date) + +This Standard presents a recommended plan for the implementation of authentication enhancements for use in the Wireless Radiotelephone Service. Its intent is to describe the authentication enhancements so that the manner in which a system implements them may remain reasonably consistent from system to system. + +The authentication enhancements include: + +- Count Update after Handoff +- Obtaining subscriber profile before authentication on initial system access +- Handling of suspicious call originations +- Identify the Serving MSC when reporting the outcome of a requested authentication operation +- Handling of authentication capable mobile stations when the home system is not authentication capable +- Clarification and editorial correction of authentication procedures +- Miscellaneous authentication enhancements + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0014-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-778 | | Published | --03-1999 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0014 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0014.zip | +| TTC | JP-3GB-N.S0014 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0014.pdf | + +### 10.2.12 N.S0015 Version 1.0.0 ANSI-41-D Miscellaneous Enhancements (28 January 2000) + +This document is intended to justify *TIA/EIA-41-D* technical enhancement or technical correction contributions that have been supported for incorporation into PN-3590 (*TIA/EIA-41-E*) but are not expected to be published in a *TIA/EIA-41-D* enhancement Interim Standard (IS). + +This document is for tracking purposes only, there is no intention of publishing the contents of this document independent of ANSI/TIA/EIA-41-E. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-N.S0015
v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0015v1.0.0.pdf | + +### 10.2.13 N.S0016-0 Version 1.0 TIA/EIA-41-D Internationalization (no date) + +This document specifies the ANSI/TIA/EIA-41-D Chapters 1, 3, 5 and 6 enhancements that are necessary to support international intersystem operations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------|---------|------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0016-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-807
TIA/EIA/IS-807-1 | | Published
Published | --08-1999
--03-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0016 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0016.zip | +| TTC | JP-3GB-N.S0016 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0016.pdf | + +### 10.2.14 N.S0017-B Version 1.0.0 International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41 Revision: B (December 2002) + +When the first edition of Mobile Station – Land Station Compatibility Specification (*IS-3*, now *TIA/EIA-553-A*) was issued, it was envisioned that it would be adopted for use within Northern America. Provisions were included for international implementation; however, detailed guidelines to assist with such implementations were not included. Subcommittee TR-45.2 recognized the need to provide such guidance, and charted a Working Group (Working Group VI) with this responsibility. The result of this Working Group's deliberations has been the production of TSB-29 as well as ongoing internationalization of other TIA standards, such as *TIA/EIA-41-D (N.S0005)*, *TIA-751 (N.S0009)*, *TIA/EIA/IS-807 (N.S0016)*, *TIA/EIA/IS-875 (N.S0027)*, *TIA/EIA-124 (N.S0026)*, *TIA/EIA-136*, *IS-95*, *IS-91* and *TIA/EIA-2000 (C.S0001)*. TSG-N has taken TSB-29 and produced the specification N.S0017. + +The principle aspects of international implementation addressed by this document are: + +- The administration and assignment of System Identification Numbers (SIDs) +- The administration and assignment of Mobile Identification Numbers (MINs) +- Format of International Mobile Subscriber Identifiers (IMSIs) + +The goal of this publication is to provide the international wireless telecommunications industry with the framework permitting the coordinated implementation of Wireless Radio Telecommunication Systems in compliance with the provisions of the AMPS family of air interface standards (e.g., *TIA/EIA-553*, *IS-54*, *IS-91*, *IS-95*, *TIA/EIA-2000* and *TIA/EIA-136*). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0017-0 | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TSB-29E | | Published | --12-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0017-B_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0017-B_v1.0.zip | +| TTC | TS-3GB-N.S0017-Bv1.0 | 1.0 | TTC Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsns0017-Bv10.pdf | + +### 10.2.15 N.S0018 Version 1.0.0 TIA/EIA-41-D Prepaid Charging (14 July 2000) + +Pre-Paid Charging (PPC) allows the subscriber to pay for voice telecommunication services prior to usage. This document presents a recommended plan for the implementation of Wireless Intelligent Network (WIN) capabilities that support PPC. The WIN capabilities that support PPC are for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-826 | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0018 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0018.zip | +| TTC | JP-3GB-N.S0018 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0018.pdf | + +### 10.2.16 N.S0019 Version 1.0.0 Intersystem Link Protocol Revision: 0 (28 January 2000) + +This document specifies an Intersystem Link Protocol (ISLP) for circuit-mode data services. These data services include Asynchronous Data (ADS) and Group-3 Fax as specified in IS-99 and IS-135. The ISLP adapts between air-interface data rates and higher-speed intersystem rates. The ISLP may be used between a serving system and an anchor system, possibly through one or more tandem systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-728 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0019 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0019.zip | +| TTC | JP-3GB-N.S0019 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0019.pdf | + +### 10.2.17 N.S0020 TIA/EIA-41-D Message Segmentation (August 1999) + +3GPP2 document was withdrawn. + +### 10.2.18 N.S0021 Version 1.0.0 User Selective Call Forwarding Revision: 1 (14 July 2000) + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (SCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0021 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-838 | | Published | --07-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0021
v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0021v1.0.0.pdf | +| TTC | JP-3GB-N.S0021 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0021.pdf | + +### 10.2.19 N.S0022 Version 1.0.0 Answer Hold (14 July 2000) + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0022 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-837 | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0022
v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0022v1.0.0.pdf | +| TTC | JP-3GB-N.S0022 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0022.pdf | + +### 10.2.20 N.S0023-0 Version 1.0 Automatic Code Gapping (no date) + +This document presents a recommended plan for the implementation of Automatic Code Gapping (ACG) for use in the Wireless Radiotelephone Service. ACG is used to reduce the rate at which a network entity, typically an MSC, sends service request messages to a service control function (SCF) network entity. ACG controls can be applied automatically by the SCF when it is in overload. ACG controls can also be applied by an SCF for purposes of SCF service management. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0023-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-786 | | Published | --11-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0023-0
v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0023-0v1.0.pdf | +| TTC | JP-3GB-N.S0023 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0023.pdf | + +### 10.2.21 N.S0024-0 Version 1.0 Network support for MDN-Based Message Centers (November 2000) + +This document is intended to identify *TIA/EIA-41-D* WNP-PH3 (Wireless Number Portability – Phase III) technical enhancements required to support SMS (Short Message Service) delivery to MDN (Mobile Directory Number) based MCs (Message Centers). These enhancements have been supported for incorporation into PN-3590 (*TIA/EIA-41-E*) and are being published as a *TIA/EIA-41-D* enhancement Interim Standard (IS). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0024-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-841 | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0024-0 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0024-0v1.0.pdf | +| TTC | TS-3GB-N.S0024v1.0 | 1.0 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0024-v10.pdf | + +### 10.2.22 N.S0025 Version 1.0.0 Roamer Database Verification (January 2001) + +This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0025 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-N.S0025 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0025v1.0.0.pdf | +| TTC | TS-3GB-N.S0025v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0025-v10.pdf | + +#### 10.2.22.1 N.S0025-A Version 1.0.0 Roamer Database Verification Revision: A (June 2002) + +This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. + +Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities. + +RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system. + +RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in *IS-41-C* or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0025-A | 1.0.0 | Published | -09-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TIA | TIA/EIA/IS-847-A | | Published | --07-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0025-A v1.0.0 | 1.0.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0025-A_v1.0.0.zip | + +### 10.2.22.2 N.S0025-B Version 1.0.0 Roamer Database Verification Revision: B (October 2002) + +3GPP2 document was superseded by X.S0021-B v1.0 + +This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. + +Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities. + +RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in *IS-41-C* or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system as well as other message routing database related problems. + +This document describes the RDV network capability and the intersystem operations to enable a wireless system to use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0025-B | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-N.S0025-B_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0025-B_v1.0.zip | + +### 10.2.23 N.S0026 Version 1.0.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (August 2000) + +This standard is complementary to the ANSI-41, Cellular Radiotelecommunications Intersystem Operations, series of standards and identifies wireless services specifically involving non-signaling data communications which require intersystem cooperation, presents the general background against which those services are to be provided and summarizes the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +This standard describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0026 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-124-C | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0026 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0026v1.0.0.pdf | + +### 10.2.23.1 N.S0026-A Version 1.0.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH Revision A (December 2001) + +This standard is complementary to the *ANSI-41, Cellular Radiotelecommunications Intersystem Operations*, series of standards and identifies wireless services specifically involving non-signaling data communications which require intersystem cooperation, presents the general background against which those services are to be provided and summarizes the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +This standard describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0026-A | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA/EIA-124-D | | Published | --12-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0026-A_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0026-A_v1.0.zip | + +### 10.2.24 N.S0027 Version 1.0.0 Enhanced International Dialing, Calling Number Identification & Callback, Calling Party Category Identification (April 2001) + +This document presents a recommended plan for the implementation of enhanced international dialing, calling number identification and callback, and calling party category identification for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0027 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-875 | | Published | --05-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0027 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0027v1.0.0.pdf | +| TTC | TS-3GB-N.S0027v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0027-v10.pdf | + +### 10.2.25 N.S0028 Version 1.0.0 Network Interworking Between GSM MAP and ANSI-41 MAP Rev. B Revision: 0 (April 2002) + +3GPP2 document was superseded by X.S0023-B v1.0. + +### 10.2.26 N.S0029 Version 1.0.0 TIA/EIA-41 Based Network Enhancements for CDMA Packet Data Service (C-PDS), Phase 1 Revision: 0 (June 2002) + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with Packet Data Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0029 | 1.0.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TIA | TIA/EIA-IS-880 | | Published | --07-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0029-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0029-0 v1.0.zip | +| TTC | TS-3GB-N.S0029-0v1.0 | 1.0 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsns0029-0v10.pdf | + +## **10.2.27 N.S0030 Version 1.0.0 Enhanced Wireless 9-1-1 Phase 2 Revision: 0 (April 2002)** + +3GPP2 document was withdrawn. + +## **10.3 Packet Data Specifications** + +### **10.3.1 P.S0001-A Version 3.0.0 Wireless IP Network Standard (16 July 2001)** + +This standard defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification is based on P.R0001; cdma2000 Wireless IP Network Architecture based on IETF protocols. + +This standard defines the two methods for accessing Public networks (Internet) and Private networks (Intranets): Simple IP and Mobile IP, and the required Quality of Service and Accounting support. IETF protocols are widely employed whenever possible to minimize the number of new protocols required and to maximize the utilization of well accepted standards and hence the speed to market. Reference to the required IETF protocols is provided in Section 3 of this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-P.S0001-A | 3.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-835-A | | Published | --05-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-P.S0001-A v3.0.0 | 3.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-P.S0001-Av3.0.0.pdf | +| TTC | TS-3GB-P.S0001-Av3.0 | 3.0 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsp0001-A-v30.pdf | + +### **10.3.2 P.S0001-B Version 1.0.0 Wireless IP Network Standard (25 October 2002)** + +3GPP2 document superseded by X.S0011-C. + +### **10.3.3 P.S0001-B Version 2.0 cdma2000 Wireless IP Network Standard (September 2004)** + +3GPP2 document superseded by X.S0011-C. + +## **10.4 Services and system aspects specifications** + +### **10.4.1 S.R0003 Version 1.0.0 3GPP2 System Capability Guide Release A (20 January 2000)** + +3GPP2 document is re-numbered as SC.R2001-001 v1.0 + +#### **10.4.1.1 S.R0003-A Version 1.0 3GPP2 System Capability Guide Release B (14 June 2001)** + +This document is re-numbered as SC.R2002-001 v1.0 + +### **10.4.2 S.R0004 Version 1.0.0 Service Implementation Guide Revision: 0 (20 January 2000)** + +This Service Implementation document describes and defines features adopted by 3GPP2 TSG-S. The features descriptions may include both stage 1 and stage 2 functional levels. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0004 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0004v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0004v1.0.0.pdf | + +### 10.4.3 S.R0005-B Version 1.0 Network Reference Model for cdma2000 Spread Spectrum Systems Revision: B (16 April 2001) + +This document recommends the basic 3GPP2 Wireless Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0005-B | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TSB100-A | | Published | --03-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-S.R0005-B | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0005-B.zip | +| TTC | TS-3GB-S.R0005-Bv1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0005-B-v10.pdf | + +### 10.4.3.1 S.R0005-B Version 2.0 Network Reference Model for cdma2000 Spread Spectrum Systems Revision: B (May 2007) + +This document recommends the basic 3GPP2 Wireless Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0005-B v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0005-B v2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0005-B v2.0.zip | +| TTC | TS-3GB-S.R0005-Bv2.0 | 2.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0005-Bv2.0.pdf | + +### 10.4.4 S.R0006 Version 1.0.0 Wireless Features Description Revision: 0 (13 December 1999) + +This Standard presents a recommended plan for the implementation of Uniform Features for use in the Wireless Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonable consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0006 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-664-A | | Published | --12-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-S.R0006 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0006v1.0.0.pdf | +| TTC | JP-3GB-S.R0006 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0006.pdf | + +#### 10.4.4.1 S.R0006-000-A Version 1.0 Wireless Features Description (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-000-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-B-3[E] | 3 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-000-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-000-A.v1.0.zip | +| TTC | TS-3GB-S.R0006-000-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-000-Av1.0.pdf | + +#### 10.4.4.2 S.R0006-100-A Version 1.0 Wireless Features Description: General Background and Assumptions (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-100-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.100-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-100-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-100-A.v1.0.zip | +| TTC | TS-3GB-S.R0006-100-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-100-Av1.0.pdf | + +#### 10.4.4.3 S.R0006-501-A Version 1.0 Wireless Features Description: Call Delivery (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. + +system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-501-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.501-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-501-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-501-A v1.0.zip | +| TTC | TS-3GB-S.R0006-501-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-501-Av1.0.pdf | + +#### 10.4.4.4 S.R0006-502-A Version 1.0 Wireless Features Description: Call Forwarding-Busy (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-502-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.502-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-502-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-502-A v1.0.zip | +| TTC | TS-3GB-S.R0006-502-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-502-Av1.0.pdf | + +#### 10.4.4.5 S.R0006-503-A Version 1.0 Wireless Features Description: Call Forwarding-Default (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-503-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.503-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-503-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-503-A v1.0.zip | +| TTC | TS-3GB-S.R0006-503-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-503-Av1.0.pdf | + +#### 10.4.4.6 S.R0006-504-A Version 1.0 Wireless Features Description: Call Forwarding-No Answer (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-504-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-504-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-504-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-504-A v1.0.zip | +| TTC | TS-3GB-S.R0006-504-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-504-Av1.0.pdf | + +#### 10.4.4.7 S.R0006-505-A Version 1.0 Wireless Features Description: Call Forwarding-Unconditional (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-505-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-505-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-505-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-505-A v1.0.zip | +| TTC | TS-3GB-S.R0006-505-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-505-Av1.0.pdf | + +#### 10.4.4.8 S.R0006-506-A Version 1.0 Wireless Features Description: Call Transfer (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-506-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-506-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-506-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-506-A v1.0.zip | +| TTC | TS-3GB-S.R0006-506-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-506-Av1.0.pdf | + +#### 10.4.4.9 S.R0006-507-A Version 1.0 Wireless Features Description: Call Waiting (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-507-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-507-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-507-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-507-A v1.0.zip | +| TTC | TS-3GB-S.R0006-507-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-507-Av1.0.pdf | + +#### 10.4.4.10 S.R0006-508-A Version 1.0 Wireless Features Description: Calling Number Identification Presentation (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-508-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-508-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-508-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-508-A v1.0.zip | +| TTC | TS-3GB-S.R0006-508-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-508-Av1.0.pdf | + +#### 10.4.4.11 S.R0006-509-A Version 1.0 Wireless Features Description: Calling Number Identification Restriction (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-509-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-509-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-509-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-509-A v1.0.zip | +| TTC | TS-3GB-S.R0006-509-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-509-Av1.0.pdf | + +#### **10.4.4.12 S.R0006-510-A Version 1.0 Wireless Features Description: Conference Calling (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-510-A v1. | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-510-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-510-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-510-A v1.0.zip | +| TTC | TS-3GB-S.R0006-510-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-510-Av1.0.pdf | + +#### **10.4.4.13 S.R0006-511-A Version 1.0 Wireless Features Description: Do Not Disturb (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-511-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-511-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-511-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-511-A v1.0.zip | +| TTC | TS-3GB-S.R0006-511-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-511-Av1.0.pdf | + +#### **10.4.4.14 S.R0006-512-A Version 1.0 Wireless Features Description: Flexible Alerting (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. + +system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-512-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-512-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-512-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-512-A v1.0.zip | +| TTC | TS-3GB-S.R0006-512-Av1. | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-512-Av1.0.pdf | + +#### **10.4.4.15 S.R0006-513-A Version 1.0 Wireless Features Description: Message Waiting Notification (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-513-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-513-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-513-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-513-A v1.0.zip | +| TTC | TS-3GB-S.R0006-513-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-513-Av1.0.pdf | + +#### **10.4.4.16 S.R0006-514-A Version 1.0 Wireless Features Description: Mobile Access Hunting (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-514-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-514-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-514-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-514-A v1.0.zip | +| TTC | TS-3GB-S.R0006-514-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-514-Av1.0.pdf | + +#### **10.4.4.17 S.R0006-515-A Version 1.0 Wireless Features Description: Password Call Acceptance (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-515-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-515-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-515-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-515-A v1.0.zip | +| TTC | TS-3GB-S.R0006-515-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-515-Av1.0 | + +#### **10.4.4.18 S.R0006-516-A Version 1.0 Wireless Features Description: Preferred Language (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-516-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-516-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-516-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-516-A v1.0.zip | +| TTC | TS-3GB-S.R0006-516-Av1.0 | 1.0 | TTC Published | 0-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-516-Av1.0.pdf | + +#### **10.4.4.19 S.R0006-517-A Version 1.0 Wireless Features Description: Priority Access and channel Assignment (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-517-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-517-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-517-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-517-A v1.0.zip | +| TTC | TS-3GB-S.R0006-517-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-517-Av1.0.pdf | + +#### **10.4.4.20 S.R0006-518-A Version 1.0 Wireless Features Description: Remote Feature Control (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-518-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-518-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-518-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-518-A v1.0.zip | +| TTC | TS-3GB-S.R0006-518-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-518-Av1.0.pdf | + +#### **10.4.4.21 S.R0006-519-A Version 1.0 Wireless Features Description: Selective Call Acceptance (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-519-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-519-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-519-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-519-A v1.0.zip | +| TTC | TS-3GB-S.R0006-519-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-519-Av1.0.pdf | + +#### **10.4.4.22 S.R0006-520-A Version 1.0 Wireless Features Description: Subscriber PIN Access (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. + +system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-520-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-520-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-520-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-520-A v1.0.zip | +| TTC | TS-3GB-S.R0006-520-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-520-Av1.0.pdf | + +#### 10.4.4.23 S.R0006-521-A Version 1.0 Wireless Features Description: Subscriber PIN Intercept (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-521-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-521-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-521-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-521-A v1.0.zip | +| TTC | TS-3GB-S.R0006-521-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-521-Av1.0.pdf | + +#### 10.4.4.24 S.R0006-522-A Version 1.0 Wireless Features Description: Three Way Calling (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-522-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-522-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-522-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-522-A v1.0.zip | +| TTC | TS-3GB-S.R0006-522-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-522-Av1.0.pdf | + +#### **10.4.4.25 S.R0006-523-A Version 1.0 Wireless Features Description: Voice Message Retrieval (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-523.A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-523-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-523-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-523.A v1.0.zip | +| TTC | TS-3GB-S.R0006-523-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-523-Av1.0.pdf | + +#### **10.4.4.26 S.R0006-524-A Version 1.0 Wireless Features Description: Voice Privacy (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-524-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-524-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-524-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-524.A v1.0.zip | +| TTC | TS-3GB-S.R0006-524-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-524-Av1.0.pdf | + +#### **10.4.4.27 S.R0006-525-A Version 1.0 Wireless Features Description: Asynchronous Data Service (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-525-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-525-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-525-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-525-A v1.0.zip | +| TTC | TS-3GB-S.R0006-525-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-525-Av1.0.pdf | + +#### 10.4.4.28 S.R0006-526-A Version 1.0 Wireless Features Description: Calling Name Presentation (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-526-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-526-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-526-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-526-A v1.0.zip | +| TTC | TS-3GB-S.R0006-526-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-526-Av1.0.pdf | + +#### 10.4.4.29 S.R0006-527-A Version 1.0 Wireless Features Description: Calling Name Restriction (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-527-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-527-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-527-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-527-A v1.0.zip | +| TTC | TS-3GB-S.R0006-527-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-527-Av1.0.pdf | + +#### 10.4.4.30 S.R0006-528-A Version 1.0 Wireless Features Description: Data Privacy (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. + +system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-528-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-528-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-528-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-528-A v1.0.zip | +| TTC | TS-3GB-S.R0006-528-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-528-Av1.0.pdf | + +#### 10.4.4.31 S.R0006-529-A Version 1.0 Wireless Features Description: Emergency Services (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-529-A v1. | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-529-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-529-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-529-A v1.0.zip | +| TTC | TS-3GB-S.R0006-529-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-529-Av1.0.pdf | + +#### 10.4.4.32 S.R0006-530-A Version 1.0 Wireless Features Description: Group 3 Facsimile Service (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-530-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-530-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-530-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-530-A v1.0.zip | +| TTC | TS-3GB-S.R0006-530-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-530-Av1.0.pdf | + +#### 10.4.4.33 S.R0006-531-A Version 1.0 Wireless Features Description: Network Directed System Selection (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-531-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-531-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-531-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-531-A v1.0.zip | +| TTC | TS-3GB-S.R0006-531-A | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-531-Av1.0.pdf | + +#### 10.4.4.34 S.R0006-532-A Version 1.0 Wireless Features Description: Non-Public Service Mode (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-532-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-532-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-532-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-532-A v1.0.zip | +| TTC | TS-3GB-S.R0006-532-A v1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-532-Av1.0.pdf | + +#### 10.4.4.35 S.R0006-533-A Version 1.0 Wireless Features Description: Over-the-Air Service Provisioning (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-533-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-533-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-533-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-533-A v1.0.zip | +| TTC | TS-3GB-S.R0006-533-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-533-Av1.0.pdf | + +#### **10.4.4.36 S.R0006-534-A Version 1.0 Wireless Features Description: Service Negotiation (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-534-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-534-A | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-534-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-534-A v1.0.zip | +| TTC | TS-3GB-S.R0006-534-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-534-Av1.0.pdf | + +#### **10.4.4.37 S.R0006-535-A Version 1.0 Wireless Features Description: User Group (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-535-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-535-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-535-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-535-A v1.0.zip | +| TTC | TS-3GB-S.R0006-535-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-535-Av1.0.pdf | + +#### **10.4.4.38 S.R0006-536-A Version 1.0 Wireless Features Description: Group 3 Analog Fax (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. + +system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-536-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-536-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-536-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-536-A v1.0.zip | +| TTC | TS-3GB-S.R0006-536-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-536-Av1.0.pdf | + +#### 10.4.4.39 S.R0006-537-A Version 1.0 Wireless Intelligent Network Feature Descriptions (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-537-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-537-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-537-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-537-A v1.0.zip | +| TTC | TS-3GB-S.R0006-537-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-537-Av1.0.pdf | + +#### 10.4.4.40 S.R0006-601-A Version 1.0 Wireless Features Description: Short Message Deliver Point-to-Point Bearer Service (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-601-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-601-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-601-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-601-A v1.0.zip | +| TTC | TS-3GB-S.R0006-601-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-601-Av1.0.pdf | + +#### **10.4.4.41 S.R0006-602-A Version 1.0 Wireless Features Description: Wireless Messaging Teleservice (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-602-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-602-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-602-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-602-A v1.0.zip | +| TTC | TS-3GB-S.R0006-602-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-602-Av1.0.pdf | + +#### **10.4.4.42 S.R0006-603-A Version 1.0 Wireless Features Description: Wireless Paging Teleservice (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-603-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-603-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-603-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-603-A v1.0.zip | +| TTC | TS-3GB-S.R0006-603-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-603-Av1.0.pdf | + +#### **10.4.4.43 S.R0006-701-A Version 1.0 Wireless Features Description: Mobile Station Functionality (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-701-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-701-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-701-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-701-A v1.0.zip | +| TTC | TS-3GB-S.R0006-701-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-701-Av1.0.pdf | + +#### **10.4.4.44 S.R0006-801-A Version 1.0 Wireless Features Description: System Functionality (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-801-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-801-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-801-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-801-A v1.0.zip | +| TTC | TS-3GB-S.R0006-801-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-801-Av1.0.pdf | + +#### **10.4.4.45 S.R0006-802-A Version 1.0 Wireless Features Description: Subscriber Confidentiality (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-802-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-802-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-802-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-802-A v1.0.zip | +| TTC | TS-3GB-S.R0006-802-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-802-Av1.0.pdf | + +#### **10.4.4.46 S.R0006-803-A Version 1.0 Wireless Features Description: Network Services (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to + +system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-803-A v1. | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-803-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-803-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-803-A v1.0.zip | +| TTC | TS-3GB-S.R0006-803-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-803-Av1.0.pdf | + +#### **10.4.4.47 S.R0006-804-A Version 1.0 Wireless Features Description: Enhanced Security Services (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-804-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-804-A | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-804-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-804-A v1.0.zip | +| TTC | TS-3GB-S.R0006-804-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-804-Av1.0.pdf | + +#### **10.4.4.48 S.R0006-805-A Version 1.0 Wireless Features Description: CDMA Packet Data Service (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-805-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-805-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-805-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-805-A v1.0.zip | +| TTC | TS-3GB-S.R0006-805-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS-3GB-S.R0006-805-Av1.0.pdf | + +#### 10.4.4.49 S.R0006-806-A Version 1.0 Wireless Features Description: Over-the-Air Parameter Administration (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-806-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-806 | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0006-806-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0006-806-A v1.0.zip | +| TTC | TS-3GB-S.R0006-806-Av1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-806-Av1.0.pdf | + +#### 10.4.5 S.R0007 Version 1.0.0 User Selective Call Forwarding (Stage 1) Revision: 0 (13 December 1999) + +This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the User Selective Call Forwarding (USCF) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0007 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0007 v.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0007 v.1.0.zip | + +#### 10.4.5.1 S.R0007 Version 2.1 User Selective Call Forwarding (Stage 1) (31 January 2001) + +This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the User Selective Call Forwarding (USCF) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0007 v2.1 | 2.1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0007 v.2.1 | 2.1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0007 v.2.1.zip | +| TTC | TS-3GB-S.R0007v2.1 | 2.1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsr0007-v21.pdf | + +#### **10.4.6 S.R0008-0 Version 1.0.0 Answer Hold (Stage 1) Revision: 0 (13 December 1999)** + +This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the Answer Hold (AH) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0008 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0008 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0008_v1.0.zip | + +#### **10.4.6.1 S.R0008-0 Version 2.0 Answer Hold (Stage 1) Revision: 0 (8 December 2000)** + +This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the Answer Hold (AH) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0008 v2.1 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0008 V.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0008_v2.0.zip | +| TTC | JP-3GB-S.R0008 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0008.pdf | + +#### **10.4.7 S.R0009-0 v1.0 User Identity Module (Stage 1) Revision: 0 (13 December 1999)** + +This standard defines the enhancements required for the support of mobile stations equipped with User Identification Modules (UIM). The UIM provided functionality to certain types of mobile stations to enable them to operate in the wireless network. + +This document defines requirements for the wireless network to support operation of UIM equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of Mobile stations operating in the *TIA/EIA-41* environment and specific additional functionality unique to UIM-equipped mobile stations. + +The UIM can be in one of two forms, as either integrated within the mobile or removable that can be inserted or removed from the mobile equipment. This document addresses Removable UIM (R-UIM) only. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0009 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0009.zip | +| TTC | TS-3GB-S.R0009 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsr0009-v10.pdf | + +#### **10.4.8 S.R0010-0 Version 1.0.0 Preferred Language (Stage 1) Revision: 0 (13 December 1999)** + +Preferred Language (PL) provides the subscriber the ability to specify the language for network services. + +Network services which could be offered in the subscriber's preferred language include: + +- Recorded announcements +- Directory assistance +- Operator services +- Emergency services +- "Help" lines +- Message Waiting Notification +- CNIP *number not available* +- CNIP *number restricted* + +If the subscriber's preferred language is not available, service shall be provided in the default language, which shall be determined by the wireless network operator. + +PL does not impact a subscriber's ability to originate calls or to receive calls. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0010 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0010 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0010.zip | +| TTC | JP-3GB-S.R0010 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0010.pdf | + +#### **10.4.9 S.R0011-0 Version 1.0.0 Advice of Charge (Stage 1) Revision: 0 (13 December 1999)** + +This specification presents Stage-1 for supporting the Advice of Charge feature for use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Advice of Charge (AoC) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0011 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0011 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0011.zip | +| TTC | JP-3GB-S.R0011 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0011.pdf | + +#### **10.4.10 S.R0012-0 Version 1.0.0 Rejection of Undesired Annoying Calls (Stage 1) Revision: 0 (13 December 1999)** + +This specification presents Stage-1 for supporting Rejection of Undesired Annoying Calls feature for use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Rejection of Undesired Annoying Calls (RUAC) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0012 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0012 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0012.zip | +| TTC | JP-3GB-S.R0012 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0012.pdf | + +#### **10.4.11 S.R0013-0 Version 1.0.0 Global Emergency Call Origination (GECO) Revision: 0 (13 December 1999)** + +This document presents a Stage 1 description for a Global Emergency Call Origination (GECO) which will increase the probability that any user can originate a call to a Public Service Access Point (PSAP) even in those service areas where the Emergency Service Access Number (ESAN) is not known to the user. + +The intent of GECO is described as follows: + +- The MS may provide a means for the user to initiate an emergency call +- A special form of the call origination message (defined as a Global Emergency Call Origination Message (GECO\_MSG)) may be issued by the MS in lieu of the normal call origination message to indicate that the call origination being requested is an emergency call origination. GECO\_MSGs may be accepted and the GECO call connected by the network from both subscribed and unsubscribed mobiles. The system may support "implicit registration" for GECO calls such that the use of registration request/acceptance protocol is not required prior to the issuance of a GECO\_MSG. +- If the MS is currently registered on and accessing an operating network when the GECO call is initiated by the user, the MS may use that system to initiate the GECO call. If the MS is not currently accessing a system, the MS may attempt to access its preferred service as indicated by its internal system selection and system access restriction programming to maximize the probability that the GECO call will be accepted by the system. If no preferred system is available, the MS may override its internal system selection and system access restriction programming in an attempt to access any available system. +- Initiation of GECO call by the MS shall in no way degrade the user's access to any other feature/service which would normally be available to him from the accessed service provider's network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0013 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0013 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0013.zip | +| TTC | JP-3GB-S.R0013 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0013.pdf | + +#### **10.4.12 S.R0014-0 Version 1.0.0 Tandem Free Operation (Stage 1) Revision: 0 (13 December 1999)** + +It is expected that the need for Tandem Free Operations will be driven by the increasing market penetration of digital technologies which will result in an increase in percentage of mobile-to-mobile calls. In addition, given that the effects of tandem vocoding are greater for lower bit rate vocoders, the need for this feature becomes greater as the use of low bit rate vocoders increases. The Tandem Free Operation (TFO) feature, also known as Vocoder Bypass, improves the end-to-end voice quality observed in mobile-to-mobile voice calls in wireless networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0014 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0014 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0014.zip | +| TTC | JP-3GB-S.R0014 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0014.pdf | + +#### **10.4.13 S.R0015-0 Version 1.0.0 ISDN Interworking (Stage 1) Release A (13 December 1999)** + +This document presents Stage-1 (new chapter TTA/EIA-664-B) recommendations for supporting the ISDN Interworking feature use in Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting subscribers with the ISDN Interworking feature. This document defines the functional characteristics for interconnecting to ISDN in circuit-switched mode. The interworking function in ISDN packet mode, i.e., B-channel Packet is out of scope at present. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0015 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0015.zip | +| TTC | JP-3GB-S.R0015 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0015.pdf | + +#### **10.4.14 S.R0016-0 Version 1.0.0 Automatic Code Gapping (Stage 1) Revision: 0 (13 December 1999)** + +Automatic Code Gapping (ACG) is intended to provide a Network Entity, such as a Service Control Point (SCP) or Service Control Function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load-related or in response to a traffic engineering command as from a Service Management System (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0016 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0016 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0016.zip | + +#### **10.4.14.1 S.R0016-0 Version 2.0 Automatic Code Gapping (Stage 1) Revision: 0 (8 December 2000)** + +Automatic Code Gapping (ACG) is intended to provide a Network Entity, such as a Service Control Point (SCP) or Service Control Function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load-related or in response to a traffic engineering command as from a Service Management System (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0016 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0016 V.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0016_v2.0.zip | +| TTC | JP-3GB-S.R0016 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0016.pdf | + +#### **10.4.15 S.R0017-0 3G Wireless Network Management System High Level Requirements Revision: 0 (13 December 1999)** + +This report specifies the 3G Wireless Network Management System High Level Requirements Including: OAM&P TMN Applications Required Network and Systems Management Processes and Network Reference Model (NRM). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0017 | | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0017 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0017.zip | +| TTC | TR-3GB-S.R0017-0v1.0 | 1.0 | TTC Published | 26-02-2002 | http://www.ttc.or.jp/imt2000/tr/trsr0017-0v10.pdf | + +#### **10.4.16 S.R0018-0 Version 1.0.0 Pre-Paid Charging (Stage 1) Revision: 0 (13 December 1999)** + +PPC allows the subscriber to pay for voice telecommunication services prior to usage. + +A PPC subscriber establishes an account with the service provider to access voice telecommunications services in home and roaming networks. Charges for voice telecommunication services are applied to the PPC account by decrementing the account in real time. The PPC subscriber may be notified about the account information at the beginning, during, or at the end of the voice telecommunications service. When the account balance is low the subscriber may be notified so that the subscriber may refill the account. When the account balance is below a pre-defined threshold, the subscriber's use of voice telecommunications services may be de-authorized. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0018 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0018.zip | +| TTC | JP-3GB-S.R0018 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0018.pdf | + +#### **10.4.17 S.R0019-0 Version 1.0.0 Location-Based Services System (LBSS) Stage 1 Description (22 September 2000)** + +This document defines LBSS for implementation in 3GPP2 systems. The location services functionality has been adopted from existing TR-45 standards as defined and also as described within the document. + +The scope of this document includes 3GPP2 system support required to facilitate Location-Based services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0019 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-S.R0019v1.0.0.pdf | +| TTC | JP-3GB-S.R0019 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0019.pdf | + +#### 10.4.18 S.R0021-0 Version 1.0 Video Streaming Service – Stage 1 (10 July 2000) + +The objective is to define and to standardize the functionality of Video Services that can be incorporated into the operations of wireless telecommunications networks. Audio-only streaming is a special case of video streaming. This document defines the functional characteristics and requirements of the video streaming services. The areas that must be defined are service features and system requirements, necessary for video streaming services to be provided in wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0021 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0021 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-S.R0021v1.0.pdf | +| TTC | JP-3GB-S.R0021 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0021.pdf | + +#### 10.4.18.1 S.R0021-0 Version 2.0 Multimedia Streaming Service – Stage 1 (18 April 2002) + +The objective is to define and to standardize the functionality of Multimedia Services that can be incorporated into the operations of wireless telecommunications networks. Audio-only or video-only streaming are a special case of multimedia streaming. This document defines the functional characteristics and requirements of the multimedia streaming services. The areas that must be defined are service features and system requirements, necessary for multimedia streaming services to be provided in wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0021 | 2.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0021-0_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0021-0_v2.0.zip | +| TTC | TS-3GB-S.R0021-0v2.0 | 2.0 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0021-0v20.pdf | + +#### 10.4.19 S.R0022-0 Version 1.0 Video Conferencing Service (10 July 2000) + +The objective is to define and to standardize the functionality of Video Services that can be incorporated into the operations of wireless telecommunications networks. This report defines the functional characteristics and the requirements of the video conferencing services. The areas that must be defined are service features and system requirements in order for voice conferencing services to be provided in wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0022 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0022 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-S.R0022v1.0.pdf | +| TTC | JP-3GB-S.R0022 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0022.pdf | + +#### 10.4.20 S.R0023-0 Version 1.0 High-Speed Data Enhancements for cdma2000 1x – Data Only (9 June 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0023 | 1.0 | Published | -02-2002 | http://www.cesa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0023 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-_R0023v1.0.pdf | + +#### 10.4.20.1 S.R0023-0 Version 2.0 High-Speed Data Enhancements for cdma2000 1x – Data Only Stage 1 Requirements (5 December 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0023 v2.0 | 2.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0023_V2.PDF | +| CCSA | CWTS-MC-S.R0023 v2.0 | 2.0 | Published | -02-2002 | http://www.cesa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0023 v.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0023_v2.0.zip | + +#### 10.4.21 S.R0024-0 Version 1.0 Wireless Local Loop Stage 1 Description (22 September 2000) + +Wireless Local Loop (WLL) is a feature implementation using a serving system that utilizes a wireless connection to a wireless device, such as a mobile station or a network interface unit to provide local loop service to an end user. WLL permits local loop service for subscriber call origination and for receipt of calls. WLL applies to voice and data services. WLL provides signalling mechanisms between the serving system and the mobile station or the network interface unit. This signalling mechanism permits the exchange of call control information. + +The essential signalling elements of WLL are: + +- Mobile station or Network interface unit Device Type specification and request for WLL of the serving system or optional serving system Device Type specification +- Mobile Station or Network interface unit Dial Tone or optional Dial Tone of the serving system + +- Mobile Station or Network interface unit Hook Status enabling WLL call control of the serving system +- Serving system Autonomous Message Interval specification and request of the mobile station or the network interface unit or optional network interface unit Autonomous Message Interval specification +- Serving system Call Waiting Indicator notification to the mobile station or the network interface unit. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0024 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0024 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-S.R0024v1.0.pdf | + +#### 10.4.22 S.R0025-0 Version 1.0 Wireless Pay Phone Stage 1 Description (22 September 2000) + +Wireless Pay Phone is a public telecommunications service feature that allows mobile station support of pay phone applications. The Wireless Pay Phone feature is useful to subscribers that originate or receive calls at a pay phone. + +The feature may be comprised of two signalling capabilities. The first signalling capability is that which allows a serving system to convey answer supervision. The second signalling capability is that which allows a serving system to meter calls. + +NOTE – A serving system may convey answer supervision using Alert-signaled or Flash-signaled Line Control. A serving system may meter using Alert-signaled or Flash-signaled Meter Pulses. + +Answer element of supervision is used by the mobile station to convey line polarity, which is useful as an answer supervision indication. Line Control specification and notification of the mobile station enables specification of Polarity Included, Toggle Mode, Reverse Polarity and Power Denial Time. These are specified in IS-95B section 7.7.5.15. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0025 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0025 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-S.R0025v1.0.pdf | + +#### 10.4.23 S.R0026-0 Version 1.0 High Speed Data Enhancements for cdma2000 1x-Integrated Data and Voice Stage 1 Requirements (17 October 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x-evolved high-speed integrated data and voice (1xEV-DV). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This document is intended as a guide for 3GPP2 TSGs in the development of specifications for high-speed integrated data and voice systems beyond cdma2000 1x services (voice, fax, circuit switched data), to provide increased spectral efficiency and the capability to satisfy customer demand for wireless voice and packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0026 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0026 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0026.zip | + +#### **10.4.24 S.R0027-0 Version 1.0 Personal Mobility Stage 1 Requirements (8 December 2000)** + +The objective is to define and standardize the functionality of personal mobility that can be incorporated into the operations of both 2G/3G TTA/EIA-41 and 2G/3G GSM-derived wireless telecommunications networks. This document defines the requirements of personal mobility features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0027 | 1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0027 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0027.zip | +| TTC | JP-3GB-S.R0027 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0027.pdf | + +#### **10.4.25 S.S0028-0 Version 1.0 OAM&P for cdma2000 (3GPP Delta Specification) (18 April 2001)** + +This document contains the OAM&P requirements and interface definitions for cdma2000-based systems. It is an extension of operations and maintenance requirements, per latest 3GPP 32-series specifications capabilities to enable operation in a cdma2000 systems environment as part of the TTA/EIA/IS-2000 family of standards. They are in alignment with OAM&P Stage 1 IS-2000 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.S0028 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_S0028_v1.0.zip | +| TTC | JP-3GB-S.S0028v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-v10.pdf | + +#### **10.4.25.1 S.S0028-0 Version 2.0 OAM&P for cdma2000 (3GPP Delta Specification) (23 July 2001)** + +This document is intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.S0028 V.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_S0028_v2.0.zip | +| TTC | TS-3GB-S.S0028-0v2.0 | 2.0 | TTC Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v20.pdf | + +#### **10.4.25.2 S.S0028-0 Version 3.0 OAM&P for cdma2000 (3GPP Delta Specification) (11 March 2002)** + +This document is intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 3.0 | Published | -06-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.S0028-0 v3.0 | 3.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.S0028-0 v3.0.zip | +| TTC | TS-3GB-S.S0028-0v3.0 | 3.0 | TTC Published | 28-05-2002 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v30.pdf | + +#### **10.4.25.3 S.S0028-A Version 1.0 OAM&P for cdma2000 (3GPP R4 Delta Specification) Revision: A (12 December 2002)** + +This document is intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0028-A_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v1.0.zip | + +#### **10.4.25.4 S.S0028-A Version 2.0 OAM&P for cdma2000 (3GPP R4Delta Specification) Revision: A (20 February 2003)** + +This document is intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 2.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0028-A_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v2.0.zip | +| TTC | TS-3GB-S.S0028-Av2.0 | 2.0 | TTC Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsss0028-Av20.pdf | + +#### **10.4.25.5 S.S0028-A Version 3.0 OAM&P for cdma2000 (3GPP R4Delta Specification) Revision: A (20 February 2003)** + +This document is intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A v3.0.zip | +| TTC | S.S0028-A v3.0 | 3.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-av30.pdf | + +#### 10.4.25.6 S.S0028-000-B Version 1.0 OAM&P for cdma2000 (Overview) (17 February 2005) + +The present document is the overview component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- **S.S0028-000-B: "OAM&P for cdma2000 (Overview)";** +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-000-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-000-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-000-B v1.0.zip | +| TTC | TS-3GB-S.S0028-000-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-bv10.pdf | + +#### 10.4.25.7 S.S0028-000-B Version 2.0 OAM&P for cdma2000 (Overview) (18 July 2005) + +The present document is the overview component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- **S.S0028-000-B: "OAM&P for cdma2000 (Overview)";** +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-000-B v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.S0028-000-B v2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-000-B v2.0.zip | +| TTC | TS-3GB-S.S0028-000-Bv2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.S0028-000-Bv2.0.pdf | + +#### 10.4.25.8 S.S0028-000-C Version 1.0 OAM&P for cdma2000 (Overview) Revision: C (18 January 2006) + +The present document is the overview component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- **S.S0028-000-C: "OAM&P for cdma2000 (Overview)";** +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; + +2 cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the organizational partners (OPs) of 3GPP2. Geographically (and at the date of publication) cdma2000® is a registered trademark of the Telecommunication Industry Association (TIA-USA) in the United States. + +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-000-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-000-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-000-C v1.0.zip | +| TTC | TS-3GB-S.S0028-000-Cv1.0 | 1.0 | TTC Published | 02/06/06 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-cv10.pdf | + +#### 10.4.25.9 S.S0028-000-C Version 2.0 OAM&P for cdma2000 (Overview) Revision: C (October 2007) + +The present document is the overview component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- **S.S0028-000-C: "OAM&P for cdma2000 (Overview)";** +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-000-Cv2.0 | 2.0 | TTC Published | 28/11/2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.S0028-000-Cv2.0.pdf | + +#### 10.4.25.10 S.S0028-001-B Version 1.0 OAM&P for cdma2000 (3GPP R5 Delta Specification) (17 February 2005) + +The present document is the 3GPP R5 Delta Specification component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";** +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-001-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-001-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-B v1.0.zip | +| TTC | TS-3GB-S.S0028-001-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv10.pdf | + +#### 10.4.25.11 S.S0028-001-B Version 2.0 OAM&P for cdma2000 (3GPP R5 Delta Specification) Revision: B (18 July 2005) + +The present document is the 3GPP R5 Delta Specification component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";** +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-001-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-001-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-B v2.0.zip | +| TTC | S.S0028-001-B v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv20.pdf | + +#### 10.4.25.12 S.S0028-001-C Version 1.0 OAM&P for cdma2000 (3GPP R6 Delta Specification) Revision: C (18 January 2006) + +The present document is the 3GPP R6 Delta Specification component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)";** +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-001-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-001-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-C v1.0.zip | +| TTC | S.S0028-001-C v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-cv10.pdf | + +#### 10.4.25.13 S.S0028-001-C Version 2.0 OAM&P for cdma2000 (3GPP R6 Delta Specification) Revision: C (October 2007) + +The present document is the 3GPP R6 Delta Specification component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)";** +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; + +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-001-Cv2.0 | 2.0 | TTC Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0028-001-Cv2.0.pdf | + +#### 10.4.25.14 S.S0028-002-B Version 1.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) (17 February 2005) + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- **S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-002-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-002-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-002-B v1.0.zip | +| TTC | TS-3GB-S.S0028-002-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-bv10.pdf | + +#### 10.4.25.15 S.S0028-002-B Version 2.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) (18 July 2005) + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- **S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM)". + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-002-Bv2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0028-002-Bv2.0.pdf | + +#### 10.4.25.16 S.S0028-002-C Version 1.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) Revision: C (18 January 2006) + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; + +- **S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-002-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-002-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-002-C v1.0.zip | +| TTC | TS-3GB-S.S0028-002-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-cv10.pdf | + +#### **10.4.25.17 S.S0028-002-C Version 2.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) Revision: C (11 October 2007)** + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- **S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-002-Cv2.0 | 2.0 | TTC Published | 28-11-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.S0028-002-Cv2.0.pdf | + +#### **10.4.25.18 S.S0028-003-B Version 1.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) (17 February 2005)** + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-003-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-003-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-B v1.0.zip | +| TTC | TS-3GB-S.S0028-003-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv10.pdf | + +**10.4.25.19 S.S0028-003-B Version 2.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) +Revision: B (18 July 2005)** + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-003-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-003-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-B_v2.0.zip | +| TTC | S.S0028-003-B v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv20.pdf | + +**10.4.25.20 S.S0028-003-C Version 1.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) +Revision: C (18 January 2006)** + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-003-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-003-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-003-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-cv10.pdf | + +**10.4.25.21 S.S0028-003-C Version 2.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) +Revision: C (11 October 2007)** + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** + +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-003-Cv2.0 | 2.0 | TTC Published | 28/11/2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.S0028-003-Cv2.0.pdf | + +#### 10.4.25.22 S.S0028-004-B Version 1.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) (17 February 2005) + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-004-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-004-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-B_v1.0.zip | +| TTC | TS-3GB-S.S0028-004-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv10.pdf | + +#### 10.4.25.23 S.S0028-004-B Version 2.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) (17 February 2005) + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-004-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-004-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-B_v2.0.zip | +| TTC | S.S0028-004-B v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv20.pdf | + +#### 10.4.25.24 S.S0028-004-C Version 1.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) Revision: C (18 January 2006) + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-004-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-004-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-004-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-cv10.pdf | + +#### 10.4.25.25 S.S0028-004-C Version 2.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) Revision: C (11 October 2007) + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P Stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®2-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-004-Cv2.0 | 2.0 | TTC Published | 28-11-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.S0028-004-Cv2.0.pdf | + +#### 10.4.26 S.R0029 Version 1.0.0 Access Control Based on Call Type (22 September 2000) + +This document defines requirements for the cdma2000 Air Interface to support Access Control based on Call Type (ACCT). ACCT provides the control of access attempt from mobile stations by service option or a set of service options. + +Control for terminating calls to mobile stations are outside the scope of this feature description. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0029 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0029 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0029v1.0.0.pdf | +| TTC | TS-3GB-S.R0029v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0029-v10.pdf | + +#### **10.4.27 S.R0030 Version 1.0 Broadcast/Multicast Services – Stage 1 (22 August 2001)** + +The objective of this document is to define and to standardize the functionality of Broadcast/Multicast Services that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. This document defines the functional characteristics and requirements of Broadcast/Multicast services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0030 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.R0030-0 v1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE.3G-S.R0030-0 v1.0.zip | +| TTC | TS-3GB-S.R0030-0v1.0 | 1.0 | TTC Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0030-0v10.pdf | + +#### **10.4.27.1 S.R0030-A Version 1.0 Broadcast/Multicast Services – Stage 1 Revision A (15 January 2004)** + +The objective of this document is to define and to standardize the functionality of Broadcast/Multicast Services that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. This document defines the functional characteristics and requirements of Broadcast/Multicast services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0030-A v1.0 | 1 | Approved | 15-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0030-A v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0030-A v1.0.zip | +| TTC | TS-3GB-S.R0030-Av1.0 | 1.0 | TTC published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0030-av10.pdf | + +#### **10.4.28 S.R0032-0 Version 1.0 Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP) (6 December 2000)** + +This document defines requirements for the cdma2000 Air Interface to support Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP). ESA provides enhanced security in authentication and ESP provides enhanced privacy of user data. Selection of cryptographic algorithms is outside the scope of this feature description. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0032 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0032 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0032.zip | +| TTC | JP-3GB-S.R0032 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0032.pdf | + +#### 10.4.29 S.R0033-0 Version 1.0 Realm Configured Packet Data Session Dormancy Timer (06 December 2001) + +This document specifies the requirements for the operations of the RC-PDSDT (Realm Configured Packet Data Session Dormancy Timer) feature from the perspective of the user(s) and/or the system operator. The RC-PDSDT is a timer which is used to measure the duration of dormancy of a packet data session. The purpose of this timer is similar to the packet data inactivity timer specified in the C.S0017 standard. + +The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of cdma-2000 based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0033 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/O.1742/200306/MC | +| TTA | TTAT.3G-S.R0033-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0033-0 v1.0.zip | + +#### 10.4.30 S.R0034-0 Version 1.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (18 April 2001) + +These guidelines are based on the content of the ANSI TIA/EIA-41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*)). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0034 | 1.0 | Published | -02-02 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0034 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0034.zip | +| TTC | TS-3GB-S.R0034v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0034-v10.pdf | + +#### 10.4.30.1 S.R0034-0 Version 2.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (29 August 2002) + +These guidelines are based on the content of the ANSI TIA/EIA-41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*)). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. This is to facilitate international roaming and to minimize fraud. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0034 | 2.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0034-0_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0034-0_v2.0.zip | +| TTC | TS-3GB-S.R0034-0v2.0 | 2.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0034-0v20.pdf | + +#### 10.4.30.2 S.R0034-0 Version 3.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (26 July 2007) + +These guidelines are based on the content of the ANSI TIA/EIA-41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95* and *TIA/EIA/IS-2000*), and TDMA (*IS-54*, *IS-136*)). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. This is to facilitate international roaming and to minimize fraud. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0034-0 v3.0 | 3.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0034-0 v3.0 | 3.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0034-0 v3.0.zip | +| TTC | TS-3GB-S.R0034-0v3.0 | 3.0 | TTC Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/fee/TS/TS-3GB-S.R0034-0v3.0.pdf | + +#### 10.4.31 S.R0037-0 Version 2.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (14 May 2002) + +3GPP2 document superseded by S.R0037-0 Version 3. + +#### 10.4.31.1 S.R0037-0 Version 3.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (21 August 2003) + +This document recommends the basic 3GPP2 Wireless IP Network Architecture Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0037-0 v3.0 | 3.0 | Published | 21-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TSB-151 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0037-0 V3.0 | 3.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0037-0 v3.0.zip | +| TTC | TS-3GB-S.R0037-0V3.0 | 3.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0037-0v30.pdf | + +#### 10.4.31.2 S.R0037-B Version 1.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (June 2007) + +This document recommends the basic 3GPP2 Wireless IP Network Architecture Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0037-B v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0037-B V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0037-B v1.0.zip | + +### 10.4.32 S.R0048-0 Version 1.0 3G Mobile Equipment Identifier (MEID) (10 May 2001) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0048 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0048-0 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0048 v1.0.zip | +| TTC | TS-3GB-S.R0048v1.0 | 1.0 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0048-v10.pdf | + +#### 10.4.32.1 S.R0048-A Version 1.0 3G Mobile Equipment Identifier (MEID) (22 August 2003) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies becomes a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A v1.0 | 1 | Approved | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0048-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v1.0.zip | +| TTC | TS-3GB-S.R0048-AV1.0 | 1.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av10.pdf | + +#### 10.4.32.2 S.R0048-A Version 2.0 3G Mobile Equipment Identifier (MEID) Stage 1 (22 April 2004) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies becomes a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A v2.0 | 1 | Approved | 22-04-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-928-1 | | Approved | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0048-A V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v2.0.zip | +| TTC | TS-3GB-S.R0048-AV2.0 | 2.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av20.pdf | + +### 10.4.32.3 S.R0048-A Version 3.0 3G Mobile Equipment Identifier (MEID) Stage 1 (23 September 2004) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies becomes a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A | 3.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0048-A V3.0 | 3.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v3.0.zip | +| TTC | TS-3GB-S.R0048-AV3.0 | 3.0 | TTC published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av30.pdf | + +### 10.4.32.4 S.R0048-A Version 4.0 3G Mobile Equipment Identifier (MEID) Stage 1 (23 June 2005) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A | 4.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0048-A V4.0 | 4.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v4.0.zip | +| TTC | TS-3GB-S.R0048-AV4.0 | 4.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av40.pdf | + +### 10.4.33 S.R0051 Version 1.0 Enhanced Message Service (EMS) Stage 1 Description (25 July 2001) + +This document specifies the system requirements for Enhanced Message Service (EMS). + +The objective is to define and to standardize the functionality of this capability that can be incorporated into the operation of cdma2000-based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0051 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.R0051-0 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_R0051 v1.0.zip | +| TTC | TS-3GB-S.R0051-0v1.0 | 1.0 | TTC Published | 22-28-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0051-0v10.pdf | + +#### **10.4.34 S.R0052-0 Version 1.0 System Release Guide for the Release (ALPHA) of the cdma2000 System Specifications (15 January 2004)** + +This document is re-numbered as SC.R2003-002 v1.0. + +#### **10.4.35 S.S0053-0 Version 1.0 Common Cryptographic Algorithms (21 January 2002)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0053-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0053-0_V1.0.PDF | +| TTA | TTAE.3G-S.S0053 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0053-0v1.0.pdf | + +#### **10.4.36 S.S0054-0 Version 1.0 Interface Specification for Common Cryptographic Algorithms (21 January 2002)** + +This document describes the interfaces to cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. The procedures are described in detail in Common Cryptographic Algorithms. + +The purpose of this specification is to describe the cryptographic functions without revealing the technical details that are subject to export controls under regional laws. It is intended that developers of 3GPP2 specifications for systems using these cryptographic functions use the information in this document in standards that are not subject to export restrictions. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0054-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0054-0_V1.0.PDF | +| TTA | TTAE.3G-S.S0054 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0054-0v1.0.pdf | + +#### **10.4.37 S.S0055-0 Version 1.0 Enhanced Cryptographic Algorithms (21 January 2002)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0055-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0055-0_V1.0.PDF | +| TIA | TIA-946 | | Published | -06-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-S.S0055 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0055-0v1.0.pdf | + +#### 10.4.37.1 S.S0055-A Version 1.0 Enhanced Cryptographic Algorithms (November 2003) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A v1.0 | 1 | Approved | --11-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0055-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A v1.0.zip | + +#### 10.4.37.2 S.S0055-A Version 2.0 Enhanced Cryptographic Algorithms (17 January 2005) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0055-A v2.0 | 2.0 | ARIB Published | 29-09-2005 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742_5/ARIB_STD-T64-S.S0055-A v2.0.pdf | +| CCSA | CCSA-TSD-MC-S.S0055-A | 2.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TTA | TTAT.3G-S.S0055-A V2.0 | 2.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A v2.0.zip | + +#### 10.4.37.3 S.S0055-A Version 3.0 Enhanced Cryptographic Algorithms (26 September 2005) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TIA | TIA-946-1 | | Published | -10-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0055-A V3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A v3.0.zip | + +#### **10.4.37.4 S.S0055-A Version 4.0 Enhanced Cryptographic Algorithms (January 2008)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-946-2 [E] | | Published | -03-2008 | http://www.tiaonline.org/standards/catalog/search.cfm | + +#### **10.4.38 S.R0057-0 Version 1.0 IP-based Service Architecture System Requirements (09 July 2002)** + +This document specifies the system requirements for the "IP-based Service Architecture" from the perspective of the user(s) and/or the network operator for the support of IP multimedia applications. + +IP multimedia applications are supported by IP multimedia sessions that use IP connectivity bearers of the All-IP network. This document identifies Stage 1 architectural requirements for the All IP network to support the applications. + +The objective is to define and to standardize the "IP-based Service Architecture" that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0057 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0057-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0057-0_v1.0.zip | +| TTC | TS-3GB-S.R0057-0v1.0 | 1.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0057-0v10.pdf | + +#### **10.4.39 S.R0058-0 Version 1.0 IP Multimedia Domain System Requirements (17 April 2003)** + +This document specifies the system requirements for and operations of the IP Multimedia Domain (IP-MM Domain) system. The IP Multimedia Domain system encompasses the mobile station, the access network, and the core network. The various major functions and capabilities of the IP-MM Domain system are discussed with a focus on the broad requirements that shall be met in providing those functions and capabilities. + +The requirements contained in this document apply to the complete IP Multimedia Domain system. Actual development of stage 2 and stage 3 work is expected to be done in a phased manner, with releases of the specifications containing successively more complete implementations of these requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0058 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0058_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0058_v1.0.zip | + +#### **10.4.40 S.R0059-0 Version 1.0 Legacy MS Domain – Step 1 System Requirements (16 May 2002)** + +This document specifies the system requirements for and operations of the initial release (step-1) of the Legacy MS Domain (LMSD) of the All-IP network. Each of the functional entities of the + +LMSD is described with respect to functionality, interfaces and the roles it plays in the functioning of the network. + +The requirements contained in this document apply only to the initial step of the LMSD. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0059 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0059-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0059-0_v1.0.zip | + +#### **10.4.41 S.R0060-0 Version 1.0 Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Testing Stage 1 Description (14 March 2002)** + +This document specifies the product conformance objectives to be met by the Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Test Specification. The overall objective of this activity is the development of an industry standard compliance test specification, which can be employed to ensure that R-UIM equipped handsets properly interface with various vendor provided R-UIM cards. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0060-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0060-0_V1.0.PDF | +| CCSA | CWTS-MC-S.R0060 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0060-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0060-0_v1.0.zip | + +#### **10.4.42 S.R0061-0 Version 1.0 Wireless Immediate Messaging Stage 1 Requirements (25 October 2002)** + +This document specifies the requirements for and operations of the immediate messaging feature from the perspective of the user(s) and/or the system operator. Immediate Messaging (IM) is one of the most popular services on the Internet because of its near real-time, interactive nature. IM, using Presence information, allows users to determine when their friends are online and communicate with them in near real-time. + +The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of 3GPP2-based wireless telecommunications networks. This document makes extensive use of the Internet terminology to ensure alignment with immediate messaging service description and behavior in Internet recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0061 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0061-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0061-0_v1.0.zip | + +#### **10.4.43 S.R0062-0 Version 1.0 Presence for Wireless Systems Stage 1 Requirements (30 October 2002)** + +This document defines Stage 1 level requirements of the presence service from the perspective of the user and the system operator, so that it may be incorporated into cdma2000-based wireless + +networks. This document limits itself to presence service and does not delve into other applications that make use of presence, such as instant messaging. + +Presence is an attribute related to, but quite different from mobility information, and is a service that can be exploited to create additional services. The presence service enables presence information to be made available to other users or services. This Stage 1 makes extensive use of Internet terminology to ensure alignment with the presence service description and behavior in Internet recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0062 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0062-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0062-0_v1.0.zip | + +#### **10.4.44 S.R0064-0 Version 1.0 Multimedia Messaging Services (MMS) Stage 1 Requirements (30 October 2002)** + +This document defines the Stage 1 description of the non real-time Multimedia Messaging Service (MMS). MMS will allow users to send and receive messages exploiting the whole array of media types available today, e.g., text, images, audio, and video, while also making it possible to support new content types as they become popular. A multimedia message (MM), as observed by the user, is a combination of one or more different media elements in a multimedia presentation that can be transferred without the requirements for the need to be transferred in real-time. The multimedia messaging service shall be capable of supporting current and future multimedia types, and exploit the advances being made in the multimedia technology, with additional mobile requirements. Stage one is the set of requirements seen primarily from the subscriber's and service providers' points of view. It includes information of relevance to network operators, media content suppliers, service providers, and terminal and network manufacturers. + +It contains core requirements for the Multimedia Messaging Service, sufficient to provide a complete service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0064-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0064-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0064-0_v1.0.zip | +| TTC | TS-3GB-S.R0064-0v1.0 | 1.0 | TTC Published | 14-02-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0064-0v10.pdf | + +#### **10.4.44.1 S.R0064-A Version 1.0 Multimedia Messaging Services (MMS) Stage 1 Requirements (22 April 2004)** + +This document defines the Stage 1 description of the non real-time Multimedia Messaging Service (MMS). MMS will allow users to send and receive messages exploiting the whole array of media types available today, e.g., text, images, audio, and video, while also making it possible to support new content types as they become popular. A multimedia message (MM), as observed by the user, is a combination of one or more different media elements in a multimedia presentation that can be transferred without the requirements for the need to be transferred in real-time. The multimedia messaging service shall be capable of supporting current and future multimedia types, and exploit the advances being made in the multimedia technology, with additional mobile requirements. Stage one is the set of requirements seen primarily from the subscriber's and service providers' points of view. It includes information of relevance to network operators, media content suppliers, service providers, and terminal and network manufacturers. + +It contains core requirements for the Multimedia Messaging Service, sufficient to provide a complete service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0064-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0064-A v1.0 | 1.0 | Approved | 15-11-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0064-A_v1.0.zip | + +#### **10.4.45 S.R0065-0 Version 1.0 Fast Call Set-up System Requirements (15 April 2002)** + +This document specifies the system requirements for Fast Call Setup. This feature allows accelerated process in call setup (bearer resource assignment), which is particularly beneficial when a connection is returned from dormancy as a result of a packet arrival to the wireless network. The feature can be considered as falling into the category of standing requirements for network performance improvement. + +The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. + +The Fast Call Setup feature is a set of enhancements/mechanisms that reduce the latency involved in MS-terminated and MS-originated call setup. + +Call Setup involves a set of signaling message exchanges between the Mobile Station, Base Station, and the Network in order to allocate resources and allow user communication to proceed. Each step of this process introduces delay that contributes to the end-to-end call setup latency. Enhancements that reduce the delay in each step of this process and enhancements that streamline this process result in reduced call setup latency which is beneficial to cdma2000 services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0065 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0065-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0065-0_v1.0.zip | +| TTC | TS-3GB-S.R0065-0v1.0 | 1.0 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0065-0v10.pdf | + +#### **10.4.46 S.R0066-0 Version 1.0 IP-Based Location Services Stage 1 Requirements (17 April 2003)** + +This version of the Stage 1 supports location through IP in current packet data connections offered in cdma2000. SIP-based services in the All-IP domain (MMD), such as VoIP, are not assumed to be supported. Thus deployment of IP-Based Location Services will be possible prior to a full standardization and deployment of MMD. By the same token, there is no concept of an "emergency call" in the current packet data domain. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0066-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TIA-1020 | | Approved | --04-2003 | http://www.ttaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0066-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0066-0_v1.0.zip | + +#### **10.4.47 S.R0068-0 Version 1.0 Link Layer Assisted Robust Header Compression Stage 1 Requirements (11 June 2002)** + +This document specifies the requirements for and operations of the Link Layer Assisted Header Compression (LLA HC) from the perspective of the user and the system operator. + +The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. + +The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the all-IP multimedia domain, although all-IP is not the only application. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0068 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0068-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0068-0 v1.0.zip | +| TTC | TS-3GB-S.R0068-0v1.0 | 1.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0068-0v10.pdf | + +#### **10.4.48 S.R0069-0 Version 1.0 Header Stripping and Generation Stage 1 Requirements (15 March 2002)** + +This document specifies the requirements for and operations of the header stripping and generation feature from the perspective of the user and the system operator. + +The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. + +The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the all-IP multimedia domain, although all-IP is not the only application. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0069 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0069-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0069-0 v1.0.zip | + +#### **10.4.49 S.R0070-0 Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002)** + +3GPP2 document is superseded by SC.R1003-0 v1.0. + +#### **10.4.50 S.R0071 Version 1.0 Legacy System Packet Data Surveillance Requirements Stage 1 Requirements (18 April 2002)** + +The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested. + +This document serves as a pointer to the appropriate Standards Development Organization (SDO) documents for Packet Data Surveillance (PDS) for 3GPP2 All-IP systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0071 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0071-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0071-0_v1.0.zip | + +#### **10.4.51 S.R0072-0 Version 1.0 All IP Packet Data Surveillance Requirements Stage 1 Requirements (18 April 2002)** + +The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested. + +This document serves as a pointer to the appropriate Standards Development Organization (SDO) documents for Packet Data Surveillance (PDS) for 3GPP2 All-IP systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0072 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0072-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0072-0_v1.0.zip | + +#### **10.4.52 S.R0073-0 Version 1.0 Internet Over-the-Air Handset Configuration Management (IOTA) Stage 1 (11 July 2002)** + +This document specifies the requirements for and operation of Internet based Over-the-Air Handset Configuration Management (IOTA HCM) from the perspective of the users and system operators. + +The objective of this document is to define the requirements of this feature for incorporation into the operations of cdma2000-based wireless telecommunications systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0073 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0073-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0073-0_v1.0.zip | +| TTC | TS-3GB-S.R0073-0v1.0 | 1.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0073-0v10.pdf | + +#### **10.4.53 S.R0074-0 Version 1.0 File Format for Multimedia Services (FFMS) Stage 1 Requirements (17 April 2003)** + +This document specifies the requirements for the file format for multimedia services (FFMS) feature from the perspective of the user(s) and/or the system operator. The objective is to define and to standardize the file that can be used for interchanging multimedia data in general multimedia services including the Multimedia Messaging Services and the Multimedia Streaming Services. Multimedia data will be stored in a single file. Employing a common file format also enables combined services. For example, a multimedia message is sent to and stored in a multimedia streaming server, and then it is used for streaming to a multimedia streaming client terminal. This document does not specify how this file format is used in specific services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0074 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0074_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0074_v1.0.zip | + +#### **10.4.54 S.R0075-0 Version 1.0 Accounting & Auditing ALL-IP System Requirements (17 April 2003)** + +This document specifies the system requirements for Accounting & Auditing in the All-IP Network Architecture Model (Nam – S.R0037-0). The AAA is the primary functional entity with respect to the Accounting & Auditing functionality, interfaces, and the role it plays in the support of facilities & services message accounting in the network. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0075-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0075-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0075-0_v1.0.zip | + +#### **10.4.55 S.S0078-0 Version 1.0 Common Security Algorithms (12 December 2002)** + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0078-0_V1.0.PDF | +| CCSA | CCSA-TSD-MC-S.S0078-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0078-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-0_v1.0.zip | + +#### **10.4.55.1 S.S0078-A Version 1.0 Common Security Algorithms (13 December 2004)** + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A_v1.0.zip | + +#### **10.4.55.2 S.S0078-A Version 2.0 Common Security Algorithms (17 January 2005)** + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-A v2.0 | 2.0 | ARIB Published | 29-09-2005 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742_5/ARIB_STD-T64-S.S0078-A_v2_0.pdf | +| CCSA | CCSA-TSD-MC-S.S0078-A | 2.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v2.0 | 2.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A_v2.0.zip | + +### 10.4.55.3 S.S0078-A Version 3.0 Common Security Algorithms (26 September 2005) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A_v3.0.zip | + +### 10.4.56 S.R0079-0 Version 1.0 Support for End-to-End QoS Stage 1 Requirements (13 May 2004) + +This document describes the requirements necessary to support E2E (End-to-End) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging, and extending where applicable, the standard IETF protocols for QoS. The proposed functionality described by the requirements include the use of int-serv, diff-serv, int-serv to diff-serv inter-working, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 Radio Link QoS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0079-0 v1.0 | 1 | Approved | 13-05-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0079-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0079-0_v1.0.zip | +| TTC | TS-3GB-S.R0079-0V1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0079-0v10.pdf | + +### 10.4.56.1 S.R0079-A Version 1.0 Support for End-to-End QoS Stage 1 Requirements (29 June 2006) + +This document describes the requirements necessary to support E2E (End-to-End) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging, and extending where applicable, the standard IETF protocols for QoS. The proposed functionality described by the requirements include the use of int-serv, diff-serv, int-serv to diff-serv inter-working, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 Radio Link QoS. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0079-A v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0079-A V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0079-A_v1.0.zip | +| TTC | TS-3GB-S.R0079-AV1.0 | 1.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0079-av10.pdf | + +#### 10.4.57 S.R0080-0 Version 1.0 cdma2000 Wideband Speech Codec Stage 1 Requirements (20 February 2003) + +Wideband speech and audio coding has been gaining popularity in recent years. The emergence of the 3rd generation cellular systems as well as increasing public demand for applications such as Wireless multimedia, Voice over IP, Videophone, ISDN teleconferencing systems, Multipoint interactive audiovisual communication and Audio streaming require improved voice quality and intelligibility. Multimedia services are among the main deliverables of 3G wireless communications. This implies the use of high Quality audio and speech in multimedia content. Even in 3G voice applications the introduction of wideband speech would be an important step for CDMA service providers to deliver speech quality beyond the traditional limits of wireline communication systems. + +This document describes the cdma2000 Wideband Speech Codec Stage-1 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0080-0v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0080-0_v1.pdf | +| CCSA | CCSA-TSD-MC-S.R0080-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0080-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0080-0_v1.0.zip | + +#### 10.4.58 S.R0082-0 Version 1.0 Enhanced Packet Data Air Interface Security (22 August 2003) + +This document defines requirements for the cdma2000 Air Interface to support Data Subscriber Authentication (DSA) and Data Privacy (DP) for packet data services. DSA provides enhanced security in authentication and DP provides enhanced privacy of user data. DSA provides mutual authentication between the Access Terminal and the serving Access Network. DP provides encryption to prevent signalling and user traffic from unauthorized disclosure, and to prevent hijacking of user data channels. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0082 v1.0 | 1 | Approved | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0082 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0082_v1.0.zip | +| TTC | TS-3GB-S.R0082-0V1.0 | 1.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0082-0v10.pdf | + +#### **10.4.59 S.R0083-0 Version 1.0 Broadcast-Multicast Service Security Framework (16 October 2003)** + +This document defines the security framework for the Broadcast-Multicast Services (BCMCS). The security framework provides a logical description of the security information, functions and protocols for BCMCS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0083-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0083-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0083-0 v1.0.zip | +| TTC | TS-3GB-S.R0083-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0083-0v1.0.pdf | + +#### **10.4.59.1 S.S0083-A Version 1.0 Broadcast-Multicast Service Security Framework (26 August 2004)** + +This document defines the security framework for the Broadcast-Multicast Services (BCMCS). The security framework provides a logical description of the security information, functions and protocols for BCMCS. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0083-A | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-1053 | | Published | --09-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0083-A V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0083-A v1.0.zip | +| TTC | TS-3GB-S.S0083-AV1.0 | 1.0 | TTC published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsss0083-av10.pdf | + +#### **10.4.60 S.R0084-0 Version 2.0 Prepaid Packet Data Service in cdma2000 Wireless IP Network, Stage 1 Requirements (18 September 2003)** + +Prepaid service allows the subscriber to pay for packet data services prior to usage. A prepaid subscriber establishes an account with the service provider to access packet data services in home and roaming networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0084-0v2.0 | 1 | Approved | 18-09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0084-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0084-0 v2.0.zip | +| TTC | TS-3GB-S.R0084-0V2.0 | 2.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0084-0v20.pdf | + +#### **10.4.61 S.R0086-A Version 1.0 IMS Security Framework (10 June 2004)** + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0086-Av1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0086-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.R0086-A v1.0.zip | +| TTC | TS-3GB-S.R0086-AV1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/ssr0086-Av10.pdf | + +#### 10.4.61.1 S.S0086-B Version 1.0 IMS Security Framework (08 December 2005) + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0086-B | 1 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1091 | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0086-B V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.S0086-B v1.0.zip | +| TTC | S.S0086-B V1.0 | 1.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/ssss0086-bv10.pdf | + +#### 10.4.62 S.R0087-0 Version 1.0 3GPP2 – WLAN Interworking Stage 1 Requirements (22 July 2004) + +This document describes requirements of interworking between 3GPP2 systems and Wireless Local Area Networks (WLANs). The intent of 3GPP2-WLAN interworking is to extend 3GPP2 packet data services and/or capabilities to the WLAN environment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0087-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0087-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.R0087-0 v1.0.zip | +| TTC | TS-3GB-S.R0087-0V1.0 | 1.0 | TTC published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/ssr0087-0v10.pdf | + +#### 10.4.62.1 S.R0087-A Version 1.0 cdma2000 – WLAN Interworking Stage 1 Requirements (23 February 2006) + +This document describes requirements of interworking between cdma2000® systems and Wireless Local Area Networks (WLANs). The intent of cdma2000-WLAN is to extend cdma2000 packet data and multimedia services and/or capabilities to the WLAN environment, and to support the handoff of voice calls between WLAN and cdma2000 1X circuit-switched (CS) environments. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0087-A v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0087-A v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.R0087-A v1.0.zip | +| TTC | TS-3GB-S.R0087-AV1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/ssr0087-av10.pdf | + +#### **10.4.63 S.R0090-0 Version 1.0 Network Initiated Data Session (NIDS) Stage 1 Requirements (10 June 2004)** + +This document defines the requirements for providing the Network Initiated Data Session (NIDS) capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R-0090-0 v1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0090-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0090-0 v1.0.zip | +| TTC | TS-3GB-S.R0090-0V1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0090-0v10.pdf | + +#### **10.4.64 S.R0092-0 Version 1.0 Legacy MS Domain Step 2 System Requirements (18 March 2004)** + +This document specifies the system requirements for and operations of the second release (Step-2) of the Legacy MS Domain (LMSD) of the All-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces, and the roles it plays in the functioning of the network. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0092-0 v1.0 | 1 | Approved | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0092-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0092-0 v1.0.zip | +| TTC | TS-3GB-S.R0092-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0092-0v10.pdf | + +#### **10.4.65 S.S0093-0 Version 1.0 cdma2000 Network Performance Measurement Types (11 December 2003)** + +This document defines the Performance Measurement Types applicable to CDMA and cdma2000 systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0093-0 v1.0 | 1 | Approved | 11-12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0093-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0093-0 v1.0.zip | +| TTC | TS-3GB-S.S0093-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsss0093-0v10.pdf | + +#### **10.4.65.1 S.S0093-0 Version 2.0 cdma2000 Network Performance Measurement Types Revision: 0 (18 January 2006)** + +This document defines the Performance Measurement Types applicable to CDMA and cdma2000® systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0093-0 v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0093-0 V2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.S0093-0 v2.0.zip | +| TTC | TS-3GB-S.S0093-0V2.0 | 2.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0093-0v20.pdf | + +#### **10.4.66 S.R0094-0 Version 1.0 Rm Interface Enhancements for cdma2000 System Requirements (17 February 2005)** + +This document specifies the system requirements for an enhanced Rm Interface. The objective is to define and to standardize the functionality of this interface for incorporation into the operations of cdma2000® based wireless telecommunications networks. + +The Rm Interface is between a Mobile Termination 2 (MT2) and a Terminal Equipment 2 (TE2). An MT2 is a cdma2000 network interface device, such as a hand-held phone. A TE2 is a general-purpose computer such as a laptop. The Rm Interface is currently specified in C.S0017 to support only a best effort, point-to-point packet data link assuming the presence of an RS-232 physical layer. Enhancements are needed to support applications hosted on the TE2 that require Quality-of-Service (QoS) from the cdma2000 network, and to support a network-layer interface that can be re-used across many different physical layer technologies. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0094-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0094-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.R0094-0 v1.0.zip | +| TTC | TS-3GB-S.R0094-0V1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0094-0v10.pdf | + +#### **10.4.67 S.R0095-0 Version 1.0 Support for IP Multimedia Services Identity Module (ISIM) on Universal Integrated Circuit Card (UICC) in 3GPP2 Systems Stage 1 Requirements (10 June 2004)** + +This document defines the enhancements required for the support of IMS capable mobile stations equipped with Universal Integrated Circuit Card (UICC). This document specifies the requirements and operations for the support of ISIM on UICC. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0095-0-v1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0095-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-S.R0095-0 v1.0.zip | +| TTC | TS-3GB-S.R0095-0V1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0095-0v10.pdf | + +#### **10.4.68 S.R0096-0 Version 1.0 Transcoder Free Operation Stage 1 Requirements (18 March 2004)** + +This document states that Transcoder Free Operation (TrFO) is the transport of compressed speech, from legacy mobiles, in a packet transport network through the elimination of unnecessary coding and decoding of the signal by intermediate elements in the bearer path. Transcoders may be associated either with the RAN or Media Gateway (MGW). By transporting only the compressed speech, TrFO achieves bandwidth efficiencies in the bearer stream and reduces round trip delays + +introduced by unnecessary transcoding. Also, TrFO may increase voice quality. TrFO is not applicable to VoIP. TrFO is a capability of the Legacy MS domain. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0096-0 v1.0 | 1 | Approved | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0096-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0096-0 v1.0.zip | +| TTC | TS-3GB-S.R0096-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/ssr0096-0v10.pdf | + +#### **10.4.69 S.R0100-0 Version 1.0 Push to Talk over Cellular (PoC) System Requirements (29 September 2005)** + +The PoC system level requirements specified in this document describe the requirements for PoC with respect to the Core Network, Radio Access Network, and Mobile Station. The system requirements support the application requirements and use cases specified by the OMA (Open Mobile Alliance). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0100-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0100-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0100-0 v1.0.zip | + +#### **10.4.70 S.R0101-0 Version 1.0 IOTA Device Management for cdma2000 Systems – Stage 1 Requirements (22 April 2004)** + +This document specifies the stage-1 Mobile Station (MS) and Operator requirements for the next release of IP Based Over-the-Air Handset Configuration standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0101-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0101-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0101-0 v1.0.zip | + +#### **10.4.71 S.R0103-0 Version 1.0 Network Firewall Configuration and Control (NFCC) Stage 1 Requirements (09 December 2004)** + +This document specifies the system requirements and operation of the Network Firewall Configuration and Control (NFCC) feature, from both the perspective of the subscriber and the system operator. The objective is to define and to standardize the functionality of this feature to be incorporated into the operations of cdma2000® based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0103-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TTA | TTAT.3G-S.R0103-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0103-0 v1.0.zip | +| TTC | TS-3GB-S.R0103-0V1.0 | 1.0 | TTC published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/ssr0103-0v10.pdf | + +#### **10.4.72 S.R0104-0 Version 1.0 HRPD Network Access Authentication for a Hybrid Access Terminal (HAT) with an R-UIM Used to Access Spread Spectrum Systems Requirements (21 October 2004)** + +A hybrid access terminal (referred to herein as a Hybrid Access Terminal, or HAT) is a device which can access both cdma2000® 1x and HRPD networks for packet data services. + +To access the cdma2000 1x network, a HAT that has an R-UIM uses R-UIM-supported CAVE-based authentication. To access the HRPD network, an optional network access authentication step may be required by the HRPD network. This optional step uses CHAP to exchange a challenge and response between the HAT and HRPD network. Currently, CHAP specifies that MD5 is used to compute the response. It is important to note that MD5 is not currently supported by all R-UIMs used to access a cdma2000 1x network. + +For an operator that deploys both cdma2000 1x and HRPD networks, there can be benefits to using common authentication credentials and authentication methods for accessing both networks. + +These requirements allow a properly configured HAT with an R-UIM to use CAVE-based authentication for access to both networks. These requirements specify the HAT authentication requirements and also the support required by the HRPD AN-AAA to authenticate such a HAT. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0104-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0104-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0104-0 v1.0.zip | +| TTC | TS-3GB-S.R0104-0V1.0 | 1.0 | TTC published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0104-0v10.pdf | + +#### **10.4.73 S.R0105-0 Version 1.0 Hot-lining Service (Packet Data) Stage 1 Requirements (08 December 2004)** + +This document specifies the system requirements for Hot-lining for packet data service. The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000® based wireless IP networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0105-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0105-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0105-0 v1.0.zip | +| TTC | TS-3GB-S.R0105-0V1.0 | 1.0 | TTC published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0105-0v10.pdf | + +#### **10.4.74 S.R0106-0 Version 1.0 Packet-Switched Video Telephony Stage 1 (21 July 2005)** + +This document defines the functional characteristics and the requirements of the packet-switched Video Telephony (VT) services, sometimes also referred to as Multimedia Conversational Services (MCS). Video Telephony is defined as one-to-one video/speech communication capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0106-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0106-0 V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0106-0_v1.0.zip | +| TTC | S.R0106-0 V1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0106-0v10.pdf | + +#### **10.4.74.1 S.R0106-0 Version 2.0 Packet-Switched Video Telephony Stage 1 (29 March 2007)** + +This document defines the functional characteristics and the requirements of the packet-switched Video Telephony (VT) services, sometimes also referred to as a Multimedia Conversational Services (MCS). Video Telephony is defined as one-to-one video/speech communication capability. VT (MCS) should be used as a basis for multiparty multimedia conferencing, but this is out of scope for the initial document revision. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0106-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0106-0 V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0106-0_v2.0.zip | +| TTC | TS-3GB-S.R0106-0V2.0 | 2.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.R0106-0v2.0.pdf | + +#### **10.4.75 S.R0108-0 Version 1.0 HRPD-cdma2000 1x Interoperability for Voice and Data System Requirements (23 February 2006)** + +This document defines the system requirements for HRPD-cdma2000 1x Interoperability for Voice and Data. The cellular network includes Multimedia Domain (MMD), Legacy Mobile Station Domain (LMSD) Support, and HRPD/cdma2000 1x radio access networks (RANs) for the delivery of voice, video, and data services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0108-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0108-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0108-0_v1.0.zip | +| TTC | TS-3GB-S.R0108-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0108-0v10.pdf | + +#### **10.4.75.1 S.R0108-0 Version 2.0 HRPD-cdma2000 1x Interoperability for Voice and Data System Requirements (17 May 2007)** + +This document defines the system requirements for HRPD-cdma2000 1x Interoperability for Voice and Data. The cellular network includes Multimedia Domain (MMD), Legacy Mobile Station Domain (LMSD) Support, and HRPD/cdma2000 1x radio access networks (RANs) for the delivery of voice, video, and data services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0108-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0108-0 V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0108-0 v2.0.zip | +| TTC | TS-3GB-S.R0108-0V2.0 | 2.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0108-0v2.0.pdf | + +#### **10.4.76 S.S0109-0 Version 1 Generic Bootstrapping Architecture (GBA) Framework (30 March 2006)** + +This document describes the security features and a mechanism to bootstrap keys for application security. The scope of this specification includes a generic bootstrapping function, an architecture overview and the detailed procedure on how to bootstrap the credential. The specification also describes a mechanism, called GBA\_U, to bootstrap keys inside the (R-)UIM as well as keys in the ME. GBA\_U requires GBA support in the (R-)UIM, but provides enhanced security by storing certain derived keys on the (R-)UIM. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0109-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-1098 | | Published | xx-01-2008 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0109-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0109-0 v1.0.zip | +| TTC | TS-3GB-S.S0109-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0109-0v10.pdf | + +#### **10.4.77 S.S0110-0 Version 1.0 IP-Based Location Services Security Framework (23 February 2006)** + +This document defines the security framework for the IP-based Location Services. The security framework provides a logical description of the security information, functions and protocols for IP-based Location Services. The architectural design of the network that supports these functions is outside the scope of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0110-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0110-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0110-0 v1.0.zip | +| TTC | TS-3GB-S.S0110-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0110-0v10.pdf | + +#### **10.4.78 S.R0111-0 Version 1.0 Expanded R-UIM Identifier (26 October 2005)** + +An expanded R-UIM identifier (EUM-ID) solution is needed in time to address issues associated with the impending exhaustion of the existing 32-bit UIM\_ID/ESN numbering space in CDMA networks. The purpose of introducing a new identifier is to define a larger numbering space, and also set the stage for moving away from the functions such as authentication and reverse long code mask generation. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0111-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0111-0 V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0111-0_v1.0.zip | +| TTC | S.R0111-0 V1.0 | 1.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/ssr0111-0v10.pdf | + +#### **10.4.78.1 S.R0111-0 Version 2.0 Expanded R-UIM Identifier Stage 1 Requirements (17 May 2007)** + +An expanded R-UIM identifier (EUIM-ID) solution is needed in time to address issues associated with the impending exhaustion of the existing 32-bit UIM\_ID/ESN numbering space in CDMA networks. The purpose of introducing a new identifier is to define a larger numbering space, and also set the stage for moving away from the functions such as authentication and reverse long code mask generation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0111-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0111-0 V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0111-0_v2.0.zip | +| TTC | TS-3GB-S.R0111-0V2.0 | 2.0 | TTC Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0111-0v2.0.pdf | + +#### **10.4.79 S.R0112-0 Version 1.0 Generic Bootstrapping Architecture System Requirements (08 December 2005)** + +This specification contains the high level requirements for the Generic Bootstrapping Architecture work. The aim of this work is to specify a general method of providing an application and a mobile with some shared keying material. The requirements on how the application and mobile use this shared keying material is out of scope of specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0112-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0112-0 V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0112-0_v1.0.zip | +| TTC | S.R0112-0 V1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/ssr0112-0v10.pdf | + +#### **10.4.80 S.R0113-0 Version 1.0 cdma2000 Enhanced Packet Data Air Interface System Requirements Document (25 May 2006)** + +3GPP2 document was withdrawn. + +#### **10.4.80.1 S.R0113-0 Version 2.0 cdma2000 Enhanced Packet Data Air Interface System Requirements Document (17 May 2007)** + +This document specifies the system requirements for the development of the cdma2000® Enhanced Packet Data Air Interface (E-PDAI) system. E-PDAI is a part of cdma2000 evolution effort. This document is intended to be used to guide the formal technical development of the E-PDAI air interfaced system and applicable IOS support. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0113-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0113-0 V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0113-0_v2.0.zip | +| TTC | TS-3GB-S.R0113-0V2.0 | 2.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.R0113-0v2.0.pdf | + +#### **10.4.81 S.S0114-0 Version 1.0 Security Mechanisms using GBA (30 March 2006)** + +This document describes profile of security mechanisms such that the mechanism can utilize keys that have been generated using the Generic Bootstrapping Architecture (GBA). GBA is a method of providing keys in a generic manner based on the 3GPP2 authentication methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0114-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-1097 | | Published | --01-2008 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0114-0 V1.0 | 1.0 | Approved | 02-15-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0114-0_v1.0.zip | +| TTC | TS-3GB-S.S0114-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0114-0v10.pdf | + +#### **10.4.82 S.R0115-0 Version 1.0 All-IP Network Emergency Call Support Stage 1 Requirements (14 September 2006)** + +This document specifies the system requirements for All-IP Network Emergency Call Support as described in [1]. With the introduction of VoIP in HRPD [2], WLAN [6], or other air interfaces, it is important to add support for emergency calls. The intent of this specification is to provide a general set of functionality with the flexibility needed to support variances in regional regulatory requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0115-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0115-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0115-0_v1.0.zip | +| TTC | TS-3GB-S.R0115-0V1.0 | 1.0 | TTC Published | 01-12-2006 | http://www.ttc.or.jp/imt2000/ts/tsr0115-0v10.pdf | + +#### **10.4.82.1 S.R0115-0 Version 2.0 All-IP Network Emergency Call Support Stage 1 Requirements (October 2007)** + +This document specifies the system requirements for All-IP Network Emergency Call Support as described in [1]. With the introduction of VoIP in HRPD [2], WLAN [6], or other air interfaces, it is important to add support for emergency calls. The intent of this specification is to provide a general set of functionality with the flexibility needed to support variances in regional regulatory requirements. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.R0115-0v2.0 | 2.0 | TTC Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0115-0v2.0.pdf | + +#### **10.4.83 S.R0117-0 Version 1.0 Multimedia Priority Service (MMPS) for MMD-based Networks – Stage 1 Requirements (29 June 2006)** + +The scope of this document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0117-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0117-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0117-0 v1.0.zip | +| TTC | TS-3GB-S.R0117-0V1.0 | 1.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/ssr0117-0v10.pdf | + +#### **10.4.84 S.R0118-0 Version 1.0 Telephone Number Mapping (ENUM) Stage 1 Requirements (25 May 2006)** + +The scope of this document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0118-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0118-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0118-0 v1.0.zip | +| TTC | TS-3GB-S.R0118-0V1.0 | 1.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/ssr0118-0v10.pdf | + +#### **10.4.85 S.R0120-0 Version 1.0 All IP System – MMD Policy Enhancements (September 2007)** + +Multimedia Domain (MMD) specifications enable an operator to apply Quality of Service (QoS) policy controls to the Internet Protocol (IP) Connectivity Access Network on session-based applications, and to provision flow-based charging rules at the Packet Data Serving node (PDSN). These current specifications are confined to the PDSN as the sole policy enforcement point supported. The scope of MMD policy needs to be expanded to include overall coordination of network resource usage for Session Initiation Protocol (SIP) and non-SIP applications for all subscribers, enhancements to policy contexts, and incorporation of additional network elements in the policy architecture. This document specifies the system requirements related to these MMD Policy Enhancements, which are intended to guide the associated technical specification development. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0120-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0120-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0120-0 v1.0.zip | + +#### **10.4.86 S.R0121-0 Version 1.0 Network Evolution for cdma2000 Networks System Requirements Document (17 May 2007)** + +The scope of this document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0121-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0121-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0121-0 v1.0.zip | +| TTC | TS-3GB-S.R0121-0V1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0121-0v1.0.pdf | + +#### **10.4.87 S.R0122-0 Version 1.0 Preferred Cryptographic Profiles (29 March 2007)** + +The scope of this document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0122-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0122-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0122-0 v1.0.zip | +| TTC | TS-3GB-S.R0122-0V1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0122-0v1.0.pdf | + +#### **10.4.88 S.R0123-0 Version 1.0 Enhanced MMD Security – Stage 1 Requirements (September 2005)** + +The scope of this document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0123-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0123-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0123-0 v1.0.zip | + +#### **10.4.89 SC.R1003-0 Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002)** + +This 3GPP2 document is renamed from S.R0070 Version 1.0. This document is to provide uniform procedures and guidance for the development, completion, distribution and approval of Work Items, Stage 1 and System Requirements across all TSGs. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R1003-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TS-3GB-SC.R1003-0v1.0 | 1.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsscr1003-0v10.pdf | + +#### **10.4.90 SC.R2001-001 Version 1.0 3GPP2 System Capability Guide Release A (20 January 2000)** + +This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2001-001 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2001-001 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-SC.R2001-001 v1.0.zip | + +#### **10.4.91 SC.R2002-001 Version 1.0 3GPP2 System Capability Guide Release B (14 June 2001)** + +This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2002-001 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2002-001 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-SC.R2002-001 v1.0.zip | + +#### **10.4.92 SC.R2003-002 Version 1.0 System Release Guide for the Release (ALPHA) of the cdma2000 System Specifications (15 January 2004)** + +This 3GPP2 document is renamed from document S.R0052-0 Version 1.0. This document is the System Release Guide (SRG) for the 3GPP2 wireless telecommunication system. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. The objective of this document is to provide an informative overview for and reference to the Release (ALPHA) of the 3GPP2 wireless telecommunication system (cdma2000) capabilities, features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2003-002 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2003-002 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-SC.R2003-002 v1.0.zip | +| TTC | TS-3GB-SC.R2003-002-0V1.0 | 1.0 | TTC Published | 08-25-2006 | http://www.ttc.or.jp/imt2000/ts/tsser2003-002-0v10.pdf | + +### **10.5 Core Network Specifications** + +#### **10.5.1 X.S0001-A Version 1.0 MAP Enhancements for CDMA Packet Data Services (C-PDS) (April 2004)** + +This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0001-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-880-A | 0 | Published | 07-09-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0001-A V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0001-A v1.0.zip | +| TTC | TS-3GB-X.S0001-AV1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0001-Av1.0.pdf | + +## 10.5.2 X.S0002-0 Version 1.0 TIA/EIA-41-D Location Services Enhancements (March 2004) + +This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0002-0 v1.0 | | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-881 | | Published | --03-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0002-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0002-0 v1.0.zip | +| TTC | TS-3GB-X.S0002-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/sxs0002-0v10.pdf | + +### 10.5.2.1 X.S0002-0 Version 2.0 MAP Location Services Enhancements (May 2006) + +This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0002-0 v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-881-1 [E] | | Published | --01-2008 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0002-0 V2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0002-0 v2.0.zip | +| TTC | TS-3GB-X.S0002-0V2.0 | 2.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/sxs0002-0v20.pdf | + +## 10.5.3 X.S0003-0 Version 1.0 One-Way Roaming from X.S0004 to GSM (January 2005) + +This document provides recommended *ANS/TIA/EIA-41-D* enhancements required to support *TIA/EIA-41* SIM (Subscription Identification Module) roaming one-way into *GSM* serving areas (without modification to the *GSM* serving network). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0003-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-868 | | Published | --01-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0003-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0003-0 v1.0.zip | +| TTC | TS-3GB-X.S0003-0V1.0 | 1.0 | TTC | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0003-0v10.pdf | + +#### 10.5.4 X.S0004-000-E Version 1.0.0 Introduction to TIA-41 (March 2004) + +This document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.000-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-000-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v1.0.0.zip | + +##### 10.5.4.1 X.S0004-000-E Version 2.0.0 Introduction to TIA-41 (March 2004) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.000-E-1[E] | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-000-E V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v2.0.zip | + +##### 10.5.4.2 X.S0004-000-E Version 3.0.0 Introduction to MAP (October 2005) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E | 3.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.000-E-2[E] | | Published | --08/2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-000-E V3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v3.0.zip | + +#### 10.5.4.3 X.S0004-000-E Version 4.0 Mobile Application Part (MAP) – Introduction (May 2006) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-000-E v4.0 | 4.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.000-E-3[E] | | Published | --11-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-000-E V4.0 | 4.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v4.0.zip | + +#### 10.5.4.4 X.S0004-000-E Version 5.0 Mobile Application Part (MAP) – Introduction (January 2007) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E v5.0 | 5.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.000-E-4[E] | 4 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-000-E V5.0 | 5.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v5.0.zip | + +#### 10.5.4.5 X.S0004-000-E Version 6.0 Mobile Application Part (MAP) – Introduction (July 2007) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E v6.0 | 6.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-000-E V6.0 | 6.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v6.0.zip | + +#### 10.5.4.6 X.S0004-200-E Version 1.0 Mobile Application Part (MAP) – Intersystem Handoff (May 2006) + +This specification defines intersystem handoff by describing the information flows between functional entities which occur in a number of intersystem handoff scenarios. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-200-E v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0004-200-E V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-200-E v1.0.zip | + +#### 10.5.4.7 X.S0004-290-E Version 1.0 Mobile Application Part (MAP) – Intersystem Handoff Annexes (May 2006) + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-290-E v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41-290-E | | Published | 02-02-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-290-E V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-290-E v1.0.zip | + +#### 10.5.4.8 X.S0004-321-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Delivery (January 2007) + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-321-E v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.321-E | 0 | Published | 07-09-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-321-E V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-321-E v1.0.zip | + +#### 10.5.4.9 X.S0004-322-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Forwarding (January 2007) + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-322-E v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.322-E | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-322-E V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-322-E v1.0.zip | + +#### **10.5.4.10 X.S0004-323-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Waiting (January 2007)** + +This Annex is normative and is considered part of the specification. + +#### **10.5.4.11 X.S0004-324-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Calling Number Identification, Calling Number Identification Restriction (January 2007)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-324-E v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.324-E | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-324-E V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-324-E v1.0.zip | + +#### **10.5.4.12 X.S0004-400-E Version 1.0 Operations Administration and Maintenance (July 2005)** + +This document defines the intersystem Operations, Administration, and Maintenance (OA&M) information flows and procedures required for intersystem trunk maintenance. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-400-E | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-41.400-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-400-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-400-E v1.0.zip | + +#### **10.5.4.13 X.S0004-500-E Version 1.0.0 Introduction to Signaling Protocols (March 2004)** + +This document introduces the signalling protocols for this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-500-E v1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.500-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-500-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-500-E v1.0.0.zip | + +#### **10.5.4.14 X.S0004-510-E Version 1.0.0 X.25 Transport Signaling Protocols (March 2004)** + +This document describes X.25 Transport Signaling Protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-510-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.510-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-510-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-510-E v1.0.0.zip | + +#### **10.5.4.15 X.S0004-511-E Version 1.0.0 ANS/SS7 Transport Signaling Protocols (March 2004)** + +This document describes ANS/SS7 Transport Signaling Protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-511-E v1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.511-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-511-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-511-E v1.0.0.zip | + +#### **10.5.4.16 X.S0004-512-E Version 1.0.0 ITU-T SS7 Transport Signaling Protocols (March 2004)** + +This document describes ITU-T SS7 Transport Signaling Protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-512-E V1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.512-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-512-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-512-E v1.0.0.zip | + +#### **10.5.4.17 X.S0004-520-E Version 1.0.0 TCAP Application Signaling Protocols (March 2004)** + +This document describes TCAP application signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-520-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.520-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-520-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-520-E v1.0.0.zip | + +#### **10.5.4.18 X.S0004-520-E Version 2.0 Mobile Application Part (MAP) TCAP Application Signaling Protocols (July 2007)** + +This document describes TCAP application signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-520-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-520-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-520-E v2.0.zip | + +#### 10.5.4.19 X.S0004-540-E Version 1.0.0 MAP Operations Signaling Protocols (March 2004) + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-540-E V1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.540-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-540-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-540-E v1.0.0.zip | + +#### 10.5.4.20 X.S0004-540-E Version 2.0 Mobile Application Part (MAP) Operations Signaling Protocols (July 2007) + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-540-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-540-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-540-E v2.0.zip | + +#### 10.5.4.21 X.S0004-550-E Version 1.0.0 MAP Parameters Signaling Protocols (March 2004) + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-550-E V1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.550-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-550-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-550-E v1.0.0.zip | + +#### 10.5.4.22 X.S0004-550-E Version 2.0 Mobile Application Part (MAP) Parameters Signaling Protocols (July 2007) + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-550-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-550-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-550-E v2.0.zip | + +#### **10.5.4.23 X.S0004-551-E Version 1.0.0 Parameter Types Signaling Protocols (March 2004)** + +This document provides the definitions of the parameter types used in this Standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-551-E V1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.551-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-551-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-551-E v1.0.0.zip | + +#### **10.5.4.24 X.S0004-590-E Version 1.0.0 MAP Compatibility Signaling Protocols (March 2004)** + +While this document outlines guidelines and rules, which will in the near term be beneficial to implementation of this standard, other activities which may impact these rules are in progress. As such, the remainder of this Section, "MAP Compatibility Guidelines and Rules" may be subject to change and revision based on future TIA-41 recommendations. This is to ensure that there is no long-term impediment to Cellular Radiotelecommunications networks to evolve and implement significant new functionality. Also, to better allow for the longer-term alignment of TIA-41 with emerging international standards. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-590-E V1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.590-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-590-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-590-E v1.0.0.zip | + +#### **10.5.4.25 X.S0004-600-E Version 1.0 Introduction to Procedures (July 2005)** + +This document describes the signaling and call processing procedures required to perform automatic roaming features and services. The messages required to perform the automatic roaming are defined in Part 540. Conformance with this document shall mean that a system's externally visible behavior is the same as the externally visible behavior of the abstract system described here. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-600-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.600-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-600-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-600-E v1.0.zip | + +#### **10.5.4.26 X.S0004-630-E Version 1.0 Basic Call Processing (July 2005)** + +This document describes the signaling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-630-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.630-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-630-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-630-E v1.0.zip | + +#### **10.5.4.27 X.S0004-630-E Version 2.0 Mobile Application Part (MAP) Basic Call Processing (July 2007)** + +This document describes the signaling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-630-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.7/ | +| TTA | TTAT.3G-X.S0004-630-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-630-E v2.0.zip | + +#### **10.5.4.28 X.S0004-640-E Version 1.0 Intersystem Procedures (July 2005)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-640-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.640-E | | Published | --12-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-640-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-640-E v1.0.zip | + +#### **10.5.4.29 X.S0004-640-E Version 2.0 Mobile Application Part (MAP) Intersystem Procedures (July 2007)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-640-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.7/ | +| TTA | TTAT.3G-X.S0004-640-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-640-E v2.0.zip | + +#### **10.5.4.30 X.S0004-641-E Version 1.0 Short Message Services (SMS) (July 2005)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-641-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.641-E | | Published | --12-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-641-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-641-E v1.0.zip | + +### 10.5.4.31 X.S0004-641-E Version 2.0 Mobile Application Part (MAP) Short Message Services (SMS) (July 2007) + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-641-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.7/ | +| TTA | TTAT.3G-X.S0004-641-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-641-E v2.0.zip | + +### 10.5.4.32 X.S0004-642-E Version 1.0 Segmentation (July 2005) + +This section describes procedures to allow the transmission of messages, which may or may not require Segmentation and Reassembly (S&R). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-642-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.642-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-642-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-642-E v1.0.zip | + +### 10.5.4.33 X.S0004-650-E Version 1.0 Common Voice Feature Procedures (July 2005) + +This section describes common voice feature procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-650-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.650-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-650-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-650-E v1.0.zip | + +### 10.5.4.34 X.S0004-651-E Version 1.0 Voice Feature Procedures (July 2005) + +This section describes modular procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-651-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.651-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-651-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-651-E v1.0.zip | + +### 10.5.4.35 X.S0004-651-E Version 2.0 Mobile Application Part (MAP) Voice Feature Procedures (July 2007) + +This section describes modular procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-651-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-651-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-651-E v2.0.zip | + +### 10.5.4.36 X.S0004-660-E Version 1.0 Wireless Intelligent Network (WIN) Procedures (July 2005) + +In addition to the specific procedures described in this part of the Standard, the functional entity call and service logic processing models provide a tool used by WIN architects to model a call and to understand and describe the distribution of functions between functional entities and functional entity relationships. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-660-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.660-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-660-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-660-E v1.0.zip | + +### 10.5.4.37 X.S0004-690-E Version 1.0 Operation Timer Values (July 2005) + +The following references provide a summary of the timers used for MAP operations. The timer values specified in this table are default values only and should be optimized for actual operating environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-690-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.690-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-690-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-690-E v1.0.zip | + +### 10.5.4.38 X.S0004-690-E Version 2.0 Mobile Application Part (MAP) Timers (July 2007) + +The following references provide a summary of the timers used for MAP operations. The timer values specified in this table are default values only and should be optimized for actual operating + +environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer). + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-690-E v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-690-E V2.0 | 2.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-690-E_v2.0.zip | + +#### 10.5.4.39 X.S0004-691-E Version 1.0 Annexes (July 2005) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-691-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E_v1.0.zip | + +#### 10.5.4.40 X.S0004-691-E Version 2.0 Annexes (September 2005) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-691-E V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E_v2.0.zip | + +#### 10.5.4.41 X.S0004-691-E Version 3.0 Mobile Application Part (MAP) Annexes for the 6XX Series (July 2007) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E v3.0 | 3.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-691-E V3.0 | 3.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E_v3.0.zip | + +#### 10.5.4.42 X.S0004-700-E Version 1.0.0 Wireless Intelligent Networks (March 2004) + +This document part of *TIA-41* defines the distributed functional plane (DFP) for the Wireless Intelligent Network (WIN). + +Specifically, the scope of this part of the Standard is: + +- 1) To define the WIN functional entities and the relationships applicable to WIN. +- 2) To specify a high level model description of call control function (CCF) activities required to establish and maintain communication paths for users. +- 3) To specify a high level model description of service switching function (SSF) activities required for interaction between the CCF and a service control function (SCF). +- 4) To specify WIN triggers and provide a high level model description of detection point processing. +- 5) To describe mobility management and radio access control functions in the context of WIN. +- 6) To illustrate how the WIN basic call state models interact with TIA-41 signaling. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-700-EV1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.700-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-700-EV1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-700-E v1.0.0.zip | + +#### 10.5.4.43 X.S0004-730-E Version 1.0.0 WIN Distributed Functional Model (March 2004) + +This document depicts the functional entities and relationships applicable to WIN. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-730-EV1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.730-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-730-EV1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-730-E v1.0.0.zip | + +#### 10.5.4.44 X.S0004-750-E Version 1.0.0 SSF/CCF Call and Service Logic Model (March 2004) + +This document describes WIN call and service logic processing in terms of call modelling and modelling of service logic processing. WIN call and service logic encompasses call and connection processing in the SSF/CCF, service logic execution in the SCF, and the use of supporting resources and data in the SRF and SDF, respectively. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-750-EV1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.750-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-750-EV1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-750-E v1.0.0.zip | + +#### 10.5.4.45 X.S0004-790-E Version 1.0.0 WIN Call Delivery (March 2004) + +This document describes how MS-to-MS call delivery can be modelled using the WIN Basic Call State Models (BCSMs). The message sequences shown in the annex are as in TIA-41. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-790-EV1.0.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.790-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-790-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-790-E v1.0.0.zip | + +### 10.5.5 X.S0006-0 Version 1.0 Map Support of Authentication and Key Agreement (AKA) (October 2005) + +Enhanced Subscriber Authentication (ESA) uses 3GPP Authentication and Key Agreement (AKA) procedures for mutual authentication of the MS and the network in the serving system. The successful execution of AKA results in the establishment of a security association (i.e., a set of security data) between the MS and the serving system. This enables a set of security services to be provided (e.g., data integrity of a signaling message, signaling information element encryption, user data encryption). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0006-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0006-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0006-0 v1.0.zip | +| TTC | TS-3GB-X.S0006-0V1.0 | 1.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0006-0v10.pdf | + +### 10.5.6 X.S0008-0 Version 1.0 Support for the Mobile Equipment Identity (MEID) (June 2004) + +TIA-41 support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0008-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-928-1 | | Published | --06-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0008-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0 v1.0.zip | +| TTC | TS-3GB-X.S0008-0V1.0 | 1.0 | TTC published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v10.pdf | + +### 10.5.6.1 X.S0008-0 Version 2.0 Map Support for the Mobile Equipment Identity (MEID) (October 2005) + +TIA-41 support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0008-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-928-2[E] | | Published | --01-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0008-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0 v2.0.zip | +| TTC | TS-3GB-X.S0008-0V2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v20.pdf | + +### 10.5.7 X.S0009-0 Version 1.0 Wireless Intelligent Network Support for Location Based Services (June 2004) + +The purpose of this document is to describe FAM, LBC, LBIS and ECR, and to specify the intersystem operations that enable a wireless system to provide these location-based services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0009-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-843 | | Published | --08-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0009-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0009-0 v1.0.zip | +| TTC | TS-3GB-X.S0009-0V1.0 | 1.0 | TTC published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0009-0v10.pdf | + +### 10.5.8 X.S0010-A Version 1.0 Pre-Paid charging Enhancements for Circuit-Switched Data and Short Message Services (05 January 2004) + +This document describes the additions and modifications to *TIA/EIA/IS-826*, Wireless Intelligent Network Capabilities for Pre-Paid Charging, to support circuit-switched data and short message services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0010-A v1.0 | 1 | Approved | 05-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-826-A | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0010-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0010-A v1.0.zip | +| TTC | TS-3GB-X.S0010-AV1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0010-av10.pdf | + +### 10.5.9 X.S0011-001-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Introduction (August 2003) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-001-C v1.0.0 | 1 | Approved | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-001-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv100.pdf | + +### **10.5.9.1 X.S0011-001-C Version 2.0 cdma2000 Wireless IP Network Standard: Introduction (July 2005)** + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-001-C | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-001-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v2.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv20.pdf | + +### **10.5.9.2 X.S0011-001-C Version 3.0 cdma2000 Wireless IP Network Standard: Introduction (October 2006)** + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-001-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-001-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v3.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv30.pdf | + +### **10.5.9.3 X.S0011-001-D Version 1.0 cdma2000 Wireless IP Network Standard: Introduction (February 2006)** + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-001-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-001-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-D v1.0.zip | +| TTC | TS-3GB-X.S0011-001-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-dv10.pdf | + +#### 10.5.9.4 X.S0011-002-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (August 2003) + +This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-002-C v1.0.0 | 1 | Approved | --08-03 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-002-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv100.pdf | + +#### 10.5.9.5 X.S0011-002-C Version 2.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (July 2005) + +This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-002-C | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-002-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-C v2.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv20.pdf | + +#### 10.5.9.6 X.S0011-002-C Version 3.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (October 2006) + +This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-002-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-002-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-C v3.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv30.pdf | + +### 10.5.9.7 X.S0011-002-D Version 1.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (February 2006) + +This document describes the basic IP access services: Simple IPv4/IPv6, MIP6 and MIP4 with Home Agent (HA) and/or Dynamic Home IP address Assignment. It also addresses the security requirements between the Wireless IP Network nodes: PDSN, HA and RADIUS servers. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-002-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-002-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-D v1.0.zip | +| TTC | TS-3GB-X.S0011-002-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-dv10.pdf | + +### 10.5.9.8 X.S0011-003-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (August 2003) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-003-C v1.0.0 | 1 | Approved | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-003-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv100.pdf | + +### 10.5.9.9 X.S0011-003-C Version 2.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (July 2005) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-003-C | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-003-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-C v2.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv20.pdf | + +#### 10.5.9.10 X.S0011-003-C Version 3.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (October 2006) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-003-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-003-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-C v3.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv30.pdf | + +#### 10.5.9.11 X.S0011-003-D Version 1.0 cdma2000 Wireless IP Network Standard: Data Mobility and Resource Management (February 2006) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-003-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-003-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-D v1.0.zip | +| TTC | TS-3GB-X.S0011-003-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-dv10.pdf | + +#### 10.5.9.12 X.S0011-004-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (August 2003) + +This document describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction + +techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-004-C V1.0.0 | 1 | Approved | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-004-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv100.pdf | + +### 10.5.9.13 X.S0011-004-C Version 2.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (July 2005) + +This document describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-004-C | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0011-004-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v2.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv20.pdf | + +### 10.5.9.14 X.S0011-004-C Version 3.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (October 2006) + +This document describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-004-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-004-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v3.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv30.pdf | + +### 10.5.9.15 X.S0011-004-D Version 1.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (February 2006) + +This document describes Flow Mapping/Treatment mechanisms and protocols used when more than one service connection is established between the MS and the PDSN. Furthermore, a signalling mechanism between the MS, the RAN, and the PDSN is presented in this document to support QoS on a per application flow basis. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for + +applications that require a synchronous flow of 20-ms frames, such as VoIP application. This document also specifies the requirement and procedures for MS and PDSN to support SO type 67. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-004-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-004-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-D v1.0.zip | +| TTC | TS-3GB-X.S0011-004-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-dv10.pdf | + +#### **10.5.9.16 X.S0011-005-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (August 2003)** + +This document describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-005-C v1.0.0 | 1 | Approved | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-005-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv1.0.0 | 1.0.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv100.pdf | + +#### **10.5.9.17 X.S0011-005-C Version 2.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (July 2005)** + +This document describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-005-C | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0011-005-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v2.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv20.pdf | + +#### **10.5.9.18 X.S0011-005-C Version 3.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (October 2006)** + +This document describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-005-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-005-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v3.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv30.pdf | + +### 10.5.9.19 X.S0011-005-D Version 1.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (February 2006) + +This document describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the described capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-005-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-005-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-D v1.0.zip | +| TTC | TS-3GB-X.S0011-005-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-dv10.pdf | + +### 10.5.9.20 X.S0011-006-C Version 1.0.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Service (August 2003) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-006-C V1.0.0 | 1 | Approved | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-006-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv1.0.0 | 1.0.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv100.pdf | + +### 10.5.9.21 X.S0011-006-C Version 2.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (July 2005) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-006-C | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-006-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-X.S0011-006-C v2.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/sxss0011-006-cv20.pdf | + +### 10.5.9.22 X.S0011-006-C Version 3.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (October 2006) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 1. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-006-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-006-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-X.S0011-006-C v3.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv3.0 | 3.0 | TTC Published | 23-02-3007 | http://www.ttc.or.jp/imt2000/ts/sxss0011-006-cv30.pdf | + +### 10.5.9.23 X.S0011-006-D Version 1.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (February 2006) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-006-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-006-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TAT.3G-X.S0011-006-D v1.0.zip | +| TTC | TS-3GB-X.S0011-006-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/sxss0011-006-dv10.pdf | + +### 10.5.10 X.S0012-0 Version 2.0 Legacy MS Domain Step 1 (March 2004) + +This recommendation supports the 3GPP2 All-IP Step 1 Evolution Path by providing Stage-1, 2 and 3 for the architecture identified. The Legacy MS Domain provides support for existing MSs in an IP core network environment. The Legacy MS Domain supports the features and capabilities provided in a legacy network in a manner transparent to the user. New features and capabilities supported by the IP core network may be made available to subscribers where they are supported by MS capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0012-0 v2.0 | 1 | Approved | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-872-A | | Published | --05-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0012-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0012-0 v2.0.zip | +| TTC | TS-3GB-X.S0012-0v2.0 | 2.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0012-0v20.pdf | + +### 10.5.11 X.S0013-000-0 Version 1.0 All-IP Core Network Multimedia Domain Overview (December 2003) + +This document contains the introduction of the Stage-1, Stage-2, and Stage-3 recommendations for the 3GPP2 All-IP Multimedia Domain. It includes an overview of the system elements and interfaces and lists the series of documents that provide the complete specifications for the core network portions of the MMD. Not all MMD entities and interfaces may be covered by this version of this series of specifications. The specific entities and interfaces covered by a particular version are identified in each of the individual specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-0v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.000 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-000-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-000-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v10.pdf | + +### 10.5.11.1 X.S0013-000-0 Version 2.0 All-IP Core Network Multimedia Domain Overview (July 2005) + +The Multimedia Domain (MMD) is a CDMA based wireless network providing 3rd generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-000-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-000-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v20.pdf | + +### 10.5.11.2 X.S0013-000-A Version 1.0 All-IP Core Network Multimedia Domain Overview (November 2005) + +The Multimedia Domain (MMD) is a collection of core network entities providing 3rd generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This + +document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0013-000-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-A v1.0.zip | + +### 10.5.11.3 X.S0013-002-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (December 2003) + +This document defines stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services in PLMNs and perhaps other networks. This document identifies the mechanisms to enable support for IP multimedia applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-002-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.002 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-002-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-002-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-002-0v10.pdf | + +### 10.5.11.4 X.S0013-002-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (November 2005) + +This document defines stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. Recommendation ITU-T I.130 describes a three-stage method for characterization of telecommunication services, and Recommendation ITU-T Q.65 defines stage 2 of the method. This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-IMS IP applications, the general approach is to adopt non-IMS specific IP based solutions. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-002-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0013-002-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-A v1.0.zip | + +### 10.5.11.5 X.S0013-003-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (December 2003) + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.003 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-003-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-003-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v10.pdf | + +### **10.5.11.6 X.S0013-003-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (July 2005)** + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. This document includes interactions between an Application Server and IP multimedia sessions. The IP Multimedia (IM) Subsystem stage 2 and stage 3 for the IP multimedia call control based on SIP and SDP are specified in other documents. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-003-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-003-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v20.pdf | + +### **10.5.11.7 X.S0013-003-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (November 2005)** + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. This document includes interactions between an Application Server and IP multimedia sessions. The IP Multimedia (IM) Subsystem stage 2 and stage 3 for the IP multimedia call control based on SIP and SDP are specified in other documents. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-003-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-A v1.0.zip | + +### **10.5.11.8 X.S0013-004-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (December 2003)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.004 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-004-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-004-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v10.pdf | + +### **10.5.11.9 X.S0013-004-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (July 2005)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | A-TSD-MC-X.S0013-004-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-004-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-004-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v20.pdf | + +### **10.5.11.10 X.S0013-004-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (November 2005)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-004-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-A v1.0.zip | + +### **10.5.11.11 X.S0013-005-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signaling flows and Message Contents (December 2003)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.005 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-005-0V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-0v1.0.zip | +| TTC | TS-3GB-X.S0013-005-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v10.pdf | + +### **10.5.10.12 X.S0013-005-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signaling flows and Message Contents (July 2005)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-005-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-0 v2.0.zip | +| TTC | 3GB-X.S0013-005-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v20.pdf | + +### **10.5.11.13 X.S0013-005-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signaling flows and Message Contents (November 2005)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-005-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-A v1.0.zip | + +### **10.5.11.14 X.S0013-006-0 Version 1.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (December 2003)** + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.006 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-006-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-006-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v10.pdf | + +### 10.5.11.15 X.S0013-006-0 Version 2.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (July 2005) + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-006-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-006-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v20.pdf | + +### 10.5.11.16 X.S0013-006-A Version 1.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (November 2005) + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to the Cx interface between the I-CSCF/S-CSCF and the HSS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-006-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-A v1.0.zip | + +### 10.5.11.17 X.S0013-007-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Charging Architecture (December 2003) + +This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of this document are: to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-007-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0013-007-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-007-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-007-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-007-0v10.pdf | + +### **10.5.11.18 X.S0013-007-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Charging Architecture (November 2005)** + +This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of this document are: to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-007-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-007-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-007-A v1.0.zip | + +### **10.5.11.19 X.S0013-008-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Accounting Information Flows and Protocol (December 2003)** + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.008 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-008-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-008-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v10.pdf | + +### **10.5.11.20 X.S0013-008-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Accounting Information Flows and Protocol (July 2005)** + +This document covers offline charging for the IMS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-008-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-008-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v20.pdf | + +### **10.5.11.21 X.S0013-008-A Version 1.0 All-IP Core Network Multimedia Domain Offline Accounting Information Flows and Protocols (November 2005)** + +This document covers offline charging for the IMS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-008-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-A v1.0.zip | + +**10.5.11.22 X.S0013-010-0 Version 1.0 All-IP Core Network Multimedia Domain IP +Multimedia Subsystem Sh Interface; Signaling flows and message contents – +Stage 2 (December 2003)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signaling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TIA-873.010 | | Published | --12-2003 | http://www.ttaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-010-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-010-0v1.0 | 1.0 | TTC Published | 2-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v10.pdf | + +**10.5.11.23 X.S0013-010-0 Version 2.0 All-IP Core Network Multimedia Domain IP +Multimedia Subsystem Sh Interface; Signaling flows and message contents – +Stage 2 (July 2005)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signaling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-010-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-010-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v20.pdf | + +**10.5.11.24 X.S0013-010-A Version 1.0 All-IP Core Network Multimedia Domain IP +Multimedia Subsystem Sh Interface; Signaling flows and message contents – +Stage 2 (November 2005)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signaling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-010-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-A v1.0.zip | + +### **10.5.11.25 X.S0013-011-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (December 2003)** + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-0 v1.0 | 1 | Approved | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TIA-873.011 | | Published | --12-2003 | http://www.ttaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-011-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-011-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v10.pdf | + +### **10.5.11.26 X.S0013-011-0 Version 2.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (July 2005)** + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-0 | 2.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-011-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-011-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v20.pdf | + +### **10.5.11.27 X.S0013-011-A Version 1.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (November 2005)** + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-A | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-011-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-A v1.0.zip | + +### 10.5.12 X.S0014-E Version 1.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (December 2004) + +This document describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0014-E | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-124E | | Published | --05-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0014-E V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0014-E v1.0.zip | +| TTC | TS-3GB-X.S0014-Ev1.0 | 1.0 | TTC Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0014-ev10.pdf | + +### 10.5.12.1 X.S0014-E Version 2.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (August 2006) + +This document describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0014-E v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0014-E V2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0014-E v2.0.zip | +| TTC | TS-3GB-X.S0014-Ev2.0 | 2.0 | TTC Published | 01-12-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0014-ev20.pdf | + +### 10.5.13 X.S0016-000-A Version 1.0 3GPP2 Multimedia Messaging System MMS Specification Overview, Revision A (May 2003) + +This document describes the Multimedia Messaging System (MMS) specification documents for 3GPP2. It provides references to the Stage 1 (Requirements), Stage 2 (Functional Description), and one or more Stage 3 (Technical Realization) documents that collectively represent the MMS specification for 3GPP2 systems. The Multimedia Messaging System is distributed within many documents, with a simple multi-level hierarchy. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-000-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-000-A | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-000-A V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-000-A v1.0.zip | + +### 10.5.13.1 X.S0016-000-B Version 1.0 3GPP2 Multimedia Messaging System MMS Specification Overview, Revision B (June 2004) + +This document describes the Multimedia Messaging System (MMS) specification documents for 3GPP2. It provides references to the Stage 1 (Requirements), Stage 2 (Functional Description), and one or more Stage 3 (Technical Realization) documents that collectively represent the MMS specification for 3GPP2 systems. The Multimedia Messaging System is distributed within many + +documents, with a simple multi-level hierarchy. The purpose of this section is to introduce the readers to the contents of the whole document. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-000-B v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-000-B V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-000-B v1.0.zip | +| TTC | TS-3GB-X.S0016-000-Bv1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016-000-Bv1.0.pdf | + +### 10.5.13.2 X.S0016-000-C Version 1.0 Multimedia Messaging Service – Overview (January 2006) + +This document describes the Multimedia Messaging System (MMS) specification documents for 3GPP2. It provides references to the Stage 1 (Requirements), Stage 2 (Functional Description), and one or more Stage 3 (Technical Realization) documents that collectively represent the MMS specification for 3GPP2 systems. The Multimedia Messaging System is distributed within many documents, with a simple multi-level hierarchy. The purpose of this section is to introduce the readers to the contents of the whole document. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-000-C v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-000-C V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-000-C v1.0.zip | + +### 10.5.13.3 X.S0016-101-0 Version 1.0 Multimedia Messaging Service – MM10 Interface Based on Diameter Protocol – Stage 3 (January 2006) + +This document defines the procedures and transport protocol for use in the Multimedia Messaging Service (MMS) based on Diameter. This document is applicable to the MM10 interface between an MMS Relay/Server and the MSCF. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-101-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-101-0 V1. | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-101-0 v1.0.zip | + +### 10.5.13.4 X.S0016-102-0 Version 1.0 Multimedia Messaging Service – MM10 Interface Based on RADIUS Protocol – Stage 3 (January 2006) + +This document defines the procedures and transport protocol for use in the Multimedia Messaging Service (MMS) based on Diameter. This document is applicable to the MM10 interface between an MMS Relay/Server and the MSCF. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-102-0 v1. | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-102-0 V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-102-0 v1.0.zip | + +### **10.5.13.5 X.S0016-200-0 Version 1.0 MMS Stage 2 Functional Description (03 April 2003)** + +This document defines the stage 2 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. This document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +This document contains the core functions for a non-realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-200-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-200 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-200-0 V1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-200-0 v1.0.zip | + +### **10.5.13.6 X.S0016-200-0 Version 2.0 MMS Stage 2 Functional Description (June 2004)** + +This document defines the stage 2 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. This document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +This document contains the core functions for a non-realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-200-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-200-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-200-0 v2.0.zip | + +### **10.5.13.7 X.S0016-200-A Version 1.0 Multimedia Messaging Service – Stage 2 Functional Description (January 2006)** + +This document defines the stage 2 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. This document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +This document contains the core functions for a non-realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-200-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-200-A V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-200-A v1.0.zip | + +### **10.5.13.8 X.S0016-310-0 Version 1.0 MMS MM1 Stage 3 Using OMA/WAP (03 April 2003)** + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and server and device manufacturers. The document contains the core protocol and formats for interoperability between a device client and an MMS Relay/Server. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-310-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-310 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-310-0 v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-310-0 v1.0.zip | + +### 10.5.13.9 X.S0016-310-0 Version 2.0 MMS MM1 Stage 3 Using OMA/WAP (June 2004) + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and server and device manufacturers. The document contains the core protocol and formats for interoperability between a device client and an MMS Relay/Server. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-310-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-310-A | 1 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-310-0 V2.0 | 2.0 | Approved | 15-11-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-310-0 v2.0.zip | + +### 10.5.13.10 X.S0016-311-0 Version 1.0 MMS MM1 Stage 3 Using M-IMAP for Message Submission and Retrieval (14 April 2003) + +This specification defines a technical realization of the MMS MM1 interface for Message Submission and Message Retrieval. The methods defined within this document are independent of and may be used with any particular delivery notification method, as section 3.9 explains. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-311-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-311 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-311-0 V1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-311-0 v1.0.zip | + +### 10.5.13.11 X.S0016-312-0 Version 1.0 MMS MM1 Stage 3 Using SIP (June 2004) + +This specification defines a technical realization of the MMS MM1 interface for Message Submission, Message Notification, Message Acknowledgement, Message Retrieval, Message Delivery Reporting and Message Read Reporting. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-312-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-312-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-312-0 v1.0.zip | + +### 10.5.12.12 X.S0016-330-0 Version 1.0 MMS MM1 Stage 3 for Internet Mail Exchange (June 2004) + +This specification describes how to use MM3 to exchange messages with Internet mail systems. This includes translation between MMS and Internet Mail messages using Extended Simple Mail Transfer Protocol [SMTP] and Internet mail format [Msg-Fmt]. This protocol is a Stage 3 on reference point MM3 to exchange messages with systems in Internet Message format. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-330-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-330-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-330-0 v1.0.zip | + +### 10.5.13.13 X.S0016-330-A Version 1.0 Multimedia Messaging Service – MM3 Stage 3 for Internet Mail Exchange (January 2006) + +This specification describes how to use MM3 to exchange messages with Internet mail systems. This includes translation between MMS and Internet Mail messages using Extended Simple Mail Transfer Protocol [SMTP] and Internet mail format [Msg-Fmt]. This protocol is a Stage 3 on reference point MM3 to exchange messages with systems in Internet Message format. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-330-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-330-A V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-330-A v1.0.zip | + +### 10.5.13.14 X.S0016-340-0 Version 1.0 MMS MM4 Stage 3 for Intercarrier Interworking (03 April 2003) + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and switch and database manufacturers. This document contains the core protocol and formats for interworking between network operators in support of Multimedia Messaging Services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-340-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-340 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-340-0 V1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-340-0 v1.0.zip | + +### 10.5.13.15 X.S0016-340-0 Version 2.0 MMS MM4 Stage 3 for Intercarrier Interworking (June 2004) + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and switch and database manufacturers. This document contains the core protocol and formats for interworking between network operators in support of Multimedia Messaging Services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-340-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-340-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-340-0 v2.0.zip | +| TTC | TS-3GB-X.S0016-340-0v2.0 | 2.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016-340-0v2.0.pdf | + +### 10.5.13.16 X.S0016-340-A Version 1.0 Multimedia Messaging Service – MM4 Stage 3 Inter-carrier Interworking (January 2006) + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and switch and database manufacturers. This document contains the core protocol and formats for interworking between network operators in support of Multimedia Messaging Services + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-340-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-340-A V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-340-A v1.0.zip | + +### 10.5.13.17 X.S0016-370-0 Version 1.0 MMS MM7 VASP Interworking Stage 3 Specification (03 April 2003) + +This document describes the technical realization (Stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-370-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-370 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0016-370-0 V1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-370-0 v1.0.zip | + +### 10.5.13.18 X.S0016-370-0 Version 2.0 MMS MM7 VASP Interworking Stage 3 Specification (June 2004) + +This document describes the technical realization (Stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-370-0 v2.0 | 2.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-370-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-370-0 v2.0.zip | +| TTC | TS-3GB-X.S0016-370-0v2.0 | 2.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-X.S0016-370-0v2.0.pdf | + +### **10.5.13.19 X.S0016-370-A Version 1.0 Multimedia Messaging Service – MM7 VASP Interworking Stage 3 (January 2006)** + +This document describes the technical realization (Stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-370-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-370-A V1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-370-A v1.0.zip | + +### **10.5.14 X.S0017 Version 1.0.0 Open Service Access (OSA) Application Programming Interface (API) OSA API Revision: 0 (June 2003)** + +This document is intended to define the OSA API Stage 3 interface definitions and it provides the complete OSA specifications for cdma2000-based systems. This document is an extension of OSA API, per latest 3GPP TS 29.198 series specifications capabilities to enable operation in cdma2000 systems environment as part of the TTA/EIA/IS-2000 family of standards. The information given here is to be used by developers in 3GPP2 cdma2000 network architecture to the 3GPP OSA Specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0017 v1.0.0 | 1 | Approved | --06-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-937 | | Published | --06-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0017 V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0017 v1.0.0.zip | +| TTC | TS-3GB-X.S0017-0v1.0.0 | 1.0.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0017-0v100.pdf | + +### **10.5.15 X.S0018 Version 1.0.0 Legacy Mobile Station Domain (LMSD) Step 1 Revision: 0 (May 2003)** + +This standard specifies the necessary interfaces to support the bearer traffic between Media Gateways in the initial step of the Legacy Mobile Station Domain (LMSD). The requirements for this work are defined in [6], and the overall architecture model is defined in [5]. + +This standard defines bearer support of G.711 PCM encoded voice over IP as defined in RFC 1890 at a minimum, for use between media gateways in a cdma2000 Legacy Mobile Station Domain. This standard utilizes existing IETF and 3GPP2 protocols when applicable to minimize the new work needed. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0018-0 | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA-930 | | Published | --01-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0018_v1.0.0 | 1.0.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0018_v1.0.0.zip | + +### 10.5.16 X.S0021-B Version 1.0 Roamer Database Verification (July 2004) + +The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0021-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-847-B | | Published | --08-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0021-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0021-B v1.0.zip | +| TTC | TS-3GB-X.S0021-Bv1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0021-bv10.pdf | + +### 10.5.17 X.S0022-A Version 1.0 Broadcast and Multicast Service in cdma2000 Wireless IP Network Revision A (16 February 2007) + +The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0022-A v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0022-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0022-A v1.0.zip | +| TTC | TS-3GB-X.S0022-Av1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0022-Av1.0.pdf | + +### 10.5.18 X.S0023-B Version 1.0 Network Interworking Between GSM MAP and TIA-41 Map – cdma2000 Support (July 2004) + +The purpose of this standard is to define and describe the functions necessary for roaming between ANSI-41 MAP and GSM MAP-based networks in the support of roaming subscribers. This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., a TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM Foreign Mode. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0023-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | J-STD-038-B | | Published | --08-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0023-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0023-B v1.0.zip | +| TTC | TS-3GB-X.S0023-Bv1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0023-bv10.pdf | + +### 10.5.19 X.S0024-0 Version 1.0 IP Based Location Services (October 2005) + +The purpose of this document is to specify the intersystem operations that enable a wireless system to provide IP-Based location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0024-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1020 | 0 | Published | --01-2007 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0024-0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0024-0 v1.0.zip | + +### 10.5.20 X.S0025-0 Version 1.0 Legacy MS Domain Step 2 (February 2006) + +The Legacy MS Domain (LMSD) provides support for existing MSs in a network that supports IP bearers. This specification provides support for transport of compressed speech (e.g., 13K, SMV, EVRC, etc.) over IP bearers. All bearer features in the legacy network are supported. Additionally, this specification provides support for placing bearer signal processing transcoders in the Base Station (BS) and/or in the Media Gateway (MGW). Network capabilities that support minimizing the number of transcoders in the bearer path are also supported. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0025-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0025-0 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0025-0 v1.0.zip | +| TTC | TS-3GB-X.S0025-0v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0025-0v10.pdf | + +### 10.5.21 X.S0027-000-0 Version 1.0 Presence Overview (September 2004) + +This document describes network aspects of the Presence Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0027-000-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-1032.000 | | Published | --11-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0027-000-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-000-0 v1.0.zip | +| TTC | TS-3GB-X.S0027-000-0v1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-000-0v10.pdf | + +#### 10.5.21.1 X.S0027-001-0 Version 1.0 Presence Service: Architecture and Functional Description (September 2004) + +This document describes the Stage 2 (architectural solution and functionalities) for the presence service, which includes the elements necessary to realize the Stage 1 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0027-001-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1032 | | Published | --11-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0027-001-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-001-0 v1.0.zip | +| TTC | TS-3GB-X.S0027-001-0v1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-001-0v10.pdf | + +### **10.5.22 X.S0028-000-0 Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – List of Parts (March 2007)** + +This document describes the list of parts for WLAN interworking. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0028-000-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0028-000-0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0028-000-0 v1.0.zip | +| TTC | TS-3GB-X.S0028-000-0v1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-X.S0028-000-0v1.0.pdf | + +#### **10.5.22.1 X.S0028-100-0 Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – Access to Internet (March 2007)** + +This document describes WLAN Interworking – Access to Internet, which includes the elements necessary to realize the Stage 1 requirements + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0028-100-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0028-100-0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0028-100-0 v1.0.zip | +| TTC | TS-3GB-X.S0028-100-0v1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-X.S0028-100-0v1.0.pdf | + +#### **10.5.22.2 X.S0028-200-0 Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – Access to Operator Service and Mobility (March 2007)** + +This document describes WLAN Interworking – Access to Operator Service and Mobility, which includes the elements necessary to realize the Stage 1 requirements + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0028-200-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0028-200-0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0028-200-0 v1.0.zip | +| TTC | TS-3GB-X.S0028-200-0v1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-X.S0028-200-0v1.0.pdf | + +### 10.5.23 X.S0029-0 Version 1.0 Conferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem Revision: 0 (May 2007) + +This document provides the protocol details for conferencing within the IP Multimedia Core Network Subsystem (IMS) based on the Session Initiation Protocol (SIP), SIP Events and the Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0029-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0029-0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0029-0 v1.0.zip | +| TTC | TS-3GB-X.S0029-0v1.0 | 1.0 | TTC Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0029-0v1.0.pdf | + +### 10.5.24 X.S0030-0 Version 1.0 MAP Enhancements to Support Enhanced Message Waiting Notification (MWN) (September 2005) + +This document provides automatic roaming information flows that illustrate enhanced Message Waiting Count operation. This document also describes the signaling protocol and signalling procedure modifications needed for enhanced Message Waiting Count operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0030-0 | 1 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TTA | TTAT.3G-X.S0030-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0030-0 v1.0.zip | +| TTC | TS-3GB-X.S0030-0v1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0030-0v10.pdf | + +### 10.5.25 X.S0033-0 Version 1.0 OTA Support for MEID (October 2005) + +This document presents a recommended plan for the implementation of Over-The-Air (OTA) support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0033-0 | 1.0 | Approved | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-1074 | | Published | --03-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0033-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0033-0 v1.0.zip | +| TTC | TS-3GB-X.S0033-0v1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0033-0v10.pdf | + +### 10.5.25.1 X.S0033-0 Version 2.0 OTA Support for MEID (February 2006) + +This document presents a recommended plan for the implementation of Over-The-Air (OTA) support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0033-0 v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0033-0 v2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0033-0 v2.0.zip | +| TTC | TS-3GB-X.S0033-0v2.0 | 2.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0033-0v20.pdf | + +### 10.5.26 X.S0034-0 Version 1.0 cdma2000/GPRS Roaming (September 2004) + +The scope of this document includes the roaming of a subscriber homed in a cdma2000 packet data system to a GPRS system and vice versa. The roaming between cdma2000 packet data systems is outside the scope of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0034-0 | 1.0 | Approved | 09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0034-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0034-0 v1.0.zip | +| TTC | TS-3GB-X.S0034-0v1.0 | 1.0 | TTC Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0034-0v10.pdf | + +### 10.5.27 X.S0037-0 Version 1.0 Tunneling Support in Simple IP (May 2006) + +The scope of this specification includes tunneling support for the Simple IP packet data subscriber roaming across cdma2000 packet data systems that are administered by different service providers. In this specification, the tunneling scheme is specified in the context of layer-two tunneling. Other tunneling schemes are not precluded. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0037-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0037-0 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0037-0 v1.0.zip | +| TTC | TS-3GB-X.S0037-0v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0037-0v10.pdf | + +### 10.5.28 X.R0039-0 Version 1.0 Packet Switched Voice (over IP) and Video Telephony Services End to End Design Technical Report (November 2005) + +This document describes the end-to-end protocols and procedures for support of Packet Switched Video Telephony (PSVT) and Voice-Over-IP (VoIP) Services over cdma2000® networks. The document describes the end-to-end PSVT and VoIP services and architectures. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.R0039-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.R0039-0 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.R0039-0 v1.0.zip | +| TTC | TS-3GB-X.R0039-0v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxr0039-0v10.pdf | + +### **10.5.29 X.S0040-0 Version 1.0 OPPP-Alternative Protocol (AltPPP) for cdma2000 Wireless IP Network Standard (January 2007)** + +This document defines the AltPPP protocol for packet data session setup for cdma2000 wireless IP networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0040-0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0040-0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0040-0 v1.0.zip | +| TTC | TS-3GB-X.S0040-0v1.0 | 1.0 | TTC Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0040-0v1.0.pdf | + +### **10.5.30 X.S0042-0 Version 1.0 Voice Call Continuity between IMS and Circuit Switched Systems (October 2007)** + +Voice call continuity allows users to move voice calls between the Circuit-Switched (CS) domain and the Multimedia Domain (MMD), connected through different Internet Protocol – Connectivity Access Networks (IPCANs) (e.g., WLAN, HRPD). This document defines an inter-technology Domain Transfer (DT) call model which supports procedures that allow a mobile subscriber to DT from an HRPD or WLAN multimedia session with a voice component to a 1x CS voice session and from a 1x CS voice session to a WLAN VoIP session. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0042-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0042-0v1.0.pdf | + +### **10.5.31 X.S0048-0 Version 1.0 Short Message Service Over IMS (November 2007)** + +This document provides SMS over IMS procedures based upon [MMD Part-4] and [MMD Part-10]. This document is applicable to Application Servers (ASs) and User Equipments (UEs) providing SMS over IMS functionality. It is the goal of this specification to allow the core network to know as closely as possible, the current accessibility of the UE and to deliver SMS efficiently across the appropriate access network while minimizing the impact on the legacy systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0048-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0048-0v1.0.pdf | + +### **10.5.32 X.S0050-0 Version 1.0 Session Initiation Protocol (SIP) to ISDN User Part (ISUP) Interworking (January 2008)** + +This document provides SMS over IMS procedures based upon [MMD Part-4] and [MMD Part-10]. This document is applicable to Application Servers (ASs) and User Equipments (UEs) providing SMS over IMS functionality. It is the goal of this specification to allow the core network to know as closely as possible, the current accessibility of the UE and to deliver SMS efficiently across the appropriate access network while minimizing the impact on the legacy systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0050-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0050-0v1.0.pdf | + +### **10.5.33 X.R0052-0 Version 1.0 All-IP System – MMD Roaming Technical Report (August 2007)** + +This document contains example scenarios for mobiles which roam into a visited network that is different from their home network. It offers recommendations on how these roaming scenarios may be supported. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.R0052.0 v1.0 | 1.0 | Approved | 25-11-2007 | http://www.ccsa.org.cn/english/te/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.R0052.0 v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.R0052.0 v1.0.zip | + +### **10.5.34 X.S0054-000-0 Version 1.0 CAN Wireless IP Network Overview and List of Parts (December 2007)** + +This document provides an overview of the series of documents used to specify the Converged Access Network (CAN). The CAN enables optimization and upgrade for packet data access network to support services to the customers. This document also describes the CAN Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-000-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-000-0v1.0.pdf | + +#### **10.5.34.1 X.S0054-100-0 Version 1.0 Basic IP Services for Converged Access Network Specification (December 2007)** + +This document defines the stage-2 and stage-3 requirements for Simple IP access to the Converged Access Network supporting Ultra Mobile Broadband (UMB) 1 Wireless access. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-100-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-100-0v1.0.pdf | + +#### **10.5.34.2 X.S0054-102-0 Version 1.0 Multiple Authentication and 2G-RUIM Support for Converged Access Network (December 2007)** + +This document describes Stage 2 and Stage 3 specification details for Multiple-Authentication and 2G R-UIM support for UMB. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-102-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-102-0v1.0.pdf | + +#### **10.5.34.3 X.S0054-110-0 Version 1.0 MIPv4 Specification in Converged Access Network Specification (December 2007)** + +This document defines the stage-2 and stage-3 requirements for client based Mobile IPv4 access to the Converged Access Network supporting Ultra Mobile Broadband radio access. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-110-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-110-0v1.0.pdf | + +#### **10.5.34.4 X.S0054-210-0 Version 1.0 CMIP Based Inter-AGW Handoff (December 2007)** + +This document describes inter-AGW handoff operation using Mobile IP (e.g., the AT implements MIP client functionality, called CMIP) for layer 3 mobility, for both active and idle handoffs. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-210-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-210-0v1.0.pdf | + +#### **10.5.34.5 X.S0054-220-0 Version 1.0 PMIP Support between AGW and LMA (December 2007)** + +This document defines the stage-2 and stage-3 requirements for supporting PMIP between AGW and HA. This document describes PMIP based Simple IP address assignment and PMIP based inter-AGW handoff. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-220-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-220-0v1.0.pdf | + +#### **10.5.34.6 X.S0054-300-0 Version 1.0 QoS Support for Converged Access Network Specification (December 2007)** + +This document defines the stage-3 requirements for QoS support in the Converged Access Network (CAN). + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-300-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-300-0v1.0.pdf | + +#### **10.5.34.7 X.S0054-400-0 Version 1.0 Converged Access Network Accounting Specification (December 2007)** + +This document defines offline accounting functionality in the CAN. It describes the functional responsibilities of the network elements including the accounting data to be collected by certain elements in the CAN architecture. It describes the protocol messages and message contents that are exchanged between eBSs in an AT's Route Set and the AGW, and between the AGW and the accounting server. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-400-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-400-0v1.0.pdf | + +#### **10.5.34.8 X.S0054-910-0 Version 1.0 CAN Data Dictionary (December 2007)** + +This document defines AAA Data Dictionary in the CAN system. It defines 3GPP2 specific RADIUS attributes and Diameter AVPs. It describes the AAA RADIUS attributes and Diameters AVP for different interfaces such as eBS/SRNC-AGW interface, AGW-AAA interface, HA-AAA interface, etc. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-910-0v1.0 | 1.0 | TTC Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-910-0v1.0.pdf | + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..678552b6232525dff298dcc8cd227fe9eba90fe3 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:233c3b933d4158fc1ea6485f5d28075311a30845f372a2b1ef8581c494c65efe +size 238463 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43fbc813e4a42045993c53bdec920b8b86c4eb88 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f7521aa392064bce7d252eacb1b96ffc00b5595fbe7d1cd2e8e5f0465117f3c +size 217017 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482fdb9525ff7d93caa6ad75db6d98ea92bd9cc2 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b9c7d6ada0abaef82a2852432a8ab350658b105c1ceaba99720619f266fe52b +size 219721 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef513314b4e4313f7bcfa2fa75e8c8fac81c328a --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d359382b73f944f2410e53ab62c858f93801f6ad0bbadffa60bcc6438a02b776 +size 52194 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c220bc7b9a59a2f665327cf7948488df57a9db73 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4cc061e155b39abacde838450db8fcdb68b8a5582dd08a8e7316a8e033849cf +size 99426 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3825f80d61943baf05b4e11673e2ffe29cddd2d5 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92310ab45b4cdc09c82608a7f4eee72fcec4c4a9e99699dc0c6c5b73d7f9714f +size 182501 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7753ce6ac3d6d44ec835ee58ba73785f3ca56eca --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3b4dc3966757a5a9631713c5fc98b1bb1c8224f94ad0d13e83aeb6747a4d912 +size 91427 diff --git a/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6918942884a847fb8a615ca92e522b4e72b37808 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.9-201111-I_PDF-E/raw.md @@ -0,0 +1,7290 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1742.9** + +(11/2011) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**IMT-2000 references (approved as of +31 December 2010) to ANSI-41 evolved core +network with cdma2000 access network** + +Recommendation ITU-T Q.1742.9 + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.1742.9 + +## IMT-2000 references (approved as of 31 December 2010) to ANSI-41 evolved core network with cdma2000 access network + +## Summary + +Recommendation ITU-T Q.1742.9 associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 31 December 2010 for the IMT-2000 Family Member "ANSI-41 evolved Core Network with cdma2000 Access Network". + +- 3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.1. +- 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.2. +- 3GPP2 specifications that were approved as of 30 June 2003 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.3. +- 3GPP2 specifications that were approved as of 30 June 2004 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.4. +- 3GPP2 specifications that were approved as of 31 December 2005 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.5. +- 3GPP2 specifications that were approved as of 31 December 2006 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.6. +- 3GPP2 specifications that were approved as of 30 June 2008 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.7. +- 3GPP2 specifications that were approved as of 30 January 2010 were associated with the published core network standards from the regional standards development organizations in Recommendation ITU-T Q.1742.8. + +The radio interface and radio access network and standards from the SDOs for this IMT-2000 family member are associated in Recommendation ITU-R M.1457. The associations for other IMT-2000 family members are identified in the ITU-T Q.174x series. + +This Recommendation combines and associates the regional standards for the core network of this IMT-2000 family member into a global Recommendation. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.1742.9 | 2011-11-29 | 13 | + +## Keywords + +ANSI-41, cdma2000, core network, IMT-2000, third generation system. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2012 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|---------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Introduction ..... | 10 | +| 6 | Basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member..... | 10 | +| 7 | Network Entities ..... | 16 | +| 7.1 | Authentication, Authorization and Accounting (AAA) ..... | 16 | +| 7.2 | Authentication Centre (AC) ..... | 16 | +| 7.3 | Call Data Collection Point (CDCP)..... | 16 | +| 7.4 | Call Data Generation Point (CDGP) ..... | 17 | +| 7.5 | Call Data Information Source (CDIS)..... | 17 | +| 7.6 | Call Data Rating Point (CDRP)..... | 17 | +| 7.7 | Collection Function (CF) – [Intercept]..... | 17 | +| 7.8 | Coordinate Routing Data Base (CRDB)..... | 17 | +| 7.9 | Customer Service Centre (CSC)..... | 17 | +| 7.10 | Delivery Function (DF) – [Intercept] ..... | 17 | +| 7.11 | Equipment Identity Register (EIR)..... | 18 | +| 7.12 | evolved Packet Data Interworking Function (ePDIF) ..... | 18 | +| 7.13 | Home Agent (HA) ..... | 18 | +| 7.14 | Home Location Register (HLR) ..... | 18 | +| 7.15 | Intelligent Peripheral (IP) ..... | 18 | +| 7.16 | Intercept Access Point (IAP) ..... | 18 | +| 7.17 | Interworking Function (IWF)..... | 18 | +| 7.18 | IP Services ..... | 18 | +| 7.19 | Local Position Determining Entity (LPDE) ..... | 19 | +| 7.20 | Managed Wireless Network Entity (MWNE) ..... | 19 | +| 7.21 | Message Centre (MC)..... | 19 | +| 7.22 | Mobile Position Centre (MPC)..... | 19 | +| 7.23 | Mobile Switching Centre (MSC)..... | 19 | +| 7.24 | Number Portability Database (NPDB) ..... | 19 | +| 7.25 | Over-The-Air Service Provisioning Function (OTAF) ..... | 19 | +| 7.26 | Packet Data Network (PDN) ..... | 19 | +| 7.27 | Packet Data Serving Node (PDSN) ..... | 19 | +| 7.28 | Position Determining Entity (PDE)..... | 19 | +| 7.29 | Service Control Point (SCP)..... | 20 | +| 7.30 | Service Node (SN)..... | 20 | + +| | | Page | +|------|---------------------------------------------------------------|------| +| 7.31 | Short Message Entity (SME)..... | 20 | +| 7.32 | Visitor Location Register (VLR)..... | 20 | +| 7.33 | Voice Message Centre (VMS)..... | 20 | +| 7.34 | Wireless Network Entity (WNE)..... | 20 | +| 7.35 | Access Gateway (AGW) ..... | 20 | +| 7.36 | Access Terminal (AT) ..... | 20 | +| 7.37 | Application Server..... | 20 | +| 7.38 | Authentication, Authorization and Accounting (AAA) ..... | 20 | +| 7.39 | Border Router (BR) ..... | 21 | +| 7.40 | Breakout Gateway Control Function (BGCF)..... | 21 | +| 7.41 | Call Session Control Function (CSCF) ..... | 21 | +| 7.42 | Databases (DB)..... | 21 | +| 7.43 | evolved Base Station (eBS) ..... | 21 | +| 7.44 | IP Multimedia Client ..... | 21 | +| 7.45 | IP Network..... | 21 | +| 7.46 | Local Mobility Anchor (LMA) ..... | 21 | +| 7.47 | Media Gateway (MGW)..... | 22 | +| 7.48 | Media Gateway Control Function (MGCF) ..... | 22 | +| 7.49 | Media Resource Function Controller (MRFC)..... | 22 | +| 7.50 | Media Resource Function Processor (MRFP)..... | 22 | +| 7.51 | Mobile IP Home Agent (HA) ..... | 22 | +| 7.52 | Mobile Station (MS)..... | 22 | +| 7.53 | non-3GPP2 System..... | 22 | +| 7.54 | OSA Service Capability Server (OSA-SCS)..... | 23 | +| 7.55 | Policy Decision Function (PDF) ..... | 23 | +| 7.56 | Position Determining Entity (PDE)..... | 23 | +| 7.57 | Position Server..... | 23 | +| 7.58 | Public Switched Telephone Network (PSTN)..... | 23 | +| 7.59 | Proxy Mobile Agent (PMA) or Mobile Access Gateway (MAG) ..... | 23 | +| 7.60 | Policy and Charging Rules Function (PCRF) ..... | 23 | +| 7.61 | Session Reference Network Controller (SRNC) ..... | 23 | +| 8 | Reference Points ..... | 23 | +| 8.1 | Reference Point B..... | 23 | +| 8.2 | Reference Point C..... | 23 | +| 8.3 | Reference Point D..... | 24 | +| 8.4 | Reference Point d ..... | 24 | +| 8.5 | Reference Point D1..... | 24 | +| 8.6 | Reference Point Di ..... | 24 | +| 8.7 | Reference Point E ..... | 24 | +| 8.8 | Reference Point E3 ..... | 24 | + +| | Page | +|--------------------------------|------| +| 8.9 Reference Point E5 ..... | 24 | +| 8.10 Reference Point E9 ..... | 24 | +| 8.11 Reference Point E11 ..... | 24 | +| 8.12 Reference Point E12 ..... | 24 | +| 8.13 Reference Point e ..... | 24 | +| 8.14 Reference Point F ..... | 24 | +| 8.15 Reference Point G ..... | 24 | +| 8.16 Reference Point H ..... | 24 | +| 8.17 Reference Point I ..... | 25 | +| 8.18 Reference Point J ..... | 25 | +| 8.19 Reference Point K ..... | 25 | +| 8.20 Reference Point L ..... | 25 | +| 8.21 Reference Point M1 ..... | 25 | +| 8.22 Reference Point M2 ..... | 25 | +| 8.23 Reference Point M3 ..... | 25 | +| 8.24 Reference Point N ..... | 25 | +| 8.25 Reference Point N1 ..... | 25 | +| 8.26 Reference Point O1 ..... | 25 | +| 8.27 Reference Point O2 ..... | 25 | +| 8.28 Reference Point Pi ..... | 25 | +| 8.29 Reference Point Q ..... | 25 | +| 8.30 Reference Point Q1 ..... | 25 | +| 8.31 Reference Point T1 ..... | 26 | +| 8.32 Reference Point T2 ..... | 26 | +| 8.33 Reference Point T3 ..... | 26 | +| 8.34 Reference Point T4 ..... | 26 | +| 8.35 Reference Point T5 ..... | 26 | +| 8.36 Reference Point T6 ..... | 26 | +| 8.37 Reference Point T7 ..... | 26 | +| 8.38 Reference Point T8 ..... | 26 | +| 8.39 Reference Point T9 ..... | 26 | +| 8.40 Reference Point V ..... | 26 | +| 8.41 Reference Point X ..... | 26 | +| 8.42 Reference Point Y ..... | 26 | +| 8.43 Reference Point Z ..... | 26 | +| 8.44 Reference Point Z1 ..... | 26 | +| 8.45 Reference Point Z2 ..... | 26 | +| 8.46 Reference Point Z3 ..... | 27 | +| 8.47 Reference Point 1 ..... | 27 | +| 8.48 Reference Point 2 ..... | 27 | + +| | Page | +|------------------------------------|------| +| 8.49 Reference Point 3 ..... | 27 | +| 8.50 Reference Point 4 ..... | 27 | +| 8.51 Reference Point 5/Mk..... | 27 | +| 8.52 Reference Point 6 ..... | 27 | +| 8.53 Reference Point 7 ..... | 27 | +| 8.54 Reference Point 8/OSA ..... | 27 | +| 8.55 Reference Point 9/Mi..... | 27 | +| 8.56 Reference Point 10 ..... | 27 | +| 8.57 Reference Point 11/Sh ..... | 28 | +| 8.58 Reference Point 12/ISC ..... | 28 | +| 8.59 Reference Point 13 ..... | 28 | +| 8.60 Reference Point 14 ..... | 28 | +| 8.61 Reference Point 15 ..... | 28 | +| 8.62 Reference Point 16/Cx..... | 28 | +| 8.63 Reference Point 17/(Mg) ..... | 28 | +| 8.64 Reference Point 18 ..... | 28 | +| 8.65 Reference Point 19 ..... | 28 | +| 8.66 Reference Point 20 ..... | 28 | +| 8.67 Reference Point 21 ..... | 28 | +| 8.68 Reference Point 22 ..... | 28 | +| 8.69 Reference Point 23 ..... | 29 | +| 8.70 Reference Point 24/Mr ..... | 29 | +| 8.71 Reference Point 25/Mp..... | 29 | +| 8.72 Reference Point 26/PSTN..... | 29 | +| 8.73 Reference Point 27 ..... | 29 | +| 8.74 Reference Point 28/Go ..... | 29 | +| 8.75 Reference Point 29 ..... | 29 | +| 8.76 Reference Point 30/Mc ..... | 29 | +| 8.77 Reference Point 31 ..... | 29 | +| 8.78 Reference Point 32/Mb..... | 29 | +| 8.79 Reference Point 33/Mb..... | 29 | +| 8.80 Reference Point 34/Mb..... | 29 | +| 8.81 Reference Point 35 ..... | 30 | +| 8.82 Reference Point 36/Mb..... | 30 | +| 8.83 Reference Point 37/Mb..... | 30 | +| 8.84 Reference Point 38/Mb..... | 30 | +| 8.85 Reference Point 39 ..... | 30 | +| 8.86 Reference Point 40/Mb..... | 30 | +| 8.87 Reference Point 41 ..... | 30 | +| 8.88 Reference Point 42/Mb..... | 30 | + +| | | Page | +|-------|-----------------------------------------|-------------| +| 8.89 | Reference Point 43/Mb..... | 30 | +| 8.90 | Reference Point 44/Mb..... | 30 | +| 8.91 | Reference Point 45/Mb..... | 30 | +| 8.92 | Reference Point 46/Mb..... | 30 | +| 8.93 | Reference Point 47 ..... | 31 | +| 8.94 | Reference Point 48 ..... | 31 | +| 8.95 | Reference Point 49/(Mj) ..... | 31 | +| 8.96 | Reference Point 50 ..... | 31 | +| 8.97 | Reference Point U1..... | 31 | +| 8.98 | Reference Point U2..... | 31 | +| 8.99 | Reference Point U3..... | 31 | +| 8.100 | Reference Point U4..... | 31 | +| 8.101 | Reference Point U6..... | 31 | +| 8.102 | Reference Point U14..... | 31 | +| 8.103 | Reference Point U15..... | 31 | +| 8.104 | Reference Point U15' ..... | 31 | +| 8.105 | Reference Point U16..... | 32 | +| 8.106 | Reference Point U17..... | 32 | +| 8.107 | Reference Point U18..... | 32 | +| 8.108 | Reference Point U19..... | 32 | +| 8.109 | Reference Point U20..... | 32 | +| 8.110 | Reference Point U21..... | 32 | +| 8.111 | Reference Point U22..... | 32 | +| 8.112 | Reference Point U23..... | 32 | +| 8.113 | Reference Point U24..... | 32 | +| 8.114 | Reference Point U25..... | 33 | +| 8.115 | Reference Point U26..... | 33 | +| 8.116 | Reference Point U27..... | 33 | +| 8.117 | Reference Point U28..... | 33 | +| 8.118 | Reference Point U29..... | 33 | +| 8.119 | Reference Point U30..... | 33 | +| 8.120 | Reference Point U31..... | 33 | +| 8.121 | Reference Point U32..... | 33 | +| 8.122 | Reference Point UMB-AI ..... | 33 | +| 9 | Technical specifications structure..... | 33 | + +| | Page | +|-------------------------------------------------------|------| +| 10 Technical Specifications..... | 34 | +| 10.1 A Series RAN Specifications ..... | 34 | +| 10.2 Intersystem Specifications..... | 35 | +| 10.3 Packet Data Specifications ..... | 45 | +| 10.4 Services and system aspects specifications ..... | 46 | +| 10.5 Core Network Specifications..... | 124 | + +## Recommendation ITU-T Q.1742.9 + +## IMT-2000 references (approved as of 31 December 2010) to ANSI-41 evolved core network with cdma2000 access network + +## 1 Scope + +This Recommendation identifies the IMT-2000 family member "ANSI-41 evolved Core Network with cdma2000 Access Network". This set of referenced specifications includes those 3GPP2 specifications that were approved as of 31 December 2010. + +The core network interfaces identified in this recommendation and the radio interfaces and radio access network interfaces identified in Recommendation ITU-R M.1457 [1] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 family member. + +It is the intent of the International Telecommunication Union that the references in this document are made only to specifications that specify the network aspects of this IMT-2000 family member. In the event that a referenced specification also includes material that specifies any of the radio aspects of this IMT-2000 family member, Recommendation ITU-R M.1457 [1], shall take precedence. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions, which through reference in this text constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] Recommendation ITU-R M.1457 (2001), *Detailed specifications of the radio interfaces of international mobile telecommunications-2000 (IMT-2000)*. +- [2] ANSI; TIA/EIA 41D (1997), *Cellular Radiotelecommunications Intersystem Operations (ANSI/TIA/EIA-41-D-97)*. +- [3] ANSI; TIA/EIA 95 (1999), *Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems (ANSI/TIA/EIA-95-B-99)*. +- [4] ANSI; TIA/EIA 124 (2001), *Wireless Radio Telecommunications Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (ANSI/124-D-2001)*. +- [5] ANSI; TIA/EIA 136 (2001), *TDMA Cellular PCS (ANSI/TIA/EIA-136, Rev C-2001)*. +- [6] ANSI; TIA/EIA 553A (1999), *Mobile Station – Base Station Compatibility Standard (ANSI TIA/EIA-553-A-99)*. +- [7] ANSI; TIA/EIA 664A (2000), *Cellular Features Description (ANSI/TIA/EIA-664-A-2000)*. +- [8] TIA Specification IS-91 (1999), *Base Station – Mobile Station Compatibility Specification for 800 MHz Cellular, Auxiliary, and Residential Services (TIA/EIA/IS-91-A)*. + +- [9] TIA Specification IS-2000 (2000), *CDMA 2000 Series (TIA/EIA/IS-2000 Series Revision A)*. +- [10] TIA Specification IS-2001-A (2001), *Interoperability Specifications (IOS) for cdma2000 Access Network Interfaces (TIA/EIA/IS-2001-A)*. +- [11] TIA Specification TSB-29D (2000), *International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41*. +- [12a] CWTS; CWTS-MC-S.R0005-B (2002), *Network Reference Model for cdma2000 Spread Spectrum Systems*. +- [12b] TTA; TSB100-A (2001), *Wireless Network Reference Model*. +- [12c] TTA; TTAE.3G-S.R0005-B (2001), *3GPP2 Network Reference Model for cdma2000 Spread Spectrum Systems*. +- [12d] TTC; TS-3GB-S.R0005-Bv1.0 (2001), *Network Reference Model for cdma2000 Spread Spectrum Systems*. +- [13a] CWTS; CWTS-MC-N.S0037 (2002), *IP Network Architecture Model for cdma2000 Spread Spectrum Systems*. +- [13b] TTA; TTAT.3G-S.R0037-0v2.0 (2003), *IP Network Architecture Model for cdma2000 Spread Spectrum Systems*. +- [13c] TTC; TS-3GB-S.R0037-0v2.0 (2002), *IP Network Architecture Model for cdma2000 Spread Spectrum Systems*. +- [14] TIA/EIA TSB29-E (2002), *International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41*. +- [15] TIA/EIA/IS-826 (2003), *TIA/EIA-41-D Based Pre-Paid Charging Enhancements for Circuit Switched Data and Short Message*. + +## 3 Definitions + +This Recommendation defines the following terms: + +**3.1 access denial call treatment:** A tone, announcement, or call redirection applied as appropriate. + +**3.2 access network:** A network that connects access technologies (such as a radio access network) to the core network. + +**3.3 active:** The MS is available for call delivery. This state is maintained by the MSC, the VLR and the HLR (see also Available, Inactive and Unavailable). + +**3.4 adjunct MSC:** A mobile switching centre (MSC) that is providing adjunct services such as voice response, voice recognition, DTMF tone detection, voice message storage, etc. + +**3.5 anchor MSC:** The mobile switching centre (MSC) that is the first to assign a traffic channel to a call on origination or termination is called the Anchor MSC. For the duration of this call, this MSC shall be the anchor (fixed) point in the event that the Mobile Station (MS) should be handed off to other MSCs. + +**3.6 authentication:** The act of verifying the identity of an entity (e.g., a user, device). + +**3.7 available:** The MS can accept a call delivery (i.e., the MS is in a known location and it is in a state able to accept call deliveries). The availability of a MS to accept a call delivery is maintained only by the MSC (see also Active, Inactive and Unavailable). + +- 3.8 base transceiver station:** A piece of radio access network equipment that contains the radios and serves a geographic area. +- 3.9 call delivery:** The process by which calls directed to the cellular subscriber are delivered to the subscriber while roaming in a visited system. +- 3.10 call delivery method:** Method by which a call is delivered to a subscriber in MSC-V. +- 3.11 call disconnect:** The process of requesting the release of a connection between two or more network addresses. +- 3.12 call release:** The process of relinquishing the facilities and circuits used for a call. +- 3.13 call Termination:** The process of connecting a subscriber to an incoming call. +- 3.14 candidate MSC:** This term is used during the handoff measurement request by the current serving mobile switching centre (MSC) to reference the MSC that is being requested to provide its best CELL ID and SIGNAL QUALITY values. +- 3.15 cell site:** The physical location of a cell's radio equipment and supporting systems. This term is also used to refer to the equipment located at the cell site. +- 3.16 clearinghouse:** A service used for the exchange and management of information. +- 3.17 data communications:** The digital transmission of information (other than voice). +- 3.18 dialogue:** A user interaction sequence composed of tones and announcements that may gather information. +- 3.19 gateway MSC:** See MSC-G. +- 3.20 home system:** The system which is transmitting the system identifier (SID) (refer to *EIA/TIA-553*) which is recognized by the MS as the "Home" SID. +- 3.21 inactive:** The MS is not available for call delivery. The MS may not be registered. The MS may be registered, but is out of radio contact (e.g., missing autonomous registrations) or is intentionally inaccessible for periods of time (e.g., slotted mode, paging frame class, or sleep mode). An inactive MS may accept SMS message deliveries. This state is maintained by the MSC, the VLR and the HLR (see also Active, Available, and Unavailable). +- 3.22 market identification (MarketID):** A unique market identifier that is specified by the service provider (e.g., FCC assigned SID, CIBERNET assigned BID – see *TIA/EIA TSB29*). +- 3.23 mobile assisted handoff (MAHO):** A process where handoff measurements are done by the MS under the control of the MSC and Base Station. The MSC and base station retain the control over when the handoff actually occurs. +- 3.24 mobility:** The ability to access services from any point in the network. The degree of service availability may depend on the access network capabilities, as well as any service level agreements between the user's home network and the visited network. Types of mobility include personal mobility, service mobility, and terminal mobility. +- 3.25 mobility management:** The set of functions used to manage a mobile user accessing a network other than that user's home network. These functions include communication with the home network for purposes of authentication, authorization, location updating and download of user information. +- 3.26 MSC-G:** mobile switching centre (MSC) that is capable of the Intersystem procedures, defined in this Recommendation, between entities in the network reference model so as to provide service. + +- 3.27 MSC-H:** The "home" mobile switching centre (MSC) of a mobile station (MS) which is broadcasting the SID that is recorded in the MS's security and identification memory, and to which the MS's directory number is assigned. +- 3.28 MSC-V:** A "visited" mobile switching centre (MSC) in whose service area a roamer is operating. +- 3.29 network reference model:** The functional entities and the associated interface reference points that may logically comprise a cellular network (see clause 6). +- 3.30 number portability:** A mechanism that allows a user to retain the same directory number, regardless of the subscribed-to service provider. Number portability may be limited to specific geographical areas. In the context of the All-IP network, the term "number portability" refers specifically to ITU-T E.164 numbers used for telephony. +- 3.31 originating MSC:** The MSC-H or MSC-G that initiates the call delivery procedures defined in this document. +- 3.32 originating SMS supplementary service:** Services or features that affect SMS message originations and are requested on a per message basis as supported by a particular teleservice, for example, delayed delivery, or message distribution to a list of destinations. +- 3.33 personal mobility:** The ability of users to change their association with one or more terminals at any point and time. The user should continue to receive subscribed and otherwise authorized services as supported by the current MS and access network. +- 3.34 personalized services:** Services that need access to the subscriber profile and/or are dependent on the overall call/session state (of the user) for reasons of service interaction. An example: a call termination service such as TIA/EIA-41's "Call Forward on Busy". +- 3.35 protocol extension:** A mechanism provided to allow systems with a common bilateral agreement to extend the *TIA/EIA-41* protocol. There is a range of reserved Error Codes, Operation Codes, Parameter Identifiers (in addition to PRIVATE Parameter Identifiers), and ranges of values in enumerated parameter types and data fields. The only mechanism to resolve conflicting uses of protocol extension is to standardize their usage. The Protocol Extension mechanism is used at the risk of the implementation. Protocol Extensions should not be used unless the message recipient is known to support them. +- 3.36 radio access network:** The network that connects radio base stations to the core network. The RAN provides and maintains radio-specific functions, which may be unique to a given radio access technology, that allow users to access the core network. +- 3.37 registered:** The HLR has a pointer to a system serving an MS. A registered MS may be active or inactive. +- 3.38 registration:** The procedure by which a MS becomes listed as being present in the service area of an MSC. +- 3.39 remote feature control port (RFC port):** A terminating directory number supporting service profile modification. +- 3.40 roamer port:** A terminating directory number supporting call delivery to mobile stations. +- 3.41 roamer service profile:** The specific set of features, capabilities and/or operating restrictions, other than financial accountability, associated with the subscriber. +- 3.42 roamer validation:** That aspect of roamer service qualification dealing with financial accountability. Also, the general procedure by which a roamer's financial accountability is established. + +- 3.43 roaming:** Action whereby users access services while outside of their subscribed home network. +- 3.44 service qualification:** The service capabilities, features and privileges to which an MS is entitled. Also, the general procedure by which such service capabilities, features, and privileges become established in an MSC. +- 3.45 serving MSC:** The MSC which currently has the MS obtaining service at one of its cell sites within its coverage area. +- 3.46 signalling:** The information exchanged between the mobile station and the network, or within the network, for the purposes of service provision (e.g., connection establishment). +- 3.47 switch number (SWNO):** A number uniquely identifying a particular switch (i.e., a group of cell sites and the associated switch resources) within a group of switches associated with a common MarketID. +- 3.48 target MSC:** The mobile switching centre (MSC) which was selected from the candidate list as having the cell site with the best signal quality value for the MS during the location request function. +- 3.49 temporary local directory number (TLDN):** A network address temporarily assigned for call set-up. +- 3.50 terminating SMS supplementary service:** Services or features that affect SMS message terminations, for example, screening, forwarding, delivery to an MS, delayed delivery while roaming, or distribution to a group based upon a destination address. +- 3.51 termination address:** One or more digits, as determined by the Home System, which identify the Terminating Party. This could include Speed Call Codes (when supported by the Home Service Provider), other Mobile Telephone Numbers or any valid World Telephone Number. +- 3.52 traffic:** The information generated by the subscriber that is transported on the network (i.e., user voice or data). +- 3.53 unavailable:** The MS cannot accept a normal call delivery (i.e., the MS is in an unknown location or it is in a state unable to accept call deliveries). The availability of an MS to accept a call delivery is maintained only by the MSC (see also Active, Available, and Inactive). +- 3.54 unregistered:** A state where the MS is unavailable for any type of termination event and the HLR pointer is not directed to any visited system. +- 3.55 visited network:** The visited network is a carrier's network where a subscriber currently is roaming. The term visited network is more business significant, than geographically significant. +- 3.56 visited system:** From the MS's perspective, a system which is transmitting a SID which is not recognized by the MS as the "Home" SID. From a network perspective, the system in which an MS is currently registered. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|----------------------------------------------------| +| 3G | Third Generation | +| 3GPP2 | Third Generation Partnership Project (ANSI driven) | +| AAA | Authentication, Authorization, and Accounting | +| AC | Authentication Centre | +| ADDS | Application Data Delivery Service | + +| | | +|-------|--------------------------------------------------------| +| ADPCM | Adaptive Differential Pulse Code Modulation | +| ADS | Asynchronous Data Service | +| AGW | Access Gateway | +| AH | Answer Hold | +| AMPS | Advanced Mobile Phone System | +| ANSI | American National Standards Institute | +| AOC | Advice of Charge | +| API | Application Programming Interface | +| ARIB | Association of Radio Industries and Businesses (Japan) | +| AS | Application Server | +| BCMCS | Broadcast-Multicast Services | +| BCSMs | Basic Call State Models | +| BS | Base Station | +| BSC | Base Station Controller | +| BTS | Basic Transceiver System | +| CAN | Converged Access Network | +| CCF | Call Control Function | +| CDCP | Call Data Collection Point | +| CDGP | Call Data Generation Point | +| CDIS | Call Data Information Source. | +| CDMA | Code Division Multiple Access | +| CDRP | Call Data Rating Point | +| CMIP | Client Mobile IP | +| CN | Core Network | +| CNAP | Calling Name Presentation | +| CNAR | Calling Name Restriction | +| CNIP | Calling Number Identification Presentation | +| CSC | Customer Service Centre | +| CSCF | Call Session Control Functions | +| CWTS | China Wireless Telecommunication Standard Group | +| DCCH | Dedicated Control Channel | +| DFP | Distributed Functional Plane | +| DMH | Data Message Handler | +| DP | Detection Point | +| DP | Data Privacy | +| DSA | Data Subscriber Authentication | +| DTMF | Dual Tone Multi-Frequency | + +| | | +|----------|-------------------------------------------------------------------------------| +| E2E | End-to-End | +| eBS | evolved Base Station | +| ECO | Emergency Call Origination | +| EIA | Electronics Industry Association | +| EIR | Equipment Identity Register | +| EMS | Enhanced Message Service | +| ESN | Electronic Serial Number | +| ESP | Encapsulating Security Payload | +| FCC | Federal Communications Commission | +| FFMA | File Format for Multimedia Services | +| FPH | Freephone | +| FPLMTS | Future Public Land Mobile Telecommunications Systems – Now: IMT-2000 | +| GECO | Global ECO | +| GSM | Formerly: Group Special Mobile – Now: Global System for Mobile communications | +| HA | Home Agent | +| HHS | Home subscriber Server | +| HLR | Home Location Register | +| IETF | Internet Engineering Task Force | +| IM | IP Multimedia call model | +| IMS | IP Multimedia core network subsystem | +| IMSI | International Mobile Subscriber Identity | +| IMT | International Mobile Telecommunications | +| IMT-2000 | International Mobile Telecommunications – 2000 | +| IOTA | IP Over-the-Air | +| IOTA HCM | Internet based Over-the-Air Handset Configuration Management | +| IP | Internet Protocol | +| IP | Intelligent Peripheral | +| IPE | In-Path Equipment | +| IS | Interim Standard | +| ISDN | Integrated Services Digital Network | +| ISIM | IP multimedia Services Identity Module | +| ISLP | Intersystem Link Protocol | +| ISO | International Standards Organization | +| ITU | International Telecommunication Union | +| ITU-R | International Telecommunication Union – Radio communication Sector | + +| | | +|-------|----------------------------------------------------------------------------------| +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| IWF | Interworking Function | +| LBSS | Location Based Services System | +| LMA | Local Mobility Agent | +| LMSD | Legacy Mobile Station Domain | +| MAP | Mobile Application Part | +| MC | Multi-Carrier | +| MC | Message Centre | +| MDN | Mobile Directory Number | +| MEID | Mobile Equipment Identifier | +| MGW | Media Gateway | +| MM | Multimedia Message | +| MMS | Multimedia Messaging Service | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MSID | Mobile Station Identifier | +| NAM | Number Assignment Module | +| NAMPS | Narrowband Advanced Mobile Phone Service | +| NDSS | Network Directed System Selection | +| NRM | Network Reference Model | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OSA | Open Service Access | +| OTAF | Over-the-Air Function | +| OTAPA | Over-the-Air Parameter Administration | +| OTASP | Over-the-Air Service Provisioning | +| PCF | Packet Control Function | +| PCS | Personal Communications Service | +| PCS | Personal Communications System | +| PDE | Positioning Determining Element | +| PDS | Packet Data Surveillance | +| PDSN | Packet Data Serving Node | +| PL | Preferred Language | +| PMIP | Proxy Mobile IP | +| PN | Project Number | +| PPC | Pre-Paid Charging | +| PPP | Point-to-Point Protocol | + +| | | +|-------|---------------------------------------------------| +| PRC | Premium Rate Charging | +| RAN | Radio Access Network | +| RUAC | Rejection of Undesired Annoying Calls | +| R-UIM | Removable User Identity Module | +| SC | Subscriber Confidentially | +| SCF | Service Call Forwarding | +| SCF | Service Control Function | +| SCP | Service Control Point | +| SCS | Service Capability Server | +| SDO | Standards Development Organization | +| SDP | Session Description Protocol | +| SID | System Identifier | +| SIP | Session Initiation Protocol | +| SME | Short Message Entity | +| SMS | Service Management System | +| SMS | Short Message Service | +| SMTP | Simple Mail Transfer Protocol | +| SN | Service Node | +| SRG | System Release Guide | +| SRNC | Session Reference Network Controller | +| SS7 | Signalling System 7 | +| SSF | Service Switching Function | +| SSG | Special Study Group | +| TFO | Tandem Free Operation | +| TIA | Telecommunications Industry Association | +| TMSI | Temporary Mobile Station Identification | +| TRAU | Transcoder and Rate Adaptor Unit | +| TrFO | Transcoder Free Operation | +| TSB | Telecommunications Systems Bulletin | +| TTA | Telecommunications Technology Association (Korea) | +| TTC | Telecommunication Technology Committee (Japan) | +| UICC | Universal Integrated Circuit Card | +| UIM | User Identity Module | +| UMB | Ultra Mobile Broadband | +| USCF | User Selective Call Forwarding | +| VASP | Value-Added Service Provider | +| VLR | Visitor Location Register | + +| | | +|-----|------------------------------| +| WIN | Wireless Intelligent Network | +| WLL | Wireless Local Loop | +| WNP | Wireless Number Portability | + +## 5 Introduction + +The Core Network for cdma2000 is based on an evolved ANSI-41 2nd generation mobile system. The core network technical specifications have been developed in a third generation partnership project (approved in 3GPP2 as of 31 December 2006) and transposed to the involved regional Standards Development Organizations (SDOs). The system will support different applications ranging from narrow-band to wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements. + +The Core Network interfaces identified in this recommendation and the radio interfaces and radio access network interfaces identified in Recommendation ITU-R M.1457 [1] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 Family Member. + +The descriptions in clauses 6, 7, and 8 and the descriptions of the Technical Specifications listed in clause 10 are for informative purposes only. Normative information is in the tables for the respective specification. + +## 6 Basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member + +The basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member includes a circuit-based and packet based core network and an all-IP multimedia domain. + +The following text is based on reference [12 a-d] section 2.1. + +Figure 6-1 presents the network entities and associated reference points that comprise the ANSI-41 evolved Core Network with cdma2000 Access Network. The network entities are represented by squares, triangles and rounded corner rectangles; circles represent the reference points. The network reference model in this document is the compilation of several reference models currently in use. + +- The network reference model is a functional block diagram. +- A network entity represents a group of functions, not a physical device. For example, a Mobile Switching Centre (MSC) is a physical device; it comprises frames, shelves, circuit packs, etc. The physical device may comprise a single network entity such as the MSC, or it may comprise some combination such as the MSC, the Visitor Location Register (VLR), the Home Location Register (HLR), and the Authentication Centre (AC). The physical realization is an implementation issue; a manufacturer may choose any physical implementation of network entities, either individually or in combination, as long as the implementation meets the functional requirements. Sometimes, for practical reasons, the functional network entity is a physical device. The Mobile Station (MS) is an excellent example. +- A reference point is a conceptual point that divides two groups of functions. It is not necessarily a physical interface. A reference point only becomes a physical interface when the network entities on either side of it are contained in different physical devices. +- A "Collective Entity" contains encompassed network entities that are an instance of the collective. +- A "Composite Entity" contains encompassed network entities that are part of the composite. + +[THE PORTION OF THE FIGURE WITHIN THE SOLID LINE IS THE CORE NETWORK] + +![Figure 6-1: ANSI-41 evolved Core Network with cdma2000 Access Network Reference Model. The diagram shows a complex network architecture with various entities and interfaces. A solid line encloses the core network, while the area outside represents the access network and user equipment. Entities include MS (Mobile Station), ME (Mobile Equipment), MT0, MT1, TAm, MT2, UIM, Vehicle, MWNE, OSF, NPDB, LPDE, VMS, BTS, BSC, MSC, IP, SCP, SN, EIR, PSTN [ESNE], DCE, PDN [ESNE], ISDN [ESNE], CSC, TA, IWG, PDSN, AAA, HA, MPC, PDE, ESME, CRDB, CDGP, CDCP, CDRP, DF, CF. Interfaces are labeled with letters (A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z) and numbers (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). Reference points are labeled with numbers (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). A key at the bottom explains the symbols used: Specific Network Entity (square), Collective Entity (dashed line), Interface to Another Instance of Same Network Entity (circle with x), Composite Entity (dotted area), Interface Reference Point (circle with H), and Line Intersection (cross).](812e188283162af0b54fb3e30ffee51b_img.jpg) + +Figure 6-1: ANSI-41 evolved Core Network with cdma2000 Access Network Reference Model. The diagram shows a complex network architecture with various entities and interfaces. A solid line encloses the core network, while the area outside represents the access network and user equipment. Entities include MS (Mobile Station), ME (Mobile Equipment), MT0, MT1, TAm, MT2, UIM, Vehicle, MWNE, OSF, NPDB, LPDE, VMS, BTS, BSC, MSC, IP, SCP, SN, EIR, PSTN [ESNE], DCE, PDN [ESNE], ISDN [ESNE], CSC, TA, IWG, PDSN, AAA, HA, MPC, PDE, ESME, CRDB, CDGP, CDCP, CDRP, DF, CF. Interfaces are labeled with letters (A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z) and numbers (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). Reference points are labeled with numbers (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). A key at the bottom explains the symbols used: Specific Network Entity (square), Collective Entity (dashed line), Interface to Another Instance of Same Network Entity (circle with x), Composite Entity (dotted area), Interface Reference Point (circle with H), and Line Intersection (cross). + +**Figure 6-1 – ANSI-41 evolved Core Network with cdma2000 Access Network Reference Model** + +The basic architecture for the ANSI-41 evolved Core Network with cdma2000 Access Network family member also includes an all-IP multimedia domain. The following text is based on reference [13 a-c] section 2.1. + +All-IP MMD Core Network Architecture: + +Figure 6-2 presents the core network entities and associated reference points that comprise the MMD (Multimedia Domain) of the wireless All-IP Network Architecture Model. The network entities are represented by squares and rectangles; the interfaces between network entities are reference points identified by numbers. Figure 6-2 includes several reference points that have dual + +labels. Either of these labels may be used in the specifications relating to these reference points. + NOTE – In Figure 6-2 the network elements and reference points highlighted in "blue" identify the "IP MMD Core Network". + +![Figure 6-2 – ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model. The diagram shows a complex network architecture with various components and reference points. A dashed blue box labeled 'IP MMD Core Network' encloses most of the central elements. On the left, a 'Mobile Station' connects to a 'cdma2000 Access Network' (containing BTS, BSC/RNC+PCF, and MM) and 'Other Access Networks'. The 'cdma2000 Access Network' connects to an 'Access Gateway' (part of the IP MMD Core Network). The 'Access Gateway' connects to a 'Mobile IP Home Agent' (IP MMD Core Network) via reference point 41 (FA/Attendant). The 'Mobile IP Home Agent' connects to a 'Border Router' (IP MMD Core Network) via reference points 42/Mb, 43/Mb, 44/Mb, and 45/Mb. The 'Border Router' connects to an 'IP Network' via reference point 46/Mb and to a 'PSTN' via reference point 34/Mb. Above the 'Mobile IP Home Agent' is a 'Media Resource Function Processor' (IP MMD Core Network) connected via reference points 32/Mb, 33/Mb, 36/Mb, 37/Mb, and 38/Mb. To the right of the 'Media Resource Function Processor' is a 'Media Gateway' (IP MMD Core Network) connected via reference points 26/PSTN, 30/Mc, and 40/Mb. Above the 'Media Gateway' is a 'Media Gateway Control Function' (IP MMD Core Network) connected via reference point 28/Go. Above that is a 'Policy Decision Function' (IP MMD Core Network) connected via reference points 9/Mi and 49/Mj. To the left of the 'Policy Decision Function' is a 'Call Session Control Function' (IP MMD Core Network) connected via reference points 16/Cx, 23, 50, and 17/Mg. Above the 'Call Session Control Function' is an 'OSA Service Capability Server' (IP MMD Core Network) connected via reference points 11/Sh and 10. Above the 'OSA Service Capability Server' are an 'Application Server' (IP MMD Core Network) and a 'SIP Application Server' (IP MMD Core Network), connected via reference points 8/OSA and 12/ISC respectively. At the top left, a 'Databases' block (containing EIR, DSI, Subscription Profile, Network Policy Rules, and others) is connected to the 'AAA' (IP MMD Core Network) via reference points 1, 2, 3, and 4. The 'AAA' is connected to the 'Position Server' (IP MMD Core Network) via reference points 15, 18, and 19. The 'Position Server' is connected to a 'Position Determining Entity' (IP MMD Core Network) via reference points 18 and 19. The 'Position Determining Entity' is connected to the 'Mobile Station' via reference point 47. Various other reference points are labeled, including 5/Mk, 6/Mk, 7, 11/Sh, 12/ISC, 13/Mg, 14/Mg, 20, 21, 22, 24/Mr, 25/Mp, 29, 31, 35, 47, and hh.](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg) + +Figure 6-2 – ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model. The diagram shows a complex network architecture with various components and reference points. A dashed blue box labeled 'IP MMD Core Network' encloses most of the central elements. On the left, a 'Mobile Station' connects to a 'cdma2000 Access Network' (containing BTS, BSC/RNC+PCF, and MM) and 'Other Access Networks'. The 'cdma2000 Access Network' connects to an 'Access Gateway' (part of the IP MMD Core Network). The 'Access Gateway' connects to a 'Mobile IP Home Agent' (IP MMD Core Network) via reference point 41 (FA/Attendant). The 'Mobile IP Home Agent' connects to a 'Border Router' (IP MMD Core Network) via reference points 42/Mb, 43/Mb, 44/Mb, and 45/Mb. The 'Border Router' connects to an 'IP Network' via reference point 46/Mb and to a 'PSTN' via reference point 34/Mb. Above the 'Mobile IP Home Agent' is a 'Media Resource Function Processor' (IP MMD Core Network) connected via reference points 32/Mb, 33/Mb, 36/Mb, 37/Mb, and 38/Mb. To the right of the 'Media Resource Function Processor' is a 'Media Gateway' (IP MMD Core Network) connected via reference points 26/PSTN, 30/Mc, and 40/Mb. Above the 'Media Gateway' is a 'Media Gateway Control Function' (IP MMD Core Network) connected via reference point 28/Go. Above that is a 'Policy Decision Function' (IP MMD Core Network) connected via reference points 9/Mi and 49/Mj. To the left of the 'Policy Decision Function' is a 'Call Session Control Function' (IP MMD Core Network) connected via reference points 16/Cx, 23, 50, and 17/Mg. Above the 'Call Session Control Function' is an 'OSA Service Capability Server' (IP MMD Core Network) connected via reference points 11/Sh and 10. Above the 'OSA Service Capability Server' are an 'Application Server' (IP MMD Core Network) and a 'SIP Application Server' (IP MMD Core Network), connected via reference points 8/OSA and 12/ISC respectively. At the top left, a 'Databases' block (containing EIR, DSI, Subscription Profile, Network Policy Rules, and others) is connected to the 'AAA' (IP MMD Core Network) via reference points 1, 2, 3, and 4. The 'AAA' is connected to the 'Position Server' (IP MMD Core Network) via reference points 15, 18, and 19. The 'Position Server' is connected to a 'Position Determining Entity' (IP MMD Core Network) via reference points 18 and 19. The 'Position Determining Entity' is connected to the 'Mobile Station' via reference point 47. Various other reference points are labeled, including 5/Mk, 6/Mk, 7, 11/Sh, 12/ISC, 13/Mg, 14/Mg, 20, 21, 22, 24/Mr, 25/Mp, 29, 31, 35, 47, and hh. + +**Figure 6-2 – ANSI-41 evolved Core Network with cdma2000 Access Network IP MMD Core Network Architecture Model** + +The MMD of the All-IP Network offers both general packet data support and multi-media session capabilities. The multi-media session capabilities are built on top of the general packet data support capabilities. The general packet data capabilities may be deployed without the multi-media session capabilities. Some network entities are common to providing both capabilities. + +Figure 6-3 shows the entities that comprise the general packet data support portion of the MMD core network. These are known collectively as the Packet Data Subsystem (PDS). Figure 6-3 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE – In Figure 6-3 the network elements and reference points highlighted in "blue" identify the "Packet Data Subsystem". + +![Diagram of ANSI-41 evolved Core Network with cdma2000 Access Network Packet Data Subsystem Core Network Architecture Model. The diagram shows various network elements and their interconnections, with the Packet Data Subsystem (PDS) highlighted in blue.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +The diagram illustrates the architecture of an ANSI-41 evolved Core Network with a cdma2000 Access Network. The Packet Data Subsystem (PDS) is highlighted in blue, indicating the network elements and reference points relevant to packet data support. + +**Network Elements:** + +- Databases:** EIR, DSI, Subscription Profile, Network Policy Rules, and others (highlighted in blue). +- AAA:** Authentication, Authorization, Accounting server (highlighted in blue). +- Policy Decision Function:** (highlighted in blue). +- Access Gateway:** (highlighted in blue). +- FA / Attendant:** (highlighted in blue). +- Mobile IP Home Agent:** (highlighted in blue). +- Border Router:** (highlighted in blue). + +**Other Network Elements:** + +- Application Server +- SIP Application Server +- OSA Service Capability Server +- Breakout Gateway Control Function +- Position Server +- Position Determining Entity +- Media Resource Function Controller +- Media Resource Function Processor +- Media Gateway Control Function +- Media Gateway + +**Access Networks:** + +- cdma2000 Access Network (containing BTS, BSC/RNC + PCF, and MM) +- Other Access Networks + +**External Networks:** + +- PSTN +- IP Network + +**Reference Points:** + +- 1, 2, 3, 4 (between Databases and AAA) +- 7 (between Databases and Application Server) +- 8/OSA (between Application Server and OSA Service Capability Server) +- 11/Sh (between AAA and OSA Service Capability Server) +- 12/ISC (between SIP Application Server and OSA Service Capability Server) +- 15 (between Position Server and AAA) +- 16/Cx (between AAA and Call Session Control Function) +- 17/Mg (between AAA and Policy Decision Function) +- 18 (between Position Server and Position Determining Entity) +- 19 (between Position Determining Entity and AAA) +- 20 (between Position Determining Entity and AAA) +- 21 (between AAA and Access Gateway) +- 22 (between AAA and Access Gateway) +- 23 (between AAA and Policy Decision Function) +- 24/Mr (between AAA and Media Resource Function Controller) +- 25/Mp (between Media Resource Function Controller and Media Resource Function Processor) +- 26/PSTN (between Media Gateway Control Function and Media Gateway) +- 28/Go (between Policy Decision Function and Media Gateway Control Function) +- 29 (between Policy Decision Function and Border Router) +- 30/Mc (between Media Gateway Control Function and Media Gateway) +- 31 (between cdma2000 Access Network and Access Gateway) +- 32/Mb (between Access Gateway and Media Resource Function Processor) +- 33/Mb (between Media Resource Function Processor and Media Gateway) +- 34/Mb (between Border Router and PSTN) +- 35 (between cdma2000 Access Network and AAA) +- 36/Mb (between Access Gateway and Mobile IP Home Agent) +- 37/Mb (between Media Resource Function Processor and Mobile IP Home Agent) +- 38/Mb (between Media Gateway and Mobile IP Home Agent) +- 40/Mb (between Media Gateway and Border Router) +- 41 (between FA / Attendant and Mobile IP Home Agent) +- 42/Mb (between Mobile IP Home Agent and Border Router) +- 43/Mb (between FA / Attendant and Border Router) +- 44/Mb (between Mobile IP Home Agent and Border Router) +- 45/Mb (between Mobile IP Home Agent and Border Router) +- 46/Mb (between Border Router and IP Network) +- 47 (between Mobile Station and cdma2000 Access Network) + +Diagram of ANSI-41 evolved Core Network with cdma2000 Access Network Packet Data Subsystem Core Network Architecture Model. The diagram shows various network elements and their interconnections, with the Packet Data Subsystem (PDS) highlighted in blue. + +Figure 6-3 – ANSI-41 evolved Core Network with cdma2000 Access Network Packet Data Subsystem Core Network Architecture Model + +Figure 6-4 shows the entities that comprise the multimedia session capabilities of an All-IP network. These entities are known collectively as the IP Multimedia Session Subsystem (IMS). Figure 6-4 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE – In Figure 6-4 the "IP Multimedia Session Subsystem" is identified by the network elements and reference points highlighted in "blue". + +![Figure 6-4: ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem Core Network Architecture Model. The diagram shows various network elements and their interconnections, with the IMS components highlighted in blue.](366a77fdefb0097b3289b4a011911390_img.jpg) + +The diagram illustrates the architecture of an ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem (IMS) Core Network. The network elements and their interconnections are as follows: + +- Databases:** A group of databases including EIR, DSI, Subscription Profile, Network Policy Rules, and others. They are connected to the AAA element via reference points 1, 2, 3, and 4. +- AAA:** A central authentication, authorization, and accounting element. It is connected to the Position Server (15), Position Determining Entity (18, 19), cdma2000 Access Network (31, 35), Access Gateway (20, 21, 22), Mobile IP Home Agent (41, 43), and Border Router (29). It also has connections to the OSA Service Capability Server (10, 11/Sh), Call Session Control Function (16/Cx, 17/Mg), and Policy Decision Function (23, 50). +- Call Session Control Function:** A central control element for multimedia sessions. It is connected to the AAA (16/Cx, 17/Mg), OSA Service Capability Server (10, 11/Sh), Policy Decision Function (23, 50), Media Resource Function Controller (24/Mr), and Media Gateway (30/Mc). +- Media Resource Function Controller:** A control element for media resources. It is connected to the Call Session Control Function (24/Mr), Media Resource Function Processor (25/Mp), and Media Gateway (26/PSTN, 30/Mc). +- Media Resource Function Processor:** A processing element for media resources. It is connected to the Media Resource Function Controller (25/Mp), Media Gateway (33/Mb), and Mobile IP Home Agent (37/Mb). +- Media Gateway:** A gateway for media streams. It is connected to the Call Session Control Function (30/Mc), Media Resource Function Controller (26/PSTN, 30/Mc), Media Resource Function Processor (33/Mb), and Border Router (40/Mb). +- Border Router:** A router at the edge of the network. It is connected to the Media Gateway (40/Mb), Mobile IP Home Agent (44/Mb), and external networks (46/Mb). +- Mobile IP Home Agent:** A home agent for mobile IP. It is connected to the AAA (41, 43), Media Resource Function Processor (37/Mb), and Border Router (44/Mb). +- External Networks:** PSTN and IP Network, connected to the Border Router (46/Mb). +- Access Network:** cdma2000 Access Network (BTS, BSC/RNC + PCF, MM) and Other Access Networks, connected to the AAA (31, 35) and Access Gateway (32/Mb, 36/Mb). +- Access Gateway:** A gateway for the access network, connected to the AAA (20, 21, 22), cdma2000 Access Network (32/Mb, 36/Mb), and Mobile IP Home Agent (41, 43). +- FA / Attendant:** A forwarding agent, connected to the Access Gateway (41, 43). +- Mobile Station:** The user equipment, connected to the cdma2000 Access Network (47). +- Other Elements:** + - Application Server:** Connected to the OSA Service Capability Server (8/OSA). + - SIP Application Server:** Connected to the Breakout Gateway Control Function (12/ISC, 5/Mk). + - OSA Service Capability Server:** Connected to the Application Server (8/OSA), AAA (10, 11/Sh), and Call Session Control Function (11/Sh, 12/ISC). + - Breakout Gateway Control Function:** Connected to the SIP Application Server (12/ISC, 5/Mk), AAA (9/Mi, 49/Mj), and Policy Decision Function (28/Go). + - Policy Decision Function:** Connected to the AAA (23, 50), Call Session Control Function (23, 50), Breakout Gateway Control Function (28/Go), and Media Gateway (29). + - Position Server:** Connected to the AAA (15) and Position Determining Entity (18, 19). + - Position Determining Entity:** Connected to the Position Server (18, 19) and AAA (18, 19). + +Reference points are labeled with numbers and letters (e.g., 1, 2, 3, 4, 5/Mk, 8/OSA, 11/Sh, 12/ISC, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh). The IMS elements and reference points are highlighted in blue in the original figure. + +Figure 6-4: ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem Core Network Architecture Model. The diagram shows various network elements and their interconnections, with the IMS components highlighted in blue. + +Figure 6-4 – ANSI-41 evolved Core Network with cdma2000 Access Network IP Multimedia Session Subsystem Core Network Architecture Model + +The session control functions within the IMS are logically interconnected in various ways in the session scenarios. Figure 6-5 identifies the reference points within the IMS between these session control entities. In many cases there are dual labels for these reference points either of which may be used in the applicable specifications. + +![Figure 6-5 – Session Control Reference Model. This diagram shows the logical interconnections between various IMS entities. At the top, an IP Multimedia Client (dashed box) connects to a (Proxy) Call Session Control Function (dashed box) via the hh/Gm interface. The (Proxy) CSCF connects to an (Interrogating) Call Session Control Function via the dd/Mw interface. The (Interrogating) CSCF connects to a (Serving) Call Session Control Function via the ff/Mw interface. Below these, a Media Gateway Control Function connects to the (Interrogating) CSCF via the 17/Mg interface and to a Breakout Gateway Control Function via the 49/Mj interface. This Breakout Gateway Control Function connects to another Breakout Gateway Control Function via the 5/Mk interface. The (Serving) CSCF connects to the second Breakout Gateway Control Function via the 9/Mi interface.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +Figure 6-5 – Session Control Reference Model. This diagram shows the logical interconnections between various IMS entities. At the top, an IP Multimedia Client (dashed box) connects to a (Proxy) Call Session Control Function (dashed box) via the hh/Gm interface. The (Proxy) CSCF connects to an (Interrogating) Call Session Control Function via the dd/Mw interface. The (Interrogating) CSCF connects to a (Serving) Call Session Control Function via the ff/Mw interface. Below these, a Media Gateway Control Function connects to the (Interrogating) CSCF via the 17/Mg interface and to a Breakout Gateway Control Function via the 49/Mj interface. This Breakout Gateway Control Function connects to another Breakout Gateway Control Function via the 5/Mk interface. The (Serving) CSCF connects to the second Breakout Gateway Control Function via the 9/Mi interface. + +**Figure 6-5 – Session Control Reference Model** + +Figure 6-6 shows the network reference model for the Converged Access Network (CAN) for the non-roaming case. This system supports access via the Ultra Mobile Broadband (UMB) air interface. + +![Figure 6-6 – Converged Access Network Reference Model, non-Roaming. This diagram illustrates the network architecture for non-roaming. An Access Terminal (AT) connects to an eBS via the UMB-AI interface. The eBS connects to a srv-AGW (MAG) via the U1 interface and to an SRNC via the U2 interface. The SRNC connects to the srv-AGW (MAG) via the U6 interface and to an HRPD AN via the U4 interface. The HRPD AN connects to a PDSN via the A10/A11 interface. The PDSN connects to an ePDIF via the U22b interface and to an Untrusted Non-3 GPP2 System via the U21 interface. The srv-AGW (MAG) connects to an anc-AGW (FA/LMA/MAG) via the U15' (PMIP) interface and has a reference point U15. The anc-AGW (FA/LMA/MAG) connects to a HA (LMA) via the U16 (Note2) (PMIP/CMIP) interface and to a PDSN via the U19 interface. The HA (LMA) connects to a PCRF via the U20 interface and to a Trusted Non-3 GPP2 System via the U17a interface. The PCRF connects to an IP Services (AF) cloud via the U23 interface and to a VAAA via the U14 interface. The VAAA connects to a BAAA via the U14 interface. The BAAA connects to an HAAA. Various other reference points are labeled: U3 (eBS), U15 (srv-AGW), U17b (HA to PDSN), U22a (HA to PDSN), U29 (HA to anc-AGW), and CMIP/PMIP (anc-AGW to HA). Notes include: (Note1) near VAAA, (Note2) near U16, and (Note3) near PCRF.](e354b57563dae469c00b412b2abdf765_img.jpg) + +Figure 6-6 – Converged Access Network Reference Model, non-Roaming. This diagram illustrates the network architecture for non-roaming. An Access Terminal (AT) connects to an eBS via the UMB-AI interface. The eBS connects to a srv-AGW (MAG) via the U1 interface and to an SRNC via the U2 interface. The SRNC connects to the srv-AGW (MAG) via the U6 interface and to an HRPD AN via the U4 interface. The HRPD AN connects to a PDSN via the A10/A11 interface. The PDSN connects to an ePDIF via the U22b interface and to an Untrusted Non-3 GPP2 System via the U21 interface. The srv-AGW (MAG) connects to an anc-AGW (FA/LMA/MAG) via the U15' (PMIP) interface and has a reference point U15. The anc-AGW (FA/LMA/MAG) connects to a HA (LMA) via the U16 (Note2) (PMIP/CMIP) interface and to a PDSN via the U19 interface. The HA (LMA) connects to a PCRF via the U20 interface and to a Trusted Non-3 GPP2 System via the U17a interface. The PCRF connects to an IP Services (AF) cloud via the U23 interface and to a VAAA via the U14 interface. The VAAA connects to a BAAA via the U14 interface. The BAAA connects to an HAAA. Various other reference points are labeled: U3 (eBS), U15 (srv-AGW), U17b (HA to PDSN), U22a (HA to PDSN), U29 (HA to anc-AGW), and CMIP/PMIP (anc-AGW to HA). Notes include: (Note1) near VAAA, (Note2) near U16, and (Note3) near PCRF. + +**Figure 6-6 – Converged Access Network Reference Model, non-Roaming** + +Figure 6-7 shows the network reference model for the Converged Access Network (CAN) for the roaming case. + +![Figure 6-7 – Converged Access Network Reference Model – Roaming. This diagram illustrates the network architecture for roaming, divided into a Visited Network and a Home Network by a dashed line labeled 'Tx'. In the Visited Network, an AT (Access Terminal) connects to an eBS (evolved Base Station) via UMB-AI. The eBS connects to an AGW (FA/MAG) via U1 and U2. The AGW connects to a VAAA (Visited AAA) via U14 and to an SRNC via U6. The SRNC connects to an HRPD-AN via U4. The AGW also connects to a Trusted Non-3GPP2 System via U19a, U19b, U23, U24a, U24b, U24c, and U26 (PMIP). The AGW connects to an ePDIF via U28. The ePDIF connects to a PDSN via U22b. The PDSN connects to an Untrusted non-3GPP2 System via U21 and A10/A11. The AGW also connects to an IP Services (AF) cloud via U30. The AF connects to a HA (Home Agent) via U31 and U32. The HA connects to a HAAA (Home AAA) via U27 (CMIP). The HA also connects to a V-PCRF via U20. The V-PCRF connects to an H-PCRF via U18. The H-PCRF connects to a Trusted non-3GPP2 System via U25a and U25b. The H-PCRF also connects to an ePDIF via U29. The diagram includes several notes: (Note1) near VAAA, (Note2) near the Tx line, (Note3) near U27, and (Note4) near U18.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Figure 6-7 – Converged Access Network Reference Model – Roaming. This diagram illustrates the network architecture for roaming, divided into a Visited Network and a Home Network by a dashed line labeled 'Tx'. In the Visited Network, an AT (Access Terminal) connects to an eBS (evolved Base Station) via UMB-AI. The eBS connects to an AGW (FA/MAG) via U1 and U2. The AGW connects to a VAAA (Visited AAA) via U14 and to an SRNC via U6. The SRNC connects to an HRPD-AN via U4. The AGW also connects to a Trusted Non-3GPP2 System via U19a, U19b, U23, U24a, U24b, U24c, and U26 (PMIP). The AGW connects to an ePDIF via U28. The ePDIF connects to a PDSN via U22b. The PDSN connects to an Untrusted non-3GPP2 System via U21 and A10/A11. The AGW also connects to an IP Services (AF) cloud via U30. The AF connects to a HA (Home Agent) via U31 and U32. The HA connects to a HAAA (Home AAA) via U27 (CMIP). The HA also connects to a V-PCRF via U20. The V-PCRF connects to an H-PCRF via U18. The H-PCRF connects to a Trusted non-3GPP2 System via U25a and U25b. The H-PCRF also connects to an ePDIF via U29. The diagram includes several notes: (Note1) near VAAA, (Note2) near the Tx line, (Note3) near U27, and (Note4) near U18. + +Figure 6-7 – Converged Access Network Reference Model – Roaming + +## 7 Network Entities + +### 7.1 Authentication, Authorization and Accounting (AAA) + +The AAA is an entity that provides IP based Authentication, authorization, and Accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions. + +- The Authentication Function provides Authentication of users. +- The Authorization Function of AAA provides authorization of service requests based on subscriber profiles, and network policy. It also generates keys required for establishing security associations between PDSNs in access provider networks and HAs in home IP networks. + +The Accounting Function gathers accounting data concerning the services used by individual subscribers. + +### 7.2 Authentication Centre (AC) + +The AC is an entity that manages the authentication information related to the MS. The AC may, or may not be located within, and be indistinguishable from an HLR. An AC may serve more than one HLR. + +### 7.3 Call Data Collection Point (CDCP) + +The CDCP is the entity that collects the call detail information. + +### **7.4 Call Data Generation Point (CDGP)** + +The CDGP is an entity which provides call detail information to the CDCP [in ANSI-124 format]. This may be the entity that converts call detail information from a proprietary format into a standard format. All information from the CDGP to the CDCP must be in this standard format. + +### **7.5 Call Data Information Source (CDIS)** + +The CDIS is an entity that can be the source of call detail information. This information may be in proprietary format. It is not required to be in the standard format. + +### **7.6 Call Data Rating Point (CDRP)** + +The CDRP is the entity that takes the unrated call detail information and applies the applicable charge and tax related information. The charge and tax information is added using the standard format. + +### **7.7 Collection Function (CF) – [Intercept]** + +The CF is an entity that is responsible for collecting intercepted communications for a lawfully authorized law enforcement agency. + +The CFs typically include: + +- the ability to receive and process call contents information for each intercept subject. +- the ability to receive information regarding each intercept subject (e.g., call associated or non-call associated) from the Delivery function and process it. + +### **7.8 Coordinate Routing Data Base (CRDB)** + +The CRDB is an entity that stores information to translate a given position expressed as a latitude and longitude to a string of digits. + +### **7.9 Customer Service Centre (CSC)** + +The CSC is an entity where service provider representatives receive telephone calls from customers wishing to subscribe to initial wireless service or request a change in the customer's existing service. The CSC interfaces proprietarily with the OTAF to perform network and MS related changes necessary to complete the service provisioning request. + +### **7.10 Delivery Function (DF) – [Intercept]** + +The DF is an entity that is responsible for delivering intercepted communications to one or more collection functions. + +The DFs typically include: + +- the ability to accept call contents for each intercept subject over one or more channels from each Access function. +- the ability to deliver call contents for each intercept subject over one or more channels to a Collection function as authorized for each law enforcement agency. +- the ability to accept information over one or more data channels and combine that information into a single data flow for each intercept subject. +- the ability to filter or select information on an intercept subject before delivery to a Collection function as authorized for a particular law enforcement agency. +- the optional ability to detect audio in-band DTMF digits for translation and delivery to a Collection function as authorized for a particular law enforcement agency. + +- the ability to duplicate and deliver information on the intercept subject to one or more Collection functions as authorized for each law enforcement agency. +- the ability to provide security to restrict access. + +### **7.11 Equipment Identity Register (EIR)** + +The EIR is an entity that is the register to which user equipment identity may be assigned for record purposes. The nature, purpose, and utilization of this information is an area for further study. + +### **7.12 evolved Packet Data Interworking Function (ePDIF)** + +The evolved Packet Data Interworking Function (ePDIF) is an Interworking function for connectivity between a 3GPP2 network and an untrusted non-3GPP2 network (for example, WiFi AP). + +### **7.13 Home Agent (HA)** + +The HA is an entity that: + +- authenticates Mobile IP registrations from the MS. +- redirects packets to the foreign agent component of the PDSN, and optionally receives and routes reverse packets from the foreign agent component of the PSDN. +- may establish, maintain and terminate secure communications to the PDSN. +- receives provisioning information from the AAA Function for users. +- may assign a dynamic home IP address. + +Depending on the architectural configuration, the HA may include the Local Mobility Agent (LMA). + +### **7.14 Home Location Register (HLR)** + +The HLR is the location register to which a user identity is assigned for record purposes such as subscriber information (e.g., Electronic Serial Number (ESN), Mobile Directory Number (MDN), Profile Information, Current Location, Authorization Period). + +### **7.15 Intelligent Peripheral (IP)** + +The IP is an entity that performs specialized resource functions such as playing announcements, collecting digits, performing speech-to-text or text-to-speech conversion, recording and storing voice messages, facsimile services, data services, etc. + +### **7.16 Intercept Access Point (IAP)** + +The IAP is an entity that provides access to the communications to, or from, the equipment, facilities, or services of an intercept subject. + +### **7.17 Interworking Function (IWF)** + +The IWF is an entity that provides information conversion for one or more WNEs. An IWF may have an interface to a single WNE providing conversion services. An IWF may augment an identified interface between two WNEs, providing conversion services to both WNEs. + +### **7.18 IP Services** + +IP Services comprise any IP based services provided by the operator or 3rd party. This may be part of the Internet or a closed network + +### **7.19 Local Position Determining Entity (LPDE)** + +The LPDE facilitates the determination of the position or geographical location of a wireless terminal. Each LPDE supports one or more position determining technologies. Multiple LPDEs using the same technology may serve the coverage area of a Mobile Position Centre (MPC) and the multiple LPDEs each using a different technology may serve the same coverage area of an MPC. Local PDEs (LPDEs) reside at the Base Station (BS). + +### **7.20 Managed Wireless Network Entity (MWNE)** + +A MWNE [within the Collective Entity] or any specific network entity having Operation System wireless management needs, including another Operations System. + +### **7.21 Message Centre (MC)** + +The MC is an entity that stores and forwards short messages. The MC may also provide supplementary services for Short Message Service (SMS). + +### **7.22 Mobile Position Centre (MPC)** + +The MPC selects a PDE to determine the position of a mobile station. The MPC may restrict access to position information (e.g., require that the MS be engaged in an emergency call or only release position information to authorized network entities). + +### **7.23 Mobile Switching Centre (MSC)** + +The MSC switches circuit mode MS originated or MS terminated traffic. An MSC is usually connected to at least one BS. It may connect to the other public networks (PSTN, ISDN, etc.), other MSCs in the same network, or MSCs in different networks. The MSC may store information to support these capabilities. + +### **7.24 Number Portability Database (NPDB)** + +The NPDB is an entity which provides portability information for portable Directory Numbers. + +### **7.25 Over-The-Air Service Provisioning Function (OTAF)** + +The OTAF is an entity that interfaces proprietarily to CSCs to support service provisioning activities. The OTAF interfaces with the MSC to send MS orders necessary to complete service provisioning requests. + +### **7.26 Packet Data Network (PDN)** + +A PDN, such as the Internet, provides a packet data transport mechanism between processing network entities capable of using such services. + +### **7.27 Packet Data Serving Node (PDSN)** + +The PDSN routes MS originated or MS terminated packet data traffic. The PDSN establishes, maintains, and terminates link layer sessions to MSs. The PDSN may interface to one or more MSs and may interface to one or more PDNs. + +### **7.28 Position Determining Entity (PDE)** + +A PDE facilitates determination of the position or geographical location of a wireless terminal. Each PDE supports one or more position determining technologies. Multiple PDEs using the same technology may serve the coverage area of a Mobile Position Centre (MPC) and the multiple PDEs each using a different technology may serve the same coverage area of an MPC. + +### **7.29 Service Control Point (SCP)** + +The SCP is an entity that acts as a real-time database and transaction processing system that provides service control and service data functionality. + +### **7.30 Service Node (SN)** + +The SN is an entity that provides service control, service data, specialized resources and call control functions to support bearer-related services. + +### **7.31 Short Message Entity (SME)** + +The SME is an entity that composes and decomposes short messages. A SME may, or may not be located within, and be indistinguishable from, an HLR, MC, VLR, MS, or MSC. + +### **7.32 Visitor Location Register (VLR)** + +The VLR is the location register other than the HLR used by an MSC to retrieve information for handling of calls to or from a visiting subscriber. The VLR may, or may not be located within, and be indistinguishable from an MSC. The VLR may serve more than one MSC. + +### **7.33 Voice Message Centre (VMS)** + +A VMS stores received voice messages, data messages e.g., email, or both message types and supports a method to retrieve previously stored messages. A VMS may also support (on a Directory Number basis) notification of the presence of stored messages and notification of a change in the number of voice messages, data messages, or both message types that are waiting retrieval. + +### **7.34 Wireless Network Entity (WNE)** + +A Network Entity in the wireless Collective Entity. + +The remaining text in this section is based on reference [13 a-c] section 2.1. + +### **7.35 Access Gateway (AGW)** + +The Access Gateway (AGW) is an entity that provides the user's "point of IP connectivity" to the network. That is, the AGW is in effect the first-hop router for the mobile terminal. The AGW performs layer 3 services and above, including hot-lining, accounting, policy enforcement, etc. + +### **7.36 Access Terminal (AT)** + +The access terminal is the subscriber device supported by the network. + +### **7.37 Application Server** + +Application Servers provide value-added network-based services for wireless subscribers. These services may be accessed via the OSA Service Capability Server (OSA-SCS) or accessed directly from the user's mobile station via other network entities, by-passing the OSA-SCS. + +### **7.38 Authentication, Authorization and Accounting (AAA)** + +The AAA is an entity that provides IP based Authentication, authorization, and Accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions. + +- The Authentication Function is an entity that provides Authentication of terminal devices and subscribers. + +- The Authorization Function of AAA provides authorization of requests for services and/or bandwidth, etc. and has access to the Policy Repository, the Directory Services, Subscriber Profiles, and the Device Register. +- The Accounting Function gathers data concerning the services, QoS, and multimedia resources requested and used by individual subscribers. + +### **7.39 Border Router (BR)** + +The BR connects the Core Network with peer networks (e.g., other service providers, corporate networks, Internet). The BR performs IP packet routing, exterior gateway routing protocols, and policing of incoming and outgoing traffic, ensuring traffic complies with defined Service Level Agreements established with peer networks. The BR may intercept any QoS allocation request, and issue a request to the Policy Decision Function (PDF), which shall verify that the requested inbound and/or outbound QoS is available. A successful response from the PDF may cause the BR to forward the bandwidth allocation request to its final destination. + +### **7.40 Breakout Gateway Control Function (BGCF)** + +The BGCF selects the network in which PSTN breakout is to occur and, within the network where the breakout is to occur, selects the MGCF. + +### **7.41 Call Session Control Function (CSCF)** + +The CSCF establishes, monitors, supports, releases Multimedia sessions, and manages the user's service interactions. + +### **7.42 Databases (DB)** + +The information in the core network DBs may include but is not limited to EIR, Dynamic Subscriber Information, Network Policy Rules and Subscriber Profile data. + +### **7.43 evolved Base Station (eBS)** + +The Evolved base Station (eBS) provides the over-the-air signalling and user data transport that is used by the AT for connectivity to the radio access network. + +### **7.44 IP Multimedia Client** + +The IP Multimedia Client communicates with Application Servers, P-CSCFs, and other IP Multimedia Clients. The IP Multimedia Client is an application that resides in the MS. + +### **7.45 IP Network** + +The IP network corresponds to IP based packet data networks that provide a transport mechanism between the core network and external IP networks. IP Network represents packet networks connected to the core network including the public Internet, private IP backbone networks and private IP networks such as corporate Intranets. + +### **7.46 Local Mobility Anchor (LMA)** + +The Local Mobility Anchor is the home agent for the mobile node in the Proxy Mobile IPv6 domain. It is the topological anchor point for the mobile node's home prefix and is the entity that manages the mobile node's reachability state. + +### **7.47 Media Gateway (MGW)** + +The MGW provides an interface between the packet environment of the Core Network and the circuit switched environment of the PSTN for bearer traffic, when equipped with circuit capabilities. The MGW may provide vocoding and/or transcoding functions to the bearer traffic. The MGW may also provide modem functions to convert digital byte streams to and from audio modem tones placed on circuits, and may provide the capability to terminate PPP (Point-to-Point Protocol) connections. It also provides policy enforcement relative to its activities and resources. + +### **7.48 Media Gateway Control Function (MGCF)** + +The MGCF provides the ability to control a Media Gateway through standardized interfaces. Such control includes allocation and de-allocation of resources of the Media Gateway, as well as modification of the usage of those resources. + +### **7.49 Media Resource Function Controller (MRFC)** + +The MRFC, in conjunction with the MRFP, provides a set of resources within the core network that are useful in supporting services to subscribers. The MRFC, in conjunction with the MRFP, provides multi-way conference bridges, announcement playback services, tone playback services, etc. + +### **7.50 Media Resource Function Processor (MRFP)** + +The MRFP, in conjunction with the controlling entity, provides multi-way conference bridges, announcement playback services, tone playback services, etc. + +### **7.51 Mobile IP Home Agent (HA)** + +The HA provides two major functions: registering the current point of attachment of the user, and forwarding of IP packets to and from the current point of attachment (IPv4 Care of Address [CoA] and/or IPv6 Co-located CoA) of the user. The HA accepts registration requests using the Mobile IP protocol and uses the information in those requests to update internal information about the current point of attachment of the user, i.e., the current IP address to be used to transmit and receive IP packets to and from that user. The HA interacts with the AAA to receive Mobile IP registration requests that have been authenticated, and to return Mobile IP registration responses. The HA also interacts with the Access Gateway to receive subsequent Mobile IP registration requests. The HA may interact with several network entities in performing its work of forwarding IP packets to the current point of attachment of the user. + +### **7.52 Mobile Station (MS)** + +The MS is a wireless terminal used by subscribers to access the Legacy MS Domain or the IP Multimedia Domain services over a radio interface. MSs include portable units (e.g., hand-held units), units installed in vehicles, and somewhat paradoxically, fixed location MSs. The MS is the interface equipment used to terminate the radio path at the subscriber. A MS is a ME with a programmed UIM. + +### **7.53 non-3GPP2 System** + +A non-3GPP2 System may be trusted or untrusted. The AT accesses an operator's network via an ePDIF if the access network is untrusted, and the AT accesses an operators network directly (i.e., without an ePDIF) if the access network is trusted + +### **7.54 OSA Service Capability Server (OSA-SCS)** + +The OSA-SCS provides access to network resources needed during service application execution. The interface towards the Application Server uses application programming interfaces such as Open Service Architecture (OSA). The interfaces towards other network entities use the relevant protocols. + +### **7.55 Policy Decision Function (PDF)** + +The PDF provides management of core network QoS resources within its own core network necessary to support services to network users. It communicates with the Access Gateway to provide authorization of resource allocations. The PDF makes policy decisions with regard to use of core network QoS resources within its own network, including consideration of Service Level Agreements (SLAs [Note, the maintenance of SLAs is for further study.]). QoS policy information for network resource utilization may be forwarded to and cached by the PDF. + +### **7.56 Position Determining Entity (PDE)** + +The PDE communicates with the Position Server to determine the precise geographic position of the MS based on input data provided by the Position Server. + +### **7.57 Position Server** + +The Position Server provides geographic position information to requesting entities. + +### **7.58 Public Switched Telephone Network (PSTN)** + +The PSTN is defined in accordance with the appropriate applicable national and regional standards. + +### **7.59 Proxy Mobile Agent (PMA) or Mobile Access Gateway (MAG)** + +The Proxy mobile agent (or mobile access gateway) is a function that manages the mobility related signalling for a mobile node that is attached to its access link. It is responsible for tracking the mobile node's attachment to the link and for signalling the mobile node's local mobility anchor. PMA is PMIPv4 term and MAG is PMIPv6 term. + +### **7.60 Policy and Charging Rules Function (PCRF)** + +The PCRF provides rules to the AGW over the U23 reference point for Quality of Service and charging control. + +### **7.61 Session Reference Network Controller (SRNC)** + +The Session Reference Network Controller (SRNC) is responsible for maintaining the session reference with the AT. The SRNC is also responsible for supporting idle state management of the AT, and providing paging control functions when the AT is idle. The SRNC contains a Session Anchor Access Network Route Instance (ANRI) for each AT it is supporting. + +## **8 Reference Points** + +The following text is based on reference [12 a-d] section 2.1.2. + +### **8.1 Reference Point B** + +Reference Point B is the interface between MSC and the VLR. + +### **8.2 Reference Point C** + +Reference Point C is the interface between the MSC and the HLR. + +### **8.3 Reference Point D** + +Reference Point D is the interface between the VLR and HLR. + +### **8.4 Reference Point d** + +Reference Point d is the interface between an IAP and the DF. + +### **8.5 Reference Point D1** + +Reference Point D1 is the interface between the OTAF and the VLR. + +### **8.6 Reference Point Di** + +Reference Point Di is the interface between: + +- The IP and the ISDN +- The IWF and the ISDN +- The MSC and the ISDN [ESBE] +- The SN and the ISDN + +### **8.7 Reference Point E** + +Reference Point E is the interface between the MSC and MSC. + +### **8.8 Reference Point E3** + +Reference Point E3 is the interface between MPC and the MSC. + +### **8.9 Reference Point E5** + +Reference Point E5 is the interface between the MPC and the PDE. + +### **8.10 Reference Point E9** + +Reference Point E9 is the interface between the MPC and the SCP. + +### **8.11 Reference Point E11** + +Reference Point E11 is the interface between the CRDB and the MPC. + +### **8.12 Reference Point E12** + +Reference Point E12 is the interface between MSC and the PDE. + +### **8.13 Reference Point e** + +Reference Point e is the interface between the CF and the DF. + +### **8.14 Reference Point F** + +Reference Point F is the interface between the MSC and the EIR. + +### **8.15 Reference Point G** + +Reference Point G is the interface between the VLR and the VLR. + +### **8.16 Reference Point H** + +Reference Point H is the interface between the HLR and the AC. + +### **8.17 Reference Point I** + +Reference Point I is the interface between the CDIS and the CDGP. + +### **8.18 Reference Point J** + +Reference Point J is the interface between the CDGP and the CDCP. + +### **8.19 Reference Point K** + +Reference Point K is the interface between the CDGP and the CDRP. + +### **8.20 Reference Point L** + +Reserved. + +### **8.21 Reference Point M1** + +Reference Point M1 is the interface between the SME and the MC. + +### **8.22 Reference Point M2** + +Reference Point M2 is the MC to MC interface. + +### **8.23 Reference Point M3** + +Reference Point M3 is the SME to SME interface. + +### **8.24 Reference Point N** + +Reference Point N is the interface between the HLR and the MC. + +### **8.25 Reference Point N1** + +Reference Point N1 is the interface between the HLR and the OTAF. + +### **8.26 Reference Point O1** + +Reference Point O1 is the interface between an MWNE and the OSF. + +### **8.27 Reference Point O2** + +Reference Point O2 is the interface between an OSF and the OSF. + +### **8.28 Reference Point P1** + +Reference Point P1 is the interface between: + +- The AAA and the AAA, +- The AAA and the PDN, +- The IWF and the PDN, +- The MSC and the PDN, plus +- The PDSN and the PDN. + +### **8.29 Reference Point Q** + +Reference Point Q is the interface between the MC and the MSC. + +### **8.30 Reference Point Q1** + +Reference Point Q1 is the interface between the MSC and the OTAF. + +### **8.31 Reference Point T1** + +Reference Point T1 is the interface between the MSC and the SCP. + +### **8.32 Reference Point T2** + +Reference Point T2 is the interface between the HLR and the SCP. + +### **8.33 Reference Point T3** + +Reference Point T3 is the interface between the IP and the SCP. + +### **8.34 Reference Point T4** + +Reference Point T4 is the interface between the HLR and the SN. + +### **8.35 Reference Point T5** + +Reference Point T5 is the interface between the IP and the MSC. + +### **8.36 Reference Point T6** + +Reference Point T6 is the interface between the MSC and the SN. + +### **8.37 Reference Point T7** + +Reference Point T7 is the interface between the SCP and the SN. + +### **8.38 Reference Point T8** + +Reference Point T8 is the interface between the SCP and the SCP. + +### **8.39 Reference Point T9** + +Reference Point T9 is the interface between the HLR and the IP. + +### **8.40 Reference Point V** + +Reference Point V is the interface between the OTAF and the OTAF. + +### **8.41 Reference Point X** + +Reference Point X is the interface between the CSC and the OTAF. + +### **8.42 Reference Point Y** + +Reference Point Y is the interface between a Wireless Network Entity (WNE) and the IWF. + +### **8.43 Reference Point Z** + +Reference Point Z is the interface between the MSC and the NPDB. + +### **8.44 Reference Point Z1** + +Reference Point Z1 is the interface between the MSC and the VMS. + +### **8.45 Reference Point Z2** + +Reference Point Z2 is the interface between the HLR and the VMS. + +### **8.46 Reference Point Z3** + +Reference Point Z3 is the interface between the MC and the VMS. + +The remaining text in this section is based on reference [13 a-c] section 2.1. + +An interface exists when two Network Entities are interconnected through exactly one signalling or bearer stream Reference Point. The Reference Points and their associated Network Entities are: + +### **8.47 Reference Point 1** + +Reference Point 1 is the signalling interface between the Databases and the Position Server [Multimedia Domain only]. + +### **8.48 Reference Point 2** + +Reference Point 2 is the signalling interface between the Databases and the cdma2000 Access Network. + +#### **8.49 Reference Point 3** + +Reference Point 3 is the signalling interface between the Databases and the Policy Decision Function [Multimedia Domain only]. + +#### **8.50 Reference Point 4** + +Reference Point 4 is the signalling interface between the Databases and the AAA. + +#### **8.51 Reference Point 5/Mk** + +Reference Point 5/Mk is the signalling interface between Breakout Gateway Control Functions [Multimedia Domain only]. + +#### **8.52 Reference Point 6** + +Reference Point 6 is the signalling interface between the Databases and the Legacy MS Domain Support [Legacy MS Domain only]. + +#### **8.53 Reference Point 7** + +Reference Point 7 is the signalling interface between the OSA Service Capability Server and the Databases. + +#### **8.54 Reference Point 8/OSA** + +Reference Point 8/OSA is the signalling interface between the OSA Application Server and the OSA Service Capability Server. Reference Point 8/OSA may employ interfacing techniques that support a wide spectrum of capabilities, ranging from secure (e.g., application programming interfaces such as Parlay, used for un-trusted parties) to non-secure (e.g., used for trusted parties). + +#### **8.55 Reference Point 9/Mi** + +Reference Point 9/Mi is the signalling interface between the Visited Network's BGCF and the Home Service Network's Serving-CSCF + +#### **8.56 Reference Point 10** + +Reference Point 10 is the signalling interface between the Position Server and the OSA Service Capability Server [Multimedia Domain only]. + +#### **8.57 Reference Point 11/Sh** + +Reference Point 11/Sh is the signalling interface between the SIP Application Server and the AAA and between the OSA Service Capability Server and the AAA for user's service authentication and/or authorization, and for retrieving information from the MMD database [Multimedia Domain only]. + +#### **8.58 Reference Point 12/ISC** + +Reference Point 12/ISC is the signalling interface between the SIP Application Server and Call Session Control Function and between the OSA Service Capability Server and the Call Session Control Function for service control [Multimedia Domain only]. + +#### **8.59 Reference Point 13** + +Reference Point 13 is the signalling interface between the Legacy MS Domain Support and the PSTN [Legacy MS Domain only]. + +#### **8.60 Reference Point 14** + +Reference Point 14 is the signalling interface between the Legacy MS Domain Support and the MAP (TIA/EIA-41 & GSM) [Legacy MS Domain only]. + +#### **8.61 Reference Point 15** + +Reference Point 15 is the signalling interface between the Position Server and AAA. + +#### **8.62 Reference Point 16/Cx** + +Reference Point 16/Cx is the signalling interface between the AAA and the Call Session Control Function [Multimedia Domain only]. + +#### **8.63 Reference Point 17/(Mg)** + +Reference Point 17/(Mg) is the signalling interface between the Call Session Control Function and the Media Gateway Control Function [Multimedia Domain only]. + +#### **8.64 Reference Point 18** + +Reference Point 18 is the signalling interface between the Position Server and the Position Determining Entity. + +#### **8.65 Reference Point 19** + +Reference Point 19 is the signalling interface between the Position Server and the Access Gateway [Multimedia Domain only]. + +#### **8.66 Reference Point 20** + +Reference Point 20 is the signalling interface between the AAA and the cdma2000 Access Network [Multimedia Domain only]. + +#### **8.67 Reference Point 21** + +Reference Point 21 is the signalling interface between the AAA and Access Gateway. + +#### **8.68 Reference Point 22** + +Reference Point 22 is the signalling interface between the AAA and the Mobile IP Home Agent. + +#### **8.69 Reference Point 23** + +Reference Point 23 is the signalling interface between the AAA and the Policy Decision Function [Multimedia Domain only]. + +#### **8.70 Reference Point 24/Mr** + +Reference Point 24/Mr is the signalling interface between the Call Session Control Function and the Media Resource Function Controller [Multimedia Domain only]. + +#### **8.71 Reference Point 25/Mp** + +Reference Point 25/Mp is the signalling interface between the Media Resource Function Controller and the Media Resource Function Processor. + +#### **8.72 Reference Point 26/PSTN** + +Reference Point 26/PSTN is the signalling interface between the Media Gateway Control Function and the PSTN [Multimedia Domain only]. + +#### **8.73 Reference Point 27** + +Reference Point 27 is the bearer stream interface between the cdma2000 Access Network and the Media Gateway [Legacy MS Domain only]. + +#### **8.74 Reference Point 28/Go** + +Reference Point 28/Go is the signalling interface between the Policy Decision Function and Access Gateway. + +#### **8.75 Reference Point 29** + +Reference Point 29 is the signalling interface between Policy Decision Function and the Border Router. + +#### **8.76 Reference Point 30/Mc** + +Reference Point 30/Mc is the signalling interface between the Media Gateway Control Function and the Media Gateway [Multimedia Domain only]. + +#### **8.77 Reference Point 31** + +Reference Point 31 is the bearer stream interface between cdma2000 Access Network and the Access Gateway. + +#### **8.78 Reference Point 32/Mb** + +Reference Point 32/Mb is the bearer stream interface between the Access Gateway and the Media Resource Function Processor [Multimedia Domain only]. + +#### **8.79 Reference Point 33/Mb** + +Reference Point 33/Mb is the bearer stream interface between the Media Resource Function Processor and the Media Gateway. + +#### **8.80 Reference Point 34/Mb** + +Reference Point 34/Mb is the bearer stream interface between the Media Gateway and the PSTN. + +#### **8.81 Reference Point 35** + +Reference Point 35 is the signalling interface between the cdma2000 Access Network and the Access Gateway. + +#### **8.82 Reference Point 36/Mb** + +Reference Point 36/Mb is the bearer stream interface between the Access Gateway and the Media Gateway [Multimedia Domain only]. + +#### **8.83 Reference Point 37/Mb** + +Reference Point 37/Mb is the bearer stream interface between the Media Resource Function Processor and the Mobile IP Home Agent [Multimedia Domain only]. + +#### **8.84 Reference Point 38/Mb** + +Reference Point 38/Mb is the bearer stream interface between the Media Gateway and the Mobile IP Home Agent [Multimedia Domain only]. + +#### **8.85 Reference Point 39** + +Reference Point 39 is the signalling interface between the Media Gateway and the Legacy MS Domain Support [Legacy MS Domain only]. + +#### **8.86 Reference Point 40/Mb** + +Reference Point 40/Mb is the bearer streams interface between the Media Gateway and the Border Router. + +#### **8.87 Reference Point 41** + +Reference Point 41 is the signalling interface between the Access Gateway and the Mobile IP Home Agent. + +#### **8.88 Reference Point 42/Mb** + +Reference Point 42/Mb is the bearer streams interface between the Media Resource Function Processor and the Border Router. + +#### **8.89 Reference Point 43/Mb** + +Reference Point 43/Mb is the bearer streams interface between the Access Gateway and the Mobile IP Home Agent. + +#### **8.90 Reference Point 44/Mb** + +Reference Point 44/Mb is the bearer stream interface between the Mobile IP Home Agent and the Border Router. + +#### **8.91 Reference Point 45/Mb** + +Reference Point 45/Mb is the bearer stream interface between the Access Gateway and the Border Router. + +#### **8.92 Reference Point 46/Mb** + +Reference Point 46/Mb is the bearer stream interface between the Border Router and the IP Network. + +#### **8.93 Reference Point 47** + +Reference Point 47 is the Radio Link (air interface) between the Mobile Station and the cdma2000 Access Network. + +#### **8.94 Reference Point 48** + +Reference Point 48 is the signalling interface between the cdma2000 Access Network and the Legacy MS Domain Support [Legacy MS Domain only]. + +#### **8.95 Reference Point 49/(Mj)** + +Reference Point 49/(Mj) is the signalling interface between the Breakout Gateway Control Function and the Media Gateway Control Function [Multimedia Domain only]. + +#### **8.96 Reference Point 50** + +Reference Point 50 is the signalling interface between the Policy Decision Function and the P-CSCF [Multimedia Domain only]. + +#### **8.97 Reference Point U1** + +Reference Point U1 carries control and bearer information between evolved Base Station (eBS) and the Access gateway (AGW). The U1 reference point includes interfaces for bearer transport (user data and signalling), QoS, and accounting. + +#### **8.98 Reference Point U2** + +Reference Point U2 provides interfaces for carrying control information between the eBS and the SRNC. + +#### **8.99 Reference Point U3** + +Reference Point U3 carries control and bearer information between eBSs. + +#### **8.100 Reference Point U4** + +Reference Point U4 carries control information between SRNCs. + +#### **8.101 Reference Point U6** + +Reference Point U6 connects the SRNC to the AGW. + +#### **8.102 Reference Point U14** + +Reference Point U14 connects the anc-AGW or AGW with the AAA infrastructure via the Visited AAA server (VAAA). This reference point implements a signalling protocol to support user authentication, authorization and accounting. + +#### **8.103 Reference Point U15** + +Reference Point U15 carries control and bearer information between srv-AGW. U15 reference point provides local mobility based on PMIP. + +#### **8.104 Reference Point U15'** + +Reference Point U15' carries control and bearer information between two AGWs: the Serving AGW (srv-AGW) and the Anchor AGW (anc-AGW). This reference point is not exposed if the srv-AGW and anc-AGW are collocated. This reference point also carries policy information. + +#### **8.105 Reference Point U16** + +Reference Point U16 carries control and bearer information between the AGW and the Home Agent (HA), and supports bearer transport and signalling for mobility. + +#### **8.106 Reference Point U17** + +Reference Point U17 carries control and bearer information between the 3GPP2 network and a non-3GPP2 network. The U17a reference point carries control and bearer information between the 3GPP2 network and a trusted non-3GPP2 network (e.g., 3GPP SAE/LTE or WiMAX). The U17b reference point carries control and bearer information between the 3GPP2 network and an untrusted non-3GPP2 network via the ePDIF (e.g., a WiFi network). + +#### **8.107 Reference Point U18** + +Reference Point U18 carries control information between a Visited PCRF (V-PCRF) and a Home PCRF (H-PCRF) in order to transfer policy and charging rules between domains. + +#### **8.108 Reference Point U19** + +Reference Point U19 carries control and bearer (optional) information between the AGW and the trusted non-3GPP2 System (U19a), and between the AGW and the ePDIF (U19b), and between the anc-AGW/AGW and the PDSN (U19/U19c). The U19 reference point supports fast/seamless handoff between a CAN and another system. + +#### **8.109 Reference Point U20** + +Reference Point U20 connects the HA and the PCRF, and allows (QoS) policy and charging information to be conveyed to the HA. + +#### **8.110 Reference Point U21** + +Reference Point U21 connects the ePDIF to an untrusted non-3GPP2 access network. + +#### **8.111 Reference Point U22** + +Reference Point U22 provides two separate interfaces: U22a and U22b. The U22a reference point connects the PDSN to a trusted non-3GPP2 network. For this connection the ePDIF is not required to be on the data path. The U22b reference point, however, carries control and bearer information between the PDSN and an untrusted non-3GPP2 network. For this connection the ePDIF is required to be on the data path. + +#### **8.112 Reference Point U23** + +Reference Point U23 carries control information from the (QoS) Policy and Charging Rules Function (PCRF) to the anc-AGW/AGW. + +#### **8.113 Reference Point U24** + +Reference Point U24 carries control and bearer information between an LMA and another system. The U24 reference point carries control and bearer information with PMIP between the LMA and the trusted non-3GPP2 System (U24a), and between the LMA and the ePDIF (U24b), and between the LMA and the PDSN (U24c). The U24 reference point supports handoff between a CAN and another system. + +#### **8.114 Reference Point U25** + +Reference Point U25 carries control and bearer information with CMIP between the HA and the trusted non-3GPP2 System (U25a), and between the HA and the ePDIF (U25b). The U25 reference point supports handoff between a CAN and another system. + +#### **8.115 Reference Point U26** + +Reference Point U26 carries control and bearer information with PMIP between the LMA and the AGW and supports handoff between AGWs. + +#### **8.116 Reference Point U27** + +Reference Point U27 carries control and bearer information with CMIP between the HA and the AGW and supports handoff between AGWs. + +#### **8.117 Reference Point U28** + +Reference Point U28 carries control and bearer (optional) information between the AGWs and supports fast inter-AGW handoff. + +#### **8.118 Reference Point U29** + +Reference Point U29 carries control and bearer information between the HA and the PDSN. The U29 reference point carries CMIP and PMIP for the split AGW architectures. The U29 reference point carries CMIP for the single AGW architecture. + +#### **8.119 Reference Point U30** + +Reference Point U30 carries IP traffic between the AGW and the IP Services network. + +#### **8.120 Reference Point U31** + +Reference Point U31 carries IP traffic between the HA and the IP Services network. + +#### **8.121 Reference Point U32** + +Reference Point U32 carries IP traffic between the LMA and the IP Services network. + +#### **8.122 Reference Point UMB-AI** + +Reference Point MB-AI (Air Interface) carries control and bearer information between the AT and the eBS. + +### **9 Technical specifications structure** + +This section provides an overview of the specifications for this IMT-2000 Family member based on ANSI-41 evolved Core Network with cdma2000 Access Network. Details for these specifications may be found in section 10. + +The following text describes the numbering scheme for the specifications and reports for the 3GPP2 3rd Generation Mobile System. + +The 3GPP2 document-numbering scheme is indicated as follows: + +A.Bcccc-w-x version y.z + +where: + +- 1) A denotes the TSG (A, C, N, P, S) which developed the specification where: + - TSG-A develops RAN (i.e., A-interface) specifications + - TSG-C develops air interface specifications + - TSG-N develops intersystem interface specifications + - TSG-P develops packet data specifications + - TSG-S develops service and system aspects specifications including stage 1 requirements descriptions and OAM&P specifications +- 2) B denotes project, report, specification (P, R, S). +- 3) cccc denotes a four (4) digit number which identifies the specific specification +- 4) w denotes revision + - 0 is the first release (0th revision), + - A is the first revision, + - and so on +- 5) x denotes whether this is the prime revision or an addendum + - 0 is the prime revision, and is used when the document is first created + - 1 is the first addendum + - 2 is the second addendum + - and so on +- 6) y is the "point release" indicator – 0 is used when the document is first created; the number is incremented whenever approved for publishing by the plenary of a TSG (e.g., 1 is the first approval by the plenary for publishing). +- 7) z is an internal edit level. The internal edit level z, is always reset to 0 when the document is approved by the applicable plenary. It is incremented by the entity (e.g., working group) that is developing the document for each new edit release. + +NOTE 1 – If the designator w and the designator x are both equal to 0, then neither designator needs to be included. + +NOTE 2 – The document reference section does not need to include "version y.z" unless specifically needed to resolve a technical incompatibility that would exist. + +## 10 Technical Specifications + +All dates in the tables of clause 10 are formatted day-month-year. If no day is shown for the document, then the format is -month-year.1 + +### 10.1 A Series RAN Specifications + +The 3GPP2 A Series RAN specifications are outside of the scope of this Recommendation. The radio access network to core network interface specifications for the cdma2000 (ANSI-41 evolved core network with cdma2000 access network) system family will be referenced in a new issue of ITU-R M.1457. + +--- + +1 Note on nomenclature of TTA documents: before TTA was accredited, documents were created under EIA. After TTA was accredited as a standards development organization, documents were named beginning with TTA/EIA. TTA documents can now stand by themselves, so since 2000, documents are now titled TTA only. The IS was an interim standard valid for 3 years and that naming system is no longer used for new documents. + +### **10.1.1 A.S0020-0 Version 1.0 Interoperability Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces (November 2007)** + +This document provides an interoperability specification for a RAN that supports UMB. This document contains message procedures and formats necessary to obtain this interoperability. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1134 | | Published | --08-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-A.S0020-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-A.S0020-0v1.0.pdf | + +### **10.1.2 A.S0020-0 Version 2.0 Interoperability specification (IOS) for ultra mobile broadband (UMB) radio access network interfaces (July 2008)** + +This document provides an interoperability specification for a RAN that supports UMB. This document contains message procedures and formats necessary to obtain this interoperability. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1134-1 | | Published | --01-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-A.S0020-0v2.0 | 2.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-A.S0020-0v2.0.pdf | + +### **10.1.3 A.S0021-0 Version 1.0 Inter-Technology Handoff for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces (July 2008)** + +This document provides an interoperability specification between a RAN that supports UMB, the AT and other access technologies. This document contains message procedures and formats necessary to obtain this interoperability. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1135 | | Published | --01-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-A.S0021-0v1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-A.S0021-0v1.0.pdf | + +## **10.2 Intersystem Specifications** + +### **10.2.1 N.S0003-0 v.1.0 User Identity Module (April 2001)** + +This standard defines the enhancements required for the support of mobile stations equipped with User Identification Modules (UIM). The UIM provides functionality to certain types of mobile stations to enable them to operate in the wireless network. + +This document defines requirements for the wireless network to support operation of UIM equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of mobile stations operating in the TIA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations. + +The UIM can be in one of two forms, as either integrated within the mobile or removable that can be inserted or removed from the mobile equipment. This document addresses Removable UIM (R-UIM) only. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0003-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-808 | | Published | --12-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0003 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0003.zip | +| TTC | TS-3GB-N.S0003v1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0003-v10.pdf | + +### 10.2.2 N.S0004-0 v 1.0 WIN Phase 2 (April 2001) + +- Triggers for Preferred Language +- Advice of Charge – Rejection of Undesired Annoying Calls +- Premium Rate Charging +- Freephone + +Premium Rate Charging (PRC), Freephone (FPH) and Advice of Charging (AOC) are charging related services that provide a set of advanced wireless charging capabilities. Rejection of Undesired Annoying Calls (RUAC) is a screening service that blocks undesired annoying calls to the subscriber. Enhanced Preferred Language (EPL) uses Wireless Intelligent Network (WIN) capabilities to provide announcements to the subscriber in the subscriber's preferred language. This specification presents a recommended plan for the implementation of WIN capabilities that support these features. The WIN capabilities are for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0004-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-848 | | Published | --12-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0004 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0004.zip | +| TTC | TS-3GB-N.S0004-0V1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0004-0v10.pdf | + +### 10.2.3 N.S0005-0 Version 1.0 Cellular Radiotelecommunications Intersystem Operations (no date) + +(O) The purpose of this document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | YDT 1031-1999 | 1.0 | Published | -12-1999 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-41-D | | Published | --12-1997 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0005 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0005.zip | + +### 10.2.4 N.S0006 Version 1.0.0 PCS Multi-band Based on IS-41-C Revision: 0 (28 January 2000) + +3GPP2 document was withdrawn. + +### 10.2.5 N.S0008 Version 1.0 Circuit Mode Services (no date) + +This Standard presents a recommended plan for the implementation of Uniform Features for use in the Cellular Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +Services: + +- Asynchronous Data Service (ADS) +- Data Privacy (DP) +- Group 3 Facsimile Service (G3 Fax) +- Service Negotiation (SN) +- Mobile Termination Functions + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0008 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-737 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0008 V1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0008v1.0.pdf | +| TTC | JP-3GB-N.S0008 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0008.pdf | + +### 10.2.6 N.S0009-0 Version 1.0 IMSI ( no date) + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-751 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0009 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0009.zip | +| TTC | JP-3GB-N.S0009 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0009.pdf | + +### 10.2.7 N.S0010-0 Version 1.0 Advanced features in Wideband Spread Spectrum Systems (no date) + +For this revision of this Standard, the advanced CDMA features include: Network Directed System Selection (NDSS) and Subscriber Confidentiality (SC) supported by TMSI. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0010-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-735 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0010 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0010-0v1.0.pdf | +| TTC | JP-3GB-N.S0010-0 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0010.pdf | + +### 10.2.8 N.S0011-0 Version 1.0 OTASP and OTAPA (no date) + +This document presents recommendations for supporting the Over-The-Air "Service Provisioning" (OTASP) and "Parameter Administration" (OTAPA) capability. + +Specifically, this document includes stage-1 recommendations for OTASP Subscriber Feature and OTAPA Network Feature Descriptions. It also provides intersystem operation recommendations for supporting the OTASP & OTAPA capability for the CDMA and TDMA air interfaces, with stage-2 operations and scenarios, stage-3 operations and parameter definitions plus stage-3 procedures. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0011-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-725-A | | Published | --07-1999 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0011 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0011.zip | +| TTC | JP-3GB.N.S0011 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0011.pdf | + +### 10.2.9 N.S0012-0 CNAP/CNAR Revision: 0 (28 January 2000) + +This document presents a recommended plan for the implementation of Calling Name Presentation (CNAP) and Calling Name Restriction (CNAR) for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0012-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-764 | | Published | --01-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0012 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0012.zip | +| TTC | JP-3GB-N.S0012 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0012.pdf | + +### 10.2.10 N.S0013-0 Version 1.0 WIN Phase 1 (no date) + +The Wireless Intelligent Network (WIN) is a network which supports the use of intelligent network capabilities to provide seamless terminal services, personal mobility services and advanced network services in mobile environment. + +This document presents a recommended plan for the implementation of the Wireless Intelligent Network (WIN) for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------|---------|------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0013-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-771
TIA/EIA/IS-771-1 | | Published
Published | --07-1999
--08-2001 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0013 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0013.zip | +| TTC | JP-3GB-N.S0013 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0013.pdf | + +### 10.2.11 N.S0014-0 Version 1.0 Authentication Enhancements (no date) + +This Standard presents a recommended plan for the implementation of authentication enhancements for use in the Wireless Radiotelephone Service. Its intent is to describe the authentication enhancements so that the manner in which a system implements them may remain reasonably consistent from system to system. + +The authentication enhancements include: + +- Count Update after Handoff +- Obtaining subscriber profile before authentication on initial system access +- Handling of suspicious call originations +- Identify the Serving MSC when reporting the outcome of a requested authentication operation +- Handling of authentication capable mobile stations when the home system is not authentication capable +- Clarification and editorial correction of authentication procedures +- Miscellaneous authentication enhancements + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0014-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-778 | | Published | --03-1999 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0014 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0014.zip | +| TTC | JP-3GB-N.S0014 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0014.pdf | + +### 10.2.12 N.S0015 Version 1.0.0 ANSI-41-D Miscellaneous Enhancements (28 January 2000) + +This document is intended to justify *TIA/EIA-41-D* technical enhancement or technical correction contributions that have been supported for incorporation into PN-3590 (*TIA/EIA-41-E*) but are not expected to be published in a *TIA/EIA-41-D* enhancement Interim Standard (IS). + +This document is for tracking purposes only, there is no intention of publishing the contents of this document independent of ANSI/TIA/EIA-41-E. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-N.S0015 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0015v1.0.0.pdf | +| TTC | TR-3GB-N.S0015-0v1.0 | 1.0.0 | Published | 26-02-2002 | http://www.ttc.or.jp/j/document_list/free/TR/TR-3GB-N.S0015-0v1.0.pdf | + +### 10.2.13 N.S0016-0 Version 1.0 TIA/EIA-41-D Internationalization (no date) + +This document specifies the ANSI/TIA/EIA-41-D Chapters 1, 3, 5 and 6 enhancements that are necessary to support international intersystem operations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------|---------|------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0016-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-807
TIA/EIA/IS-807-1 | | Published
Published | --08-1999
--03-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0016 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0016.zip | +| TTC | JP-3GB-N.S0016 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0016.pdf | + +### 10.2.14 N.S0017-B Version 1.0.0 International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41 Revision: B (December 2002) + +When the first edition of Mobile Station – Land Station Compatibility Specification (*IS-3*, now *TIA/EIA-553-A*) was issued, it was envisioned that it would be adopted for use within Northern America. Provisions were included for international implementation; however, detailed guidelines to assist with such implementations were not included. Subcommittee TR-45.2 recognized the need to provide such guidance, and charted a Working Group (Working Group VI) with this responsibility. The result of this Working Group's deliberations has been the production of TSB-29 as well as on-going internationalization of other TIA standards, such as *TIA/EIA-41-D (N.S0005)*, *TIA-751 (N.S0009)*, *TIA/EIA/IS-807 (N.S0016)*, *TIA/EIA/IS-875 (N.S0027)*, *TIA/EIA-124 (N.S0026)*, *TIA/EIA-136*, *IS-95*, *IS-91* and *TIA/EIA-2000 (C.S0001)*. TSG-N has taken TSB-29 and produced the specification N.S0017. + +The principle aspects of international implementation addressed by this document are: + +- The administration and assignment of System Identification Numbers (SIDs). +- The administration and assignment of Mobile Identification Numbers (MINs). +- Format of International Mobile Subscriber Identifiers (IMSIs). + +The goal of this publication is to provide the international wireless telecommunications industry with the framework permitting the coordinated implementation of Wireless Radio Telecommunication Systems in compliance with the provisions of the AMPS family of air interface standards (e.g., *TIA/EIA-553*, *IS-54*, *IS-91*, *IS-95*, *TIA/EIA-2000* and *TIA/EIA-136*). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0017-0 | 1.0.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TSB-29E | | Published | --12-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-N.S0017-B_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-N.S0017-B_v1.0.zip | +| TTC | TS-3GB-N.S0017-Bv1.0 | 1.0 | Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsns0017-Bv10.pdf | + +### 10.2.15 N.S0018 Version 1.0.0 TIA/EIA-41-D Prepaid Charging (14 July 2000) + +Pre-Paid Charging (PPC) allows the subscriber to pay for voice telecommunication services prior to usage. This document presents a recommended plan for the implementation of Wireless Intelligent Network (WIN) capabilities that support PPC. The WIN capabilities that support PPC are for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-826 | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0018 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0018.zip | +| TTC | JP-3GB-N.S0018 | 2 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0018.pdf | + +#### **10.2.16 N.S0019 Version 1.0.0 Intersystem Link Protocol Revision: 0 (28 January 2000)** + +This document specifies an Intersystem Link Protocol (ISLP) for circuit-mode data services. These data services include Asynchronous Data (ADS) and Group-3 Fax as specified in IS-99 and IS-135. The ISLP adapts between air-interface data rates and higher-speed intersystem rates. The ISLP may be used between a serving system and an anchor system, possibly through one or more tandem systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-728 | | Published | --01-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0019 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0019.zip | +| TTC | JP-3GB-N.S0019 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0019.pdf | + +#### **10.2.17 N.S0020 TIA/EIA-41-D Message Segmentation (August 1999)** + +3GPP2 document was withdrawn. + +#### **10.2.18 N.S0021 Version 1.0.0 User Selective Call Forwarding Revision: 1 (14 July 2000)** + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (SCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0021 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-838 | | Published | --07-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0021
v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0021v1.0.0.pdf | +| TTC | JP-3GB-N.S0021 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0021.pdf | + +#### **10.2.19 N.S0022 Version 1.0.0 Answer Hold (14 July 2000)** + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0022 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-837 | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0022 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0022v1.0.0.pdf | +| TTC | JP-3GB-N.S0022 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0022.pdf | + +### 10.2.20 N.S0023-0 Version 1.0 Automatic Code Gapping (no date) + +This document presents a recommended plan for the implementation of Automatic Code Gapping (ACG) for use in the Wireless Radiotelephone Service. ACG is used to reduce the rate at which a network entity, typically an MSC, sends service request messages to a service control function (SCF) network entity. ACG controls can be applied automatically by the SCF when it is in overload. ACG controls can also be applied by an SCF for purposes of SCF service management. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0023-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-786 | | Published | --11-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0023-0 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0023-0v1.0.pdf | +| TTC | JP-3GB-N.S0023 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0023.pdf | + +### 10.2.21 N.S0024-0 Version 1.0 Network support for MDN-Based Message Centres (November 2000) + +This document is intended to identify *TIA/EIA-41-D* WNP-PH3 (Wireless Number Portability – Phase III) technical enhancements required to support SMS (Short Message Service) delivery to MDN (Mobile Directory Number) based MCs (Message Centres). These enhancements have been supported for incorporation into PN-3590 (*TIA/EIA-41-E*) and are being published as a *TIA/EIA-41-D* enhancement Interim Standard (IS). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0024-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-841 | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0024-0 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0024-0v1.0.pdf | +| TTC | TS-3GB-N.S0024v1.0 | 1.0 | Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0024-v10.pdf | + +### 10.2.22 N.S0025 Version 1.0.0 Roamer Database Verification (January 2001) + +This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0025 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-N.S0025 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0025v1.0.0.pdf | +| TTC | TS-3GB-N.S0025v1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0025-v10.pdf | + +#### 10.2.22.1 N.S0025-A Version 1.0.0 Roamer Database Verification Revision: A (June 2002) + +This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. + +Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities. + +RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system. + +RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in *IS-41-C* or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0025-A | 1.0.0 | Published | -09-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TIA | TIA/EIA/IS-847-A | | Published | --07-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-N.S0025-A v1.0.0 | 1.0.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0025-A v1.0.0.zip | + +#### 10.2.22.2 N.S0025-B Version 1.0.0 Roamer Database Verification Revision: B (October 2002) + +3GPP2 document was superseded by X.S0021-B v1.0 + +This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. + +Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities. + +RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in *IS-41-C* or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system as well as other message routing database related problems. + +This document describes the RDV network capability and the intersystem operations to enable a wireless system to use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0025-B | 1.0.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-N.S0025-B_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-N.S0025-B_v1.0.zip | + +### 10.2.23 N.S0026 Version 1.0.0 Wireless radio telecommunication intersystem non-signalling data communication DMH (August 2000) + +This standard complements the ANSI-41, cellular radiotelecommunications intersystem operations, series of standards and identifies wireless services specifically involving non-signalling data communications which require intersystem cooperation. It presents the general background against which those services are to be provided and summarizes the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +This standard describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0026 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-124-C | | Published | --09-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0026 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-N.S0026v1.0.0.pdf | + +#### 10.2.23.1 N.S0026-A Version 1.0.0 Wireless Radio Telecommunication Intersystem Non-Signalling Data Communication DMH Revision A (December 2001) + +This standard is complementary to the *ANSI-41, Cellular Radiotelecommunications Intersystem Operations*, series of standards and identifies wireless services specifically involving non-signalling data communications which require intersystem cooperation, presents the general background against which those services are to be provided and summarizes the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +This standard describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0026-A | 1.0.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA/EIA-124-D | | Published | --12-2001 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-N.S0026-A_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-N.S0026-A_v1.0.zip | + +#### **10.2.24 N.S0027 Version 1.0.0 Enhanced International Dialling, Calling Number Identification & Callback, Calling Party Category Identification (April 2001)** + +This document presents a recommended plan for the implementation of enhanced international dialling, calling number identification and callback, and calling party category identification for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0027 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-875 | | Published | --05-2001 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-N.S0027 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0027v1.0.0.pdf | +| TTC | TS-3GB-N.S0027v1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0027-v10.pdf | + +#### **10.2.25 N.S0028 Version 1.0.0 Network Interworking Between GSM MAP and ANSI-41 MAP Rev. B Revision: 0 (April 2002)** + +3GPP2 document was superseded by X.S0023-B v1.0. + +#### **10.2.26 N.S0029 Version 1.0.0 TIA/EIA-41 Based Network Enhancements for CDMA Packet Data Service (C-PDS), Phase 1 Revision: 0 (June 2002)** + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with Packet Data Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0029 | 1.0.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TIA | TIA/EIA-IS-880 | | Published | --07-2002 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-N.S0029-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0029-0 v1.0.zip | +| TTC | TS-3GB-N.S0029-0v1.0 | 1.0 | Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsns0029-0v10.pdf | + +#### **10.2.27 N.S0030 Version 1.0.0 Enhanced Wireless 9-1-1 Phase 2 Revision: 0 (April 2002)** + +3GPP2 document was withdrawn. + +### **10.3 Packet Data Specifications** + +#### **10.3.1 P.S0001-A Version 3.0.0 Wireless IP Network Standard (16 July 2001)** + +This standard defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification is based on P.R0001; cdma2000 Wireless IP Network Architecture based on IETF protocols. + +This standard defines the two methods for accessing Public networks (Internet) and Private networks (Intranets): Simple IP and Mobile IP, and the required Quality of Service and Accounting support. IETF protocols are widely employed whenever possible to minimize the number of new protocols required and to maximize the utilization of well accepted standards and hence the speed to market. Reference to the required IETF protocols is provided in section 3 of this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-P.S0001-A | 3.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-835-A | | Published | --05-2001 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-P.S0001-A v3.0.0 | 3.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-P.S0001-Av3.0.0.pdf | +| TTC | TS-3GB-P.S0001-Av3.0 | 3.0 | Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsps0001-A-v30.pdf | + +### 10.3.2 P.S0001-B Version 1.0.0 Wireless IP Network Standard (25 October 2002) + +3GPP2 document superseded by X.S0011-C. + +### 10.3.3 P.S0001-B Version 2.0 cdma2000 Wireless IP Network Standard ( September 2004) + +3GPP2 document superseded by X.S0011-C. + +## 10.4 Services and system aspects specifications + +### 10.4.1 S.R0003 Version 1.0.0 3GPP2 System Capability Guide Release A (20 January 2000) + +3GPP2 document is re-numbered as SC.R2001-001 v1.0 + +#### 10.4.1.1 S.R0003-A Version 1.0 3GPP2 System Capability Guide Release B (14 June 2001) + +This document is re-numbered as SC.R2002-001 v1.0 + +### 10.4.2 S.R0004 Version 1.0.0 Service Implementation Guide Revision: 0 (20 January 2000) + +This Service Implementation document describes and defines features adopted by 3GPP2 TSG-S. The features descriptions may include both stage 1 and stage 2 functional levels. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0004 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0004v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0004v1.0.0.pdf | +| TTC | JP-3GB-S.R0004 | 1.0.0 | Published | 31-03-2000 | http://www.ttc.or.jp/j/document_list/pdf/j/STD/JP-3GB-S.R0004v1.pdf | + +### 10.4.3 S.R0005-B Version 1.0 Network Reference Model for cdma2000 Spread Spectrum Systems Revision: B (16 April 2001) + +This document recommends the basic 3GPP2 Wireless Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0005-B | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TSB100-A | | Published | --03-2001 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-S.R0005-B | 1 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0005-B.zip | +| TTC | TS-3GB-S.R0005-Bv1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsrr0005-B-v10.pdf | + +#### 10.4.3.1 S.R0005-B Version 2.0 Network Reference Model for cdma2000 Spread Spectrum Systems Revision: B (May 2007) + +This document recommends the basic 3GPP2 Wireless Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0005-B v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TSB-100-A-2 | 2.0 | Published | --02-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0005-B v2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0005-B v2.0.zip | +| TTC | TS-3GB-S.R0005-Bv2.0 | 2.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0005-Bv2.0.pdf | + +#### 10.4.4 S.R0006 Version 1.0.0 Wireless Features Description Revision: 0 (13 December 1999) + +This Standard presents a recommended plan for the implementation of Uniform Features for use in the Wireless Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonable consistent from system to system. It is no intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0006 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-664-A | | Published | --12-2000 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-S.R0006 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTA_E.3G-S.R0006v1.0.0.pdf | +| TTC | JP-3GB-S.R.0006 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0006.pdf | + +##### 10.4.4.1 S.R0006-000-A Version 1.0 Wireless Features Description (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-000-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-B-3[E] | 3 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-000-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0006-000-A v1.0.zip | +| TTC | TS-3GB-S.R0006-000-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-000-Av1.0.pdf | + +##### 10.4.4.2 S.R0006-000-A Version 2.0 Wireless Features Description (July 2008) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-000-A v2.0 | 2.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=/ITU-T/Q.1742/Q.1742.8 | + +#### 10.4.4.3 S.R0006-100-A Version 1.0 Wireless Features Description: General Background and Assumptions (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-100-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.100-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-100-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-100-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-100-A v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-100-Av1.0.pdf | + +#### 10.4.4.4 S.R0006-501-A Version 1.0 Wireless Features Description: Call Delivery (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-501-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.501-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-501-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-501-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-501-A v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-501-Av1.0.pdf | + +#### 10.4.4.5 S.R0006-502-A Version 1.0 Wireless Features Description: Call Forwarding-Busy (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-502-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664.502-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-502-A v1.0 | 1.0 | Approved | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-502-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-502-A v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-502-Av1.0.pdf | + +#### 10.4.4.6 S.R0006-503-A Version 1.0 Wireless Features Description: Call Forwarding-Default (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-503-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-503-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-503-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-503-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-503-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-503-Av1.0.pdf | + +#### 10.4.4.7 S.R0006-504-A Version 1.0 Wireless Features Description: Call Forwarding-No Answer (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-504-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-504-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-504-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-504-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-504-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-504-Av1.0.pdf | + +#### 10.4.4.8 S.R0006-505-A Version 1.0 Wireless Features Description: Call Forwarding-Unconditional (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-505-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-505-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-505-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-505-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-505-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-505-Av1.0.pdf | + +#### 10.4.4.9 S.R0006-506-A Version 1.0 Wireless Features Description: Call Transfer (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-506-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-506-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-506-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-506-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-506-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-506-Av1.0.pdf | + +#### 10.4.4.10 S.R0006-507-A Version 1.0 Wireless Features Description: Call Waiting (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-507-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-507-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-507-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-507-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-507-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-507-Av1.0.pdf | + +#### 10.4.4.11 S.R0006-508-A Version 1.0 Wireless Features Description: Calling Number Identification Presentation (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-508-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-508-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-508-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-508-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-508-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-508-Av1.0.pdf | + +#### 10.4.4.12 S.R0006-509-A Version 1.0 Wireless Features Description: Calling Number Identification Restriction (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-509-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-509-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-509-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-509-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-509-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-509-Av1.0.pdf | + +#### 10.4.4.13 S.R0006-510-A Version 1.0 Wireless Features Description: Conference Calling (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-510-A v1. | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-510-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-510-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-510-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-510-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-510-Av1.0.pdf | + +#### 10.4.4.14 S.R0006-511-A Version 1.0 Wireless Features Description: Do Not Disturb (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-511-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-511-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-511-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-511-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-511-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-511-Av1.0.pdf | + +#### 10.4.4.15 S.R0006-512-A Version 1.0 Wireless Features Description: Flexible Alerting (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-512-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-512-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-512-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-512-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-512-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-512-Av1.0.pdf | + +#### 10.4.4.16 S.R0006-513-A Version 1.0 Wireless Features Description: Message Waiting Notification (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-513-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-513-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-513-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-513-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-513-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-513-Av1.0.pdf | + +#### 10.4.4.17 S.R0006-514-A Version 1.0 Wireless Features Description: Mobile Access Hunting (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-514-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-514-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-514-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-514-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-514-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-514-Av1.0.pdf | + +#### **10.4.4.18 S.R0006-515-A Version 1.0 Wireless Features Description: Password Call Acceptance (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-515-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-515-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-515-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.R0006-515-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-515-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-515-Av1.0 | + +#### **10.4.4.19 S.R0006-516-A Version 1.0 Wireless Features Description: Preferred Language (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-516-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-516-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-516-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.R0006-516-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-516-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-516-Av1.0.pdf | + +#### **10.4.4.20 S.R0006-517-A Version 1.0 Wireless Features Description: Priority Access and channel Assignment (June 2007)** + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-517-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-517-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-517-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.R0006-517-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-517-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-517-Av1.0.pdf | + +#### 10.4.4.21 S.R0006-518-A Version 1.0 Wireless Features Description: Remote Feature Control (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-518-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-518-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-518-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-518-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-518-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-518-Av1.0.pdf | + +#### 10.4.4.22 S.R0006-519-A Version 1.0 Wireless Features Description: Selective Call Acceptance (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-519-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-519-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-519-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-519-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-519-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-519-Av1.0.pdf | + +#### 10.4.4.23 S.R0006-520-A Version 1.0 Wireless Features Description: Subscriber PIN Access (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-520-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-520-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-520-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-520-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-520-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-520-Av1.0.pdf | + +#### 10.4.4.24 S.R0006-521-A Version 1.0 Wireless Features Description: Subscriber PIN Intercept (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-521-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-521-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-521-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-521-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-521-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-521-Av1.0.pdf | + +#### 10.4.4.25 S.R0006-522-A Version 1.0 Wireless Features Description: Three Way Calling (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-522-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-522-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-522-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-522-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-522-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-522-Av1.0.pdf | + +#### 10.4.4.26 S.R0006-523-A Version 1.0 Wireless Features Description: Voice Message Retrieval (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-523-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-523-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-523-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-523-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-523-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-523-Av1.0.pdf | + +#### 10.4.4.27 S.R0006-524-A Version 1.0 Wireless Features Description: Voice Privacy (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-524-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-524-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-524-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-524_A_v1.0.zip | +| TTC | TS-3GB-S.R0006-524-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-524-Av1.0.pdf | + +#### 10.4.4.28 S.R0006-525-A Version 1.0 Wireless Features Description: Asynchronous Data Service (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-525-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-525-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-525-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-525_A_v1.0.zip | +| TTC | TS-3GB-S.R0006-525-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-525-Av1.0.pdf | + +#### 10.4.4.29 S.R0006-526-A Version 1.0 Wireless Features Description: Calling Name Presentation (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-526-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-526-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-526-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-526_A_v1.0.zip | +| TTC | TS-3GB-S.R0006-526-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-526-Av1.0.pdf | + +#### 10.4.4.30 S.R0006-527-A Version 1.0 Wireless Features Description: Calling Name Restriction (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-527-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-527-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-527-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-527-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-527-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-527-Av1.0.pdf | + +#### 10.4.4.31 S.R0006-528-A Version 1.0 Wireless Features Description: Data Privacy (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-528-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-528-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-528-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-528-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-528-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-528-Av1.0.pdf | + +#### 10.4.4.32 S.R0006-529-A Version 1.0 Wireless Features Description: Emergency Services (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-529-A v1. | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-529-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-529-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-529-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-529-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-529-Av1.0.pdf | + +#### 10.4.4.33 S.R0006-530-A Version 1.0 Wireless Features Description: Group 3 Facsimile Service (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-530-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-530-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-530-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-530-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-530-A v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-530-Av1.0.pdf | + +#### 10.4.4.34 S.R0006-531-A Version 1.0 Wireless Features Description: Network Directed System Selection (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-531-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-531-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-531-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-531-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-531-A v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-531-Av1.0.pdf | + +#### 10.4.4.35 S.R0006-532-A Version 1.0 Wireless Features Description: Non-Public Service Mode (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-532-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-532-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-532-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-532-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-532-A v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-532-Av1.0.pdf | + +#### 10.4.4.36 S.R0006-533-A Version 1.0 Wireless Features Description: Over-the-Air Service Provisioning (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-533-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-533-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-533-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-533-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-533-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-533-Av1.0.pdf | + +#### 10.4.4.37 S.R0006-534-A Version 1.0 Wireless Features Description: Service Negotiation (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-534-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-534-A | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-534-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-534-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-534-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-534-Av1.0.pdf | + +#### 10.4.4.38 S.R0006-535-A Version 1.0 Wireless Features Description: User Group (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-535-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-535-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-535-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-535-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-535-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-535-Av1.0.pdf | + +#### 10.4.4.39 S.R0006-536-A Version 1.0 Wireless Features Description: Group 3 Analogue Fax (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-536-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-536-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-536-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-536-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-536-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-536-Av1.0.pdf | + +#### 10.4.4.40 S.R0006-537-A Version 1.0 Wireless Intelligent Network Feature Descriptions (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-537-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-537-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-537-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-537-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-537-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-537-Av1.0.pdf | + +#### 10.4.4.41 S.R0006-601-A Version 1.0 Wireless Features Description: Short Message Deliver-Point-to-Point Bearer Service (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-601-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-601-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-601-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-601-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-601-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-601-Av1.0.pdf | + +#### 10.4.4.42 S.R0006-602-A Version 1.0 Wireless Features Description: Wireless Messaging Teleservice (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-602-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-602-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-602-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-602-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-602-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-602-Av1.0.pdf | + +#### 10.4.4.43 S.R0006-603-A Version 1.0 Wireless Features Description: Wireless Paging Teleservice (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-603-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-603-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-603-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-603-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-603-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-603-Av1.0.pdf | + +#### 10.4.4.44 S.R0006-701-A Version 1.0 Wireless Features Description: Mobile Station Functionality (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-701-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-701-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-701-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-701-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-701-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-701-Av1.0.pdf | + +#### 10.4.4.45 S.R0006-801-A Version 1.0 Wireless Features Description: System Functionality (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-801-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-801-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-801-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-801-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-801-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-801-Av1.0.pdf | + +#### 10.4.4.46 S.R0006-802-A Version 1.0 Wireless Features Description: Subscriber Confidentiality (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-802-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-802-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-802-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-802-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-802-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-802-Av1.0.pdf | + +#### 10.4.4.47 S.R0006-803-A Version 1.0 Wireless Features Description: Network Services (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-803-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-803-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-803-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-803-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-803-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-803-Av1.0.pdf | + +#### 10.4.4.48 S.R0006-804-A Version 1.0 Wireless Features Description: Enhanced Security Services (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-804-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-804-A | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-804-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-804-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-804-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-804-Av1.0.pdf | + +#### 10.4.4.49 S.R0006-805-A Version 1.0 Wireless Features Description: CDMA Packet Data Service (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-805-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-805-B | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-805-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-805-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-805-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-805-Av1.0.pdf | + +#### 10.4.4.50 S.R0006-806-A Version 1.0 Wireless Features Description: Over-the-Air Parameter Administration (June 2007) + +This specification presents a recommended plan for the implementation of uniform features for use in wireless telecommunications systems. Its intent is to describe services and features so that the manner in which they are used by a subscriber can remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-806-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-664-806 | 0 | Published | --11-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0006-806-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0006-806-A_v1.0.zip | +| TTC | TS-3GB-S.R0006-806-Av1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0006-806-Av1.0.pdf | + +#### 10.4.4.51 S.R0006-807-A Version 1.0 Wireless Features Description: Generic Broadcast Teleservice Transport Capability: Network Perspective (July 2008) + +The Broadcast Teleservice Transport Capability (BTTC) provides a method to deliver and manage broadcast SMS messages and other compatible teleservice messages. In addition to the Bearer Data and Teleservice Identifier attributes, support is provided within *MAP* SMS signalling protocols and procedures to specify the broadcast scope and method related to a specific teleservice message to be broadcast. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-807-A 1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0006-807-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0006-807-Av1.0 | +| TTC | TS-3GB-S.R0006-807-Av1.0 | 1.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-807-Av1.0.pdf | + +#### 10.4.4.52 S.R0006-808-A Version 1.0 Wireless Features Description: Circuit Switched Call Precedence Over CDMA Packet Data Session (July 2008) + +Circuit Switched Call Precedence Over CDMA Packet Data Session (CPOP) enables circuit-switched calls to be delivered to a subscriber engaged in an active CDMA packet data session. The packet data session is suspended (i.e., dormant) for the duration of the circuit-switched call. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0006-808-A 1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0006-808-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0006-808-Av1.0 | +| TTC | TS-3GB-S.R0006-808-Av1.0 | 1.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0006-808-Av1.0.pdf | + +#### 10.4.5 S.R0007 Version 1.0.0 User Selective Call Forwarding (Stage 1) Revision: 0 (13 December 1999) + +This Interim Standard (IS) presents stage-1 (new chapter *TIA/EIA-664-B*), stage-2 (*TIA/EIA-41.3-D* enhancements), and stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the User Selective Call Forwarding (USCF) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0007 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0007 v.1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0007_v1.0.zip | + +#### 10.4.5.1 S.R0007 Version 2.1 User Selective Call Forwarding (Stage 1) (31 January 2001) + +This Interim Standard (IS) presents stage-1 (new chapter *TIA/EIA-664-B*), stage-2 (*TIA/EIA-41.3-D* enhancements), and stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the User Selective Call Forwarding (USCF) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0007 v2.1 | 2.1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0007 v.2.1 | 2.1 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0007_v2.1.zip | +| TTC | TS-3GB-S.R0007v2.1 | 2.1 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0007-v21.pdf | + +#### 10.4.6 S.R0008-0 Version 1.0.0 Answer Hold (Stage 1) Revision: 0 (13 December 1999) + +This Interim Standard (IS) presents stage-1 (new chapter *TIA/EIA-664-B*), stage-2 (*TIA/EIA-41.3-D* enhancements), and stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the Answer Hold (AH) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0008 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0008 V.1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0008_v1.0.zip | + +##### 10.4.6.1 S.R0008-0 Version 2.0 Answer Hold (Stage 1) Revision: 0 (8 December 2000) + +This Interim Standard (IS) presents stage-1 (new chapter *TIA/EIA-664-B*), stage-2 (*TIA/EIA-41.3-D* enhancements), and stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the Answer Hold (AH) feature use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0008 v2.1 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0008 V.2.0 | 2.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0008_v2.0.zip | +| TTC | JP-3GB-S.R0008 | 2 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0008.pdf | + +#### 10.4.7 S.R0009-0 v1.0 User Identity Module (Stage 1) Revision: 0 (13 December 1999) + +This standard defines the enhancements required for the support of mobile stations equipped with User Identification Modules (UIM). The UIM provided functionality to certain types of mobile stations to enable them to operate in the wireless network. + +This document defines requirements for the wireless network to support operation of UIM equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of Mobile stations operating in the TIA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations. + +The UIM can be in one of two forms, as either integrated within the mobile or removable that can be inserted or removed from the mobile equipment. This document address Removable UIM (R-UIM) only. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0009 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0009.zip | +| TTC | TS-3GB-S.R0009 | 1 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0009-v10.pdf | + +#### 10.4.8 S.R0010-0 Version 1.0.0 Preferred Language (Stage 1) Revision: 0 (13 December 1999) + +Preferred Language (PL) provides the subscriber the ability to specify the language for network services. + +Network services which could be offered in the subscriber's preferred language include: + +- Recorded announcements +- Directory assistance +- Operator services +- Emergency services +- "Help" lines +- Message Waiting Notification +- CNIP *number not available* +- CNIP *number restricted* + +If the subscriber's preferred language is not available, service shall be provided in the default language, which shall be determined by the wireless network operator. + +PL does not impact a subscriber's ability to originate calls or to receive calls. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0010 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0010 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0010.zip | +| TTC | JP-3GB-S.R0010 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0010.pdf | + +#### 10.4.9 S.R0011-0 Version 1.0.0 Advice of Charge (Stage 1) Revision: 0 (13 December 1999) + +This specification presents stage-1 for supporting the Advice of Charge feature for use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Advice of Charge (AoC) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0011 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0011 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0011.zip | +| TTC | JP-3GB-S.R0011 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0011.pdf | + +#### 10.4.10 S.R0012-0 Version 1.0.0 Rejection of Undesired Annoying Calls (Stage 1) Revision: 0 (13 December 1999) + +This specification presents stage-1 for supporting Rejection of Undesired Annoying Calls feature for use in the Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Rejection of Undesired Annoying Calls (RUAC) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0012 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0012 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0012.zip | +| TTC | JP-3GB-S.R0012 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0012.pdf | + +#### **10.4.11 S.R0013-0 Version 1.0.0 Global Emergency Call Origination (GECO) Revision: 0 (13 December 1999)** + +This document presents a stage 1 description for a Global Emergency Call Origination (GECO) which will increase the probability that any user can originate a call to a Public Service Access Point (PSAP) even in those service areas where the Emergency Service Access Number (ESAN) is not known to the user. + +The intent of GECO is described as follows: + +- The MS may provide a means for the user to initiate an emergency call. +- A special form of the call origination message (defined as an Global Emergency Call Origination Message (GECO\_MSG) may be issued by the MS in lieu of the normal call origination message to indicate that the call origination being requested is an emergency call origination. GECO\_MSGs may be accepted and the GECO call connected by the network from both subscribed and unsubscribed mobiles. The system may support "implicit registration" for GECO calls such that the use of registration request/acceptance protocol is not required prior to the issuance of a GECO\_MSG. +- If the MS is currently registered on and accessing an operating network when the GECO call is initiated by the user, the MS may use that system to initiate the GECO call. If the MS is not currently accessing a system, the MS may attempt to access its preferred service as indicated by its internal system selection and system access restriction programming to maximize the probability that the GECO call will be accepted by the system. If no preferred system is available, the MS may override its internal system selection and system access restriction programming in an attempt to access any available system. +- Initiation of GECO call by the MS shall in no way degrade the user's access to any other feature/service which would normally be available to him from the accessed service provider's network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0013 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0013 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0013.zip | +| TTC | JP-3GB-S.R0013 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0013.pdf | + +#### **10.4.12 S.R0014-0 Version 1.0.0 Tandem Free Operation (Stage 1) Revision: 0 (13 December 1999)** + +It is expected that the need for Tandem Free Operations will be driven by the increasing market penetration of digital technologies which will result in an increase in percentage of calls that mobile-to-mobile calls. In addition, given that the effects of tandem vocoding are greater for lower bit rate vocoders, the need for this feature becomes greater as the use of low bit rate vocoders increases. The Tandem Free Operation (TFO) feature, also known as Vocoder Bypass, improves the end-to-end voice equality observed in mobile-to-mobile voice calls in wireless networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0014 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0014 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0014.zip | +| TTC | JP-3GB-S.R0014 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0014.pdf | + +#### **10.4.13 S.R0015-0 Version 1.0.0 ISDN Interworking (Stage 1) Release A (13 December 1999)** + +This document presents stage-1 (new chapter TTA/EIA-664-B) recommendations for supporting the ISDN Interworking feature use in Wireless Radiotelephone Service. + +This document specifies the wireless intersystem network operation enhancements required for supporting subscribers with the ISDN Interworking feature. This document defines the functional characteristics for interconnecting to ISDN in circuit switched mode. The interworking function in ISDN packet mode, i.e., B-channel Packet is out of scope at present. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0015 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0015.zip | +| TTC | JP-3GB-S.R0015 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0015.pdf | + +#### **10.4.14 S.R0016-0 Version 1.0.0 Automatic Code Gapping (Stage 1) Revision: 0 (13 December 1999)** + +Automatic Code Gapping (ACG) is intended to provide a Network Entity, such as a Service Control Point (SCP) or Service Control Function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load related or in response to a traffic engineering command as from a Service Management System (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0016 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0016 V.1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0016.zip | + +#### **10.4.14.1 S.R0016-0 Version 2.0 Automatic Code Gapping (Stage 1) Revision: 0 (8 December 2000)** + +Automatic Code Gapping (ACG) is intended to provide a Network Entity, such as a Service Control Point (SCP) or Service Control Function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load related or in response to a traffic engineering command as from a Service Management System (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0016 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0016 V.2.0 | 2.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0016_v2.0.zip | +| TTC | JP-3GB-S.R0016 | 2 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0016.pdf | + +#### **10.4.15 S.R0017-0 3G Wireless Network Management System High Level Requirements Revision: 0 (13 December 1999)** + +This report specifies the 3G Wireless Network Management System High Level Requirements Including: OAM&P TMN Applications Required Network and Systems Management Processes and Network Reference Model (NRM) + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0017 | | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0017 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0017.zip | +| TTC | TR-3GB-S.R0017-0v1.0 | 1.0 | Published | 26-02-2002 | http://www.ttc.or.jp/imt2000/tr/trsr0017-0v10.pdf | + +#### **10.4.16 S.R0018-0 Version 1.0.0 Pre-Paid Charging (Stage 1) Revision: 0 (13 December 1999)** + +PPC allows the subscriber to pay for voice telecommunication services prior to usage. + +A PPC subscriber establishes an account with the service provider to access voice telecommunications services in home and roaming networks. Charges for voice telecommunication services are applied to the PPC account by decrementing the account in real time. The PPC subscriber may be notified about the account information at the beginning, during, or at the end of the voice telecommunications service. When the account balance is low the subscriber may be notified so that the subscriber may refill the account. When the account balance is below a pre-defined threshold, the subscriber's use of voice telecommunications services may be de-authorized. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0018 | 1 | Published | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0018.zip | +| TTC | JP-3GB-S.R0018 | 1 | Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0018.pdf | + +#### **10.4.17 S.R0019-0 Version 1.0.0 Location-Based Services System (LBSS) Stage 1 Description (22 September 2000)** + +This document defines LBSS for implementation in 3GPP2 systems. The location services functionality has been adopted from existing TR-45 standards as defined and also as described in the following text. + +The scope of this document includes 3GPP2 system support required to facilitate Location-Based services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0019 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0019v1.0.0.pdf | +| TTC | JP-3GB-S.R0019 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0019.pdf | + +#### 10.4.18 S.R0021-0 Version 1.0 Video Streaming Service – Stage 1 (10 July 2000) + +The objective is to define and to standardize the functionality of Video Services that can be incorporated into the operations of wireless telecommunications networks. Audio- only streaming is a special case of video streaming. This document defines the functional characteristics and requirements of the video streaming services. The areas that must be defined are service features and system requirements, necessary for video streaming services to be provided in wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0021 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0021 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0021v1.0.pdf | +| TTC | JP-3GB-S.R0021 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0021.pdf | + +#### 10.4.18.1 S.R0021-0 Version 2.0 Multimedia Streaming Service – Stage 1 (18 April 2002) + +The objective is to define and to standardize the functionality of Multimedia Services that can be incorporated into the operations of wireless telecommunications networks. Audio- only or video only streaming are a special case of multimedia streaming. This document defines the functional characteristics and requirements of the multimedia streaming services. The areas that must be defined are service features and system requirements, necessary for multimedia streaming services to be provided in wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0021 | 2.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0021-0_v2.0 | 2.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0021-0_v2.0.zip | +| TTC | TS-3GB-S.R0021-0v2.0 | 2.0 | Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0021-0v20.pdf | + +#### 10.4.19 S.R0022-0 Version 1.0 Video Conferencing Service (10 July 2000) + +The objective is to define and to standardize the functionality of Video Services that can be incorporated into the operations of wireless telecommunications networks. This report defines the functional characteristics and the requirements of the video conferencing services. The areas that must be defined are service features and system requirements in order for voice conferencing services to be provided in wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0022 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0022 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0022v1.0.pdf | +| TTC | JP-3GB-S.R0022 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0022.pdf | + +#### 10.4.20 S.R0023-0 Version 1.0 High-Speed Data Enhancements for cdma2000 1x – Data Only (9 June 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0023 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0023 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-.R0023v1.0.pdf | + +#### 10.4.20.1 S.R0023-0 Version 2.0 High-Speed Data Enhancements for cdma2000 1x – Data Only Stage 1 Requirements (5 December 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0023 v2.0 | 2.0 | Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0023_V2.PDF | +| CCSA | CWTS-MC-S.R0023 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0023 v2.0 | 2.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S_R0023_v2.0.zip | + +#### 10.4.21 S.R0024-0 Version 1.0 Wireless Local Loop Stage 1 Description (22 September 2000) + +Wireless Local Loop (WLL) is a feature implementation using a serving system that utilizes a wireless connection to a wireless device, such as a mobile station or a network interface unit to provide local loop service to an end user. WLL permits local loop service for subscriber call origination and for receipt of calls. WLL applies to voice and data services. WLL provides signalling mechanisms between the serving system and the mobile station or the network interface unit. This signalling mechanism permits the exchange of call control information. + +The essential signalling elements of WLL are: + +- Mobile station or Network interface unit Device Type specification and request for WLL of the serving system or optional serving system Device Type specification. +- Mobile Station or Network interface unit Dial Tone or optional Dial Tone of the serving system. +- Mobile Station or Network interface unit Hook Status enabling WLL call control of the serving system. + +- Serving system Autonomous Message Interval specification and request of the mobile station or the network interface unit or optional network interface unit Autonomous Message Interval specification. +- Serving system Call Waiting Indicator notification to the mobile station or the network interface unit. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0024 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0024 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0024v1.0.pdf | + +#### 10.4.22 S.R0025-0 Version 1.0 Wireless Pay Phone Stage 1 Description (22 September 2000) + +Wireless Pay Phone is a public telecommunications service feature that allows mobile station support of pay phone applications. The Wireless Pay Phone feature is useful to subscribers that originate or receive calls at a pay phone. + +The feature may be comprised of two signalling capabilities. The first signalling capability is that which allows a serving system to convey answer supervision. The second signalling capability is that which allows a serving system to meter calls. + +(NOTE – A serving system may convey answer supervision using Alert-signalled or Flash-signalled Line Control. A serving system may meter using Alert-signalled or Flash-signalled Meter Pulses.) + +Answer element of supervision is used by the mobile station to convey line polarity, which is useful as an answer supervision indication. Line Control specification and notification of the mobile station enables specification of Polarity Included, Toggle Mode, Reverse Polarity and Power Denial Time. These are specified in IS-95B section 7.7.5.15. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0025 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0025 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0025v1.0.pdf | + +#### 10.4.23 S.R0026-0 Version 1.0 High Speed Data Enhancements for cdma2000 1 x-Integrated Data and Voice Stage 1 Requirements (17 October 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x-evolved high-speed integrated data and voice (1xEV-DV). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This document is intended as a guide for 3GPP2 TSGs in the development of specifications for high-speed integrated data and voice systems beyond cdma2000 1x services (voice, fax, circuit switched data), to provide increased spectral efficiency and the capability to satisfy customer demand for wireless voice and packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0026 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0026 | 1 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0026.zip | + +#### **10.4.24 S.R0027-0 Version 1.0 Personal Mobility Stage 1 Requirements (8 December 2000)** + +The objective is to define and standardize the functionality of personal mobility that can be incorporated into the operations of both 2G/3G TTA/EIA-41 and 2G/3G GSM-derived wireless telecommunications networks. This document defines the requirements of personal mobility features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0027 | 1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0027 | 1 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0027.zip | +| TTC | JP-3GB-S.R0027 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0027.pdf | + +#### **10.4.25 S.S0028-0 Version 1.0 OAM&P for cdma2000 (3GPP Delta Specification) (18 April 2001)** + +This document contains the OAM&P requirements and interface definitions for cdma2000-based systems. It is an extension of operations and maintenance requirements, per latest 3GPP 32-series specifications capabilities to enable operation in a cdma2000 systems environment as part of the TTA/EIA/IS-2000 family of standards. They are in alignment with OAM&P stage 1 IS-2000 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.S0028 V.1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_S0028_v1.0.zip | +| TTC | JP-3GB-S.S0028v1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-v10.pdf | + +#### **10.4.25.1 S.S0028-0 Version 2.0 OAM&P for cdma2000 (3GPP Delta Specification) (23 July 2001)** + +This document is intended to define the OAM&P stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.S0028 V.2.0 | 2.0 | Published | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_S0028_v2.0.zip | +| TTC | TS-3GB-S.S0028-0v2.0 | 2.0 | Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v20.pdf | + +#### **10.4.25.2 S.S0028-0 Version 3.0 OAM&P for cdma2000 (3GPP Delta Specification) (11 March 2002)** + +This document is intended to define the OAM&P stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 3.0 | Published | -06-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.S0028-0 v3.0 | 3.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.S0028-0 v3.0.zip | +| TTC | TS-3GB-S.S0028-0v3.0 | 3.0 | Published | 28-05-2002 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v30.pdf | + +#### 10.4.25.3 S.S0028-A Version 1.0 OAM&P for cdma2000 (3GPP R4 Delta Specification) Revision: A (12 December 2002) + +This document is intended to define the OAM&P stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 1.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0028-A_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v1.0.zip | +| TTC | TS-3GB-S.S0028-Av1.0 | 1.0 | Published | 14-02-2003 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.S0028-Av1.0.pdf | + +#### 10.4.25.4 S.S0028-A Version 2.0 OAM&P for cdma2000 (3GPP R4Delta Specification) Revision: A (20 February 2003) + +This document is intended to define the OAM&P stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 2.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0028-A_v2.0 | 2.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v2.0.zip | +| TTC | TS-3GB-S.S0028-Av2.0 | 2.0 | Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsss0028-Av20.pdf | + +#### 10.4.25.5 S.S0028-A Version 3.0 OAM&P for cdma2000 (3GPP R4Delta Specification) Revision: A (20 February 2003) + +This document is intended to define the OAM&P stage 2 and 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 3.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-A v3.0 | 3.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v3.0.zip | +| TTC | TS-3GB-S.S0028-A v3.0 | 3.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-av30.pdf | + +#### 10.4.25.6 S.S0028-000-B Version 1.0 OAM&P for cdma2000 (Overview) (17 February 2005) + +The present document is the overview component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- **S.S0028-000-B: "OAM&P for cdma2000 (Overview)"**; + +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-000-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742_5 | +| TTA | TTAT.3G-S.S0028-000-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-000-B_v1.0.zip | +| TTC | TS-3GB-S.S0028-000-Bv1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-bv10.pdf | + +#### 10.4.25.7 S.S0028-000-B Version 2.0 OAM&P for cdma2000 (Overview) ( 18 July 2005) + +The present document is the overview component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-000-B v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.S0028-000-B v2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-000-B_v2.0.zip | +| TTC | TS-3GB-S.S0028-000-Bv2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.S0028-000-Bv2.0.pdf | + +#### 10.4.25.8 S.S0028-000-C Version 1.0 OAM&P for cdma2000 (Overview) Revision: C (18 January 2006) + +The present document is the overview component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- **S.S0028-000-C: "OAM&P for cdma2000 (Overview)";** +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-000-C v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-000-C v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-000-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-000-Cv1.0 | 1.0 | Published | 02/06/06 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-cv10.pdf | + +#### 10.4.25.9 S.S0028-000-C Version 2.0 OAM&P for cdma2000 (Overview) Revision: C (October 2007) + +The present document is the overview component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- **S.S0028-000-C: "OAM&P for cdma2000 (Overview)";** +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-000-Cv2.0 | 2.0 | Published | 28-11-2007 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.S0028-000-Cv2.0.pdf | + +#### 10.4.25.10 S.S0028-001-B Version 1.0 OAM&P for cdma2000 (3GPP R5 Delta Specification) (17 February 2005) + +The present document is the 3GPP R5 Delta Specification component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";** +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-001-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-001-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.S0028-001-B_v1.0.zip | +| TTC | TS-3GB-S.S0028-001-Bv1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv10.pdf | + +#### 10.4.25.11 S.S0028-001-B Version 2.0 OAM&P for cdma2000 (3GPP R5 Delta Specification) Revision: B (18 July 2005) + +The present document is the 3GPP R5 Delta Specification component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";** +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-001-B | 2.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-001-B v2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-001-B_v2.0.zip | +| TTC | TS-3GB-S.S0028-001-B v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv20.pdf | + +#### 10.4.25.12 S.S0028-001-C Version 1.0 OAM&P for cdma2000 (3GPP R6 Delta Specification) Revision: C (18 January 2006) + +The present document is the 3GPP R6 Delta Specification component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)";** +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-001-C v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-001-C v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-001-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-001-C v1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-cv10.pdf | + +#### 10.4.25.13 S.S0028-001-C Version 2.0 OAM&P for cdma2000 (3GPP R6 Delta Specification) Revision: C (October 2007) + +The present document is the 3GPP R6 Delta Specification component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- **S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)";** +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-001-Cv2.0 | 2.0 | Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0028-001-Cv2.0.pdf | + +#### 10.4.25.14 S.S0028-002-B Version 1.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) (17 February 2005) + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; + +- **S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-002-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-002-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.S0028-002-B v1.0.zip | +| TTC | TS-3GB-S.S0028-002-Bv1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-bv10.pdf | + +#### **10.4.25.15 S.S0028-002-B Version 2.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) (18 July 2005)** + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- **S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-002-Bv2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.S0028-002-Bv2.0.pdf | + +#### **10.4.25.16 S.S0028-002-C Version 1.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) Revision: C (18 January 2006)** + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- **S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-002-C v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-002-C v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.S0028-002-C v1.0.zip | +| TTC | TS-3GB-S.S0028-002-Cv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-cv10.pdf | + +**10.4.25.17 S.S0028-002-C Version 2.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) +Revision: C (11 October 2007)** + +The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- **S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";** +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-002-Cv2.0 | 2.0 | Published | 28-11-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.S0028-002-Cv2.0.pdf | + +**10.4.25.18 S.S0028-003-B Version 1.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) +(17 February 2005)** + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-003-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-003-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.S0028-003-B_v1.0.zip | +| TTC | TS-3GB-S.S0028-003-Bv1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv10.pdf | + +**10.4.25.19 S.S0028-003-B Version 2.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) +Revision: B (18 July 2005)** + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-003-B | 2.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-003-B v2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-003-B_v2.0.zip | +| TTC | TS-3GB-S.S0028-003-B v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv20.pdf | + +#### 10.4.25.20 S.S0028-003-C Version 1.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) Revision: C (18 January 2006) + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)" + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-003-C v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-003-C v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-003-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-003-Cv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-cv10.pdf | + +#### 10.4.25.21 S.S0028-003-C Version 2.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) Revision: C (11 October 2007) + +The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- **S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";** +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)" + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-003-Cv2.0 | 2.0 | Published | 28-11-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.S0028-003-Cv2.0.pdf | + +#### 10.4.25.22 S.S0028-004-B Version 1.0 OAM&P for cdma2000 (Radio Access NRM IRP) (17 February 2005) + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; + +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-004-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-004-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.S0028-004-B v1.0.zip | +| TTC | TS-3GB-S.S0028-004-Bv1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv10.pdf | + +#### **10.4.25.23 S.S0028-004-B Version 2.0 OAM&P for cdma2000 (Radio Access NRM IRP) (17 February 2005)** + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"; +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-004-B | 2.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-004-B v2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.S0028-004-B v2.0.zip | +| TTC | TS-3GB-S.S0028-004-B v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv20.pdf | + +#### **10.4.25.24 S.S0028-004-C Version 1.0 OAM&P for cdma2000 (Radio Access NRM IRP) Revision: C (18 January 2006)** + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-004-C v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-004-C v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0028-004-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-004-Cv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-cv10.pdf | + +#### 10.4.25.25 S.S0028-004-C Version 2.0 OAM&P for cdma2000 (Radio Access NRM IRP) Revision: C (11 October 2007) + +The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- & cdma2000®1-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)"; +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)"; +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; +- **S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"** + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0028-004-Cv2.0 | 2.0 | Published | 28-11-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.S0028-004-Cv2.0.pdf | + +#### 10.4.25.26 S.S0028-D Version 1.0 OAM&P for cdma2000 (Overview, 3GPP R7 Delta Specification, 3GPP2 Network Resource Model IRP) (October 2008) + +This document defines the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- and cdma2000®1-based systems + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1156 | | Published | --04-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.S0028-Dv1.0 | 1.0 | Published | 06-03-2009 | http://www.ttc.or.jp/imt2000/ts/tsss0028-dv10.pdf | + +#### 10.4.25.27 S.S0028-E Version 1.0 OAM&P for cdma2000 (Overview, 3GPP R7 Delta Specification, 3GPP2 Network Resource Model IRP) (January 2010) + +This document defines the OAM&P stage 2 and 3 requirements and interface definitions for CDMA- and cdma2000®1-based systems + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-S.S0028-E v1.0 | 1.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1156-A | | Published | --05-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.S0028-Ev1.0 | 1.0 | Published | 27-07-2010 | http://www.ttc.or.jp/imt2000/ts/tsss0028-ev10.pdf | + +#### 10.4.26 S.R0029 Version 1.0. Access Control Based on Call Type (22 September 2000) + +This document defines requirements for the cdma2000 Air Interface to support Access Control based on Call Type (ACCT). ACCT provides the control of access attempt from mobile stations by service option or a set of service options. + +Control for terminating calls to mobile stations are outside the scope of this feature description. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0029 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0029 v1.0.0 | 1.0.0 | Published | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0029v1.0.0.pdf | +| TTC | TS-3GB-S.R0029v1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0029-v10.pdf | + +#### 10.4.27 S.R0030 Version 1.0 Broadcast/Multicast Services – Stage 1 (22 August 2001) + +The objective of this document is to define and to standardize the functionality of Broadcast/Multicast Services that can be incorporated into the operations of cdma2000 based wireless telecommunications networks. This document defines the functional characteristics and requirements of Broadcast/Multicast services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0030 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.R0030-0 v1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE.3G-S.R0030-0 v1.0.zip | +| TTC | TS-3GB-S.R0030-0v1.0 | 1.0 | Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0030-0v10.pdf | + +#### 10.4.27.1 S.R0030-A Version 1.0 Broadcast/Multicast Services – Stage 1 Revision A (15 January 2004) + +The objective of this document is to define and to standardize the functionality of Broadcast/Multicast Services that can be incorporated into the operations of cdma2000 based wireless telecommunications networks. This document defines the functional characteristics and requirements of Broadcast/Multicast services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0030-A v1.0 | 1 | Published | 15-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0030-A v1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0030-A v1.0.zip | +| TTC | TS-3GB-S.R0030-Av1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0030-av10.pdf | + +#### 10.4.28 S.R0032-0 Version 1.0 Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP) (6 December 2000) + +This document defines requirements for the cdma2000 Air Interface to support Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP). ESA provides enhanced security in authentication and ESP provides enhanced privacy of user data. Selection of cryptographic algorithms is outside the scope of this feature description. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0032 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0032 | 1 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0032.zip | +| TTC | JP-3GB-S.R0032 | 1 | Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0032.pdf | + +#### 10.4.29 S.R0033-0 Version 1.0 Realm Configured Packet Data Session Dormancy Timer (06 December 2001) + +This document specifies the requirements for the operations of the RC-PDS DT (Realm Configured Packet Data Session Dormancy Timer) feature from the perspective of the user(s) and/or the system operator. The RC-PDS DT is a timer which is used to measure the duration of dormancy of a packet data session. The purpose of this timer is similar to the packet data inactivity timer specified in the C.S0017 standard. + +The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of cdms2000 based wireless telecommunications networks.. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0033 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0033-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0033-0_v1.0.zip | + +#### 10.4.30 S.R0034-0 Version 1.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (18 April 2001) + +These guidelines are based on the content of the ANSI TIA/EIA -41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0034 | 1.0 | Published | -02-02 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0034 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0034.zip | +| TTC | TS-3GB-S.R0034v1.0 | 1.0 | Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0034-v10.pdf | + +#### 10.4.30.1 S.R0034-0 Version 2.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (29 August 2002) + +These guidelines are based on the content of the ANSI TIA/EIA -41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. This is to facilitate international roaming and to minimize fraud. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0034 | 2.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0034-0_v2.0 | 2.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0034-0_v2.0.zip | +| TTC | TS-3GB-S.R0034-0v2.0 | 2.0 | Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0034-0v20.pdf | + +### 10.4.30.2 S.R0034-0 Version 3.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (26 July 2007) + +These guidelines are based on the content of the ANSI TIA/EIA -41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. This is to facilitate international roaming and to minimize fraud. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0034-0 v3.0 | 3.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0034-0 v3.0 | 3.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0034-0_v3.0.zip | +| TTC | TS-3GB-S.R0034-0v3.0 | 3.0 | Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0034-0v3.0.pdf | + +### 10.4.31 S.R0037-0 Version 2.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (14 May 2002) + +3GPP2 document superseded by S.R0037-0 Version 3. + +#### 10.4.31.1 S.R0037-0 Version 3.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (21 August 2003) + +This document recommends the basic 3GPP2 Wireless IP Network Architecture Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0037-0 v3.0 | 3.0 | Published | 21-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TSB-151 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0037-0 V3.0 | 3.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0037-0_v3.0.zip | +| TTC | TS-3GB-S.R0037-0V3.0 | 3.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0037-0v30.pdf | + +#### 10.4.31.2 S.R0037-A Version 1.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (May 2007) + +This document recommends the basic 3GPP2 Wireless IP Network Architecture Model. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TSB-151-A | | Published | --02-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.R0037-A V1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0037-Av1.0.pdf | + +#### 10.4.31.3 S.R0037-B Version 1.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (June 2007) + +This document recommends the basic 3GPP2 Wireless IP Network Architecture Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0037-B v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0037-B V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0037-B_v1.0.zip | +| TIA | TSB-151-B | | Published | --09-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.31.4 S.R0037-B Version 2.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (June 2009) + +This document recommends the basic 3GPP2 Wireless IP Network Architecture Model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0037-B v2.0 | 2.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=/ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0037-Bv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S_R0037-B_v2.0 | +| TIA | TSB-151-B-1 | | Published | --08-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.32 S.R0048-0 Version 1.0 3G Mobile Equipment Identifier (MEID) (10 May 2001) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0048 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0048-0 V.1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTA_E_3G-S_R0048_v1.0.zip | +| TTC | TS-3GB-S.R0048v1.0 | 1.0 | Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0048-v10.pdf | + +#### 10.4.32.1 S.R0048-A Version 1.0 3G Mobile Equipment Identifier (MEID) (22 August 2003) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally as global roaming and harmonization between 3G technologies becomes a reality the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A v1.0 | 1 | Published | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0048-A V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0048-A_v1.0.zip | +| TTC | TS-3GB-S.R0048-AV1.0 | 1.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av10.pdf | + +### 10.4.32.2 S.R0048-A Version 2.0 3G Mobile Equipment Identifier (MEID) Stage 1 (22 April 2004) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally as global roaming and harmonization between 3G technologies becomes a reality the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A v2.0 | 1 | Published | 22-04-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0048-A V2.0 | 2.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0048-A_v2.0.zip | +| TTC | TS-3GB-S.R0048-AV2.0 | 2.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av20.pdf | + +### 10.4.32.3 S.R0048-A Version 3.0 3G Mobile Equipment Identifier (MEID) Stage 1 (23 September 2004) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally as global roaming and harmonization between 3G technologies becomes a reality the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A | 3.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0048-A V3.0 | 3.0 | Published | 09/12/2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0048-A_v3.0.zip | +| TTC | TS-3GB-S.R0048-AV3.0 | 3.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av30.pdf | + +### 10.4.32.4 S.R0048-A Version 4.0 3G Mobile Equipment Identifier (MEID) Stage 1 (23 June 2005) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A | 4.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0048-A V4.0 | 4.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0048-A_v4.0.zip | +| TTC | TS-3GB-S.R0048-AV4.0 | 4.0 | Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av40.pdf | + +### 10.4.33 S.R0051 Version 1.0 Enhanced Message Service (EMS) Stage 1 Description (25 July 2001) + +This document specifies the system requirements for Enhanced Message Service (EMS). + +The objective is to define and to standardize the functionality of this capability that can be incorporated into the operation of cdma2000-based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0051 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.R0051-0 V.1.0 | 1.0 | Published | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_R0051_v1.0.zip | +| TTC | TS-3GB-S.R0051-0v1.0 | 1.0 | Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0051-0v10.pdf | + +#### **10.4.34 S.R0052-0 Version 1.0 System Release Guide for the Release (ALPHA) of the cdma2000 System Specifications (15 January 2004)** + +This document is re-numbered as SC.R2003-002 v1.0 + +#### **10.4.35 S.S0053-0 Version 1.0 Common Cryptographic Algorithms (21 January 2002)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAE.3G-S.S0053 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0053-0v1.0.pdf | + +#### **10.4.35.1 S.S0053-0 Version 2.0 Common Cryptographic Algorithms (May 2009)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0053-0 v2.0 | 2.0 | Published | 16-12-2009 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742.8/ARIB_STD-T64-S.S0053-0v2.0.pdf | + +#### **10.4.36 S.S0054-0 Version 1.0 Interface Specification for Common Cryptographic Algorithms (21 January 2002)** + +This document describes the interfaces to cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. The procedures are described in detail in Common Cryptographic Algorithms. + +The purpose of this specification is to describe the cryptographic functions without revealing the technical details that are subject to export controls under regional laws. It is intended that developers of 3GPP2 specifications for systems using these cryptographic functions use the information in this document in standards that are not subject to export restrictions. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0054-0 v1.0 | 1.0 | Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0054-0_V1.0.PDF | +| TTA | TTAE.3G-S.S0054 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0054-0v1.0.pdf | + +### **10.4.37 S.S0055-0 Version 1.0 Enhanced Cryptographic Algorithms (21 January 2002)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0055-0 v1.0 | 1.0 | Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0055-0_V1.0.PDF | +| TIA | TIA-946 | | Published | -06-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAE.3G-S.S0055 v1.0 | 1.0 | Published | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0055-0v1.0.pdf | + +### **10.4.37.1 S.S0055-A Version 1.0 Enhanced Cryptographic Algorithms (November 2003)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A v1.0 | 1 | Published | --11-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0055-A V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0055-A_v1.0.zip | + +### **10.4.37.2 S.S0055-A Version 2.0 Enhanced Cryptographic Algorithms (17 January 2005)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A | 2.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0055-A V2.0 | 2.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0055-A_v2.0.zip | + +### **10.4.37.3 S.S0055-A Version 3.0 Enhanced Cryptographic Algorithms (26 September 2005)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A | 3.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-946-1 | | Published | -10-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.S0055-A V3.0 | 3.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0055-A_v3.0.zip | + +#### **10.4.37.4 S.S0055-A Version 4.0 Enhanced Cryptographic Algorithms (January 2008)** + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-946-2 [E] | | Published | -03-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| ARIB | STD-T64-S.S0055-A v4.0 | 4.0 | Published | 06-06-2008 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742.8/ARIB_STD-T64-S.S0055-Av4.0.pdf | + +#### **10.4.38 S.R0057-0 Version 1.0 IP-based Service Architecture System Requirements (09 July 2002)** + +This document specifies the system requirements for the "IP-based Service Architecture" from the perspective of the user(s) and/or the network operator for the support of IP multimedia applications. + +IP multimedia applications are supported by IP multimedia sessions that use IP connectivity bearers of the All-IP network. This document identifies stage 1 architectural requirements for the All IP network to support the applications. + +The objective is to define and to standardize the "IP-based Service Architecture" that can be incorporated into the operations of cdma2000 based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0057 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0057-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0057-0_v1.0.zip | +| TTC | TS-3GB-S.R0057-0v1.0 | 1.0 | Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0057-0v10.pdf | + +#### **10.4.39 S.R0058-0 Version 1.0 IP Multimedia Domain System Requirements (17 April 2003)** + +This document specifies the system requirements for and operations of the IP Multimedia Domain (IP-MM Domain) system. The IP Multimedia Domain system encompasses the mobile station, the access network, and the core network. The various major functions and capabilities of the IP-MM Domain system are discussed with a focus on the broad requirements that shall be met in providing those functions and capabilities. + +The requirements contained in this document apply to the complete IP Multimedia Domain system. Actual development of stage 2 and stage 3 work is expected to be done in a phased manner, with releases of the specifications containing successively more complete implementations of these requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0058 | 1.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0058_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.R0058_v1.0.zip | +| TTC | TS.3GB-S.R0058-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0058-0v1.0.pdf | + +#### **10.4.40 S.R0059-0 Version 1.0 Legacy MS Domain – Step 1 System Requirements (16 May 2002)** + +This document specifies the system requirements for and operations of the initial release (step-1) of the Legacy MS Domain (LMSD) of the All-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces and the roles it plays in the functioning of the network. + +The requirements contained in this document apply only to the initial step of the LMSD. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0059 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0059-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0059-0_v1.0.zip | + +#### **10.4.41 S.R0060-0 Version 1.0 Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Testing Stage 1 Description (14 March 2002)** + +This document specifies the product conformance objectives to be met by the Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Test Specification. The overall objective of this activity is the development of an industry standard compliance test specification, which can be employed to ensure that R-UIM equipped handsets properly interface with various vendor provided R-UIM cards. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0060-0 v1.0 | 1.0 | Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0060-0_V1.0.PDF | +| CCSA | CWTS-MC-S.R0060 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0060-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0060-0_v1.0.zip | + +#### **10.4.42 S.R0061-0 Version 1.0 Wireless Immediate Messaging Stage 1 Requirements (25 October 2002)** + +This document specifies the requirements for and operations of the immediate messaging feature from the perspective of the user(s) and/or the system operator. Immediate Messaging (IM) is one of the most popular services on the Internet because of its near real-time, interactive nature. IM, using Presence information, allows users to determine when their friends are online and communicate with them in near real-time. + +The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of 3GPP2 based wireless telecommunications networks. This document makes extensive use of the Internet terminology to ensure alignment with immediate messaging service description and behaviour in Internet recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0061 | 1.0 | Published | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0061-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0061-0_v1.0.zip | + +#### **10.4.43 S.R0062-0 Version 1.0 Presence for Wireless Systems Stage 1 Requirements (30 October 2002)** + +This document defines stage 1 level requirements of the presence service from the perspective of the user and the system operator, so that it may be incorporated into cdma2000 based wireless networks. This document limits itself to presence service and does not delve into other applications that make use of presence, such as instant messaging. + +Presence is an attribute related to, but quite different from mobility information, and is a service that can be exploited to create additional services. The presence service enables presence information to be made available to other users or services. This stage 1 makes extensive use of Internet terminology to ensure alignment with the presence service description and behaviour in Internet recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0062 | 1.0 | Published | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0062-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0062-0_v1.0.zip | + +#### **10.4.44 S.R0064-0 Version 1.0 Multimedia Messaging Services (MMS) Stage 1 Requirements (30 October 2002)** + +This document defines the stage 1 description of the non-real-time Multimedia Messaging Service (MMS). MMS will allow users to send and receive messages exploiting the whole array of media types available today, e.g., text, images, audio, and video, while also making it possible to support new content types as they become popular. A multimedia message (MM), as observed by the user, is a combination of one or more different media elements in a multimedia presentation that can be transferred without the requirements for the need to be transferred in real-time. The multimedia messaging service shall be capable of supporting current and future multimedia types, and exploit the advances being made in the multimedia technology, with additional mobile requirements. Stage one is the set of requirements seen primarily from the subscriber's and service providers' points of view. It includes information of relevance to network operators, media content suppliers, service providers, and terminal and network manufacturers. + +It contains core requirements for the Multimedia Messaging Service, sufficient to provide a complete service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0064-0 | 1.0 | Published | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0064-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0064-0_v1.0.zip | +| TTC | TS-3GB-S.R0064-0v1.0 | 1.0 | Published | 14-02-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0064-0v10.pdf | + +#### **10.4.44.1 S.R0064-A Version 1.0 Multimedia Messaging Services (MMS) Stage 1 Requirements (22 April 2004)** + +This document defines the stage 1 description of the non-real-time Multimedia Messaging Service (MMS). MMS will allow users to send and receive messages exploiting the whole array of media types available today, e.g., text, images, audio, and video, while also making it possible to support new content types as they become popular. A multimedia message (MM), as observed by the user, is a combination of one or more different media elements in a multimedia presentation that can be transferred without the requirements for the need to be transferred in real-time. The multimedia messaging service shall be capable of supporting current and future multimedia types, and exploit the advances being made in the multimedia technology, with additional mobile requirements. Stage + +one is the set of requirements seen primarily from the subscriber's and service providers' points of view. It includes information of relevance to network operators, media content suppliers, service providers, and terminal and network manufacturers. + +It contains core requirements for the Multimedia Messaging Service, sufficient to provide a complete service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0064-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0064-A v1.0 | 1.0 | Published | 15-11-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0064-A_v1.0.zip | + +#### **10.4.45 S.R0065-0 Version 1.0 Fast Call Set-up System Requirements (15 April 2002)** + +This document specifies the system requirements for Fast Call Setup. This feature allows accelerated process in call setup (bearer resource assignment), which is particularly beneficial when a connection is returned from dormancy as a result of a packet arrival to the wireless network. The feature can be considered as falling into the category of standing requirements for network performance improvement. + +The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000 based wireless telecommunications networks. + +The Fast Call Setup feature is a set of enhancements/mechanisms that reduce the latency involved in MS terminated and MS originated call setup. + +Call Setup involves a set of signalling message exchange between the Mobile Station, Base Station, and the Network in order to allocate resources and allow user communication to proceed. Each step of this process introduces delay that contributes to the end-to-end call setup latency. Enhancements that reduce the delay in each step of this process and enhancements that streamline this process result in reduced call setup latency which is beneficial to cdma2000 services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0065 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0065-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0065-0_v1.0.zip | +| TTC | TS-3GB-S.R0065-0v1.0 | 1.0 | Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0065-0v10.pdf | + +#### **10.4.46 S.R0066-0 Version 1.0 IP Based Location Services Stage 1 Requirements (17 April 2003)** + +This version of the stage 1 supports location through IP in current packet data connections offered in cdma2000. SIP-based services in the ALL-IP domain (MMD), such as VoIP, are not assumed to be supported. Thus deployment of IP Based Location Services will be possible prior to a full standardization and deployment of MMD. By the same token, there is no concept of an "emergency call" in the current packet data domain. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0066-0 | 1.0 | Published | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0066-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0066-0_v1.0.zip | +| TTC | TS-3GB-S.R0066-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0066-0v1.0.pdf | + +#### **10.4.47 S.R0068-0 Version 1.0 Link Layer Assisted Robust Header Compression Stage 1 Requirements (11 June 2002)** + +This document specifies the requirements for and operations of the Link Layer Assisted Header Compression (LLA HC) from the perspective of the user and the system operator. + +The objective is to define and to standardize the functionality of the this feature that can be incorporated into the operations of CDMA2000 based wireless telecommunications networks. + +The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the ALLIP multimedia domain, although ALLIP is not the only application. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0068 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0068-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0068-0 v1.0.zip | +| TTC | TS-3GB-S.R0068-0v1.0 | 1.0 | Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0068-0v10.pdf | + +#### **10.4.48 S.R0069-0 Version 1.0 Header Stripping and Generation Stage 1 Requirements (15 March 2002)** + +This document specifies the requirements for and operations of the header stripping and generation feature from the perspective of the user and the system operator. + +The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of CDMA2000 based wireless telecommunications networks. + +The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the ALLIP multimedia domain, although ALLIP is not the only application. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0069 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0069-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0069-0 v1.0.zip | + +#### **10.4.49 S.R0070-0 Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002)** + +3GPP2 document is superseded by SC.R1003-0 v1.0 + +#### **10.4.50 S.R0071 Version 1.0 Legacy System Packet Data Surveillance Requirements Stage 1 Requirements (18 April 2002)** + +The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested. + +This document serves as a pointed to the appropriate Standards Development Organization (SDO) documents for Packet Data Surveillance (PDS) for 3GPP2 All-IP systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0071 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0071-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0071-0 v1.0.zip | + +#### **10.4.51 S.R0072-0 Version 1.0 All IP Packet Data Surveillance Requirements Stage 1 Requirements (18 April 2002)** + +The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested. + +This document serves as a pointer to the appropriate Standards Development Organization (SDO) documents for Packet Data Surveillance (PDS) for 3GPP2 All-IP systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0072 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0072-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0072-0 v1.0.zip | + +#### **10.4.52 S.R0073-0 Version 1.0 Internet Over-the-Air Handset Configuration Management (IOTA) Stage 1 (11 July 2002)** + +This document specifies the requirements for and operation of Internet based Over-the-Air Handset Configuration Management (IOTA HCM) from the perspective of the users and system operators. + +The objective of this document is to define the requirements of this feature for incorporation into the operations of cdma2000 based wireless telecommunications systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0073 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0073-0 v1.0 | 1.0 | Published | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0073-0 v1.0.zip | +| TTC | TS-3GB-S.R0073-0v1.0 | 1.0 | Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0073-0v10.pdf | + +#### **10.4.53 S.R0074-0 Version 1.0 File Format for Multimedia Services (FFMS) Stage 1 Requirements (17 April 2003)** + +This document specifies the requirements for the file format for multimedia services (FFMS) feature from the perspective of the user(s) and/or the system operator. The objective is to define and to standardize the file that can be used for interchanging multimedia data in general multimedia services including the Multimedia Messaging Services and the Multimedia Streaming Services. Multimedia data will be stored in a single file,. Employing a common file format also enables combined services. For example, a multimedia message is sent to and stored in a multimedia streaming server, and then it is used for streaming to a multimedia streaming client terminal. This document does not specify how this file format is used in specific services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0074 | 1.0 | Published | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0074_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.R0074_v1.0.zip | +| TTC | TS-3GB-S.R0074-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0074-0v1.0.pdf | + +#### 10.4.54 S.R0075-0 Version 1.0 Accounting & Auditing AL-IP System Requirements (17 April 2003) + +This document specifies the system requirements for Accounting & Auditing in the All-IP Network Architecture Model (Nam – S.R0037-0). The AAA is the primary functional entity with respect to the Accounting & Auditing functionality, interfaces, and the role it plays in the support of facilities & services message accounting in the network. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0075-0 | 1.0 | Published | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0075-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0075-0_v1.0.zip | +| TTC | TS-3GB-S.R0075-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0075-0v1.0.pdf | + +#### 10.4.55 S.S0078-0 Version 1.0 Common Security Algorithms (12 December 2002) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-0 v1.0 | 1.0 | Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB_STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0078-0_V1.0.PDF | +| CCSA | CCSA-TSD-MC-S.S0078-0 | 1.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0078-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0078-0_v1.0.zip | + +##### 10.4.55.1 S.S0078-A Version 1.0 Common Security Algorithms (13 December 2004) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0078-A_v1.0.zip | + +##### 10.4.55.2 S.S0078-A Version 2.0 Common Security Algorithms (17 January 2005) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 2.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v2.0 | 2.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0078-A_v2.0.zip | + +### **10.4.55.3 S.S0078-A Version 3.0 Common Security Algorithms (26 September 2005)** + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 3.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v3.0 | 3.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0078-A_v3.0.zip | + +### **10.4.55.4 S.S0078-A Version 4.0 Common Security Algorithms (26 September 2005)** + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-A v4.0 | 4.0 | Published | 06-06-2008 | http://www.arib.or.jp/IMT-2000/ARIB_STD/ITU-T/T64forQ.1742.8/ARIB_STD-T64-S.S0078-Av4.0.pdf | + +### **10.4.55.5 S.S0078-B Version 1.0 Common Security Algorithms (February 2008)** + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-B v1.0 | 1.0 | Published | 06-06-2008 | http://www.arib.or.jp/IMT-2000/ARIB_STD/ITU-T/T64forQ.1742.8/ARIB_STD-T64-S.S0078-Bv1.0.pdf | + +### **10.4.56 S.R0079-0 Version 1.0 Support for End-to-End QoS Stage 1 Requirements (13 May 2004)** + +This document describes the requirements necessary to support E2E (End-to-End) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging, and extending where applicable, the standard IETF protocols for QoS. The proposed functionality described by the requirements include the use of int-serv, diff-serv, int-serv to diff-serv inter-working, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 Radio Link QoS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0079-0 v1.0 | 1 | Published | 13-05-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0079-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0079-0_v1.0.zip | +| TTC | TS-3GB-S.R0079-0V1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0079-0v10.pdf | + +### **10.4.56.1 S.R0079-A Version 1.0 Support for End-to-End QoS Stage 1 Requirements (29 June 2006)** + +This document describes the requirements necessary to support E2E (End-to-End) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging, and extending where applicable, the standard IETF protocols for QoS. The proposed functionality described by the + +requirements include the use of int-serv, diff-serv, int-serv to diff-serv inter-working, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 Radio Link QoS. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0079-A v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0079-A V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0079-A_v1.0.zip | +| TTC | TS-3GB-S.R0079-AV1.0 | 1.0 | Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0079-av10.pdf | + +#### **10.4.57 S.R0080-0 Version 1.0 CDMA2000 Wideband Speech Codec Stage 1 Requirements (20 February 2003)** + +Wideband speech and audio coding has been gaining popularity in recent years. The emergence of the 3rd generation cellular systems as well as increasing public demand for applications such as Wireless multimedia, Voice over IP, Videophone, ISDN teleconferencing systems, Multi-point interactive audiovisual communication and Audio streaming require improved voice quality and intelligibility. Multimedia services are among the main deliverables of 3G wireless communications. This implies the use of high Quality audio and speech in multimedia content. Even in 3G voice applications the introduction of wideband speech would be an important step for CDMA service providers to deliver speech quality beyond the traditional limits of wire line communication systems. + +This document describes the cdma2000 Wideband Speech Codec stage-1 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0080-0v1.0 | 1.0 | Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0080-0_v1.pdf | +| CCSA | CCSA-TSD-MC-S.R0080-0 | 1.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0080-0_v1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0080-0_v1.0.zip | + +#### **10.4.58 S.R0082-0 Version 1.0 Enhanced Packet Data Air Interface Security (22 August 2003)** + +This document defines requirements for the cdma2000 Air Interface to support Data Subscriber Authentication (DSA) and Data Privacy (DP) for packet data services. DSA provides enhanced security in authentication and DP provides enhanced privacy of user data. DSA provides mutual authentication between the Access Terminal and the serving Access Network. DP provides encryption to prevent signalling and user traffic from unauthorized disclosure, and to prevent hijacking of user data channels. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0082 v1.0 | 1 | Published | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0082 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0082_v1.0.zip | +| TTC | TS-3GB-S.R0082-0V1.0 | 1.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0082-0v10.pdf | + +#### **10.4.59 S.R0083-0 Version 1.0 Broadcast-Multicast Service Security Framework (16 October 2003)** + +This document defines the security framework for the Broadcast-Multicast Services (BCMCS). The security framework provides a logical description of the security information, functions and protocols for BCMCS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0083-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0083-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0083-0_v1.0.zip | +| TTC | TS-3GB-S.R0083-0V1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0083-0v1.0.pdf | + +#### **10.4.59.1 S.S0083-A Version 1.0 Broadcast-Multicast Service Security Framework (26 August 2004)** + +This document defines the security framework for the Broadcast-Multicast Services (BCMCS). The security framework provides a logical description of the security information, functions and protocols for BCMCS. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0083-A | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-1053 | | Published | --01-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.S0083-A V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0083-A_v1.0.zip | +| TTC | TS-3GB-S.S0083-AV1.0 | 1.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsss0083-av10.pdf | + +#### **10.4.60 S.R0084-0 Version 2.0 Prepaid Packet Data Service in cdma2000 Wireless IP Network, Stage 1 Requirements (18 September 2003)** + +Prepaid service allows the subscriber to pay for packet data services prior to usage. A prepaid subscriber establishes an account with the service provider to access packet data services in home and roaming networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0084-0v2.0 | 1 | Published | 18-09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0084-0 V2.0 | 2.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0084-0_v2.0.zip | +| TTC | TS-3GB-S.R0084-0V2.0 | 2.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0084-0v20.pdf | + +#### **10.4.61 S.R0086-A Version 1.0 IMS Security Framework (10 June 2004)** + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0086Av1.0 | 1.0 | Published | 24-03-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0086-A V1.0 | 10 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0086-Av1.0.zip | +| TTC | TS-3GB-S.R0086-AV1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S_R0086-Av1.0.pdf | + +#### 10.4.61.1 S.S0086-B Version 1.0 IMS Security Framework (08 December 2005) + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0086-B | 1 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1091 | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.S0086-B V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_S0086-B_v1.0.zip | +| TTC | TS-3GB-S.S0086-B V1.0 | 1.0 | Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0086-bv10.pdf | + +#### 10.4.61.2 S.S0086-B Version 2.0 IMS Security Framework (February 2008) + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0086-B v2.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=/ITU-T/Q.1742//Q.1742.8 | +| TTC | TS-3GB-S.S0086-B V2.0 | 2.0 | Published | 06-12-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0086-Bv2.0.pdf | + +#### 10.4.62 S.R0087-0 Version 1.0 3GPP2 – WLAN Interworking Stage 1 Requirements (22 July 2004) + +This document describes requirements of interworking between 3GPP2 systems 2 + +and Wireless Local Area Networks (WLANs). The intent of 3GPP2 – WLAN 3 + +Interworking is to extend 3GPP2 packet data services and/or capabilities to the 4 WLAN environment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0087-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0087-0 v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0087-0_v1.0.zip | +| TTC | TS-3GB-S.R0087-0V1.0 | 1.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0087-0v10.pdf | + +#### 10.4.62.1 S.R0087-A Version 1.0 cdma2000 – WLAN Interworking Stage 1 Requirements (23 February 2006) + +This document describes requirements of interworking between cdma2000®1 systems 2 and Wireless Local Area Networks (WLANs). The intent of cdma2000 – WLAN is to extend cdma20002 packet data and multimedia services and/or capabilities to the WLAN environment, and to support the handoff of voice calls between WLAN and cdma2000 1X circuit-switched (CS) environments. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0087-A v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0087-A v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0087-A_v1.0.zip | +| TTC | TS-3GB-S.R0087-AV1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0087-av10.pdf | + +#### 10.4.63 S.R0090-0 Version 1.0 Network Initiated Data Session (NIDS) Stage 1 Requirements (10 June 2004) + +This document defines the requirements for providing the Network Initiated Data Session (NIDS) capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R-0090-0 v1.0 | 1 | Published | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R-0090-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R-0090-0_v1.0.zip | +| TTC | TS-3GB-S.R-0090-0V1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0090-0v10.pdf | + +#### 10.4.64 S.R0092-0 Version 1.0 Legacy MS Domain Step 2 System Requirements (18 March 2004) + +This document specifies the system requirements for and operations of the second release (Step-2) of the Legacy MS Domain (LMSD) of the All-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces, and the roles it plays in the functioning of the network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R-0092-0 v1.0 | 1 | Published | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R-0092-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R-0092-0_v1.0.zip | +| TTC | TS-3GB-S.R0092-0V1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0092-0v10.pdf | + +#### 10.4.65 S.S0093-0 Version 1.0 cdma2000 Network Performance Measurement Types (11 December 2003) + +This document defines the Performance Measurement Types applicable to CDMA and cdma2000 systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0093-0 v1.0 | 1 | Published | 11-12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0093-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.S0093-0 v1.0.zip | +| TTC | TS-3GB-S.S0093-0V1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsss0093-0v10.pdf | + +#### 10.4.65.1 S.S0093-0 Version 2.0 cdma2000 Network Performance Measurement Types Revision: 0 (18 January 2006) + +This document defines the Performance Measurement Types applicable to CDMA and cdma2000 systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0093-0 v2.0 | 2.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0093-0 V2.0 | 2.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.S0093-0 v2.0.zip | +| TTC | TS-3GB-S.S0093-0V2.0 | 2.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0093-0v20.pdf | + +#### 10.4.65.2 S.S0093-0 Version 3.0 cdma2000 Network Performance Measurement Types Revision: 0 (October 2008) + +This document defines the Performance Measurement Types applicable to CDMA and cdma2000 systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0093-0 v3.0 | 3.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=/ITU-T/Q.1742/Q.1742.8 | +| TTC | TS-3GB-S.S0093-0V3.0 | 3.0 | Published | 06-03-2009 | http://www.ttc.or.jp/j/document_list/free/3gpps2009/TS/TS-3GB-S.S0093-0v3.0.pdf | + +#### 10.4.66 S.R0094-0 Version 1.0 Rm Interface Enhancements for cdma2000 System Requirements (17 February 2005) + +This document specifies the system requirements for an enhanced Rm Interface. The objective is to define and to standardize the functionality of this interface for incorporation into the operations of cdma2000 based wireless telecommunications networks. + +The Rm Interface is between a Mobile Termination 2 (MT2) and a Terminal Equipment 2 (TE2). An MT2 is a cdma2000 network interface device, such as a hand-held phone. A TE2 is a general-purpose computer such as a laptop. The Rm Interface is currently specified in C.S0017 [3] to support only a best effort, point-to-point packet data link assuming the presence of an RS-232 physical layer. Enhancements are needed to support applications hosted on the TE2 that require Quality-of-Service (QoS) from the cdma2000 network, and to support a network-layer interface that can be re-used across many different physical layer technologies. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0094-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0094-0 V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.R0094-0 v1.0.zip | +| TTC | TS-3GB-S.R0094-0V1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0094-0v10.pdf | + +#### **10.4.67 S.R0095-0 Version 1.0 Support for IP Multimedia Services identity Module (ISIM) on Universal Integrated Circuit Card (UICC) in 3GPP2 Systems Stage 1 Requirements (10 June 2004)** + +This document defines the enhancements required for the support of IMS capable mobile stations equipped with Universal Integrated Circuit Card (UICC). This document specifies the requirements and operations for the support of ISIM on UICC. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0095-0-v1.0 | 1 | Published | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R-0095-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R-0095-0_v1.0.zip | +| TTC | TS-3GB-S.R0095-0V1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0095-0v10.pdf | + +#### **10.4.68 S.R0096-0 Version 1.0 Transcoder Free Operation Stage 1 Requirements (18 March 2004)** + +This document states that Transcoder Free Operation (TrFO) is the transport of compressed speech, from legacy mobiles, in a packet transport network through the elimination of unnecessary coding and decoding of the signal by intermediate elements in the bearer path. Transcoders may be associated either with the RAN or Media Gateway (MGW). By transporting only the compressed speech, TrFO achieves bandwidth efficiencies in the bearer stream and reduces round trip delays introduced by unnecessary transcoding. Also, TrFO may increase voice quality. TrFO is not applicable to VoIP. TrFO is a capability of the Legacy MS domain. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0096-0 v1.0 | 1 | Published | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0096-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0096-0_v1.0.zip | +| TTC | TS-3GB-S.R0096-0V1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0096-0v10.pdf | + +#### **10.4.69 S.R0100-0 Version 1.0 Push to Talk over Cellular (PoC) System Requirements (29 September 2005)** + +The PoC system level requirements specified in this document describe the requirements for PoC with respect to the Core Network, Radio Access Network, and Mobile Station. The system requirements support the application requirements and use cases specified by the OMA (Open Mobile Alliance). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0100-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0100-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0100-0_v1.0.zip | + +#### **10.4.70 S.R0101-0 Version 1.0 IOTA Device Management for cdma2000 Systems – Stage 1 Requirements ( 22 April 2004)** + +This document specifies the stage-1 Mobile Station (MS) and Operator requirements for the next release of IP Based Over-the-Air Handset Configuration standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0101-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0101-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0101-0_v1.0.zip | + +#### **10.4.71 S.R0103-0 Version 1.0 Network Firewall Configuration and Control – NFCC Stage 1 Requirements (09 December 2004)** + +This document specifies the system requirements and operation of the Network Firewall Configuration and Control (NFCC) feature, from both the perspective of the subscriber and the system operator. The objective is to define and to standardize the functionality of this feature to be incorporated into the operations of CDMA2000®1 based wireless telecommunications networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0103-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TTA | TTAT.3G-S.R0103-0 V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0103-0_v1.0.zip | +| TTC | TS-3GB-S.R0103-0V1.0 | 1.0 | Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0103-0v10.pdf | + +#### **10.4.72 S.R0104-0 Version 1.0 HRPD Network Access Authentication for a Hybrid Access Terminal (HAT) with an R-UIM Used to Access Spread Spectrum Systems Requirements (21 October 2004)** + +A hybrid access terminal (referred to herein as a Hybrid Access Terminal, or HAT) is a device which can access both cdma2000® 1x and HRPD networks for packet data services. + +To access the cdma2000 1x network, a HAT that has an R-UIM uses R-UIM-supported CAVE-based authentication. To access the HRPD network, an optional network access authentication step may be required by the HRPD network. This optional step uses CHAP to exchange a challenge and response between the HAT and HRPD network. Currently, CHAP specifies that MD5 is used to compute the response. It is important to note that MD5 is not currently supported by all R-UIMs used to access a cdma2000 1x network. + +For an operator that deploys both cdma2000 1x and HRPD networks, there can be benefits to using common authentication credentials and authentication methods for accessing both networks. + +These requirements allow a properly configured HAT with an R-UIM to use CAVE-based authentication for access to both networks. These requirements specify the HAT authentication requirements and also the support required by the HRPD AN-AAA to authenticate such a HAT. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0104-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TTA | TTAT.3G-S.R0104-0 V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S_R0104-0_v1.0.zip | +| TTC | TS-3GB-S.R0104-0V1.0 | 1.0 | Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0104-0v10.pdf | + +#### **10.4.73 S.R0105-0 Version 1.0 Hot-lining Service (Packet Data) Stage 1 Requirements (08 December 2004)** + +This document specifies the system requirements for Hot-lining for packet data service. The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000®1 based wireless IP networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0105-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0105-0 V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0105-0_v1.0.zip | +| TTC | TS-3GB-S.R0105-0V1.0 | 1.0 | Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0105-0v10.pdf | + +#### 10.4.74 S.R0106-0 Version 1.0 Packet-Switched Video Telephony Stage 1 (21 July 2005) + +This document defines the functional characteristics and the requirements of the packet-switched Video Telephony (VT) services, sometimes also referred to as Multimedia Conversational Services (MCS). Video Telephony is defined as one-to-one video/speech communication capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0106-0 | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0106-0 V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0106-0_v1.0.zip | +| TTC | TS-3GB-S.R0106-0 V1.0 | 1.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0106-0v10.pdf | + +#### 10.4.74.1 S.R0106-0 Version 2.0 Packet-Switched Video Telephony Stage 1 (29 March 2007) + +This document defines the functional characteristics and the requirements of the packet-switched Video Telephony (VT) services, sometimes also referred to as a Multimedia Conversational Services (MCS). Video Telephony is defined as one-to-one video/speech communication capability. VT (MCS) should be used as a basis for multiparty multimedia conferencing, but this is out of scope for the initial document revision. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0106-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0106-0 V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0106-0_v2.0.zip | +| TTC | TS-3GB-S.R0106-0V2.0 | 2.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0106-0v2.0.pdf | + +#### 10.4.74.2 S.R0106-A Version 1.0 Packet-Switched Video Telephony Stage 1 Requirements (May 2008) + +This document defines the functional characteristics and the requirements of the packet-switched Video Telephony (VT) services, sometimes also referred to as a Multimedia Conversational Services (MCS). Video Telephony is defined as one-to-one video/speech communication capability. VT (MCS) should be used as a basis for multiparty multimedia conferencing, but this is out of scope for the initial document revision. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0106-A v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=/ITU-T/Q.1742/Q.1742.8 | +| TTA | TTAT.3G-S.R0106-AV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0106-A_v1.0 | +| TTC | TS-3GB-S.R0106-AV1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0106-Av1.0.pdf | + +### 10.4.75 S.R0108-0 Version 1.0 HRPD-cdma2000 1x Interoperability for Voice and Data System Requirements (23 February 2006) + +This document defines the system requirements for HRPD-cdma2000 1x Interoperability for Voice and Data. The cellular network includes Multimedia Domain (MMD), Legacy Mobile Station Domain Support (LMSD), and HRPD/cdma2000 1x radio access networks (RANs) for the delivery of voice, video, and data services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0108-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0108-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0108-0_v1.0.zip | +| TTC | TS-3GB-S.R0108-0V1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsr0108-0v10.pdf | + +### 10.4.75.1 S.R0108-0 Version 2.0 HRPD-cdma2000 1x Interoperability for Voice and Data System Requirements (17 May 2007) + +This document defines the system requirements for HRPD-cdma2000 1x Interoperability for Voice and Data. The cellular network includes Multimedia Domain (MMD), Legacy Mobile Station Domain Support (LMSD), and HRPD/cdma2000 1x radio access networks (RANs) for the delivery of voice, video, and data services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0108-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1128 | | Published | --08-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0108-0 V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0108-0_v2.0.zip | +| TTC | TS-3GB-S.R0108-0V2.0 | 2.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0108-0v2.0.pdf | + +### 10.4.76 S.S0109-0 Version 1.0 Generic Bootstrapping Architecture (GBA) Framework (30 March 2006) + +This document describes the security features and a mechanism to bootstrap keys for application security. The scope of this specification includes a generic bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential. The specification also describes a mechanism, called GBA\_U, to bootstrap keys inside the (R-)UIM as well as keys in the ME. GBA\_U requires GBA support in the (R-)UIM, but provides enhanced security by storing certain derived keys on the (R-)UIM. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0109-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-1098 | | Published | xx-01-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.S0109-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0109-0_v1.0.zip | +| TTC | TS-3GB-S.S0109-0V1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0109-0v10.pdf | + +#### 10.4.76.1 S.S0109-0 Version 2.0 Generic Bootstrapping Architecture (GBA) Framework (February 2008) + +This document describes the security features and a mechanism to bootstrap keys for application security. The scope of this specification includes a generic bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential. The specification also describes a mechanism, called GBA\_U, to bootstrap keys inside the (R-)UIM as well as keys in the ME. GBA\_U requires GBA support in the (R-)UIM, but provides enhanced security by storing certain derived keys on the (R-)UIM. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1098 | | Published | xx-01-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.S0109-0V2.0 | 2.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0109-0v2.0.pdf | + +#### 10.4.76.2 S.S0109-A Version 1.0 Generic Bootstrapping Architecture (GBA) Framework (February 2008) + +This document describes the security features and a mechanism to bootstrap keys for application security. The scope of this specification includes a generic bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential. The specification also describes a mechanism, called GBA\_U, to bootstrap keys inside the (R-)UIM as well as keys in the ME. GBA\_U requires GBA support in the (R-)UIM, but provides enhanced security by storing certain derived keys on the (R-)UIM. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1098-A | | Published | --07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.S0109-AV1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0109-Av1.0.pdf | + +#### 10.4.77 S.S0110-0 Version 1.0 IP-Based Location Services Security Framework (23 February 2006) + +This document defines the security framework for the IP-based Location Services. The security framework provides a logical description of the security information, functions and protocols for IP-based Location Services. The architectural design of the network that supports these functions is outside the scope of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0110-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0110-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.S0110-0_v1.0.zip | +| TTC | TS-3GB-S.S0110-0V1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0110-0v10.pdf | +| TIA | TIA-1085 | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.78 S.R0111-0 Version 1.0 Expanded R-UIM Identifier (26 October 2005) + +An expanded R-UIM identifier (EUM-ID) solution is needed in time to address 25 issues associated with the impending exhaustion of the existing 32-bit UIM\_ID/ESN 26 numbering space in CDMA networks. The purpose of introducing a new identifier is 27 to define a larger numbering space, and also set the stage for moving away from the 28 functions such as authentication and reverse long code mask generation. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0111-0 | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0111-0 V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0111-0_v1.0.zip | +| TTC | TS-3GB-S.R0111-0 V1.0 | 1.0 | Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0111-0v10.pdf | + +#### **10.4.78.1 S.R0111-0 Version 2.0 Expanded R-UIM Identifier Stage 1 Requirements (17 May 2007)** + +An expanded R-UIM identifier (EUIM-ID) solution is needed in time to address 25 issues associated with the impending exhaustion of the existing 32-bit UIM\_ID/ESN 26 numbering space in CDMA networks. The purpose of introducing a new identifier is 27 to define a larger numbering space, and also set the stage for moving away from the 28 functions such as authentication and reverse long code mask generation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0111-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0111-0 V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0111-0_v2.0.zip | +| TTC | TS-3GB-S.R0111-0V2.0 | 2.0 | Published | 28-11-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0111-0v2.0.pdf | + +#### **10.4.79 S.R0112-0 Version 1.0 Generic Bootstrapping Architecture System Requirements (08 December 2005)** + +This specification contains the high level requirements for the Generic Bootstrapping Architecture work. The aim of this work is to specify a general method of providing an application and a mobile with some shared keying material. The requirements on how the application and mobile use this shared keying material is out of scope of specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0112-0 | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0112-0 V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0112-0_v1.0.zip | +| TTC | TS-3GB-S.R0112-0 V1.0 | 1.0 | Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0112-0v10.pdf | + +#### **10.4.80 S.R0113-0 Version 1.0 cdma2000 Enhanced Packet Data Air Interface System Requirements Document (25 May 2006)** + +3GPP2 document was withdrawn. + +#### **10.4.80.1 S.R0113-0 Version 2.0 cdma2000 Enhanced Packet Data Air Interface System Requirements Document (17 May 2007)** + +This document specifies the system requirements for the development of the cdma2000®1 Enhanced Packet Data Air Interface (E-PDAI) system. E-PDAI is a part of cdma2000 evolution effort . This document is intended to be used to guide the formal technical development of the E-PDAI air interfaced system and applicable IOS support. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0113-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0113-0 V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.R0113-0_v2.0.zip | +| TTC | TS-3GB-S.R0113-0V2.0 | 2.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0113-0v2.0.pdf | + +#### 10.4.81 S.S0114-0 Version 1.0 Security Mechanisms using GBA (30 March 2006) + +This document describes profile of security mechanisms such that the mechanism can utilize keys that have been generated using the Generic Bootstrapping Architecture (GBA). GBA is a method of providing keys in a generic manner based on the 3GPP2 authentication methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0114-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-1097 | | Published | --01-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.S0114-0 V1.0 | 1.0 | Published | 02-15-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.S0114-0_v1.0.zip | +| TTC | TS-3GB-S.S0114-0V1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0114-0v10.pdf | + +##### 10.4.81.1 S.S0114-0 Version 2.0 Security Mechanisms using GBA (February 2008) + +This document describes profile of security mechanisms such that the mechanism can utilize keys that have been generated using the Generic Bootstrapping Architecture (GBA). GBA is a method of providing keys in a generic manner based on the 3GPP2 authentication methods. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1097 | | Published | --01-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.S0114-0V2.0 | 2.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0114-0v2.0.pdf | + +##### 10.4.81.2 S.S0114-A Version 1.0 Security Mechanisms using GBA (February 2008) + +This document describes profile of security mechanisms such that the mechanism can utilize keys that have been generated using the Generic Bootstrapping Architecture (GBA). GBA is a method of providing keys in a generic manner based on the 3GPP2 authentication methods. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.S0114-AV1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.S0114-Av1.0.pdf | + +#### 10.4.82 S.R0115-0 Version 1.0 All-IP Network Emergency Call Support Stage 1 Requirements (14 September 2006) + +This document specifies the system requirements for All-IP Network Emergency Call Support as described in [1]. With the introduction of VoIP in HRPD [2], WLAN [6], or other air interfaces, it is important to add support for emergency calls. The intent of this specification is to provide a general set of functionality with the flexibility needed to support variances in regional regulatory requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0115-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0115-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.R0115-0_v1.0.zip | +| TTC | TS-3GB-S.R0115-0V1.0 | 1.0 | Published | 01-12-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0115-0v10.pdf | + +#### **10.4.82.1 S.R0115-0 Version 2.0 All-IP Network Emergency Call Support Stage 1 Requirements (October 2007)** + +This document specifies the system requirements for All-IP Network Emergency Call Support as described in [1]. With the introduction of VoIP in HRPD [2], WLAN [6], or other air interfaces, it is important to add support for emergency calls. The intent of this specification is to provide a general set of functionality with the flexibility needed to support variances in regional regulatory requirements. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1133 | | Published | --07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0115-0v2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0115-0_v2.0 | +| TTC | TS-3GB-S.R0115-0v2.0 | 2.0 | Published | 28/11/2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0115-0v2.0.pdf | + +#### **10.4.83 S.R0117-0 Version 1.0 Multimedia Priority Service (MMPS) for MMD-based Networks – Stage 1 Requirements (29 June 2006)** + +The scope of this requirements document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0117-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0117-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-S.R0117-0_v1.0.zip | +| TTC | TS-3GB-S.R0117-0V1.0 | 1.0 | Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0117-0v10.pdf | + +#### **10.4.83.1 S.R0117-A Version 1.0 Multimedia Priority Service (MMPS) for MMD-based Networks – Stage 1 Requirements (October 2010)** + +The scope of this requirements document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1196 | | Published | --07-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.R0117-AV1.0 | 1.0 | Published | 02-12-2010 | http://www.ttc.or.jp/imt2000/ts/tssr0117-av10.pdf | + +#### **10.4.84 S.R0118-0 Version 1.0 Telephone Number Mapping (ENUM) Stage 1 Requirements (25 May 2006)** + +The scope of this requirements document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0118-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0118-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0118-0_v1.0.zip | +| TTC | TS-3GB-S.R0118-0V1.0 | 1.0 | Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0118-0v10.pdf | + +#### 10.4.85 S.R0120-0 Version 1.0 All IP System – MMD Policy Enhancements (September 2007) + +Multimedia Domain (MMD) specifications enable an operator to apply Quality of Service (QoS) policy controls to the Internet Protocol (IP) Connectivity Access Network on session-based applications, and to provision flow-based charging rules at the Packet Data Serving node (PDSN). These current specifications are confined to the PDSN as the sole policy enforcement point supported. The scope of MMD policy needs to be expanded to include overall coordination of network resource usage for Session Initiation Protocol (SIP) and non-SIP applications for all subscribers, enhancements to policy contexts, and incorporation of additional network elements in the policy architecture. This document specifies the system requirements related to these MMD Policy Enhancements, which are intended to guide the associated technical specification development. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0120-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0120-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0120-0_v1.0.zip | +| TTC | TS-3GB-S.R0120-0V1.0 | 1.0 | Published | 28-11-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0120-0v1.0.pdf | +| TIA | TIA-1124 | | Published | --02-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.86 S.R0121-0 Version 1.0 Network Evolution for cdma2000 Networks System Requirements Document (17 May 2007) + +The scope of this requirements document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0121-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0121-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0121-0_v1.0.zip | +| TTC | TS-3GB-S.R0121-0V1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0121-0v1.0.pdf | +| TIA | TIA-1123 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.87 S.R0122-0 Version 1.0 Preferred Cryptographic Profiles (29 March 2007) + +The scope of this requirements document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0122-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-S.R0122-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.R0122-0_v1.0.zip | +| TTC | TS-3GB-S.R0122-0V1.0 | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0122-0v1.0.pdf | + +#### **10.4.88 S.R0123-0 Version 1.0 Enhanced MMD Security – Stage 1 Requirements (September 2005)** + +The scope of this requirements document is to define the requirements for Multimedia Priority Service for MMD-based Networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0123-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1125 | | Published | --02-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0123-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-S.R0123-0_v1.0.zip | +| TTC | TS-3GB-S.R0123-0V1.0 | 1.0 | Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0123-0v1.0.pdf | + +#### **10.4.89 S.R0124-0 Version 1.0 Ultra Mobile Broadband Network Architecture Model (April 2008)** + +This document provides the Network Architecture Model (NAM) for the Ultra Mobile Broadband (UMB)1 system. The NAM supports the requirements in [1] and the Phase II requirements in [2]. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.R0124-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0124-0v1.0.pdf | + +#### **10.4.89.1 S.R0124-0 Version 2.0 Ultra Mobile Broadband Network Architecture Model (June 2009)** + +This document provides the Network Architecture Model (NAM) for the Ultra Mobile Broadband (UMB)1 system. The NAM supports the requirements in [1] and the Phase II requirements in [2]. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-S.R0124-0V2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0124-0_v2.0 | + +#### **10.4.90 S.R0125-000-0 Version 1.0 VoIP Supplementary Services: Feature Descriptions (April 2008)** + +This document outlines standard operational procedures for a number of features. The particular features included were selected with the following considerations in mind: + +The features are restricted to those that afford the user an acceptable degree of control over common call situations. No attempt is made to "standardize" all of the features that are, may be, or could be made available in the wireless industry. The objective is to provide users with reasonable comfort and familiarity as they move between systems while not infringing on the manufacturers and service providers to compete by means of non-standard offerings. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-000-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.000 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-000-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-000-0v1.0 | +| TTC | TS-3GB-S.R0125-000-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.R0125-000-0v1.0.pdf | + +#### 10.4.90.1 S.R0125-502-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Forwarding-Busy (April 2008) + +Call Forwarding-Busy (CFB) permits a called subscriber to have the system send incoming calls addressed to the called subscriber's public identity to another public identity (forward-to identity) or to the called subscriber's designated message box, when the subscriber is considered to be busy. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-502-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.502 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-502-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-502-0v1.0 | +| TTC | TS-3GB-S.R0125-502-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.R0125-502-0v1.0.pdf | + +#### 10.4.90.2 S.R0125-503-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Forwarding-Default (April 2008) + +Call Forwarding-Default (CFD) permits a called subscriber to send incoming calls addressed to the called subscriber's identity to the subscriber's designated voice mailbox or to another identity (forward-to identity) when the subscriber is engaged in a call (and CFB is not enabled); does not answer the call within a specified period after being alerted (and CFNA is not enabled); or is otherwise inaccessible (including no paging response, the subscriber's location is not known, the subscriber is reported as inactive, etc.). CFD does not impact a subscriber's ability to originate calls. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-503-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.503 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-503-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-503-0v1.0 | +| TTC | TS-3GB-S.R0125-503-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-S.R0125-503-0v1.0.pdf | + +### 10.4.90.3 S.R0125-504-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Forwarding-No Answer (April 2008) + +Call Forwarding-No Answer (CFNA) permits a called subscriber to have the system send incoming calls addressed to the called subscriber's public identity to another public identity (forward-to identity) or to the called subscriber's designated voice mailbox, when the subscriber fails to answer, or is otherwise inaccessible (including TBD, etc.). CFNA does not apply when the subscriber is considered to be busy. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-504-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.504 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-504-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-504-0v1.0 | +| TTC | TS-3GB-S.R0125-504-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-504-0v1.0.pdf | + +### 10.4.90.4 S.R0125-505-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Forwarding-Unconditional (April 2008) + +Call Forwarding-Unconditional (CFU) permits a called subscriber to send incoming calls addressed to the called subscriber's public identity to another public identity (forward-to identity) or to the called subscriber's designated voice mailbox. If this feature is active, calls are forwarded regardless of the condition of the termination. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-505-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.505 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-505-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-505-0v1.0 | +| TTC | TS-3GB-S.R0125-505-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-505-0v1.0.pdf | + +### 10.4.90.5 S.R0125-506-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Transfer (April 2008) + +Call Transfer (CT) enables the subscriber to transfer an in-progress established call to a third party. The call to be transferred may be an incoming or outgoing call. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-506-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.506 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-506-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-506-0v1.0 | +| TTC | TS-3GB-S.R0125-506-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-506-0v1.0.pdf | + +#### 10.4.90.6 S.R0125-507-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Waiting (April 2008) + +Call Waiting (CW) provides notification to a controlling subscriber of an incoming call while the subscriber is in another call. Subsequently, the controlling subscriber can either answer or ignore the incoming call. If the controlling subscriber answers the incoming call, he/she may alternate between calls. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-507-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.507 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-507-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-507-0v1.0 | +| TTC | TS-3GB-S.R0125-507-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-507-0v1.0.pdf | + +#### 10.4.90.7 S.R0125-508-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Identification Presentation (April 2008) + +Calling Identification Presentation (CIP) provides the identification of the calling party to the called subscriber. One or more identities may be presented to identify the calling party. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-508-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.508 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-508-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-508-0v1.0 | +| TTC | TS-3GB-S.R0125-508-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-508-0v1.0.pdf | + +#### 10.4.90.8 S.R0125-509-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Identification Restriction (April 2008) + +Calling Identification Restriction (CIR) restricts presentation of that subscriber's Calling Identification (CI) to the called party. The terminating network may receive the Calling Identification (CI) as part of basic call setup. This CI may include one or more Calling Party identities and Redirecting Identities. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-509-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.509 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-509-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-509-0v1.0 | +| TTC | TS-3GB-S.R0125-509-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-509-0v1.0.pdf | + +#### 10.4.90.9 S.R0125-512-0 Version 1.0 VoIP Supplementary Services Descriptions: Flexible Alerting (April 2008) + +Flexible Alerting (FA) causes a call to a Pilot Identity to branch the call into several legs to alert several termination addresses (group members) simultaneously. The UEs in the group may be alerted using FA-distinct alerting. Additional calls may be delivered to the FA Pilot Identity at any time. The first leg to be answered is connected to the calling party. The other call legs are abandoned. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-512-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742/Q.1742.8 | +| TIA | TIA-1126.512 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-512-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-512-0v1.0 | +| TTC | TS-3GB-S.R0125-512-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-512-0v1.0.pdf | + +#### 10.4.90.10 S.R0125-513-0 Version 1.0 VoIP Supplementary Services Descriptions: Message Waiting Indication (April 2008) + +Message Waiting Indication (MWI) informs enrolled subscribers when a voice mail message is available for retrieval. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-513-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742/Q.1742.8 | +| TIA | TIA-1126.513 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-513-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-513-0v1.0 | +| TTC | TS-3GB-S.R0125-513-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-513-0v1.0.pdf | + +#### 10.4.90.11 S.R0125-522-0 Version 1.0 VoIP Supplementary Services Descriptions: Three-Way Calling (April 2008) + +Three-Way Calling (3WC) provides the subscriber the capability of adding a third party to an established two-party call, so that all three parties may communicate in a three-way call. If either of the two non-controlling parties to an established three-way call disconnects, the remaining parties remain connected as in a normal two-party call. If the controlling subscriber of a three-way call disconnects, all other parties are released. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-522-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742/Q.1742.8 | +| TIA | TIA-1126.522 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-522-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-522-0v1.0 | +| TTC | TS-3GB-S.R0125-522-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-522-0v1.0.pdf | + +#### 10.4.90.12 S.R0125-551-0 Version 1.0 VoIP Supplementary Services Descriptions: Abbreviated Dialling/Short Code Dialling (April 2008) + +Three-Way Calling (3WC) provides the subscriber the capability of adding a third party to an established two-party call, so that all three parties may communicate in a three-way call. If either of the two non-controlling parties to an established three-way call disconnects, the remaining parties remain connected as in a normal two-party call. If the controlling subscriber of a three-way call disconnects, all other parties are released. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-551-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.551 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-551-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-551-0v1.0 | +| TTC | TS-3GB-S.R0125-551-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-551-0v1.0.pdf | + +#### 10.4.90.13 S.R0125-552-0 Version 1.0 VoIP Supplementary Services Descriptions: Call Hold (April 2008) + +Call Hold (HOLD) allows the controlling subscriber in an active call to temporarily suspend media transmission and reception with the other party. The session is not torn down, and can be later re-activated by resuming media transmission. Meanwhile, the controlling subscriber can attend to a different task, such as responding to an incoming call that is waiting, or initiating another call. More than one call may be placed on hold. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-552-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.552 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-552-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-552-0v1.0 | +| TTC | TS-3GB-S.R0125-552-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-552-0v1.0.pdf | + +#### 10.4.90.14 S.R0125-553-0 Version 1.0 VoIP Supplementary Services Descriptions: Customized Ring Back Tone (April 2008) + +Customized Ring Back Tone service allows a user to customize the ring back tone which is played to the calling party. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-553-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.553 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-553-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-553-0v1.0 | +| TTC | TS-3GB-S.R0125-553-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-553-0v1.0.pdf | + +### 10.4.90.15 S.R0125-554-0 Version 1.0 VoIP Supplementary Services Descriptions: Directory Assistance (April 2008) + +Directory Assistance service allows a user to call directory assistance to interact with the attendant, obtain the desired destination address, and have the call connected to the desired destination with assistance from the attendant. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-554-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742/Q.1742.8 | +| TIA | TIA-1126.554 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-554-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-554-0v1.0 | +| TTC | TS-3GB-S.R0125-554-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-554-0v1.0.pdf | + +### 10.4.90.16 S.R0125-555-0 Version 1.0 VoIP Supplementary Services Descriptions: Inbound Call Restriction / Anonymous Call Rejection (April 2008) + +Inbound Call Restriction (ICR) is a call screening service that allows a subscriber to receive incoming calls only from parties whose Calling Identities are either in a list of specified identities or not in a list of specified identities. Calls restricted by the list shall be given call refusal treatment while ICR is active. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-555-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742/Q.1742.8 | +| TIA | TIA-1126.555 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-555-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-555-0v1.0 | +| TTC | TS-3GB-S.R0125-555-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-555-0v1.0.pdf | + +### 10.4.90.17 S.R0125-556-0 Version 1.0 VoIP Supplementary Services Descriptions: Outbound Call Restriction (April 2008) + +Outbound Call Restriction allows network to restrict the type of calls that a user is allowed to originate. Examples of such restrictions include: Local call only; Selected leading digits of directory number only; National long distance calls; International calls; Calls to certain destinations (e.g., Hot Line); Toll free calls Calls to certain domains only or exclusion of calls to certain domains + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-556-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742/Q.1742.8 | +| TIA | TIA-1126.556 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-556-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-556-0v1.0 | +| TTC | TS-3GB-S.R0125-556-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-556-0v1.0.pdf | + +#### 10.4.90.18 S.R0125-558-0 Version 1.0 VoIP Supplementary Services Descriptions: Terminating Identification Presentation (April 2008) + +Termination Identification Presentation (TIP) provides the identification of the called party and of the forwarded-to parties (if any) to the calling subscriber. Any form of public identity may be presented to identify the called party. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-558-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.558 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-558-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-558-0v1.0 | +| TTC | TS-3GB-S.R0125-558-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-558-0v1.0.pdf | + +#### 10.4.90.19 S.R0125-559-0 Version 1.0 VoIP Supplementary Services Descriptions: Terminating Identification Restriction (April 2008) + +Terminating Identification Restriction (TIR) restricts presentation of the Terminating Identification (TI) to the calling party. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-559-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.559 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-559-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-559-0v1.0 | +| TTC | TS-3GB-S.R0125-559-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-559-0v1.0.pdf | + +#### 10.4.90.20 S.R0125-562-0 Version 1.0 VoIP Supplementary Services Descriptions: Voice Message Retrieval (April 2008) + +Terminating Identification Restriction (TIR) restricts presentation of the Terminating Identification (TI) to the calling party. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0125-562-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TIA | TIA-1126.562 | | Published | 07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-S.R0125-562-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0125-562-0v1.0 | +| TTC | TS-3GB-S.R0125-562-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0125-562-0v1.0.pdf | + +#### 10.4.91 S.R0126-0 Version 1.0 System Requirements for Femto Cell Systems (May 2008) + +This document specifies the requirements for and operations of femto cells within cdma20001 networks from the perspective of the user(s) and/or the system operator. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0126-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0126-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0126-0 v1.0 | +| TTC | TS-3GB-S.R0126-0V1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0126-0v1.0.pdf | +| TIA | TIA-1144 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.92 S.R0127-0 Version 1.0 CAVE Based IMS Security (June 2008) + +IP Multimedia Subsystem (IMS) security is defined for cdma2000 networks in [3]. This document [3] defines how the SIP signalling is protected between the User Equipment (UE) and the Proxy Call Session Control Function (P-CSCF), how the subscriber is authenticated and how the subscriber authenticates the IMS using AKA authentication credentials present at the UE. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-S.R0127-0V1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0127-0v1.0.pdf | + +#### 10.4.93 S.R0128-0 Version 1.0 HRPD and WiMAX Inter-Technology Handoff – Stage 1 Requirements (January 2008) + +This document specifies the requirements for Interworking and Inter-Technology Handoff between 3GPP2 High Rate Packet Data (HRPD) and Worldwide Interoperability for Microwave Access (WiMAX) systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0128-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0128-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0128-0 v1.0 | +| TTC | TS-3GB-S.R0128-0V1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0128-0v1.0.pdf | + +#### 10.4.94 S.R0129-0 Version 1.0 HRPD/1XRTT and 3GPP E-UTRAN (LTE) Interworking and Inter-Technology – Stage 1 Requirements (January 2008) + +This document specifies the requirements for Interworking and Inter-Technology Handoff between 3GPP2 High Rate Packet Data (HRPD) [2,3]/cdma2000®1 1x Radio Transmission Technology (1xRTT) [1] and 3GPP Evolved Universal Terrestrial Radio Access (E-UTRA) [4,5] (also known as Long Term Evolution (LTE)) systems + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0129-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0129-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0129-0 v1.0 | +| TTC | TS-3GB-S.R0129-0V1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0129-0v1.0.pdf | + +#### 10.4.94.1 S.R0129-A Version 1.0 HRPD/1XRTT and 3GPP E-UTRAN (LTE) Interworking and Inter-Technology – Stage 1 Requirements (April 2009) + +This document specifies the requirements for Interworking and Inter-Technology Handoff between 3GPP2 High Rate Packet Data (HRPD) [2,3] / cdma2000®1 1x Radio Transmission Technology (1xRTT) [1] and 3GPP Evolved Universal Terrestrial Radio Access (E-UTRA) [4,5] (also known as Long Term Evolution (LTE)) systems + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0129-A v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0129-AV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0129-Av1.0 | +| TTC | TS-3GB-S.R0129-AV1.0 | 1.0 | Published | 15-07-2009 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0129-Av1.0.pdf | +| TIA | TIA-1175 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.94.2 S.R0129-A Version 2.0 HRPD/1XRTT and 3GPP E-UTRAN (LTE) Interworking and Inter-Technology Handoff (December 2009) + +This document specifies the requirements for Interworking and Inter-Technology Handoff between 3GPP2 High Rate Packet Data (HRPD) [2,3]/cdma2000®1 1x Radio Transmission Technology (1xRTT) [1] and 3GPP Evolved Universal Terrestrial Radio Access (E-UTRA) [4,5] (also known as Long Term Evolution (LTE)) systems + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1175-A-1 | | Published | --08-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.R0129-AV2.0 | 2.0 | Published | 19-02-2010 | http://www.ttc.or.jp/imt2000/ts/tssr0129-av20.pdf | + +#### 10.4.95 S.R0130-0 Version 1.0 Interworking and Inter-Technology Handoff for UMB and UTRA/E-UTRA Technologies – Stage 1 Requirement (February 2008) + +This document specifies the requirements for Interworking and Inter-Technology Handoffs between 3GPP2 Ultra Mobile Broadband (UMB) and access technologies supported on UTRAN (e.g., WCDMA) and EUTRAN (e.g., LTE). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0130-0 v1 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0130-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0130-0v1.0 | +| TTC | TS-3GB-S.R0130-0V1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0130-0v1.0.pdf | + +#### 10.4.96 S.R0131-0 Version 1.0 IMS Centralized Services – Stage 1 Requirement (June 2008) + +This document provides service requirements for IP Multimedia System (IMS) Centralized Services (ICS). ICS enables the delivery of IMS-based services to users regardless of the attached access network type, e.g., CS domain access (1xRTT) or IP-based (HRPD or WLAN) access. Service continuity between access networks is addressed. Service scenarios are described. Requirements are identified from both user and service provider perspectives. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0131-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0131-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0131-0 v1.0 | +| TTC | TS-3GB-S.R0131-0V1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0131-0v1.0.pdf | +| TIA | TIA-1147 | | Published | --12-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.97 S.R0134-0 Version 1.0 Evolution of Ultra Mobile Broadband – System Requirements (February 2009) + +This System Requirements Document SRD aims to outline the requirements to strengthen and broaden the capabilities of radio transmission technologies and associated network capabilities and services of Ultra Mobile Broadband. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0134-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0134-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0134-0 v1.0 | +| TTC | TS-3GB-S.R0134-0V1.0 | 1.0 | Published | 15-07-2009 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0134-0v1.0.pdf | +| TIA | TIA-1161 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.98 S.R0136-0 Version 1.0 System Requirements for MSC Pool (October 2008) + +This document specifies the requirements necessary to support MSC Pool in the CDMA2000 wireless network. MSC Pool enables signaling connections between one BSC with multiple MSCs, so the MS served by any BSC of that pool area can be served by any MSC in that pool area. MSC Pool is built upon to the Legacy Mobile Station Domain architecture. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0136-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0136-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0136-0 v1.0 | +| TTC | TS-3GB-S.R0136-0V1.0 | 1.0 | Published | 06-03-2009 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-S.R0136-0v1.0.pdf | +| TIA | TIA-1154 | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### 10.4.98.1 S.R0136-0 Version 2.0 System Requirements for MSC Pool (November 2009) + +This document specifies the requirements necessary to support MSC Pool in the CDMA2000 wireless network. MSC Pool enables signaling connections between one BSC with multiple MSCs, so the MS served by any BSC of that pool area can be served by any MSC in that pool area. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1154-1 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-S.R0136-0V2.0 | 2.0 | Published | 19-02-2010 | http://www.ttc.or.jp/imt2000/ts/tssr0136-0v20.pdf | + +#### 10.4.99 S.R0137-0 Version 1.0 Common IMS Impacts to 3GPP2 Specifications (December 2008) + +This document identifies the MMD network entities and interfaces that are covered by the documents in the first phase of Common IMS. Future enhancements to these entities and interfaces, as they pertain to the transferred documents, will be made in 3GPP rather than 3GPP2. Additional enhancements may continue to be made in 3GPP2 as needed. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0137-0 v1.0 | 1.0 | Published | --12-2009 | http://www.ccsa.org.cn/english/files.php?docpath=/ITU-T/Q.1742//Q.1742.8 | +| TTA | TTAT.3G-S.R0137-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0137-0 v1.0 | +| TTC | TS-3GB-S.R0137-0V1.0 | 1.0 | Published | 06-03-2009 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-S.R0137-0v1.0.pdf | + +#### 10.4.100 S.R0138-0 Version 1.0 eHRPD Security Frameworks (May 2009) + +This document describes security mechanisms in eHRPD. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-S.R0138-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-S.R0138-0 v1.0 | + +#### 10.4.101 SC.R1003-0 Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002) + +3GPP2 document is renamed as SC.R1003-0 Version 1.0. This document is to provide uniform procedures and guidance for the development, completion, distribution and approval of Work Items, stage 1 and System Requirements across all TSGs. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R1003-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTC | TS-3GB-SC.R1003-0v1.0 | 1.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsser1003-0v10.pdf | + +#### 10.4.102 SC.R1003-A Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (September 2010) + +This document is to provide uniform procedures and guidance for the development, completion, distribution and approval of Work Items, stage 1 and System Requirements documents across all TSGs. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-SC.R1003-Av1.0 | 1.0 | Published | 02-12-2010 | http://www.ttc.or.jp/imt2000/ts/tsser1003-av10.pdf | + +#### 10.4.103 SC.R2001-001 Version 1.0 3GPP2 System Capability Guide Release A (20 January 2000) + +This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2001-001
v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2001-001
v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-SC.R2001-001_v1.0.zip | + +#### 10.4.104 SC.R20002-001 Version 1.0 3GPP2 System Capability Guide Release B (14 June 2001) + +This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2002-001
v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2002-001
v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-SC.R2002-001_v1.0.zip | + +#### 10.4.105 SC.R2003-002 Version 1.0 System Release Guide for the Release (ALPHA) of the cdma2000 System Specifications (15 January 2004) + +3GPP2 document is renamed as document SC.R2003-002-0 Version 1.0. This document is the System Release Guide (SRG) for the 3GPP2 wireless telecommunication system. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. The objective of this document is to provide an informative overview for and reference to the Release (ALPHA) of the 3GPP2 wireless telecommunication system (cdma2000) capabilities, features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2003-002
v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2003-002
V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-SC.R2003-002_v1.0.zip | +| TTC | TS-3GB-SC.R2003-002-0V1.0 | 1.0 | Published | 08-25-2006 | http://www.ttc.or.jp/imt2000/ts/tsser2003-002-0v10.pdf | + +### 10.5 Core Network Specifications + +#### 10.5.1 X.S0001-A Version 1.0 MAP Enhancements for CDMA Packet Data Services (C-PDS) (April 2004) + +This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0001-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-880-A | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0001-A
V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0001-A_v1.0.zip | +| TTC | TS-3GB-X.S0001-AV1. | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0001-Av1.0.pdf | + +## 10.5.2 X.S0002-0 Version 1.0 TIA/EIA-41-D Location Services Enhancements (March 2004) + +This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0002-0 v1.0 | | Published | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-881 | | Published | --03-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0002-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0002-0_v1.0.zip | +| TTC | TS-3GB-X.S0002-0V1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0002-0v10.pdf | + +### 10.5.2.1 X.S0002-0 Version 2.0 MAP Location Services Enhancements (May 2006) + +This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0002-0 v2.0 | 2.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-881-1 [E] | | Published | --01-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0002-0 V2.0 | 2.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0002-0_v2.0.zip | +| TTC | TS-3GB-X.S0002-0V2.0 | 2.0 | Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0002-0v20.pdf | + +### 10.5.3 X.S0003-0 Version 1.0 One-Way Roaming from X.S0004 to GSM (January 2005) + +This document provides recommended *ANS/TIA/EIA-41-D* enhancements required to support *TIA/EIA-41 SIM* (Subscription Identification Module) roaming one-way into *GSM* serving areas (without modification to the *GSM* serving network). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0003-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-868 | | Published | --02-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0003-0 V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0003-0_v1.0.zip | +| TTC | TS-3GB-X.S0003-0V1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0003-0v10.pdf | + +### 10.5.4 X.S0004-000-E Version 1.0.0 Introduction to TIA-41 (March 2004) + +This document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E v1.0.0 | 1 | Published | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.000-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-000-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v1.0.0.zip | + +#### 10.5.4.1 X.S0004-000-E Version 2.0.0 Introduction to TIA-41 (March 2004) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E | 2.0 | Published | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.000-E-1[E] | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-000-E V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v2.0.zip | + +#### 10.5.4.2 X.S0004-000-E Version 3.0.0 Introduction to MAP (October 2005) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E | 3.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.000-E-2[E] | | Published | --08/2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-000-E V3.0 | 3.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v3.0.zip | + +#### 10.5.4.3 X.S0004-000-E Version 4.0 Mobile Application Part (MAP) – Introduction (May 2006) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-000-E v4.0 | 4.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.000-E-3[E] | | Published | --11-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-000-E V4.0 | 4.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v4.0.zip | + +#### 10.5.4.4 X.S0004-000-E Version 5.0 Mobile Application Part (MAP) – Introduction (January 2007) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E v5.0 | 5.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.000-E-4[E] | 4 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-000-E V5.0 | 5.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v5.0.zip | + +#### 10.5.4.5 X.S0004-000-E Version 6.0 Mobile Application Part (MAP) – Introduction (July 2007) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E v6.0 | 6.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-000-E V6.0 | 6.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v6.0.zip | + +#### 10.5.4.6 X.S0004-000-E Version 8.0 Mobile Application Part (MAP) – Introduction (January 2009) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-000-E V8.0 | 8.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-000-E_v8.0.zip | + +#### 10.5.4.7 X.S0004-000-E Version 9.0 Mobile Application Part (MAP) – Introduction (June 2009) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-000-E V9.0 | 9.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G | + +#### 10.5.4.8 X.S0004-200-E Version 1.0 Mobile Application Part (MAP) – Intersystem Handoff (May 2006) + +This specification defines intersystem handoff by describing the information flows between functional entities which occur in a number of intersystem handoff scenarios. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-200-E v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TIA | TIA-41.200-E | | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-200-E V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-200-E_v1.0.zip | + +#### 10.5.4.9 X.S0004-290-E Version 1.0 Mobile Application Part (MAP) – Intersystem Handoff Annexes (May 2006) + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-290-E v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TIA | TIA-41-290-E | | Published | 02-02-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-290-E V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-290-E_v1.0.zip | + +#### 10.5.4.10 X.S0004-321-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Delivery (January 2007) + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-321-E v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.321-E | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-321-E V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-321-E_v1.0.zip | + +#### 10.5.4.11 X.S0004-321-E Version 2.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Delivery (January 2009) + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-321-E V2.0 | 2.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-321-E_v2.0.zip | + +#### **10.5.4.12 X.S0004-322-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Forwarding (January 2007)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-322-E v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.322-E | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-322-E V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-322-E_v1.0.zip | + +#### **10.5.4.13 X.S0004-323-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Call Waiting (January 2007)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-323-E v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.323-E | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-323-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-323-E_v1.0.zip | + +#### **10.5.4.14 X.S0004-324-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Calling Number Identification, Calling Number Identification Restriction (January 2007)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-324-E v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-41.324-E | 0 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-324-E V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-324-E_v1.0.zip | + +#### **10.5.4.15 X.S0004-324-E Version 2.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Calling Number Identification, Calling Number Identification Restriction (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-324-E V2.0 | 2.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-324-E_v2.0.zip | + +#### **10.5.4.16 X.S0004-325-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Conference Calling (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-325-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-325-E_v1.0.zip | + +#### **10.5.4.17 X.S0004-326-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Do Not Disturb (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-326-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-326-E_v1.0.zip | + +#### **10.5.4.18 X.S0004-327-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Flexible Alerting (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-327-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-327-E_v1.0.zip | + +#### **10.5.4.19 X.S0004-328-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Mobile Access Hunting (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-328-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-328-E_v1.0.zip | + +#### **10.5.4.20 X.S0004-329-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Message Waiting Notification (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-329-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-329-E_v1.0.zip | + +#### **10.5.4.21 X.S0004-330-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Password Call Acceptance / Selective Call Acceptance (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-330-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-330-E_v1.0.zip | + +#### **10.5.4.22 X.S0004-331-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Priority Access and Channel Assignment (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-331-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-331-E_v1.0.zip | + +#### **10.5.4.23 X.S0004-332-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Remote Feature Control (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-332-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-332-E_v1.0.zip | + +#### **10.5.4.24 X.S0004-333-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Subscriber PIN Access, Subscriber PIN Intercept (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-333-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-333-E_v1.0.zip | + +#### **10.5.4.25 X.S0004-334-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Voice Message Retrieval (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-334-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-334-E_v1.0.zip | + +#### **10.5.4.26 X.S0004-335-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Calling Name Presentation, Calling Name Restriction (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-335-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-335-E_v1.0.zip | + +#### **10.5.4.27 X.S0004-336-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Wireless Emergency Services (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-336-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-336-E_v1.0.zip | + +#### **10.5.4.28 X.S0004-350-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: MDN-Based Validation (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-350-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-350-E_v1.0.zip | + +#### **10.5.4.29 X.S0004-371-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Broadcast Teleservice Transport Capability (April 2008)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-371-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-371-E_v1.0.zip | + +#### **10.5.4.30 X.S0004-372-E Version 1.0 Mobile Application Part (MAP) – Voice Feature Scenarios: Border MSC SMS Scenarios (January 2009)** + +This Annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-372-E V1.0 | 1.0 | Published | 17-07-2009 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-372-E_v1.0.zip | + +#### **10.5.4.31 X.S0004-400-E Version 1.0 Operations Administration and Maintenance (July 2005)** + +This document defines the intersystem Operations, Administration, and Maintenance (OA&M) information flows and procedures required for intersystem trunk maintenance. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-400-E | 1.0 | Published | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.400-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-400-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-400-E_v1.0.zip | + +#### **10.5.4.32 X.S0004-500-E Version 1.0.0 Introduction to Signalling Protocols (March 2004)** + +This document introduces the signalling protocols for this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-500-E v1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.500-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-500-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-500-E_v1.0.0.zip | + +#### **10.5.4.33 X.S0004-510-E Version 1.0.0 X.25 Transport Signalling Protocols (March 2004)** + +This document describes X.25 Transport Signalling Protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-510-E v1.0.0 | 1 | Published | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.510-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-510-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-510-E_v1.0.0.zip | + +#### **10.5.4.34 X.S0004-511-E Version 1.0.0 ANS/SS7 Transport Signalling Protocols (March 2004)** + +This document describes ANS/SS7 Transport Signalling Protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-511-E v1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.511-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-511-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-511-E_v1.0.0.zip | + +### 10.5.4.35 X.S0004-512-E Version 1.0.0 ITU-T SS7 Transport Signalling Protocols (March 2004) + +This document describes ITU-T SS7 Transport Signalling Protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-512-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.512-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-512-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-512-E_v1.0.0.zip | + +### 10.5.4.36 X.S0004-520-E Version 1.0.0 TCAP Application Signalling Protocols (March 2004) + +This document describes TCAP application signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-520-E v1.0.0 | 1 | Published | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.520-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-520-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-520-E_v1.0.0.zip | + +### 10.5.4.37 X.S0004-520-E Version 2.0 Mobile Application Part (MAP) TCAP Application Signalling Protocols (July 2007) + +This document describes TCAP application signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-520-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-520-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-520-E_v2.0.zip | + +### 10.5.4.38 X.S0004-540-E Version 1.0.0 MAP Operations Signalling Protocols (March 2004) + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-540-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.540-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-540-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-540-E_v1.0.0.zip | + +#### **10.5.4.39 X.S0004-540-E Version 2.0 Mobile Application Part (MAP) Operations Signalling Protocols (July 2007)** + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-540-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-540-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-540-E_v2.0.zip | + +#### **10.5.4.40 X.S0004-550-E Version 1.0.0 MAP Parameters Signalling Protocols (March 2004)** + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-550-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.550-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-550-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-550-E_v1.0.0.zip | + +#### **10.5.4.41 X.S0004-550-E Version 2.0 Mobile Application Part (MAP) Parameters Signalling Protocols (July 2007)** + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-550-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-550-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-550-E_v2.0.zip | + +#### **10.5.4.42 X.S0004-550-E Version 3.0 Mobile application part (MAP) parameters signalling protocols (June 2009)** + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-550-E V3.0 | 3.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0004-550-E_v3.0 | + +#### **10.5.4.43 X.S0004-551-E Version 1.0.0 Parameter Types Signalling Protocols (March 2004)** + +This document provides the definitions of the parameter types used in this Standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-551-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.551-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-551-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-551-E_v1.0.0.zip | + +#### **10.5.4.44 X.S0004-590-E Version 1.0.0 MAP Compatibility Signalling Protocols (March 2004)** + +While this document outlines guidelines and rules, which will in the near term be beneficial to implementation of this standard, other activities which may impact these rules are in progress. As such, the remainder of this Section, "MAP Compatibility Guidelines and Rules" may be subject to change and revision based on future TTA-41 recommendations. This is to ensure that there is no long-term impediment to Cellular Radiotelecommunications networks to evolve and implement significant new functionality. Also, to better allow for the longer-term alignment of TTA-41 with emerging international standards. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-590-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.590-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-590-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-590-E_v1.0.0.zip | + +#### **10.5.4.45 X.S0004-600-E Version 1.0 Introduction to Procedures (July 2005)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. The messages required to perform the automatic roaming are defined in Part 540. Conformance with this document shall mean that a system's externally visible behaviour is the same as the externally visible behaviour of the abstract system described here. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-600-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.600-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-600-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-600-E_v1.0.zip | + +#### **10.5.4.46 X.S0004-630-E Version 1.0 Basic Call Processing (July 2005)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-630-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.630-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-630-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-630-E_v1.0.zip | + +#### **10.5.4.47 X.S0004-630-E Version 2.0 Mobile Application Part (MAP) Basic Call Processing (July 2007)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-630-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-630-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-630-E_v2.0.zip | +| TIA | TIA-41.630-E-1[E] | | Published | --07-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### **10.5.4.48 X.S0004-630-E Version 3.0 Mobile Application Part (MAP) Basic Call Processing (April 2008)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0004-630-E V3.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-630-E_v3.0.zip | + +#### **10.5.4.49 X.S0004-640-E Version 1.0 Intersystem Procedures (July 2005)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-640-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-41.640-E | | Published | --12-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-640-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-640-E_v1.0.zip | + +#### **10.5.4.50 X.S0004-640-E Version 2.0 Mobile application part (MAP) intersystem procedures (July 2007)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-640-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-640-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-640-E_v2.0.zip | + +#### **10.5.4.51 X.S0004-641-E Version 1.0 Short message services (SMS) (July 2005)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-641-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | TIA-41.641-E | | Published | --12-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-641-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-641-E_v1.0.zip | + +### **10.5.4.52 X.S0004-641-E Version 2.0 Mobile Application Part (MAP) Short Message Services (SMS) (July 2007)** + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-641-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-641-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-641-E_v2.0.zip | + +### **10.5.4.53 X.S0004-642-E Version 1.0 Segmentation (July 2005)** + +This section describes procedures to allow the transmission of messages, which may or may not require Segmentation and Reassembly (S&R). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-642-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.642-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-642-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-642-E_v1.0.zip | + +### **10.5.4.54 X.S0004-650-E Version 1.0 Common Voice Feature Procedures (July 2005)** + +This section describes common voice feature procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-650-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.650-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-650-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-650-E_v1.0.zip | + +### **10.5.4.55 X.S0004-651-E Version 1.0 Voice Feature Procedures (July 2005)** + +This section describes modular procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-651-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.651-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-651-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-651-E_v1.0.zip | + +### **10.5.4.56 X.S0004-651-E Version 2.0 Mobile Application Part (MAP) Voice Feature Procedures (July 2007)** + +This section describes modular procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-651-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-651-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-651-E_v2.0.zip | + +### 10.5.4.57 X.S0004-660-E Version 1.0 Wireless Intelligent Network (WIN) Procedures (July 2005) + +In addition to the specific procedures described in this part of the Standard, the functional entity call and service logic processing models provide a tool used by WIN architects to model a call and to understand and describe the distribution of functions between functional entities and functional entity relationships. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-660-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.660-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-660-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-660-E_v1.0.zip | + +### 10.5.4.58 X.S0004-690-E Version 1.0 Operation Timer Values (July 2005) + +The following table provides a summary of the timers used for MAP operations. The timer values specified in this table are default values only and should be optimized for actual operating environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-690-E | 1.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.690-E | | Published | --12-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-690-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-690-E_v1.0.zip | + +### 10.5.4.59 X.S0004-690-E Version 2.0 Mobile Application Part (MAP) Timers (July 2007) + +The following table provides a summary of the timers used for MAP operations. The timer values specified in this table are default values only and should be optimized for actual operating environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer). + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-690-E v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.7/ | +| TTA | TTAT.3G-X.S0004-690-E V2.0 | 2.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-690-E_v2.0.zip | + +### 10.5.4.60 X.S0004-691-E Version 1.0 Annexes (July 2005) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742. | +| TTA | TTAT.3G-X.S0004-691-E V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-691-E_v1.0.zip | + +#### 10.5.4.61 X.S0004-691-E Version 2.0 Annexes (September 2005) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0004-691-E V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-691-E_v2.0.zip | + +#### 10.5.4.62 X.S0004-691-E Version 3.0 Mobile Application Part (MAP) Annexes for the 6XX Series (July 2007) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E v3.0 | 3.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0004-691-E V3.0 | 3.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-691-E_v3.0.zip | + +#### 10.5.4.63 X.S0004-700-E Version 1.0.0 Wireless Intelligent Networks (March 2004) + +This document part of *TIA-41* defines the distributed functional plane (DFP) for the Wireless Intelligent Network (WIN). + +Specifically, the scope of this part of the Standard is: + +- 1) To define the WIN functional entities and the relationships applicable to WIN. +- 2) To specify a high level model description of call control function (CCF) activities required to establish and maintain communication paths for users. +- 3) To specify a high level model description of service switching function (SSF) activities required for interaction between the CCF and a service control function (SCF). +- 4) To specify WIN triggers and provide a high level model description of detection point processing. +- 5) To describe mobility management and radio access control functions in the context of WIN. +- 6) To illustrate how the WIN basic call state models interact with *TIA-41* signalling. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-700-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TIA | TIA-41.700-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-700-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0004-700-E_v1.0.0.zip | + +#### 10.5.4.64 X.S0004-730-E Version 1.0.0 WIN Distributed Functional Model (March 2004) + +This document depicts the functional entities and relationships applicable to WIN. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-730-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.730-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-730-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-730-E_v1.0.0.zip | + +#### 10.5.4.65 X.S0004-750-E Version 1.0.0 SSF/CCF Call and Service Logic Model (March 2004) + +This document describes WIN call and service logic processing in terms of call modelling and modelling of service logic processing. WIN call and service logic encompasses call and connection processing in the SSF/CCF, service logic execution in the SCF, and the use of supporting resources and data in the SRF and SDF, respectively. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-750-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.750-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-750-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-750-E_v1.0.0.zip | + +#### 10.5.4.66 X.S0004-790-E Version 1.0 WIN Call Delivery (March 2004) + +This document annex describes how MS-to-MS call delivery can be modelled using the WIN Basic Call State Models (BCSMs). The message sequences shown in the annex are as in TIA-41. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-790-E V1.0.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.790-E | | Published | --04-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0004-790-E V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0004-790-E_v1.0.0.zip | + +#### 10.5.5 X.S0006-0 Version 1.0 Map Support of Authentication and Key Agreement (AKA) (October 2005) + +Enhanced Subscriber Authentication (ESA) uses 3GPP Authentication and Key Agreement (AKA) procedures for mutual authentication of the MS and the network in the serving system. The successful execution of AKA results in the establishment of a security association (i.e., a set of security data) between the MS and the serving system. This enables a set of security services to be provided (e.g., data integrity of a signalling message, signalling information element encryption, user data encryption). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0006-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-945 | | Published | --02-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0006-0 V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0006-0_v1.0.zip | +| TTC | TS-3GB-X.S0006-0V1.0 | 1.0 | Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0006-0v10.pdf | + +### 10.5.6 X.S0008-0 Version 1.0 Support for the Mobile Equipment Identity (MEID) (June) + +TIA-41 support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0008-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-928
TIA-928-1 | | Published
Published | --08-2004
--06-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0008-0 v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0_v1.0.zip | +| TTC | TS-3GB-X.S0008-0v1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v10.pdf | + +#### 10.5.6.1 X.S0008-0 Version 2.0 Map Support for the Mobile Equipment Identity (MEID) (October 2005) + +TIA-41 support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0008-0 | 2.0 | Published | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-928-2[E] | | Published | --01-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0008-0 v2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0_v2.0.zip | +| TTC | TS-3GB-X.S0008-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v20.pdf | + +#### 10.5.6.2 X.S0008-0 Version 3.0 Map Support for the Mobile Equipment Identity (MEID) (January 2009) + +TIA-41 support for the Mobile Equipment Identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-928-3[E] | | Published | --08-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTA.3G-X.S0008-0 V3.0 | 3.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0008-0_v3.0 | +| TTC | TS-3GB-X.S0008-0v3.0 | 3.0 | Published | 15-07-2009 | http://www.ttc.or.jp/document_list/free/3gpps2009/TS/TS-3GB-X.S0008-0v3.0.pdf | + +### 10.5.7 X.S0009-0 Version 1.0 Wireless Intelligent Network Support for Location Based Services (June 2004) + +The purpose of this document is to describe FAM, LBC, LBIS and ECR, and to specify the intersystem operations that enable a wireless system to provide these location-based services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0009-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-843 | | Published | --08-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0009-0 V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0009-0_v1.0.zip | +| TTC | TS-3GB-X.S0009-0V1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0009-0v10.pdf | + +### 10.5.8 X.S0010-A Version 1.0 Pre-Paid charging Enhancements for Circuit-Switched Data and Short Message Services (05 January 2004) + +This document describes the additions and modifications to *TIA/EIA/IS-826*, Wireless Intelligent Network Capabilities for Pre-Paid Charging, to support circuit-switched data and short message services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0010-A v1.0 | 1 | Published | 05-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-826-A | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0010-A V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0010-A_v1.0.zip | +| TTC | TS-3GB-X.S0010-AV1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0010-av10.pdf | + +### 10.5.9 X.S0011-001-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Introduction (August 2003) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-001-C v1.0.0 | 1 | Published | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-001-C V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-001-C_v1.0.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv100.pdf | + +### 10.5.9.1 X.S0011-001-C Version 2.0 cdma2000 Wireless IP Network Standard: Introduction (July 2005) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-001-C | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-835-C-1 | | Published | --08-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-001-C V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-001-C_v2.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv2.0 | 2.0 | Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv20.pdf | + +### 10.5.9.2 X.S0011-001-C Version 3.0 cdma2000 Wireless IP Network Standard: Introduction (October 2006) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-001-C v3.0 | 3.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C-2 [E] | | Published | --05-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-001-C V3.0 | 3.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C_v3.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv3.0 | 3.0 | Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv30.pdf | + +### 10.5.9.3 X.S0011-001-D Version 1.0 cdma2000 Wireless IP Network Standard: Introduction (February 2006) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-001-D v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-D | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-001-D V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-D_v1.0.zip | +| TTC | TS-3GB-X.S0011-001-Dv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-dv10.pdf | + +### 10.5.9.4 X.S0011-001-D Version 2.0 cdma2000 Wireless IP Network Standard: Introduction (November 2008) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0011-001-Dv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0011-001-Dv2.0 | +| TTC | TS-3GB-X.S0011-001-Dv2.0 | 2.0 | Published | 06-03-2009 | http://www.ttc.or.jp/document_list/free/3gpps2009/TS/TS-3GB-X.S0011-001-Dv2.0.pdf | + +### 10.5.9.5 X.S0011-001-E Version 1.0 cdma2000 Wireless IP Network Standard: Introduction (November 2009) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-835-E | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0011-001-Ev1.0 | 1.0 | Published | 19-20-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-ev10.pdf | + +### 10.5.9.6 X.S0011-002-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (August 2003) + +This chapter describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple Ipv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-002-C v1.0.0 | 1 | Published | --08-03 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-002-C V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-002-C_v1.0.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv100.pdf | + +### 10.5.9.7 X.S0011-002-C Version 2.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (July 2005) + +This chapter describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple Ipv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-002-C | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-835-C-1 | | Published | --08-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-002-C V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-002-C_v2.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv2.0 | 2.0 | Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv20.pdf | + +### 10.5.9.8 X.S0011-002-C Version 3.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (October 2006) + +This chapter describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-002-C v3.0 | 3.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C-2 [E] | | Published | --05-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-002-C V3.0 | 3.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-002-C_v3.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv3.0 | 3.0 | Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv30.pdf | + +### 10.5.9.9 X.S0011-002-D Version 1.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (February 2006) + +This chapter describes the basic IP access services: Simple IPv4/IPv6, MIP6 and MIP4 with Home Agent (HA) and/or Dynamic Home IP address Assignment. It also addresses the security requirements between the Wireless IP Network nodes: PDSN, HA and RADIUS servers. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-002-D v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-D | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-002-D V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-002-D_v1.0.zip | +| TTC | TS-3GB-X.S0011-002-Dv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-dv10.pdf | + +### 10.5.9.10 X.S0011-002-D Version 2.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (November 2008) + +This chapter describes the basic IP access services: Simple IPv4/IPv6, MIP6 and MIP4 with Home Agent (HA) and/or Dynamic Home IP address Assignment. It also addresses the security requirements between the Wireless IP Network nodes: PDSN, HA and RADIUS servers. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0011-002-Dv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDownn.jsp?where=14688&pk_num=TTAT.3G-X.S0011-002-Dv2.0 | +| TTC | TS-3GB-X.S0011-002-Dv2.0 | 2.0 | Published | 06-03-2009 | http://www.ttc.or.jp/document_list/free/3gpps2009/TS/TS-3GB-X.S0011-002-Dv2.0.pdf | + +### 10.5.9.11 X.S0011-002-E Version 1.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (November 2009) + +This chapter describes the basic IP access services: Simple IPv4/IPv6, MIP6 and MIP4 with Home Agent (HA) and/or Dynamic Home IP address Assignment. It also addresses the security requirements between the Wireless IP Network nodes: PDSN, HA and RADIUS servers. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-835-E | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.Sp0011-002-Ev1.0 | 1.0 | Published | 19-02-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-ev10.pdf | + +### 10.5.9.12 X.S0011-003-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (August 2003) + +This chapter describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This chapter also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this chapter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-003-C v1.0.0 | 1 | Published | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-003-C V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-003-C_v1.0.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv100.pdf | + +### 10.5.9.13 X.S0011-003-C Version 2.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (July 2005) + +This chapter describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This chapter also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this chapter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-003-C | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-835-C-1 | | Published | --08-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-003-C V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-003-C_v2.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv2.0 | 2.0 | Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv20.pdf | + +#### 10.5.9.14 X.S0011-003-C Version 3.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (October 2006) + +This chapter describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This chapter also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this chapter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-003-C v3.0 | 3.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C-2 [E] | | Published | --05-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-003-C V3.0 | 3.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-003-C_v3.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv3.0 | 3.0 | Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv30.pdf | + +#### 10.5.9.15 X.S0011-003-D Version 1.0 cdma2000 Wireless IP Network Standard: Data Mobility and Resource Management (February 2006) + +This chapter describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This chapter also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this chapter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-003-D v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-D | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-003-D V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-003-D_v1.0.zip | +| TTC | TS-3GB-X.S0011-003-Dv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-dv10.pdf | + +#### 10.5.9.16 X.S0011-003-D Version 2.0 cdma2000 Wireless IP Network Standard: Data Mobility and Resource Management (November 2008) + +This chapter describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This chapter also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this chapter. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0011-003-Dv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown_jsp?where=14688&pk_num=TTAT.3G-X.S0011-003-Dv2.0 | +| TTC | TS-3GB-X.S0011-003-Dv2.0 | 2.0 | Published | 06-03-2009 | http://www.ttc.or.jp/i/document_list/free/3gpps2009/TS/TS-3GB-X.S0011-003-Dv2.0.pdf | + +#### 10.5.9.17 X.S0011-003-E Version 1.0 cdma2000 Wireless IP Network Standard: Data Mobility and Resource Management (November 2009) + +This chapter describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This chapter also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this chapter. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-835-E | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0011-003-Ev1.0 | 1.0 | Published | 19-02-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-ev10.pdf | + +#### 10.5.9.18 X.S0011-004-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (August 2003) + +This chapter describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-004-C V1.0.0 | 1 | Published | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-004-C V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0011-004-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv100.pdf | + +#### 10.5.9.19 X.S0011-004-C Version 2.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (July 2005) + +This chapter describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-004-C | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-835-C-1 | | Published | --08-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-004-C V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-004-C_v2.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv2.0 | 2.0 | Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv20.pdf | + +### 10.5.9.20 X.S0011-004-C Version 3.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (October 2006) + +This chapter describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-004-C v3.0 | 3.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C-2 [E] | | Published | --05-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-004-C V3.0 | 3.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-004-C_v3.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv3.0 | 3.0 | Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv30.pdf | + +### 10.5.9.21 X.S0011-004-D Version 1.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (February 2006) + +This chapter describes Flow Mapping/Treatment mechanisms and protocols used when more than one service connection is established between the MS and the PDSN. Furthermore, a signalling mechanism between the MS, the RAN, and the PDSN is presented in this chapter to support QoS on a per application flow basis. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20ms frames, such as VoIP application. This chapter also specifies the requirement and procedures for MS and PDSN to support SO type 67. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-004-D v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-D | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-004-D V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0011-004-D_v1.0.zip | +| TTC | TS-3GB-X.S0011-004-Dv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-dv10.pdf | + +### 10.5.9.22 X.S0011-004-D Version 2.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (November 2008) + +This chapter describes Flow Mapping/Treatment mechanisms and protocols used when more than one service connection is established between the MS and the PDSN. Furthermore, a signalling mechanism between the MS, the RAN, and the PDSN is presented in this chapter to support QoS on a per application flow basis. It also describes two optional Header Reduction techniques that are + +specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20ms frames, such as VoIP application. This chapter also specifies the requirement and procedures for MS and PDSN to support SO type 67. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0011-004-Dv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0011-004-Dv2.0 | +| TTC | TS-3GB-X.S0011-004-Dv2.0 | 2.0 | Published | 06-03-2009 | http://www.ttc.or.jp/j/document_list/free/3gpps2009/TS/TS-3GB-X.S0011-004-Dv2.0.pdf | + +### 10.5.9.23 X.S0011-004-E Version 1.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (November 2009) + +This chapter describes Flow Mapping/Treatment mechanisms and protocols used when more than one service connection is established between the MS and the PDSN. Furthermore, a signalling mechanism between the MS, the RAN, and the PDSN is presented in this chapter to support QoS on a per application flow basis. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20ms frames, such as VoIP application. This chapter also specifies the requirement and procedures for MS and PDSN to support SO type 67. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-835-E | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0011-004-Ev1.0 | 1.0 | Published | 19-20-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-ev10.pdf | + +### 10.5.9.24 X.S0011-005-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (August 2003) + +This chapter described the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S00011-011-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-005-C v1.0.0 | 1 | Published | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-005-C V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0011-005-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv100.pdf | + +### 10.5.9.25 X.S0011-005-C Version 2.0 cdma2000 wireless IP network standard: accounting services and 3GPP2 RADIUS VSAs (July 2005) + +This chapter describes the off-line accounting procedures and the usage data records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S00011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-005-C | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-835-C-1 | | Published | --08-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-005-C V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-005-C_v2.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv2.0 | 2.0 | Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv20.pdf | + +### **10.5.9.26 X.S0011-005-C Version 3.0 cdma2000 wireless IP network standard: accounting services and 3GPP2 RADIUS VSAs (October 2006)** + +This chapter describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S00011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-005-C v3.0 | 3.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C-2 [E] | | Published | --05-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-005-C V3.0 | 3.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-005-C_v3.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv3.0 | 3.0 | Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv30.pdf | + +### **10.5.9.27 X.S0011-005-D Version 1.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (February 2006)** + +This chapter describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of standards [Chapter 1-6]. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-005-D v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-D | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-005-D V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-005-D_v1.0.zip | +| TTC | TS-3GB-X.S0011-005-Dv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-dv10.pdf | + +### **10.5.9.28 X.S0011-005-D Version 2.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (November 2008)** + +This chapter describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of standards [Chapter 1-6]. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0011-005-Dv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDownn_jsp?where=14688&pk_num=TTAT.3G-X.S0011-005-Dv2.0 | +| TTC | TS-3GB-X.S0011-005-Dv2.0 | 2.0 | Published | 06-03-2009 | http://www.ttc.or.jp/j/document_list/free/3gpps2009/TS/TS-3GB-X.S0011-005-Dv2.0.pdf | + +### 10.5.9.29 X.S0011-005-E Version 1.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (November 2009) + +This chapter describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of standards [Chapters 1-6]. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-835-E | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0011-005-Ev1.0 | 1.0 | Published | 12-02-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-ev10.pdf | + +### 10.5.9.30 X.S0011-006-C Version 1.0.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Service (August 2003) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-006-C V1.0.0 | 1 | Published | --08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | --08-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-006-C V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0011-006-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv100.pdf | + +### 10.5.9.31 X.S0011-006-C Version 2.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (July 2005) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-006-C | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-835-C-1 | | Published | --08-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-006-C V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-006-C_v2.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv2.0 | 2.0 | Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv20.pdf | + +### 10.5.9.32 X.S0011-006-C Version 3.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (October 2006) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 1. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-006-C v3.0 | 3.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C-2 [E] | | Published | --05-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-006-C V3.0 | 3.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-006-C_v3.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv3.0 | 3.0 | Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv30.pdf | + +### 10.5.9.33 X.S0011-006-D Version 1.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (February 2006) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-006-D v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-D | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0011-006-D V1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0011-006-D_v1.0.zip | +| TTC | TS-3GB-X.S0011-006-Dv1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-dv10.pdf | + +### 10.5.9.34 X.S0011-006-D Version 2.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (November 2008) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0011-006-Dv2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0011-006-Dv2.0 | +| TTC | TS-3GB-X.S0011-006-Dv2.0 | 2.0 | Published | 06-03-2009 | http://www.ttc.or.jp/j/document_list/free/3gpps2009/TS/TS-3GB-X.S0011-006-Dv2.0.pdf | + +### 10.5.9.35 X.S0011-006-E Version 1.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (November 2009) + +Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-835-D | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0011-006-Ev1.0 | 1.0 | Published | 19-02-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-ev10.pdf | + +### 10.5.10 X.S0012-0 Version 2.0 Legacy MS Domain Step 1 (March 2004) + +This recommendation supports the 3GPP2 All-IP Step 1 Evolution Path by providing stage-1, 2 and 3 for the architecture identified. The Legacy MS Domain provides support for existing MSs in an IP core network environment. The Legacy MS Domain supports the features and capabilities provided in a legacy network in a manner transparent to the user. New features and capabilities supported by the IP core network may be made available to subscribers where they are supported by MS capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0012-0 v2.0 | 1 | Published | --03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/O.1742 | +| TIA | TIA-872-A | | Published | --05-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0012-0 V2.0 | 2.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0012-0_v2.0.zip | +| TTC | TS-3GB-X.S0012-0v2.0 | 2.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0012-0v20.pdf | + +### 10.5.11 X.S0013-000-0 Version 1.0 All-IP Core Network Multimedia Domain Overview (December 2003) + +This document contains the introduction of the stage-1, stage-2, and stage-3 recommendations for the 3GPP2 All-IP Multimedia Domain. It includes an overview of the system elements and interfaces and lists the series of documents that provide the complete specifications for the core network portions of the MMD. Not all MMD entities and interfaces may be covered by this version of this series of specifications. The specific entities and interfaces covered by a particular version are identified in each of the individual specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.000 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-000-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-000-0_v1.0.zip | +| TTC | TS-3GB-X.S0013-000-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v10.pdf | + +### 10.5.11.1 X.S0013-000-0 Version 2.0 All-IP Core Network Multimedia Domain Overview (July 2005) + +The Multimedia Domain (MMD) is a CDMA based wireless network providing 3rd generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.000-1[E] | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-000-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-000-0_v2.0.zip | +| TTC | TS-3GB-X.S0013-000-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v20.pdf | + +### 10.5.11.2 X.S0013-000-A Version 1.0 All-IP Core Network Multimedia Domain Overview (November 2005) + +The Multimedia Domain (MMD) is a collection of core network entities providing 3rd generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.000-A | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-000-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-000-A_v1.0.zip | +| TTC | TS-3GB-X.S0013-000-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0013-000-Av1.0.pdf | + +### 10.5.11.3 X.S0013-000-B Version 1.0 All-IP Core Network Multimedia Domain Overview (December 2007) + +This document contains the introduction of the stage-1, stage-2 and stage-3 recommendations for the Multimedia Domain + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.000-B | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-000-BV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-000-B_v1.0 | + +### 10.5.11.4 X.S0013-002-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (December 2003) + +This document defines stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services in PLMNs and perhaps other networks. This document identifies the mechanisms to enable support for IP multimedia applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-002-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.002 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-002-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-002-0_v1.0.zip | +| TTC | TS-3GB-X.S0013-002-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-002-0v10.pdf | + +### 10.5.11.5 X.S0013-002-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (November 2005) + +This document defines stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. Recommendation ITU-T I.130 describes a three-stage method for characterisation of telecommunication services, and Recommendation ITU-T Q.65 defines stage 2 of the method. This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-IMS IP applications, the general approach is to adopt non-IMS specific IP based solutions. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-002-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.002-A | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-002-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-A v1.0.zip | +| TTC | TS-3GB-X.S0013-002-A V1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0013-002-Av1.0.pdf | + +#### 10.5.11.6 X.S0013-002-B Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (December 2007) + +This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.002-B | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-002-B V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-002-B v1.0 | + +#### 10.5.11.7 X.S0013-003-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (December 2003) + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.003 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-003-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-003-0 v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v10.pdf | + +#### 10.5.11.8 X.S0013-003-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (July 2005) + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.003-1[E] | | Published | --05-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-003-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-003-0 v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v20.pdf | + +### **10.5.11.9 X.S0013-003-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (November 2005)** + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.003-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-003-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0013-003-A_v1.0.zip | +| TTC | TS-3GB-X.S0013-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0013-003-Av1.0.pdf | + +### **10.5.11.10 X.S0013-003-B Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (December 2007)** + +This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.003-B | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-003-BV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-003-B_v1.0 | + +### **10.5.11.11 X.S0013-004-0 Version 1.0 All-IP core network multimedia domain IP multimedia call control protocol based on SIP and SDP stage 3 (December 2003)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.004 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-004-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0013-004-0_v1.0.zip | +| TTC | TS-3GB-X.S0013-004-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v10.pdf | + +### **10.5.11.12 X.S0013-004-0 Version 2.0 All-IP core network multimedia domain IP multimedia call control protocol based on SIP and SDP stage 3 (July 2005)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | A-TSD-MC-X.S0013-004-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.004-1[E] | | Published | --06-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-004-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-004-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v20.pdf | + +### **10.5.11.13 X.S0013-004-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (November 2005)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.004-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-004-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-A v1.0.zip | +| TTC | TS-3GB-X.S0013-004-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0013-004-Av1.0.pdf | + +### **10.5.11.14 X.S0013-004-B Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (December 2007)** + +This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.004-B | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-004-BV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-004-B v1.0 | + +### **10.5.11.15 X.S0013-005-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signalling flows and Message Contents (December 2003)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.005 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-005-0V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-005-0v1.0.zip | +| TTC | TS-3GB-X.S0013-005-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v10.pdf | + +### **10.5.11.16 X.S0013-005-0 Version 2.0 All-IP core network multimedia domain IP multimedia subsystem Cx interface signalling flows and message contents (July 2005)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.005-1[E] | | Published | --06-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-005-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-005-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-005-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v20.pdf | + +### **10.5.11.17 X.S0013-005-A Version 1.0 All-IP core network multimedia domain IP multimedia subsystem Cx interface signalling flows and message contents (November 2005)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.005-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-005-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-005-A v1.0.zip | +| TTC | TS-3GB-X.S0013-005-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0013-005-Av1.0.pdf | + +### **10.5.11.18 X.S0013-005-B Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signalling flows and Message Contents (December 2007)** + +This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.005-B | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-005-BV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-005-Bv1.0 | + +### 10.5.11.19 X.S0013-006-0 Version 1.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (December 2003) + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/O.1742 | +| TIA | TIA-873.006 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-006-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0013-006-0_v1.0.zip | +| TTC | TS-3GB-X.S0013-006-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v10.pdf | + +### 10.5.11.20 X.S0013-006-0 Version 2.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (July 2005) + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/O.1742/Q.1742 | +| TIA | TIA-873.006-1[E] | | Published | --06-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-006-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0013-006-0_v2.0.zip | +| TTC | TS-3GB-X.S0013-006-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v20.pdf | + +### 10.5.11.21 X.S0013-006-A Version 1.0 All-IP core network multimedia domain Cx interface based on the diameter protocol; protocol details (November 2005) + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to: The Cx interface between the I-CSCF/S-CSCF and the HSS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/O.1742/Q.1742 | +| TIA | TIA873-A SERIES | | Published | | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-006-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0013-006-A_v1.0.zip | +| TTC | TS-3GB-X.S0013-006-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0013-006-Av1.0.pdf | + +### 10.5.11.22 X.S0013-006-B Version 1.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (December 2007) + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to: The Cx interface between the I-CSCF/S-CSCF and the HSS. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.006-B | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-006-BV1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-006-Bv1.0 | + +### 10.5.11.23 X.S0013-007-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Charging Architecture (December 2003) + +This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of the present document are: to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-007-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.007 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-007-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0013-007-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-007-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-007-0v10.pdf | + +### 10.5.11.24 X.S0013-007-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Charging Architecture (November 2005) + +This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of the present document are: to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-007-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.007-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-007-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0013-007-A v1.0.zip | +| TTC | TS-3GB-X.S0013-007-Av1.0 | 1.0 | Published | 02-06-2006 | TS/TS-3GB-X.S0013-007-Av1.0.pdf | + +**10.5.11.25 X.S0013-008-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Accounting Information Flows and Protocol (December 2003)** + +This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.008 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-008-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-008-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v10.pdf | + +**10.5.11.26 X.S0013-008-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Accounting Information Flows and Protocol (July 2005)** + +This document covers offline charging for the IMS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.008-1[E] | | Published | --07-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-008-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-008-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v20.pdf | + +**10.5.11.27 X.S0013-008-A Version 1.0 All-IP Core Network Multimedia Domain Offline Accounting Information Flows and Protocols (November 2005)** + +This document covers offline charging for the IMS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TIA | TIA-873.008-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-008-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-A v1.0.zip | +| TTC | TS-3GB-X.S0013-008-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0013-008-Av1.0.pdf | + +**10.5.11.28 X.S0013-009-0 Version 1.0 IMS/MMD Call Flow Examples (December 2007)** + +The document provides examples of signaling flows for the IP multimedia call control based on SIP and SDP. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.009 | 1.0 | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-009-0V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-009-0 v1.0 | + +**10.5.11.29 X.S0013-010-0 Version 1.0 All-IP core network multimedia domain IP multimedia subsystem Sh interface; signalling flows and message contents – Stage 2 (December 2003)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.010 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-010-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-010-0_v1.0.zip | +| TTC | TS-3GB-X.S0013-010-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v10.pdf | + +**10.5.11.30 X.S0013-010-0 Version 2.0 All-IP core network multimedia domain IP multimedia subsystem Sh interface; signalling flows and message contents – Stage 2 (July 2005)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-873.010-1[E] | | Published | --07-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-010-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-010-0_v2.0.zip | +| TTC | TS-3GB-X.S0013-010-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v20.pdf | + +**10.5.11.31 X.S0013-010-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signalling flows and message contents – Stage 2 (November 2005)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-873.010-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-010-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0013-010-A_v1.0.zip | +| TTC | TS-3GB-X.S0013-010-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0013-010-Av1.0.pdf | + +**10.5.11.32 X.S0013-010-B Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signalling flows and message contents – Stage 2 (December 2007)** + +This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873-B SERIES | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-010-B V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-010-Bv1.0 | + +**10.5.11.33 X.S0013-011-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (December 2003)** + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between as SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-0 v1.0 | 1 | Published | --12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.011 | | Published | --12-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-011-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-011-0v1.0 | 1.0 | Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v10.pdf | + +**10.5.11.34 X.S0013-011-0 Version 2.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (July 2005)** + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between as SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-0 | 2.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-873.011-1[E] | | Published | --07-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-011-0 V2.0 | 2.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-011-0v2.0 | 2.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v20.pdf | + +**10.5.11.35 X.S0013-011-A Version 1.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (November 2005)** + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between as SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-A | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-873.011-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-011-A V1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-A v1.0.zip | +| TTC | TS-3GB-X.S0013-011-Av1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0013-011-Av1.0.pdf | + +### 10.5.11.36 X.S0013-011-B Version 1.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (December 2009) + +This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873-B SERIES | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-011-B V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-011-B v1.0 | + +### 10.5.11.37 X.S0013-012-0 Version 1.0 All-IP Core Network Multimedia Domain Service Based Bearer Control – Stage 2 (December 2007) + +This specification addresses the linkage between session control and bearer level resource control mechanisms. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.012 | 1.0 | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-012-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-012-0 v1.0 | + +### 10.5.11.38 X.S0013-013-0 Version 1.0 All-IP Core Network Multimedia Domain Service Based Bearer Control Tx Interface – Stage 3 (December 2007) + +This document addresses the stage-3 protocol between an Application Function (AF) and a Policy and Charging Rules Function (PCRF) in support of Service Based Bearer Control. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.013 | 1.0 | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-013-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-013-0 v1.0 | + +### 10.5.11.39 X.S0013-014-0 Version 1.0 All-IP Core Network Multimedia Domain Service Based Bearer Control Ty Interface – Stage 3 (December 2007) + +This document addresses the stage-3 protocol between an Access Gateway (AGW) and a Policy and Charging Rules Function (PCRF) in support of Service Based Bearer Control as described in [X.S0013-012]. The reference point between the AGW and the PCRF is designated as the Ty reference point and supports all cdma2000® radio technologies. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0013-014-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-014-0v1.0 | + +#### **10.5.11.40 X.S0013-016-0 Version 1.0 All-IP Core Network Multimedia Domain Messaging Service Using the IP Multimedia Subsystem (December 2007)** + +The present document provides the protocol details for the messaging service within the IP Multimedia Subsystem (IMS) based on the Session Initiation Protocol (SIP), the Session Description Protocol (SDP) and, the Message Session Relay Protocol (MSRP). + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-873.016 | 1.0 | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0013-016-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0013-016-0v1.0 | + +#### **10.5.12 X.S0014-E Version 1.0 Wireless Radio Telecommunication Intersystem Non-Signalling Data Communication DMH (Data Message Handler) (December 2004)** + +This document describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0014-E | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-124E | | Published | --05-2005 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0014-E V1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0014-E v1.0.zip | +| TTC | TS-3GB-X.S0014-Ev1.0 | 1.0 | Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0014-ev10.pdf | + +#### **10.5.12.1 X.S0014-E Version 2.0 Wireless Radio Telecommunication Intersystem Non-Signalling Data Communication DMH (Data Message Handler) (August 2006)** + +This document describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0014-E v2.0 | 2.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | ANSI TIA-124E | | Published | --12-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0014-E V2.0 | 2.0 | Published | 15-02-2007 | http://www.tta.or.kr/stan_X.S0014-E v2.0.zip
dardDB/stnfile/TTAT.3G-X.S0014-E v2.0.zip | +| TTC | TS-3GB-X.S0014-Ev2.0 | 2.0 | Published | 01-12-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0014-ev20.pdf | + +### 10.5.13 X.S0016-000-A Version 1.0 3GPP2 Multimedia Messaging System MMS Specification Overview, Revision A (May 2003) + +This document describes the Multimedia Messaging System (MMS) specification documents for 3GPP2. It provides references to the stage 1 (Requirements), stage 2 (Functional Description), and one or more stage 3 (Technical Realization) documents that collectively represent the MMS specification for 3GPP2 systems. The Multimedia Messaging System is distributed within many documents, with a simple multi-level hierarchy. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-000-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-000-A V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0016-000-A v1.0.zip | +| TTC | TS-3GB-X.S0016.000-Av1.0.0 | 1.0 | Published | 28-11-2003 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016.000-Av1.0.0.pdf | + +### 10.5.13.1 X.S0016-000-B Version 1.0 3GPP2 Multimedia Messaging System MMS Specification Overview, Revision B (June 2004) + +This document describes the Multimedia Messaging System (MMS) specification documents for 3GPP2. It provides references to the stage 1 (Requirements), stage 2 (Functional Description), and one or more stage 3 (Technical Realization) documents that collectively represent the MMS specification for 3GPP2 systems. The Multimedia Messaging System is distributed within many documents, with a simple multi-level hierarchy. The purpose of this section is to introduce the readers to the contents of the whole document. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-000-B v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-000-B V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0016-000-B v1.0.zip | +| TTC | TS-3GB-X.S0016-000-Bv1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016-000-Bv1.0.pdf | + +### 10.5.13.2 X.S0016-000-C Version 1.0 Multimedia Messaging Service – Overview (January 2006) + +This document describes the Multimedia Messaging System (MMS) specification documents for 3GPP2. It provides references to the stage 1 (Requirements), stage 2 (Functional Description), and one or more stage 3 (Technical Realization) documents that collectively represent the MMS specification for 3GPP2 systems. The Multimedia Messaging System is distributed within many documents, with a simple multi-level hierarchy. The purpose of this section is to introduce the readers to the contents of the whole document. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-000-C v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-000-C V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0016-000-C v1.0.zip | + +### 10.5.13.3 X.S0016-101-0 Version 1.0 Multimedia Messaging Service – MM10 Interface Based on Diameter Protocol – Stage 3 (January 2006) + +This document defines the procedures and transport protocol for use in the Multimedia Messaging Service (MMS) based on Diameter. The present document is applicable to the MM10 interface between an MMS Relay/Server and the MSCF. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-101-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-101-0 V1. | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-101-0 v1.0.zip | + +#### **10.5.13.4 X.S0016-102-0 Version 1.0 Multimedia Messaging Service – MM10 Interface Based on RADIUS Protocol – Stage 3 (January 2006)** + +This document defines the procedures and transport protocol for use in the Multimedia Messaging Service (MMS) based on Diameter. The present document is applicable to the MM10 interface between an MMS Relay/Server and the MSCF. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-102-0 v1. | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-102-0 V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-102-0 v1.0.zip | + +#### **10.5.13.5 X.S0016-200-0 Version 1.0 MMS Stage 2 Functional Description ( 03 April 2003)** + +The present document defines the stage 2 description of the non-real-time Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +The present document contains the core functions for a non-real-time Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-200-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-200 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-200-0 V1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-200-0 v1.0.zip | + +#### **10.5.13.6 X.S0016-200-0 Version 2.0 MMS Stage 2 Functional Description (June 2004)** + +The present document defines the stage 2 description of the non-real-time Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +The present document contains the core functions for a non-real-time Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-200-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-200-0 V1.0 | 2.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-200-0 v1.0.zip | + +### 10.5.13.7 X.S0016-200-A Version 1.0 Multimedia Messaging Service – Stage 2 Functional Description (January 2006) + +The present document defines the stage 2 description of the non-real-time Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +The present document contains the core functions for a non-real-time Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-200-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-200-A V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0016-200-A_v1.0.zip | + +### 10.5.13.8 X.S0016-310-0 Version 1.0 MMS MM1 Stage 3 Using OMA/WAP (03 April 2003) + +This document defines the stage 3 description of the non-real-time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and server and device manufacturers. The document contains the core protocol and formats for interoperability between a device client and an MMS Relay/Server. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-310-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-310 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-310-0 V1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0016-310-0_v1.0.zip | + +### 10.5.13.9 X.S0016-310-0 Version 2.0 MMS MM1 Stage 3 Using OMA/WAP (June 2004) + +This document defines the stage 3 description of the non-real-time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and server and device manufacturers. The document contains the core protocol and formats for interoperability between a device client and an MMS Relay/Server. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-310-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-310-A | 1 | Published | --09-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-310-0 V2.0 | 2.0 | Published | 15-11-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0016-310-0_v2.0.zip | + +### 10.5.13.10 X.S0016-311-0 Version 1.0 MMS MM1 Stage 3 Using M-IMAP for Message Submission and Retrieval (14 April 2003) + +This specification defines a technical realization of the MMS MM1 interface for Message Submission and Message Retrieval. The methods defined within this document are independent of and may be used with any particular delivery notification method, as section 3.9 explains. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-311-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-311 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-311-0 V1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0016-311-0 v1.0 | + +#### 10.5.13.11 X.S0016-312-0 Version 1.0 MMS MM1 Stage 3 Using SIP (June 2004) + +This specification defines a technical realization of the MMS MM1 interface for Message Submission, Message Notification, Message Acknowledgement, Message Retrieval, Message Delivery Reporting and Message Read Reporting. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-312-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-312 | 0 | Published | --04-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-312-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-312-0 v1.0.zip | + +#### 10.5.13.12 X.S0016-330-0 Version 1.0 MMS MM1 Stage 3 for Internet Mail Exchange (June 2004) + +This specification describes how to use MM3 to exchange messages with Internet mail systems. This includes translation between MMS and Internet Mail messages using Extended Simple Mail Transfer Protocol [SMTP] and Internet mail format [Msg-Fmt]. This protocol is a stage 3 on reference point MM3 to exchange messages with systems in Internet Message format. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-330-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-330 | 0 | Published | --03-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-330-0 V1.0 | 1.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-330-0 v1.0.zip | + +#### 10.5.13.13 X.S0016-330-A Version 1.0 Multimedia Messaging Service – MM3 Stage 3 for Internet Mail Exchange (January 2006) + +This specification describes how to use MM3 to exchange messages with Internet mail systems. This includes translation between MMS and Internet Mail messages using Extended Simple Mail Transfer Protocol [SMTP] and Internet mail format [Msg-Fmt]. This protocol is a stage 3 on reference point MM3 to exchange messages with systems in Internet Message format. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-330-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-330-A V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0016-330-A v1.0.zip | + +### **10.5.13.14 X.S0016-340-0 Version 1.0 MMS MM4 Stage 3 for Intercarrier Interworking (03 April 2003)** + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and switch and database manufacturers. The present document contains the core protocol and formats for interworking between network operators in support of Multimedia Messaging Services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-340-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-340 | 0 | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-340-0 V1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-340-0_v1.0.zip | +| TTC | TS-3GB-X.S0016.340-0v1.0.0 | 1.0 | Published | 28-11-2003 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016.340-0v1.0.0.pdf | + +### **10.5.13.15 X.S0016-340-0 Version 2.0 MMS MM4 Stage 3 for intercarrier interworking (June 2004)** + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and switch and database manufacturers. The present document contains the core protocol and formats for interworking between network operators in support of Multimedia Messaging Services. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-340-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-340-0 V2.0 | 2.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-340-0_v2.0.zip | +| TTC | TS-3GB-X.S0016-340-0v2.0 | 2.0 | Published | 03-09-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016-340-0v2.0.pdf | + +### **10.5.13.16 X.S0016-340-A Version 1.0 Multimedia Messaging Service – MM4 Stage 3 Inter-carrier Interworking (January 2006)** + +This document defines the stage 3 description of the non-real time Multimedia Messaging Service, MMS. Stage 3 identifies the protocols and formats needed to support the functional capabilities and information flows described in stage 2. + +This document includes information applicable to network operators, service providers and switch and database manufacturers. The present document contains the core protocol and formats for interworking between network operators in support of Multimedia Messaging Services + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-340-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-340-A V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-340-A_v1.0.zip | + +### **10.5.13.17 X.S0016-370-0 Version 1.0 MMSS MM7 VASP Interworking Stage 3 Specification (03 April 2003)** + +This document describes the technical realization (stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-370-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-934-370 | | Published | --05-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0016-370-0 V1.0 | 1.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-370-0 v1.0.zip | +| TTC | TS-3GB-X.S0016.370-0v1.0.0 | 1.0 | Published | 28-11-2003 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016.370-0v1.0.0.pdf | + +### **10.5.13.18 X.S0016-370-0 Version 2.0 MMSS MM7 VASP Interworking Stage 3 Specification (June 2004)** + +This document describes the technical realization (stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-370-0 v2.0 | 2.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-370-0 V2.0 | 2.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-370-0 v2.0.zip | +| TTC | TS-3GB-X.S0016-370-0v2.0 | 2.0 | Published | 03-09-2004 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0016-370-0v2.0.pdf | + +### **10.5.13.19 X.S0016-370-A Version 1.0 Multimedia Messaging Service – MM7 VASP Interworking Stage 3 (January 2006)** + +This document describes the technical realization (stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0016-370-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0016-370-A V1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0016-370-A v1.0.zip | + +### **10.5.14 X.S0017 Version 1.0.0 Open Service Access (OSA) Application Programming Interface (API) OSA API Revision: 0 (June 2003)** + +This document is intended to define the OSA API stage 3 interface definitions and it provides the complete OSA specifications for cdma2000-based systems. This document is an extension of OSA API, per latest 3GPP TS 29.198 series specifications capabilities to enable operation in cdma2000 systems environment as part of the TTA/EIA/IS-2000 family of standards. The information given here is to be used by developers in 3GPP2 cdma2000 network architecture to the 3GPP OSA Specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0017 v1.0.0 | 1 | Published | --06-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-937 | | Published | --06-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0017 V1.0.0 | 1.0.0 | Published | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0017_v1.0.0.zip | +| TTC | TS-3GB-X.S0017-0v1.0.0 | 1.0.0 | Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0017-0v100.pdf | + +### 10.5.15 X.S0018 Version 1.0.0 Legacy Mobile Station Domain (LMSD) Step 1 Revision: 0 (May 2003) + +This standard specifies the necessary interfaces to support the bearer traffic between Media Gateways in the initial step of the Legacy Mobile Station Domain (LMSD). The requirements for this work are defined in [6], and the overall architecture model is defined in [5]. This standard defines bearer support of G.711 PCM encoded voice over IP as defined in RFC1890 at a minimum, for use between media gateways in a cdma2000 Legacy Mobile Station Domain. This standard utilizes existing IETF and 3GPP2 protocols when applicable to minimize the new work needed. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0018-0 | 1.0.0 | Published | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA-930 | | Published | --01-2003 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0018_v1.0.0 | 1.0.0 | Published | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0018_v1.0.0.zip | +| TTC | TS-3GB-X.S0018-0v1.0.0 | 1.0 | Published | 28-11-2003 | http://www.ttc.or.jp/document_list/free/TS/TS-3GB-X.S0018-0v1.0.0.pdf | + +### 10.5.16 X.S0021-B Version 1.0 Roamer Database Verification (July 2004) + +The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0021-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TIA | TIA-847-B | | Published | --08-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0021-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0021-B_v1.0.zip | +| TTC | TS-3GB-X.S0021-Bv1.0 | 1.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0021-bv10.pdf | + +### 10.5.17 X.S0022-A Version 1.0 Broadcast and Multicast Service in cdma2000 Wireless IP Network Revision A (16 February 2007) + +The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0022-A v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1041-A | | Published | --10-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0022-A v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0022-A_v1.0.zip | +| TTC | TS-3GB-X.S0022-Av1.0 | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0022-Av1.0.pdf | + +### 10.5.18 X.S0023-B Version 1.0 Network Interworking Between GSM MAP and TIA-41 Map – cdma2000 Support (July 2004) + +The purpose for this standard is to define and describe the functions necessary for roaming between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers. 16 This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., a TDMA or 17 CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS 18 network in GSM Foreign Mode. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0023-B | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-5 | +| TIA | J-STD-038-B | | Published | --08-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0023-B v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0023-B_v1.0.zip | +| TTC | TS-3GB-X.S0023-Bv1.0 | 1.0 | Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0023-bv10.pdf | + +### 10.5.19 X.S0024-0 Version 1.0 IP Based Location Services (October 2005) + +The purpose of this document is to specify the intersystem operations that enable a wireless system to provide IP-Based location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0024-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1020 | 0 | Published | --01-2007 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0024-0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0024-0_v1.0.zip | + +### 10.5.20 X.S0025-0 Version 1.0 Legacy MS Domain Step 2 (February 2006) + +The Legacy MS Domain (LMSD) provides support for existing MSs in a network that supports IP bearers. This specification provides support for transport of compressed speech (e.g., 13K, SMV, EVRC, etc.) over IP bearers. All bearer features in the legacy network are supported. + +Additionally, this specification provides support for placing bearer signal processing transcoders in the Base Station (BS) and/or in the Media Gateway (MGW). Network capabilities that support minimizing the number of transcoders in the bearer path are also supported. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0025-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-1022 | | Published | --04-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0025-0 v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0025-0 v1.0.zip | +| TTC | TS-3GB-X.S0025-0v1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0025-0v10.pdf | + +### 10.5.21 X.S0027-000-0 Version 1.0 Presence Overview (September 2004) + +This document describes network aspects of the Presence Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0027-000-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1032.000 | | Published | --11-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0027-000-0 v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-000-0 v1.0.zip | +| TTC | TS-3GB-X.S0027-000-0v1.0 | 1.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-000-0v10.pdf | + +### 10.5.21.1 X.S0027-000-A Version 1.0 Presence Overview (February 2008) + +This document describes network aspects of the Presence Service. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1032.000-1 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0027-000-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0027-000-Av1.0 | +| TTC | TS-3GB-X.S0027-000-Av1.0 | 1.0 | Published | 12-06-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0027-000-Av1.0.pdf | + +### 10.5.21.2 X.S0027-001-0 Version 1.0 Presence Service: Architecture and Functional Description (September 2004) + +This document describes the stage 2 (architectural solution and functionalities) for the presence service, which includes the elements necessary to realize the stage 1 requirements + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0027-001-0 | 1.0 | Published | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1032-001 | | Published | --11-2004 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0027-001-0 v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-001-0 v1.0.zip | +| TTC | TS-3GB-X.S0027-001-0v1.0 | 1.0 | Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-001-0v10.pdf | + +### 10.5.21.3 X.S0027-002-0 Version 1.0 Presence Stage 3 (February 2008) + +This document describes the stage 2 security requirements, security architecture, security features and security mechanisms for the Presence Service. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1032.002 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0027-002-0 v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0027-002-0v1.0 | + +#### 10.5.21.4 X.S0027-003-0 Version 1.0 Presence Security (February 2008) + +This document provides the protocol details for the presence service within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events. + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1032.003 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0027-003-0 v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0027-003-0v1.0 | + +#### 10.5.21.5 X.S0027-004-0 Version 1.0 Network Presence (February 2008) + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1032.004 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0027-004-0 v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0027-004-0v1.0 | + +#### 10.5.22 X.S0028-000-0 Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – List of Parts (March 2007) + +This document describes the list of parts for WLAN interworking. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0028-000-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0028-000-0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0028-000-0v1.0.zip | +| TTC | TS-3GB-X.S0028-000-0v1.0 | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0028-000-0v1.0.pdf | + +#### 10.5.22.1 X.S0028-000-A Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – List of Parts (June 2008) + +This document describes the list of parts for WLAN interworking. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0028-000-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0028-000-Av1.0 | +| TTC | TS-3GB-X.S0028-000-Av1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0028-000-Av1.0.pdf | + +#### 10.5.22.2 X.S0028-100-0 Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – Access to Internet (March 2007) + +This document describes WLAN Interworking – Access to Internet , which includes the elements necessary to realize the stage 1 requirements + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0028-100-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0028-100-0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0028-100-0 v1.0.zip | +| TTC | TS-3GB-X.S0028-100-0v1.0 | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0028-100-0v1.0.pdf | + +### **10.5.22.3 X.S0028-200-0 Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – Access to Operator Service and Mobility (March 2007)** + +This document describes WLAN Interworking – Access to Operator Service and Mobility, which includes the elements necessary to realize the stage 1 requirements + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0028-200-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.S0028-200-0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0028-200-0 v1.0.zip | +| TTC | TS-3GB-X.S0028-200-0v1.0 | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0028-200-0v1.0.pdf | + +### **10.5.22.4 X.S0028-200-A Version 1.0 cdma2000 Packet Data Services: Wireless Local Area Network (WLAN) Interworking – Access to Operator Service and Mobility (June 2008)** + +This document describes WLAN Interworking – Access to Operator Service and Mobility, which includes the elements necessary to realize the stage 1 requirements + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0028-200-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0028-200-Av1.0 | +| TTC | TS-3GB-X.S0028-200-Av1.0 | 1.0 | Published | 05-09-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0028-200-Av1.0.pdf | + +### **10.5.23 X.S0029-0 Version 1.0 Conferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem Revision: 0 (May 2007)** + +This document provides the protocol details for conferencing within the IP Multimedia Core Network Subsystem (IMS) based on the Session Initiation Protocol (SIP), SIP Events and the Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0029-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1069 | | Published | --02-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0029-0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA.T.3G-X.S0029-0 v1.0.zip | +| TTC | TS-3GB-X.S0029-0v1.0 | 1.0 | Published | 07-09-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0029-0v1.0.pdf | + +### 10.5.24 X.S0030-0 Version 1.0 MAP Enhancements to Support Enhanced Message Waiting Notification (MWN) (September 2005) + +This document provides automatic roaming information flows that illustrate enhanced Message Waiting Count operation. This document also describes the signalling protocol and signalling procedure modifications needed for enhanced Message Waiting Count operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0030-0 | 1 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1055 | | Published | --03-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0030-0 v1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0030-0_v1.0.zip | +| TTC | TS-3GB-X.S0030-0v1.0 | 1.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0030-0v10.pdf | + +### 10.5.25 X.S0033-0 Version 1.0 OTA Support for MEID (October 2005) + +This document presents a recommended plan for the implementation of Over-The-Air (OTA) support for the Mobile Equipment Identity (MEID) + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0033-0 | 1.0 | Published | --01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1074 | | Published | --03-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0033-0 v1.0 | 1.0 | Published | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0033-0_v1.0.zip | +| TTC | TS-3GB-X.S0033-0v1.0 | 1.0 | Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0033-0v10.pdf | + +### 10.5.25.1 X.S0033-0 Version 2.0 OTA Support for MEID (February 2006) + +This document presents a recommended plan for the implementation of Over-The-Air (OTA) support for the Mobile Equipment Identity (MEID) + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0033-0 v2.0 | 2.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742 | +| TIA | TIA-1074-1 [E] | | Published | --03-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0033-0 v2.0 | 2.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.S0033-0_v2.0.zip | +| TTC | TS-3GB-X.S0033-0v2.0 | 2.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0033-0v20.pdf | + +### 10.5.26 X.S0034-0 Version 1.0 cdma2000/GPRS Roaming (September 2004) + +The scope of this document includes the roaming of a subscriber homed in a cdma2000 packet data system to a GPRS system and vice versa. The roaming between cdma2000 packet data systems is outside the scope of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0034-0 | 1.0 | Published | 09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1068 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0034-0 v1.0 | 1.0 | Published | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0034-0_v1.0.zip | +| TTC | TS-3GB-X.S0034-0v1.0 | 1.0 | Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0034-0v10.pdf | + +### 10.5.27 X.S0037-0 Version 1.0 Tunnelling Support in Simple IP (May 2006) + +The scope of this specification includes tunnelling support for the Simple IP packet data subscriber roaming across cdma2000 packet data systems that are administered by different service providers. In this specification, the tunnelling scheme is specified in the context of layer-two tunnelling. Other tunnelling schemes are not precluded. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0037-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-1092 | | Published | --10-2006 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0037-0 v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0037-0_v1.0.zip | +| TTC | TS-3GB-X.S0037-0v1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0037-0v10.pdf | + +### 10.5.28 X.R0039-0 Version 1.0 Packet Switched Voice (over IP) and Video Telephony Services End to End Design Technical Report (November 2005) + +This document describes the end-to-end protocols and procedures for support of Packet Switched 4 Video Telephony (PSVT) and Voice-Over-IP (VoIP) Services over cdma2000®1 networks. The 5 document describes the end-to-end PSVT and VoIP services and architectures. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.R0039-0 v1.0 | 1.0 | Published | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.R0039-0 v1.0 | 1.0 | Published | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.R0039-0_v1.0.zip | +| TTC | TS-3GB-X.R0039-0v1.0 | 1.0 | Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxr0039-0v10.pdf | + +### 10.5.29 X.S0040-0 Version 1.0 PPP- Alternative Protocol (AltPPP) for cdma2000 Wireless IP Network Standard (January 2007) + +This document defines the AltPPP protocol for packet data session setup for cdma2000 wireless IP networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0040-0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742-7/ | +| TIA | TIA-1100 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0040-0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T_3G-X.S0040-0_v1.0.zip | +| TTC | TS-3GB-X.S0040-0v1.0 | 1.0 | Published | 25-05-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0040-0v1.0.pdf | + +### 10.5.30 X.S0042-0 Version 1.0 Voice Call Continuity between IMS and Circuit Switched Systems (October 2007) + +Voice call continuity allows users to move voice calls between the Circuit-Switched (CS) domain and the Multimedia Domain (MMD), connected through different Internet Protocol – Connectivity Access Networks (IPCANs) (e.g., WLAN, HRPD). This document defines an inter-technology Domain Transfer (DT) call model which supports procedures that allow a mobile subscriber to DT from an HRPD or WLAN multimedia session with a voice component to a 1x CS voice session and from a 1x CS voice session to a WLAN VoIP session. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1093 | | Published | --07-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0042-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0042-0 v1.0 | +| TTC | TS-3GB-X.S0042-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-X.S0042-0v1.0.pdf | + +### 10.5.30.1 X.S0042-A Version 1.0 Voice Call Continuity between IMS and Circuit Switched Systems (August 2008) + +Voice call continuity allows users to move voice calls between the Circuit-Switched (CS) domain and the Multimedia Domain (MMD), connected through different Internet Protocol – Connectivity Access Networks (IPCANs) (e.g., WLAN, HRPD). This document defines an inter-technology Domain Transfer (DT) call model which supports procedures that allow a mobile subscriber to DT from an HRPD or WLAN multimedia session with a voice component to a 1x CS voice session and from a 1x CS voice session to a WLAN VoIP session. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0042-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0042-A v1.0 | +| TTC | TS-3GB-X.S0042-Av1.0 | 1.0 | Published | 28-11-2008 | http://www.ttc.or.jp/i/document_list/free/TS/TS-3GB-X.S0042-Av1.0.pdf | + +### 10.5.31 X.S0044-0 Version 1.0 Mobile IPv4 Enhancements (September 2010) + +This document provides additional functionality to the functionality specified in [2] and later versions. It supports the allocation of a Home Agent in a visited network when a user is operating in a network that is not its home network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0044-0 v1.0 | 1.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1116 | | Published | --11-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0044-0v1.0 | 1.0 | Published | 02-12-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0044-0v10.pdf | + +### 10.5.32 X.S0047-0 Version 1.0 Mobile IPv6 Enhancements (February 2009) + +This document defines enhancements to Mobile IPv6 (MIP6). The enhancements are in addition to the MIP6 related requirements specified in [1]. This document applies to both 1X and HRPD systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0047-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0047-0 v1.0 | + +### 10.5.33 X.S0048-0 Version 1.0 Short Message Service Over IMS (November 2007) + +The present document provides SMS over IMS procedures based upon [MMD Part-4] and [MMD Part-10]. The present document is applicable to Application Servers (ASs) and User Equipment (UEs) providing SMS over IMS functionality. It is the goal of this specification to allow the core network to know as closely as possible, the current accessibility of the UE and to deliver SMS efficiently across the appropriate access network while minimizing the impact on the legacy systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1109 | | Published | --04-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0048-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0048-0 v1.0 | +| TTC | TS-3GB-X.S0048-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0048-0v1.0.pdf | + +### 10.5.34 X.S0049-0 Version 1.0 All-IP Network Emergency Call Support (February 2008) + +This document defines the stage-2 service description and normative stage 3 procedures in Annex D for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services efficiently across the appropriate access network while minimizing the impact on the legacy systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1111 | | Published | --05-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0049-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0049-0 v1.0 | + +### 10.5.35 X.S0050-0 Version 1.0 Session Initiation Protocol (SIP) to ISDN User Part (ISUP) Interworking (January 2008) + +The present document provides SMS over IMS procedures based upon [MMD Part-4] and [MMD Part-10]. The present document is applicable to Application Servers (ASs) and User Equipment (UEs) providing SMS over IMS functionality. It is the goal of this specification to allow the core network to know as closely as possible, the current accessibility of the UE and to deliver SMS efficiently across the appropriate access network while minimizing the impact on the legacy systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1112 | | Published | --10-2008 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0050-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0050-0 v1.0 | +| TTC | TS-3GB-X.S0050-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0050-0v1.0.pdf | + +### 10.5.36 X.R0052-0 Version 1.0 All-IP System – MMD Roaming Technical Report (August 2007) + +This document contains example scenarios for mobiles which roam into a visited network that is different from their home network. It offers recommendations on how these roaming scenarios may be supported. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.R0052.0 v1.0 | 1.0 | Published | 25-11-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/Q.1742-7/ | +| TTA | TTAT.3G-X.R0052.0 v1.0 | 1.0 | Published | 24-12-2007 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-X.R0052.0_v1.0.zip | +| TTC | TS-3GB-X.R0052-0v1.0 | 1.0 | Published | 28-11-2007 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.R0052-0v1.0.pdf | + +### 10.5.37 X.S0053-0 Version 1.0 All-IP System – MMD Policy Enhancements (June 2008) + +This document describes a policy-based approach to resource management, interactions between network services and network resources, and interactions between network services themselves. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0053-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0053-0_v1.0 | + +### 10.5.38 X.S0054-000-0 Version 1.0 CAN Wireless IP Network Overview and List of Parts (December 2007) + +This document provides an overview of the series of documents used to specify the Converged Access Network (CAN). The CAN enables optimization and upgrade for packet data access network to support services to the customers. This document also describes the CAN Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0054-000v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-000-0_v1.0 | +| TTC | TS-3GB-X.S0054-000-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-000-0v1.0.pdf | + +### 10.5.38.1 X.S0054-000-0 Version 2.0 CAN Wireless IP Network Overview and List of Parts (August 2008) + +This document provides an overview of the series of documents used to specify the Converged Access Network (CAN). The CAN enables optimization and upgrade for packet data access network to support services to the customers. This document also describes the CAN Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.000-1 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-000-0v2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-000-0_v2.0 | +| TTC | TS-3GB-X.S0054-000-0v2.0 | 2.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-000-0v2.0.pdf | + +### 10.5.38.2 X.S0054-000-A Version 1.0 CAN Wireless IP Network Overview and List of Parts (August 2008) + +This document provides an overview of the series of documents used to specify the Converged Access Network (CAN). The CAN enables optimization and upgrade for packet data access network to support services to the customers. This document also describes the CAN Network Reference Model. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.000-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-000-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-000-Av1.0 | +| TTC | TS-3GB-X.S0054-000-Av1.0 | 1.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-000-Av1.0.pdf | + +### 10.5.38.3 X.S0054-100-0 Version 1.0 Basic IP Services for Converged Access Network Specification (December 2007) + +This document defines the stage-2 and stage-3 requirements for Simple IP access to the Converged Access Network supporting Ultra Mobile Broadband (UMB) 1 Wireless access. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0054-100-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-100-0v1.0 | +| TTC | TS-3GB-X.S0054-100-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-100-0v1.0.pdf | + +### 10.5.38.4 X.S0054-100-0 Version 2.0 Basic IP Services for Converged Access Network Specification (August 2008) + +This document defines the stage-2 and stage-3 requirements for Simple IP access to the Converged Access Network supporting Ultra Mobile Broadband (UMB) 1 Wireless access. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.100-1 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-100-0v2.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-100-0v2.0 | +| TTC | TS-3GB-X.S0054-100-0v2.0 | 2.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-100-0v2.0.pdf | + +### 10.5.38.5 X.S0054-102-0 Version 1.0 Multiple Authentication and 2G-RUIM Support for Converged Access Network (December 2007) + +This document describes stage 2 and stage 3 specification details for Multiple-Authentication and 2G R-UIIM support for UMB. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.102 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-102-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-102-0v1.0 | +| TTC | TS-3GB-X.S0054-102-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-102-0v1.0.pdf | + +### 10.5.38.6 X.S0054-102-0 Version 2.0 Multiple Authentication and 2G-RUIM Support for Converged Access Network (August 2008) + +This document describes stage 2 and stage 3 specification details for Multiple-Authentication and 2G R-UIIM support for UMB. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.102-1 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-102-0v2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-102-0v2.0 | +| TTC | TS-3GB-X.S0054-102-0v2.0 | 2.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-102-0v2.0.pdf | + +### 10.5.38.7 X.S0054-110-0 Version 1.0 MIPv4 Specification in Converged Access Network Specification (December 2007) + +This document defines the stage-2 and stage-3 requirements for client based Mobile IPv4 access to the Converged Access Network supporting Ultra Mobile Broadband radio access. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.110 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-110-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-110-0v1.0 | +| TTC | TS-3GB-X.S0054-110-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-110-0v1.0.pdf | + +### 10.5.38.8 X.S0054-110-0 Version 2.0 MIPv4 Specification in Converged Access Network Specification (December 2007) + +This document defines the stage-2 and stage-3 requirements for client based Mobile IPv4 access to the Converged Access Network supporting Ultra Mobile Broadband radio access. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.110-1 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-110-0v2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-110-0v2.0 | +| TTC | TS-3GB-X.S0054-110-0v2.0 | 2.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-110-0v2.0.pdf | + +### 10.5.38.9 X.S0054-210-0 Version 1.0 CMIP Based Inter-AGW Handoff (December 2007) + +This document describes inter-AGW handoff operation using Mobile IP (e.g., the AT implements MIP client functionality, called CMIP) for layer 3 mobility, for both active and idle handoffs. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.210 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-210-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-210-0v1.0 | +| TTC | TS-3GB-X.S0054-210-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-210-0v1.0.pdf | + +### 10.5.38.10 X.S0054-220-0 Version 1.0 PMIP Support between AGW and LMA (December 2007) + +This document defines the stage-2 and stage-3 requirements for supporting PMIP between AGW and HA. This document describes PMIP based Simple IP address assignment and PMIP based inter-AGW handoff. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.220 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0054-220-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-220-0v1.0.pdf | + +### 10.5.38.11 X.S0054-220-0 Version 2.0 PMIP Support between AGW and LMA (August 2008) + +This document defines the stage-2 and stage-3 requirements for supporting PMIP between AGW and HA. This document describes PMIP based Simple IP address assignment and PMIP based inter-AGW handoff. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.220-1 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-220-0v2.0 | 2.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-220-0v2.0 | +| TTC | TS-3GB-X.S0054-220-0v2.0 | 2.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-220-0v2.0.pdf | + +### 10.5.38.12 X.S0054-220-A Version 1.0 PMIP Support between AGW and LMA (August 2008) + +This document defines the stage-2 and stage-3 requirements for supporting PMIP between AGW and HA. This document describes PMIP based Simple IP address assignment and PMIP based inter-AGW handoff. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.220-A | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-220-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-220-Av1.0 | +| TTC | TS-3GB-X.S0054-220-Av1.0 | 1.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-220-Av1.0.pdf | + +### 10.5.38.13 X.S0054-300-0 Version 1.0 QoS Support for Converged Access Network Specification (December 2007) + +This document defines the stage-3 requirements for QoS support in the Converged Access Network (CAN). + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0054-300-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-300-0v1.0 | +| TTC | TS-3GB-X.S0054-300-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-300-0v1.0.pdf | +| TIA | TIA-1137.300 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### **10.5.38.14 X.S0054-400-0 Version 1.0 Converged Access Network Accounting Specification (December 2007)** + +This document defines offline accounting functionality in the CAN. It describes the functional responsibilities of the network elements including the accounting data to be collected by certain elements in the CAN architecture. It describes the protocol messages and message contents that are exchanged between eBSs in an AT's Route Set and the AGW, and between the AGW and the accounting server. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0054-400-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-400-0v1.0 | +| TTC | TS-3GB-X.S0054-400-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-400-0v1.0.pdf | +| TIA | TIA-1137.400 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### **10.5.38.15 X.S0054-610-0 Version 1.0 UMB and HRPD/1x Interworking (August 2008)** + +This document defines the stage-2 and stage-3 requirements for interworking between Ultra Mobile Broadband (UMB) Wireless access and HRPD/1x Wireless access in the Converged Access Network. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0054-610-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-610-0v1.0 | +| TIA | TIA-1137.610 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### **10.5.38.16 X.S0054-910-0 Version 1.0 CAN Data Dictionary (December 2007)** + +This document defines AAA Data Dictionary in the CAN system. It defines 3GPP2 specific RADIUS attributes and Diameter AVPs. It describes the AAA RADIUS attributes and Diameters AVP for different interfaces such as eBS/SRNC-AGW interface, AGW-AAA interface, HA-AAA interface etc. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTC | TS-3GB-X.S0054-910-0v1.0 | 1.0 | Published | 07-03-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-910-0v1.0.pdf | +| TIA | TIA-1137.910 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | + +### 10.5.38.17 X.S0054-910-0 Version 2.0 CAN Data Dictionary (August 2008) + +This document defines AAA Data Dictionary in the CAN system. It defines 3GPP2 specific RADIUS attributes and Diameter AVPs. It describes the AAA RADIUS attributes and Diameters AVP for different interfaces such as eBS/SRNC-AGW interface, AGW-AAA interface, HA-AAA interface etc. + +| | Document No. | Version | Status | Issued date | Location | +|-----|--------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1137.910-1 | | Published | --06-2009 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0054-90-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-910-0v1.0 | +| TTC | TS-3GB-X.S0054-910-0v2.0 | 2.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-910-0v2.0.pdf | + +### 10.5.38.18 X.S0054-910-A Version 1.0 CAN Data Dictionary (August 2008) + +This document defines AAA Data Dictionary in the CAN system. It defines 3GPP2 specific RADIUS attributes and Diameter AVPs. It describes the AAA RADIUS attributes and Diameters AVP for different interfaces such as eBS/SRNC-AGW interface, AGW-AAA interface, HA-AAA interface etc. + +| | Document No. | Version | Status | Issued date | Location | +|-----|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0054-910-Av1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0054-910-Av1.0 | +| TTC | TS-3GB-X.S0054-910-Av1.0 | 1.0 | Published | 28-11-2008 | http://www.ttc.or.jp/j/document_list/free/TS/TS-3GB-X.S0054-910-Av1.0.pdf | + +### 10.5.39 X.S0055-0 Version 1.0 MMD Supplementary Services (May 2009) + +This document provides the protocol details and example call flows for providing supplementary service to mobile users connected to Multimedia Domain (MMD) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1136 | | Published | --02-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0055-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0055-0v1.0 | + +### 10.5.40 X.S0057-0 Version 1.0 E-UTRAN – eHRPD Connectivity and Interworking: Core Network Aspects (April 2009) + +The scope of this document covers support for an evolved access terminal (UE as known in this specification) using the eHRPD air interface and the S101 tunnel to access the core network architecture defined in 3GPP TS 23.401 [15] and TS 23.402 [16] . + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0057-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0057-0v1.0 | +| TIA | TIA-1163 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | + +#### **10.5.40.1 X.S0057-0 Version 2.0 E-UTRAN – eHRPD Connectivity and Interworking: Core Network Aspects (December 2009)** + +The scope of this document covers support for an evolved access terminal (UE as known in this specification) using the eHRPD air interface and the S101 tunnel to access the core network architecture defined in 3GPP TS 23.401 [15] and TS 23.402 [16] . + +| | Document No. | Version | Status | Issued date | Location | +|-----|----------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1163-1 | | Published | --02-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0057-0v2.0 | 2.0 | Published | 19-02-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0057-0v20.pdf | + +#### **10.5.40.2 X.S0057-0 Version 3.0 E-UTRAN – eHRPD Connectivity and Interworking: Core Network Aspects (September 2010)** + +The scope of this document covers support for an evolved access terminal (UE as known in this specification) using the eHRPD air interface and the S101 tunnel to access the core network architecture defined in 3GPP TS 23.401 [19] and TS 23.402 [20]. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0057-0 v3.0 | 3.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1163-2 | | Published | --08-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0057-0v3.0 | 3.0 | Published | 02-12-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0057-0v30.pdf | + +#### **10.5.41 X.S0058-0 Version 1.0 WiMAX-HRPD Interworking: Core Network Aspects (January 2009)** + +This document defines a method of interworking between WiMAX and HRPD systems. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0058-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0058-0 v1.0 | + +#### **10.5.41.1 X.S0058-0 Version 2.0 WiMAX-HRPD Interworking: Core Network Aspects (June 2010)** + +This document defines a method of interworking between WiMAX and HRPD systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0058-0 v2.0 | 2.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1164-1 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0058-0v2.0 | 2.0 | Published | 27-07-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0058-0v20.pdf | + +#### **10.5.42 X.S0059-000-0 Version 1.0 cdma2000 Femtocell Network: Overview (January 2010)** + +This document provides an overview of the series of documents that specify the HRPD and cdma2000 1x Femtocell network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0059-000-0 v1.0 | 1.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1165-000 | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0059-000-v1.0 | 1.0 | Published | 27-07-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0059-000-0v10.pdf | + +#### 10.5.42.1 X.S0059-100-0 Version 1.0 cdma2000 Femtocell Network: Packet Data Network Aspects (January 2010) + +This document provides a packet data specifications for the HRPD and 1x packet data Femtocell network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0059-100-0 v1.0 | 1.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1165-100 | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0059-100-0v1.0 | 1.0 | Published | 27-07-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0059-100-0v10.pdf | + +#### 10.5.42.2 X.S0059-200-0 Version 1.0 cdma2000 Femtocell Network: 1x and IMS Network Aspects (January 2010) + +This document defines the stage 2 service descriptions, call flows and normative stage 3 procedures that provide cdma2000 1x circuit-switched services to the MS through the IMS core network when the MS is camped on a Femto Access Point (FAP). + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0059-200-0 v1.0 | 1.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1165-200 | | Published | --03-2010 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0059-200-0v1.0 | 1.0 | Published | 27-07-2010 | http://www.ttc.or.jp/imt2000/ts/tsxs0059-200-0v10.pdf | + +#### 10.5.43 X.S0060 Version 1.0 HRPD Support for Emergency Services (July 2008) + +This document covers the Access Network aspects that are essential for the provisioning of IMS emergency services. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAT.3G-X.S0060-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0060-0 v1.0 | + +#### 10.5.44 X.S0061 Version 1.0 Network PMIP Support (December 2008) + +The scope of this document covers support for PMIPv4 and PMIPv6 between PDSN and LMA/HA, called network PMIP. It includes network PMIP based Simple IP address assignment and network PMIP tunnel management. The transport between PDSN and HA/LMA may use IPv4 or IPv6. + +| | Document No. | Version | Status | Issued date | Location | +|-----|-----------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIA | TIA-1160 | | Published | --09-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTA | TTAT.3G-X.S0061-0v1.0 | 1.0 | Published | 29-01-2010 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-X.S0061-0 v1.0 | + +#### **10.5.45 X.S0062 Version 1.0 PCC for cdma2000 1x and HRPD Networks (October 2010)** + +The scope of the specifications in this document is limited to cdma2000 1x and HRPD networks. This document covers support for 3GPP TS 23.203 specified Policy and Charging Control (PCC) architecture using cdma2000 1x and HRPD air interfaces and networks. This document is limited to alignment with 3GPP Release 9 specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-X.S0062-0 v1.0 | 1.0 | Published | --09-2011 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-1187 | | Published | --08-2011 | http://www.tiaonline.org/standards/catalog/index.cfm | +| TTC | TS-3GB-X.S0062-0v1.0 | 1.0 | Published | 27-04-2010 | http://www.ttc.or.jp/imt2000/ts-tsxs0062-0v10.pdf | + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a21983bb60d8058a4739b6142d94954631344f07 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7030600d04d1affa1a3c073e2179080a7fa25d30cbbfba029e04938a6bc82748 +size 50925 diff --git a/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fad9787c57b41f811e65b69af1e42f589591057c --- /dev/null +++ b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea4542563ddea0559d577b46cf697de71f819c7c39290a9dd329a27b275e025d +size 8224 diff --git a/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72f4178068a596fdda2cb049e87cc946a0435d12 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4651764f9fe3f208b27407e0d5afa14454c17db9cfc14e5a532f7c0550549cc4 +size 71876 diff --git a/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2dd30a6342b0163f31715ef427aca52f49d76ad4 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aaf4fb163d49b1e12084edb5ed5408c0938a7d4c4eb9353f1ec70ee6f3a1296 +size 83120 diff --git a/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..799b475f983d5c2001176139467e307288ce8363 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8447eae12426e5ff541f26ac5670e7838fbb032c7c5a3a8870e0995dbf318d20 +size 212368 diff --git a/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fd2cdbbdec045a056741167c025ba815649e561e --- /dev/null +++ b/marked/Q/T-REC-Q.1902.1-200107-I_PDF-E/raw.md @@ -0,0 +1,832 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1902.1** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Bearer Independent Call Control protocol +(Capability Set 2): Functional description** + +ITU-T Recommendation Q.1902.1 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Bearer Independent Call Control protocol (Capability Set 2): Functional description** + +## **Summary** + +This Recommendation provides a functional description of the Bearer Independent Call Control (BICC) protocol for the support of narrowband ISDN services independent of the bearer technology and signalling message transport technology used. + +## **Source** + +ITU-T Recommendation Q.1902.1 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +# CONTENTS + +| | Page | | +|------------|-------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 5 | +| 4 | Abbreviations..... | 7 | +| 5 | Conventions ..... | 9 | +| 6 | Architecture ..... | 9 | +| 6.1 | Network model ..... | 9 | +| 6.2 | Protocol model..... | 11 | +| 6.3 | Recommendation structure ..... | 11 | +| 7 | Introduction to BICC protocol signalling procedures..... | 12 | +| 7.1 | Address signalling..... | 12 | +| 7.2 | Basic procedures ..... | 12 | +| 7.3 | Signalling methods ..... | 12 | +| 7.4 | Interworking..... | 12 | +| 7.4.1 | BICC interworking ..... | 12 | +| 7.4.2 | Interworking with ISUP..... | 12 | +| 7.4.3 | Interworking with other signalling systems or user parts..... | 13 | +| 8 | Capabilities supported..... | 13 | +| 8.1 | Internationally applicable class..... | 16 | +| 8.2 | National use class..... | 16 | +| 9 | Future enhancements and compatibility procedure ..... | 16 | +| 9.1 | Version compatibility ..... | 17 | +| 9.2 | Additional coding guidelines for compatibility of BICC protocol versions..... | 17 | +| 9.2.1 | Messages..... | 17 | +| 9.2.2 | Parameters ..... | 18 | +| 9.3 | Forward and backward compatibility for the BICC APM user application ..... | 19 | +| Appendix I | –Guidelines for use of instruction indicators ..... | 19 | +| I.1 | Introduction..... | 19 | +| I.2 | Priority of execution ..... | 19 | +| I.3 | Notification ..... | 19 | +| I.4 | Considerations ..... | 20 | +| I.4.1 | Discarding unrecognized messages ..... | 20 | +| I.4.2 | Essential services ..... | 20 | + +| | Page | +|------------------------------------------------|-------------| +| I.4.3 Non-essential services ..... | 20 | +| I.4.4 Broadband/narrow-band interworking ..... | 20 | +| I.4.5 Pass on ..... | 20 | + +## **Bearer Independent Call Control protocol (Capability Set 2): Functional description** + +# **1 Scope** + +This Recommendation provides a functional description of the Bearer Independent Call Control (BICC) protocol. The BICC protocol provides the signalling functions required to support narrowband ISDN services independent of the bearer technology and signalling transport technology used. + +The BICC protocol uses the Signalling Transport Converter (STC) layer for signalling message transport. The Generic Signalling Transport Service is described in ITU-T Q.2150.0 [31]. The STCs are defined in other Recommendations in the Q.2150.x family of Recommendations. + +Several arrangements are possible for nodes that support BICC signalling. These nodes may have an associated Bearer Control Function (BCF) in which case they are referred to as Serving Nodes (SN). A node without an associated BCF is referred to as Call Mediation Node (CMN). Between Serving Nodes the control of bearers is provided by other protocols – not specified by this Recommendation. + +In a Serving Node (SN), the Call Service Function and the Bearer Control Function (BCF) entities may be physically separated. The Call Bearer Control (CBC) signalling is used between these two entities in case of physical separation. The CBC protocol is specified in ITU-T Q.1950 [61]. + +Bearer control signalling can be deployed over a separate signalling transport or the Bearer Control Protocol (BCP) can be tunnelled over the "horizontal" BICC protocol between peer CSFs and the "vertical" CBC interface between a CSF and a BCF. The Bearer Control Tunnelling Protocol is specified in ITU-T Q.1990 [62]. + +Both SNs and CMNs are modelled using the "Half Call" modelling technique. Every call processing scenario is thus divided between an incoming and an outgoing signalling procedure. In the scope of this Recommendation at least one of these procedures is the BICC procedure (see Figures 1 and 2). + +![Diagram illustrating the scope of the Recommendation in case of a Serving Node (SN).](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +The diagram shows the internal structure of a Serving Node (SN) and the scope of the Recommendation. The SN is represented by a large dashed rectangle. Inside it, a Call Service Function (CSF) is shown, which is further divided into 'Incoming procedures' and 'Outgoing procedures'. Below the CSF, a Bearer Control Function (BCF) is shown, which is part of a Bearer Interface Function (BIWF). The CSF and BCF are connected by 'Call Bearer Control (CBC) signalling'. The CSF is connected to external 'Call Control Signalling (BICC protocol or other signalling system)' on both sides. The BCF is connected to external 'Bearer Control Signalling' on both sides. A horizontal line at the bottom represents the 'Bearer'. A dashed box labeled 'SCOPE OF THIS RECOMMENDATION' encloses the CSF and BCF components. + +Diagram illustrating the scope of the Recommendation in case of a Serving Node (SN). + +**Figure 1/Q.1902.1 – Scope of this Recommendation in case of an SN** + +![Diagram of the scope of the recommendation in case of a CMN. The diagram shows a Call Mediation Node (CMN) containing a Call Service Function (CSF) with Incoming and Outgoing procedures. The CSF is connected to external Call Control Signalling (BICC protocol) on both sides. Below the CMN, a Bearer Independent Function (BIWF) contains a Bearer Control Function (BCF). The BCF is connected to external Bearer Control Signalling on both sides and is also connected to a Bearer line. A dashed box labeled 'SCOPE OF THIS RECOMMENDATION' encloses the CMN and the BCF. The diagram is labeled T11111840-01.](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +The diagram illustrates the architecture of a Call Mediation Node (CMN) and its interaction with external systems. At the top, a dashed box labeled 'SCOPE OF THIS RECOMMENDATION' contains a 'CALL MEDIATION NODE (CMN)'. Inside the CMN, a 'Call Service Function (CSF)' is shown, which includes 'Incoming procedures' and 'Outgoing procedures'. The CSF is connected to 'Call Control Signalling (BICC protocol)' on both the left and right. Below the CMN, a 'BIWF' (Bearer Independent Function) contains a 'BCF' (Bearer Control Function). The BCF is connected to 'Bearer Control Signalling' on both the left and right. A horizontal line at the bottom represents the 'Bearer'. The diagram is labeled 'T11111840-01' in the bottom right corner. + +Diagram of the scope of the recommendation in case of a CMN. The diagram shows a Call Mediation Node (CMN) containing a Call Service Function (CSF) with Incoming and Outgoing procedures. The CSF is connected to external Call Control Signalling (BICC protocol) on both sides. Below the CMN, a Bearer Independent Function (BIWF) contains a Bearer Control Function (BCF). The BCF is connected to external Bearer Control Signalling on both sides and is also connected to a Bearer line. A dashed box labeled 'SCOPE OF THIS RECOMMENDATION' encloses the CMN and the BCF. The diagram is labeled T11111840-01. + +**Figure 2/Q.1902.1 – Scope of this Recommendation in case of a CMN** + +This Recommendation is one of the set of Recommendations that describe the Bearer Independent Call Control protocol. Other Recommendations in this group include: + +- ITU-T Q.1902.2 (2001) that describes BICC CS-2 general functions of messages and parameters; +- ITU-T Q.1902.3 (2001) that describes BICC CS-2 formats and codes; +- ITU-T Q.1902.4 (2001) that describes BICC CS-2 basic call procedures; +- ITU-T Q.1902.5 (2001) that describes extensions to the Application Transport Mechanism in the context of the Bearer Independent Call Control; +- ITU-T Q.765.5 (2000) and its Amendment 1 that specifies the APM-user to support the transport of the bearer related information for the BICC protocol. + +Interworking between BICC and other signalling systems is described in the Q.1912 series of Recommendations. + +Generic signalling procedures and support of ISDN User Part supplementary services by the BICC protocol are described in ITU-T Q.1902.6 [18]. + +The Bearer Independent Call Control protocol is suitable for both international and national applications. Therefore coding space has been reserved in order to allow national Administrations and recognized operating agencies to introduce network specific signalling messages and elements of information within the internationally standardized protocol structure. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revisions; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T E.164 (1997), *The international public telecommunication numbering plan.* +- [2] ITU-T I.112 (1993), *Vocabulary of terms for ISDNs.* +- [3] ITU-T I.210 (1993), *Principles of telecommunication services supported by an ISDN and the means to describe them.* +- [4] ITU-T Q.850 (1998), *Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part.* +- [5] ITU-T Q.730 (1999), *ISDN User Part supplementary services.* +- [6] ITU-T Q.761 (1999), *Signalling System No. 7 – ISDN User Part functional description.* +- [7] ITU-T Q.762 (1999), *Signalling System No. 7 – ISDN User Part general functions of messages and signals.* +- [8] ITU-T Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes.* +- [9] ITU-T Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures.* +- [10] ITU-T Q.766 (1993), *Performance objectives in the integrated services digital network application.* +- [11] ITU-T Q.765 (2000), *Signalling System No. 7 – Application transport mechanism.* +- [12] ITU-T Q.769.1 (1999), *Signalling System No. 7 – ISDN User Part enhancements for the support of number portability.* +- [13] ITU-T Q.1901 (2000), *Bearer Independent call control protocol.* +- [14] ITU-T Q.1902.2 (2001), *Bearer independent Call Control protocol (CS-2) and Signalling System No. 7 – ISDN User Part general functions of messages and parameters.* +- [15] ITU-T Q.1902.3 (2001), *Bearer independent call control protocol (CS-2) and signalling system No. 7 – ISDN user part formats and codes.* +- [16] ITU-T Q.1902.4 (2001), *Bearer independent call control protocol (CS-2) basic call procedures.* +- [17] ITU-T Q.1902.5 (2001), *Exceptions to the application transport mechanism in the context of bearer independent call control.* +- [18] ITU-T Q.1902.6 (2001), *Generic signalling procedures and support of ISDN user part supplementary services with the bearer independent call control protocol.* +- [19] ITU-T Q.1912.1 (2001), *Interworking between signalling system No. 7 ISDN user part and the bearer independent call control protocol.* +- [20] ITU-T Q.701 (1993), *Functional description of the message transfer part (MTP) of signalling system No. 7.* +- [21] ITU-T Q.704 (1996), *Signalling network functions and messages.* +- [22] ITU-T Q.2210 (1996), *Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140.* +- [23] ITU-T Q.2110 (1994), *B-ISDN ATM adaptation layer – Service specific connection oriented protocol (SSCOP).* +- [24] ITU-T Q.2111 (1999), *Service specific connection oriented protocol in a multi-link and connectionless environment (SSCOPMCE).* +- [25] ITU-T Q.765.1 (1998), *Signalling system No. 7 – Application transport mechanism: Support of VPN applications with PSSI information flows.* + +- [26] ITU-T Q.765.4 (2000), *Signalling system No. 7 – Application transport mechanism: Support of the generic addressing and transport protocol.* +- [27] ITU-T Q.765.5 (2000), *Signalling System No. 7 – Application transport mechanism: Bearer Independent Call Control (2000).* +- [28] ITU-T Q.765.5 (2000), Amd. 1 (2001), *Bearer Independent Call Control Capability Set 2.* +- [29] ITU-T Q.1218 (1995), *Interface Recommendation for intelligent network CS-1.* +- [30] ITU-T Q.1228 (1997), *Interface Recommendation for intelligent network Capability Set 2.* +- [31] ITU-T Q.2150.0 (2001), *Generic signalling transport service.* +- [32] ITU-T Q.28 (1988), *Determination of the moment of the called subscriber's answer in the automatic service.* +- [33] ITU-T E.260 (1988), *Basic technical problems concerning the measurement and recording of call durations.* +- [34] ITU-T Q.101 (1988), *Facilities provided in international semi-automatic working.* +- [35] ITU-T E.412 (1998), *Network management controls.* +- [36] ITU-T X.880 (1994) | ISO/IEC 13712-1:1995, *Information technology – Remote Operations: Concepts, model and notation.* +- [37] ITU-T X.121 (2000), *International numbering plan for public data networks.* +- [38] ITU-T E.212 (1998), *The international identification plan for mobile terminals and mobile users.* +- [39] ITU-T Q.703 (1996), *Signalling link.* +- [40] ITU-T Q.2763 (1995), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Format and codes.* +- [41] ITU-T E.172 (1992), *ISDN routing plan.* +- [42] ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies.* +- [43] ITU-T Q.12 (1988), *Overflow – alternative routing – rerouting – automatic repeat attempt.* +- [44] ITU-T Q.107 (1988), *Standard sending sequence of forward address information.* +- [45] ITU-T Q.115 (1999), *Logic for the control of echo control devices.* +- [46] ITU-T Q.118 (1997), *Abnormal conditions – Special release arrangements.* +- [47] ITU-T Q.542 (1993), *Digital exchange design objectives – Operations and maintenance.* +- [48] ITU-T Q.706 (1993), *Message transfer part signalling performance.* +- [49] ITU-T E.141 (1993), *Instructions for operators on the operator assisted international telephone service.* +- [50] ITU-T X.680 (1997) | ISO/IEC 8824-1:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.* +- [51] ITU-T X.681 (1997) | ISO/IEC 8824-2:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Information object specification.* +- [52] ITU-T X.682 (1997) | ISO/IEC 8824-3:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Constraint specification.* +- [53] ITU-T X.683 (1997) | ISO/IEC 8824-4:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications.* + +- [54] ITU-T 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)*. +- [55] ITU-T Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*. +- [56] ITU-T Q.932 (1998), *Digital Subscriber Signalling System No. 1 – Generic procedures for the control of ISDN supplementary services*. +- [57] ITU-T Q.104 (1988), *Language digit or discriminating digit*. +- [58] ITU-T F.69 (1994), *The international telex service – Service and operational provisions of telex destination codes and telex network identification codes*. +- [59] ITU-T G.732 (1988), *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s*. +- [60] ITU-T G.744 (1988), *Second order PCM multiplex equipment operating at 8448 kbit/s*. +- [61] ITU-T Q.1950 (2001), *Bearer independent call bearer control protocol*. +- [62] ITU-T Q.1990 (2001), *BICC bearer control tunnelling protocol*. +- [63] ITU-T Q.2150.1 (2001), *Signalling Transport Converter on MTP3 and MTP3b*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 Backbone Network Connection (BNC):** Represents the edge to edge transport connection within the backbone network, consisting of one or more Backbone Network Connection Links (BNCL). The Backbone Network Connection represents a segment of the end to end Network Bearer Connection (NBC). + +**3.2 Backbone Network Connection Link (BNCL):** Represents the transport facility between two adjacent backbone network entities containing a bearer control function. + +**3.3 Bearer Control Function (BCF):** Note that five types of BCFs are illustrated in the composite functional model; BCF-G, BCF-J, BCF-N, BCF-R and BCF-T. + +- The Bearer Control Joint Function (BCF-J) provides the control of the bearer switching function, the communication capability with two associated call service functions (CSF), and the signalling capability necessary to establish and release the backbone network connection. +- The Bearer Control Gateway Function (BCF-G) provides the control of the bearer switching function, the communication capability with its associated call service function (CSF-G), and the signalling capability necessary to establish and release of the backbone network connection. +- The Bearer Control Nodal Function (BCF-N) provides the control of the bearer switching function, the communication capability with its associated call service function (CSF), and the signalling capability necessary to establish and release of the backbone network connection to its peer (BCF-N). +- The Bearer Control Relay Function (BCF-R) provides the control of the bearer switching function and relays the bearer control signalling requests to next BCF in order to complete the edge to edge backbone network connection. + +- The Bearer Control Transit Function (BCF-T) provides the control of the bearer switching function, the communication capability with its associated call service function (CSF-T), and the signalling capability necessary to establish and release of the backbone network connection. +- 3.4 Bearer Control Segment (BCS):** Represents the signalling relationship between two adjacent Bearer Control Functional entities (BCF). +- 3.5 Bearer InterWorking Function (BIWF):** A functional entity which provides bearer control functions (BCF) and media mapping/switching functions within the scope of a Serving Node (BCF-N, BCF-T or BCF-G) and one or more MCF and MMSF, and is functionally equivalent to a Media Gateway that incorporates bearer control. +- 3.6 Bearer InterWorking Node (BIWN):** A physical unit incorporating functionality similar to a BIWF. +- 3.7 Call Control Association (CCA):** Defines the peer to peer signalling association between Call, and Call & Bearer state machines located in different physical entities. +- 3.8 Call Mediation Node (CMN):** A functional entity that provides CSF-C functions without an associated BCF entity. +- 3.9 Call Service Function (CSF):** Four types of CSF are defined: +- The Call Service Nodal Function (CSF-N) provides the service control nodal actions associated with the narrowband service by interworking with narrowband and Bearer Independent Call Control (BICC) signalling, signalling to its peer (CSF-N) the characteristics of the call, and invoking the Bearer Control Nodal Functions (BCF-N) necessary to transport the narrowband bearer service across the backbone network. + - The Call Service Transit Function (CSF-T) provides the service transit actions necessary to establish and maintain a backbone network call (see Figure 3), and its associated bearer by relaying signalling between CSF-N peers and invoking the Bearer Control Transit Functions (BCF-T) necessary to transport the narrowband bearer service across the backbone network. + - The Call Service Gateway Function (CSF-G) provides the service gateway actions necessary to establish and maintain a backbone network call and its associated bearer by relaying signalling between CSF-N peers and invoking the Bearer Control Gateway Functions (BCF-G) necessary to transport the narrowband bearer service between backbone networks. + - The Call Service Coordination Function (CSF-C) provides the call coordination and mediation actions necessary to establish and maintain a backbone network call by relaying signalling between CSF-N peers. The CSF-C has no association with any BCF. It is only a call control function. +- 3.10 Gateway Serving Node (GSN):** A functional entity which provides gateway functionality between two network domains. This functional entity contains one or more call service gateway functions (CSF-G), and one or more bearer interworking functions (BIWF). GSNs interact with other GSNs, in other backbone network domains and other ISNs and TSNs within its own backbone network domain. The network signalling flows for a GSN are equivalent as those for a TSN. +- 3.11 Integrated Services Digital Network (ISDN):** See definition 308 in 2.1/I.112 [2]. +- 3.12 Interface Serving Node (ISN):** A functional entity which provides the interface with non-BICC networks and terminal equipment. This functional entity contains one or more call service nodal functions (CSF-N), and one or more bearer interworking functions (BIWF) which interact with the non-BICC networks and terminal equipment and its peers within the broadband backbone network. +- 3.13 Media Control Function (MCF):** A functional entity that interacts with the BCF to provide the control of the bearer and MMSF. The precise functionality is outside the scope of BICC. + +- 3.14 Media Mapping/Switching Function (MMSF):** An entity providing the function of controlled interconnection of two bearers and optionally the conversion of the bearer from one technology and adaptation/encoding technique to another. +- 3.15 service; telecommunication service:** See definition 201 in 2.1/I.112 [2]. +- 3.16 Serving Node (SN):** A generic term referring to ISN, GSN or TSN nodes. +- 3.17 Signalling Transport Layers (STL):** Any suite of protocol layers currently specified to provide Transport and/or Network Layer services to the BICC. Their functions, protocol and service primitives are outside the scope of this Recommendation. +- 3.18 Signalling Transport Converter (STC):** A protocol layer between the STL and BICC. This layer enables the BICC protocol to be independent of the STL being used. +- 3.19 subaddress:** See 12.2/E.164 [1]. +- 3.20 supplementary service:** See 2.4/I.210 [3]. +- 3.21 Switching Node (SWN):** A functional entity which provides the switching functions within the broadband backbone network. This functional entity contains a bearer control state machine (BCF R). SWNs interact with other SWNs, within their own backbone network domain. The SWNs BCF-R also interact with the BCF-N functions contained in BIWF entities. +- 3.22 Switched Circuit Network (SCN):** A generic term for any network that uses circuit switching technology, i.e. ISDN, PSTN, PLMN. +- 3.23 Terminal Equipment (TE):** Represents the customer's access equipment used to request and terminate network associated connectivity services. +- 3.24 Transit Serving Node (TSN):** A functional entity which provides transit functionality between ISNs and GSNs. This functional entity contains one or more call service transit functions (CSF-T), and one or more bearer interworking functions (BIWF). TSNs interact with other TSNs, GSNs and ISNs within their own backbone network domain. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------| +| ACM | Address Complete Message | +| AEI | Application Entity Invocation | +| APM | Application Transport Mechanism | +| APP | Application Transport Parameter | +| ASE | Application Service Element | +| ATII | Application Transport Instruction Indicators | +| BAT | Bearer Association Transport | +| BCF | Bearer Control Function | +| BCF-G | Bearer Control Gateway Function | +| BCF-N | Bearer Control Nodal Function | +| BCF-T | Bearer Control Transit Function | +| BCTP | Bearer Control Tunnelling Protocol | +| BICC | Bearer Independent Call Control | +| BIWF | Bearer Interworking Function | + +| | | +|--------|---------------------------------------------------------------------------| +| BNC-ID | Backbone Network Connection Identifier | +| CIC | Call Instance Code | +| CMN | Call Mediation Node | +| COT | Continuity message | +| CPG | Call Progress message | +| CSF | Call Service Function | +| CSF-C | Call Service Coordination Function | +| CSF-G | Call Service Gateway Function | +| CSF-N | Call Service Nodal Function | +| CSF-T | Call Service Transit Function | +| DPC | Destination Point Code | +| EH | Errors Handling | +| GAT | Generic Addressing and Transport | +| GRS | Group Reset message | +| GSN | Gateway Serving Node | +| IAM | Initial Address Message | +| ISDN | Integrated Services Digital Network | +| ISN | Interface Serving Node | +| ISUP | ISDN User Part | +| LSB | Least Significant Bit | +| MCF | Media Control Function | +| MLPP | Multi-Level Precedence and Pre-emption | +| MMSF | Media Mapping/Switching Function | +| MSB | Most Significant Bit | +| MTP | Message Transfer Part | +| MTP3 | Message Transfer Part level 3 (Narrowband) | +| MTP3b | Message Transfer Part level 3 (Broadband) | +| NI | Network Indicator (in SIO), or Network Interface (in specification model) | +| OPC | Originating Point Code | +| PLMN | Public Land Mobile Network | +| PSTN | Public Switched Telephone Network | +| REL | Release message | +| RLC | Release Complete message | +| RSC | Reset CIC message | +| SACF | Single Association Control Function | +| SAM | Subsequent Address Message | +| SAO | Single Association Object | + +| | | +|-----|--------------------------------| +| SCN | Switched Circuit Network | +| SI | Service Indicator | +| SIO | Service Information Octet | +| SLS | Signalling Link Selection | +| SN | Serving Node | +| STC | Signalling Transport Converter | +| STL | Signalling Transport Layers | +| SWN | Switching Node | +| TE | Terminal Equipment | +| TSN | Transit Serving Node | + +# 5 Conventions + +1) The name of each element of the following classes of terms is capitalized: + +- indicators; +- parameters; +- information elements; +- messages. + +Examples: Called Party Number parameter, Initial Address message. + +2) The definition of a parameter value is written in *italics* and is put between quotation marks. + +Example: Nature of Address value 0000011 – *"national (significant) number"*. + +3) All message names are BICC messages unless explicitly stated otherwise. + +Example: the "IAM message" is the IAM message in BICC, whereas an IAM message in ISUP is referred to as an "ISUP IAM message". + +# 6 Architecture + +## 6.1 Network model + +Figure 3 shows the complete functional model of a network using the BICC protocol for call control signalling. + +![Figure 3/Q.1902.1 – Network Functional model. A complex diagram showing the functional architecture of a network, including components like ISN-A, TSN-x, GSN-x, GSN-y, CMN-x, ISN-B, ACN-E, and various BCF (Bearer Control Function) units. It illustrates signaling paths (Call Control, Bearer Control, CBC, Access Control) and data paths (Bearer Interworking Function, Backbone Network Connections, Network Bearer Connection).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates the Network Functional model for Q.1902.1. At the top, a 'Signalling Transport Network' is shown as a shaded oval. Below it, various network elements are depicted: + +- ISN-A** (ISDN Switching Network) contains **CSF-N** (Control Signalling Function) and **BCF-N (v)** (Bearer Control Function). +- TSN-x** (Transport Switching Network) contains **CSF-T** and **BCF-T (w)**. +- GSN-x** (Gateway Switching Network) contains **CSF-G** and **BCF-G (x)**. +- GSN-y** (Gateway Switching Network) contains **CSF-G** and **BCF-G (y)**. +- CMN-x** (Common Network) contains **CSF-C** and **BCF-J**. +- ISN-B** (ISDN Switching Network) contains **CSF-N** and **BCF-N (z)**. +- ACN-E** (Access Network) contains **CSF-R** and **BCF-A (a)**. +- Intermediate **BCF-R** units are shown between **BCF-N (v)** and **BCF-T (w)**, **BCF-T (w)** and **BCF-G (x)**, **BCF-G (y)** and **BCF-J**, and **BCF-N (z)** and **BCF-A (a)**. +- SWN-1**, **SWN-2**, and **SWN-3** (Switching Network) units are also shown. + +Signaling paths are indicated by dashed lines from the 'Signalling Transport Network' to the CSF functions, labeled as 'Call Control Signalling', 'Bearer Control Signalling', 'Call & Bearer Control (CBC) Signalling', and 'Access Control Signalling'. + +Data paths are indicated by solid lines, labeled as 'Bearer Interworking Function (BIWF)', 'Backbone Network Connections', and 'Network Bearer Connection (end-to-end)'. + +External entities include 'TE' (Terminal Equipment) and 'Other service supplier networks' connected to the network elements. + +The diagram is labeled with 'T11111850-01' in the bottom right corner. + +Figure 3/Q.1902.1 – Network Functional model. A complex diagram showing the functional architecture of a network, including components like ISN-A, TSN-x, GSN-x, GSN-y, CMN-x, ISN-B, ACN-E, and various BCF (Bearer Control Function) units. It illustrates signaling paths (Call Control, Bearer Control, CBC, Access Control) and data paths (Bearer Interworking Function, Backbone Network Connections, Network Bearer Connection). + +Figure 3/Q.1902.1 – Network Functional model + +## 6.2 Protocol model + +Figure 4 shows the protocol model adopted for this Recommendation. + +![Figure 4/Q.1902.1 – Protocol model diagram](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +The diagram illustrates the protocol model for BICC. At the top is a block labeled 'BICC procedures'. Below it, two vertical paths are shown. The left path consists of a 'Generic interface' connecting to a stack of three 'Signalling Transport Converter' blocks, which are then connected via a 'Transport specific interface' to a stack of three 'Signalling Transport Layers' blocks. The right path consists of a 'Generic interface' connecting to a stack of three 'Mapping Function' blocks, which are then connected via a 'Bearer specific interface' to a stack of three 'Bearer Control' blocks. Both the 'Signalling Transport Layers' and the 'Bearer Control' blocks have a 'Call control protocol' or 'Bearer control protocol' interface at their base. + +Figure 4/Q.1902.1 – Protocol model diagram + +T11111860-01 + +Figure 4/Q.1902.1 – Protocol model + +The protocol aspects of the functional model in Figure 3 are provided by the elements of the protocol model in Figure 4. + +- The BICC procedures block includes the functions of the CSF element in the functional model. +- The protocol functions of the BCF element of the functional model are distributed between the Mapping Function, and Bearer Control blocks in Figure 4. The other functions included in the BCF element, e.g. control of switching functions, are not shown in Figure 4. +- Where the BICC description refers to sending/receiving bearer signalling events to/from the BCF, this relates to use of the generic interface to the mapping function block in Figure 4. +- Where the BICC description refers to sending/receiving BICC messages, this relates to the use of the generic interface to the Signalling Transport Converter, see ITU-T Q.2150.0 [31]. + +## 6.3 Recommendation structure + +This Recommendation provides a functional description of the BICC protocol, independent of the bearer technology employed. This is the block labelled BICC procedures in Figure 4. It also uses the generic interface to the blocks labelled Mapping Functions and Signalling Transport Converter. + +The blocks in Figure 4 labelled Mapping Function are defined in additional publications1 that are to be provided for each bearer technology to describe specific adaptation for that technology. + +The blocks in Figure 4 labelled Signalling Transport Converter are defined in the Q.2150.x family of Recommendations which describe transport specific issues relating to the signalling transport service [31]. + +# **7 Introduction to BICC protocol signalling procedures** + +## **7.1 Address signalling** + +In general, the call setup procedure described is standard for both speech and non-speech applications using *en bloc* address signalling. Overlap address signalling is also specified. + +## **7.2 Basic procedures** + +The basic call control procedure is divided into three phases: call setup, the data/conversation phase and call teardown. Messages on the signalling link are used to establish and terminate the different phases of a call. Standard in-band supervisory tones and/or recorded announcements are returned to the caller on appropriate connection types to provide information on call progress. Calls originating from ISDN terminals may be supplied with more detailed call progress information by means of additional messages in the access protocol supported by a range of messages in the network. + +## **7.3 Signalling methods** + +Only link-by-link signalling method is used in this Recommendation. + +It is primarily used for messages that need to be examined at each SN/CMN. The link-by-link method may also be used for messages of end point significance. + +## **7.4 Interworking** + +### **7.4.1 BICC interworking** + +In call control interworking between two (BICC) protocols, the call control provides the interworking logic. + +Peer-to-peer interworking takes place between two SNs/CMNs that support different implementations of the same protocol. + +Interworking is realized following interpretation of the protocol information received by either SN/CMN. + +For this purpose only one BICC protocol implementation may be present in an SN/CMN and peer-to-peer compatibility of versions can be assured, as described in clause 9. + +### **7.4.2 Interworking with ISUP** + +The BICC protocol is an adaptation of the ISUP protocol definition, but it is not peer-to-peer compatible with ISUP (see ITU-T Q.1912.1 [19]). + +The goal is to keep the BICC and ISUP protocols as closely aligned as possible. This will avoid extensive call control interworking and provide consistency of end-to-end functionality in mixed BICC/ISUP networks. The compatibility mechanism (see clause 9) provides for independent introduction of new capabilities in either protocol. + +--- + +1 See Bibliography. + +### 7.4.3 Interworking with other signalling systems or user parts + +The examples included in this Recommendation are typical only and should not be used as a definitive interworking guide. Interworking between BICC and other signalling systems and user parts is a combination of the BICC-ISUP interworking according to ITU-T Q.1912.1 [19] and the relevant Recommendations specifying the interworking between ISUP and those other signalling systems and user parts (Recommendations in the Q.1912 series). + +# 8 Capabilities supported + +Table 1 lists the signalling capabilities supported by BICC for basic call. Table 2 lists the generic signalling procedures, supplementary services and some additional functions/services supported by BICC. These capabilities are categorized into two classes; internationally applicable class and national use class. These classes are defined as follows. + +**Table 1/ Q.1902.1 – Signalling capabilities for basic call** + +| Function/service | National use | International | +|------------------------------------------------------------------------|--------------|---------------| +| Speech/3.1 kHz audio | √ | √ | +| 64 kbit/s unrestricted | √ | √ | +| Multirate connection types (Note 1) | √ | √ | +| N × 64 kbit/s connection types | √ | √ | +| En bloc address signalling | √ | √ | +| Overlap address signalling | √ | √ | +| Transit network selection | √ | – | +| Continuity indication | √ | √ | +| Forward transfer | – | √ | +| Simple segmentation | √ | √ | +| Tones and announcements | √ | √ | +| Access delivery information | √ | √ | +| Transportation of User teleservice information | √ | √ | +| Suspend and resume | √ | √ | +| Signalling procedures for connection type allowing fallback capability | √ | √ | +| Propagation delay determination procedure | √ | √ | +| Simplified echo control signalling procedures | √ | √ | +| Automatic repeat attempt | √ | √ | +| Blocking and unblocking | √ | √ | +| CIC group query | √ | – | +| Dual seizure | √ | √ | +| Reset | √ | √ | +| Receipt of unreasonable signalling information | √ | √ | +| Compatibility procedure (BICC and BAT APM user application) | √ | √ | +| ISDN User Part signalling congestion control | Note 2 | Note 2 | +| Automatic congestion control | √ | √ | + +**Table 1/ Q.1902.1 – Signalling capabilities for basic call** + +| Function/service | National use | International | +|-----------------------------------------------------|--------------|---------------| +| Interaction with INAP | √ | √ | +| Unequipped CIC | √ | – | +| ISDN User Part availability control | Note 3 | Note 3 | +| MTP pause and resume | Note 2 | Note 2 | +| Overlength messages | √ | √ | +| Temporary Alternative Routing (TAR) | √ | √ | +| Hop counter procedure | √ | √ | +| Collect call request procedure | √ | √ | +| Hard-to-Reach | √ | √ | +| Calling geodetic location procedure | √ | √ | +| Carrier selection indication | √ | – | +| Inter-nodal traffic group identification | √ | √ | +| Codec negotiation and modification procedures | √ | √ | +| Joint BIWF support | √ | √ | +| Global Call Reference procedure | √ | √ | +| Out of band transport of DTMF tones and information | √ | √ | + +√ represents ITU-T support. +– represents ITU-T non-support. +NOTE 1 – Multirate connection types are 2 × 64, 384, 1536 and 1920 kbit/s. +NOTE 2 – If BICC is deployed on an MTP3 or MTP3b signalling transport service, these functions are provided by the STC sublayer as described in ITU-T Q.2150.1 [63]. +NOTE 3 – If BICC is deployed on an MTP3 or MTP3b signalling transport service, an equivalent procedure is provided by the STC sublayer as described in ITU-T Q.2150.1 [63]. + +**Table 2/Q.1902.1 – Generic signalling procedures, services and functions** + +| Function/service | National use | International | +|-----------------------------------------------------|--------------|---------------| +| Generic signalling procedures | | | +| Generic number transfer | √ | √ | +| Generic digit transfer | √ | – | +| Generic notification procedure | √ | √ | +| Service activation | √ | √ | +| Remote Operations Service Element (ROSE) capability | √ | – | +| Network specific facilities | √ | – | +| Pre-release information transport | √ | √ | +| Application Transport Mechanism (APM) | √ | √ | +| Redirection | √ | – | +| Pivot routeing | √ | √ | + +**Table 2/Q.1902.1 – Generic signalling procedures, services and functions** + +| Function/service | National use | International | +|----------------------------------------------------------|--------------|---------------| +| Bearer redirection | √ | √ | +| Supplementary services | | | +| Direct-Dialling-In (DDI) | √ | √ | +| Multiple Subscriber Number (MSN) | √ | √ | +| Calling Line Identification Presentation (CLIP) | √ | √ | +| Calling Line Identification Restriction (CLIR) | √ | √ | +| Connected Line Identification Presentation (COLP) | √ | √ | +| Connected Line Identification Restriction (COLR) | √ | √ | +| Malicious Call Identification (MCID) | √ | √ | +| Sub-addressing (SUB) | √ | √ | +| Call Forwarding Busy (CFB) | √ | √ | +| Call Forwarding No Reply (CFNR) | √ | √ | +| Call Forwarding Unconditional (CFU) | √ | √ | +| Call Deflection (CD) | √ | √ | +| Explicit Call Transfer (ECT) | √ | √ | +| Call Waiting (CW) | √ | √ | +| Call HOLD (HOLD) | √ | √ | +| Completion of Calls to Busy Subscriber (CCBS) | √ | √ | +| Completion of Calls on No Reply (CCNR) | √ | √ | +| Terminal Portability (TP) | √ | √ | +| Conference calling (CONF) | √ | √ | +| Three-Party Service (3PTY) | √ | √ | +| Closed User Group (CUG) | √ | √ | +| Multi-Level Precedence and Preemption (MLPP) (Note) | √ | √ | +| Global Virtual Network Service (GVNS) | √ | √ | +| International telecommunication charge card (ITCC) | √ | √ | +| Reverse charging (REV) | √ | – | +| User-to-User Signalling (UUS) | √ | √ | +| Additional functions/services | | | +| Support of VPN applications with PSS1 Information Flows | √ | √ | +| Support of GAT protocol | √ | √ | +| Support of Number Portability (NP) | √ | – | +| / represents ITU-T support. | | | +| – represents ITU-T non-support. | | | +| NOTE – Only transiting of MLPP information is supported. | | | + +## **8.1 Internationally applicable class** + +The signalling capabilities of this class are to be supported over the international boundary. It is recommended that all international network operators support these capabilities. These capabilities are also applicable nationally except for those specific to the international interface. Any international SN implemented with BICC CS-1 [13] or later versions, however, has to be able to recognize all the messages and parameters defined for the international interface and properly react to them. If a capability of this class is requested internationally, the network operator should provide the capability. + +However, if it is not possible to provide the requested capability, the following actions are deemed appropriate: + +- release the call with an appropriate cause parameter; +- ignore the request and if necessary inform the preceding network of this fact; or +- provide an appropriate interworking action (e.g. fallback). + +## **8.2 National use class** + +The signalling capabilities of this class are basically supported only in national networks. However, they may also be applied internationally if a bilateral or multilateral agreement is reached among the network operators concerned. It is up to each Administration or recognized operating agency (ROA) whether or not to support the capabilities of this class. + +All the signalling elements qualified as of national use class are marked "national use" in the BICC Recommendations. + +# **9 Future enhancements and compatibility procedure** + +Requirements for additional protocol capabilities, such as the ability to support new supplementary services, will result from time to time in the need to add to or modify existing protocol elements and thus to create a new protocol version. + +In order to ensure adequate service continuity, the insertion of a new protocol version into one part of a network should be transparent to the remainder of the network. Compatible interworking between protocol versions is optimized by adhering to the following guidelines when specifying a new version: + +- 1) Existing protocol elements, i.e. procedures, messages, parameters and codes, should not be changed unless a protocol error needs to be corrected or it becomes necessary to change the operation of the service that is being supported by the protocol. +- 2) The semantics of a message, a parameter or of a field within a parameter should not be changed. +- 3) Established rules for formatting and encoding messages should not be modified. +- 4) The addition of parameters to the mandatory part of an existing message should not be allowed. +- 5) A parameter may be added to an existing message as long as it is allocated to the optional part of the message. +- 6) The addition of new octets to an existing mandatory fixed length parameter should be avoided. If needed, a new optional parameter should be defined containing the desired set of existing and new information fields. +- 7) The sequence of fields in an existing variable length parameter should remain unchanged. New fields may be added at the end of the existing sequence of parameter fields. If a change in the sequence of parameter fields is required, a new parameter should be defined. + +- 8) The all-zeros code point should be used exclusively to indicate an unallocated (spare) or insignificant value of a parameter field. This avoids an all-zeros code, sent by one protocol version as a spare value, to be interpreted as a significant value in another version. +- 9) The compatibility mechanism described in 9.1 applies to this and future versions of the BICC Recommendations. + +Rules 1) to 8) also apply, and in addition principles, which allow this and future versions of the BICC protocol to directly interwork with each other, maintaining protocol and service compatibility, and including end-to-end transparency. This is further outlined below. + +The compatibility mechanism at a Serving Node acts as at an ISUP exchange, and thus the introduction of BICC into a network using ISUP signalling does not degrade the ability to introduce new signalling versions into the network, e.g. an ISN receiving an unrecognized ISUP parameter will handle it according to 2.9.5/Q.764, Compatibility rules, passing it on to BICC if required. + +## 9.1 Version compatibility + +From CS-1 version of the BICC onwards, compatibility between versions will be guaranteed, in the sense that any two versions can be interconnected directly with each other, and the following requirements are fulfilled: + +### - i) *Protocol compatibility* + +Calls between any two BICC versions do not fail for the reason of "not satisfying" protocol requirements. + +### - ii) *Service and functional compatibility* + +This feature may be considered as compatibility typically between originating and destination SNs. Services and functions available at these SNs, but possibly not yet taken into account in the intermediate SNs/CMNs, are supported, provided they require only transparency of the intermediate SNs/CMNs. If this is not the case, a controlled call rejection or service rejection is required. + +### - iii) *Resource control and management compatibility* + +For these functions, occurring only link by link, at least a backward notification is needed, if correct handling is not possible. + +The compatibility mechanism is common for all BICC protocol versions from CS-1 [13] onwards. It is based on forward compatibility information associated with new signalling information. + +The compatibility method eases the network operation, e.g. for the typical case of a BICC protocol mismatch during a network upgrading, to interconnect two networks on a different functional level, for networks using a different subset of the same BICC capability set, etc. + +## 9.2 Additional coding guidelines for compatibility of BICC protocol versions + +The following guidelines are mandatory. + +### 9.2.1 Messages + +All new messages, not used by BICC CS-1 (see IUT-T Q.1901 [13]), use only parameters coded according to the coding rules for the parameters of the optional part of BICC messages. They always contain a Message Compatibility Information parameter. (Note that tables in clause 7 of ITU-T Q.1902.3 [15] show which of the current messages contain the Message Compatibility Information parameter.) + +Messages received and not recognized will be handled as described in ITU-T Q.1902.4 [16]. + +### 9.2.2 Parameters + +As a general principle, mixing information for different application associations (requiring different functional entity actions) inside a new BICC parameter should be avoided so that the behaviour of cooperating nodes can be defined using the compatibility mechanism. + +All parameters not listed in Table 3 shall have associated compatibility information contained in the Parameter Compatibility Information parameter. + +**Table 3/Q.1902.1 – Parameters not accompanied by compatibility information contained in the Parameter Compatibility Information parameter** + +| | | +|----|-----------------------------------------------| +| 1 | Access transport | +| 2 | Automatic congestion level | +| 3 | Backward call indicator | +| 4 | Called party number | +| 5 | Calling party number | +| 6 | Calling party's category | +| 7 | Cause indicators | +| 8 | CIC group supervision message type indicators | +| 9 | CIC state indicator (national use) | +| 10 | Closed user group interlock code | +| 11 | Connected number | +| 12 | Continuity indicators | +| 13 | End of optional parameters indicator | +| 14 | Event information | +| 15 | Facility indicator | +| 16 | Forward call indicators | +| 17 | Information indicators (national use) | +| 18 | Information request indicators (national use) | +| 19 | Message compatibility information | +| 20 | Nature of connection indicators | +| 21 | Optional backward call indicators | +| 22 | Optional forward call indicators | +| 23 | Original called number | +| 24 | Parameter compatibility information | +| 25 | Range and status | +| 26 | Redirecting number | +| 27 | Redirection information | +| 28 | Redirection number | +| 29 | Subsequent number | +| 30 | Suspend/Resume indicators | +| 31 | Transit network selection (national use) | +| 32 | Transmission medium requirement | +| 33 | User service information | +| 34 | User-to-user indicators | +| 35 | User-to-user information | + +Unrecognized parameter handling procedures can be found in ITU-T Q.1902.4 [16]. + +## **9.3 Forward and backward compatibility for the BICC APM user application** + +BICC uses an APM user application to transfer signalling information. The Bearer Association Transport (BAT) APM user ASE is used to provide a transport mechanism for this information. In order to provide forward and backward compatibility within BICC, a compatibility mechanism is introduced for the information elements transferred by this mechanism. Compatible interworking between BAT ASE versions is optimized by adhering to the same guidelines when specifying a new version as outlined above for the BICC protocol. + +This compatibility mechanism remains unchanged for all capability sets and/or subsets of the BICC protocol defined in this Recommendation. It is based on compatibility information sent with all signalling information related to the BAT APM user application. Formats and codes used by this compatibility mechanism can be found in ITU-T Q.765.5 [27], and relevant procedures are described in ITU-T Q.1902.4 [16]. + +# **APPENDIX I** + +## **Guidelines for use of instruction indicators** + +### **I.1 Introduction** + +Instruction indicators are used to indicate to an SN/CMN receiving unrecognized information what action should be taken due to this information being unrecognized. Unrecognized information may be a message or one or more parameters within a message, unrecognized values within a parameter cause the parameter itself to be treated as unrecognized. Instruction indicators are only examined once the message or parameter has been detected as unrecognized. + +### **I.2 Priority of execution** + +When processing instruction indicators, a certain order is implied by the type of actions which can be specified, the following list indicates a decreasing order of processing priority: + +- transit at intermediate exchange indicator; +- broadband/narrow-band interworking indicator; +- release call indicator; +- discard message, with or without notification, based on the notification indicator; +- discard parameter, with or without notification, based on the notification indicator; +- pass on not possible indicator. + +Only ISNs where interworking with B-ISUP is performed examine the broadband/narrow-band interworking indicator in place of the conventional release call, discard message or discard parameter indicators. + +### **I.3 Notification** + +The notification indicator is not strictly tied to the order of processing of the other indicators. It is recommended that notification is only required when information is discarded, this minimizes the amount of Confusion messages which may be generated along the call path for a particular piece of unrecognized information (this would not be the case if each SN passing information on, also generated Confusion messages). + +The notification (Confusion message) contains a Cause indicators parameter with a Cause value indicating if the unrecognized information was a message or parameter(s), the Diagnostic field contains the message or parameter name code(s). + +### I.4 Considerations + +#### I.4.1 Discarding unrecognized messages + +Message Compatibility Information may indicate "*discard message*", for those messages which do not affect the basic state of the protocol, such as the NRM message, otherwise there would be a misalignment between the states of the two protocol machines. This would normally result in the release of the call due to timer expiry. + +This would also be the case if an SN/CMN generates Parameter Compatibility Information indicating "*discard message*". Particular care must be taken in this case because it becomes possible that messages such as Answer may be discarded. + +#### I.4.2 Essential services + +If a service is essential to a call and the information related to that service is unrecognized, then the call should be released. An example of this type of service is the user-to-user essential services. + +#### I.4.3 Non-essential services + +If the service is not essential to a call and the information related to that service is unrecognized, then the information should be discarded. A notification should be requested if an explicit indication needs to be generated when the service is not provided; this notification can then result in the explicit service rejection/notification being generated by the SN/CMN which recognizes the contents of the diagnostic field of the cause parameter contained in the confusion message (this is an SN/CMN which was capable of generating the information which is notified as being unrecognized). An example of this type of service is the user-to-user non-essential services. + +#### I.4.4 Broadband/narrow-band interworking + +Services such as many of the supplementary services are developed to operate in both the broadband and the narrow-band networks; these services should have the broadband/narrow-band interworking indicator set to "pass on". + +However, some information which may relate more to the nature of the networks such as the broadband bearer capability should not be passed from the broadband to the narrow-band network; hence, the broadband/narrow-band interworking indicator should be set to "*Release call*" if the bearer service is one which cannot be supported in the narrow-band. In other cases it may be set to "*discard*" or "*pass on*" dependent on whether the ability of broadband services transiting the narrow-band is supported. + +#### I.4.5 Pass on + +Pass on allows unrecognized information to be passed through an SN/CMN which is acting as an end node. + +The pass on not possible indicator must be examined when pass on has been requested but it is not possible to pass on the information. Pass on is not possible when the protocol on the other side of the SN has a different syntax (message and parameter structure) to BICC (B-ISUP or N-ISUP), or the policing actions performed in the SN prohibit the passing of unrecognized information. When it has been determined that pass on is not possible, another action must be performed such as release of the call or discarding of the information. + +# Bibliography + +- [1] ITU-T Q-series Supplement 31 (2000), TRQ 2141.0: *Signalling Requirements for the Support of Narrowband Services over Broadband Technologies (CS-2).* +- [2] ITU-T Q-series Supplement 32 (2000), TRQ 2141.1: *Signalling Requirements for the Support of Narrowband services via Broadband Transport Technologies, CS-2 (Signalling Flows).* +- [3] ITU-T Q-series Supplement 34 (2000), TRQ 2410: *Signalling requirements, capability set 1 for support of IP bearer control in BICC networks.* +- [4] ITU-T Q-series Supplement 22 (1999), TRQ 3000: *Operation of the Bearer Independent Call Control (BICC) protocol with digital subscriber signalling system No. 2 (DSS2).* +- [5] ITU-T Q-series Supplement 23 (1999), TRQ 3010: *Operation of the Bearer Independent Call Control (BICC) protocol with AAL type 2 signalling protocol (CS-1).* +- [6] ITU-T Q-series Supplement 24 (1999), TRQ 3020: *Operation of the Bearer Independent Call Control (BICC) protocol with broadband integrated services digital network User Part (B-ISUP) protocol for AAL type 1 adaptation.* +- [7] ITU-T Q-series Supplement 36 (2000), TRQ 3030: *Operation of the bearer independent call control (BICC) protocol (CS-2) with IP bearer control protocol (CS-1).* + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1902.6-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1902.6-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2d778388af9c6a0a14b05cc9f763ceccc01a6245 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.6-200107-I_PDF-E/raw.md @@ -0,0 +1,710 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1902.6** + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Bearer Independent Call Control protocol +(Capability Set 2): Generic signalling +procedures for the support of the ISDN user +part supplementary services and for bearer +redirection** + +ITU-T Recommendation Q.1902.6 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation Q.1902.6** + +# **Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures for the support of the ISDN user part supplementary services and for bearer redirection** + +## **Summary** + +This Recommendation specifies the generic signalling procedures and support of the Signalling System No. 7 ISDN User Part (ISUP) supplementary services by the Bearer Independent Call Control (BICC) protocol. The details for the support of the ISUP supplementary services by BICC are described as delta documentation against the ITU-T Q.73x-series Recommendations. In addition, BICC CS-2 procedures for bearer redirection are introduced to optimize the bearer path. + +## **Source** + +ITU-T Recommendation Q.1902.6 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|--------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Delta documentation against ITU-T Q.73x-series Recommendations ..... | 3 | +| 5.1 | Delta Q.730 – Generic procedures..... | 3 | +| 5.2 | Delta Q.731 – Number Identification supplementary services..... | 5 | +| 5.3 | Delta Q.732 – Call Offering supplementary services ..... | 5 | +| 5.3.1 | Handling of Hop Counter with the Call Diversion supplementary services . | 5 | +| 5.3.2 | Handling of Global Call Reference with the Explicit Call Transfer
supplementary services..... | 5 | +| 5.4 | Delta Q.733 – Call Completion supplementary services..... | 5 | +| 5.4.1 | TC-based signalling transport with the Call Completion supplementary
services ..... | 5 | +| 5.5 | Delta Q.734 – Multiparty supplementary services ..... | 5 | +| 5.5.1 | Handling of Global Call Reference with the Multiparty supplementary
services ..... | 6 | +| 5.6 | Delta Q.735 – Community of Interest supplementary services ..... | 6 | +| 5.6.1 | TC-based signalling transport with the Community of Interest
supplementary services..... | 6 | +| 5.7 | Delta Q.736 – Charging supplementary services..... | 6 | +| 5.7.1 | TC-based signalling transport with the Charging supplementary services ... | 6 | +| 5.8 | Delta Q.737 – Additional Information Transfer supplementary services..... | 6 | +| 6 | Bearer Redirection ..... | 6 | +| 6.1 | Introduction..... | 6 | +| 6.2 | Interaction with services invoking bearer redirection..... | 6 | +| 6.3 | Cut-through of new bearer connection ..... | 8 | +| 6.4 | Use of BAT ASE ..... | 8 | +| 6.5 | Procedures..... | 9 | +| 6.5.1 | Indication of Bearer Redirection Capability..... | 9 | +| 6.5.2 | Bearer redirection takes place in the same direction as the call ..... | 9 | +| 6.5.3 | Redirection takes place in the opposite direction to the original call set-up . | 12 | +| 6.5.4 | Special Cases ..... | 12 | +| 6.5.5 | Interaction with Pivot Routing ..... | 14 | +| 6.5.6 | Interaction with Redirection (national use) ..... | 14 | + + + +# **Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures for the support of the ISDN user part supplementary services and for bearer redirection** + +# **1 Scope** + +This Recommendation specifies details about the procedures for the generic signalling procedures and support of the Signalling System No. 7 ISDN User Part (ISUP) supplementary services by the Bearer Independent Call Control (BICC) protocol. + +For the generic signalling procedures, services and functions supported by the BICC protocol (as listed in Table 2/Q.1902.1 [4]) and already supported by the ISUP protocol, the BICC protocol is fully transparent, i.e. the BICC protocol is fully compatible with the ISUP protocol. These generic signalling procedures, services and functions as supported by the ISUP protocol are specified in the ITU-T Q.73x-series Recommendations [1]. + +The details for the support of the ISUP supplementary services by the BICC protocol are described as delta documentation against the ITU-T Q.73x-series Recommendations. [1]. All references in the ITU-T Q.73x-series to the basic call procedures in ITU-T Q.761-Q.764 [2] and Q.767 [3] shall be read as references to the equivalent procedures of the BICC protocol in ITU-T Q.1902.x-family [4]. + +In addition, BICC CS-2 procedures for bearer redirection are introduced to optimize the bearer path. These procedures are described in clause 6. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.73x-series (2000), *ISDN User Part supplementary services generic procedures and clauses with procedures for the individual supplementary services.* +- [2] ITU-T Q.761 to Q.764 (2000), *Specifications of Signalling System No. 7 ISDN User Part (ISUP).* +- [3] ITU-T Q.767 (1991), *Application of the ISDN User Part of CCITT Signalling System No. 7 for international ISDN interconnections.* +- [4] ITU-T Q.1902.1 to Q.1902.4 (2001), *Specifications of the Bearer Independent Call Control Protocol (BICC).* +- [5] ITU-T Q.2150.0 (2001), *Generic Signalling Transport Service.* +- [6] ITU-T Q.2150.1 (2001), *Signalling Transport Convertor on MTP3 and MTP3b.* +- [7] ITU-T Q.765.5 (2000) and its Amendment (2001) for BICC CS-2, *Application Transport Mechanism: Bearer Independent Call Control (BICC).* + +# 3 Definitions + +For BICC specific terminology, the reader is referred to ITU-T Q.1902.1 [4]. + +BC-Anchor node: see 6.2. + +CC-Anchor node: see 6.2. + +Redirecting-from node: see 6.2. + +Redirecting-to node: see 6.2. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|---------------------------------------------| +| 3PTY | Three-Party Service | +| ACM | Address Complete Message | +| APM | Application Transport Message | +| APP | Application Transport Parameter | +| ASE | Application Service Element | +| BAT | Bearer Association Transport | +| BCF | Bearer Control Function | +| BICC | Bearer Independent Call Control | +| BIWF | Bearer InterWorking Function | +| CCBS | Completion of Calls to Busy Subscriber | +| CCNR | Completion of Calls on No Reply | +| CD | Call Deflection | +| CFB | Call Forwarding Busy | +| CFNR | Call Forwarding No Reply | +| CFU | Call Forwarding Unconditional | +| CMN | Call Mediation Node | +| CON | Connect message | +| CONF | Conference Calling | +| CSF | Call Service Function | +| CUG | Closed User Group | +| ECT | Explicit Call Transfer | +| GSN | Gateway Serving Node | +| IAM | Initial Address Message | +| ISDN | Integrated Services Digital Network | +| ISN | Intermediate Serving Node | +| ISUP | ISDN User Part | +| ITCC | International Telecommunication Charge Card | +| PCI | Protocol Control Indicator | + +| | | +|------|------------------------------------| +| REL | Release message | +| RLC | Release Complete message | +| ROSE | Remote Operations | +| SCCP | Signalling Connection Control Part | +| SN | Serving Node | +| TC | Transaction Capabilities | +| TSN | Transit Serving Node | + +# 5 Delta documentation against ITU-T Q.73x-series Recommendations + +This clause includes exceptions and additions against the ITU-T Q.73x-series [1] for the generic procedures and clauses with procedures for the individual supplementary services. + +## 5.1 Delta Q.730 – Generic procedures + +NOTE – The numbering in this clause refers to the clause numbering in ITU-T Q.730 [1]. + +# 0 Introduction + +## 0.1 Scope + +For information. + +## 0.2 References + +For information. + +### 0.3 Terms and definitions + +For information. + +### 0.4 Abbreviations + +For information. + +# 1 General + +Applicable. + +### 1.1 Exceeding the maximum message length + +Applicable. The maximum message length support by BICC depends on the capabilities of the signalling transport network. For further see details ITU-T Q.2150.0 [5]. + +## 1.2 Network specific facilities (national use) + +Applicable. + +### 1.2.1 Sending unsolicited information (national use) + +Applicable. + +## 1.3 Generic procedures + +#### 1.3.1 Service activation + +Applicable. + +#### 1.3.2 General digit transfer (national use) + +Applicable. + +#### *1.3.3 Remote Operations service (ROSE) capability (national use)* + +Applicable. + +#### *1.3.4 Generic notification procedure* + +Applicable. + +#### *1.3.5 Generic number transfer* + +Applicable. + +#### *1.3.6 Pivot Routing* + +Applicable. + +These procedures only apply to signalling relations between ISN/TSN/GSN type of nodes, i.e. both call and bearer need to be controlled in order to have both the call and the bearer rerouted. With BICC the additional bearer redirection procedure may be supported for bearer optimization, see clause 6. These procedures use SS No. 7 signalling point code relations because the pivot routing procedures are based on SS No. 7 signalling point codes. For further details of the signalling transport network capabilities, see ITU-T Q.2150.1 [6]. + +With regard to the Global Call Reference procedure (see 8.18/Q.1902.4 [4]) the Global Call Reference shall be reused by the SN performing the pivot routing as received with the incoming call. + +#### *1.3.7 Redirection (national use)* + +Applicable. + +These procedures only apply to signalling relations between ISN/TSN/GSN type of nodes, i.e. both call and bearer need to be controlled in order to have both the call and the bearer rerouted. With BICC the additional bearer redirection procedure may be supported for bearer optimization, see clause 6. These procedures use SS No. 7 signalling point code relations because the redirection procedures are based on SS No. 7 signalling point codes. For further details of the signalling transport network capabilities, see ITU-T Q.2150.1 [6]. + +With regard to the Global Call Reference procedure (see 8.18/Q.1902.4 [4]) the Global Call Reference shall be reused by the SN performing the redirection as received with the incoming call. + +#### *1.3.8 Relay methods for non-circuit related signalling* + +Applicable. + +NOTE – For further information the reader is referred to ITU-T Q-series Supplement 38 (TRQ.2600) for further details about the signalling transport options for TC-based services. + +### *1.4 End-to-end signalling* + +With BICC, this part of ITU-T Q.730 documentation is not supported any further, including the non-support of the associated definitions and codings in ITU-T Q.1902.2 and Q.1902.3 [4]. + +### *1.5 Layout of service Recommendations* + +For information. + +### *1.6 List of supplementary services* + +See 5.2 through 5.8. + +### *1.7 Association of supplementary services to bearer services and teleservices* + +For information. + +### 1.8 *Definition of supplementary services* + +For information. + +### *Appendix I – Contents of the interface elements between ISUP and SCCP* + +Not supported. + +## 5.2 **Delta Q.731 – Number Identification supplementary services** + +Applicable. + +## 5.3 **Delta Q.732 – Call Offering supplementary services** + +Applicable. Since the execution of these supplementary services involve the bearer, these services need the control of both the call and the bearer in ISN/TSN/GSN type of nodes. + +### 5.3.1 **Handling of Hop Counter with the Call Diversion supplementary services** + +- Q.732.2 Call Forwarding Busy (CFB) +- Q.732.3 Call Forwarding No Reply (CFNR) +- Q.732.4 Call Forwarding Unconditional (CFU) +- Q.732.5 Call Deflection (CD) + +For BICC the following handling of the Hop Counter (see 8.9/Q.1902.4 [4]) applies with regard to the Call Diversion supplementary services. A call forwarding SN receiving a Release message with cause #25 "Exchange routing error", shall notify the management system of the routing error and provide the called party number, identity of the succeeding CSF, and the forwarding number. Cause value #31 "normal unspecified", shall be returned to the preceding CSF. + +NOTE – The method of identifying the succeeding/preceding CSF is for further study. + +### 5.3.2 **Handling of Global Call Reference with the Explicit Call Transfer supplementary services** + +- Q.732.7 Explicit Call Transfer (ECT). + +With regard to the Global Call Reference procedure (see 8.18/Q.1902.4 [4]) the Global Call Reference associated with the call on the transferred leg is for further study. + +## 5.4 **Delta Q.733 – Call Completion supplementary services** + +Applicable. Since the execution of these supplementary services involve the bearer, these services need the control of both the call and the bearer in ISN/TSN/GSN type of nodes. + +### 5.4.1 **TC-based signalling transport with the Call Completion supplementary services** + +- Q.733.3 Completion of Calls to Busy Subscriber (CCBS) +- Q.733.5 Completion of Calls on No Reply (CCNR) + +NOTE – For further information the reader is referred to ITU-T Q-series Supplement 38 (TRQ.2600) for further details about the signalling transport options for TC-based services. + +## 5.5 **Delta Q.734 – Multiparty supplementary services** + +Applicable. As for the execution of these supplementary services the bearer is involved, these services need the control of both the call and the bearer in ISN/TSN/GSN type of nodes. + +### **5.5.1 Handling of Global Call Reference with the Multiparty supplementary services** + +- Q.734.1 Conference Calling (CONF) +- Q.734.2 Three-Party Service (3PTY) + +With regard to the Global Call Reference procedure (see 8.18/Q.1902.4 [4]) the Global Call Reference associated with the calls on the multiparty legs is for further study. + +### **5.6 Delta Q.735 – Community of Interest supplementary services** + +Applicable. + +### **5.6.1 TC-based signalling transport with the Community of Interest supplementary services** + +- Q.735.1 Closed User Group (CUG) with centralized administration of CUG data + +NOTE – For further information the reader is referred to ITU-T Q-series Supplement 38 (TRQ.2600) for further details about the signalling transport options for TC-based services. + +## **5.7 Delta Q.736 – Charging supplementary services** + +Applicable. + +### **5.7.1 TC-based signalling transport with the Charging supplementary services** + +- Q.736.1 International Telecommunication Charge Card (ITCC) + +NOTE – For further information the reader is referred to ITU-T Q-series Supplement 38 (TRQ.2600) for further details about the signalling transport options for TC-based services. + +## **5.8 Delta Q.737 – Additional Information Transfer supplementary services** + +Applicable. + +### **6 Bearer Redirection** + +## **6.1 Introduction** + +Bearer redirection is a generic mechanism for optimizing the bearer path when an endpoint of a call changes due to the operation of an application layer service. + +For example, in the case of the ISDN supplementary service Call Forwarding No Reply (CFNR), a call and bearer connection is initially made to the Served User, and subsequently a new connection is made to the Forwarded-To User. By default, the new connection would be made from the Served User's SN to the Forwarded-To user's SN, placing a requirement on the Served User's SN to tandem the bearer connection. + +Bearer redirection provides the capability for the new bearer connection to be made directly from the Calling User's SN to the Forwarded-To User's SN whilst the call control path is tandemed through the Served User's SN. This is assuming there is bearer connectivity directly between these SNs i.e. that they are part of the same network. Otherwise the mechanism is limited to operation between SNs in a single network. + +## **6.2 Interaction with services invoking bearer redirection** + +The bearer redirection procedure itself is not responsible for addition or removal of call legs between the nodes. However, call legs may be added or removed by the service which is invoking bearer redirection (e.g. when Call Forwarding adds a new call leg to the Forwarding-To node). The service + +then makes use of bearer redirection to optimize the bearer. Hence the description of bearer redirection must take account of the addition/removal of call legs by the service. + +Bearer redirection is therefore modelled using four types of node, each of which provides a particular piece of functionality required for performing bearer redirection. The four node types are as follows: + +**CC-Anchor node:** The SN or CMN at which the service invoking bearer redirection is operating. This node serves as an anchor point for the call control during the bearer redirection procedure. A CC-Anchor node remains in the call path for the duration of the call. How the CC-Anchor node determines that bearer redirection is required is beyond the scope of this Recommendation. + +**BC-Anchor node:** The SN which serves as an anchor point for the bearer control during the bearer redirection procedure. Both old and new bearer connections terminate at the BC-Anchor node. + +**Redirecting-from node:** The SN to which the call and bearer are initially connected, before redirection. + +**Redirecting-to node:** The SN to which the call and bearer are subsequently connected, after the redirection. + +The node types are functional entities and some may be combined together in a physical node in different ways, depending on the requirements of the service. For example, if the service does not require the removal of any call leg, but does require the addition of a new call leg, then the CC-Anchor node and Redirecting-from node will be combined. This is illustrated in Figure 1, and is the configuration which would operate, for example, in the case of Call Forwarding. + +![Figure 1/Q.1902.6 – CC-Anchor and Redirecting-from nodes combined. The diagram shows two states: 'Before' and 'After'. In the 'Before' state, a BC-Anchor node is connected to a combined CC-Anchor and Redirect-from node by a dashed line (Bearer). A separate Redirect-to node is shown below. In the 'After' state, the BC-Anchor node is connected to the combined CC-Anchor and Redirect-from node by a solid line (Call). A dashed line (Bearer) connects the BC-Anchor node to the Redirect-to node. A solid line (Call) also connects the combined CC-Anchor and Redirect-from node to the Redirect-to node. A legend at the bottom left indicates that a solid line represents a 'Call' and a dashed line represents a 'Bearer'. The text 'T11111950-01' is visible in the bottom right corner of the diagram area.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +Before + +After + +T11111950-01 + +—— Call + +..... Bearer + +Figure 1/Q.1902.6 – CC-Anchor and Redirecting-from nodes combined. The diagram shows two states: 'Before' and 'After'. In the 'Before' state, a BC-Anchor node is connected to a combined CC-Anchor and Redirect-from node by a dashed line (Bearer). A separate Redirect-to node is shown below. In the 'After' state, the BC-Anchor node is connected to the combined CC-Anchor and Redirect-from node by a solid line (Call). A dashed line (Bearer) connects the BC-Anchor node to the Redirect-to node. A solid line (Call) also connects the combined CC-Anchor and Redirect-from node to the Redirect-to node. A legend at the bottom left indicates that a solid line represents a 'Call' and a dashed line represents a 'Bearer'. The text 'T11111950-01' is visible in the bottom right corner of the diagram area. + +Figure 1/Q.1902.6 – CC-Anchor and Redirecting-from nodes combined + +Conversely, if the service requires a call leg to be removed, without the creation of a new call leg, the CC-Anchor node and Redirecting-to node are combined. This is shown in Figure 2. + +![Figure 2/Q.1902.6 – CC-Anchor and Redirecting-to nodes combined. The diagram shows two states: 'Before' and 'After'. In the 'Before' state, a 'BC-Anchor' node is connected to a 'Redirect-From' node by a dotted line (Bearer) and to a combined 'CC-Anchor' and 'Redirect-To' node by a solid line (Call). In the 'After' state, the 'BC-Anchor' node is connected to the 'Redirect-From' node by a dotted line (Bearer) and to the combined 'CC-Anchor' and 'Redirect-To' node by a solid line (Call). A legend indicates that solid lines represent 'Call' and dotted lines represent 'Bearer'. The identifier 'T11111960-01' is present in the bottom right of the 'After' state.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +Before + +After + +T11111960-01 + +—— Call + +..... Bearer + +Figure 2/Q.1902.6 – CC-Anchor and Redirecting-to nodes combined. The diagram shows two states: 'Before' and 'After'. In the 'Before' state, a 'BC-Anchor' node is connected to a 'Redirect-From' node by a dotted line (Bearer) and to a combined 'CC-Anchor' and 'Redirect-To' node by a solid line (Call). In the 'After' state, the 'BC-Anchor' node is connected to the 'Redirect-From' node by a dotted line (Bearer) and to the combined 'CC-Anchor' and 'Redirect-To' node by a solid line (Call). A legend indicates that solid lines represent 'Call' and dotted lines represent 'Bearer'. The identifier 'T11111960-01' is present in the bottom right of the 'After' state. + +**Figure 2/Q.1902.6 – CC-Anchor and Redirecting-to nodes combined** + +The procedures here describe the most general case where all of the functional entities are located in separate physical nodes. By modelling the bearer redirection in this way a completely generic mechanism is obtained which meets a range of possible service scenarios. + +When functional entities are combined, the links between them are not externally visible. From a protocol point of view this simply means that the signalling which would have taken place between such entities is internalized in the physical node. + +## 6.3 Cut-through of new bearer connection + +Two possibilities are provided for the cut-through of the new bearer connection at the BC-Anchor node: + +- Immediate Cut-Through. +- Late Cut-Through. + +In the case of Immediate Cut-Through, the new bearer connection is cut-through immediately it is established, according to the procedures for standard bearer set-up. + +In the case of Late Cut-Through, cut-through of the new bearer connection is under control of the CC\_Ancehor node which sends an explicit cut-through request to the BC-Anchor to trigger cut-through. + +## 6.4 Use of BAT ASE + +Bearer redirection makes use of the services of the BAT ASE described in ITU-T Q.765.5 to transport bearer redirection related information between the nodes. The services of the BAT ASE are accessed by means of primitives (such as "BICC\_data") which are defined in ITU-T Q.765.5 [7]. + +## 6.5 Procedures + +### 6.5.1 Indication of Bearer Redirection Capability + +An SN that supports the Bearer Control Anchor node capabilities shall indicate this within the IAM and first backwards Call Control message (ACM or CON) of the original call by including the Bearer Redirection Capability Information element within the BAT APP within those messages. + +In the case of ISNs and GSNs, this indication may be included only if the node itself supports the Bearer Redirection procedures for a BC-Anchor node. In the case of TSNs it may additionally be included if received from the preceding or succeeding node and if the procedures of 6.5.2.3 are supported. (A CMN has no Bearer Interworking Function and so cannot perform the Bearer Control Anchor function.) + +If the Late Cut-Through option is supported, the Late Cut-Through Indicator shall be set to "*Late Cut-Through Supported*", otherwise it shall be set to "*Late Cut-Through Not Supported*". + +The compatibility information of the Bearer Redirection Capability shall be set so as to cause the information element to be discarded by nodes that do not support Bearer Redirection. + +### 6.5.2 Bearer redirection takes place in the same direction as the call + +##### 6.5.2.1 Actions at a CC-Anchor node + +An invoking application at the CC-Anchor node may determine a new endpoint for the call at any time (either before or after ACM). If the Bearer Redirection Capability Information element has been received from the preceding node, the application may then invoke bearer redirection. How an application determines whether it is to be the CC-Anchor node for the call, or whether bearer redirection is required, is beyond the scope of this Recommendation. + +The invoking application is responsible for storing any relevant IAM information required for the service. This information may be released when no further bearer redirections are required to be invoked by the application. + +Bearer redirection is invoked at the CC-Anchor node which signals invocation to the BC-Anchor node. The new bearer will be established between this BC-Anchor and the Redirecting-to node. + +Bearer redirection involves the moving of one bearer endpoint from one destination to another. At any one time, however, only one of these destinations is considered to be the real bearer endpoint for the call. The CC-Anchor node controls the cut-over point, that is the point in time at which the bearer endpoint changes from the initial destination to the final destination. + +###### 6.5.2.1.1 Negotiation of bearer redirection capabilities + +When the CC-Anchor node has decided to invoke bearer redirection, an APM is sent to the preceding node with the action indicator in the BICC\_Data request primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*Redirect Backwards Request*" or "*Redirect Forwards Request*" as appropriate depending on the capability of the Redirecting-to node, i.e. the CC-Anchor node determines whether the Forward or Backward procedures are to be used towards the Redirecting-to node in a way similar to how a node initiating a new call determines whether the Forwards or Backwards procedure should be used towards that node. The Bearer Redirection Indicators are also included in the BICC\_Data request primitive. + +If Late Cut-Through is desired and the Late Cut-Through indicator received in the Bearer Redirection Capability Information Element in the IAM was set to "*Late Cut-Through Supported*", then a Bearer Redirection Indicator "*Late Cut-Through Requested*" shall be included. + +On receipt of a BICC\_Data indication primitive (corresponding to an APM received from the preceding node (BC-Anchor)) with action indicator set to "*Connect Backward*" or "*Connect Forward*", CC-Anchor node the procedures of 6.5.2.1.2 followed by 6.5.2.1.3 apply. + +###### 6.5.2.1.2 Set-up of new call leg and bearer connection + +To initiate set-up of the new call leg and bearer connection the service at the CC-Anchor node uses the stored IAM information to construct an IAM to be sent to the Redirecting-to node. The APP with Application Context Identifier "BAT ASE" included in the IAM shall only include the information elements from the APP received by the CC-Anchor node in 6.5.2.1.1. + +The CC-Anchor node subsequently behaves as follows: + +- BAT ASE information received from the Redirecting-from node is passed on to the BC-Anchor according to standard CMN procedures. +- BAT ASE information received from the Redirecting-to node is passed on to the BC-Anchor according to standard CMN procedures but with a Bearer Redirection Indicator "*new connection identifier*" included. +- BAT ASE information received from the BC-Anchor node containing a Bearer Redirection Indicator "*new connection identifier*" is passed on to the Redirecting-to node according to standard CMN procedures but with the Bearer Redirection Indicator "*new connection identifier*" removed. +- BAT ASE information received from the BC-Anchor node not containing a Bearer Redirection Indicator "*new connection identifier*" is passed on to the Redirecting-from node according to standard CMN procedures. + +The behaviour of the CC-Anchor node with respect to other messages/information depends on the application invoking Bearer redirection. + +The CC-Anchor node waits for a BICC\_Data indication primitive (corresponding to an APM) with Action Indicator set to "*Connected*" or with Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect bearer connected*" to be received from the BC-Anchor node. In the former case, this indication is passed onwards to the Redirecting-to node. + +In the case of Late Cut-Through, when Cut-through of the new connection is required, the CC-Anchor node shall send a BICC\_Data request primitive (in association with any suitable message) with Action indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect cut-through request*" towards the BC-Anchor node. + +The new bearer set-up procedure is now complete. + +###### 6.5.2.1.3 Release of old call leg and bearer connection + +When the controlling application requires the release of the old call leg and bearer to the Redirecting-from node, the CC-Anchor node sends an APM to the preceding node with the action indicator in the BICC\_Data request primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect bearer release request*". + +On receipt of an APM from the preceding node with the action indicator in the BICC\_Data indication primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect bearer release proceed*", a REL message is sent to the Redirecting-from node as per the normal release procedures. The release cause value is determined by the application. The CC-Anchor node awaits receipt of the RLC from the Redirecting-from node. + +On receipt of the RLC from the Redirecting-from node, an APM is sent to the preceding node with the action indicator in the BICC\_Data request primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect bearer release complete*". + +#### 6.5.2.2 Actions at a BC-Anchor + +###### 6.5.2.2.1 Negotiation of bearer redirection capabilities + +On receipt of a BICC\_Data indication primitive (corresponding to an APM received from the succeeding node) with action indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect forwards request*" or "*redirect backwards request*", the node determines whether it will perform the BC-Anchor node functions, or, in the case that Bearer Redirection Capabilities Information Element was received from the preceding node, whether the request will be sent to the preceding node. How this determination is made is beyond the scope of this Recommendation. + +In the case that the BC-Anchor node functions are to be performed, the normal BICC outgoing set-up procedures for outgoing bearer set-up (clause 7/Q.1902.4) are followed with the following exceptions: + +- 1) The BC-Anchor node selects the BIWF which is already associated with the call. +- 2) An IAM is not sent. Instead an APM is sent to the succeeding node containing the BAT ASE information that would have been sent in the IAM, other IAM parameters are not included. + +###### 6.5.2.2.2 Set-up of new bearer connection + +###### 6.5.2.2.2.1 Handling of APP parameters + +Subsequent to the procedures of 6.5.2.2.1, receipt of any message containing an APP parameter with Application Context Identifier "BAT ASE" shall be handled as follows: + +- messages containing Bearer Redirection Indicator "*new connection identifier*" shall be handled by the normal BICC outgoing call set-up procedures with respect to the new connection; +- messages not containing Bearer Redirection Indicator "*new connection identifier*" shall be handled by the procedures for existing bearers with respect to the old connection. + +Where it is required to send an APP parameter relating to the old connection, this shall be sent as for the non-bearer redirection case. + +Where it is required to send an APP parameter relating to the new connection, a Bearer Redirection Indicator "*New connection identifier*" shall also be included. + +###### 6.5.2.2.2.2 Confirmation and Cut-Through of the new bearer connection + +If the Bearer Redirection Indicators information element received with the bearer redirection request indication in 6.5.2.2.1 above did not include "*late cut-through requested*", then the newly established bearer connection is cut-through immediately it is established, according to the normal connection set-up procedures. + +On completion of the outgoing set-up procedure then except in the case of Forward Set-up with Connect Type set to "*Forwards Notify*", the BC-Anchor node shall send a BICC\_Data request primitive with Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect bearer connected*" to the CC-Anchor node. + +In the case of Forward set-up with Connect Type set to "*Forwards Notify*" the BC-Anchor node shall behave as described in the normal Forwards set-up procedures. + +If the Bearer Redirection Indicators information element received with the bearer redirection Request indication in 6.5.2.2.1 above indicated "*late cut-through requested*", then, on receipt of a BICC\_Data indication primitive (corresponding to any message) with action indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect cut-through request*", the BC-Anchor node cuts through the new bearer connection. + +###### 6.5.2.2.3 Release of old bearer connection + +On receipt of an APM from the succeeding node with the action indicator in the BICC\_Data indication primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect release request*" the BC-Anchor requests the BCF to disconnect the internal through-connection of the old bearer path connection between the BC-Anchor and the Redirecting-from node. A normal cause value is passed from the CSF to the BCF. + +At the same time as the start of the release of the switched path, the BC-Anchor sends an APM to the succeeding node with the action indicator in the BICC\_Data request primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect release proceed*". + +The BC-Anchor awaits receipt of an APM from the succeeding node with the action indicator in the BICC\_Data indication primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect release complete*". On receipt of this indication, the BC-Anchor instructs the BCF to release remaining resources associated with the old bearer connection. + +##### 6.5.2.3 Actions at an intermediate node which is not a BC-Anchor or CC-Anchor node + +An intermediate node that is not a BC-Anchor or a CC-Anchor node shall pass on unchanged all received indications related to bearer redirection. + +In the case that the Bearer Redirection Capability information element was sent to the succeeding node at call set-up, then on receipt of a BICC\_Data indication from the preceding node with Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect release proceed*", the node shall note that Bearer Release should be expected. Subsequent to receipt of this Bearer Release, the node shall behave according to the CMN procedures. + +NOTE – In the case that the Bearer Redirection Capability information element was not sent to the succeeding node at call set-up, then this scenario will not occur, since the succeeding node will not invoke Bearer Redirection. + +##### 6.5.2.4 Actions at a Redirecting-to node + +A Redirecting-to node shall follow the normal call set-up procedures described in ITU-T Q.1902.4 [4]. + +##### 6.5.2.5 Actions at a Redirecting-from node + +A Redirecting-from node shall follow the normal call set-up procedures described in ITU-T Q.1902.4 [4]. + +#### 6.5.3 Redirection takes place in the opposite direction to the original call set-up + +The procedures in 6.5.2 apply with the word "preceding" replaced by "succeeding" and vice versa. + +#### 6.5.4 Special Cases + +##### 6.5.4.1 Handling of multiple bearer redirection requests + +The following procedures ensure that multiple bearer redirection requests sent along the same call leg are handled in series rather than in parallel. + +A CC-Anchor node may not initiate more than one bearer redirection procedure at a time for a given call. + +A CC-Anchor node that receives a bearer redirection request from the succeeding node while waiting for the response to a bearer redirection request sent to the preceding node shall return to the succeeding node a BICC\_Data indication primitive (corresponding to an APM) with the Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect temporary reject*". + +A CC-Anchor node that receives a bearer redirection request from the preceding node while waiting for the response to a bearer redirection request sent to the succeeding node shall return to the preceding node a BICC-Data indication primitive (corresponding to an APM) with the Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*redirect temporary reject*". + +A CC-Anchor node that receives a bearer redirection request from the preceding node while waiting for the response to a bearer redirection request sent to the preceding node shall return to the preceding node a BICC-Data indication primitive (corresponding to an APM) with the Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*bearer redirect temporary reject*". + +A node that receives a bearer redirection request from the succeeding node while waiting for the response to a bearer redirection request sent to the succeeding node shall act on the received bearer redirection request received according to 6.5.2.2. + +##### **6.5.4.2 Temporary Reject** + +If the request for Bearer Redirection cannot be honoured by the BC-Anchor node, it shall send to the CC-Anchor node a BICC-Data indication primitive (corresponding to an APM) with the Action Indicator set to "*bearer redirect*" and including a Bearer Redirection Indicator "*redirect temporary reject*". + +A "*redirect temporary reject*" indication received by an intermediate node shall be passed on unmodified. + +If the indication is received by the CC-Anchor node originating the request then the invoking application shall take appropriate action (which could involve requesting bearer redirection again after a suitable period of time). + +##### **6.5.4.3 Bearer redirection abandoned by CC-Anchor node** + +Prior to the procedures of 6.5.2.1.3, the service at the CC-Anchor node may determine that the bearer redirection be abandoned, returning to the old bearer. + +###### **6.5.4.3.1 Actions at the CC-Anchor node** + +When the service at the CC-Anchor node determines that the bearer redirection should be abandoned, the procedures of 6.5.2.1.3 are followed except that the Bearer Redirection Indicator "*new connection identifier*" is included in each APM sent by the CC-Anchor node to the BC-Anchor. + +###### **6.5.4.3.2 Actions at the BC-Anchor node** + +On receipt of an APM from the succeeding node with the action indicator in the BICC\_Data indication primitive set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*Redirect Release Request*" and including Bearer Redirection Indicator "*new connection identifier*", the procedures of 6.5.2.2.3 are followed with respect to the new bearer. + +The Bearer Redirection Indicator "*new connection identifier*" is included in each APM sent by the BC-Anchor to the CC-Anchor node. + +#### **6.5.4.4 Bearer redirection failure at BC-Anchor Node** + +###### **6.5.4.4.1 Actions at the BC-Anchor node** + +Subsequent to the procedures of 6.5.2.2.1, if the new connection cannot be established at the BC-Anchor node, a BICC\_Data request shall be sent to the CC-Anchor node with Action Indicator set to "*Bearer Redirect*" and including Bearer Redirection Indicator "*Redirect Failure*". + +###### 6.5.4.4.2 Actions at the CC-Anchor node + +On receipt of a BICC\_Data indication (corresponding to an APM) from the BC-Anchor node containing a Bearer Redirection Indicator "*Redirect Failure*", the call leg towards the Redirecting-to node shall be released according to the standard call release procedures in ITU-T Q.1902.4 [4]. + +Further action (e.g. re-attempt of bearer redirection) may be taken according to the service at the CC-Anchor node. + +##### 6.5.4.5 Unexpected Bearer Redirection Request + +If a node receives a Bearer Redirection Request which is unexpected (e.g. because the Bearer Redirection Capabilities Information Element was not included in the BAT APP in the IAM) then this is handled according to the standard procedures for unexpected BAT ASE information described in ITU-T Q.1902.4 [4]. + +##### 6.5.4.6 Unexpected New Connection Identifier + +The Bearer Redirection Indication "*New Connection Identifier*" is only meaningful in the state where two bearer connections exist, or where one exists and the other is in the process of being set up. If this indication is received at other times, it shall be treated as unrecognized according to the procedures of ITU-T Q.1902.4 [4]. + +#### 6.5.5 Interaction with Pivot Routing + +Once bearer redirection has been invoked, Pivot Routing to redirect the call control to the same location may disconnect the call. Therefore, for any node that offers support of bearer redirection on a given call: + +- a) if an offer of Pivot Routing is received from a previous SN, it shall be passed forward unchanged; +- b) if an invocation of Pivot Routing is received, it shall be passed unchanged and the SN shall not act on the invocation; +- c) an originating SN shall not make simultaneous offers of Pivot Routing and bearer redirection. + +#### 6.5.6 Interaction with Redirection (national use) + +Once bearer redirection has been invoked, the use of Redirection to redirect the call control to the same location will temporarily interrupt the bearer path between the calling and called parties. + +# Bibliography + +- ITU-T Q-series Recommendations Supplement 38 (2001), *TRQ.2600: BICC signalling transport requirements – Capability Set 1*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c +size 8232 diff --git a/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2785a7c2e4e678d53e1ce8504b9f4a65772bae9f --- /dev/null +++ b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd70c21cd338fdea6ea1776daad02a3c92eb6160ab7584ab470aaf8cc710ef11 +size 15368 diff --git a/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f97b04fbd1d5effb0a2f88dbcac23b05cde6dcb --- /dev/null +++ b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:370ad4104792fd3bfd2a4fe7227d17e1064820be5010b7be452de1a6c2f3f0d7 +size 43210 diff --git a/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e3cdff223d94d91ba45e3817e1f7ffa36a43bb70 --- /dev/null +++ b/marked/Q/T-REC-Q.1922.2-200107-I_PDF-E/raw.md @@ -0,0 +1,220 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1922.2** + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Interaction between the Intelligent Network +Application Protocol Capability Set 2 and the +Bearer Independent Call Control protocol** + +ITU-T Recommendation Q.1922.2 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Interaction between the Intelligent Network Application Protocol Capability Set 2 and the Bearer Independent Call Control protocol** + +## **Summary** + +This Recommendation defines the signalling interaction between the Bearer Independent Call Control (BICC) protocol and the IN Application Protocol Capability Set 2 (INAP CS-2) based on the interaction between INAP and the ISDN User Part (ISUP) protocol of Signalling System No. 7. + +### **Source** + +ITU-T Recommendation Q.1922.2 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|---|----------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | General considerations..... | 3 | +| 6 | Interaction considerations ..... | 3 | + + + +## **Interaction between the Intelligent Network Application Protocol Capability Set 2 and the Bearer Independent Call Control protocol** + +## **1 Scope** + +This Recommendation defines the signalling interaction between the Bearer Independent Call Control (BICC) protocol and the IN Application Protocol Capability Set 2 (INAP CS-2) based on the interaction between INAP and the ISDN User Part (ISUP) protocol of Signalling System No. 7, i.e. to support IN services in a BICC environment. + +BICC is the protocol defined in ITU-T Q.1902.1 to Q.1902.4 [4]. INAP is the protocol defined in ITU-T Q.1228 [2]. ISUP is the protocol defined in ITU-T Q.761 to Q.764 [1]. + +This Recommendation builds upon: + +- the signalling interaction between the IN Application Protocol Capability Set 2 (INAP CS-2) and the ISDN User Part (ISUP) protocol of Signalling System No. 7 as defined in ITU-T Q.1601 [3]; and +- the signalling interworking between the Bearer Independent Call Control (BICC) protocol and the ISDN User Part (ISUP) protocol of Signalling System No. 7 as defined in ITU-T Q.1912.1 [5]. + +The scope of this Recommendation is shown in Figure 1. + +![Diagram illustrating the scope of the recommendation. It shows a stack of protocols: INAP (top), BICC (middle), and BIWF (bottom) containing BCF-N. The INAP and BICC components are enclosed in a dashed box labeled 'Scope of this Recommendation'. The INAP component is also labeled 'Scope of ITU-T Q.1601'. The BICC component is labeled 'Scope of ITU-T Q.1912.1'. Arrows indicate interactions: BICC (left and right), BICC (left and right), and Bearer control (right). The entire stack is labeled 'ISN' on the left and 'CSF-N' on the right.](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +Diagram illustrating the scope of the recommendation. It shows a stack of protocols: INAP (top), BICC (middle), and BIWF (bottom) containing BCF-N. The INAP and BICC components are enclosed in a dashed box labeled 'Scope of this Recommendation'. The INAP component is also labeled 'Scope of ITU-T Q.1601'. The BICC component is labeled 'Scope of ITU-T Q.1912.1'. Arrows indicate interactions: BICC (left and right), BICC (left and right), and Bearer control (right). The entire stack is labeled 'ISN' on the left and 'CSF-N' on the right. + +T11112040-01 + +**Figure 1/Q.1922.2 – Scope of this Recommendation** + +ITU-T Q.1601 [3] only considers the case where the SSP is located at a transit level. As a consequence, this could lead to limitations for services (e.g. no support of line based triggers). + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.761 to Q.764 (1999), *Specifications of Signalling System No. 7– ISDN user part (ISUP)*. +- [2] ITU-T Q.1228 (1997), *Interface Recommendation for intelligent network Capability Set 2*. +- [3] ITU-T Q.1601 (1999), *Signalling System No. 7– Interaction between N-ISDN and INAP CS-2*. +- [4] ITU-T Q.1902.1 to Q.1902.4 (2001), *Specifications of the Bearer Independent Call Control protocol (BICC)*. +- [5] ITU-T Q.1912.1 (2001), *Interworking between Signalling System No. 7– ISDN user part (ISUP) and the Bearer Independent Call Control protocol*. + +## 3 Definitions + +For BICC specific terminology, the reader is referred to ITU-T Q.1902.1 [4]. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|-------------------------------------| +| BCF-N | Bearer Control Nodal Function | +| BICC | Bearer Independent Call Control | +| BIWF | Bearer InterWorking Function | +| CSF-N | Call Service Nodal Function | +| IN | Intelligent Network | +| INAP | IN Application Protocol | +| ISDN | Integrated Services Digital Network | +| ISN | Interface Serving Node | +| ISUP | ISDN User Part | +| SN | Serving Node | +| SSP | Service Switching Point | + +## 5 General considerations + +This clause describes the interaction principle between INAP and BICC based on the interaction between ISUP and INAP concatenated with the interworking between ISUP and BICC. Figure 2 provides the functional grouping of the entities involved. + +![Functional description of the interaction configuration diagram](562f471e8153729557e6a4ee6343c32c_img.jpg) + +The diagram illustrates the functional grouping of entities within a CSF-N (Core Switching Function - N) block. It shows a vertical stack of four components: INAP at the top, followed by Q.1601, then Q.1912.1, and BICC at the bottom. Each component is connected to the one below it by a double-headed vertical arrow, indicating bidirectional interaction. The BICC component has two horizontal double-headed arrows extending from its left and right sides, representing its interaction with external entities. Below the diagram, the identifier 'T11112050-01' is displayed. + +Functional description of the interaction configuration diagram + +**Figure 2/Q.1922.2 – Functional description of the interaction configuration** + +## 6 Interaction considerations + +The interaction between INAP and BICC shall act according to the interaction between ISUP and INAP in ITU-T Q.1601 [3] concatenated with the interworking between ISUP and BICC in ITU-T Q.1912.1 [5]. + +NOTE – In ISUP, a dependency is specified between the sending of the InitialDP operation and the Continuity message. As in a BICC environment the continuity procedures are used in a different way (to indicate successful establishment of the bearer up to the preceding SN); this dependency is for further study. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1922.4-200212-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1922.4-200212-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9d4f69c1f62c8d235519b1751e08bce3eecbf8fb --- /dev/null +++ b/marked/Q/T-REC-Q.1922.4-200212-I_PDF-E/raw.md @@ -0,0 +1,2222 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1922.4** + +(12/2002) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Interaction between the Intelligent Network +application CS-4 protocol and the Bearer +Independent Call Control protocol** + +ITU-T Recommendation Q.1922.4 + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|---------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 | Q.120-Q.139 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 | Q.140-Q.199 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation Q.1922.4** + +# **Interaction between the Intelligent Network application CS-4 protocol and the Bearer Independent Call Control protocol** + +## **Summary** + +This Recommendation specifies procedures in order to provide interaction between the Bearer Independent Call Control (BICC) and INAP CS-4, i.e. to support IN services in an ISDN environment. + +It also specifies ISUP/INAP CS-4 interaction procedures as exceptions to BICC/INAP interaction procedures (see Annex B). + +The interaction between other signalling systems and INAP can be found by consulting the relevant interworking Recommendation to the BICC in combination with the BICC/INAP interaction Recommendation. + +## **Source** + +ITU-T Recommendation Q.1922.4 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 December 2002. + +## **Keywords** + +BICC, INAP, SS7, SSP. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|------|---------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Description..... | 4 | +| 6.1 | Establishment of bearer-related connections..... | 4 | +| 6.2 | Establishment of bearer unrelated connections ..... | 13 | +| 7 | Operational requirements..... | 13 | +| 8 | Coding requirements..... | 13 | +| 8.1 | Messages..... | 13 | +| 8.2 | Parameters ..... | 13 | +| 9 | State definitions ..... | 14 | +| 10 | Signalling procedures ..... | 14 | +| 10.1 | Bearer-related connections ..... | 14 | +| 10.2 | Bearer unrelated connections ..... | 44 | +| 11 | Interaction with other networks ..... | 44 | +| 12 | Interaction between IN basic call and ISDN supplementary services ..... | 44 | +| 12.1 | Call diversion..... | 46 | +| 12.2 | Calling line identification presentation/restriction ..... | 46 | +| 12.3 | Completion of calls service ..... | 46 | +| 12.4 | Conference..... | 47 | +| 12.5 | Connected line identification presentation/restriction..... | 47 | +| 12.6 | Explicit call transfer ..... | 48 | +| 12.7 | Malicious call identification ..... | 48 | +| 12.8 | Three party..... | 48 | +| 13 | Interactions between IN services ..... | 48 | +| 13.1 | Receiving an IN Service Compatibility in a BICC message..... | 49 | +| 13.2 | Handling of IN Service Compatibility in case outgoing legs are created
by IN ..... | 49 | +| 14 | Parameter values (timers) ..... | 50 | + +###### **Page** + +| | | +|------------------------------------------------------------------------------------------------------------------------------|----| +| Annex A – Signalling flows..... | 50 | +| Annex B – Exceptions for ISUP/INAP interaction..... | 56 | +| Appendix I – Coding of the compatibility information for the parameters ..... | 57 | +| Appendix II – Contents of the INAP serviceInteractionIndicatorsTwo ..... | 58 | +| Appendix III – Limitations for BICC basic call procedures and supplementary services
for different types of IN calls..... | 59 | + +# **Interaction between the Intelligent Network application CS-4 protocol and the Bearer Independent Call Control protocol** + +# **1 Scope** + +This Recommendation specifies the interaction between BICC and INAP CS-4. It also specifies ISUP/INAP CS-4 interaction procedures as exceptions to BICC/INAP interaction procedures (see Annex B). + +For the purpose of this Recommendation the interface INAP CS-4 between SSP and SCP is regarded as being an intra-network interface. + +The interaction between other signalling systems and INAP can be found by consulting the relevant interaction Recommendation to BICC in combination with this Recommendation. + +This Recommendation specifies procedures in order to provide interaction between BICC and INAP, i.e. to support IN services in an ISDN environment. In addition, new protocol elements for the BICC are defined in this Recommendation in order to satisfy IN specific requirements. Based on the protocol inherent compatibility mechanism, a stepwise upgrade of the BICC functionality is possible. However, the new function is only available for an IN call, if supported in any of the affected service nodes. + +In this Recommendation the IN SSF is treated as a functional part of the BICC CSF (see Figure 2). It is presupposed that this functional inclusion of the SSF has no impact on the CSF/BIWF interface. Any such impact is out of the scope of this Recommendation. + +This Recommendation describes SSF/CSF interaction only on "transit" level, i.e. no special further interworking is described for CSF-Ns with incoming/outgoing call control signalling to access networks (i.e. ISN to ACN-E/TE call control relationships). As a consequence, specific access-related interaction (e.g. interaction of line based triggering with ISDN supplementary services) is not within the scope of this Recommendation. + +This Recommendation therefore, also does not specify enhancements to the call control protocols at the access network level (e.g. DSS1), which may be needed due to additional BICC functions or IN requirements, respectively. + +The main subjects of this interaction Recommendation are the following: + +- description of specific call control functions for IN calls; +- impacts on the BICC basic call setup and the ISDN supplementary services for IN calls; and +- of the BICC protocol due to IN specific requirements. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as an stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendations Q.761 to Q.764 (2000), *Specifications of Signalling system No. 7 – ISDN User Part (ISUP)*. +- [2] ITU-T Recommendation Q.1224 (1997), *Distributed functional plane for intelligent network Capability Set 2*. +- [3] ITU-T Recommendation Q.1231 (1999), *Introduction to the Intelligent Network Capability Set 3*. +- [4] ITU-T Recommendations Q.1238.x, *Specifications of the Intelligent Network Application Protocol Capability Set 3*. +- [5] ITU-T Recommendation Q.1290 (1998) , *Glossary of terms used in the definition of intelligent networks*. +- [6] ITU-T Recommendation Q.1601 (1999), *Signalling system No. 7 – Interaction between N-ISDN and INAP CS-2*. +- [7] ITU-T Recommendations Q.1902.1 to Q.1902.4 (2001), *Specifications of the Bearer Independent Call Control protocol (BICC)*. +- [8] ITU-T Recommendation Q.1912.1 (2001), *Interworking between the Signalling system No. 7 ISDN user part (ISUP) and the Bearer Independent Call Control protocol*. +- [9] ITU-T Recommendation Q.1912.2 (2001), *Interworking between selected signalling systems (PSTN access, DSSI, C5, R1, R2, TUP) and the Bearer Independent Call Control protocol*. +- [10] ITU-T Recommendation Q.1922.2 (2001), *Interworking between the Intelligent Network Application protocol Capability Set 2 and the Bearer Independent Call Control protocol*. +- [11] ITU-T Recommendation Q.931 (1998), *ISDN user-network interface (DSSI); Layer 3 specification for basic call control*. +- [12] ITU-T Recommendation Q.765.1 (1998), *Signalling system No. 7 – Application transport mechanism: Support of VPN applications with PSS1 information flows*. +- [13] ITU-T Recommendation Q.769.1 (1999), *Signalling system No. 7 – ISDN user part enhancements for the support of number portability*. +- [14] ITU-T Recommendation Q.1902.6 (2001), *Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures and support of ISDN user part supplementary services for bearer redirection*. +- [15] ITU-T Recommendations Q.1248.x (2001), *Interface Recommendation for Intelligent Network Capability Set 4*. + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +**Call Control Function (CCF)**: see 3.3/Q.1224 [2]. + +**Service Control Function (SCF)**: see 3.3/Q.1224 [2]. + +**Service Switching Function (SSF)**: see 3.3/Q.1224 [2]. + +**Specialized Resource Function (SRF)**: see 3.3/Q.1224 [2]. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------------------| +| ACM | Address Complete Message (BICC) | +| ANM | Answer Message (BICC) | +| APM | Application Transport Mechanism | +| ATP | Access Transport Parameter (BICC) | +| BCF | Bearer Control Function (BICC) | +| BCSM | Basic Call State Model (IN) | +| BICC | Bearer Independent Call Control | +| BIWF | Bearer Inter-Working Function (BICC) | +| CCSS | Call Completion Service Set-up | +| CMN | Call Mediation Node (BICC) | +| CON | Connect message (BICC) | +| COT | Continuity message (BICC) | +| CPG | Call Progress message (BICC) | +| CSF | Call Service Function (BICC) | +| DLE | Destination Local Exchange | +| DP | Detection Point (IN) | +| DSS1 | Digital Subscriber Signalling System No. 1 | +| EDP-N | Event Detection Point – Notification (IN) | +| EDP-R | Event Detection Point – Request (IN) | +| ERB | EventReportBCSM (IN) | +| FAR | Facility Request Message (BICC) | +| FOT | Forward Transfer Message (BICC) | +| FRJ | Facility Reject (BICC) | +| GVNS | Global Virtual Network Service | +| IAM | Initial Address Message (BICC) | +| IDR | Identification Request Message (BICC) | +| IE | Information Element | +| IN | Intelligent Network | +| INAP | Intelligent Network Application Protocol | +| IP | Intelligent Peripheral (IN) | +| IRS | Identification Response message (BICC) | +| ISDN | Integrated Services Digital Network | +| ISN | Interface Serving Node (BICC) | +| ISUP | ISDN User Part | +| OLE | Originating Local Exchange | + +| | | +|-----|----------------------------------------| +| PRI | Pre-release Information message (BICC) | +| REL | RELease message (BICC) | +| RES | RESume message (BICC) | +| RLC | Release Complete message (BICC) | +| SCP | Service Control Point (IN) | +| SGM | Segmentation Message (BICC) | +| SN | Serving Node (BICC) | +| SS | Signalling System | +| SSP | Service Switching Point (IN) | +| SUS | Suspend message (BICC) | +| TMR | Transmission Medium Requirement | +| TNS | Transit Network Selection (BICC) | + +# 5 Conventions + +The name of each element of the following class of terms is capitalized, and capital letters within that term can possibly occur: + +- operations. +Example: ContinueWithArgument operation. +- parameters within operations. +Example: CalledPartyNumber. + +# 6 Description + +## 6.1 Establishment of bearer-related connections + +### 6.1.1 Integration of IN service control into a BICC serving node + +ITU-T Rec. Q.1248.1 [15] provides a distributed functional plane architecture for IN Capability Set 4 (CS-4). Interactions between the following functional entities (FEs) are relevant for this Recommendation: + +- Call Control Function (CCF); +- Service Switching Function (SSF); +- Service Control Function (SCF); and +- Specialized Resource Function (SRF). + +The functional entities can be implemented in one or more network elements called physical entities. The service control point (SCP) is the physical entity in the intelligent network that implements the SCF. The CCF and SSF are realized in the service switching point (SSP) and the SRF is realized in the intelligent peripheral (IP). + +The main function of the CCF, according to ITU-T Rec. Q.1248.1 (see [15]), is to provide the IN service logic with an abstract view of the call state and specific call(-state) associated data according to a "Basic Call State Model" (BCSM). This BCSM defines "detection points" at which the SSF can interrupt normal call processing and access an IN service logic in the SCF to change call data, or reconfigure the call, before continuing call processing at a specified BCSM-point. + +Instead of interrupting call processing, the SSF may also only retrieve call-related information to notify it to the IN service logic. + +The CCF can in turn be decomposed into several entities. Figure 1 depicts a functional decomposition of the CCF and its relationship to other components that are involved in call and service processing. Within the CCF, the Basic Call Control (BCC) Entity is responsible for the overall coordination of basic call processing, separated into control of the originating/terminating BCSM and their interactions. It interacts with the Signalling Terminations for call control signalling and the Bearer Control Entity that controls media resources embedded in a Bearer Function. + +![Figure 1/Q.1922.4 – CCF/SSF decomposition diagram showing the functional decomposition of the Call Control Function (CCF) and Service Switching Function (SSF).](e9314c83043183351ed74908e9bf2f90_img.jpg) + +The diagram illustrates the functional decomposition of the CCF/SSF. At the top is the Service Switching Function (SSF). Below it is the Call Control Function (CCF), which contains several sub-entities. In the center of the CCF is the 'Basic call control entity', which includes two ovals labeled 'O-BCSM' and 'T-BCSM'. To the left of this entity is a vertical rectangle labeled 'Signalling termination', and to the right is a vertical rectangle labeled 'Termination signalling'. Below the basic call control entity is a horizontal rectangle labeled 'Bearer control entity'. At the bottom of the diagram is a horizontal rectangle labeled 'Bearer function', with arrows pointing left and right from its sides. Vertical lines connect the SSF to the CCF, the CCF to the Bearer control entity, and the Bearer control entity to the Bearer function. On the left and right sides of the CCF, there are brackets labeled 'To other CCF'. + +Figure 1/Q.1922.4 – CCF/SSF decomposition diagram showing the functional decomposition of the Call Control Function (CCF) and Service Switching Function (SSF). + +**Figure 1/Q.1922.4 – CCF/SSF decomposition** + +The BICC protocol (see ITU-T Rec. Q.1902-1 [7]) provides the signalling functions required to support narrowband ISDN services independent of the bearer technology and signalling transport technology used. To separate the call control signalling from the bearer control aspects, nodes that support BICC signalling are decomposed in the BICC reference model into the Call Service Function (CSF) and the Bearer Control Function (BCF). + +Several arrangements are possible for nodes that support BICC signalling. These nodes may have an associated BCF, in which case they are referred to as Serving Nodes (SN). A node without an associated BCF is referred to as Call Mediation Node (CMN). Between Serving Nodes, the control of bearers is provided by other protocols, referred to as "bearer control signalling". + +In a Serving Node (SN), the Call Service Function (CSF) and the Bearer Control Function (BCF) entities may be physically separated. The Call Bearer Control (CBC) signalling is used between these two entities in case of physical separation. + +Serving Nodes may be of different type (gateway, transit, interface, access; see ITU-T Rec. Q.1902.1 [7]). In this Recommendation, only transit serving nodes (TSN) and gateway serving nodes (GSN) are within scope. + +#### Relationship between the BICC reference model and the CCF/SSF model + +- The SSF can be considered as a part of a BICC Call Service Function (CSF). +- The Signalling Terminations are part of a CSF. They will contain the functions of incoming/outgoing procedures of the Q.1902.x BICC protocol. +- The Basic Call Control entity of the CCF can be considered as a part of a CSF. +- The Bearer Control entity of the CCF can be considered as equivalent to the BICC Bearer Control Function (BCF). + +The SSF contains the capabilities beyond those that are needed for basic call control. Consequently, this Recommendation concentrates on the actions that are performed in the CCF. The SSF can be seen as functional entity that may influence the call control performed by the CSF at points notified by the CCF. In ITU-T Rec. Q.1248.1 (see [15]), only an internal functional interface is supposed between CCF and SSF, whereas an open TCAP-based interface is defined between SSF and SCF (the IN Application Protocol, ITU-T Rec. Q.1248.2 [15]). + +The minimum configuration of an SSP providing BICC/INAP interworking, according to this Recommendation consists of a CSF (according to [7]), including BCC-functionality (interacting with the BICC incoming/outgoing signalling terminations) and an SSF supporting INAP CS-4 (according to ITU-T Rec. Q.1248 [15]). Whether other functional entities, like the BIWF, are also part of the SSP or externally attached, is not relevant for the IN service switching functionality. However, the use of specific SSF functionality (e.g. for call party handling) may pose specific requirements in regard to the capabilities of the BCF (without which only limited IN functionality could be performed). + +The Figure 2 illustrates in a simplified manner a signalling configuration which is to be considered in this Recommendation. In the configuration, it is assumed that SRF support is not needed. The network signalling system used for call control is the ITU-T BICC [7], with any of the several bearer/bearer control systems allowed for BICC according to [7]. The interface between SSF and SCF is the ITU-T INAP [15]. The SSP-unit is seen as equivalent to the SN or CMN. + +![Diagram illustrating the relationship between the CCF/SSF model and the BICC reference model. The diagram shows a hierarchy of functional entities. At the top, an SCP contains an SCF. Below it, a dashed box labeled 'Serving Node (SN) / SSP' contains a 'Call Service Function (CSF)'. Inside the CSF, there are 'Incoming procedures', 'BCC', and 'Outgoing procedures'. The 'SSF' is shown above the CSF, connected via an 'INAP' interface. The 'BCC' is connected to the 'SSF' and to the 'BIWF' and 'BCF' below. The 'BIWF' and 'BCF' are connected to the 'bearer' at the bottom. 'BICC signalling' enters from the left and right, passing through the 'Incoming procedures' and 'Outgoing procedures'. 'CBC signalling' is shown between the 'BCC' and the 'BIWF'. 'Bearer control signalling' enters from the left and right, passing through the 'BIWF' and 'BCF'. A 'CCF' label is on the right side, pointing to the 'SSF'.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Diagram illustrating the relationship between the CCF/SSF model and the BICC reference model. The diagram shows a hierarchy of functional entities. At the top, an SCP contains an SCF. Below it, a dashed box labeled 'Serving Node (SN) / SSP' contains a 'Call Service Function (CSF)'. Inside the CSF, there are 'Incoming procedures', 'BCC', and 'Outgoing procedures'. The 'SSF' is shown above the CSF, connected via an 'INAP' interface. The 'BCC' is connected to the 'SSF' and to the 'BIWF' and 'BCF' below. The 'BIWF' and 'BCF' are connected to the 'bearer' at the bottom. 'BICC signalling' enters from the left and right, passing through the 'Incoming procedures' and 'Outgoing procedures'. 'CBC signalling' is shown between the 'BCC' and the 'BIWF'. 'Bearer control signalling' enters from the left and right, passing through the 'BIWF' and 'BCF'. A 'CCF' label is on the right side, pointing to the 'SSF'. + +Figure 2/Q.1922.4 – Relationship between CCF/SSF model and BICC reference model + +The interaction between BICC and INAP takes place in the CCF and SSF. The following main subjects have to be considered in this area: + +- detection point processing in the CCF; and +- receipt of INAP operations in the SSF. + +NOTE – in a Call Mediation Node (CMN) there is no bearer control capability. IN interaction on a CMN will only be possible, in case the CMN (in its network) has capabilities for remote bearer control (e.g. bearer redirection). + +#### **Detection point processing** + +The provision of detection points (DPs) is required in the BICC basic call handling in order to access IN functionality and to allow IN service logic to influence the processing of IN calls. The detection points (DPs) of the BCSM indicate points in call (PICs) at which transfer of control can occur. If a DP is recognized, an operation from the SSF to the SCF is sent. Thus the communication towards the SCP is performed. The DPs defined in [15] are listed in Table 1. + +The column "Support" indicates whether the DP is supported with the ITU-T BICC [7]. + +**Table 1/Q.1922.4 – List of detection points** + +| Detection points for the originating side | Support | Detection points for the terminating side | Support | +|--------------------------------------------------|-------------------|--------------------------------------------------|-------------------| +| OA
Origination_Attempt | No impact on BICC | TA
Terminating_Attempt | No impact on BICC | +| OAD
Originating_Attempt_Denied | No impact on BICC | TAD
Terminating_Attempt_Denied | No impact on BICC | +| OAA
Origination_Attempt_Authorized | No impact on BICC | TAA
Terminating_Attempt_Authorized | No impact on BICC | +| CI
Collected_Information | Yes | | | +| AI
Analysed_Information | Yes | | | +| ARF
Authorize_Route_Failure | For further study | | | +| RSF
Route_Select_Failure | Yes | | | +| OCPB
O_Called_Party_Busy | Yes | TB
T_Busy | Yes | +| | | FSA
Facility_Selected_and_Available | For further study | +| OTS
O_Term_Seized | Yes | CA
Call_Accepted | Yes | +| ONA
O_No_Answer | Yes | TNA
T_No_Answer | Yes | +| OAns
O_Answer | Yes | Tans
T_Answer | Yes | +| OMC
O_Mid_Call | for further study | TMC
T_Mid_Call | For further study | +| OS
O_Suspend | Yes | TS
T_Suspend | Yes | +| ORA
O_Re_Answer | Yes | TRA
T_Re_Answer | Yes | +| OD
O_Disconnect | Yes | TD
T_Disconnect | Yes | +| OAb
O_Abandon | Yes | Tab
T_Abandon | Yes | + +#### **Receipt of INAP operations** + +Table 2 lists the INAP operations with direction SCF-SSF and indicates which operation will influence the BICC call control handling. + +**Table 2/Q.1922.4 – INAP operations (direction: SCF-SSF)** + +| Operation | Influence on BICC call handling | Reference clause | +|-----------------------------------------|----------------------------------------|-------------------------------------------------------------| +| ActivateServiceFiltering | Yes | 10.1.7 (Service filtering) | +| ActivityTest | No | | +| AnalyseInformation | For further study (Note) | | +| ApplyCharging | No | | +| Authorize Termination | For further study (Note) | | +| CallFiltering | No | | +| CallGap | Yes | 10.1.6 (Call gapping) | +| CallInformationRequest | No | | +| Cancel | No | | +| CancelStatusReportRequest | For further study (Note) | | +| CollectInformation | Yes | 10.1.2 (IN call with SCP request to collect further digits) | +| Connect | Yes | 10.1.1.1.1.1 (Connect operation) | +| Continue | Yes | 10.1.1.1.1.2 (Continue operation) | +| ContinueWithArgument | Yes | 10.1.1.1.1.3 (ContinueWithArgument operation) | +| ConnectToResource | Yes | 10.1.5.1 (SSP supports requested IP capabilities) | +| CreateCallSegmentAssociation | No | | +| ConnectOrRemoveTriggerData | No | | +| DisconnectForwardConnection | Yes | 10.1.5.2 (Assist method – procedure in the initiating SSP) | +| DisconnectForwardConnectionWithArgument | Yes | 10.1.5.2 (Assist method – procedure in the initiating SSP) | +| DisconnectLeg | For further study (Note) | | +| EstablishTemporaryConnection | Yes | 10.1.5.2 (Assist method – procedure in the initiating SSP) | +| FurnishChargingInformation | No | | +| HoldCallInNetwork | For further study (Note) | | +| InitiateCallAttempt | Yes | 10.1.8 (SCP initiated call) | +| ManageTriggerData | No | | +| MergeCallSegments | For further study (Note) | | +| MonitorRouteRequest | No | | + +**Table 2/Q.1922.4 – INAP operations (direction: SCF-SSF)** + +| Operation | Influence on BICC call handling | Reference clause | +|--------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------| +| MoveCallSegments | For further study (Note) | | +| MoveLeg | For further study (Note) | | +| Reconnect | For further study (Note) | | +| ReleaseCall | Yes | 10.1.1.4 (ReleaseCall operation) | +| RequestCurrentStatusReport | For further study (Note) | | +| RequestEveryStatusChangeReport | For further study (Note) | | +| RequestFirstStatusMatchReport | For further study (Note) | | +| RequestNotificationChargingEvent | Yes | The treatment is national network specific and not described further within this Recommendation | +| RequestReportBCSMEVENT | Yes | 10.1.3 (Detection Point processing) | +| RequestReportFacilityEvent | No | | +| RequestReportUTSI | No | | +| ResetTimer | No | | +| SelectFacility | For further study (Note) | | +| SendFacilityInformation | No | | +| SelectRoute | For further study (Note) | | +| SendSTUI | For further study (Note) | | +| SplitLeg | For further study (Note) | | +| SendChargingInformation | Yes | 10.1.1.1.2 (SendChargingInformation operation) | +| NOTE – More information can be found in reference [4]. | | | + +### 6.1.2 Support of the SCF-SRF relationship + +A Specialized Resource Function (SRF) is used in the IN context to provide the IN service logic (in the SCF) with the possibility of inserting user interactive (UI) dialogues into the controlled call. This may consist of playing announcements, voice recording, voice recognition, DTMF collection, etc. The SRF is modeled as part of a physical entity called Intelligent Periphery (IP). In ITU-T Rec. Q.1238.3 (see [4], CS-3, document unchanged in CS-4) a number of scenarios for support of the SCF, SSF, and SRF functional entities as physical entities have been identified. The scenarios differ in the method to support the SCF-SRF relationship and are summarized in Figure 4/Q.1238.3 of the ITU-T INAP [4]. + +The following figures provide, in a simplified manner, some signalling configurations for IN calls needing an IP for user interaction. The figures are only included to ease the understanding and should not be seen as exhaustive representation of the various physical scenarios. + +#### 6.1.2.1 SSF relay method + +The control of the SRF is done by the SCF using the INAP operations *ConnectToResource*, *PlayAnnouncement*, *PromptAndCollectUserInformations*, *PromptAndReceiveMessage*, *DisconnectForwardConnection* and receiving INAP operations *SpecializedResourceReport*, *ReturnReportForPromptAndReceiveMessage*. Therefore, an extra service control channel between SCF/SRF has to be provided additionally to the normal call/bearer control for a connection of the user to the IP. For the service control channel, several physical scenarios are defined in [5]. The first of them being the relaying of the service control messages between SCP and IP using the SSP. + +Figure 3 shows the relay of INAP-operations via a logical service control channel between SSF and SRF. Note that the operations *ConnectToResource*/*DisconnectForwardConnection* are not only relayed through the service control channel, but also send to CCF for Call/Bearer control. The procedure for this scenario is described in 10.1.5.1 (SSP supports requested IP capabilities) and a typical arrow diagram is given in Figure A.3. + +NOTE – In the following figures the service/call/bearer control signalling are displayed as *logically* separate. In fact there may even be only one physical type of signalling for this three types of relationship. Additional interface functions are needed in the BICC SN for this purpose, that are not displayed in the figures. + +![Diagram illustrating the connection to IP with SSF relay of SRF operations. The diagram shows three main entities: SCP, SN, and IP. The SCP contains an SCF block. The SN contains a CSF-x block, which includes an SSF block, a BCC block (dashed), and a BIWF block. The IP contains an SRF block, a CSF-x block, and a BCF block. Signalling flows are shown: INAP between SCF and SSF; Service control signalling between SSF and SRF; Call control signalling between CSF-x (SN) and CSF-x (IP); Bearer control signalling between BIWF and BCF; and BICC between SN and IP. All three blocks (SSF, BCC, BIWF) in the SN are connected to a common 'bearer' line at the bottom.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +Diagram illustrating the connection to IP with SSF relay of SRF operations. The diagram shows three main entities: SCP, SN, and IP. The SCP contains an SCF block. The SN contains a CSF-x block, which includes an SSF block, a BCC block (dashed), and a BIWF block. The IP contains an SRF block, a CSF-x block, and a BCF block. Signalling flows are shown: INAP between SCF and SSF; Service control signalling between SSF and SRF; Call control signalling between CSF-x (SN) and CSF-x (IP); Bearer control signalling between BIWF and BCF; and BICC between SN and IP. All three blocks (SSF, BCC, BIWF) in the SN are connected to a common 'bearer' line at the bottom. + +**Figure 3/Q.1922.4 – Connection to IP with SSF relay of SRF operations** + +Different implementations of the service/call control between SN and IP for SSF relay are possible in alignment with 7.3.5/Q.1238.3: + +- The IP may be physically integrated into the SSP ("internal IP"), with the control signalling being internal interfaces (7.3.5.1/Q.1238.3). This case is of no relevance to this Recommendation. +- The IP may be connected to the SSP via an access network. In 7.3.5.2/Q.1238.3 the DSS1 signalling is explicitly used for service/call/bearer control signalling, whereby the service control signalling is implemented using facility information elements for the relayed INAP-operations. The extension of this example to other access network types is for further study (depending on how relay of INAP-operations could be performed). + +NOTE – The case of a DSS1 connection between SSP and IP has to be modeled using a BICC interface SN to narrowband ISDN (see [8]). + +- The IP may be connected to the SSP via ISUP using TCAP for relaying INAP operations (7.3.5.2/Q.1238.3). The connection between SSP and IP has to be modeled using a BICC interface SN to narrowband ISDN (see [8]). The TCAP relaying between SSF and SRF is out of the scope of this Recommendation. +- The external SRFs mentioned so far (using narrowband ISDN access) can be attached to BICC-SNs only by the intermediation of a Media Gateway. In INAP CS-4 (see ITU-T Rec. Q.1244) a new kind of Media Gateway containing a SRF is defined. All the control signalling in this case is done using H.248.x procedures. The impact of this scenario on 10.1.5 is for further study. + +#### 6.1.2.2 Direct SCP-IP information transfer + +In Figure 4 the SRF-SCF INAP operations are directly exchanged between IP and SCP. + +When receiving the *ConnectToResource* operation in this context, "assist request instructions" are sent via call control signalling to the IP (correlating the SCP connected to the SSP with the SCP/IP-connection). On completion of the user interaction, control is returned to the initiating SSP. This procedure is called the "Assist" method. The procedure for this scenario is described in 10.1.5.2 (Assist method – procedure in the initiating SSP). The procedure between the SCP and the SRF has no impact on the BICC and is outside the scope of this Recommendation. More information can be found in [5]. A typical arrow diagram is given in Figure A.4. + +![Figure 4/Q.1922.4 – External IP connected via BICC; direct TCAP link between SRF and SCF. The diagram shows a signaling flow between an SCP, a Service Node (SN), and an IP. The SN contains a CSF-x, SSF, BCC, and BIWF. The IP contains an SRF, CSF-x, and BCF. The SCP is connected to the SN via INAP. The SN is connected to the IP via BICC. The SN is connected to the IP via Call control signalling. The SN is connected to the IP via Bearer control signalling. The SN is connected to the IP via a bearer. The SCP is connected to the IP via INAP. The SCP is connected to the IP via a direct TCAP link between the SRF and the SCF.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +The diagram illustrates the signaling architecture for external IP connected via BICC with a direct TCAP link between SRF and SCF. At the top, the **SCP** is connected to the **SN** (Service Node) via an **INAP** interface. The **SN** contains a **CSF-x**, **SSF**, **BCC** (dashed box), and **BIWF**. The **IP** (IP node) contains an **SRF**, **CSF-x**, and **BCF**. The **SCP** is also connected to the **IP** via an **INAP** interface. The **SN** is connected to the **IP** via **BICC** (indicated by an arrow pointing left from the SN). The **SN** is connected to the **IP** via **Call control signalling** (indicated by an arrow pointing right from the SN). The **SN** is connected to the **IP** via **Bearer control signalling** (indicated by an arrow pointing right from the SN). The **SN** is connected to the **IP** via a **bearer** (indicated by a thick line at the bottom). The **SCP** is connected to the **IP** via a direct **TCAP link** between the **SRF** and the **SCF** (indicated by a double-headed arrow between the **SRF** and the **SCF**). + +Figure 4/Q.1922.4 – External IP connected via BICC; direct TCAP link between SRF and SCF. The diagram shows a signaling flow between an SCP, a Service Node (SN), and an IP. The SN contains a CSF-x, SSF, BCC, and BIWF. The IP contains an SRF, CSF-x, and BCF. The SCP is connected to the SN via INAP. The SN is connected to the IP via BICC. The SN is connected to the IP via Call control signalling. The SN is connected to the IP via Bearer control signalling. The SN is connected to the IP via a bearer. The SCP is connected to the IP via INAP. The SCP is connected to the IP via a direct TCAP link between the SRF and the SCF. + +**Figure 4/Q.1922.4 – External IP connected via BICC; +direct TCAP link between SRF and SCF** + +NOTE 1 – The same implementation scenarios as in 6.1.2.1 are possible. + +NOTE 2 – In the case where the SSP/IP connection is done via BICC, problems were identified regarding network integrity aspects and the lack of standardized ISUP signalling for this type of interface. + +#### 6.1.2.3 SSP assist + +In Figure 5, the IP is integrated into another SSP (assisting SSP), than the one that is interacting with the SCP (initiating SSP). Whether the SRF-SCF INAP operations are relayed via the SSP, or are directly exchanged between IP and SCP, is not relevant for this Recommendation. However, in Figure 5 only the scenario is shown where a relay via SSP is applied. + +On completion of the user interaction, control is returned to the initiating SSP. This procedure is called the "Assist" method. The procedure for this scenario is described in clauses 10.1.5.2 (Assist + +method – procedure in the initiating SSP) and 10.1.5.4 (Assist/Hand-off method – procedure in the assisting SSP). A typical arrow diagram is given in Figure A.4. + +If the control of the call is retained in the assisting SSP, the "Hand-off" method is applied. This scenario is not explicitly shown in a figure. The procedure for this scenario is described in 10.1.5.3 (Hand-off method – procedure in the initiating SSP) and a typical arrow diagram is given in Figure A.5. + +![Figure 5/Q.1922.4 – IP attached to an assisting SSP ('Assist' method). The diagram shows a network architecture with three main components: SN (Switching Network), SCP (Service Control Point), and IP (IP network). The SN contains CSF-x, SSF, BCC, and BIWF. The IP contains SRF, CSF-x, and BCF. Signalling flows include INAP between SCP and SN, BICC between SN and IP, Service control signalling between SSF and SRF, Call control signalling between CSF-x and CSF-x, and Bearer control signalling between BIWF and BCF. A 'bearer' line is shown at the bottom.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +Figure 5/Q.1922.4 – IP attached to an assisting SSP ('Assist' method). The diagram shows a network architecture with three main components: SN (Switching Network), SCP (Service Control Point), and IP (IP network). The SN contains CSF-x, SSF, BCC, and BIWF. The IP contains SRF, CSF-x, and BCF. Signalling flows include INAP between SCP and SN, BICC between SN and IP, Service control signalling between SSF and SRF, Call control signalling between CSF-x and CSF-x, and Bearer control signalling between BIWF and BCF. A 'bearer' line is shown at the bottom. + +Figure 5/Q.1922.4 – IP attached to an assisting SSP ("Assist" method) + +## 6.2 Establishment of bearer unrelated connections + +For further study. + +# 7 Operational requirements + +Not applicable. + +# 8 Coding requirements + +## 8.1 Messages + +None. + +## 8.2 Parameters + +### 8.2.1 Call diversion treatment indicators parameter + +The format of the call diversion treatment indicators parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### 8.2.2 Called IN number parameter + +The format of the called IN number parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### 8.2.3 Call offering treatment indicators parameter + +The format of the call offering treatment indicators parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### 8.2.4 Charged party identification parameter + +The format of the charged party identification parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.5 Conference treatment indicators parameter** + +The format of the conference treatment indicators parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.6 Correlation id parameter** + +The format of the correlation id parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.7 Display information parameter** + +The format of the display information parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.8 SCF id parameter** + +The format of the SCF id parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.9 UID action indicators parameter** + +The format of the UID action indicators parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.10 UID capability indicators parameter** + +The format of the UID capability indicators parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.11 Original Called IN number parameter** + +The format of the called IN number parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +### **8.2.12 IN Service Compatibility Information parameter** + +The format of the IN Service Compatibility Information parameter is defined in ITU-T Rec. Q.1902.3 [7]. + +# **9 State definitions** + +No specific state definitions are required. + +# **10 Signalling procedures** + +## **10.1 Bearer-related connections** + +### **10.1.1 IN basic call** + +For this Recommendation an "IN basic call" is considered as: + +- a normal BICC basic call invoking IN functionality in the SSP; +- with no EDPs armed dynamically in the request mode; and +- no user interaction needed. + +For an IN basic call, the normal BICC basic call procedures are applicable as described in ITU-T Rec. Q.1902.4 [7] for national intermediate exchanges, unless indicated otherwise in the clauses below. + +#### **10.1.1.1 Successful call set-up** + +##### **10.1.1.1.1 Forward address signalling** + +If an IAM is received in an SSP and the call is recognized as IN call, i.e. by detecting a DP as TDP-R (see 10.1.3 (Detection Point processing)), an InitialDP operation, or a DP specific operation for a TDP-R, is sent from the SSF to the SCF. If the IAM is segmented, the remainder of the call set-up information is awaited (see 10.1.1.1.7 (Simple segmentation)). + +The mapping of parameters is shown in Table 4. + +**Table 4/Q.1922.4 – Mapping of parameters from IAM to InitialDP** + +| BICC message
IAM (Note 1) | INAP operation
InitialDP | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| Called party number | CalledPartyNumber | +| Calling party number | CallingPartyNumber | +| Calling party subaddress IE contained in access transport | CallingPartySubaddress | +| Calling party's category | CallingPartysCategory | +| Location number | LocationNumber | +| Original called number | OriginalCalledPartyID | +| User teleservice information (1st priority)
High layer compatibility IE contained in access transport (2nd priority) (Note 2) | HighLayerCompatibility | +| Generic number "additional calling party number" | AdditionalCallingPartyNumber | +| Forward call indicators | ForwardCallIndicators | +| User service information prime (1st priority)
User service information (2nd priority)
or
TMR (Note 3) | BearerCapability | +| Redirecting number | RedirectingPartyID | +| Redirection information | RedirectionInformation | +| CCSS with "CCSS call indicator" | CCSS | +| Access Transport | ISDNAccessRelatedInformation | +| Generic Number | GenericNumbers | +| Carrier Selection Information | Carrier (Note 4) | +| Transit Network Selection | Carrier (Note 5) | +| Calling geodetic location | CallingGeodeticLocation | +| NOTE 1 – Optional parameters may be absent, i.e. they are only mapped, if these parameters are available at the DP. | | +| NOTE 2 – If two high layer compatibility information elements are contained in the access transport parameter, then the second information element, carrying the preferred HLC, is mapped to the INAP highLayerCompatibility parameter. | | +| NOTE 3 – The choice whether to use the user service information or the TMR is a network option | | +| NOTE 4 – The first octet of the INAP carrier parameter is coded according to the first octet of Carrier Selection Information. | | +| NOTE 5 – Starting with the second octet of the carrier-parameter, the TNS may be included here. Instead of this, as a network option, also the "Carrier Id"-coding may be used for this second part of the carrier-parameter (see 14.1/Q.1238.2). If no TNS is received, the second part of the carrier-parameter may be determined by the CCF itself based on the analysis of the called party number. | | + +###### **10.1.1.1.1.1 Connect operation** + +On receipt of a Connect operation from the SCP, the actions described in 7.2.2/Q.1902.4 [7] are performed. For routing of the call, the called party number is derived from the destinationRoutingAddress (see Table 5 – Mapping of parameters from Connect to IAM). + +If no cutAndPaste parameter is received in the Connect operation, an ACM message may be sent to the preceding exchange if there is no outstanding O:COT, and the preceding bearer connection is + +established. The ACM shall contain the corresponding BICC parameters if a serviceInteractionIndicatorsTwo parameter was received in the Connect operation (see below). Other optional parameters will not be sent. The backward call indicators parameter in the ACM is encoded as follows: + +| | | +|-----------------------------------|----------------------------------------------------| +| Charge indicator: | See 10.1.1.1.2 (SendChargingInformation operation) | +| Called party's status indicator: | 00 (no indication) | +| Called party's category: | 00 (no indication) | +| End-to-end method indicator: | 00 (no end-to-end method available) | +| Interworking indicator: | 0 (no interworking encountered) | +| End-to-end information indicator: | 0 (no end-to-end information available) | +| ISDN User Part indicator: | 1 (ISDN User Part used all the way) | +| Holding indicator: | National matter | +| ISDN access indicator: | 1 (terminating access ISDN) | +| Echo Control device indicator: | see 8.4.2.1.2/Q.1902.4 [7] | +| SCCP method indicator: | 00 (no indication) | + +NOTE – As a network operator option, the sending of the ACM message may be postponed to a later stage during call set-up. + +Table 5 illustrates the mapping of parameters received in the Connect operation, to parameters sent in the IAM message to the succeeding exchange. Parameters which were received in the IAM and which are not replaced by parameters of the Connect operation, are treated according to the normal procedures. + +On sending of the IAM, the awaiting address complete timer T7 is started. If timer T7 expires, the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +**Table 5/Q.1922.4 – Mapping of parameters from Connect to IAM** + +| INAP operation
Connect (Note 1) | BICC message
IAM | +|--------------------------------------------|------------------------------------------------------------------------| +| DestinationRoutingAddress (Note 2) | Called party number (Note 3) | +| CallingPartyNumber | (Note 4) | +| ServiceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| OriginalCalledPartyID | Original called number | +| CallingPartysCategory | Calling party's category | +| RedirectingPartyID | Redirecting number | +| RedirectionInformation | Redirection information | +| isdnAccessRelated Information | ATP (Note 5) | +| ForwardCallIndicators | Forward call indicators | +| GenericNumbers | Generic Number (Note 4) | +| Carrier (Note 6) | Carrier Selection Information | +| Carrier (Note 7) | Transit Network Selection | + +NOTE 1 – Optional parameters may be absent, i.e. they are only mapped, if received. + +NOTE 2 – The Connect operation sent by the SCF to the SSF may contain a list of up to three destination routing addresses. Following processing by the SSF, only one of these addresses is passed to BICC. + +NOTE 3 – The treatment of the called party number, in the case where the cutAndPaste parameter, is present in the Connect operation is described in [5] § 3.3.16. + +NOTE 4 – The mapping of this parameter must not compromise the existing services supported by BICC (MCID, CLIP, etc.). + +NOTE 5 – Due to the end-to-end significance of the ATP DSS1 information elements, only the "called party subaddress" and "calling party subaddress" contained in the "IsdnAccessRelatedInformation" are mapped to the "called party subaddress" and "calling party subaddress" of the ATP. Other information elements are copied from the ATP received on the incoming BICC. The mapping of these information elements must not compromise the existing services supported by BICC (CLIP, etc.). + +NOTE 6 – The first octet of the carrier-parameter is mapped to the first octet of the Carrier Selection Information. + +NOTE 7 – If the carrier-parameter contains more than one octet and the network option is "TNS", then the rest of the carrier parameter is copied into the Transit Network Selection parameter. In the case where the network option is "carrier Id", the mapping of this part of the carrier-parameter is network specific. + +###### **10.1.1.1.1.2 Continue operation** + +On receipt of a Continue operation from the SCP, call processing is resumed and the call set-up is performed as described in 7.2.2/Q.1902.4 [7]. + +###### **10.1.1.1.1.3 ContinueWithArgument operation** + +On receipt of a ContinueWithArgument operation from the SCP, call processing is resumed and the call set-up is performed as described in 7.2.2/Q.1902.4 [7]. + +In addition, the following parameter received from the SCP in the ContinueWithArgument operation is sent in the IAM by the SSP as shown in Table 6. + +Parameters which were received in the IAM and are not replaced by parameters of the ContinueWithArgument operation, are treated according to the normal procedures. + +**Table 6/Q.1922.4 – Mapping of parameters from ContinueWithArgument to IAM** + +| INAP operation
ContinueWithArgument (Note) | BICC message
IAM | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------| +| serviceInteractionIndicatorsTwo | see 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| NOTE – Optional parameters may be absent, i.e. they are only mapped, if received. | | + +###### **10.1.1.1.1.4 Mapping of the INAP serviceInteractionIndicatorsTwo** + +The INAP serviceInteractionIndicatorsTwo parameter contains information that is: + +- only of local significance, i.e. to be treated in the SSP; +- relevant for the originating local exchange; or +- relevant for the destination local exchange. + +NOTE – In the context of IN CS-4, the serviceInteractionsIndicatorsTwo is used. However, the serviceInteractionsIndicators may also be received, but the mapping of the serviceInteractionsIndicators is network operator specific. + +Table 7 describes the mapping from the INAP to the BICC with regard to the serviceInteractionIndicatorsTwo. + +Furthermore, for the IN basic call, the following rules shall apply: + +- If, in the INAP serviceInteractionIndicatorsTwo parameter, a value has been received indicated as default in Table 7, this value is mapped to the value "no indication" in the appropriate BICC parameter. +- A BICC parameter is only included in a message, if the parameter contents is unequal to zero. + +**Table 7/Q.1922.4 – Mapping of the INAP serviceInteractionIndicatorsTwo** + +| INAP
serviceInteractionIndicatorsTwo | BICC parameter in
ACM/CPG/CON/ANM                      IAM | | +|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call to be diverted indicator:
– call diversion allowed (default);
– call diversion not allowed. | – | Call diversion treatment indicators parameter
Call to be diverted indicator:
– no indication;
– call diversion allowed;
– call diversion not allowed. | +| Call to be offered indicator:
– call offering not allowed (default);
– call offering allowed. | – | Call offering treatment indicators parameter
Call to be offered indicator:
– no indication;
– call offering not allowed;
– call offering allowed. | + +**Table 7/Q.1922.4 – Mapping of the INAP serviceInteractionIndicatorsTwo** + +| INAP
serviceInteractionIndicatorsTwo | BICC parameter in | | +|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ACM/CPG/CON/ANM | IAM | +| Conference at DLE accept. ind.:
– accept conference request (default);
– reject conference request. | – | Conference treatment indicators parameter
Conference acceptance ind.:
– no indication;
– accept conference request;
– reject conference request. | +| Conference at OLE accept. Ind.:
– accept conference request (default);
– reject conference request. | Conference treatment indicators parameter
Conference acceptance ind.:
– no indication;
– accept conference request;
– reject conference request. | – | + +If multiple IN services are invoked for a call, then the serviceInteractionIndicatorsTwo received via the INAP may conflict with the received BICC parameters transferring service interaction information. In this case, the BICC parameters to be sent in forward and backward direction shall transfer the most stringent condition, i.e. the non-default value (refer to Appendix II). + +###### **10.1.1.1.1.4.1 Interworking with an SN/CMN not supporting the parameters** + +No specific action is required. If the parameters cannot be transferred to the local exchanges, the behavior in these exchanges for IN calls is the same as for basic BICC calls. i.e. no IN controlled treatment of features is possible. + +##### **10.1.1.1.2 SendChargingInformation operation** + +The following mapping is not intended for freephone services but for supporting reverse charging on a per call basis. + +The presence of the noCharge parameter in the SendChargingInformation operation indicates that no charge should be applied to the A-party. + +If the partyToCharge parameter (also of the sendChargingInformation (SCI) operation) indicates the B-party, then the noCharge parameter, if present, should be ignored. + +If the SCI operation is received by BICC after call set-up, then the noCharge parameter, if present, should be ignored. + +If the noCharge parameter is determined not be ignored then this parameter should be mapped to the "Charge indicator" within the next backward signalling message which includes the backward call indicators parameter. + +This mapping does not exclude a different mapping in a specific national network. + +##### **10.1.1.1.3 Address complete or connect message** + +The procedures as described in 7.7.2/Q.1902.4 [7] are applicable with the following exceptions: + +Upon receipt of an ACM or CON message the awaiting address complete timer T7 is stopped. If an ACM message is received, the awaiting answer timer T9 is started. + +If an ACM message has not been sent, the received message is passed on. The message shall contain the corresponding BICC parameters, if a serviceInteractionIndicatorsTwo parameter was received in the Connect operation (see 10.1.1.1.1.4 – Mapping of the INAP serviceInteractionIndicatorsTwo). + +If an ACM message has already been sent, a received ACM message is mapped to a CPG message and a received CON message to an ANM message, respectively. The mapping of parameters is performed as described in the Call Diversion stage 3n description (see [11]). + +##### **10.1.1.1.4 Information message (national option)** + +The procedure as described in 8.12/Q.1902.4 is applicable. If call set-up information is missing, an INR message should be sent by the SSP before the InitialDP operation is sent to the SCP. + +##### **10.1.1.1.5 Answer message** + +Upon receipt of an ANM message, the awaiting answer timer T9 is stopped and the actions described in 7.8.2/Q.1902.4 [7] are performed. + +##### **10.1.1.1.6 Continuity check** + +If an IAM is received indicating that either a continuity check is requested or is performed on a previous circuit, the normal procedures as described in 7.6.2/Q.1902.4 [7] are applicable. + +The setting of the continuity indicator in the outgoing IAM message and the conditions of sending a COT message and its coding, are as described in 7.6.2/Q.1902.4 [7]. + +NOTE – As opposed to ISUP/INAP interaction, the sending of the InitialDP is not delayed until a COT message is received. + +##### **10.1.1.1.7 Simple segmentation** + +With regard to the simple segmentation procedure the SSP behaves like a local exchange. Consequently, items d), e), f) of 12.2/Q.1902.4 [7] are applicable. + +##### **10.1.1.1.8 Pre-release Information message** + +Upon receipt of a PRI message by an SSP, the received information is stored and processed upon receipt of the associated release message as specified in 12.3/Q.1902.4. + +When the SSP detects that additional information is to be sent at release time, this information is sent in a PRI message immediately prior to the REL message. + +#### **10.1.1.2 Normal call release** + +The CCF part of the SSP releases the call as described in item b) of clauses 11.2 and 11.3/Q.1902.4 [7]. For the SSF part of the SSP the general rules described in clause 6/Q.1238.2 [5] are applicable. + +#### **10.1.1.3 Suspend, resume** + +Upon receipt of a SUS message with the indication "network initiated", the timer TSUS is started to ensure that a RES message with the indication "network initiated", or a REL message, is received. The received SUS message is not passed on. If the timer TSUS expires, the procedures described in 10.2/Q.1902.4 [7] apply. The value of timer TSUS depends on the time limits received in serviceInteractionIndicatorsTwo parameter. + +#### **10.1.1.4 ReleaseCall operation** + +Upon receipt of the ReleaseCall operation, the SSP sends REL messages in both directions. The cause indicators parameter contains the releaseCallArg parameter of the ReleaseCall operation. If no releaseCallArg was present, cause value #31 is sent. Furthermore, the normal procedures as described in clause 11/Q.1902.4 [7] are applicable. + +#### **10.1.1.5 Transfer of the called IN number and original called IN number** + +In all cases, the calledPartyNumber parameter sent in the InitialDP operation is transferred in the called IN number parameter to the succeeding exchange. + +The address presentation restricted indicator of the Called IN number parameter is set according to the called IN number presentation restricted indicator received in the INAP serviceInteractionIndicatorsTwo parameter. + +If the Called IN Number parameter had been received from the preceding exchange, but no Original Called IN Number was received, the contents of the received Called IN Number is transferred unchanged in the Original Called IN number parameter. + +If an Original Called IN Number is received, it is passed on unchanged. + +##### **10.1.1.5.1 Interworking with a SN/CMN not supporting the called IN number or the original called IN number parameter** + +No specific action is required. + +#### **10.1.1.6 Abnormal conditions** + +##### **10.1.1.6.1 General requirements on receipt of unrecognized signalling information messages and parameters** + +With regard to the handling of unrecognized signalling information, an SSP behaves like a type A exchange. + +NOTE – In the future this limit may be relaxed. + +### **10.1.2 IN call with SCP request to collect further digits** + +After sending the InitialDP operation to the SCP, a RequestReportBCSMEVENT operation to arm DP CI accompanied by a CollectInformation operation, may be received from the SCP (see clause 6/Q.1238.5 [4], referred to as unmodified in ITU-T Rec. Q.1248). In this case, the specified number of digits is collected in the SSP. Encountering DP CI, i.e. the specified number of digits has been received, will result in sending an EventReportBCSM operation or a CollectedInformation operation, respectively, to the SCP. + +In addition to 10.1.1.5, the digits sent to the SCP in the EventReportBCSM operation, or the CollectedInformation operation, shall be taken into account when constructing the called IN number parameter. + +There is no further impact on the BICC protocol, and the call handling will continue as described in 10.1.1 (IN basic call), unless a further RequestReportBCSMEVENT operation to arm DP CI, accompanied by a CollectInformation operation, is received from the SCP. In this case, the procedure described above is repeated. + +### **10.1.3 Detection point processing** + +#### **10.1.3.1 General** + +The SCF uses the RequestReportBCSMEVENT operation to request the SSF to monitor for call-related events. The monitor mode is indicated in the operation as either "interrupted" or "notifyAndContinue". + +In the "notifyAndContinue" mode the event is reported as EDP-N (notification mode) in the EventReportBCSM operation or a DP-specific operation, respectively, to the SCF and normal call processing continues as described in 10.1.1 (IN basic call). + +In the "interrupted" mode, the event is reported as EDP-R (request mode) in the EventReportBCSM operation or a DP specific operation, respectively, and the SSF will wait for instructions from the SCF. + +**Table 8/Q.1922.4 – Event detection points** + +| DP | DP encountered on.. . | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CI | See 10.1.2 (IN call with SCP request to collect further digits). | +| OTS, CA | Receipt of an ACM or CPG message with an alerting indication. | +| RSF | Receipt of a route select failure event from called destination. Cause value maps to RSF according to 6.3.5/Q.1238.2 (Note). | +| OCPB, TB | Receipt of a REL message with cause value mapping to "busy" in 6.3.5/Q.1238.2 (Note). | +| ONA, TNA | Expiry of timer $T_{\text{noReply}}$ . | +| OAns, TAns | Receipt of an ANM or CON message. | +| OS, TS | Receipt of a SUS message with the indication "network initiated". | +| ORA, TRA | Receipt of a RES message with the indication "network initiated". | +| OD, TD | a) Receipt of a REL message with cause value mapping to "disconnect" in 6.3.5/Q.1238.2 in the active phase of a call (Note).
b) Expiry of timer $T_{\text{SUS}}$ . | +| OAb, Tab | Receipt of a REL message with cause value mapping to "abandon" according to 6.3.5/Q.1238.2 from a preceding exchange before the call is answered (Note). | +| NOTE – The mappings defined in 6.3.5/Q.1238.2 only defines mappings for the 128 cause values specified in ITU-T Rec. Q.850. The network operator shall have the possibility to define mapping between cause values and DPs for cause values greater 127. | | + +In the following subclauses, the differences in call processing for IN calls with dynamically armed detection points compared to the procedures described in 10.1.1 (IN basic call) and 10.1.4 (Set-up of an IN call to destination B) are listed. + +##### 10.1.3.1.1 Address complete message + +On receipt of an ACM message without cause parameter, the timer $T_{\text{NoReply}}$ is started if either DP ONA or TNA has been armed by the SCF. Event report to SCF, see 10.1.3.1. + +##### 10.1.3.1.2 Answer or connect message + +The timer $T_{\text{NoReply}}$ is stopped, if applicable. Event report to SCF, see 10.1.3.1. + +##### 10.1.3.1.3 Release message + +If a REL is received from either the preceding or succeeding CSF and corresponds to a DP armed as EDP-N (notification mode), the CCF part of the SSP releases the call like an ordinary transit exchange. For the SSF part of the SSP, the general rules described in clause 6/Q.1238.2 [4] are applicable. + +If a REL is received from the preceding or succeeding CSF at a CMN, and corresponds to a DP armed as EDP-R (request mode), the CCF part of the SSP releases the call like an ordinary CMN. For the SSF part of the SSP, the general rules described in clause 6/Q.1238.2 [4] are applicable. + +If a REL is received at an SN from the preceding CSF and corresponds to a DP armed as EDP-R (request mode), the CCF part of the SSP releases the call like an ordinary transit SN. For the SSF part of the SSP, the general rules described in clause 6/Q.1238.2 [4] are applicable. + +If a REL is received at an SN from the succeeding CSF and corresponds to a DP armed as EDP-R (request mode), the CCF part of the SSP releases the outgoing leg of the connection (both call control and bearer control related disconnection) and holds the incoming signalling leg. + +NOTE – This procedure does not directly apply in the CMN case but methods for remotely influencing bearer control have to be introduced (e.g. bearer redirection). + +For the SSF part of the SSP, the general rules described in clause 6/Q.1238.2 [4] are applicable. The call processing is suspended, and the SSP waits for SCP instructions. + +#### **10.1.3.2 Actions to be performed in case of DPs armed in the request mode (except for DP Collect information)** + +##### **10.1.3.2.1 Storage and release of initial address information** + +Initial address information is not released from memory on receipt of an ACM message. This is not true for a possible received bearer related information (e.g. Codec List for codec negotiation), because the bearer redirect procedure will completely renegotiate bearer information. + +NOTE – Memory capacity in the exchange may limit the use of services requiring the storage of initial address information. + +##### **10.1.3.2.2 Signalling procedures for connection type allowing fallback** + +If: + +- a) an IAM was received with the TMR value set to "64 kbit/s unrestricted preferred"; and +- b) no fallback has already been performed, + +then a fallback is performed on receipt of the Connect operation as described in 8.6/Q.1902.4 [7]. + +##### **10.1.3.2.3 Impact on supplementary services** + +###### **10.1.3.2.3.1 User-to-user signalling** + +###### **10.1.3.2.3.1.1 User-to-user signalling, service 1** + +If user-to-user service 1 is implicitly requested, the user-to-user information parameter is discarded from the IAM message and the user-to-user indicators parameter indicating "user-to-user information discarded by the network" is sent in the ACM message, + +If the user-to-user service 1 was explicitly requested as "not essential", the user-to-user indicators parameter is discarded from the IAM and service 1 is indicated as "not provided" in the ACM. + +If the user-to-user service 1 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.3.2.3.1.2 User-to-user signalling, service 2** + +If the user-to-user service 2 was explicitly requested as "not essential", the user-to-user indicators parameter is discarded from the IAM and service 2 is indicated as "not provided" in the ACM. + +If the user-to-user service 2 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.3.2.3.1.3 User-to-user signalling, service 3** + +- a) *Service request during call set-up* + +If the user-to-user service 3 was explicitly requested as "not essential", the user-to-user indicators parameter is discarded from the IAM and service 3 is indicated as "not provided" in the ACM. + +If the user-to-user service 3 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### b) *Service request after call set-up* + +An FRQ with facility indicators set to "user-to-user service" and the user-to-user indicators parameter (containing the relevant service 3 information) is responded by an FRJ message indicating "not provided" for service 3 in the user-to-user indicators. + +### 10.1.4 Set-up of an IN call to destination B + +This clause describes the set-up of an IN call to destination B after a user interactive dialogue has been performed, or after the SSF has reported an EDP-R in the EventReportBCSM operation, or a DP specific operation, respectively, to the SCF. In these situations, the call set-up differs from the normal call set-up for the "IN basic call". + +#### 10.1.4.1 Successful call set-up + +##### 10.1.4.1.1 Forward address signalling + +###### 10.1.4.1.1.1 Connect operation + +On receipt of the Connect operation, the actions described in 10.1.1.1.1.1 (Connect operation) are performed with the following exception: + +- a) An ACM message is sent towards the originating local exchange, if none had been sent before, when the following conditions are satisfied: + - if the incoming IAM indicated "*COT to be expected*", a Continuity message, with the Continuity Indicators parameter set to "*continuity*", has been received. + - the incoming bearer set-up procedure is successfully completed. + +##### 10.1.4.1.2 Mapping of the INAP serviceInteractionIndicatorsTwo + +The SCF logic may generate new service interaction information for the call. + +In this case, the indicators of the INAP serviceInteractionIndicatorsTwo parameter relevant for the forward direction, i.e. to be mapped into the IAM, are treated as described in 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo). + +The handling of the indicators relevant for the backward direction is, however, different: + +- The indicators contained in the received INAP serviceInteractionIndicatorsTwo parameter are compared one by one against the indicators that are stored in the SSP, i.e. that have been received in an earlier INAP operation. +- If the received value of an indicator differs from the one that is stored in the SSP, then this indicator is mapped to the corresponding value in the appropriate BICC parameter. +- If the received value of an indicator is equal to the one that is stored in the SSP, then this indicator is mapped to the value "no indication" in the appropriate BICC parameter. + +If, for the call, no new service interaction information was received, then the exchange applies the information that is stored, i.e. the forward indicators sent in the IAM are the same as for the previous connection, backward indicators need not be sent. + +##### 10.1.4.1.3 Sending of backward messages + +If backward messages have already been sent to preceding exchanges, it may be required: + +- a) to map a received message into another message; or +- b) to generate another message instead of the message, that would normally be generated. + +Table 9 describes which message is to be sent in the different cases. + +**Table 9/Q.1922.4 – Sending of backward messages** + +| Message received or →
message to be sent,
respectively

↓ Messages already sent | ACM | CPG
"alerting" or
"in-band
information
or an.. ." | CPG
"progress" | CON | ANM | +|-----------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------------------------------|-------------------|-----------------------------------------|-------------------------------| +| ACM/CON not sent | ACM
(Note 1) | Not relevant | Not relevant | CON
(Note 1) | Not relevant | +| ACM sent, ANM not sent | CPG
(Note 1) | CPG | CPG | ANM
(Note 1) | ANM | +| ANM/CON sent for
previous connection, but
ANM/CON not received
for actual connection | CPG
"progress"
(Notes 1
and 2) | CPG
"progress"
(Note 2) | CPG
"progress" | CPG
"progress"
(Notes 1
and 2) | CPG
"progress"
(Note 2) | +| ANM/CON sent for
previous connection and
ANM/CON received for
actual connection | Not relevant | Not relevant | CPG
"progress" | Not relevant | Not relevant | + +NOTE 1 – If a serviceInteractionIndicatorsTwo parameter was provided in the INAP operation, this message carries the corresponding BICC parameters, if applicable. +NOTE 2 – An originating local exchange conforming to [1] discards this CPG message since no generic notification parameter is contained in the message. + +##### 10.1.4.1.4 Address complete message + +Upon receipt of an ACM message the following actions shall be performed: + +- The awaiting address complete timer T7 is stopped. +- If a UID action indicators parameter indicates "stop or do not start T9", then the SSP shall not start/shall stop timer T9 and shall start timer $T_{UID}$ , else timer T9 is started or restarted, respectively. +- If a UID action indicators parameter indicates "through-connect in both directions", the SSP shall through-connect the transmission path in both directions (if not already connected). + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). If the ACM contains a UID action indicators parameter, then the parameter shall be passed on transparently to preceding exchanges unless an ANM has already been sent. + +##### 10.1.4.1.5 Call Progress message (Basic call) + +Upon receipt of a CPG message the following actions shall be performed: + +- If a UID action indicators parameter indicates "stop or do not start T9", then SSP shall not start/shall stop timer T9 and shall start timer $T_{UID}$ . +- If a UID action indicators parameter indicates "through-connect in both directions", the SSP shall through-connect the transmission path in both directions (if not already connected). + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). If the CPG contains a UID action indicators parameter, then the parameter shall be passed on transparently to preceding exchanges unless an ANM message has already been sent. + +##### **10.1.4.1.6 Connect message** + +Upon receipt of a CON message, the awaiting address complete timer T7 is stopped and the transmission path is throughconnected in forward direction, if not already connected. + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). + +##### **10.1.4.1.7 Answer message** + +Upon receipt of an ANM message, the awaiting answer timer T9 or the timer TUID, respectively, is stopped and the transmission path is throughconnected in forward direction, if not already connected. + +Which message is sent to preceding exchanges is described in 10.1.4.1.3 (Sending of backward messages). + +#### **10.1.4.2 Timer TUID expiry** + +If TUID expires, the call is released using cause value #31 (normal, unspecified). + +#### **10.1.4.3 Abnormal conditions** + +##### **10.1.4.3.1 Handling of unexpected messages** + +The procedures described in 13.4.2/Q.1902.4 [7] are applicable with the following exceptions: + +- a) If an ACM message has already been sent for the incoming leg of the call, but an ACM has not been received for the outgoing leg of the call, then + - i) a CPG received in forward direction shall be discarded, i.e. the message is not treated as an unexpected message; + - ii) an unrecognized message received in forward direction shall not be passed on and the procedure described in item xi) of 13.4.3/Q.1902.4 [7] shall be applied. +- b) If an ANM message has already been sent for the incoming leg of the call, but an ANM has not been received for the outgoing leg of the call, then the following messages received in forward direction shall be discarded, i.e., the messages are not treated as unexpected messages: SUS, RES, FAR and FOT. + +#### **10.1.4.4 Impact on supplementary services** + +##### **10.1.4.4.1 Call hold** + +On receipt of a CPG message with the generic notification indicator set to "remote hold", a note in memory shall be set. The note shall be reset on receipt of a CPG message with the generic notification indicator set to "remote retrieval". + +If the note is set on receipt of a connect operation, then an artificial CPG message with the generic notification indicator set to "remote retrieval" shall be generated. + +##### **10.1.4.4.2 Malicious call identification** + +On receipt of an IDR message two cases exist: + +- a) If an IDR or an ANM was already sent to the preceding exchange, then the IDR message is not passed on and is immediately responded to by an IRS message. +- b) If an IDR was not sent to the preceding exchange, then the IDR message is passed on transparently towards the originating local exchange. + +If bit A of the MCID request indicators was set to 1, then, in addition to the normal procedure, the service switching point includes the charged party identification parameter, if available, into the IRS message. + +### 10.1.5 User interactive dialogue (in-band) + +If in response to the InitialDP operation, the EventReportBCSM operation or a DP specific operation, a ConnectToResource or EstablishTemporaryConnection operation is received from the SCF, then the incoming call shall be connected to a physical entity containing the SRF, i.e. intelligent peripheral (IP). In case of ConnectToResource, the SSP that interacts with the SCP supports the requested IP capabilities, and the IP is therefore either integrated or co-located in the SSP. In case of EstablishTemporaryConnection, the IP is available in another network element. Consequently, the Assist method is applied. + +#### 10.1.5.1 SSP supports requested IP capabilities + +##### 10.1.5.1.1 Successful call set-up + +###### 10.1.5.1.1.1 Forward address signalling + +###### 10.1.5.1.1.1.1 ConnectToResource operation + +On receipt of the ConnectToResource operation at an SN, the IP is connected to the incoming call if the TMR value received in the IAM message is set to either "speech" or "3.1 kHz audio" or "64 kbit/s unrestricted preferred". For the latter case, see also 10.1.3.2.2 (Signalling procedures for connection type allowing fallback). If other TMR values are received, the call is released using cause value #65. + +As the further call setup to the SRF is bound to the establishment of the complete incoming bearer connection, depending on network specific configurations, the following options for further call setup are possible: + +- 1) In case the SRF supports the Continuity Check protocol, the setup to the SRF will continue. An ACM will be sent backwards by the SN when the following conditions are satisfied: + - if the incoming IAM indicated "*COT to be expected*", a Continuity message, with the Continuity Indicators parameter set to "*continuity*" has been received; + - the incoming bearer set-up procedure is successfully completed. +- 2) In case the SRF does not support the Continuity Check protocol, the setup to the SRF will be delayed until the following conditions are satisfied: + - if the incoming IAM indicated "*COT to be expected*", a Continuity message, with the Continuity Indicators parameter set to "*continuity*" has been received. + - the incoming bearer set-up procedure is successfully completed. + +An ACM will be sent backwards when the above conditions are satisfied. + +In this case, the codec negotiation in the SN (acting as Terminating SN) depends on the internal knowledge of the capabilities of the SRF. In the worst case, the SN may have to start a codec modification when the setup starts to the called party. + +NOTE 1 – This possible delay has to be taken into account for the provision of the application timers in the SCF. + +NOTE 2 – In case of a CMN, these procedures cannot be directly applied but methods for remotely influencing bearer control have to be introduced (e.g. bearer redirection). + +###### 10.1.5.1.1.2 Address complete message or call progress message + +An ACM message containing an optional backward call indicators parameter indicating "in-band information, or an appropriate pattern is now available", is sent depending on the options mentioned in 10.1.5.1.1.1. The backward call indicators parameter in the ACM is encoded as described in 10.1.1 (IN basic call). + +Depending on the contents of the INAP serviceInteractionIndicatorsTwo and capabilities of the preceding exchanges, the UID action indicators parameter may be included in the ACM: + +###### a) *Through-connection instruction* + +If the bothway through-connect indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "required", and if a UID capability indicators parameter was received with bit A coded 1 (through-connection modification possible) in the IAM, then the UID action indicators parameter shall be included into the ACM message with bit A coded (through-connect in both directions). + +###### b) *T9 timer instruction* + +If the dialogue duration indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "long duration" and if a UID capability indicators parameter was received with bit B coded 1 (stopping of timer possible) in the IAM, then a UID action indicators parameter shall be included into the ACM with bit B coded 1 (stop or do not start T9). + +If backward messages have already been sent to preceding exchange then, instead of ACM, a CPG message is sent. This is described in 10.1.4.1.3 (Sending of backward messages). The CPG message shall contain the UID action indicators parameter as described above for the ACM message. + +###### 10.1.5.1.1.3 Answer message + +When the IP answers, the sending of an ANM message depends on the following conditions: + +- a) If the bothway through-connect indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "required", and if a through-connection capability indicator set to "through-connection modification possible" was not received in the IAM, then an ANM message is sent. +- b) If the dialogue duration indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "long duration", and if a T9 timer indicator set to "stopping of timer possible" was not received in the IAM, then an ANM message is sent. + +If backward messages have already been sent to preceding exchange then, instead of ANM, a different message may be sent. This is described in 10.1.4.1.3 (Sending of backward messages). + +NOTE – The sending of an ANM message may also be required, if a chargeable announcement is to be connected. However, charging aspects are outside the scope of this Recommendation. + +##### 10.1.5.1.2 Storage and release of initial address information + +Initial address information is retained in memory to allow a call set-up to a new destination after disconnecting the IP. This is not true for a possible received bearer-related information (e.g. Codec List for codec negotiation), because the bearer redirect procedure will completely renegotiate bearer information. + +NOTE – Memory capacity in the exchange may limit the use of services requiring the storage of initial address information. + +##### 10.1.5.1.3 Signalling procedures for connection type allowing fallback + +If: + +- a) the TMR value received in the IAM is set to "64 kbit/s unrestricted preferred"; +- b) no fallback has already been performed; and +- c) an ANM message is to be sent, i.e., the bothway throughconnect indicator in the serviceInteractionIndicatorsTwo parameter of the ConnectToResource operation was set to "required", + +then a fallback is performed on receipt of the ConnectToResource operation as described in 8.6/Q.1902.4 [7]. + +##### **10.1.5.1.4 DisconnectForwardConnection operation** + +When the DisconnectForwardConnection operation is received, the IP is disconnected. + +##### **10.1.5.1.5 Impact on supplementary services** + +###### **10.1.5.1.5.1 Connected line identification presentation** + +The following text is only applicable if an ANM message is to be sent for the IP connection and no ANM message was sent before. + +If the connected line identity was requested by the calling user, the SSP behaves as follows: + +If "no impact" was received in the INAP serviceInteractionIndicatorsTwo (connected number treatment indicator): + +- a) and a connected number is available for the IP, the procedure as described in 5.5.2.5/Q.731.5 and .6 is performed. +- b) and a connected number is not available for the IP, the SSP sends a connected number parameter in the ANM message encoded as follows: + +| | | +|--------------------------------------------|--------------------------------------------| +| nature of address indicator: | 0000000 | +| numbering plan indicator: | 000 | +| address presentation restricted indicator: | 10 (address not available) | +| Screening indicator: | 11 (network provided), no address signals. | + +If "presentation restricted" was received in the INAP serviceInteractionIndicatorsTwo (connected number treatment indicator): + +- a) and a connected number is available for the IP, the procedure as described in 6.5.2.5/Q.731.5 and .6 is performed. +- b) and a connected number is not available for the IP, then the SSP sends a connected number parameter in the ANM message encoded as shown in item b above. + +If "present called IN number" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) A connected number parameter is generated as follows: + +| | | +|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| nature of address indicator and numbering plan indicator | are encoded as received in the called party number of the IAM message, | +| address presentation restricted indicator: | 00 (presentation allowed); | +| address signals: | as received in called party number or subsequent number parameters, respectively, until ACM message was sent. | +- b) A generic number parameter "additional connected number" is not sent. + +###### **10.1.5.1.5.2 User-to-user signalling** + +The text in the following three clauses is only applicable, if an ANM message is to be sent for the IP connection, and if an ANM message was not sent before. + +###### **10.1.5.1.5.2.1 User-to-user signalling, service 1** + +If user-to-user service 1 is implicitly requested, the user-to-user information parameter is discarded from the IAM message and the user-to-user indicators parameter indicating "user-to-user information discarded by the network" is sent in the ACM message. + +If the user-to-user service 1 was explicitly requested as "not essential", the user-to-user indicators parameter is discarded from the IAM and service 1 is indicated as "not provided" in the ACM. + +If the user-to-user service 1 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.5.1.5.2.2 User-to-user signalling, service 2** + +If the user-to-user service 2 was explicitly requested as "not essential", the user-to-user indicators parameter is discarded from the IAM and service 2 is indicated as "not provided" in the ACM. + +If the user-to-user service 2 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **10.1.5.1.5.2.3 User-to-user signalling, service 3** + +###### **a) *Service request during call set-up*** + +If the user-to-user service 3 was explicitly requested as "not essential", the user-to-user indicators parameter is discarded from the IAM and service 3 is indicated as "not provided" in the ACM. + +If the user-to-user service 3 was explicitly requested as "essential", the call is cleared with cause value #29 and diagnostics in the REL message. + +###### **b) *Service request after call set-up*** + +An FRQ with facility indicators set to "user-to-user service" and the user-to-user indicators parameter (containing the relevant service 3 information) is responded by an FRJ message indicating "not provided" for service 3 in the user-to-user indicators. + +#### **10.1.5.2 Assist method – procedure in the initiating SSP** + +##### **10.1.5.2.1 Successful call set-up** + +###### **10.1.5.2.1.1 Forward address signalling** + +###### **10.1.5.2.1.1.1 EstablishTemporaryConnection operation** + +On receipt of the EstablishTemporaryConnection operation at an SN from the SCP, a connection to an external IP is established if the TMR value received in the IAM message is set to either "speech" or "3.1 kHz audio" or "64 kbit/s unrestricted preferred". For the latter case, see also 10.1.3.2.2 (Signalling procedures for connection type allowing fallback). If other TMR values are received, the call is released using cause value #65. + +The IAM message for set-up of the temporary connection is newly generated as in an originating local exchange. The IAM or the backward ACM has to be delayed according to different SRF options as described in 10.1.5.1.1.1.1. + +For routing of the call, the called party number is derived from the assistingSSPIPRoutingAddress. + +Table 10 illustrates the mapping of parameters received in the EstablishTemporaryConnection operation to parameters sent in the IAM message. + +**Table 10/Q.1922.4 – Mapping of parameters from EstablishTemporaryConnection to IAM** + +| INAP operation
EstablishTemporaryConnection (Note) | BICC message
IAM | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------| +| assistingSSPIRoutingAddress | Called party number | +| serviceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| correlationID | Correlation id | +| ScfID | SCF id | +| NOTE – Optional parameters may be absent, i.e., they are only mapped if received. | | + +Except the called party number parameter the remaining mandatory parameters of the IAM message are set as follows: + +- a) Nature of connection indicators: + - Satellite indicator: set as in an OLE + - Continuity indicator: set according to handling described in 10.1.1.1.6 + - Echo control device indicator: set as in an OLE +- b) Forward call indicators: + - National/international call indicator: set as in an OLE + - End-to-end method indicator: 00 (no end-to-end method available) + - Interworking indicator: 0 (no interworking encountered) + - End-to-end information indicator: 0 (no end-to-end information available) + - ISDN user part indicator: 1 (ISDN user part used all the way) + - ISDN user part preference indicator: 10 (ISDN user part required all the way) + - ISDN access indicator: 0 (originating access non-ISDN) + - SCCP method indicator: 00 (no indication) +- c) Calling party's category: 00001010 (ordinary subscriber). +- d) Transmission medium requirement: 00000011 (3.1 kHz audio). + +Besides the parameters listed in Table 10 (Mapping of parameters from EstablishTemporaryConnection to IAM), the IAM contains the following optional parameters: + +- propagation delay counter (set as in an OLE); +- hop counter (set as in an OLE). The necessary optional parameters according to BAT ASE for bearer data may be set as in forward call setup for transit nodes (7.2.2/Q.1902.4 [7]). + +On sending of the IAM, the awaiting address complete timer T7 is started. + +In the case of unsuccessful establishment of temporary connection, e.g., expiry of timer T7, or route busy to the SRF, the SSP should return ETCfailed error to the SCP. The SSP remains in the same state. + +The ACM message is sent to the preceding exchange encoded as described in 10.1.1 (IN basic call). + +###### **10.1.5.2.1.1.2 Interworking with a SN/CMN not supporting the Correlation Id and SCF Id parameters** + +If the parameters cannot be transferred to the assisting SSP, the set-up of the connection will fail. + +###### **10.1.5.2.1.2 Address complete message** + +Refer to 10.1.4.1.4. + +###### **10.1.5.2.1.3 Call Progress message (Basic call)** + +Refer to 10.1.4.1.5. + +###### **10.1.5.2.1.4 Connect message** + +Refer to 10.1.4.1.6. + +###### **10.1.5.2.1.5 Answer message** + +Refer to 10.1.4.1.7. + +##### **10.1.5.2.2 Storage and release of initial address information** + +In the initiating SSP, initial address information is retained to allow a call set-up to a new destination after disconnecting the IP. + +NOTE – Memory capacity in the exchange may limit the use of services requiring the storage of initial address information. + +##### **10.1.5.2.3 DisconnectForwardConnection operation** + +When the DisconnectForwardConnection operation is received from the SCP, the normal release procedures are applied for the outgoing circuit. The REL message sent in forward direction contains cause value #31. + +##### **10.1.5.2.4 DisconnectForwardConnectionWithArgument operation** + +When the DisconnectForwardConnectionWithArgument operation is received from the SCP the normal release procedures are applied for the outgoing circuit. The REL message sent in forward direction contains cause value #31. + +##### **10.1.5.2.5 Abnormal conditions** + +###### **10.1.5.2.5.1 Handling of unexpected messages** + +Refer to 10.1.4.3.1. + +##### **10.1.5.2.6 Impact on supplementary services** + +The actions as described in 10.1.4.4 are applicable. + +#### **10.1.5.3 Hand-off method – Procedure in the initiating SSP** + +On receipt of a Connect operation from the SCP, the actions described in 10.1.1 (IN basic call) or in 10.1.4 (Set-up of an IN call to destination B) are performed. The INAP correlationID and scfID parameters are mapped to the corresponding BICC parameters in the IAM message. + +#### **10.1.5.4 Assist/Hand-off method – Procedure in the assisting SSP** + +##### **10.1.5.4.1 Successful call set-up** + +###### **10.1.5.4.1.1 Forward address signalling** + +If an IAM is received in an SSP and the call is recognized as a call which is to be routed to an IP, an AssistReqInstructions operation is sent from the SSF to the SCF. The mapping of parameters is shown in Table 11. + +**Table 11/Q.1922.4 – Mapping of parameters +from IAM to AssistRequestInstruction** + +| BICC message
IAM | INAP operation
AssistRequestInstruction | +|-----------------------------|----------------------------------------------------| +| Correlation id | correlationID | + +###### **10.1.5.4.1.1.1 ConnectToResource operation** + +The procedure to be performed after receipt of the ConnectToResource operation is identical to the procedure described in 10.1.5.1 (SSP supports requested IP capabilities). + +### **10.1.6 Call gapping** + +When receiving the CallGap operation, the SSF reduces the rate at which specific service requests are sent to the SCF. The detailed procedure is described in 11.4.2/Q.1224 [2] . + +If the call is to be gapped and the gapTreatment parameter was present in the CallGap operation, then: + +- a) If the "informationToSend" indicates announcement or tone, then the ACM message contains an optional backward call indicators parameter indicating "in-band information or an appropriate pattern is now available" when the following conditions are satisfied (see Note): + - if the incoming IAM indicated "*COT to be expected*", a Continuity message, with the Continuity Indicators parameter set to "*continuity*" has been received. + - the incoming bearer set-up procedure is successfully completed. + +NOTE – This possible delay has to be taken into account for the provision of the application timers in the SCF. + +After the calling user has received the "informationToSend", the call is released and the cause indicators parameter contains the releaseCause parameter of the CallGap operation. If no releaseCause was present, cause value #31 is sent. + +- b) If the "informationToSend" indicates display information, then the call is released and a display information parameter is included in the REL message. The cause indicators parameter contains the releaseCause parameter of the CallGap operation. If no releaseCause was present, cause value #31 is sent. + +If the gapTreatment is not present in the CallGap operation, the SSF will use a default treatment depending on network-operator implementation. + +### **10.1.7 Service filtering** + +When receiving the ActivateServiceFiltering operation, the SSF handles calls which are to be filtered in a specified manner without request for instructions to the SCF. The detailed procedure is described in 11.2.14/Q.1224 [2]. + +- a) If a call is to be filtered and the "informationToSend" indicates announcement or tone, then an ACM message is sent to the preceding exchange with an optional backward call indicators parameter indicating "in-band information or an appropriate pattern is now available" when the following conditions are satisfied (Note): + - if the incoming IAM indicated "*COT to be expected*", a Continuity message, with the Continuity Indicators parameter set to "*continuity*" has been received. + - the incoming bearer set-up procedures is successfully completed. + +NOTE – This possible delay has to be taken into account for the provision of the application timers in the SCF. + +In the case of a chargeable in-band information, an ANM is sent in addition. After the calling user has received the "informationToSend" the call is released and the cause indicators parameter contains the releaseCause parameter of the ServiceFiltering operation. If no releaseCause was present, cause value #31 is sent. + +- b) If a call is to be filtered and the "informationToSend" indicates display information, then: +- if the "informationToSend" is free of charge, the call is released and a display information parameter is included in the REL message. The cause indicators parameter contains the releaseCause parameter of the ServiceFiltering operation. If no releaseCause was present, cause value #31 is sent; + - if the "informationToSend" is not free of charge, an ANM message containing the display information parameter is sent. Then the call is released and the cause indicators parameter contains the releaseCause parameter of the ServiceFiltering operation. If no releaseCause was present, cause value #31 is sent. + +#### **10.1.7.1 Impact on supplementary services** + +##### **10.1.7.1.1 Closed user group** + +If the call is a CUG call with outgoing access not allowed, then the "informationToSend" is not provided and the call is released using cause value #29 with diagnostics. The diagnostics field contains the CUG interlock code parameter name. + +### **10.1.8 SCP-initiated call** + +For an SCP-initiated call, the SSP behaves like an originating local exchange with the exception that no information is received/sent from/to the access protocol. The call set-up information needed for the generation of the IAM message is partly provided with the InitiateCallAttempt operation. The remaining mandatory fields of the IAM message are supplied with default values. This is described in the subclauses below. + +As there is no setup information received from an incoming access protocol, there is no implicit creation of a bearer connection, when the call legs of an SCP initiated call are build. An intermediate default BIWF may be used for the bearer setup. This intermediate bearer connection may be used for applying tones or announcements. If, later on, other legs are to be connected to a leg created with InitiateCallAttempt, a redirection of the bearer connections may be required. + +#### **10.1.8.1 Successful call set-up** + +##### **10.1.8.1.1 Forward address signalling** + +On receipt of an InitiateCallAttempt operation from the SCP the contents is stored and call processing is suspended. + +###### **10.1.8.1.1.1 Continue operation** + +The actions described in 7.2.1/Q.1902.4 [7] are performed. For routing of the call, the called party number is derived from the destinationRoutingAddress (see Table 12 – Mapping of parameters from InitiateCallAttempt to IAM). + +Table 12 illustrates the mapping of parameters received in the InitiateCallAttempt operation to parameters sent in the IAM message. + +**Table 12/Q.1922.4 – Mapping of parameters from InitiateCallAttempt to IAM** + +| INAP operation
InitiateCallAttempt (Note 1) | BICC message
IAM | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| destinationRoutingAddress | Called party number | +| callingPartyNumber | Calling party number | +| serviceInteractionIndicatorsTwo | See 10.1.1.1.1.4 (Mapping of the INAP serviceInteractionIndicatorsTwo) | +| Carrier | Carrier Selection Information (Note 2) | +| Carrier | Transit Network Selection (Note 3) | +| NOTE 1 – Optional parameters may be absent, i.e. they are only mapped if received. | | +| NOTE 2 – The first octet of the INAP carrier parameter is mapped to the first octet of the Carrier Selection Information. | | +| NOTE 3 – If the carrier-parameter contains more than one octet and the network option is "TNS", then the rest of the carrier parameter is copied into the Transit Network Selection parameter. In case of network option is "carrier Id", the mapping of this part of the carrier-parameter is network specific. | | + +Except for the called party number parameter, the remaining mandatory parameters of the IAM message are set as follows: + +- a) Nature of connection indicators: + - Satellite indicator: set as in an OLE. + - Continuity check indicator: set as in an OLE. + - Echo control device indicator: set as in an OLE. +- b) Forward call indicators: + - National/international call indicator: set as in an OLE. + - End-to-end method indicator: 00 (no end-to-end method available). + - Interworking indicator: 0 (no interworking encountered). + - End-to-end information indicator: 0 (no end-to-end information available). + - ISDN user part indicator: 1 (ISDN user part used all the way). + - ISDN user part preference indicator: 00 (ISDN user part preferred all the way). + - ISDN access indicator: 0 (originating access non-ISDN). + - SCCP method indicator: 00 (no indication). +- c) Calling party's category: + - 00001010 (ordinary subscriber). +- d) Transmission medium requirement: + - 00000011 (3.1 kHz audio). + +Besides the parameters listed in Table 12, the IAM contains the following optional parameters: + +- propagation delay counter (set as in an OLE); +- hop counter (set as in an OLE). +- BAT ASE with bearer data for intermediate bearer connection. + +### **10.1.9 GVNS** + +This clause describes the set-up of an GVNS call. In this situation, the call set-up differs from the normal call set-up for the "IN basic call". + +#### 10.1.9.1 Procedure in the SSP providing the GVNS access function + +In addition to the description given in 10.1.1 (IN basic call) the following actions are to be performed. + +When receiving the Connect or the ContinueWithArgument Operation with the forwardGVNS parameter, the SSP maps it to the BICC parameter "Forward GVNS" in IAM in addition to the mapping given 10.1.1 (IN basic call) according to Table 13. + +**Table 13/Q.1922.4 – GVNS Mapping of parameters from Connect/ContinueWithArgument to IAM** + +| INAP operation
Connect/ContinueWithArgument | BICC message
IAM | +|--------------------------------------------------------|-----------------------------| +| forwardGVNS | Forward GVNS | + +On receipt of ANM/CON the received BICC parameter "Backward GVNS" parameter is mapped to ERB "backwardGVNS" parameter on INAP (if armed) according to Table 14. + +**Table 14/Q.1922.4 – GVNS Mapping of parameters from ANM/CON to ERB** + +| BICC message
ANM/CON | INAP operation
EventReportBCSM | +|---------------------------------|-------------------------------------------| +| Backward GVNS | backwardGVNS | + +In addition, the SSP discards the "backward GVNS" parameter received in ANM/CON. + +On receipt of ANM/CON the Backward GVNS parameter is mapped to the backwardGVNS parameter of the EventReportBCSM operation, if applicable. + +#### 10.1.9.2 Procedure in the SSP providing the originating GVNS routing function + +In addition to the description given in 10.1.1 (IN basic call) the following actions are to be performed. + +On receiving the IAM, the actions described in 10.1.1 (IN basic call) are performed. In addition to the mapping given there, the mapping in Table 15 is applied. + +**Table 15/Q.1922.4 – GVNS Mapping of parameters from IAM to InitialDP** + +| BICC message
IAM | INAP operation
InitialDP | +|-----------------------------|-------------------------------------| +| Forward GVNS | forwardGVNS | + +When receiving the Connect or the ContinueWithArgument Operation with the forwardGVNS parameter, the SSP maps it to the BICC parameter "Forward GVNS" in IAM in addition to the mapping given in 10.1.1 (IN basic call), according to Table 16. + +**Table 16/Q.1922.4 – GVNS Mapping of parameters +from Connect/ContinueWithArgument to IAM** + +| INAP operation
Connect/ContinueWithArgument | BICC message
IAM | +|--------------------------------------------------------|-----------------------------| +| forwardGVNS | Forward GVNS | + +#### **10.1.9.3 Procedure in the SSP providing the terminating GVNS routing function** + +In addition to the description given in 10.1.1 (IN basic call), the following actions are to be performed. + +When receiving the IAM, the actions described in 10.1.1 (IN basic call) are performed. In addition to the mapping given there, the mapping in Table 17 is applied. + +**Table 17/Q.1922.4 – GVNS Mapping of parameters from IAM to InitialDP** + +| BICC message
IAM | INAP operation
InitialDP | +|-----------------------------|-------------------------------------| +| Forward GVNS | forwardGVNS | + +When receiving the Connect or the ContinueWithArgument Operation with the backwardGVNS parameter, the SSP maps it to the BICC parameter "Backward GVNS" in ANM/CON according to Table 18 in addition to the actions described in 10.1.1 (IN basic call). + +**Table 18/Q.1922.4 – GVNS Mapping of parameters +from Connect/ContinueWithArgument to ANM/CON** + +| INAP operation
Connect/ContinueWithArgument | BICC message
ANM/CON | +|--------------------------------------------------------|---------------------------------| +| backwardGVNS | Backward GVNS | + +The Forward GVNS parameter received in IAM is discarded. + +### **10.1.10 Support of VPN applications with PSS1 information flows** + +This clause describes the set-up of a VPN call requesting support of PSS1 information flows (see ITU-T Rec. Q.765.1 [12]) in the context of a VPN service provided by an IN Service logic. + +#### **10.1.10.1 Actions in a SSP at call set-up** + +If, in the node addressed as PAN, the initial address message (IAM) received contains an Application Transport parameter with the Application Context Identifier coded "PSS1 ASE (VPN)", the exchange shall apply the actions described in 10.2.2.1/Q.765.1. If the call is recognized as IN call by detecting a DP as TDP, an InitialDP operation is sent from the SSF to the SCF. + +In addition to the description given in 10.1.1 (IN basic call) the following actions are to be performed. In addition to the mapping given there, the mapping in Table 19 is applied. + +**Table 19/Q.1922.4 – VPN Mapping of parameters from IAM to InitialDP** + +| BICC message
IAM | INAP operation
InitialDP | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| CNID indicator
CNID | cNInfo (Note) | +| NOTE – The first octet is coded as the first octet of the NNI-specific information received in the APP parameter (only bits 5 and 6 (CNID indicator) are significant – see 14.2/Q.765.1). The following octets contain the Corporate Telecommunications Network Identifier (CNID) if it was present in the NNI-specific information. | | + +In addition, the optional parameter vPNIndicator set to TRUE is included in the InitialDP operation. + +#### **10.1.10.2 IN intervention to allow or stop the transfer of PSS1 information flows** + +If the INAP serviceInteractionIndicatorsTwo parameter is received in a Connect or ContinueWithArgument operation with the suppressVPNAPP indicator (as part of this parameter) set to TRUE, then the Gateway PINX functionality is invoked by the node as described in 7.2.3.2.6/Q.765.1 (Gateway PINX transformation request mechanism/ Node determining gateway PINX functionality is required). The ISUP Application Transport parameter with Application Context Identifier set to "PSS1 ASE (VPN)" is not transmitted in the outgoing IAM message and any following message. + +If the INAP serviceInteractionIndicatorsTwo parameter is received with the suppressVPNAPP indicator set to FALSE, the SSF shall ignore this indicator. + +### **10.1.11 Number Portability** + +This clause describes the call set-up of a call using a query to an IN based Number Portability server insofar as it differs from the normal call set-up for the "IN basic call" (as given in 10.1.1). + +Addressing options are according to ITU-T Rec. Q.769.1 ("separate directory number", "concatenated addressing method" (with specific nature of address), "separate RN method"), whereby INAP uses the "separate directory number" method for providing NP-related address information. + +NOTE – in case the concatenated addressing method option with NoA "national significant number" is used, the procedures described in 10.1.1 for IN basic call are applied. + +#### **10.1.11.1 Mapping of parameters from IAM to InitialDp** + +If the IAM is received and number parameters for NP purposes are included in this message, they are to be mapped to parameters in the INAP operation IDP in addition to Table 4 as shown in Table 20. + +##### *Notes to Tables 20 and 21* + +- The network options according to ITU-T Rec. Q.769.1 are indicated in the column "Option" as "separate directory number" (preferred option), "concatenated addressing method" (Option Annex A), "separate network routing number" (Option Annex B). +- A number parameter coded with Nature of Address indicator set to "network routing number in national (significant) number format" (6.1.1/Q.769.1) will be indicated by postfixing it with "(NRN)". A number parameter with Nature of Address indicator set to "network routing number concatenated with called directory number" (6.1.1/Q.769.1) will be indicated by postfixing it with "(concat)". + +**Table 20/Q.1922.4 – NP-related mapping of IAM to InitialDP** + +| Option (Note 1) | BICC message
IAM | INAP operation
InitialDP | +|------------------------------------------|-----------------------------|----------------------------------------------------| +| BICC
(separate DN) | CalledPartyNumber (NRN) | networkRoutingNumber | +| | CalledDirectoryNumber | calledPartyNumber | +| BICC
Option Annex A
(concatenated) | CalledPartyNumber (concat) | networkRoutingNumber (Note 2)
calledPartyNumber | +| BICC
Option Annex B
(separate RN) | NetworkRoutingNumber | networkRoutingNumber | +| | CalledPartyNumber | calledPartyNumber | + +NOTE 1 – The network option is determined by analysing the NoA of the BICC:CdPN and the existence of the parameters CDN or NRN. In case no CDN or NRN parameter and none of the NP-related NoA indicators are present, the mapping of Table 4 remains valid (no number portability took place before IN triggering). + +NOTE 2 – The usage of the network routing number (length, numbering plan, ...) is network specific. In order to separate the RN from the DN in the concatenated case, the SSP must have knowledge about all types of RNs used in that network and for each RN modification the SSP would have to be updated. + +#### **10.1.11.2 Mapping of parameters from INAP operation Connect to IAM** + +When the Connect operation is received from the NP server, the number parameters included in this operation have to be mapped to parameters in the BICC:IAM message in addition to Table 5 as shown in Table 21. In case the INAP parameter DestinationRoutingAddress does not contain the NoA for NRN, the mapping of Table 5 remains valid as a whole and the CDN is discarded (see also 10.1.12.3). + +**Table 21/Q.1922.4 – NP-related mapping of CONNECT to IAM** + +| Option | INAP operation
CONNECT | BICC message
IAM | +|------------------------------------------|-----------------------------------|-----------------------------| +| BICC
(separate DN) | destinationRoutingAddress (NRN) | CalledPartyNumber (NRN) | +| | calledDirectoryNumber (Note 1) | CalledDirectoryNumber | +| BICC
Option Annex A
(concatenated) | destinationRoutingAddress (NRN) | CalledPartyNumber (concat) | +| | calledDirectoryNumber (Note 2) | | +| BICC
Option Annex B
(separate RN) | destinationRoutingAddress (NRN) | NetworkRoutingNumber | +| | calledDirectoryNumber (Note 3) | CalledPartyNumber | + +NOTE 1 – The INAP:calledDirectoryNumber parameter needs not to be received. In this case, the Called Party Number stored when receiving Connect has to be mapped to the BICC:CalledDirectoryNumber. +NOTE 2 – The INAP:calledDirectoryNumber parameter needs not to be received. In this case, the Called Party Number stored when receiving Connect has to be prefixed by the destinationRoutingAddress and the NoA changed to "network routing number concatenated with called directory number". +NOTE 3 – The INAP:calledDirectoryNumber parameter needs not to received. In this case, the stored Called Party Number is not changed if an INAP:destinationRoutingAddress with NoA "network routing number in national (significant) number format" is received. + +#### **10.1.11.3 SCP (non-NP-server) acting on a ported number** + +In addition to the description in 10.1.1 (IN basic call), the following actions have to be performed. + +In case a calledDirectoryNumber or networkRoutingNumber parameter is received in the incoming IAM message, and a destinationRoutingAddress is received without NP-specific NoA-indication, these parameters have to be discarded in the outgoing IAM. I.e., the INAP: destinationRoutingAddress (without NP-specific NoA) sent in a CONNECT operation for non-NP specific service from an SCP is mapped to a calledPartyNumber parameter (without NP-specific NoA) as in normal "IN basic call". + +#### **10.1.11.4 Mapping of the INAP ServiceInteractionIndicatorsTwo** + +Additionally to the description in 10.1.1.1.3 (IN basic call), the "Call to be offered indicator" is extended by the new value "callOfferingNoINImpact". + +In case the callOfferingTreatmentIndicator is contained in the SIITwo parameter and set to "callOfferingNoINImpact", the SSP shall not generate a CallOfferingTreatmentIndicator nor modify an already received one. + +#### **10.1.11.5 Transfer of the called IN number** + +Additionally to the description in 10.1.1.5 (IN basic call), the treatment of the called IN number is extended by using an additional parameter "calledINNumberOverriding" within SIITwo. + +If this parameter is set to FALSE, the SSP shall not generate the CalledINNumber, nor overwrite an already existing one. + +### **10.1.12 Global Call Reference** + +The Global Call Reference Parameter is introduced in BICC (Rec. ITU-T Q.1902.3) and INAP CS-4 to assist the correlation of Charging Data Records for the same call from different nodes and operators by using a common call reference which uniquely identifies the call. + +#### 10.1.12.1 Treatment of Global Call Reference at call setup + +In addition to the description given in 10.1.1 (IN basic call), the following actions are to be performed. In addition to the mapping given there the mapping in Table 22 is applied. + +**Table 22/Q.1922.4 – Mapping of parameter from IAM to InitialDP** + +| BICC message
IAM | INAP operation
InitialDP | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| Global Call Reference | globalCallReference | +| NOTE – In case the CCF receives separately a Call Reference parameter from BICC, it will be mapped to the INAP callReference parameter, but should not influence the globalCallReference parameter. | | + +#### 10.1.12.2 Treatment of Global Call Reference for outgoing legs created by a T-BCSM processing + +In case T-BCSM processing creates a new outgoing leg (e.g. CONNECT after a trigger detection point T\_Busy), the same handling of the Global Call Reference has to be done as for call diversion supplementary services, e.g., optionally a new Global Call Reference for the outgoing leg may be determined (see ITU-T Rec. Q.732.7). Otherwise, triggering of TDPs does not influence the Global Call Reference. + +#### 10.1.12.3 Providing the Global Call Reference for SCP-initiated calls + +In addition to the description given in 10.1.8 (SCP initiated call), the following actions are to be performed. In addition to the mapping given there, the mapping in Table 23 is applied. + +**Table 23/Q.1922.4 – Mapping of parameters from InitiateCallAttempt to IAM** + +| INAP operation
InitiateCallAttempt | BICC message
IAM | +|-----------------------------------------------------------------------------------------------------------------|-----------------------------| +| globalCallReference | Global Call Reference | +| NOTE – In case the INAP callReference parameter is received, it is mapped to the BICC Call Reference parameter. | | + +### 10.1.13 Pivot Routing and Redirection + +This clause describes an interaction using the Pivot Routing and Redirection which are specified in ITU-T Rec. Q.730 associated with an IN call. In addition to the description given in 10.1.1.1.1.1 (Connect operation), the following actions are to be performed in an SSP. + +When an SSP receives a redirectServiceTreatmentIndicator parameter included in a serviceInteractionIndicatorsTwo parameter by Connect operation from a SCP, the SSP may decide the invocation of either Pivot Routing or Redirection in order to reroute the call toward a new destination address indicated by destinationRoutingAddress parameter. If a redirectServiceTreatmentIndicator parameter does not exist, neither Pivot Routing nor Redirection is allowed and the Connect operation is normally processed in the SSP (see 10.1.1.1.1.1). + +In the event of the existence of a redirectReason parameter in the redirectServiceTreatmentIndicator parameter, whether the Pivot Routing/Redirection can be actually invoked depends on the indicated redirectReason parameter value within the redirectServiceTreatmentIndicator parameter and the conditions of the SSP as specified in ITU-T Rec. Q.730 (e.g., whether the SSP receives a Pivot/Redirection capability parameter in an IAM or not). When the invoking reason was indicated in the received redirectReason parameter, the SSP decides according to it whether the Pivot Routing/Redirection can be invoked. If the indicated redirectReason parameter value corresponds to + +the received Performing Pivot/Redirection Reason (included in the Pivot/Redirection forward information parameter) in the IAM message, the SSP can invoke the Pivot Routing/Redirection, and the redirectReason parameter value should be set in the "Invoking Pivot/Redirection Reason" field in the Pivot routing/Redirection backward information parameter in a FAC/REL message. In the other cases, neither Pivot Routing nor Redirection is allowed and the Connect operation is normally processed in the SSP (see 10.1.1.1.1.1). + +In the event of the absence of a redirectReason parameter in the redirectServiceTreatmentIndicator parameter, whether the Pivot Routing/Redirection can be actually invoked depends on the conditions of the SSP as specified in ITU-T Rec. Q.730. (e.g., whether the SSP received a Pivot/Redirection capability parameter in an IAM or not). In the other cases, neither Pivot Routing nor Redirection is allowed and the Connect operation is normally processed in the SSP (see 10.1.1.1.1.1). + +When the SSP invokes the Pivot Routing, the mapping in Table 24 is applied. + +**Table 24/Q.1922.4 – Mapping of parameters from Connect to FAC for Pivot Routing** + +| INAP operation
Connect | ISUP/BICC message
FAC | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| destinationRoutingAddress | Redirection Number | +| redirectReason | Pivot routing backward information (Note) | +| NOTE – If the redirectReason parameter exists, it should be mapped to the "Invoking Pivot Reason" field in the Pivot routing backward information parameter. | | + +When the SSP invokes the Redirection, the mapping in Table 25 is applied. + +**Table 25/Q.1922.4 – Mapping of parameters from Connect to REL for Redirection** + +| INAP operation
Connect | ISUP/BICC message
REL | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| +| destinationRoutingAddress | Redirection Number | +| redirectReason | Redirection backward information (Note) | +| NOTE – If the redirectReason parameter exists, it should be mapped to the "Invoking Redirection Reason" field in the Redirection backward information parameter. | | + +### **10.1.14 Actions to be performed in local exchanges** + +#### **10.1.14.1 Actions in the originating local exchange** + +For an IN basic call, the normal BICC basic call procedures are applicable as described in [7] for originating local exchanges, unless indicated otherwise in the subclauses below. + +##### **10.1.14.1.1 Successful call set-up** + +###### **10.1.14.1.1.1 Forward address signalling** + +If the exchange has the capability to through-connect the transmission path in both directions upon receipt of the UID action indicators parameter with bit A coded 1, then the exchange shall send the UID capability indicators parameter in the IAM message with bit A coded 1. + +If the exchange has the capability to stop or not to start timer T9 upon receipt of the UID action indicators parameter with bit B coded 1, then the exchange shall send the UID capability indicators parameter in the IAM message bit B coded 1. + +###### **10.1.14.1.1.2 Address complete, call progress, connect or answer message** + +Upon receipt of an ACM or CPG message with the UID action indicators parameter indicating "through-connect in both directions" (bit A coded 1), the local exchange shall through-connect the transmission path in both directions, if not already connected. + +Upon receipt of an ACM or CPG message with the UID action indicators parameter indicating "stop or do not start T9 timer" (bit B coded 1), the local exchange shall not start/shall stop timer T9 and shall start timer $T_{UID}$ to guard the connection. If $T_{UID}$ was already running upon receipt of the UID action indicators parameter with bit B coded 1, then $T_{UID}$ shall be restarted. + +Upon receipt of an ANM or CON message, the local exchange shall stop T9 or $T_{UID}$ , if running. + +If $T_{UID}$ expires, see subclause 10.1.4.2 (Timer $T_{UID}$ expiry). + +If received in these messages, the conference treatment indicators parameter shall be stored in the exchange. If the parameters have already been stored, then the stored information is overwritten. The application of this parameter is described in clause 12 (Interaction between IN basic call and ISDN supplementary services). + +#### **10.1.14.2 Actions in the destination local exchange** + +##### **10.1.14.2.1 Successful call set-up** + +###### **10.1.14.2.1.1 Forward address signalling** + +If received in the IAM message, the following parameters shall be stored: conference treatment indicators, call diversion treatment indicators, called IN number, Original Called IN number. + +The application of these parameters is described in clause 12 (Interaction between IN basic call and ISDN supplementary services). + +###### **10.1.14.2.1.1.1 Preventing of call offering for calls not routed via IN at a destination access** + +Upon receipt of an IAM for an access which is marked as "prevent call offering for non-authorized calls", the following actions are performed: + +- If the IAM contains the call to be offered indicator set to "call offering allowed" in the call offering treatment indicators parameter field, the call is set up as described in 7.2.8/Q.1902.4 [7]. +- If the IAM contains either the call to be offered indicator set to "call offering not allowed" in the call offering treatment indicators parameter field, or no call offering treatment parameter field at all, the call is released using cause value #21 (call rejected) without diagnostics in the REL message. + +NOTE – If the functionality required for this procedure is not implemented in the DLE the call to be offered indicator is regarded as an unknown parameter value and treated as described in 13.4/Q.1902.4 [7]. The compatibility information for the call offering treatment indicators parameter field is given in Appendix I. + +### **10.1.15 Actions in an intermediate exchange** + +#### **10.1.15.1 In an intermediate exchange not starting timer T9** + +An intermediate exchange not starting timer T9 shall not modify the UID capability and UID action indicators parameters; these two parameters shall be passed on transparently. + +#### **10.1.15.2 In an intermediate exchange starting timer T9** + +On receipt of the UID capability parameter, the intermediate exchange shall pass it on transparently to the succeeding exchange, if it has the capability to stop or not to start T9 timer upon receipt of the UID action indicators parameter with bit B coded 1. Otherwise, the bit B of the UID capability parameter shall be set to 0. + +On receipt of the UID action indicators parameter indicating "stop or do not start T9 timer" (bit B coded 1), the intermediate exchange shall not start/shall stop timer T9 and shall start timer $T_{UID}$ to guard the connection. If $T_{UID}$ was already running upon receipt of the UID action indicators parameter with bit B coded 1, then $T_{UID}$ shall be restarted. + +The UID action indicators parameter shall be passed on transparently to the preceding exchange. + +Upon receipt of an ANM or CON message, the intermediate exchange shall stop T9 or $T_{UID}$ , if running. + +If $T_{UID}$ expires, see 10.1.4.2 (Timer $T_{UID}$ expiry). + +### 10.1.16 Actions in international gateway exchanges + +The UID action indicators and UID capability indicators parameters are only sent across the international interface if a bilateral agreement between both network operators exists. + +## 10.2 Bearer unrelated connections + +For further study. + +# 11 Interaction with other networks + +For further study. + +# 12 Interaction between IN basic call and ISDN supplementary services + +The description in this clause assumes that the SCF controls IN service(s) dependent whether ISDN supplementary services are influenced for a call. + +An overview on the interactions between IN services and ISDN supplementary services is given in Table 26. + +The second column of the table marked "possibly impacted by IN services" identifies the ISDN supplementary services for which SCF control is needed. As a consequence, indications "impact/no impact" are required for these supplementary services which are to be sent via the INAP in an appropriate operation (see Appendix II). The third column contains the reference to the clause describing the action to be taken in case of "impact". The fourth column identifies the exchange where the action is to be performed. In the case where the affected exchange is not the SSP itself, a new instruction indicator is needed which is to be transferred in an BICC message to the originating or destination local exchange, or both respectively. + +**Table 26/Q.1922.4 – Interactions between IN basic call and ISDN supplementary services** + +| ISDN Supplementary service | BICC protocol possibly impacted by IN services | if impacted by IN service(s) the following action is performed | Affected exchange | +|-----------------------------------------|------------------------------------------------|----------------------------------------------------------------|-------------------| +| Advice of charge at call set-up | No | | | +| Advice of charge during the call | No | | | +| Advice of charge at the end of the call | No | | | +| Call deflection | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Call forwarding on busy | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Call forwarding on no reply | Yes | See 12.1 (Call diversion) | SSP/DLE | + +**Table 26/Q.1922.4 – Interactions between IN basic call and ISDN supplementary services** + +| ISDN Supplementary service | BICC protocol possibly impacted by IN services | if impacted by IN service(s) the following action is performed | Affected exchange | +|-----------------------------------------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------------------|--------------------------| +| Call forwarding unconditional | Yes | See 12.1 (Call diversion) | SSP/DLE | +| Calling line identification presentation
Calling line identification restriction | Yes | See 12.2 (Calling line identification presentation/restriction) | SSP | +| Call hold | No | | | +| Call waiting | No | | | +| Closed user group | No | | | +| Completion of calls to busy subscribers | Yes | See 12.3 (Completion of calls service) | SSP | +| Completion of calls on no reply | Yes | See 12.3 (Completion of calls service) | SSP | +| Conference call, add-on | Yes | See 12.4 (Conference) | OLE/DLE | +| Connected line identification presentation
Connected line identification restriction | Yes | See 12.5 (Connected line identification presentation/restriction) | SSP | +| Direct dialling in | No | | | +| Explicit call transfer | Yes | See 12.6 (Explicit call transfer) | SSP | +| GVNS | No | | | +| International telecommunication charge card | No | | | +| Malicious call identification | Yes | See 12.7 (Malicious call identification) | SSP/DLE | +| Meet-me conference | No | | | +| Multilevel precedence and preemption | No | | | +| Multiple subscriber number | No | | | +| Reverse charging | Yes | National network specific | | +| Subaddressing | No | | | +| Terminal portability | No | | | +| Three party | Yes | See 12.8 (Three party) | OLE/DLE | +| User-to-user service 1 implicit | No | | | +| User-to-user service 1 explicit | No | | | +| User-to-user service 2 explicit | No | | | +| User-to-user service 3 explicit | No | | | + +## **12.1 Call diversion** + +### **12.1.1 Actions in the service switching point** + +If "suppress information" was received in the INAP serviceInteractionIndicatorsTwo (call diversion notification treatment indicator), then the following parameters shall be discarded, if received: + +- a) generic notification indicator parameter with "call is diverting"; +- b) call diversion information parameter; +- c) redirection number parameter; +- d) redirection number restriction parameter. + +### **12.1.2 Actions in the destination local exchange** + +#### **12.1.2.1 Call forwarding unconditional** + +Call forwarding unconditional activated by the ISDN subscriber is suppressed, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). The call is offered to the subscriber. + +#### **12.1.2.2 Call forwarding busy** + +Call forwarding busy activated by the ISDN subscriber is not performed, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). The call is released using the appropriate cause in the REL message. + +#### **12.1.2.3 Call forwarding on no reply** + +Call forwarding on no reply activated by the ISDN subscriber is not performed, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). Call offering to the subscriber continues. + +#### **12.1.2.4 Call deflection** + +Call deflection requested by the ISDN subscriber is rejected, if "call diversion not allowed" was received in the call diversion treatment indicators (call to be diverted indicator). Call offering to the subscriber continues. + +## **12.2 Calling line identification presentation/restriction** + +### **12.2.1 Actions in the service switching point** + +If a callingPartyNumber parameter or GenericNumbers parameter has been received in the Connect operation, then the mapping of these parameters must not compromise existing services supported by BICC (refer to Table 5 – Mapping of parameters from Connect to IAM). + +## **12.3 Completion of calls service** + +### **12.3.1 Completion of calls to busy subscribers** + +#### **12.3.1.1 Actions in the service switching point** + +If "reject call completion request" was received in the INAP serviceInteractionIndicator parameter (call completion treatment indicator), then in a received REL message a "CCBS possible" in the diagnostics field of the cause indicators is replaced with "CCBS not possible". + +### **12.3.2 Completion of calls on no reply** + +#### **12.3.2.1 Actions in the service switching point** + +If "reject call completion request" was received in the INAP serviceInteractionIndicator parameter (call completion treatment indicator), then in a received ACM (subscriber free) or CPG (alerting) + +message a "CCNR possible" in the CCNR Possible indicator parameter is replaced with "CCNR not possible". + +## 12.4 Conference + +### 12.4.1 Actions in the originating or destination local exchange + +A request from an ISDN subscriber to add a call to a conference is rejected, if "reject conference request" was received in the conference treatment indicators (conference acceptance indicator). + +If "reject conference request" is received in the conference treatment indicators (conference acceptance indicator) for a call which is part of a conference call, then this IN call is cleared. + +## 12.5 Connected line identification presentation/restriction + +### 12.5.1 Actions in the service switching point + +If "no impact" was received in the INAP serviceInteractionIndicatorsTwo (connected number treatment indicator), then a connected number parameter and a generic number parameter "additional connected number" are passed on unchanged. + +If "presentation restricted" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ANM or CON message, the address presentation restricted indicator is set to "presentation restricted". +- b) If a generic number parameter "additional connected number" has been received in the ANM or CON message, the address presentation restricted indicator is set to "presentation restricted". +- c) If a redirection number parameter has been received, a redirection number restriction parameter is sent in the ANM message with bits AB set to "presentation restricted". + +If "present called IN number" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ANM or CON message, the connected number parameter is modified as follows: +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the IAM message; +address presentation restricted indicator: 00 (presentation allowed); +address signals: as received in the called party number and possible subsequent number parameters, until the ACM message was sent. +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable. +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +If "present called IN number restricted" was received in the INAP serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ANM or CON message, the connected number parameter is modified as follows: +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the IAM message; +address presentation restricted indicator: 01 (presentation restricted); +address signals: as received in the called party number and possible subsequent number parameters, until the ACM message was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable. +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +## **12.6 Explicit call transfer** + +### **12.6.1 Actions in the service switching point** + +If "suppress information" was received in the INAP serviceInteractionIndicatorsTwo (call transfer notification treatment indicator), then the following parameter shall be discarded, if received: + +- a) generic notification indicator parameter with either "call transfer, alerting" or "call transfer, active"; +- b) call transfer number parameter. + +## **12.7 Malicious call identification** + +### **12.7.1 Actions in the service switching point** + +The service switching point shall pass a received IDR message transparently to the preceding exchange. The subsequent IRS message is passed transparently to the succeeding exchange. If bit A of the MCID request indicators was set to 1, then in addition to the normal procedure the service switching point shall include the charged party identification parameter, if available, into the IRS message. + +### **12.7.2 Actions in the destination local exchange** + +If the MCID supplementary service is invoked by the called user, the registration of call information is extended by the registration of the called IN number and the charged party identification, if these parameters were received in the IAM or IRS message, respectively. + +## **12.8 Three party** + +### **12.8.1 Actions in the originating or destination local exchange** + +A request from an ISDN subscriber to establish a three-way conference is rejected if for one call, or both, respectively, "reject conference request" was received in the conference treatment indicators (conference acceptance indicator). + +If "reject conference request" is received in the conference treatment indicators (conference acceptance indicator) for a call which is part of a three party call, then this IN call is cleared. + +# **13 Interactions between IN services** + +The INAP [4] does not only support a single point of control anymore, i.e., multiple IN services can be invoked for a call even in one SSP ("multiple points of control"). In this case, the SSF has to manage interaction of several IN service features (see 6.4/Q.1238.2). This can have relevance on call control signalling if IN triggering occurs in different SSPs (see Figure 6). + +![Diagram showing the configuration with two SSPs involved in the call. It illustrates the flow of signaling between two User Equipment (UE) units, through OLEs, two SSPs (each containing SSF and CCF), and two SCPs (each containing SCF). The connections are labeled with Access signalling, ISUP, and INAP.](89f8aefc01866631793087542316cef2_img.jpg) + +The diagram shows a call path between two User Equipment (UE) units. Each UE is connected to an OLE via 'Access signalling'. The OLEs are connected to two SSPs via 'ISUP' links. Each SSP contains an SSF (Service Switching Function) and a CCF (Call Control Function). The SSFs are connected to SCPs via 'INAP' links. Each SCP contains an SCF (Service Control Function). The two SSPs are also interconnected by an 'ISUP' link. The diagram is labeled 'Q.1922.4\_F06' in the bottom right corner. + +Diagram showing the configuration with two SSPs involved in the call. It illustrates the flow of signaling between two User Equipment (UE) units, through OLEs, two SSPs (each containing SSF and CCF), and two SCPs (each containing SCF). The connections are labeled with Access signalling, ISUP, and INAP. + +**Figure 6/Q.1922.4 – Configuration with two SSPs involved in the call** + +In IN CS-2, some service compatibility checks have been defined based on the use of ServiceCompatibilityIDs assigned to an IN service. A signalling mechanism for this information is needed so that an IN service triggered somewhere in the network is aware of another IN service previously triggered for the call. As anywhere in the call path, a new triggering may occur, the service compatibility information has to be sent in both directions. + +## 13.1 Receiving an IN Service Compatibility in a BICC message + +For the incoming leg, the IN Service Compatibility parameter (see ITU-T Rec. Q.1902.3 [7]) may be received in an IAM or a FAC or a CPG message. For the outgoing leg, it may be received in a CPG, ACM, ANM, FAC, CON message. If the call is or may become an IN call, the IN Service Compatibility information has to be stored, a previously received one is discarded and the parameter is passed on. If the call may not become an IN call (e.g. because the node is no SSP), the IN Service Compatibility is sent on transparently. In case of an IN call, the IN Service Compatibility parameter is sent on as described in 13.2. + +In case a TDP-R is triggered, the actions as described in 10.1 are to be performed, with the following exceptions. + +When the SSP determines that an InitialDP operation (or a DP specific operation) is to be sent to the SCP, and if an IN service compatibility value is stored, this value has to be mapped as shown in Table 27. + +**Table 27/Q.1922.4 – Mapping of stored IN Service Compatibility to InitialDP** + +| BICC message
IAM/CPG/ACM/ANM/FAC/CON | INAP operation
InitialDP | +|-----------------------------------------|----------------------------------| +| IN Service Compatibility | INServiceCompatibilityIndication | + +## 13.2 Handling of IN Service Compatibility in case outgoing legs are created by IN + +IN-triggering may be followed by a range of INAP operations that contain the parameter INServiceCompatibilityResponse (see clause 14/Q.1238.2). This parameter is relevant only for SSF internal functions and, is used by it to create the IN Service Compatibility value or modify it if it already exists. This is done as soon as call processing is resumed when receiving one of the INAP + +operations Connect, ContinueWithArgument, Continue or if a new call segment is created with InitiateCallAttempt. + +As soon as an outgoing leg is created consequent to these operations, or an existing one reused, depending on the call state, the IAM, CPG, FAC is sent for this outgoing leg with the stored IN Service Compatibility while this parameter is sent back for the incoming leg with ACM, ANM, CON, FAC, CPG. + +When releasing the call in both directions, the SSP shall discard a previously stored value of the IN service compatibility indication. + +# 14 Parameter values (timers) + +**Table 28/Q.1922.4 – BICC timers for the SSP** + +| Symbol | Time-out value | Cause for initiation | Normal termination | At expiry | Reference | +|----------------------|----------------|-------------------------------------------------------------------|------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------| +| T SUS | SCF controlled | When SUS "network initiated" message is received | At receipt of RES "network initiated" or REL message | Initiate release procedure or inform SCF | See 10.1.1.3 (Suspend, resume)
See 10.1.3 (Detection Point processing) | +| T NoReply | SCF controlled | At receipt of ACM when DP ONA or TNA has been armed (Note) | At receipt of ANM or REL message | Inform SCF | | +| T UID | 30 minutes | At receipt of UID action indicators parameter with bit B set to 1 | At receipt of ANM message | Initiate release procedure | See 10.1.4.2 (Timer T UID expiry) | + +NOTE – Except for receipt of ACM with cause parameter. + +# Annex A Signalling flows + +This annex contains arrow diagrams showing different types of IN calls. In case of discrepancies between the flows contained in this annex and the text in the main part of this Recommendation, the text takes precedence. The different variants of bearer setup are used for illustrative purposes only and relate to the message flow examples of ITU-T Rec. Q.1902.4 (see [7]). + +The following abbreviations and notations are used in the figures: + +| | | +|-------------|------------------------------------| +| A-SSP | Assisting SSP | +| AssReqInstr | AssistRequestInstruction operation | +| (DPx) | arm DP x | +| DPx ! | DP x encountered | +| DFC | DisconnectForwardConnection | +| CTR | ConnectToResource operation | + +EstTempConn   EstablishTemporaryConnection operation +I-SSP   Initiating SSP +P&C   PromptAndCollectUserInformation operation +ReqReportBCSMEv   RequestReportBCSMEvent operation. + +The following note applies to all the call set-up flows: + +NOTE – The messages AAA and BBB are dependent on whether the Continuity procedure is supported in the subsequent SCN: + +| Case | Message AAA | Message BBB | +|------------------------------|------------------------------------------------------------------------|-------------------------------------------------------| +| Continuity is supported: | IAM indicating "continuity check performed on previous circuit" | COT indicating "continuity check successful" | +| Continuity is not supported: | No message is sent at this time | IAM indicating "continuity check not required" | + +![Sequence diagram of IN basic call for a call with forward establishment of backbone network connection.](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +The sequence diagram illustrates the call set-up process for a call with forward establishment of backbone network connection. The participants are ISN-A (Initiating Network), TSN (Transit Network), and ISN-B (Destination Network), which interact with an SCP via INAP. + +- ISN-A (containing CSF-N, BCF-N(x), SWN-1 BCF-R, SWN-2 BCF-R) sends an IAM (Action = Connect Forward, BNC characteristics) to TSN. +- TSN (containing CSF-T, BCF-N(y), SWN-1 BCF-R, SWN-2 BCF-R) sends an IAM (COT on previous, Action = Connect Forward, BNC characteristics) to ISN-B. +- ISN-B (containing CSF-N, BCF-N(z)) sends an InitialDP to the SCP. +- The SCP responds with a Connect message to ISN-B. +- ISN-A sends an APM (Action = Connect Forward, no notification, BNC-ID = y1, BIWF Addr = y) to TSN. +- TSN sends an APM (Action = Connect Forward, no notification, BNC-ID = z1, BIWF Addr = z) to ISN-B. +- ISN-B sends message "AAA" to the SCP. +- Bearer setup procedures occur between the nodes: Bearer Set-up req, Bearer-Set-up req, Bearer-Setup-Connect. +- TSN sends a COT message to ISN-B. +- ISN-B sends message "BBB" to the SCP. +- ACM (no indication), CPG (alerting), and ANM messages flow back from ISN-B through TSN to ISN-A. + +The diagram includes labels for ISUP, BICC, and INAP protocols. A small note at the bottom right corner reads Q.1922.4\_FA.1. + +Sequence diagram of IN basic call for a call with forward establishment of backbone network connection. + +**Figure A.1/Q.1922.4 – IN basic call for a call with forward establishment of backbone network connection** + +![Sequence diagram for Figure A.2/Q.1922.4 showing an IN call with SCP request. Lifelines include ISUP, ISN-A (CSF-N, BCF-N (x)), SWN-1 (BCF-R), SWN-2 (BCF-R), TSN (CSF-T, BCF-N (y)), SWN-1 (BCF-R), SWN-2 (BCF-R), ISN-B (CSF-N, BCF-N (z)), INAP, and SCP. The diagram shows the flow of messages like IAM, SAM, APM, ACM, CPG, and ANM, with specific actions and data like 'Connect Forward', 'BNC characteristics', and 'Tunel data'. Blue arrows indicate interactions with the SCP for InitialDP, ReqRepBCSM, CollectInfo, EventRepBCSM, and Connect. The sequence concludes with ACM, CPG, and ANM messages being passed back to the ISUP.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +The diagram illustrates the signaling sequence for an IN call with an SCP request. The main components and their interactions are: + +- ISUP**: External signaling interface at both ends. +- ISN-A (CSF-N)**: Initiates the call via **IAM** (Action = Connect Forward) with **(BNC characteristics)** and **(Tunel data)**. +- BCF-N (x)**: Internal component of ISN-A. +- SWN-1 (BCF-R)** and **SWN-2 (BCF-R)**: Routers in the first switching network. +- TSN (CSF-T)**: Core switching network element. +- BCF-N (y)**: Internal component of TSN. +- SWN-1 (BCF-R)** and **SWN-2 (BCF-R)**: Routers in the second switching network. +- ISN-B (CSF-N)**: Receiving switching network element. +- BCF-N (z)**: Internal component of ISN-B. +- INAP**: Interface between ISN-B and the **SCP**. +- SCP**: Service Control Point providing logic for the call. + +Key message exchanges include: + +- IAM** (Action = Connect Forward) with **(BNC characteristics)** and **(Tunel data)** from ISN-A to TSN. +- APM** (Action = Connect Forward, plus notification) from TSN to ISN-A. +- SAM** (Service Activation Message) from ISN-B to TSN. +- IAM** (COT on previous), (Action = Connect Forward), (BNC characteristics), (Tunel data) from TSN to ISN-B. +- APM** (Action = Connected) from TSN to ISN-B. +- COT** (Call On Transfer) from ISN-B to TSN. +- ACM** (Address Complete Message) from ISN-B to TSN, then to ISN-A, and finally to the external **ISUP**. +- CPG** (Call Progress) and **ANM** (Answer Message) from ISN-B to TSN, then to ISN-A, and finally to the external **ISUP**. + +Interactions with the **SCP** via **INAP** include: + +- InitialDP**: Sent from ISN-B to SCP. +- ReqRepBCSM**: Request for BCSM (Bearer Control and Status Management) information. +- CollectInfo**: Request for additional information. +- EventRepBCSM**: Report of BCSM events. +- Connect**: Command from SCP to ISN-B. + +Additional messages shown in the diagram include "AAA" and "BBB" placeholders, and dashed arrows indicating internal or specific signaling paths. + +Sequence diagram for Figure A.2/Q.1922.4 showing an IN call with SCP request. Lifelines include ISUP, ISN-A (CSF-N, BCF-N (x)), SWN-1 (BCF-R), SWN-2 (BCF-R), TSN (CSF-T, BCF-N (y)), SWN-1 (BCF-R), SWN-2 (BCF-R), ISN-B (CSF-N, BCF-N (z)), INAP, and SCP. The diagram shows the flow of messages like IAM, SAM, APM, ACM, CPG, and ANM, with specific actions and data like 'Connect Forward', 'BNC characteristics', and 'Tunel data'. Blue arrows indicate interactions with the SCP for InitialDP, ReqRepBCSM, CollectInfo, EventRepBCSM, and Connect. The sequence concludes with ACM, CPG, and ANM messages being passed back to the ISUP. + +Q.1922.4\_FA.2 + +**Figure A.2/Q.1922.4 – IN call with SCP request to collect further digits & per-call bearer set-up using bearer information transport tunnel – fast set-up (forward)** + +![Sequence diagram for IN call with user interactive dialogue (in-band) & Backward establishment of backbone network connection, with Codec negotiation. The diagram shows interactions between ISN-A, TSN, ISN-B, and an external SCP. It details the flow of IAM, APM, Bearer Set-up, COT, ACM, ANM, and CPG messages between various network elements like CSF-N, BCF-N, and SWN-1/2.](51d4540605fdfa2c090638305022143b_img.jpg) + +The sequence diagram illustrates the following interaction flow: + +- External Connections:** ISUP connects to ISN-A and ISN-B. INAP connects ISN-B to an external SCP. +- Internal Network Elements:** + - ISN-A:** Contains CSF-N, BCF-N (x), SWN-1 (BCF-R), and SWN-2 (BCF-R). + - TSN:** Contains CSF-T, BCF-N (y), SWN-1 (BCF-R), and SWN-2 (BCF-R). + - ISN-B:** Contains CSF-N, BCF-N (z), SWN-1 (BCF-R), and SWN-2 (BCF-R). +- Sequence of Messages:** + - IAM (Initial Address Message):** Sent from ISN-A to TSN and from TSN to ISN-B. It includes parameters like Action = Connect backward, Codec list, BNC-ID, and BIWF-Addr. + - APM (Address Presentation Message):** Sent from TSN to ISN-B and from ISN-B to TSN. It includes Action = Selected codec, Selected codec, and Available codec list. + - Bearer Set-up req:** Propagated from ISN-A through SWN-1 and SWN-2 to TSN, and then from TSN through SWN-1 and SWN-2 to ISN-B. + - Bearer Set-up Connect:** Propagated back from ISN-B through SWN-1 and SWN-2 to TSN, and then from TSN through SWN-1 and SWN-2 to ISN-A. + - COT (Continuation of Transfer):** Sent from TSN to ISN-B. + - ACM (Address Complete Message):** Sent from ISN-B to TSN and from TSN to ISN-A. It includes "no indication, in-band info". + - ANM (Answer Message):** Sent from ISN-B to TSN and from TSN to ISN-A. + - User interactive dialogue:** A phase where ISN-B sends an IAM (Codec List) to the SCP, which responds with APM (selected codec). ISN-B then sends an APM (Action = Modify codec) to TSN, which responds with APM (Action = Successful codec modification). ISN-B also sends CPG (Call Progress) messages to TSN and ISN-A. +- External Responses:** + - InitialIDP and CTR/P&C are sent from ISN-B to the SCP. + - DFC/Connect is sent from the SCP to ISN-B. + - ACM and ANM are sent from the SCP to ISN-B. + +Sequence diagram for IN call with user interactive dialogue (in-band) & Backward establishment of backbone network connection, with Codec negotiation. The diagram shows interactions between ISN-A, TSN, ISN-B, and an external SCP. It details the flow of IAM, APM, Bearer Set-up, COT, ACM, ANM, and CPG messages between various network elements like CSF-N, BCF-N, and SWN-1/2. + +Q.1922.4\_FA.3 + +**Figure A.3/Q.1922.4 – IN call with user interactive dialogue (in-band) & Backward establishment of backbone network connection, with Codec negotiation** + +![Sequence diagram for IN call with user interactive dialogue - Assist method, procedure in initiating SSP and assisting SSP; Multi-Network Example of combinations of Connect forward and backward. The diagram shows interactions between ISN-A, GSN, SWN-1, GSN, SWN-2, and ISN-B across Network 1 and Network 2, involving ISUP, IAM, APM, Bearer Set-up, ACM, CPG, ANM, and User Interactive Dialogue messages.](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +The diagram illustrates a multi-network call setup between Network 1 and Network 2. Network 1 contains ISN-A (with CSF-N and BCF-N (W)), SWN-1 (with BCF-R), and GSN (with CSF-G and BCF-N (X)). Network 2 contains GSN (with CSF-G and BCF-N (Y)), SWN-2 (with BCF-R), and ISN-B (with CSF-N and BCF-N (Z)). An SCP is also shown in Network 2. + +The sequence of messages is as follows: + +- ISUP messages enter the networks from the left (Network 1) and right (Network 2). +- In Network 1, ISN-A sends an IAM (Action = Connect Forward) with BNC characteristics to GSN. +- GSN sends an APM (Action = Connect Forward, plus notification) with BNC-ID = x1 and BIWF Addr = x to SWN-1. +- SWN-1 sends a Bearer Set-up req. (BNC-ID = x1, BIWF-Addr = x) to ISN-A. +- ISN-A sends a Bearer Set-up reg. to GSN. +- GSN sends an APM (Action = Connect Forward, no notification) with BNC-ID = y1 and BIWF Addr = y to SWN-2. +- SWN-2 sends a Bearer Set-up req. (BNC-ID = y1, BIWF-Addr = y) to ISN-B. +- ISN-B sends an APM (Action = Use Idle) with BNC-ID = y3 back to GSN. +- GSN sends a COT (Cot on previous) to ISN-A. +- ISN-A sends an ACM (Action = Connected) to GSN. +- GSN sends an ACM (no indication) to SWN-2. +- SWN-2 sends a Bearer Set-up-Connect to ISN-B. +- ISN-B sends a COT to GSN. +- GSN sends an ACM to SWN-1. +- SWN-1 sends a CPG to ISN-A. +- ISN-A sends an ANM to GSN. +- GSN sends an ANM to SWN-2. +- SWN-2 sends an ANM to ISN-B. +- A User Interactive Dialogue occurs between GSN and ISN-B, involving DFC/Connect, REL, and RLC messages. +- Blue arrows indicate interactions with the SCP (InitialDP, EstTempCon, AssistReqInstr, CTR/P&C, Result P&C). + +Sequence diagram for IN call with user interactive dialogue - Assist method, procedure in initiating SSP and assisting SSP; Multi-Network Example of combinations of Connect forward and backward. The diagram shows interactions between ISN-A, GSN, SWN-1, GSN, SWN-2, and ISN-B across Network 1 and Network 2, involving ISUP, IAM, APM, Bearer Set-up, ACM, CPG, ANM, and User Interactive Dialogue messages. + +Q.1922.4\_FA.4 + +NOTE – Instead of Connect, other operations may be received. If Connect is received, a normal call set-up as shown in Figure A.3 will be performed. + +**Figure A.4/Q.1922.4 – IN call with user interactive dialogue – Assist method, procedure in initiating SSP and assisting SSP; Multi-Network Example of combinations of Connect forward and backward** + +![Sequence diagram for Figure A.5/Q.1922.4 – IN call with user interactive dialogue (in-band). The diagram shows a call flow between Network 1 and Network 2. Network 1 contains ISN-A (with CSF-N and BCF-N (w)), SWN-1 (with BCF-R), and GSN (with CSF-G and BCF-N (x)). Network 2 contains GSN (with CSF-G and BCF-N (y)), SWN-2 (with BCF-R), and ISN-B (with CSF-N and BCF-N (z)). An SCP is connected to the GSNs in both networks via INAP. The call flow starts with ISUP messages (IAM, APM, Bearer Set-up req, Bearer-Setup reg, Bearer-Setup-Connect, ACM, CPG, ANM) and INAP messages (InitialDP, Connect, IAM, APM, COT, Bearer-Setup req, Bearer-Setup-Connect, COT, ACM, CPG, ANM). A 'User Interactive Dialogue' block is shown at the bottom, with arrows pointing to 'Result P&C' and '(Note) DFC/Connect'.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +The diagram illustrates a multi-network call flow for an IN call with user interactive dialogue (in-band). It is divided into two networks, Network 1 and Network 2, separated by a vertical dashed line. + +- Network 1:** + - ISN-A:** Contains CSF-N and BCF-N (w). It receives ISUP messages from the left and sends IAM, APM, Bearer Set-up req, Bearer-Setup reg, Bearer-Setup-Connect, ACM, CPG, and ANM messages. + - SWN-1:** Contains BCF-R. It acts as a relay between ISN-A and GSN. + - GSN:** Contains CSF-G and BCF-N (x). It receives messages from SWN-1 and sends messages to Network 2. +- Network 2:** + - GSN:** Contains CSF-G and BCF-N (y). It receives messages from Network 1 and sends messages to ISN-B. + - SWN-2:** Contains BCF-R. It acts as a relay between GSN and ISN-B. + - ISN-B:** Contains CSF-N and BCF-N (z). It receives messages from SWN-2 and sends messages to the right (ISUP). +- SCP:** A Service Control Point connected to the GSNs in both networks via INAP. It sends InitialDP, Connect, IAM, and APM messages. +- ISUP Messages:** + - From left to right: IAM, APM (Action = Connect Forward, plus notification) (BNC-ID = x1), (BIWF Addr = x), Bearer Set-up req. (BNC-ID = x1), (BIWF-Addr = x), Bearer-Setup reg, Bearer-Setup-Connect, ACM, CPG, ANM. + - From right to left: IAM (Action = Connect Forward), (BNC characteristics), APM (Action = Use Idle), (BNC-ID = y3), COT, ACM, CPG, ANM. +- INAP Messages:** + - From GSN in Network 1 to SCP: InitialDP. + - From SCP to GSN in Network 2: Connect (ScfID and Correlation ID), IAM (ScfID/Correlation ID) (Action = Connect Backward), (BNC-ID = y2), (BIWF-Addr = y), (BNC characteristics). + - From GSN in Network 2 to GSN in Network 1: APM (Action = Connect Forward, no notification) (BNC-ID = y1), (Cot on previous), (BNC characteristics), Bearer-Setup req. (BNC-ID = y1), (BIWF-Addr = y), COT. +- User Interactive Dialogue:** A horizontal bar at the bottom of the diagram. Arrows point from it to 'Result P&C' and '(Note) DFC/Connect'. +- Other Messages:** + - From GSN in Network 1 to GSN in Network 2: APM (Action = Connect Forward, plus notification) (BNC-ID = x1), (BIWF Addr = x), Bearer Set-up req. (BNC-ID = x1), (BIWF-Addr = x), Bearer-Setup reg, Bearer-Setup-Connect, ACM, CPG, ANM. + - From GSN in Network 2 to GSN in Network 1: APM (Action = Use Idle), (BNC-ID = y3), COT, ACM, CPG, ANM. + +Sequence diagram for Figure A.5/Q.1922.4 – IN call with user interactive dialogue (in-band). The diagram shows a call flow between Network 1 and Network 2. Network 1 contains ISN-A (with CSF-N and BCF-N (w)), SWN-1 (with BCF-R), and GSN (with CSF-G and BCF-N (x)). Network 2 contains GSN (with CSF-G and BCF-N (y)), SWN-2 (with BCF-R), and ISN-B (with CSF-N and BCF-N (z)). An SCP is connected to the GSNs in both networks via INAP. The call flow starts with ISUP messages (IAM, APM, Bearer Set-up req, Bearer-Setup reg, Bearer-Setup-Connect, ACM, CPG, ANM) and INAP messages (InitialDP, Connect, IAM, APM, COT, Bearer-Setup req, Bearer-Setup-Connect, COT, ACM, CPG, ANM). A 'User Interactive Dialogue' block is shown at the bottom, with arrows pointing to 'Result P&C' and '(Note) DFC/Connect'. + +Q.1922.4\_FA.5 + +NOTE – Instead of Connect, other operations may be received. If Connect is received, a normal call set-up as shown in Figure A.3 will be performed. + +**Figure A.5/Q.1922.4 – IN call with user interactive dialogue (in-band)** +**Hand-off method; procedure in initiating and assisting SSP; Multi-Network Example** + +# **Annex B****Exceptions for ISUP/INAP interaction** + +The interaction of ISUP to INAP can be derived by concatenating ISUP/BICC- and BICC/INAP-interaction procedures with the following exceptions: + +In case of ISUP incoming setup procedure, it is necessary, after receiving an IAM message containing the indication "continuity check is requested or performed on previous circuit", to delay sending of InitialDP until an COT message is received with success-indication. Because of this COT-handling and the different bearer-setup-procedure, it is possible in ISUP to send an ACM message as soon as the forward address information is determined after IN interaction (e.g. after CON, CTR, ETC). + +The differences relate to chapters: 10.1.1.1.1.1 Connect operation (basic call), 10.1.1.1.6 Continuity check, 10.1.4.1.1.1 Connect Operation (Detection Point Processing), 10.1.5.1.1.1.1 ConnectToResource, 10.1.5.1.1.2 ACM for IP, 10.1.5.2.1.1.1 EstablishTemporaryConnection, 10.1.6 Call gapping, 10.1.7 Service filtering. + +With regard to continuity-procedure and ACM-handling in the aforementioned clauses, the descriptions according to ITU-T Rec. Q.1601 [6] remain valid for ISUP/INAP interaction. + +Unlike the description given in 10.1.8 SCP-initiated call, the selection of a default BIWF for SCP-initiated call is not relevant in case of ISUP/INAP interaction, and BAT ASE information elements are not sent in the ISUP IAM. + +# Appendix I + +## Coding of the compatibility information for the parameters + +Table I.1/Q.1922.4 – Coding of the instruction indicators + +Default = 0 value for the subfield. + +| Parameter | Pass on not possible indicator | Discard parameter indicator | Discard message indicator | Send notification indicator | Release call indicator | Transit at intermediate exchange indicator | Broadband/narrow-band interworking indicator | +|--------------------------------------------|--------------------------------|-----------------------------|---------------------------|-----------------------------|------------------------|--------------------------------------------|----------------------------------------------| +| Call diversion treatment indicators | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Called IN number | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Call offering treatment indicators | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Charged party identification | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Conference treatment indicators | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Correlation id | Release call | Default | Default | Default | Release call | Transit interpretation | Pass on | +| Display information | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| SCF id | Release call | Default | Default | Default | Release call | Transit interpretation | Pass on | +| UID action indicators | Discard parameter | Discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| UID capability indicators | Discard parameter | Discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | +| Original Called IN number | Discard parameter | Do not discard parameter | Do not discard message | Do not send notification | Do not release call | Transit interpretation | Pass on | + +# Appendix II + +## Contents of the INAP serviceInteractionIndicatorsTwo + +The appendix contains a list of indicators which are to be transferred in the serviceInteractionIndicatorsTwo via the INAP in order to allow the SCF to control the network behaviour for IN calls. This appendix should be considered as a proposal for the INAP to transfer this type of information and not as a requirement for the detailed encoding of the serviceInteractionIndicatorsTwo. + +**Table II.1/Q.1922.4 – Basic call-related control information** + +| Control information | Values | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call to be offered indicator |
  • – call offering allowed
  • – call offering no IN impact
  • – call offering not allowed (default)
| +| Time limits for timer T SUS |
  • – as in ITU-T Rec. Q.1902.4 for timer T6
  • – 4 to 10 seconds
  • – 0 seconds (default)
| +| Bothway throughconnect indicator
NOTE – The indicator should be set to "required" in the ConnectToResource or EstablishTemporaryConnection operation, if user interaction has to be performed. If an announcement is to be connected or in other operations the indicator should be set to "not required". |
  • – required (default)
  • – not required
| +| Called IN number presentation restricted indicator |
  • – presentation allowed
  • – presentation not allowed (default)
| +| Called IN number Overriding |
  • – TRUE (default)
  • – FALSE
| +| User interactive dialogue duration indicator
NOTE – The indicator should be set to "long duration" in the ConnectToResource or EstablishTemporaryConnection operation, if the user interaction may last longer than 90 seconds. Otherwise the indicator should be set to "short duration". |
  • – long duration (default)
  • – short duration
| + +**Table II.2/Q.1922.4 – Supplementary service related control information** + +| Control information | Values | +|-------------------------------------------------|----------------------------------------------------------------------------------------| +| Call to be diverted indicator | – call diversion allowed (default)
– call diversion not allowed | +| Conference at DLE acceptance indicator | – accept conference request (default)
– reject conference request | +| Conference at OLE acceptance indicator | – accept conference request (default)
– reject conference request | +| Connected number treatment indicator | – no impact
– set "presentation restricted"
– present called IN number (default) | +| Call transfer notification treatment indicator | – no impact (default)
– suppress information | +| Call diversion notification treatment indicator | – no impact (default)
– suppress information | +| Call completion treatment indicator | – reject call completion request
– accept call completion request (default) | + +# **Appendix III** + +## **Limitations for BICC basic call procedures and supplementary services for different types of IN calls** + +The appendix provides an overview on the limitations for BICC basic call procedures and supplementary services for different types of IN calls. + +The CCBS supplementary service is, in general, not available for IN calls that require translation of the called party number. Additional limitations are listed in Table III.1. + +**Table III.1/Q.1922.4 – Limitations for BICC basic call procedures and supplementary services** + +| Type of IN call →

↓ BICC feature | IN call with DPs armed in the request mode (except DP CI) | IP connection without sending of ANM | IP connection with sending of ANM | IN call set-up after an ANM was sent for a previous connection | +|-------------------------------------------------------|------------------------------------------------------------------|---------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Basic call | | | | | +| Access delivery information | | | | not supported | +| Connection types allowing fallback capability | not supported | | not supported | not supported | +| Propagation delay determination | | | | In the OLE only the accumulated delay from the OLE to the first answered destination is available | +| Supplementary Services | | | | | +| Call diversion | | | | The OLE does not receive the following parameters: call diversion information, generic notification indicator, redirection number and redirection number restriction indicator. | +| Call waiting | | | | The generic notification indicator can not be delivered to the calling user | +| COLP | | | | The connected number and generic number received from the destination local exchange can not be delivered to the calling user | +| UUS1 implicit | not supported | | not supported | | +| UUS1 explicit | not supported | | not supported | | +| UUS2 explicit | not supported | | not supported | | +| UUS3 explicit | not supported | | not supported | | + + + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1990-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1990-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..262f213e155e417e9ab6368329b057cf403c5a35 --- /dev/null +++ b/marked/Q/T-REC-Q.1990-200107-I_PDF-E/raw.md @@ -0,0 +1,336 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1990** + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**BICC bearer control tunnelling protocol** + +ITU-T Recommendation Q.1990 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **BICC bearer control tunnelling protocol** + +## **Summary** + +This Recommendation defines the BICC bearer control tunnelling protocol. The BICC bearer control tunnelling protocol is a generic tunnelling mechanism for the purpose of tunnelling Bearer Control Protocols (BCP) over the "horizontal" BICC interface between CCUs and over the "vertical" CBC interface between CCU and BCU. + +This Recommendation defines the BICC bearer control tunnelling protocol, describing the coding and procedures for identification of the tunnelled bearer control protocol. + +## **Source** + +ITU-T Recommendation Q.1990 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 2001. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|-----|----------------------------------------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | Overview..... | 2 | +| 6 | Tunnelling of bearer control protocols by Q.1990 Protocol..... | 3 | +| 6.1 | Supported Bearer Control Protocols ..... | 3 | +| 6.2 | Coding of BCTP PDUs..... | 3 | +| 7 | Procedures..... | 4 | +| 7.1 | Normal Procedures ..... | 4 | +| 7.2 | Abnormal procedures..... | 4 | +| 7.3 | Policing of maximum length tunnelled PDUs ..... | 5 | + + + +# BICC bearer control tunnelling protocol + +# 1 Scope + +The purpose of this Recommendation is to define the BICC bearer control tunnelling protocol. The BICC bearer control tunnelling protocol is a generic tunnelling mechanism for the purpose of tunnelling Bearer Control Protocols (BCP) over the "horizontal" BICC interface between CCUs and the "vertical" CBC interface between CCU and BCU. + +This Recommendation defines the BICC bearer control tunnelling protocol, which transports the tunnelled protocol data units (PDU) of the bearer control protocols supported. It describes the coding and procedures for the identification of the tunnelled bearer control protocol. + +This Recommendation references the specific bearer control protocols that are tunnelled. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.765.5 (2000), *Signalling system No. 7 – Application transport mechanism: Bearer Independent Call Control (BICC)*. +- [2] ITU-T Q.1902.1 to Q.1902.4 (2001), *Specifications of the Bearer Independent Call Control Protocol (BICC)*. +- [3] ITU-T Q.1950 (2001), *Bearer independent call bearer control protocol*. +- [4] ITU-T Q.1970 (2001), *BICC IP bearer control protocol*. + +# 3 Terms and definitions + +For the purpose of this Recommendation, the following definitions apply: + +**3.1 tunnelling PDU generating entity:** The entity that populates and transmits the tunnelled PDUs. + +**3.2 tunnelling PDU receiving entity:** The entity that receives and interprets the tunnelled PDUs. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|------------------------------------| +| APM | Application Transport Mechanism | +| BCP | Bearer Control Protocol | +| BCTP | Bearer Control Tunnelling Protocol | +| BCU | Bearer Control Unit | + +| | | +|-------|------------------------------------| +| BICC | Bearer Independent Call Control | +| BIWF | Bearer Interworking Function | +| BVEI | BCTP Version Error Indicator | +| CBC | Call Bearer Control protocol | +| CCU | Call Control Unit | +| CSF | Call Serving Function | +| IPBCP | IP Bearer Control Protocol | +| MMSF | Media Mapping/Switching Function | +| PCI | Protocol Control Information | +| PDU | Protocol Data Unit | +| TPEI | Tunnelled Protocol Error Indicator | + +# 5 Overview + +This Recommendation assumes a reliable, sequenced, point-to-point signalling transport service between peer tunnelling PDU generating and receiving entities. + +This Recommendation supports the tunnelling of Bearer Control Protocols (BCP) over the following protocols: + +- BICC protocol. BICC tunnelling makes use of the BICC APM Mechanism, as defined in ITU-T Q.765.5 [1] and 6.4/Q.1902.4 [2]. +- CBC protocol. CBC tunnelling makes use of the H.248 tunnelling package, as defined in 6.9.5/Q.1950 [3]. + +The operation of the tunnelling mechanism is illustrated in Figure 1. + +![Diagram illustrating the operation of the BCTP tunnelling mechanism. Two identical stacks of network functions are shown, connected by a thick horizontal line labeled 'BICC' and 'Tunnel'. Each stack consists of a top box containing 'CSF' and 'CCU', connected by a curved arrow. Below this is a box labeled 'CBC'. The 'CBC' box connects to a large dashed box labeled 'Tunnelling PDU Generating & Receiving Entities'. Inside this dashed box, a box labeled 'BCU' contains 'Distr.', 'BCP1', 'BCP2', and 'BCF'. Below the 'BCU' box is a box labeled 'MMSF'. The 'MMSF' box is connected to a bottom box labeled 'BIWF'. The 'BICC' tunnel connects the 'CCU' of the left stack to the 'CCU' of the right stack. The 'Tunnelling PDU Generating & Receiving Entities' label points to the 'Distr.' box in both stacks. The diagram is labeled 'T11112820-01' in the bottom right corner.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +Diagram illustrating the operation of the BCTP tunnelling mechanism. Two identical stacks of network functions are shown, connected by a thick horizontal line labeled 'BICC' and 'Tunnel'. Each stack consists of a top box containing 'CSF' and 'CCU', connected by a curved arrow. Below this is a box labeled 'CBC'. The 'CBC' box connects to a large dashed box labeled 'Tunnelling PDU Generating & Receiving Entities'. Inside this dashed box, a box labeled 'BCU' contains 'Distr.', 'BCP1', 'BCP2', and 'BCF'. Below the 'BCU' box is a box labeled 'MMSF'. The 'MMSF' box is connected to a bottom box labeled 'BIWF'. The 'BICC' tunnel connects the 'CCU' of the left stack to the 'CCU' of the right stack. The 'Tunnelling PDU Generating & Receiving Entities' label points to the 'Distr.' box in both stacks. The diagram is labeled 'T11112820-01' in the bottom right corner. + +Figure 1/Q.1990 – Operation of the BCTP tunnelling mechanism + +# 6 Tunnelling of bearer control protocols by Q.1990 Protocol + +## 6.1 Supported Bearer Control Protocols + +The Bearer Control Protocols (BCP) supported by ITU-T Q.1990, are provided in Table 1. + +**Table 1/Q.1990 – Supported bearer control protocols** + +| Supported BCP | Reference | +|---------------|------------------| +| IPBCP | ITU-T Q.1970 [4] | + +## 6.2 Coding of BCTP PDUs + +The bearer control tunnelling protocol has a binary encoded Protocol Control Information (PCI) field of 2 octets in front of every tunnelled BCP PDU. The first octet of the BCTP Indicator field contains a 1-bit BCTP Version Error Indicator (BVEI) field and a five-bit BCTP version indicator field. The second octet of the BCTP indicator field contains a 1-bit Tunnelled Protocol Error Indicator (TPEI) field and a six-bit tunnelled protocol indicator field. + +The format of the BCTP Indicator field is shown in Table 2. + +**Table 2/Q.1990 – BCTP Indicator field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|---|------|-----|-----|------------------------------|---|---|-----|--------| +| 0 | BVEI | 1 | msb | BCTP Version Indicator | | | lsb | 1 | +| 0 | TPEI | msb | | Tunnelled Protocol Indicator | | | lsb | 2 | + +The Tunnelled Protocol Error Indicator (TPEI) field is coded as follows: + +- 0 No indication +- 1 Protocol Error Indication, Bearer Control Protocol not supported + +The following codes are used in the Tunnelled Protocol Indicator field: + +65 4321 + +- 00 0000 } spare (binary encoded protocols) + - to + - 01 0111 } +- 01 1000 } reserved for national use (binary encoded protocols) + - to + - 01 1111 } +- 10 0000 IPBCP (text encoded) +- 10 0001 spare (text encoded protocol) +- 10 0010 not used +- 10 0011 } spare (text encoded protocols) + - to + - 11 0111 } + +| | | +|---------|------------------------------------------------------| +| 11 1000 | } reserved for national use (text encoded protocols) | +| to | | +| 11 1111 | | + +NOTE 1 – The proper transport of BCTP, be it binary or text encoded, is the responsibility of the protocol carrying BCTP. Bit No. 6 may be used to differentiate between the two cases, if needed. See for example Annex A.7/Q.1950: Bearer Control Tunnelling Package. + +The BCTP Version Error Indicator (BVEI) field is coded as follows: + +| | | +|---|------------------------------------------------------| +| 0 | No indication | +| 1 | Version Error Indication, BCTP version not supported | + +The following codes are used in the BCTP Version Indicator field: + +5 4321 + +| | | +|--------|------------------------------------------------------| +| 0 0000 | Version 1 of the BCTP protocol (this Recommendation) | +| 0 0001 | spare | +| 0 0010 | not used | +| 0 0011 | } spare | +| to | | +| 1 1111 | | + +NOTE 2 – Bits 8 and 6 of BCTP indicator octet 1 always have the values "0" and "1", respectively. + +NOTE 3 – Bit 8 of BCTP indicator octet 2 always has the value "0". + +# 7 Procedures + +## 7.1 Normal Procedures + +The Tunnelling PDU Generating Entity populates the BCTP Indicator with the appropriate value to describe the Bearer Control Protocol that is transported in the tunnel and it adds this BCTP Indicator in front of every outgoing PDU. The Tunnelled Protocol Error Indicator is set at the "No indication" value. The BCTP Version Indicator indicates the used version of the BCTP Protocol. The BCTP Version Error Indicator is set at the "No indication" value. + +Every outgoing PDU shall have the BCTP Indicator field as its first two octets. + +Upon reception of a tunnelled PDU, the Tunnelling PDU Receiving Entity checks the value of the version indicator is supported and then distributes the incoming PDU to the appropriate Bearer Control Protocol handling entity, after inspection and removal of the BCTP Indicator octets. + +## 7.2 Abnormal procedures + +If the Tunnelling PDU Receiving Entity receives a tunnelled PDU with an unsupported value of the BCTP Version Indicator: + +- it generates a two-octet PDU back into the tunnel only containing the BCTP Indicator field. The BCTP Version Error Indicator is set to the "Version Error Indication, BCTP version not supported" value. The Tunnelled Protocol Indicator is set to the same value as the Tunnelled Protocol Indicator value received. The BCTP Version Indicator field contains the version number of the version supported; +- it sends this PDU back to the Tunnelling PDU Generating Entity that sent it; and + +- it informs the control logic in the BIWF (Note). + +If the Tunnelling PDU Receiving Entity receives a tunnelled PDU with a known value of the BCTP Version Indicator, but an unknown value of the Tunnelled Protocol Indicator: + +- it generates a two-octet PDU back into the tunnel only containing the BCTP Indicator field. The Tunnelled Protocol Error Indicator is set to the "Protocol Error Indication, bearer control protocol not supported" value. The Tunnelled Protocol Indicator is set to the same value as the Tunnelled Protocol Indicator value received; +- it sends this PDU back to the Tunnelling PDU Generating Entity that sent it; and +- it informs the control logic in the BIWF (Note). + +If the Tunnelling PDU Receiving Entity receives a tunnelled PDU with the Tunnelled Protocol Error Indicator value "Protocol Error Indication, Bearer Control Protocol not supported", and/or if the Tunnelling PDU Receiving Entity receives a tunnelled PDU with the BCTP Version Error Indicator value "Version Error Indication, BCTP version not supported": + +- it informs the control logic in the BIWF (Note). + +NOTE – It is the responsibility of the control logic in the BIWF to take appropriate release actions. The error message in the CBC protocol that carries the tunnel shall apply cause code "Interworking unspecified". However, the control logic in the BIWF is out of the scope of this Recommendation. Procedures for version negotiation and protocol negotiation are for further study. + +## **7.3 Policing of maximum length tunnelled PDUs** + +The tunnelling PDU generating entity shall police the maximum length of the tunnelled PDUs in order to ensure that the maximum data transfer capabilities of the tunnelling mechanisms in BICC and CBC are not exceeded. These maximum transfer capabilities depend on the capabilities of the underlying signalling transport network supporting the BICC [2] and CBC [3] interfaces. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.20-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.20-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.20-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.20-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.20-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4fb243ccc3d3287100b32eaa77df204d8a780c2c --- /dev/null +++ b/marked/Q/T-REC-Q.20-198811-I_PDF-E/raw.md @@ -0,0 +1,75 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters "ITU" in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.20** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**COMPARATIVE ADVANTAGES OF "IN-BAND" +AND "OUT-BAND" SYSTEMS** + +**ITU-T Recommendation Q.20** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.20 was published in Fascicle VI.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **COMPARATIVE ADVANTAGES OF "IN-BAND" AND "OUT-BAND" SYSTEMS** + +Signalling over telephone circuits may be effected *in* the frequency band used for speech ("in-band" signalling), or *outside* it ("out-band" signalling). In the latter case, the same channel carries both the signalling and speech frequency bands, the signalling band being separate from the speech band, and signalling equipment is an integral part of the carrier system. + +In a further type of out-band signalling, a circuit, not used for speech, can be used to effect the signalling requirements of a number of speech circuits. This may be termed "separate channel signalling". The separate channel may be: + +- a) a channel in a carrier system used to effect the signalling requirements of the remaining channels in the same carrier system which are used for speech, signalling equipment being an integral part of the carrier system: this may be termed "built-in separate channel signalling"; +- b) completely separate, in which case signalling equipment is not an integral part of the carrier system; this may be termed "completely separate channel signalling". + +### **1 Advantages of in-band signalling** + +1.1 In-band signalling can be applied to any type of line plant. The application of out-band signalling, and built-in separate channel signalling, is limited to carrier systems. + +1.2 Through-signalling can be employed at transit points, and at carrier system terminals when a telephone circuit comprises two or more carrier links. No direct current repetition and thus no delay and no distortion of signals arises at such points. Out-band signalling and built-in separate channel signalling require a direct current repetition at such points. + +1.3 Replacement of a faulty line section is easy. In the case of completely separate channel signalling, replacement of a faulty line section is based on security arrangements. + +1.4 It is impossible to set up a connection on a faulty speech path. In the case of completely separate channel signalling, a continuity check of the speech path is required. + +1.5 The full bandwidth of the speech channel is available for signalling. This facilitates the use of more than one signalling frequency. Normally the full bandwidth permits faster signalling than with a smaller signalling bandwidth. With in-band signalling, realization of this advantage is limited to those signals not required to be protected against signal imitation due to speech currents. + +### **2 Advantages of out-band signalling** + +2.1 Relative freedom from disturbances due to speech currents; freedom from disturbances due to echo-suppressors; freedom from disturbances which might arise from connections to other signalling systems. With in-band signalling it is necessary to take steps to guard against such disturbances. + +2.2 Possibility of signalling, during the setting-up of the call, by either discontinuous or continuous transmission, and the possibility of transmitting those signals during speech. Signalling during speech is not compatible with in-band signalling. + +2.3 Simplicity of terminal equipment due to § 2.1 above and to the possibility of continuous signalling. + +Out-band signalling (where the same channel carries both speech and signalling) also has the advantage of §1.3 of in-band signalling. + +Built-in separate channel signalling has the advantages of §§ 2.1, 2.2 and 2.3 of out-band, and the advantage of § 1.3 of in-band signalling. + +Completely separate channel signalling has the advantages of §§ 2.1 and 2.2 of out-band signalling and, compared with out-band signalling and built-in separate channel signalling, has the additional advantages that no direct current repetition is necessary, and no distortion of signals arises, at carrier system terminals when a circuit comprises two or more carrier links. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c95e09cfdacd5835b168921da65d1a2d3437ff03 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9284b2f13217f64792138c75faa048ad63852521d93c8baa9ccb27e8bfc504c7 +size 86317 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9466b84d004d10ebc13b0e61386fad765be57f49 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e14b373ae6e8f71deb9f949fcda39239bf5377cb1a102370c914cc1fa617fa4 +size 124956 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a49b3e63c54bcbc8a865070456a2a57b3e2aa74b --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:835ac1e18c14c3abcf887da47ba702b7414af10b330f14526a5a9c08aadc79e8 +size 81565 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b273893195dbb79ab93306cf6819afff70f4796 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed4066ef186bd6a32680468fcd982f74f35d3f1e6d0c8ae75dc8a63db4b23e82 +size 46865 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..838b532989b8d4a3a00dad25beddf0a7c9f219a7 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0ffba8c8bf8bbb0d83c2805c335de1e42ad141f168884f59d39674785a09e57 +size 46671 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/191840594f2b30516669ec8234e99d98_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/191840594f2b30516669ec8234e99d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..213d631c4c51e3b0e4eefd677d70d84d5772778c --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/191840594f2b30516669ec8234e99d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a511415c076ed18846945a2fcac88818b8ddacedac2aa42afc3c56d5b84e28e2 +size 7376 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcc2a00c472d13555435ad20597532d4cc60f0b6 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5da32023c6a81f41805dce59fe8dd364a7745085c871c160588bace7fac86fcc +size 143098 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70c2b1a2d31008129c56718fd79c5890dbac9fc1 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:386340ca815c42ff9cbd9450f51a32dfe79eec83df7edea1486166d58fa96658 +size 8234 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/307998a4f76d5fa18ce3713f51d0692f_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/307998a4f76d5fa18ce3713f51d0692f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42eec63abc4044b3e2e2c58a378504ec0f6ea309 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/307998a4f76d5fa18ce3713f51d0692f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f944d72933e071dddc57abdd379029d0b01d9a94b6797393f15d9ddaa3aedb04 +size 5701 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a42b544fbc9bc57999884b4fe9d9baacc5836f9 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96992f46a1b4a4b8bada1c9542b4058defff86f5e53a7897ab509188870d45b0 +size 115817 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91852fdf8fb892eb1557c5ed4882be0bf48ea461 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf5ba7152d7c50a7f83022db93c17e5c5361eaac04bdfef5ccad48fe7d804642 +size 111599 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0beacafdf37f3f079ef38502ada13942aefffdc --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3d731a14d7be8f848aaf4f270c8a088cdcaa6ce60f29d27618f273866969d12 +size 100888 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/4412857e90dfaa9a3df8836bcbde534b_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/4412857e90dfaa9a3df8836bcbde534b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..300864936cdbff22bbcd35469a3d57f1dd4fb06c --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/4412857e90dfaa9a3df8836bcbde534b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fa7cf7ec95a6ffe01caaa7ac99835d68378f186b1e2f62fa52030b36847e92b +size 24254 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfadc4fafd3c5349eae64b75d87016edf86da02b --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de0ff4b9b57c4ee9834600810d2a7821cc03a66358f8cd8fe3e1449e7aa614df +size 22257 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9965171c5b90c5cf2fc31d40abd057d4d1a66b9b --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ca55dc448b646899da7a2b9ce76da27e488a70c89bf3db6e1b86e134c8d057e +size 177099 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/483c43eac5aa582dfcb6e0aa8cee163f_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/483c43eac5aa582dfcb6e0aa8cee163f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92ff7772f691f5d6b740cce0afd38c7b1072f05f --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/483c43eac5aa582dfcb6e0aa8cee163f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33edd263c3276b30e3c425b31d056f5ea95ac246e879818572d85e5a90e6457f +size 6591 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/4943d0149cfafbd5c000816fcb174838_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/4943d0149cfafbd5c000816fcb174838_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bff8125915b790df3d46dd4d6245826e2ad16a80 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/4943d0149cfafbd5c000816fcb174838_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c76f2b4fcb91ecfdc20948fa75541c751d25c381c6cab586cb7ec1e7354f8ab +size 2769 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b902bf89867826e5985bbc2bee56a7386b766170 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07a16c826c524d16be40242f0b11949703ea600ed949675766bf85b9455fa2b1 +size 95688 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/5e60f40fa88ed1e63cc96ee8de0fe992_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/5e60f40fa88ed1e63cc96ee8de0fe992_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80dba25d71a9876e3b96a533edfd672dce3aa77 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/5e60f40fa88ed1e63cc96ee8de0fe992_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc0562132afaf514cf6b6be351cb1280b5aa6a73ef2a31bc7348281578dd0593 +size 8003 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7337e1a5cbce5cf572a850a2d429d4fe4470a018 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06fc3ec9d13c27f1c55638d2dcdd0b6ae8cd73ce2709ee0f2d2319c5b45b0578 +size 130250 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09585b00528de1b86d859aafaf16dd8ea46898dd --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8017e5ab064f4c812dd76948d6bcdf39af8c8054313dae025532c3a5a66c5eb +size 64958 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f175585d9d3daa7a49211b3aa705c4fd5b999f38 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5908c22190d70ad14bc85b52543d7f72ae8720fbe066585cf1f790efd1fd938d +size 27465 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d44f6fe8bbdc7950c79ee2072382b2e95a1455f0 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d86288669d1a6dc24de301ef4b725d2a5495a22f0c5324e951fe0b351a79d27 +size 168585 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2442ff7d867c8382752ad211d2bfaa092fd5a6d9 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dba25b5585d22d199ef489c63fcf930d4b8eea49d0140ea4f765c1ffb59bed63 +size 5386 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f76934d242e762df7296434597ae7d1fb11790d --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9238378fa66118c792fa523eb2c7f3343cd929538ac260049a66531386e5529 +size 163830 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32b748510f9300c66a5280e7a4c953a04a533097 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6613a0ab6a07c33369f38cb3d682a5d4b61b2e05d04b56cceb8791ec858db68 +size 72307 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..396b7aa7a83e9f095883a31786caf0f23de8fc85 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b129a0768c79839358e0b3b7c6ca8bd6a8dc7c4527b667e3566eb262005bd907 +size 155740 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51fa796ce336c4007fec3e3c26eb6cab5353748e --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14ff75dc0f4c32bc213d9af817018c6fe343a781915b676258422316c6a36188 +size 156703 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/9ef93bf72a7d70a562ffad9ab5dd78e6_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/9ef93bf72a7d70a562ffad9ab5dd78e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..508d3f8afe26812bd878b14bf1943169b2e08a43 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/9ef93bf72a7d70a562ffad9ab5dd78e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4c944a999ea129420a5a25e548a168a3af19c3dbaf8ee525037898a51b21a00 +size 12365 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/a4759687eefd0f5e497321ae0c346992_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/a4759687eefd0f5e497321ae0c346992_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..768c409c94d2f3159a5c3e10f173c121bd576144 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/a4759687eefd0f5e497321ae0c346992_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c31f4a3d5ee919e8a83e747e176d1a81f3afe2507c725277838c5b4eb0036dc7 +size 4587 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d39a027fda829cd23838658ba187f76086731697 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:679ca6745a2ea2f90dc231640ebd42f112081a77360c1a3e5fa38448c7ecdc8d +size 17720 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/bfbb7c9ea51b575feb18a64b41d162c1_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/bfbb7c9ea51b575feb18a64b41d162c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cad2a6fa210da0b74d6f21c67a4fdcd8f1e0eeae --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/bfbb7c9ea51b575feb18a64b41d162c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86f76cf972165e98454aba72da0b1486a3b151f6fbdef7bd5dd2e14fbf46f187 +size 7919 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68e546cc2942377691935103df2560c3b1ee03c1 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a9e2ce9ec3cb7c628967ebda7026908e223a4893b9f0c1add61e04df21dced +size 69201 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c217a2cf65def6b0a38a1671885f42f7_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c217a2cf65def6b0a38a1671885f42f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20a78780915a0204226d272c12ff70ec2b1545af --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c217a2cf65def6b0a38a1671885f42f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6adcaf53cb932497b3ffcc2ba7aeb935ee39b63aba2a73c01ffc60cc4ce5615 +size 5660 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5cb85e226caae4b48aed13121bbd025cf10610c --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69fbc987098179b8110a941ed17b6fbeb01fc7476ba0d4f4e0b7c130c3520410 +size 52877 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c145c7ee71a9c3bd7040716f29a73e06454e2cd4 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:444450d39887b655a178eeb140a6c238c3fab7f9746aa7776b6fdff3fcfe9200 +size 95507 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4524b042b595078044619d61416c0e9542b4428 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a7f064e8b139a1dbb8ebf943fba569962b0fe35d65a7032d3ac0cc292e64603 +size 30127 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/daf05db9f13b34fb12da52f007bbfe5b_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/daf05db9f13b34fb12da52f007bbfe5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15bc32c62b2f28ae138371ca44852dfd10547200 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/daf05db9f13b34fb12da52f007bbfe5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b158209dfaa26e139ce0ffb53708c738666716ed439344cebcafbbbb51d5b6d +size 42229 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53612b016219d1d2a9aff1e54419e864ad106201 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56ed52a66fe4e3112394d6a7d846b24910be8f84f66bc7b08eb9a8c20bd3a837 +size 174245 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2dacc2f1bddf5a7e8708e2870b56bc940546bd6 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1fe68428127835b200fcd96b56b119d260c9075898700b38a2fd0306544c120 +size 96542 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f6ad590e9aaa1ed61ec404ab3e73c57506cd6e9 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2347fc97c8c294b76a38dc5a3537fab586555aef8e00de6a74e1b030d199525 +size 117430 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/eadd8abb2c85161842bcd823881cbe5f_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/eadd8abb2c85161842bcd823881cbe5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d7d6185013394e6c1df40fd9d272af72f36a14b --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/eadd8abb2c85161842bcd823881cbe5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cccc0e9dda9c0879aec4db0c41d60e3c0124c10feae2d210d1635c25f921045 +size 5157 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e39c6b9a0e304760e6038c5ad5c33d7ea742ea00 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a3296b3b82a7d780be9dd4576b90c6cf13b88c27173da1535c9ab28b187d8b5 +size 151685 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fe72c97cc22e4eadc145b0a00b3d391d8248962 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cde0c90d16de0f5ad908fdd238dda68f92a147d158868ef3d073ec0e1b8ce55 +size 85372 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03026ed81bfc3e6f5251c50321d947be8462e4f2 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:759bb4bb6dca4df7920b585628acc2f2a3da94dadee5771c7b8b2af4dc3238aa +size 137456 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fa0ec0e4c8dde599567b0f9080002a46_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fa0ec0e4c8dde599567b0f9080002a46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6c536405efe159141540121f5ecf813b310d6b7 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fa0ec0e4c8dde599567b0f9080002a46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39b177d24378b498fcac00dec0349a8d276324260ed5397036f68d0192578876 +size 6976 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fc1f700bee051e30a5cf6988a3791c5d_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fc1f700bee051e30a5cf6988a3791c5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..662b8041974de95318ac401dad9f80fd5f8875ab --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fc1f700bee051e30a5cf6988a3791c5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eebc10a0c0a5cbdfd058c09e5b439d7a7de040792df9f508d210bb3183444c4 +size 6449 diff --git a/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cb1d5ff38e9de98819125a7d1d6342aea94e892 --- /dev/null +++ b/marked/Q/T-REC-Q.2120-199502-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f986a0e7c41188bfa1d7903e990f7f602bbe7df8c0dd453314c9cf42baf37d30 +size 143453 diff --git a/marked/Q/T-REC-Q.2660-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2660-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..40c5af6dbd6573671d782f0dc429d4de6c6275ee --- /dev/null +++ b/marked/Q/T-REC-Q.2660-199912-I_PDF-E/raw.md @@ -0,0 +1,1261 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2660** + +(12/99) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Broadband ISDN – Common aspects of B-ISDN +application protocols for access signalling and network +signalling and interworking + +--- + +**Interworking between signalling system No. 7 +broadband ISDN user part (B-ISUP) and +narrow-band ISDN user part (N-ISUP)** + +ITU-T Recommendation Q.2660 + +(Previously CCITT Recommendation) + +--- + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| General aspects | Q.2000–Q.2099 | +| Signalling ATM adaptation layer (SAAL) | Q.2100–Q.2199 | +| Signalling network protocols | Q.2200–Q.2299 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 | +| B-ISDN application protocols for the network signalling | Q.2700–Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +# **INTERWORKING BETWEEN SIGNALLING SYSTEM No. 7 – BROADBAND ISDN USER PART (B-ISUP) AND NARROW-BAND ISDN USER PART (N-ISUP)** + +## **Summary** + +This Recommendation shows the mapping/interworking between B-ISUP and N-ISUP for the basic call and supplementary services. + +###### **Source** + +ITU-T Recommendation Q.2660 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 1999. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2000 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|---------------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Abbreviations..... | 4 | +| 4 | General statements on interworking ..... | 6 | +| 5 | Successful basic call ..... | 7 | +| 5.1 | Mapping of the Initial Address Message ..... | 7 | +| 5.1.1 | Mapping of the Initial Address Message when continuity check is applied
in the incoming narrow-band network..... | 7 | +| 5.2 | Mapping of the Subsequent Address Message ..... | 10 | +| 5.3 | Mapping of the Address Complete Message ..... | 10 | +| 5.4 | Mapping of the Forward Transfer Message..... | 12 | +| 5.5 | Mapping of the Call Progress Message..... | 12 | +| 5.6 | Mapping of the Answer and Connect Messages..... | 13 | +| 5.7 | Mapping of the Network Resource Management Message ..... | 14 | +| 5.8 | Mapping of the Release Message..... | 14 | +| 5.9 | Network initiated suspend ..... | 15 | +| 5.10 | Network initiated resume..... | 15 | +| 5.11 | Mapping of Confusion message..... | 15 | +| 5.12 | Mapping of Pre-Release information message ..... | 16 | +| 6 | Unsuccessful basic call ..... | 16 | +| 6.1 | Mapping of the Initial Address Reject Message ..... | 16 | +| 6.2 | Mapping of the Release Message..... | 16 | +| 7 | Supplementary services..... | 17 | +| 7.1 | Direct-Dialling-In (DDI)..... | 17 | +| 7.2 | Multiple Subscriber Number (MSN) ..... | 17 | +| 7.3 | Calling Line Identification Presentation (CLIP) ..... | 17 | +| 7.4 | Calling Line Identification Restriction (CLIR)..... | 17 | +| 7.5 | Connected Line Identification Presentation (COLP) ..... | 17 | +| 7.6 | Connected Line Identification Restriction (COLR)..... | 18 | +| 7.7 | Malicious Call Identification (MCID) ..... | 18 | +| 7.8 | Sub-addressing (SUB) ..... | 19 | +| 7.9 | Call Transfer (CT)..... | 19 | +| 7.10 | Call Forwarding Busy (CFB)..... | 19 | +| 7.11 | Call Forwarding No Reply (CFNR)..... | 21 | + +| | Page | +|---------------------------------------------------------|-------------| +| 7.12 Call Forwarding Unconditional (CFU)..... | 21 | +| 7.13 Call Deflection (CD)..... | 21 | +| 7.14 Line Hunting (LH) ..... | 21 | +| 7.15 Explicit Call Transfer (ECT) ..... | 21 | +| 7.16 Single Step Call Transfer (SCT)..... | 22 | +| 7.17 Call Waiting (CW)..... | 22 | +| 7.18 Call Hold (HOLD) ..... | 23 | +| 7.19 Completion of Calls to Busy Subscriber (CCBS)..... | 23 | +| 7.20 Terminal Portability (TP)..... | 23 | +| 7.20.1 Suspend..... | 23 | +| 7.20.2 Resume ..... | 24 | +| 7.21 Conference Calling (CONF) ..... | 24 | +| 7.22 Three-Party Service (3PTY) ..... | 24 | +| 7.23 Closed User Group (CUG)..... | 24 | +| 7.24 Private Numbering Plan (PNP)..... | 25 | +| 7.25 Multi-Level Precedence and Preemption (MLPP)..... | 25 | +| 7.26 International Telecommunication Charge Card ..... | 25 | +| 7.27 Advice of Charge (AOC)..... | 25 | +| 7.28 Reverse Charging (REV) ..... | 26 | +| 7.29 User-to-User Signalling (UUS)..... | 26 | +| 7.29.1 Service 1 ..... | 26 | +| 7.29.2 Service 2 ..... | 28 | +| 7.29.3 Service 3 ..... | 28 | +| 7.30 Global Virtual Network Service (GVNS)..... | 30 | +| 8 Application Transport Mechanism ..... | 30 | +| 8.1 Segmentation not required ..... | 31 | +| 8.2 Segmentation required ..... | 31 | + +## **INTERWORKING BETWEEN SIGNALLING SYSTEM No. 7 – BROADBAND ISDN USER PART (B-ISUP) AND NARROW-BAND ISDN USER PART (N-ISUP)** + +*(revised in 1999)* + +# **1 Scope** + +This Recommendation specifies the interworking between Broadband ISDN User Part as used in the Broadband network and the Narrow-band ISDN User Part as defined in the 1997 Recommendations [10]. + +Interworking of the basic call and supplementary services applicable to the international interface are included. + +Interworking is shown as arrow diagrams showing the message interworking, with tables being used to show the mapping of parameters. In some cases the message mapping is ambiguous. In those cases, the actual state of the involved ASEs has to be considered in addition to determining in which message the information is mapped. This is, however, outside the scope of this Recommendation. + +When repeated information elements are contained in B-ISUP parameters, on ascending order of priority is assumed. + +This Recommendation covers the following three interworking scenarios: + +- Broadband transit network; +- Narrow-band/broadband interworking; +- Broadband/narrow-band interworking. + +The interworking diagrams and tables show only the case of the broadband network being a transit network between two narrow-band networks. However, the information given is also relevant to the narrow-band/broadband and broadband/narrow-band interworking cases as indicated below. (See Figures 1 to 3.) + +![Diagram of a broadband transit network showing message flow between narrow-band and broadband networks.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +The diagram illustrates a broadband transit network scenario. It consists of three main sections separated by vertical lines representing network boundaries. On the left, a 'Narrow-band' network sends an 'IAM' (Initial Address Message) arrow towards the first boundary. Inside the central 'Broadband' network section, there are two horizontal arrows: an 'IAM' arrow pointing to the right towards the second boundary, and an 'IAA' (Initial Address Ack) arrow pointing to the left from the second boundary. On the right, another 'Narrow-band' network receives the 'IAM' arrow from the second boundary. A small code 'T1162170-94' is located at the bottom right of the diagram. + +Diagram of a broadband transit network showing message flow between narrow-band and broadband networks. + +**Figure 1/Q.2260 – Broadband transit network** + +![Diagram of Narrow-band/broadband interworking. A vertical line separates 'Narrow-band' on the left and 'Broadband' on the right. An arrow labeled 'IAM' points from the Narrow-band side to the Broadband side. A return arrow labeled 'IAA' points from the Broadband side back to the Narrow-band side. The text 'T1162180-94' is at the bottom right.](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +Diagram of Narrow-band/broadband interworking. A vertical line separates 'Narrow-band' on the left and 'Broadband' on the right. An arrow labeled 'IAM' points from the Narrow-band side to the Broadband side. A return arrow labeled 'IAA' points from the Broadband side back to the Narrow-band side. The text 'T1162180-94' is at the bottom right. + +**Figure 2/Q.2260 – Narrow-band/broadband interworking** + +![Diagram of Broadband/narrow-band interworking. A vertical line separates 'Broadband' on the left and 'Narrow-band' on the right. An arrow labeled 'IAM' points from the Broadband side to the Narrow-band side. A return arrow labeled 'IAA' points from the Narrow-band side back to the Broadband side. The text 'T1162190-94' is at the bottom right.](990567efebf979be51f56d1150012c9d_img.jpg) + +Diagram of Broadband/narrow-band interworking. A vertical line separates 'Broadband' on the left and 'Narrow-band' on the right. An arrow labeled 'IAM' points from the Broadband side to the Narrow-band side. A return arrow labeled 'IAA' points from the Narrow-band side back to the Broadband side. The text 'T1162190-94' is at the bottom right. + +**Figure 3/Q.2260 –Broadband/narrow-band interworking** + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation Q.2761 (1999), *Functional description of the B-ISDN user part (B-ISUP) of signalling system No. 7.* +- [2] ITU-T Recommendation Q.2762 (1999), *General functions of messages and signals of the B-ISDN user part (B-ISUP) of signalling system No. 7.* +- [3] ITU-T Recommendation Q.2763 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Formats and codes.* +- [4] ITU-T Recommendation Q.2764 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Basic call procedures.* +- [5] ITU-T Recommendation Q.2765 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Application transport mechanism (APM).* +- [6] ITU-T Recommendation Q.2730 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Supplementary services.* +- [7] ITU-T Recommendation Q.2735.1 (1997), *Stage 3 description for community of interest supplementary services for B-ISDN using SS No. 7: Closed user group (CUG).* +- [8] CCITT Recommendation E.172 (1992), *ISDN routing plan.* + +- [9] ITU-T Recommendation Q.2931 (1995), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control.* +- [10] ITU-T Recommendation Q.761 (1997), *Signalling system No. 7 – ISDN user part functional description.* +- [11] ITU-T Recommendation Q.762 (1997), *Signalling system No. 7 – ISDN user part general functions of messages and signals.* +- [12] ITU-T Recommendation Q.763 (1997), *Signalling system No. 7 – ISDN user part formats and codes.* +- [13] ITU-T Recommendation Q.764 (1997), *Signalling system No. 7 – ISDN user part signalling procedures.* +- [14] ITU-T Recommendation Q.765 (1998), *Signalling system No. 7 – Application transport mechanism.* +- [15] ITU-T Recommendation Q.730 (1997), *ISDN user part supplementary services.* +- [16] ITU-T Recommendation Q.731.1 (1996), *Stage 3 description for number identification supplementary services using signalling system No. 7: Direct-dialling-in (DDI).* +- [17] ITU-T Recommendation Q.731.3 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Calling line identification presentation (CLIP).* +- [18] ITU-T Recommendation Q.731.4 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Calling line identification restriction (CLIR).* +- [19] ITU-T Recommendation Q.731.5 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Connected line identification presentation (COLP).* +- [20] ITU-T Recommendation Q.731.6 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Connected line identification restriction (COLR).* +- [21] ITU-T Recommendation Q.731.7 (1997), *Stage 3 description for number identification supplementary services using signalling system No. 7: Malicious call identification (MCID).* +- [22] CCITT Recommendation Q.731.8 (1992), *Stage 3 description for number identification supplementary services using signalling system No. 7: Sub-addressing (SUB).* +- [23] ITU-T Recommendation Q.732.2 (1996), *Stage 3 description for call offering supplementary services using signalling system No. 7: Call diversion services: call forwarding busy, call forwarding no reply, call forwarding unconditional, call deflection.* +- [24] ITU-T Recommendation Q.732.7 (1996), *Stage 3 description for call offering supplementary services using signalling system No. 7: Explicit call transfer.* +- [25] CCITT Recommendation Q.733.1 (1992), *Stage 3 description for call completion supplementary services using signalling system No. 7: Call waiting (CW).* +- [26] ITU-T Recommendation Q.733.2 (1993), *Stage 3 description for call completion supplementary services using signalling system No. 7: Call hold (HOLD).* +- [27] ITU-T Recommendation Q.733.3 (1997), *Stage 3 description for call completion supplementary services using signalling system No. 7: Completion of calls to busy subscriber (CCBS).* + +- [28] ITU-T Recommendation Q.733.4 (1993), *Stage 3 description for call completion supplementary services using signalling system No. 7: Terminal portability (TP)*. +- [29] ITU-T Recommendation Q.734.1 (1993), *Stage 3 description for multiparty supplementary services using signalling system No. 7: Conference calling*. +- [30] ITU-T Recommendation Q.734.2 (1996), *Stage 3 description for multiparty supplementary services using signalling system No. 7: Three-party service*. +- [31] ITU-T Recommendation Q.735.1 (1993), *Stage 3 description for community of interest supplementary services using signalling system No. 7: Closed user group (CUG)*. +- [32] ITU-T Recommendation Q.735.3 (1993), *Stage 3 description for community of interest supplementary services using signalling system No. 7: Multi-level precedence and preemption*. +- [33] ITU-T Recommendation Q.735.6 (1996), *Stage 3 description for community of interest supplementary services using signalling system No. 7: Global virtual network service (GVNS)*. +- [34] ITU-T Recommendation Q.736.1 (1995), *Stage 3 description for charging supplementary services using signalling system No. 7: International telecommunication charge card (ITCC)*. +- [35] ITU-T Recommendation Q.736.3 (1995), *Stage 3 description for charging supplementary services using signalling system No. 7: Reverse charging (REV)*. +- [36] ITU-T Recommendation Q.737.1 (1997), *Stage 3 description for additional information transfer supplementary services using signalling system No. 7: User-to-user signalling (UUS)*. +- [37] ITU-T Recommendation Q.2931 Amendment 2 (1999), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control – Amendment 2*. + +## 3 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|------------------------------------------| +| 3PTY | Three-Party Service | +| ACM | Address Complete Message | +| ANM | ANswer Message | +| AOC | Advice of Charge | +| APM | Application Transport Message | +| ASE | Application Service Element | +| CCBS | Completion of Calls to Busy Subscriber | +| CD | Call Deflection | +| CFB | Call Forwarding Busy | +| CFN | Confusion Message | +| CFNR | Call Forwarding No Reply | +| CFU | Call Forwarding Unconditional | +| CLIP | Calling Line Identification Presentation | + +| | | +|------|--------------------------------------------| +| CLIR | Calling Line Identification Restriction | +| COLP | Connected Line Identification Presentation | +| COLR | Connected Line Identification Restriction | +| CON | CONnect Message | +| CONF | CONFerence Calling | +| COT | Continuity message | +| CPG | Call Progress message | +| CT | Call Transfer | +| CTM | Call Transfer Message | +| CUG | Closed User Group | +| CW | Call Waiting | +| DDI | Direct-Dialling-In | +| ECT | Explicit Call Transfer | +| FAA | Facility Accept Message | +| FAC | Facility Message | +| FAR | Facility Request Message | +| FRJ | Facility Reject Message | +| FOT | Forward Transfer Message | +| GVNS | Global Virtual Network Service | +| HOLD | Call HOLD | +| IAA | Initial Address Acknowledgement Message | +| IAM | Initial Address Message | +| IAR | Initial Address Reject Message | +| IDR | Identification Request Message | +| IRS | Identification Response Message | +| LH | Line Hunting | +| LOP | Loop Prevention Message | +| MCID | Malicious Call IDentification | +| MLPP | Multi-Level Precedence and Preemption | +| MSN | Multiple Subscriber Number | +| NRM | Network Resource Management Message | +| PNP | Private Numbering Plan | +| PRI | Pre-Release Information Message | +| REL | Release Message | +| RES | Resume Message | +| REV | Reverse Charging | + +| | | +|-----|----------------------------------| +| SAM | Subsequent Address Message | +| SCT | Single Step Call Transfer | +| SGM | Segmentation Message | +| SUB | Sub-addressing | +| SUS | Suspend Message | +| TP | Terminal Portability | +| UID | User Interactive Dialogue | +| USR | User-to-User Information Message | +| UUS | User-to-User Signalling | + +# 4 General statements on interworking + +- No ATM specific parameters defined for B-ISUP will be carried in the N-ISUP. +- All B-ISUP messages carry message compatibility information. +- All B-ISUP parameters carry parameter compatibility information. +- Forward and backward narrow-band interworking indicators carry narrow-band information unchanged through the broadband network. +- When a call transfers from the N-ISDN to the B-ISDN and the broadband/narrow interworking indicator is not received, then the broadband/narrow-band interworking indicator shall be set to "pass on" by the interworking exchange. +- The Generic Notification indicator of N-ISUP is always mapped transparently to the Notification indicator of B-ISUP. +- If a Generic number parameter cannot be mapped, because there is no parameter defined in B-ISUP for the received type of number, then the Generic number parameter is treated according to the settings of the instruction indicators. In particular, it is transported transparently through the broadband backbone, if the Broadband/narrow-band interworking indicator is set to "pass on". +- Segmentation is not supported on the international interface for B-ISUP, when the B-ISDN receives a message indicating that segmentation has occurred in the N-ISDN, the B-ISUP message is not generated until the second segment has arrived (or timer has expired) in N-ISUP. +- Through connection will be symmetrical and occur: + - 1) in the narrow-band outgoing exchange, immediately after the N-ISUP sends the Initial Address Message, or + - 2) in the broadband outgoing exchange, immediately upon reception of the Initial Address Acknowledgement Message in B-ISUP. + +# 5 Successful basic call + +## 5.1 Mapping of the Initial Address Message + +![Sequence diagram showing the mapping of the Initial Address Message (IAM) from a narrow-band network, through a broadband network, to another narrow-band network. The diagram shows IAM being sent from the first narrow-band network to the broadband network, IAM being forwarded from the broadband network to the second narrow-band network, and an IAA (Initial Address Ack) being sent from the broadband network back to the first narrow-band network. The reference T1162200-94 is shown at the bottom right.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +T1162200-94 + +Sequence diagram showing the mapping of the Initial Address Message (IAM) from a narrow-band network, through a broadband network, to another narrow-band network. The diagram shows IAM being sent from the first narrow-band network to the broadband network, IAM being forwarded from the broadband network to the second narrow-band network, and an IAA (Initial Address Ack) being sent from the broadband network back to the first narrow-band network. The reference T1162200-94 is shown at the bottom right. + +#### 5.1.1 Mapping of the Initial Address Message when continuity check is applied in the incoming narrow-band network + +![Sequence diagram showing the mapping of the Initial Address Message (IAM) and Continuity Check (COT) from an incoming narrow-band network, through a broadband network, to an outgoing narrow-band network. The diagram shows IAM and COT being sent from the incoming narrow-band network to the broadband network, IAM being forwarded from the broadband network to the outgoing narrow-band network, and an IAA (Initial Address Ack) being sent from the broadband network back to the incoming narrow-band network. The reference T1162210-94 is shown at the bottom right.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +T1162210-94 + +Sequence diagram showing the mapping of the Initial Address Message (IAM) and Continuity Check (COT) from an incoming narrow-band network, through a broadband network, to an outgoing narrow-band network. The diagram shows IAM and COT being sent from the incoming narrow-band network to the broadband network, IAM being forwarded from the broadband network to the outgoing narrow-band network, and an IAA (Initial Address Ack) being sent from the broadband network back to the incoming narrow-band network. The reference T1162210-94 is shown at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Nature of connection indicators: Satellite indicator | Not carried | Nature of connection indicators: Satellite indicator set to integer result of propagation delay counter divided by 270 ms | +| Nature of connection indicators: Continuity check indicator | Not carried. If continuity check requested, loop is applied at interworking exchange. IAM is not generated unless continuity check (or check on a previous link) is successful | Nature of connection indicators: Continuity check indicator will only indicate "continuity check not required" or "continuity check required on this circuit" | +| Nature of connection indicators: Echo control device indicator | Echo control information: Outgoing echo control device indicator (Note 2) | Nature of connection indicators: Echo control device indicator | +| Forward call indicators: National/international call indicator | National/international call indicator | Forward call indicators: National/international call indicator | + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forward call indicators:
End-to-end method indicator | Not carried | Forward call indicators:
End-to-end method indicator set to "no end-to-end method available" | +| Forward call indicators:
Interworking indicator | Forward narrow-band interworking indicators:
Interworking indicator | Forward call indicators:
Interworking indicator. If not received, then no interworking is indicated | +| Forward call indicators:
End-to-end information indicator | Not carried | Forward call indicators:
End-to-end information indicator set to "no end-to-end information available" | +| Forward call indicators:
ISDN user part indicator | Forward narrow-band interworking indicators:
ISDN user part indicator | Forward call indicators:
ISDN user part indicator. If not received, then ISDN user part used all the way is indicated | +| Forward call indicators:
ISDN user part preference indicator | Forward narrow-band interworking indicators:
ISDN user part preference indicator | Forward call indicators:
ISDN user part preference indicator. If not received, then it is generated according to Recommendation E.172 [8]. | +| Forward call indicators:
ISDN access indicator | Forward narrow-band interworking indicators:
ISDN access indicator | Forward call indicators:
ISDN access indicator. If not received, then ISDN access is indicated | +| Forward call indicators:
SCCP method indicator | Not carried | Forward call indicators:
SCCP method indicator set according to "no indication" | +| Calling party's category | Calling party's category | Calling party's category | +| Transmission medium requirement | Not carried. Narrow-band bearer capability derived from transmission medium requirement if user service information not available | Transmission medium requirement derived from narrow-band bearer capability first repetition or second repetition, if available. If no narrow-band bearer capability is received, the call/connection is released according to 6.4.1/Q.2931 [9] | +| Called party number | Called party number | Called party number | +| Optional forward call indicators:
Simple segmentation | Not carried | Optional forward call indicators:
Simple segmentation (if required) | +| Access transport | Narrow-band high layer compatibility (Note 1)
Narrow-band low layer compatibility (Note 1)
Progress indicator (Note 1) | Access transport | +| User service information | Narrow-band bearer capability (Note 1) | User service information | + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Propagation delay counter | Propagation delay counter (delays caused by the STM/ATM interworking function are added) | Propagation delay counter (delays caused by the ATM/STM interworking function are added) | +| User service information prime | Narrow-band bearer capability (Note 1) | User service information prime, generated from second repeated narrow-band bearer capability, if available | +| Origination ISC point code | Origination ISC point code | Origination ISC point code | +| User teleservice information | Not carried | User teleservice information. Generated from narrow-band high layer compatibility | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | +| Transmission medium requirement prime | Not carried | Transmission medium requirement prime derived from narrow-band bearer capability first repetition if second repetition available otherwise not generated | +| Location number | Location number | Location number | +| Not carried | AESA for called party number | Not carried | +| Call diversion treatment indicators | Call diversion treatment indicators | Call diversion treatment indicators | +| Called IN number | Called IN number | Called IN number | +| Call offering treatment indicators | Call offering treatment indicators | Call offering treatment indicators | +| Collect call request | Collect call request | Collect call request | +| Conference treatment indicators | Conference treatment indicators | Conference treatment indicators | +| Correlation ID | Correlation ID | Correlation ID | +| Echo control information | Echo control information | Echo control information | +| Not carried | Extended quality of service | Not carried | +| Hop counter | Hop counter | Hop counter | +| Network management controls | Network management controls | Network management controls | +| SCF ID | SCF ID | SCF ID | +| UID capability indicators | UID capability indicators | UID capability indicators | +| Not carried | ATM cell rate, generated with contents set according to DSS2 [9] to support 64 kbit/s circuit emulation | Not carried | +| Not carried | Broadband bearer capability, generated with contents set according to DSS2 [9] to support 64 kbit/s circuit emulation | Not carried | + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------|-----------------------------------------------------------------------------------------------------|-----------------------------| +| Not carried | Maximum end-to-end transit delay | Not carried | +| Not carried | AAL, generated with contents set according to DSS2 [9], [37] to support 64 kbit/s circuit emulation | Not carried | + +NOTE 1 – This parameter can contain repeated access information elements. +NOTE 2 – The echo control device indicator subfield is mapped to the Echo control information parameter only when no Echo control information parameter is received from the incoming narrow-band. + +## 5.2 Mapping of the Subsequent Address Message + +![Diagram showing the mapping of the Subsequent Address Message (SAM) from an incoming narrow-band to an outgoing narrow-band via a broadband transit. The SAM message is shown as a horizontal arrow passing through the broadband section.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +The diagram illustrates the flow of the Subsequent Address Message (SAM). It starts as an 'Incoming narrow-band' SAM, which enters a 'Broadband' transit section. Within the broadband section, the message is labeled 'SAM'. It then exits the broadband section as an 'Outgoing narrow-band' SAM. A reference code 'T1162220-94' is present at the bottom right of the diagram. + +Diagram showing the mapping of the Subsequent Address Message (SAM) from an incoming narrow-band to an outgoing narrow-band via a broadband transit. The SAM message is shown as a horizontal arrow passing through the broadband section. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------|--------------------------|-----------------------------| +| Subsequent number | Subsequent number | Subsequent number | + +## 5.3 Mapping of the Address Complete Message + +![Diagram showing the mapping of the Address Complete Message (ACM) from an outgoing narrow-band to an incoming narrow-band via a broadband transit. The ACM message is shown as a horizontal arrow passing through the broadband section in the reverse direction.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +The diagram illustrates the flow of the Address Complete Message (ACM). It starts as an 'Outgoing narrow-band' ACM, which enters a 'Broadband' transit section. Within the broadband section, the message is labeled 'ACM'. It then exits the broadband section as an 'Incoming narrow-band' ACM. A reference code 'T1162230-94' is present at the bottom right of the diagram. + +Diagram showing the mapping of the Address Complete Message (ACM) from an outgoing narrow-band to an incoming narrow-band via a broadband transit. The ACM message is shown as a horizontal arrow passing through the broadband section in the reverse direction. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------| +| Backward call indicators:
Charge indicator set to "charge" or "no charge" | Charge indicator | Backward call indicators:
Charge indicator | +| Backward call indicators:
Called party's status indicator (Note 1) | Called party's indicators:
Called party's status indicator (Note 1) | Backward call indicators:
Called party's status indicator (Note 1) | +| Backward call indicators:
Called party's category indicator | Called party's indicators:
Called party's category indicator | Backward call indicators:
Called party's category indicator | + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| Backward call indicators:
End-to-end method indicator set to "no end-to-end method available" | Not carried | Backward call indicators:
End-to-end method indicator | +| Backward call indicators:
Interworking indicator. If not received, then no interworking is indicated | Backward narrow-band interworking indicators:
Interworking indicator | Backward call indicators:
Interworking indicator | +| Backward call indicators:
End-to-end information indicator set to "no end-to-end information available" | Not carried | Backward call indicators:
End-to-end information indicator | +| Backward call indicators:
ISDN user part indicator. If not received, then ISDN user part used all the way is indicated | Backward narrow-band interworking indicators:
ISDN user part indicator | Backward call indicators:
ISDN user part indicator | +| Backward call indicators:
ISDN access indicator. If not received, then ISDN access is indicated | Backward narrow-band interworking indicators:
ISDN access indicator | Backward call indicators:
ISDN access indicator | +| Backward call indicators:
Echo control device indicator | Echo control information:
Incoming echo control device indicator (Note 3) | Backward call indicators:
Echo control device indicator | +| Backward call indicators:
SCCP method indicator set to "no indication" | Not carried | Backward call indicators:
SCCP method indicator | +| Optional backward call indicators:
In-band information indicator | In-band information indicator | Optional backward call indicators:
In-band information indicator | +| Cause indicators. Any broadband unique cause values are translated to "unspecified" value in that class | Cause indicators | Cause indicators | +| Access transport | Narrow-band bearer capability (Note 2)
Narrow-band high layer compatibility (Note 2)
Progress indicator (Note 2) | Access transport | +| Transmission medium used derived from narrow-band bearer capability if available | Narrow-band bearer capability generated if not available from access transport parameter | Transmission medium used | +| Echo control information | Echo control information | Echo control information | +| Access delivery information | Access delivery information | Access delivery information | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------| +| Conference treatment indicators | Conference treatment indicators | Conference treatment indicators | +| UID action indicators | UID action indicators | UID action indicators | +| NOTE 1 – Called party's status indicator value "alerting" in B-ISDN is mapped to value "subscriber free" in N-ISDN and vice versa.
NOTE 2 – This parameter can contain repeated access information elements.
NOTE 3 – The echo control device indicator subfield is mapped to the Echo control information parameter only when no Echo control information parameter is received from the outgoing narrow-band. | | | + +## 5.4 Mapping of the Forward Transfer Message + +![Diagram showing the mapping of the Forward Transfer (FOT) message across three network segments: Narrow-band, Broadband, and Narrow-band. Arrows indicate the flow of FOT messages from left to right across the segments. The label T1162240-94 is present at the bottom right.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +Diagram showing the mapping of the Forward Transfer (FOT) message across three network segments: Narrow-band, Broadband, and Narrow-band. Arrows indicate the flow of FOT messages from left to right across the segments. The label T1162240-94 is present at the bottom right. + +No parameters are carried by this message. + +### 5.5 Mapping of the Call Progress Message + +![Diagram showing the mapping of the Call Progress (CPG) message across three network segments: Narrow-band, Broadband, and Narrow-band. Arrows indicate the flow of CPG messages from right to left across the segments. The label T1162250-94 is present at the bottom right.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Diagram showing the mapping of the Call Progress (CPG) message across three network segments: Narrow-band, Broadband, and Narrow-band. Arrows indicate the flow of CPG messages from right to left across the segments. The label T1162250-94 is present at the bottom right. + +In addition to the mapping shown against the Address Complete Message, the following mapping is relevant. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| Event information:
Alerting | Called party's indicators:
Called party's status indicator
set to "alerting" | Event information:
Alerting | +| Event information:
Progress (Note 1) | Not carried | Event information:
Progress | +| Event information:
In-band information or an
appropriate pattern is now
available (Note 2) | In-band information indicator
set to "In-band information or
an appropriate pattern is now
available" | Event information:
In-band information or an
appropriate pattern is now
available | + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------| +| Call history information | Call history information | Call history information | +| NOTE 1 – The Event information "Progress" is generated, if neither "alerting" nor "In-band information or an appropriate pattern is now available" is received.
NOTE 2 – The In-band information indicator is mapped into the Event information only, when no "alerting" is received. Otherwise the In-band information indicator is mapped into the Optional backward call indicators parameter (see 5.3). | | | + +### 5.6 Mapping of the Answer and Connect Messages + +![Diagram showing the mapping of ANM or CON messages between narrow-band and broadband systems. A narrow-band system on the left sends an ANM or CON message to a broadband system in the center, which then forwards it to another narrow-band system on the right.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` + +graph LR + subgraph NB1 [Narrow-band] + direction TB + ANM_CON1[ANM or CON] + end + subgraph B [Broadband] + direction TB + ANM[ANM] + end + subgraph NB2 [Narrow-band] + direction TB + ANM_CON2[ANM or CON] + end + ANM_CON1 --> ANM + ANM --> ANM_CON2 + +``` + +T1162260-94 + +Diagram showing the mapping of ANM or CON messages between narrow-band and broadband systems. A narrow-band system on the left sends an ANM or CON message to a broadband system in the center, which then forwards it to another narrow-band system on the right. + +In addition to the mapping shown against the Address Complete Message (with exception of the Cause indicators parameter), the following mapping is relevant. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------| +| Backward call indicators:
Called party's status indicator (Note 1). If not received, then the Called party status indicator is set to "no indication" (Note 2) | Called party's indicators:
Called party's status indicator (Note 1) | Backward call indicators:
Called party status (Note 1) | +| Backward call indicators:
Called party's category indicator. If not received, then the Called party's category indicator is set to "no indication" (Note 2) | Called party's indicators:
Called party's category indicator | Backward call indicators:
Called party's category indicator | +| Call history information | Call history information | Call history information | +| Access transport | Narrow-band low layer compatibility (Note 3) | Access transport | +| Display information | Display information | Display information | +| NOTE 1 – Called party's status indicator value "alerting" in B-ISDN is mapped to value "subscriber free" in N-ISDN and vice versa.
NOTE 2 – The Called party's indicator was not carried in earlier versions of B-ISUP.
NOTE 3 – This parameter can contain repeated access information elements. | | | + +### 5.7 Mapping of the Network Resource Management Message + +![Diagram showing the mapping of Network Resource Management (NRM) messages between narrow-band and broadband networks. An incoming narrow-band NRM message is shown entering a broadband transit network, and an outgoing narrow-band NRM message is shown exiting it.](83852ec55d4802521a727926336bedab_img.jpg) + +The diagram illustrates the flow of Network Resource Management (NRM) messages. It consists of three vertical lines representing network boundaries. The leftmost section is labeled 'Narrow-band', the middle section is 'Broadband', and the rightmost section is 'Narrow-band'. An arrow labeled 'NRM' points from the left narrow-band section into the broadband section. Another arrow labeled 'NRM' points from the broadband section into the right narrow-band section. The reference code 'T1162270-94' is located in the bottom right corner. + +Diagram showing the mapping of Network Resource Management (NRM) messages between narrow-band and broadband networks. An incoming narrow-band NRM message is shown entering a broadband transit network, and an outgoing narrow-band NRM message is shown exiting it. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|--------------------------------------------------------------------------------|-------------------------------------| +| Message compatibility information | All B-ISUP messages include the message compatibility information parameter | Message compatibility information | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | +| Echo control information | Echo control information | Echo control information | + +## 5.8 Mapping of the Release Message + +![Diagram showing the mapping of Release (REL) messages between narrow-band and broadband networks. An incoming narrow-band REL message is shown entering a broadband transit network, and an outgoing narrow-band REL message is shown exiting it.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +The diagram illustrates the flow of Release (REL) messages. It consists of three vertical lines representing network boundaries. The leftmost section is labeled 'Narrow-band', the middle section is 'Broadband', and the rightmost section is 'Narrow-band'. An arrow labeled 'REL' points from the left narrow-band section into the broadband section. Another arrow labeled 'REL' points from the broadband section into the right narrow-band section. The reference code 'T1162280-94' is located in the bottom right corner. + +Diagram showing the mapping of Release (REL) messages between narrow-band and broadband networks. An incoming narrow-band REL message is shown entering a broadband transit network, and an outgoing narrow-band REL message is shown exiting it. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| Cause indicators | Cause indicators | Cause indicators. Any broadband unique cause values are translated to "unspecified" value in that class | +| Access transport | Progress indicator | Access transport | +| Access delivery information | Access delivery information | Access delivery information | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | +| Display information | Display information | Display information | + +### 5.9 Network initiated suspend + +![Sequence diagram for Network initiated suspend. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. Arrows labeled 'SUS' are shown entering from the left, being transmitted across the Broadband section, and exiting to the right. The diagram is labeled T1162290-94.](812e188283162af0b54fb3e30ffee51b_img.jpg) + +T1162290-94 + +Sequence diagram for Network initiated suspend. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. Arrows labeled 'SUS' are shown entering from the left, being transmitted across the Broadband section, and exiting to the right. The diagram is labeled T1162290-94. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------------------|-------------------------------------------------|-------------------------------------------------| +| Suspend/resume indicators:
Network initiated | Suspend/resume indicators:
Network initiated | Suspend/resume indicators:
Network initiated | + +## 5.10 Network initiated resume + +![Sequence diagram for Network initiated resume. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. Arrows labeled 'RES' are shown entering from the left, being transmitted across the Broadband section, and exiting to the right. The diagram is labeled T1162300-94.](a3472689858b068ef469213682965325_img.jpg) + +T1162300-94 + +Sequence diagram for Network initiated resume. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. Arrows labeled 'RES' are shown entering from the left, being transmitted across the Broadband section, and exiting to the right. The diagram is labeled T1162300-94. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------------------|-------------------------------------------------|-------------------------------------------------| +| Suspend/resume indicators:
Network initiated | Suspend/resume indicators:
Network initiated | Suspend/resume indicators:
Network initiated | + +## 5.11 Mapping of Confusion message + +![Sequence diagram for Mapping of Confusion message. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. Arrows labeled 'CFN' are shown entering from the left, being transmitted across the Broadband section, and exiting to the right. The diagram is labeled T11104850-99.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +T11104850-99 + +Sequence diagram for Mapping of Confusion message. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. Arrows labeled 'CFN' are shown entering from the left, being transmitted across the Broadband section, and exiting to the right. The diagram is labeled T11104850-99. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| Cause indicators | Cause indicators | Cause indicators | + +## 5.12 Mapping of Pre-Release information message + +![Diagram showing the mapping of PRI messages across narrow-band and broadband segments. A narrow-band PRI message enters a broadband segment and is carried as a PRI message, then exits as a narrow-band PRI message. Reference T11104930-99.](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg) + +The diagram illustrates the flow of a Pre-Release Information (PRI) message. It starts as a 'Narrow-band PRI' message on the left, entering a 'Broadband' segment in the middle. Inside the broadband segment, it is labeled 'PRI'. It then exits the broadband segment on the right as a 'Narrow-band PRI' message. The reference code T11104930-99 is shown at the bottom right. + +Diagram showing the mapping of PRI messages across narrow-band and broadband segments. A narrow-band PRI message enters a broadband segment and is carried as a PRI message, then exits as a narrow-band PRI message. Reference T11104930-99. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| Optional forward call indicators or Optional backward call indicators (Notes 1 and 2) | Not carried | Optional forward call indicators or Optional backward call indicators (Notes 1 and 2) | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | + +NOTE 1 – This parameter is only present to allow the message to be segmented using ISUP simple segmentation procedure. +NOTE 2 – The Optional forward call indicators parameter is used, when the message is sent in forward direction. The Optional backward call indicators parameter is used, when the message is sent in backward direction. They should be mutually exclusive. + +## 6 Unsuccessful basic call + +## 6.1 Mapping of the Initial Address Reject Message + +![Diagram showing the mapping of Initial Address Reject (IAR) and Release (REL) messages. An IAM message enters a broadband segment, and an IAR message is returned from the broadband segment to a narrow-band segment, which then becomes a REL message. Reference T1162310-94.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +The diagram shows the interaction for an unsuccessful call. An Initial Address Message (IAM) is sent from a 'Narrow-band' source into a 'Broadband' segment. From the 'Broadband' segment, an Initial Address Reject (IAR) message is sent back to the 'Narrow-band' destination. This IAR message is then mapped to a Release (REL) message on the narrow-band side. The reference code T1162310-94 is shown at the bottom right. + +Diagram showing the mapping of Initial Address Reject (IAR) and Release (REL) messages. An IAM message enters a broadband segment, and an IAR message is returned from the broadband segment to a narrow-band segment, which then becomes a REL message. Reference T1162310-94. + +| Narrow-band, REL message | Broadband, IAR message | +|---------------------------------------------------------------------------------------------------------|------------------------| +| Cause indicators. Any broadband unique cause values are translated to "unspecified" value in that class | Cause indicators | + +## 6.2 Mapping of the Release Message + +Refer to 5.8. + +# 7 Supplementary services + +The tables in this clause show only the mapping of information relevant to the supplementary services, in addition to the mapping of information relevant to the basic call. + +## 7.1 Direct-Dialling-In (DDI) + +Implicitly supported as part of the basic call procedure. + +## 7.2 Multiple Subscriber Number (MSN) + +Implicitly supported as part of the basic call procedure. + +## 7.3 Calling Line Identification Presentation (CLIP) + +![Diagram showing the mapping of IAM and IAA messages between narrow-band and broadband networks for CLIP. An incoming narrow-band IAM message is mapped to a broadband IAM message. A broadband IAA message is mapped to an outgoing narrow-band IAM message. Reference T11104940-99.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +The diagram illustrates the message mapping for CLIP across network boundaries. On the left, a 'Narrow-band' network sends an 'IAM' (Initial Address Message) towards a central 'Broadband' network. Inside the 'Broadband' network, the 'IAM' is passed through, and an 'IAA' (Information About Calling) message is added. On the right, the 'Broadband' network maps the 'IAA' information into an 'IAM' message for the outgoing 'Narrow-band' network. The reference code T11104940-99 is shown at the bottom right. + +Diagram showing the mapping of IAM and IAA messages between narrow-band and broadband networks for CLIP. An incoming narrow-band IAM message is mapped to a broadband IAM message. A broadband IAA message is mapped to an outgoing narrow-band IAM message. Reference T11104940-99. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-----------------------------------|----------------------| +| Calling party number | Calling party number | Calling party number | +| Access transport | Calling party sub-address | Access transport | +| Generic number | Additional calling party number | Generic number | +| Not carried | AESA for additional calling party | Not carried | +| Not carried | AESA for calling party | Not carried | + +## 7.4 Calling Line Identification Restriction (CLIR) + +Refer to 7.3. + +## 7.5 Connected Line Identification Presentation (COLP) + +![Diagram showing the mapping of IAM and IAA messages between narrow-band and broadband networks for COLP. An incoming narrow-band IAM message is mapped to a broadband IAM message. A broadband IAA message is mapped to an outgoing narrow-band IAM message. Reference T1162330-94.](2119293733c74fc64de88aefd597f4bb_img.jpg) + +The diagram illustrates the message mapping for COLP across network boundaries. On the left, a 'Narrow-band' network sends an 'IAM' message towards a central 'Broadband' network. Inside the 'Broadband' network, the 'IAM' is passed through, and an 'IAA' message is added. On the right, the 'Broadband' network maps the 'IAA' information into an 'IAM' message for the outgoing 'Narrow-band' network. The reference code T1162330-94 is shown at the bottom right. + +Diagram showing the mapping of IAM and IAA messages between narrow-band and broadband networks for COLP. An incoming narrow-band IAM message is mapped to a broadband IAM message. A broadband IAA message is mapped to an outgoing narrow-band IAM message. Reference T1162330-94. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------| +| Optional forward call indicators:
Connected line identity request indicator | Connected line identity request indicator | Optional forward call indicators:
Connected line identity request indicator | + +![Diagram showing signaling flow for Connected Line Identity Request (CLIR) across narrow-band and broadband interfaces. On the left (Narrow-band), an arrow labeled 'CON or ANM, CPG' points left. In the center (Broadband), an arrow labeled 'ANM, CPG' points left. On the right (Narrow-band), an arrow labeled 'CON or ANM, CPG' points left towards the broadband interface. A vertical line separates the narrow-band and broadband sections. Reference T1162340-94 is shown at the bottom right.](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +Diagram showing signaling flow for Connected Line Identity Request (CLIR) across narrow-band and broadband interfaces. On the left (Narrow-band), an arrow labeled 'CON or ANM, CPG' points left. In the center (Broadband), an arrow labeled 'ANM, CPG' points left. On the right (Narrow-band), an arrow labeled 'CON or ANM, CPG' points left towards the broadband interface. A vertical line separates the narrow-band and broadband sections. Reference T1162340-94 is shown at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------------------------|----------------------| +| Connected number | Connected number | Connected number | +| Access transport | Connected sub-address | Access transport | +| Generic number | Additional connected number | Generic number | +| Not carried | AESA for additional connected party | Not carried | +| Not carried | AESA for connected number | Not carried | + +## 7.6 Connected Line Identification Restriction (COLR) + +Refer to 7.5. + +### 7.7 Malicious Call Identification (MCID) + +![Diagram showing signaling flow for Malicious Call Identification (MCID) across narrow-band and broadband interfaces. On the left (Narrow-band), an arrow labeled 'IDR' points left. In the center (Broadband), an arrow labeled 'IDR' points left. On the right (Narrow-band), an arrow labeled 'IDR' points left towards the broadband interface. A vertical line separates the narrow-band and broadband sections. Reference T11104950-99 is shown at the bottom right.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +Diagram showing signaling flow for Malicious Call Identification (MCID) across narrow-band and broadband interfaces. On the left (Narrow-band), an arrow labeled 'IDR' points left. In the center (Broadband), an arrow labeled 'IDR' points left. On the right (Narrow-band), an arrow labeled 'IDR' points left towards the broadband interface. A vertical line separates the narrow-band and broadband sections. Reference T11104950-99 is shown at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|--------------------------------------------------------------------------------|-------------------------------------| +| MCID request indicators | MCID request indicators | MCID request indicators | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | + +![Sequence diagram for IRS message flow. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. An IRS message is shown entering from the left Narrow-band, passing through the Broadband interface, and exiting through the right Narrow-band interface. The message is labeled 'IRS' at each stage. A reference code 'T11104960-99' is at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Sequence diagram for IRS message flow. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. An IRS message is shown entering from the left Narrow-band, passing through the Broadband interface, and exiting through the right Narrow-band interface. The message is labeled 'IRS' at each stage. A reference code 'T11104960-99' is at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|--------------------------------------------------------------------------------|-------------------------------------| +| MCID response indicators | MCID response indicators | MCID response indicators | +| Calling party number | Calling party number | Calling party number | +| Access transport | Calling party sub-address | Access transport | +| Generic number | Additional calling party number | Generic number | +| Charged party identification | Charged party identification | Charged party identification | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | + +### 7.8 Sub-addressing (SUB) + +![Sequence diagram for Sub-addressing (SUB) message flow. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. An IAM message is shown entering from the left Narrow-band, passing through the Broadband interface, and exiting through the right Narrow-band interface. A return message IAA is shown from the Broadband interface back to the Narrow-band interface. The messages are labeled 'IAM' and 'IAA'. A reference code 'T1162350-94' is at the bottom right.](26d664119ad25250780f554633444e54_img.jpg) + +Sequence diagram for Sub-addressing (SUB) message flow. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. An IAM message is shown entering from the left Narrow-band, passing through the Broadband interface, and exiting through the right Narrow-band interface. A return message IAA is shown from the Broadband interface back to the Narrow-band interface. The messages are labeled 'IAM' and 'IAA'. A reference code 'T1162350-94' is at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|--------------------------|----------------------| +| Access transport | Called party sub-address | Access transport | + +### 7.9 Call Transfer (CT) + +Not defined in ISU'P97. + +### 7.10 Call Forwarding Busy (CFB) + +![Sequence diagram for Call Forwarding Busy (CFB) message flow. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. An ACM message is shown entering from the right Narrow-band, passing through the Broadband interface, and exiting through the left Narrow-band interface. The message is labeled 'ACM' at each stage. A reference code 'T1162360-94' is at the bottom right.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +Sequence diagram for Call Forwarding Busy (CFB) message flow. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band interfaces. An ACM message is shown entering from the right Narrow-band, passing through the Broadband interface, and exiting through the left Narrow-band interface. The message is labeled 'ACM' at each stage. A reference code 'T1162360-94' is at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------| +| Optional backward call indicators:
Call diversion may occur indicator | Call diversion may occur | Optional backward call indicators:
Call diversion may occur | +| Generic notification | Notification | Generic notification | +| Redirection number | Redirection number | Redirection number | +| Redirection number restriction | Redirection number restriction | Redirection number restriction | +| Call diversion information | Call diversion information | Call diversion information | + +![Diagram showing the mapping of CPG messages between narrow-band and broadband networks. A narrow-band network on the left sends a CPG message to a broadband network in the center, which then forwards it to another narrow-band network on the right. The message is labeled 'CPG' in each segment.](0c08e48c08f96934cd6bc6911f3069dc_img.jpg) + +T1162370-94 + +Diagram showing the mapping of CPG messages between narrow-band and broadband networks. A narrow-band network on the left sends a CPG message to a broadband network in the center, which then forwards it to another narrow-band network on the right. The message is labeled 'CPG' in each segment. + +In addition to the mapping shown against the Address Complete Message, the following mapping is relevant. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------------|---------------------------------------------------------------------------------|--------------------------------| +| Event information:
Alerting | Called party's indicators:
Called party's status indicator set to "alerting" | Event information:
Alerting | +| Event information:
Progress | Not carried | Event information:
Progress | +| Access transport | Progress indicator | Access transport | + +![Diagram showing the mapping of CON or ANM messages between narrow-band and broadband networks. A narrow-band network on the left sends a CON or ANM message to a broadband network in the center, which then forwards it to another narrow-band network on the right. The message is labeled 'ANM' in the broadband segment and 'CON or ANM' in the narrow-band segments.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +T1162380-94 + +Diagram showing the mapping of CON or ANM messages between narrow-band and broadband networks. A narrow-band network on the left sends a CON or ANM message to a broadband network in the center, which then forwards it to another narrow-band network on the right. The message is labeled 'ANM' in the broadband segment and 'CON or ANM' in the narrow-band segments. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------------|--------------------------------|--------------------------------| +| Redirection number (Note) | Redirection number | Redirection number (Note) | +| Redirection number restriction | Redirection number restriction | Redirection number restriction | +| NOTE – Only ANM. | | | + +![Sequence diagram for ISUP call handling. It shows three segments: 'Narrow-band', 'Broadband', and 'Narrow-band'. In the first narrow-band segment, an 'IAM' message is sent. Upon entering the broadband segment, the 'IAM' message is passed through, and an 'IAA' message is sent back. Upon exiting the broadband segment into the second narrow-band segment, the 'IAM' message is sent again.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +Sequence diagram for ISUP call handling. It shows three segments: 'Narrow-band', 'Broadband', and 'Narrow-band'. In the first narrow-band segment, an 'IAM' message is sent. Upon entering the broadband segment, the 'IAM' message is passed through, and an 'IAA' message is sent back. Upon exiting the broadband segment into the second narrow-band segment, the 'IAM' message is sent again. + +T1162390-94 + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------|-------------------------|-------------------------| +| Redirecting number | Redirecting number | Redirecting number | +| Redirection information | Redirection information | Redirection information | +| Original called number | Original called number | Original called number | + +### 7.11 Call Forwarding No Reply (CFNR) + +Refer to 7.10. + +### 7.12 Call Forwarding Unconditional (CFU) + +Refer to 7.10. + +### 7.13 Call Deflection (CD) + +Refer to 7.10. + +### 7.14 Line Hunting (LH) + +Not supported in ISUP'97. + +### 7.15 Explicit Call Transfer (ECT) + +![Sequence diagram for ECT call handling. It shows three segments: 'Narrow-band', 'Broadband', and 'Narrow-band'. In the first narrow-band segment, a 'CPG' message is sent. Upon entering the broadband segment, the 'CPG' message is passed through. Upon exiting the broadband segment into the second narrow-band segment, the 'CPG' message is sent again.](6929132b4964d52244da61d4614bc4d6_img.jpg) + +Sequence diagram for ECT call handling. It shows three segments: 'Narrow-band', 'Broadband', and 'Narrow-band'. In the first narrow-band segment, a 'CPG' message is sent. Upon entering the broadband segment, the 'CPG' message is passed through. Upon exiting the broadband segment into the second narrow-band segment, the 'CPG' message is sent again. + +T11104970-99 + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|----------------------|-------------------------------------| +| Event information set to "progress" | Not carried | Event information set to "progress" | +| Generic notification | Notification | Generic notification | +| Call transfer number | Call transfer number | Call transfer number | + +![Diagram showing FAC message flow from Narrow-band to Broadband and then to Narrow-band. The message is labeled FAC in the first narrow-band section, CTM in the broadband section, and FAC again in the second narrow-band section. Reference T11104980-99 is shown at the bottom right.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +Diagram showing FAC message flow from Narrow-band to Broadband and then to Narrow-band. The message is labeled FAC in the first narrow-band section, CTM in the broadband section, and FAC again in the second narrow-band section. Reference T11104980-99 is shown at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------| +| Call transfer number | Call transfer number | Call transfer number | +| Access transport | Calling party sub-address | Access transport | +| Generic notification | Notification | Generic notification | +| Service activation parameter: Call transfer | Not carried | Service activation parameter: call transfer | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | + +![Diagram showing LOP message flow from Narrow-band to Broadband and then to Narrow-band. The message is labeled LOP in the first narrow-band section, LOP in the broadband section, and LOP again in the second narrow-band section. Reference T11104990-99 is shown at the bottom right.](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +Diagram showing LOP message flow from Narrow-band to Broadband and then to Narrow-band. The message is labeled LOP in the first narrow-band section, LOP in the broadband section, and LOP again in the second narrow-band section. Reference T11104990-99 is shown at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|--------------------------------------------------------------------------------|-------------------------------------| +| Loop prevention indicators | Loop prevention indicators | Loop prevention indicators | +| Call transfer reference | Call transfer reference | Call transfer reference | +| Parameter compatibility information | All B-ISUP parameters include this information as part of the parameter header | Parameter compatibility information | + +### 7.16 Single Step Call Transfer (SCT) + +Not supported in ISUP'97. + +### 7.17 Call Waiting (CW) + +![Diagram showing ACM message flow from Narrow-band to Broadband and then to Narrow-band. The message is labeled ACM in the first narrow-band section, ACM in the broadband section, and ACM again in the second narrow-band section. Reference T1166180-94 is shown at the bottom right.](805c475f0859e607af0530ba43194bf1_img.jpg) + +Diagram showing ACM message flow from Narrow-band to Broadband and then to Narrow-band. The message is labeled ACM in the first narrow-band section, ACM in the broadband section, and ACM again in the second narrow-band section. Reference T1166180-94 is shown at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| Generic notification | Notification | Generic notification | + +![Sequence diagram for Generic notification. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows labeled 'CPG' are shown: one pointing left in the Narrow-band domain, one pointing left from Broadband to the first Narrow-band domain, and one pointing left from the second Narrow-band domain to the Broadband domain. The text 'T1162400-94' is in the bottom right.](2bacc162a73d75c43a7f90715832bd13_img.jpg) + +Sequence diagram for Generic notification. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows labeled 'CPG' are shown: one pointing left in the Narrow-band domain, one pointing left from Broadband to the first Narrow-band domain, and one pointing left from the second Narrow-band domain to the Broadband domain. The text 'T1162400-94' is in the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------------------|-------------------|-------------------------------------| +| Event information set to "progress" | Not carried | Event information set to "progress" | +| Generic notification | Notification | Generic notification | + +### **7.18 Call Hold (HOLD)** + +Refer to 7.17. + +### **7.19 Completion of Calls to Busy Subscriber (CCBS)** + +![Sequence diagram for CCBS. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows labeled 'IAM' are shown: one pointing right from the first Narrow-band to Broadband, one pointing right from Broadband to the second Narrow-band, and one pointing right from the second Narrow-band. The text 'T11105000-99' is in the bottom right.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +Sequence diagram for CCBS. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows labeled 'IAM' are shown: one pointing right from the first Narrow-band to Broadband, one pointing right from Broadband to the second Narrow-band, and one pointing right from the second Narrow-band. The text 'T11105000-99' is in the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| CCSS | CCSS | CCSS | + +### **7.20 Terminal Portability (TP)** + +#### **7.20.1 Suspend** + +![Sequence diagram for Suspend. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows labeled 'SUS' are shown: one pointing left from the first Narrow-band, one pointing left from Broadband to the first Narrow-band, and one pointing left from the second Narrow-band to the Broadband domain. The text 'T1162410-94' is in the bottom right.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +Sequence diagram for Suspend. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows labeled 'SUS' are shown: one pointing left from the first Narrow-band, one pointing left from Broadband to the first Narrow-band, and one pointing left from the second Narrow-band to the Broadband domain. The text 'T1162410-94' is in the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------| +| Suspend/resume indicators:
ISDN subscriber initiated | Suspend/resume indicators:
ISDN subscriber initiated | Suspend/resume indicators:
ISDN subscriber initiated | + +#### 7.20.2 Resume + +![Sequence diagram for Resume (7.20.2) showing RES messages across Narrow-band, Broadband, and Narrow-band segments.](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +Sequence diagram illustrating the Resume (7.20.2) procedure across three network segments: Narrow-band, Broadband, and Narrow-band. The sequence of messages is as follows: + +- A RES message is sent from the rightmost Narrow-band segment into the Broadband segment. +- The RES message is then forwarded from the Broadband segment into the leftmost Narrow-band segment. + +T1162420-94 + +Sequence diagram for Resume (7.20.2) showing RES messages across Narrow-band, Broadband, and Narrow-band segments. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------| +| Suspend/resume indicators:
ISDN subscriber initiated | Suspend/resume indicators:
ISDN subscriber initiated | Suspend/resume indicators:
ISDN subscriber initiated | + +### 7.21 Conference Calling (CONF) + +![Sequence diagram for Conference Calling (CONF) showing CPG messages across Narrow-band, Broadband, and Narrow-band segments.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +Sequence diagram illustrating the Conference Calling (CONF) procedure across three network segments: Narrow-band, Broadband, and Narrow-band. The sequence of messages is as follows: + +- A CPG message is sent from the rightmost Narrow-band segment into the Broadband segment. +- The CPG message is then forwarded from the Broadband segment into the leftmost Narrow-band segment. + +T1162430-94 + +Sequence diagram for Conference Calling (CONF) showing CPG messages across Narrow-band, Broadband, and Narrow-band segments. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------------------------|-------------------|----------------------------------------| +| Event information set to
"progress" | Not carried | Event information set to
"progress" | +| Generic notification | Notification | Generic notification | + +### 7.22 Three-Party Service (3PTY) + +Refer to 7.21. + +### 7.23 Closed User Group (CUG) + +![Sequence diagram for Closed User Group (CUG) showing IAM, IAA, and IAM messages across Narrow-band, Broadband, and Narrow-band segments.](17a1ba23b641c01871b08f0a4f08ef48_img.jpg) + +Sequence diagram illustrating the Closed User Group (CUG) procedure across three network segments: Narrow-band, Broadband, and Narrow-band. The sequence of messages is as follows: + +- An IAM message is sent from the leftmost Narrow-band segment into the Broadband segment. +- The IAM message is forwarded from the Broadband segment into the rightmost Narrow-band segment. +- An IAA message is sent from the rightmost Narrow-band segment back into the Broadband segment. +- Finally, an IAM message is sent from the Broadband segment into the leftmost Narrow-band segment. + +T1162440-94 + +Sequence diagram for Closed User Group (CUG) showing IAM, IAA, and IAM messages across Narrow-band, Broadband, and Narrow-band segments. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------| +| Optional forward call indicators:
Closed user group call indicator | Closed user group information:
Closed user group call indicator | Optional forward call indicators:
Closed user group call indicator | +| Closed user group interlock code | Closed user group information:
Closed user group interlock code | Closed user group interlock code | + +### **7.24 Private Numbering Plan (PNP)** + +Not defined in ISUP'97. + +### **7.25 Multi-Level Precedence and Preemption (MLPP)** + +![Sequence diagram for MLPP call setup. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band segments. Arrows show the flow of IAM (Initial Address Message) and IAA (Information Acknowledge) messages between these segments. The first IAM is from the left Narrow-band to the Broadband. The second IAM is from the Broadband to the right Narrow-band. The IAA message is sent from the right Narrow-band back to the Broadband, and then from the Broadband back to the left Narrow-band. A label 'T1162450-94' is at the bottom right.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +Sequence diagram for MLPP call setup. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band segments. Arrows show the flow of IAM (Initial Address Message) and IAA (Information Acknowledge) messages between these segments. The first IAM is from the left Narrow-band to the Broadband. The second IAM is from the Broadband to the right Narrow-band. The IAA message is sent from the right Narrow-band back to the Broadband, and then from the Broadband back to the left Narrow-band. A label 'T1162450-94' is at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| MLPP precedence | MLPP precedence | MLPP precedence | + +![Sequence diagram for MLPP call release. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band segments. Arrows show the flow of ACM (Address Complete Message) messages. The first ACM is from the right Narrow-band to the Broadband. The second ACM is from the Broadband to the left Narrow-band. A label 'T1162460-94' is at the bottom right.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +Sequence diagram for MLPP call release. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band segments. Arrows show the flow of ACM (Address Complete Message) messages. The first ACM is from the right Narrow-band to the Broadband. The second ACM is from the Broadband to the left Narrow-band. A label 'T1162460-94' is at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------------------------------------|-----------------------|-----------------------------------------------------------| +| Optional backward call indicators:
MLPP user indicator | MLPP user information | Optional backward call indicators:
MLPP user indicator | +| Generic notification | Notification | Generic notification | + +### **7.26 International Telecommunication Charge Card** + +No impact on B-ISUP. + +### **7.27 Advice of Charge (AOC)** + +Not defined in ISUP'97. + +### 7.28 Reverse Charging (REV) + +![Sequence diagram for Reverse Charging (REV) showing signal flow from Narrow-band to Broadband to Narrow-band. Arrows indicate the direction of messages, with '(Note)' labels above each segment. Reference T11105010-99 is shown at the bottom right.](d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg) + +T11105010-99 + +Sequence diagram for Reverse Charging (REV) showing signal flow from Narrow-band to Broadband to Narrow-band. Arrows indicate the direction of messages, with '(Note)' labels above each segment. Reference T11105010-99 is shown at the bottom right. + +NOTE – Messages possible are: + +- IAM; +- ANM; +- CON (applicable only to narrow-band); +- CPG; +- REL; +- FAC. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| Remote operations | Remote operations | Remote operations | + +### 7.29 User-to-User Signalling (UUS) + +#### 7.29.1 Service 1 + +##### 7.29.1.1 Implicit request, network discard of user-to-user information + +![Sequence diagram for User-to-User Signalling (UUS) showing signal flow from Narrow-band to Broadband to Narrow-band. Arrows indicate the direction of messages, with '(Note)' labels above each segment. Reference T1162470-94 is shown at the bottom right.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +T1162470-94 + +Sequence diagram for User-to-User Signalling (UUS) showing signal flow from Narrow-band to Broadband to Narrow-band. Arrows indicate the direction of messages, with '(Note)' labels above each segment. Reference T1162470-94 is shown at the bottom right. + +NOTE – Messages possible are: + +- ACM; +- REL; +- ANM (applicable only to broadband); +- CON (applicable only to narrow-band). + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------|-------------------------|-------------------------| +| User-to-user indicators | User-to-user indicators | User-to-user indicators | + +##### 7.29.1.2 Explicit request + +![Sequence diagram for explicit request showing IAM, IAA, and IAM messages across narrow-band and broadband segments.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +Sequence diagram illustrating the explicit request process across three segments: Narrow-band, Broadband, and Narrow-band. The sequence of messages is as follows: + +- An **IAM** message is sent from the left Narrow-band segment into the Broadband segment. +- Inside the Broadband segment, an **IAA** message is sent from right to left. +- Finally, an **IAM** message is sent from the Broadband segment into the right Narrow-band segment. + +T1162480-94 + +Sequence diagram for explicit request showing IAM, IAA, and IAM messages across narrow-band and broadband segments. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------|-------------------------|-------------------------| +| User-to-user indicators | User-to-user indicators | User-to-user indicators | + +![Sequence diagram for explicit request showing ACM or CON, ACM or ANM, and ACM or CON messages across narrow-band and broadband segments.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Sequence diagram illustrating the explicit request process across three segments: Narrow-band, Broadband, and Narrow-band. The sequence of messages is as follows: + +- An **ACM or CON** message is sent from the right Narrow-band segment into the Broadband segment. +- Inside the Broadband segment, an **ACM or ANM** message is sent from right to left. +- Finally, an **ACM or CON** message is sent from the Broadband segment into the left Narrow-band segment. + +T1162490-94 + +Sequence diagram for explicit request showing ACM or CON, ACM or ANM, and ACM or CON messages across narrow-band and broadband segments. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-------------------------|-------------------------|-------------------------| +| User-to-user indicators | User-to-user indicators | User-to-user indicators | + +##### 7.29.1.3 Passing of user-to-user signalling information + +![Sequence diagram for passing of user-to-user signalling information showing (Note) messages across narrow-band and broadband segments.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +Sequence diagram illustrating the passing of user-to-user signalling information across three segments: Narrow-band, Broadband, and Narrow-band. The sequence of messages is as follows: + +- A **(Note)** message is sent from the left Narrow-band segment into the Broadband segment. +- Inside the Broadband segment, a **(Note)** message is sent from left to right. +- Finally, a **(Note)** message is sent from the Broadband segment into the right Narrow-band segment. + +T11105020-99 + +Sequence diagram for passing of user-to-user signalling information showing (Note) messages across narrow-band and broadband segments. + +NOTE – Messages possible are: + +- IAM; +- ACM; +- CPG; +- CON (applicable only to narrow-band); +- ANM; +- SGM (applicable only to narrow-band); +- REL. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------|--------------------------|--------------------------| +| User-to-user information | User-to-user information | User-to-user information | + +#### 7.29.2 Service 2 + +##### 7.29.2.1 Request + +Refer to 7.29.1.2. + +##### 7.29.2.2 Passing of user-to-user signalling information + +![Diagram showing the passing of user-to-user signalling information (USR) across narrow-band and broadband interfaces. On the left, a narrow-band interface shows an incoming USR arrow pointing right and an outgoing USR arrow pointing left. In the center, a broadband interface shows two USR arrows: one pointing right and one pointing left. On the right, another narrow-band interface shows an outgoing USR arrow pointing right and an incoming USR arrow pointing left. The diagram is labeled T1162510-94.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Diagram showing the passing of user-to-user signalling information (USR) across narrow-band and broadband interfaces. On the left, a narrow-band interface shows an incoming USR arrow pointing right and an outgoing USR arrow pointing left. In the center, a broadband interface shows two USR arrows: one pointing right and one pointing left. On the right, another narrow-band interface shows an outgoing USR arrow pointing right and an incoming USR arrow pointing left. The diagram is labeled T1162510-94. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------|------------------------------------------------------|--------------------------| +| User-to-user information | User-to-user information
User-to-user information | User-to-user information | +| Access transport | User-to-user information
More data | Access transport | + +#### 7.29.3 Service 3 + +##### 7.29.3.1 Request during call set-up + +Refer to 7.29.1.2. + +##### 7.29.3.2 Request during the active phase + +![Diagram showing the passing of user-to-user signalling information (FAR and USR) across narrow-band and broadband interfaces. On the left, a narrow-band interface shows an incoming FAR arrow pointing right. In the center, a broadband interface shows a USR arrow pointing right. On the right, another narrow-band interface shows an outgoing FAR arrow pointing right. The diagram is labeled T1162520-94.](f732d3320afe06d979aabbd366184254_img.jpg) + +Diagram showing the passing of user-to-user signalling information (FAR and USR) across narrow-band and broadband interfaces. On the left, a narrow-band interface shows an incoming FAR arrow pointing right. In the center, a broadband interface shows a USR arrow pointing right. On the right, another narrow-band interface shows an outgoing FAR arrow pointing right. The diagram is labeled T1162520-94. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------------------------------|-----------------------------------------------|--------------------------------------------------| +| Facility indicator set to "user-to-user service" | Not carried | Facility indicator set to "user-to-user service" | +| User-to-user indicators | User-to-user indicators:
Service 3 request | User-to-user indicators | + +![Sequence diagram for Service 3 request. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows indicate the flow of FAA, USR, and FAA messages between these domains. A label T1162530-94 is present in the bottom right.](85e2327652d513a7fee8fdbf97ad06f1_img.jpg) + +Sequence diagram illustrating the flow of messages for Service 3 request across three domains: Narrow-band, Broadband, and Narrow-band. The diagram shows the following message flow: + +- An arrow labeled **FAA** points left from the Broadband domain to the Incoming narrow-band domain. +- An arrow labeled **USR** points left from the Outgoing narrow-band domain to the Broadband domain. +- An arrow labeled **FAA** points left from the Outgoing narrow-band domain to the Incoming narrow-band domain. + +T1162530-94 + +Sequence diagram for Service 3 request. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows indicate the flow of FAA, USR, and FAA messages between these domains. A label T1162530-94 is present in the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|--------------------------------------------------|----------------------------------------------------------|--------------------------------------------------| +| Facility indicator set to "user-to-user service" | Not carried | Facility indicator set to "user-to-user service" | +| User-to-user indicators | User-to-user indicators:
Service 3 response, provided | User-to-user indicators | + +![Sequence diagram for Service 3 response. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows indicate the flow of FRJ, USR, and FRJ messages between these domains. A label T1162540-94 is present in the bottom right.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Sequence diagram illustrating the flow of messages for Service 3 response across three domains: Narrow-band, Broadband, and Narrow-band. The diagram shows the following message flow: + +- An arrow labeled **FRJ** points left from the Broadband domain to the Incoming narrow-band domain. +- An arrow labeled **USR** points left from the Outgoing narrow-band domain to the Broadband domain. +- An arrow labeled **FRJ** points left from the Outgoing narrow-band domain to the Incoming narrow-band domain. + +T1162540-94 + +Sequence diagram for Service 3 response. It shows three vertical lines representing Narrow-band, Broadband, and Narrow-band domains. Arrows indicate the flow of FRJ, USR, and FRJ messages between these domains. A label T1162540-94 is present in the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------| +| Cause indicators are generated with the cause value set to # 63, "Service or option not available, unspecified" | Not carried | Cause indicators | +| Facility indicator set to "user-to-user service" | Not carried | Facility indicator set to "user-to-user service" | +| User-to-user indicators | User-to-user indicators:
Service 3 response, not provided | User-to-user indicators | + +##### 7.29.3.3 Passing of user-to-user signalling information + +Refer to 7.29.2.2. + +## 7.30 Global Virtual Network Service (GVNS) + +![Sequence diagram showing Forward GVNS messages (IAM, IAA) across Narrow-band, Broadband, and Narrow-band segments. The diagram shows three vertical lines representing network segments. From left to right: Narrow-band, Broadband, and Narrow-band. Arrows represent messages: IAM from the first Narrow-band to the Broadband; IAM and IAA between the Broadband and the second Narrow-band; and IAM from the Broadband to the second Narrow-band. A reference label T11105030-99 is at the bottom right.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Sequence diagram showing Forward GVNS messages (IAM, IAA) across Narrow-band, Broadband, and Narrow-band segments. The diagram shows three vertical lines representing network segments. From left to right: Narrow-band, Broadband, and Narrow-band. Arrows represent messages: IAM from the first Narrow-band to the Broadband; IAM and IAA between the Broadband and the second Narrow-band; and IAM from the Broadband to the second Narrow-band. A reference label T11105030-99 is at the bottom right. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| Forward GVNS | Forward GVNS | Forward GVNS | + +![Sequence diagram showing Backward GVNS messages (Note) across Narrow-band, Broadband, and Narrow-band segments. The diagram shows three vertical lines representing network segments. From left to right: Narrow-band, Broadband, and Narrow-band. Arrows represent messages: (Note) from the second Narrow-band to the Broadband; (Note) from the Broadband to the first Narrow-band; and (Note) from the second Narrow-band to the Broadband. A reference label T11105040-99 is at the bottom right.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +Sequence diagram showing Backward GVNS messages (Note) across Narrow-band, Broadband, and Narrow-band segments. The diagram shows three vertical lines representing network segments. From left to right: Narrow-band, Broadband, and Narrow-band. Arrows represent messages: (Note) from the second Narrow-band to the Broadband; (Note) from the Broadband to the first Narrow-band; and (Note) from the second Narrow-band to the Broadband. A reference label T11105040-99 is at the bottom right. + +NOTE – Messages possible are: + +- ANM; +- CPG; +- CON (applicable only to narrow-band). + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|----------------------|-------------------|----------------------| +| Backward GVNS | Backward GVNS | Backward GVNS | + +# 8 Application Transport Mechanism + +The tables in this clause show the mapping of information relevant to the application transport mechanism, in addition to the mapping of information relevant to the basic call. + +## 8.1 Segmentation not required + +![Diagram showing message flow from Narrow-band to Broadband to Narrow-band without segmentation. The message passes through interworking nodes without being split. Reference: T11105050-99.](ed48e24e36ea0501953177401c900f86_img.jpg) + +The diagram illustrates a message flow across three segments: Narrow-band (Note 1), Broadband (Note 1), and Narrow-band (Note 1). The message is shown as a single continuous arrow passing through two vertical lines representing interworking nodes, indicating that no segmentation or re-assembly is performed. The reference code T11105050-99 is shown at the bottom right. + +Diagram showing message flow from Narrow-band to Broadband to Narrow-band without segmentation. The message passes through interworking nodes without being split. Reference: T11105050-99. + +NOTE 1 – Messages possible are: + +- IAM; +- ACM; +- CPG; +- ANM; +- CON (applicable only to narrow-band); +- PRI; +- APM. + +NOTE 2 – No re-assembly procedures are performed at the narrow-band/broadband interworking node. + +| Incoming narrow-band | Transit broadband | Outgoing narrow-band | +|-----------------------|-----------------------|-----------------------| +| Application Transport | Application Transport | Application Transport | + +## 8.2 Segmentation required + +![Diagram showing message flow from Broadband to Narrow-band with segmentation. The message is split into multiple streams, each followed by 1 to 9 APM for each APM-user. Reference: T11105060-99.](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +The diagram illustrates a message flow from a Broadband segment to a Narrow-band segment. At the interworking node, the single broadband message is segmented into multiple parallel arrows. Each arrow is labeled '(Note)' and 'may be followed by 1 to 9 APM for each APM-user'. An ellipsis indicates additional segments. The reference code T11105060-99 is shown at the bottom right. + +Diagram showing message flow from Broadband to Narrow-band with segmentation. The message is split into multiple streams, each followed by 1 to 9 APM for each APM-user. Reference: T11105060-99. + +NOTE – Messages possible are: + +- IAM; +- ACM; +- CPG; +- ANM; +- CON (applicable only to narrow-band); +- PRI; +- APM. + +| Broadband | Outgoing narrow-band | +|-----------------------|-----------------------| +| Application Transport | Application Transport | + + + + + +## ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Languages and general software aspects for telecommunication systems | + +\*17764\* \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a8f178a252d2b0a6061cd8228dc2e703c2c75b7 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6be1b6974f742e8f1d39a1892da0542ebe2ef92489ef0c8b30675cb3199ddf15 +size 12173 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65e69be0e3a91d1a723eb02d21416aa62ee0679a --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6213c17bac256d6a9586e3416e4f019c8aad5eada30d89c713abcee134081b5 +size 43293 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/17a1ba23b641c01871b08f0a4f08ef48_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/17a1ba23b641c01871b08f0a4f08ef48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..367443da0334a2f607f03590ac705e7ceb4f228f --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/17a1ba23b641c01871b08f0a4f08ef48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2123e201e87526945c166c5a60a7f3837f54a3db19608e95ed3aa81b49634590 +size 18720 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8002cc8e203c30e99c09e5867b29f77d636017ed --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ae2dccd96ee6634647839e6cc30f128b8e8e8848ea1ac7cb1340e80bc2694b5 +size 7999 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ad3b9beb292ca2accf64f7b92998e6bcf74801c --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c40a6fb4af8e4b56dfc37ae3a4087559502bd9256b97682affdf924c2ddf7d24 +size 18589 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/22e0e0864e0bf015260feabd4bebec60_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/22e0e0864e0bf015260feabd4bebec60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af6daa07514395b9f1aaf51f7d09d7e2be613f76 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/22e0e0864e0bf015260feabd4bebec60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff8ec2a19e5f06f622ff479b548fe5b5a3624264edbb06a59052fec9a4dca6a0 +size 7847 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac30504b4430d325bdba575775c20de2aaf2434a --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30c5c749edf6dad6a83229905a3550faedc42672313d5c73d2617ff8c5950b19 +size 24447 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3650f01cd3cc58246ec14b67e73ffb8f03f10811 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:859ffd728d04345003dc22f057e8c4646ddd4c23f4df42021cfdda39bb4326d9 +size 30200 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4254d20256f0ee48b0931a26437383d1282c454a --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c580a75dd30e1c6572fd8c706db3dd4ce6b7025051f14c4b0371e6fea87572e +size 19773 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9023ce1cb46a1c051138d67ffc5bcdff1bda4761 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90ec2ed5d9abd8fee9e7d3a0df0f7d0b9f4ea4c5efbec86c388d03329ab6395b +size 10139 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4714dfc861f1656d9c270569f1abc9630680b62 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d34646f09784278ce08fbc7bb06691ac2ac95009522fed0cf83bc7a1cf00bf1 +size 45484 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..318fd92d28dfa50160f3d1cd49040f746f10f014 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccdd793de6a98f6b372e3f9be6b0a1dd9584e77b03de082e4d30e8fc2959d431 +size 27928 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c92aa6b220bef53b5d3b1eecc672ad43ad7722bb --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f6f8fe8a04f5fd06beaa3fda767c4cd910312b52e3af4ab03031dfb45c73c2d +size 31774 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4f50daa1723a6a80a6c8694054638192_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4f50daa1723a6a80a6c8694054638192_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c000fffee4dd122bf74e083cb49c05588802122 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/4f50daa1723a6a80a6c8694054638192_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:930f470a4524011878a098bb231f3b456d4e2fc63ef960e5653bc688de762fa3 +size 11313 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1319b50e149653eeb03b8bbbce158219cd04979 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:516d768bb6b6b1e9d0b198fac98f40f437783adc19f7c0c52d42f3df3ef6f762 +size 16982 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9bb25e7e99c572cff9f5ecee1e6c3e5053e453e --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6856486a7992621301b591e6400e6647480cfa92bc01f6052cde47a197fed639 +size 18039 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/63a2519518616620ef0e53d98b923c05_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/63a2519518616620ef0e53d98b923c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9434e1d118871020140256a157f2ac3a50f4218a --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/63a2519518616620ef0e53d98b923c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d60466ffa2a1c4103d0d6226b5297f941daebe7a69658fd1b252087008a33aae +size 18577 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/6707cae4df136f92a0c9f3a4676f91a6_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/6707cae4df136f92a0c9f3a4676f91a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..537f5edd2b43e93f7bab1d34de11b09af73d07d0 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/6707cae4df136f92a0c9f3a4676f91a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c58f3b80f8339f303c7124e9c0184f576b700feaf1193d3d835b274dd67340d6 +size 10347 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64efb4f18ba3b9b44a13942949e6d992c03840a8 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f36e29528ef029097e2fd5bd5c89e52060e834015e4c79df550eb038851913c9 +size 9886 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b88116bd80a7f99c5fccd97c44a6b5c90c7d57f --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3145957d53669a9f7baf9cb66d2f9cbe9ebc89d50cd494a6624cc8773fc843a4 +size 21739 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b641c8d6f5909594e44e51d5b0f6c9ac47250982 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4bdba9d47ed73fe612339e05314974df0c9a324b20d4ee95a703b3dd89d1d57 +size 21197 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49b0358b1c74e18a460084df555a800104aa6540 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e885db144882cc6c4c324d4e24cd89684af33650c6c9e60380a2816a0273cd1d +size 10908 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d8c758885b4f754ff071bf3b572ab3c_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d8c758885b4f754ff071bf3b572ab3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01f329234a3e372fdb79af3a64ece25c6a26437c --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8d8c758885b4f754ff071bf3b572ab3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6d010a8f0395f50d1d89c9f8de7301934a4ac2600c0a5a5b425ea70c83ec02a +size 12133 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8facb5a02c64e245808bafc005e65032_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8facb5a02c64e245808bafc005e65032_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1474ed98f75d5ee474d6579d08dfd07d551ff304 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/8facb5a02c64e245808bafc005e65032_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82cd0d02a4f4e6b807552518e80548bf5490a498bf7a667eb8b4e6eaf924263b +size 20062 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/9dd03da031e134bfc9ecc730dd5f6583_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/9dd03da031e134bfc9ecc730dd5f6583_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e70a5379fb7bfd1373f85391f98c76fd35fdbf3e --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/9dd03da031e134bfc9ecc730dd5f6583_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a7aeb1a296fc97cb1438dbfda3298b1fe04d28e02aa853fb8430e498eaa6d70 +size 20063 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3827335dbad13d561239a00530f9ea527af4d41f --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14c07f75cc4cc9c305763647bbc189fa5cd900169832cd1f7d0b60ac294be127 +size 11409 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a057800564be3506d2d87b6a4daee25b_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a057800564be3506d2d87b6a4daee25b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab5e44e0535e68ff7a855efd1d6484931e7e89ba --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a057800564be3506d2d87b6a4daee25b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b61f69a25aeb173c970acaee804bb74996fe619c865c9130bc7bbaf24bda781 +size 17165 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc0dba15a846e7c3b945612edb6fc785a67c6d5b --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4733d67af99246df1c502ea4df60d2c74e09f576b2f7a59e80b63bbeddbd48f +size 17997 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95bce5ca36fd66af67acd01075b96198c7d58b9b --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7da3c770b3ddfe01be641ce7dd0fd75534b5bffe1a4c6913b4802793660b18e9 +size 9162 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c09d14d882d396577595d88c22e370552f1a4c97 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:734f9e493c0488d050feb85bcc962327ee82dd0b058629c26dc9fd1bba1c0b3a +size 9584 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..218e134b021e94b6e3192352c5b9237c5675bb38 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a9f9fd49fa812d39503345a3b3fc930992f4fa722cf4acc199f1a20462f94db +size 11485 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/b6b53a74ad203c01b81e5427e9d6a898_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/b6b53a74ad203c01b81e5427e9d6a898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f447745a6585d72f197577e84ed5b8c5d4e4b5b8 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/b6b53a74ad203c01b81e5427e9d6a898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c912008f825fabd4fb8bb7da8fcf0aa3915c241fe8be57fb97a26ffe38224991 +size 19486 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a3e9f5c7841388cfa605a223638548c4d36251a --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42f39ec8638c5d7ae15d2ef2003d2eb90083fe8408bcfa5e2c3833228ac47b8d +size 46144 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca8913a9d3e6044e5004f5edc16dcef5ac5e64f0 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10193ab14d3f6c0b5db4890fb09a0b83a4188db9435d71165d47f9751a2226c1 +size 22003 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adf827a01a4c2e5aa75fd58f5ed748170d4b5b1c --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f4de0d921f7d3eaf030be13deb777c9fcb81d0a7de2a548a48ac3053755a0ce +size 9495 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3db1151d6e01b148e091e2a0f758c9bff8dbf0c --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a965a70d9ab5e1eccbd14b9248a2169ec032af0eb90f6fc63ff0eaff773203f9 +size 12262 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19372475f95a5576de2eed9a8920825b5876c824 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bffaf70b5474e3bef34254a780dc58479e750cc2e9f716fbf7bf94c49ba0960 +size 16264 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/dec689324b075952626a86da862b9549_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/dec689324b075952626a86da862b9549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..621c30d0dcbb143ef3510540f69c58649322ad0e --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/dec689324b075952626a86da862b9549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2c47e0f36172da8752bd18e1c9d1be2870eed40901166fb8a1ac3e2f3fc8f48 +size 40428 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/df94f7807f02e218ee3c66b9cbd829e5_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/df94f7807f02e218ee3c66b9cbd829e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a63a1cc95cd441a75de80897a08495163163fc8 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/df94f7807f02e218ee3c66b9cbd829e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9f1a7e4c10c26dc18790c40a432a7aac0582adcd04dccb57fb8b15c81faf173 +size 9547 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42fb9be0cff54649ae61de53526bbc5666086e01 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e85232c1305972d862b49415487d82638ba5fa2f67361829888561ca58c6ff48 +size 10488 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62b25524d7e236543e098b6a491795b75019dc97 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d607a2e4f8f9f1d8e2d17d1c325e0587eb52061e9b6de46f700f1698ab02f0d +size 17967 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/f5d2a88925807080157c7cfb1d41cf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93246bbb2e5111af654e56c4f40e2cb6162ac416 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/f5d2a88925807080157c7cfb1d41cf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6acaf79495b02dffb7f7127386c5bc17565c99b2753e611a5740cc1ab383dde +size 9958 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e264e653c58803056178e501e64a4da344b9fd48 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38fc9f61a54792960ac4f7585451cd835bac48ca3fe538f0a08887def3156aeb +size 21312 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10e53a3a0e23cfddc4ddcd5f7c45b869957bf8f4 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f3af6fda9827c8cad9cbf072808e495ecab8e05edf8ee325b8d27970e96bdfd +size 10865 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..805f7012ca2c667cfaa55c3153034d9a4224942f --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fb1fa9b294057cad03d02cfe5996ae8bc9bd753314dc476249bf8d8f3f53668 +size 12208 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58ddf1fbc7069e8afae32359bdb9d6b6f98ec58c --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc1429d5cdf29694f8da764867ed33d788e3582bb28697d0b436d4a9f0ebf406 +size 19062 diff --git a/marked/Q/T-REC-Q.2763-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cd69c2983aa7e4c3ac76fdf0ccfbbe9ce58667c7 --- /dev/null +++ b/marked/Q/T-REC-Q.2763-199912-I_PDF-E/raw.md @@ -0,0 +1,4520 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2763** + +(12/1999) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for the +network signalling + +--- + +**Signalling System No. 7 B-ISDN User Part +(B-ISUP) – Formats and codes** + +ITU-T Recommendation Q.2763 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| General aspects | Q.2000-Q.2099 | +| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 | +| Signalling network protocols | Q.2200-Q.2299 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 | +| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **Signalling System No. 7 B-ISDN User Part (B-ISUP) – Formats and codes** + +## **Summary** + +This ITU-T Recommendation is one of a set of ITU-T Recommendations that describe the Broadband ISDN User Part. It specifies the formats and codes of the B-ISDN User Part messages and parameters required to support basic bearer services and supplementary services. + +The scope of the B-ISDN User Part covers international B-ISDN networks. However, the B-ISDN User Part is suitable for national applications. Most messages and parameters specified for international use are also required in typical national applications. + +## **Source** + +ITU-T Recommendation Q.2763 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 3 December 1999. + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +###### Page + +| | | | +|------|-----------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | General encoding principles ..... | 2 | +| 5.1 | Routing label..... | 3 | +| 5.2 | Message compatibility information ..... | 3 | +| 5.3 | Message type code ..... | 3 | +| 5.4 | Message length..... | 4 | +| 5.5 | Formatting principles ..... | 5 | +| 5.6 | Encoding principles for subfields ..... | 8 | +| 5.7 | Order of transmission..... | 9 | +| 5.8 | Coding of spare bits ..... | 9 | +| 5.9 | National message types and parameters..... | 9 | +| 5.10 | Rules for the allocation of message, parameter name, and parameter subfield codes ..... | 9 | +| 5.11 | Formats and codes of parameters originated from the access protocol ..... | 9 | +| 6 | Parameter formats and codes ..... | 9 | +| 6.1 | Message type codes..... | 9 | +| 6.2 | Coding of the message length indicator..... | 10 | +| 6.3 | Coding of the parameter length indicator ..... | 10 | +| 6.4 | Coding of the message compatibility information..... | 10 | +| 6.5 | Coding of the parameter compatibility information ..... | 11 | +| 7 | B-ISDN User Part parameters..... | 12 | +| 7.1 | Parameter names ..... | 12 | +| 7.2 | AAL parameters..... | 12 | +| 7.3 | AAL prime parameters..... | 13 | +| 7.4 | Access delivery information ..... | 13 | +| 7.5 | Additional ATM cell rate..... | 14 | +| 7.6 | Additional calling party number ..... | 15 | +| 7.7 | Additional connected number..... | 17 | +| 7.8 | AESA for additional calling party ..... | 17 | +| 7.9 | AESA for additional connected party ..... | 17 | +| 7.10 | AESA for called party..... | 17 | + +| | Page | | +|------|---------------------------------------------------|----| +| 7.11 | AESA for calling party ..... | 18 | +| 7.12 | AESA for connected party ..... | 18 | +| 7.13 | Alternative ATM cell rate ..... | 18 | +| 7.14 | Application generated identifier ..... | 19 | +| 7.15 | Application transport ..... | 20 | +| 7.16 | ATC setup parameters ..... | 20 | +| 7.17 | ATM cell rate ..... | 20 | +| 7.18 | Automatic congestion level ..... | 20 | +| 7.19 | Automatic re-routing (crankback) ..... | 21 | +| 7.20 | Backward GVNS ..... | 21 | +| 7.21 | Backward narrow-band interworking indicator ..... | 22 | +| 7.22 | Broadband bearer capability ..... | 22 | +| 7.23 | Broadband high layer information ..... | 23 | +| 7.24 | Broadband low layer information ..... | 23 | +| 7.25 | Call diversion information ..... | 24 | +| 7.26 | Call diversion may occur ..... | 24 | +| 7.27 | Call diversion treatment indicators ..... | 25 | +| 7.28 | Call history information ..... | 25 | +| 7.29 | Call offering treatment indicators ..... | 26 | +| 7.30 | Call transfer number ..... | 26 | +| 7.31 | Call transfer reference ..... | 28 | +| 7.32 | Called IN number ..... | 28 | +| 7.33 | Called party number ..... | 28 | +| 7.34 | Called party sub-address ..... | 30 | +| 7.35 | Called party's indicators ..... | 30 | +| 7.36 | Calling party number ..... | 31 | +| 7.37 | Calling party sub-address ..... | 33 | +| 7.38 | Calling party's category ..... | 33 | +| 7.39 | Cause indicators ..... | 34 | +| 7.40 | CCSS ..... | 34 | +| 7.41 | CDVT ..... | 34 | +| 7.42 | Charge indicator ..... | 34 | +| 7.43 | Charged party identification (national use) ..... | 35 | +| 7.44 | Closed User Group information ..... | 35 | +| 7.45 | Collect call request ..... | 35 | +| 7.46 | Conference treatment indicators ..... | 36 | + +| | Page | +|-----------------------------------------------------------------|-------------| +| 7.47 Connected line identity request..... | 36 | +| 7.48 Connected number ..... | 36 | +| 7.49 Connected sub-address..... | 37 | +| 7.50 Connection element identifier..... | 38 | +| 7.51 Connection identifier ..... | 38 | +| 7.52 Consistency check result information..... | 38 | +| 7.53 Correlation ID ..... | 39 | +| 7.54 Destination connection link identifier..... | 39 | +| 7.55 Destination signalling identifier (DSID)..... | 39 | +| 7.56 Display information ..... | 40 | +| 7.57 Echo control information ..... | 40 | +| 7.58 End-to-end transit delay network generated indicator ..... | 41 | +| 7.59 Exclusive connection element identifier..... | 41 | +| 7.60 Extended Quality of Service ..... | 42 | +| 7.61 Forward GVNS ..... | 42 | +| 7.62 Forward narrow-band interworking indicator..... | 44 | +| 7.63 Hop counter..... | 45 | +| 7.64 In-band information indicator ..... | 45 | +| 7.65 Leaf party type ..... | 45 | +| 7.66 Link layer core parameters..... | 46 | +| 7.67 Link layer protocol parameters ..... | 46 | +| 7.68 Location number ..... | 46 | +| 7.69 Loop prevention indicators ..... | 48 | +| 7.70 Maximum end-to-end transit delay..... | 49 | +| 7.71 MCID response indicators ..... | 49 | +| 7.72 MCID request indicators..... | 49 | +| 7.73 Minimum ATM cell rate..... | 50 | +| 7.74 MLPP precedence ..... | 50 | +| 7.75 MLPP user information..... | 51 | +| 7.76 Narrow-band bearer capability..... | 52 | +| 7.77 Narrow-band high layer compatibility ..... | 52 | +| 7.78 Narrow-band low layer compatibility ..... | 53 | +| 7.79 National/international call indicator ..... | 54 | +| 7.80 Network call correlation identifier..... | 54 | +| 7.81 Network look ahead indicator..... | 55 | +| 7.82 Network management controls ..... | 55 | + +| | Page | +|------------------------------------------------------|-------------| +| 7.83 Notification ..... | 55 | +| 7.84 OAM traffic descriptor ..... | 56 | +| 7.85 Original called number ..... | 57 | +| 7.86 Origination connection link identifier..... | 57 | +| 7.87 Origination ISC point code ..... | 58 | +| 7.88 Origination signalling identifier..... | 58 | +| 7.89 Priority ..... | 58 | +| 7.90 Progress indicator..... | 59 | +| 7.91 Propagation delay counter..... | 59 | +| 7.92 Quality of service (QoS) ..... | 60 | +| 7.93 Redirecting number..... | 60 | +| 7.94 Redirection information ..... | 61 | +| 7.95 Redirection number..... | 62 | +| 7.96 Redirection number restriction ..... | 62 | +| 7.97 Remote operations (national use)..... | 63 | +| 7.98 Report type..... | 63 | +| 7.99 Report type prime ..... | 64 | +| 7.100 Resource identifier ..... | 64 | +| 7.101 SCF ID ..... | 65 | +| 7.102 Segmentation indicator (national use) ..... | 65 | +| 7.103 Service activation..... | 66 | +| 7.104 Soft PVC called endpoint ..... | 66 | +| 7.105 Soft PVC calling endpoint ..... | 67 | +| 7.106 Subsequent number..... | 67 | +| 7.107 Suspend/resume indicators ..... | 68 | +| 7.108 Transit network selection (national use) ..... | 68 | +| 7.109 UID action indicators..... | 69 | +| 7.110 UID capability indicators ..... | 70 | +| 7.111 User-to-user indicators..... | 70 | +| 7.112 User-to-user information..... | 71 | +| 8 B-ISDN User Part messages and codes ..... | 72 | + +## **Signalling System No. 7 B-ISDN User Part (B-ISUP) – Formats and codes** + +## **1 Scope** + +This ITU-T Recommendation specifies the formats and codes of the B-ISDN User Part messages and parameters required to support basic bearer services and supplementary services for B-ISDN applications. + +The B-ISDN User Part is applicable to international B-ISDN networks. Furthermore, the B-ISDN User Part is suitable for national applications. Most messages and parameters specified for international use are also required in typical national applications. Moreover, coding space has been reserved in order to allow national Administrations and recognized operating agencies to introduce network specific signalling messages and parameters within the internationally standardized protocol structure. + +## **2 References** + +See ITU-T Recommendation Q.2761. + +## **3 Terms and definitions** + +See ITU-T Recommendation Q.2761. + +## **4 Abbreviations** + +This ITU-T Recommendation uses the following abbreviations: + +| | | +|--------|------------------------------------------------| +| ABR | Available Bit Rate | +| ABT-DT | ATM Block Transfer with Delayed Transmission | +| ABT-IT | ATM Block Transfer with Immediate Transmission | +| AESA | ATM End System Address | +| ANM | Answer Message | +| ASE | Application Service Element | +| ATC | ATM Transfer Capability | +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband Integrated Services Digital Network | +| CLP | Cell Loss Priority | +| DBR | Deterministic Bit Rate | +| DPC | Destination Point Code | +| ECT | Explicit Call Transfer (supplementary service) | +| FPH | Freephone (supplementary service) | +| GVNS | Global Virtual Network Service | +| IAM | Initial Address Message | + +| | | +|------|---------------------------------| +| ICR | Initial Cell Rate | +| MBS | Maximum Burst Size | +| MCID | Malicious Call Identification | +| NI | Network Identity | +| OPC | Origination Point Code | +| PCR | Peak Cell Rate | +| QoS | Quality of Service | +| RM | Resource Management | +| SAAL | Signalling ATM Adaptation Layer | +| SCR | Sustainable Cell Rate | +| SLS | Signalling Link Selection | +| STM | Synchronous Transfer Mode | + +For further abbreviations, see ITU-T Recommendation Q.2761. + +## 5 General encoding principles + +B-ISDN User Part messages are carried on the ATM signalling link by means of SAAL service data units, the format of which is described in 6.2/Q.2110. + +As a national option, B-ISDN User Part messages can be carried on the STM signalling link by means of signal units, the format of which is described in 2.2/Q.703. + +The format of and the codes used in the service information octet are described in 14.2/Q.704 and 9.5/Q.2210. The service indicator for the B-ISDN User Part is coded 1001. + +The signalling information field of each message signal unit containing an B-ISDN User Part message consists of an integral number of octets and encompasses the following parts (see Figure 1): + +- a) routing label; +- b) message type code; +- c) message length; +- d) message compatibility information; +- e) message content. + +A description of the various message parts is given in the following subclauses. + +![Diagram showing the B-ISDN User Part message format as a vertical stack of five rectangular boxes. From top to bottom, the boxes are labeled: 'Routing label', 'Message type code', 'Message length', 'Message compatibility information', and 'Message content'.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +| | +|-----------------------------------| +| Routing label | +| Message type code | +| Message length | +| Message compatibility information | +| Message content | + +Diagram showing the B-ISDN User Part message format as a vertical stack of five rectangular boxes. From top to bottom, the boxes are labeled: 'Routing label', 'Message type code', 'Message length', 'Message compatibility information', and 'Message content'. + +**Figure 1/Q.2763 – B-ISDN User Part message format** + +### 5.1 Routing label + +The format and codes used for the routing label are described in 2.2/Q.704. For each ATM virtual connection the same routing label must be used for each message that is transmitted for that connection. + +The SLS value is allocated on a cyclic basis per signalling association, e.g. values of a cyclic 4-bit counter incremented for each new signalling association. A counter is required for each allocated OPC/DPC/NI combination. + +### 5.2 Message compatibility information + +The message compatibility information consists of a one-octet field and is mandatory for all messages. The message compatibility information defines the behaviour of a switch if the message is not understood. + +### 5.3 Message type code + +The message type code consists of a one-octet field and is mandatory for all messages. The message type code uniquely defines the function and format of each B-ISDN User Part message. The allocation with reference to the appropriate descriptive clause of this Recommendation is summarized in Table 1. + +**Table 1/Q.2763 – Message type codes** + +| Message type | Reference (Table) | Code | +|-------------------------------------------|-------------------|-----------| +| Address complete | 3 | 0000 0110 | +| Answer | 4 | 0000 1001 | +| Application transport | 5 | 0100 0001 | +| Blocking | 6 | 0001 0011 | +| Blocking acknowledgement | 7 | 0001 0101 | +| Call progress | 8 | 0010 1100 | +| Call transfer | 9 | 0011 1001 | +| Connection available (Note) | 10 | 0011 1101 | +| Confusion | 11 | 0010 1111 | +| Consistency check request | 12 | 0000 0101 | +| Consistency check request acknowledgement | 13 | 0001 0001 | +| Consistency check end | 14 | 0001 0111 | +| Consistency check end acknowledgement | 15 | 0001 1000 | +| Facility | 16 | 00110011 | +| Forward transfer | 17 | 0000 1000 | +| Identification request | 18 | 0011 0110 | +| Identification response | 19 | 0011 0111 | +| Initial address | 20 | 0000 0001 | +| IAM acknowledgement | 21 | 0000 1010 | +| IAM reject | 22 | 0000 1011 | +| Loop prevention | 23 | 0100 0000 | +| Modify acknowledgement | 24 | 0011 1010 | + +**Table 1/Q.2763 – Message type codes (concluded)** + +| Message type | Reference
(Table) | Code | +|------------------------------------------------|----------------------|-----------| +| Modify reject | 25 | 0011 1011 | +| Modify request | 26 | 0011 1100 | +| Network resource management | 27 | 0011 0010 | +| Pre-release information | 36 | 0100 0010 | +| Release | 28 | 0000 1100 | +| Release complete | 29 | 0001 0000 | +| Reset | 6 | 0001 0010 | +| Reset acknowledgement | 7 | 0000 1111 | +| Resume | 32 | 0000 1110 | +| Segmentation (national use) | 30 | 0011 1000 | +| Subsequent address | 31 | 0000 0010 | +| Suspend | 32 | 0000 1101 | +| Unblocking | 6 | 0001 0100 | +| Unblocking acknowledgement | 7 | 0001 0110 | +| User Part available | 33 | 0011 0101 | +| User Part test | 34 | 0011 0100 | +| User-to-user information | 35 | 0010 1101 | +| Reserved, used in N-ISUP | | 0000 0011 | +| Reserved, used in N-ISUP | | 0000 0100 | +| Reserved, used in N-ISUP | | 0000 0111 | +| Reserved, used in N-ISUP | | 0001 1001 | +| | | to | +| | | 0010 1011 | +| Reserved, used in N-ISUP | | 0010 1110 | +| Reserved, used in N-ISUP | | 0011 0000 | +| Reserved, used in N-ISUP | | 0011 0001 | +| " " " " | | 0100 0011 | +| Reserved, used in N-ISUP for future extensions | | 1000 0000 | +| Reserved for extension of name code | | 1111 1111 | + +NOTE – The former name of the message was Modify Confirm. Existing procedures are not influenced by this editorial change. However, this message may be used in additional procedure(s). + +### 5.4 Message length + +The message length consists of a fixed length field and is mandatory for all messages. The message length uniquely indicates the number of octets included in the B-ISDN User Part message content and the message compatibility information fields (see Figure 1). + +### 5.5 Formatting principles + +The message content of each message contains a number of parameter listed and described in clause 6. Each parameter has a NAME which is coded as a single octet (see Table 2). The length of a parameter may be fixed or variable, and a length indicator of fixed length for each parameter is included. Every parameter contains parameter compatibility information (see Figure 2). + +**Table 2/Q.2763 – Parameter name codes** + +| Parameter name | Reference (subclause) | Code | +|---------------------------------------------|-----------------------|-----------| +| AAL parameters | 7.2 | 0100 0111 | +| AAL prime parameters | 7.3 | 1001 0001 | +| Access delivery information | 7.4 | 0010 1110 | +| Additional ATM cell rate | 7.5 | 0101 1010 | +| Additional calling party number | 7.6 | 0001 0000 | +| Additional connected number | 7.7 | 0001 0001 | +| AESA for additional calling party | 7.8 | 1001 0010 | +| AESA for additional connected party | 7.9 | 1001 0011 | +| AESA for called party | 7.10 | 0101 1000 | +| AESA for calling party | 7.11 | 0101 1001 | +| AESA for connected party | 7.12 | 0110 1101 | +| Alternative ATM cell rate | 7.13 | 0101 0111 | +| Application generated identifier | 7.14 | 0110 1010 | +| Application transport | 7.15 | 0111 1000 | +| ATC setup parameters | 7.16 | 1001 0111 | +| ATM cell rate | 7.17 | 0000 1000 | +| Automatic congestion level | 7.18 | 0010 0111 | +| Automatic re-routing (crankback) | 7.19 | 1001 0110 | +| Backward GVNS | 7.20 | 0100 1101 | +| Backward narrow-band interworking indicator | 7.21 | 0001 0100 | +| Broadband bearer capability | 7.22 | 0101 0000 | +| Broadband high layer information | 7.23 | 0100 0110 | +| Broadband low layer information | 7.24 | 0100 1111 | +| Call diversion information | 7.25 | 0011 0110 | +| Call diversion may occur | 7.26 | 0010 0110 | +| Call diversion treatment indicators | 7.27 | 0110 1110 | +| Call history information | 7.28 | 0010 1101 | +| Call offering treatment indicators | 7.29 | 0111 0000 | +| Call transfer number | 7.30 | 0100 0101 | +| Call transfer reference | 7.31 | 0100 0011 | +| Called IN number | 7.32 | 0110 1111 | +| Called party number | 7.33 | 0000 0100 | +| Called party sub-address | 7.34 | 0001 0101 | +| Called party's indicators | 7.35 | 0001 0111 | +| Calling party number | 7.36 | 0000 1010 | +| Calling party sub-address | 7.37 | 0001 0110 | + +**Table 2/Q.2763 – Parameter name codes (continued)** + +| Parameter name | Reference (subclause) | Code | +|------------------------------------------------------|------------------------------|-------------| +| Calling party's category | 7.38 | 0000 1001 | +| Cause indicators | 7.39 | 0001 0010 | +| CCSS | 7.40 | 0100 1011 | +| CDVT | 7.41 | 0111 1110 | +| Charge indicator | 7.42 | 0001 1001 | +| Charged party identification (national use) | 7.43 | 0111 0001 | +| Closed User Group information | 7.44 | 0001 1010 | +| Collect call request | 7.45 | 0111 1001 | +| Conference treatment indicators | 7.46 | 0111 0010 | +| Connected line identity request | 7.47 | 0001 1011 | +| Connected number | 7.48 | 0010 0001 | +| Connected sub-address | 7.49 | 0010 0100 | +| Connection element identifier | 7.50 | 0000 0110 | +| Connection identifier | 7.51 | 0110 1001 | +| Consistency check result information | 7.52 | 0100 1010 | +| Correlation ID | 7.53 | 0110 0101 | +| Destination connection link identifier | 7.54 | 0101 0100 | +| Destination signalling identifier | 7.55 | 0000 0011 | +| Display information | 7.56 | 0111 0011 | +| Echo control information | 7.57 | 0011 0111 | +| End-to-end transit delay network generated indicator | 7.58 | 1001 1001 | +| Exclusive connection element identifier | 7.59 | 1001 0101 | +| Extended quality of service | 7.60 | 1001 0000 | +| Forward GVNS | 7.61 | 0100 1100 | +| Forward narrow-band interworking indicator | 7.62 | 0001 1100 | +| Hop counter | 7.63 | 0011 1101 | +| In-band information indicator | 7.64 | 0001 1111 | +| Leaf party type | 7.65 | 0101 0110 | +| Link layer core parameters | 7.66 | 0110 1011 | +| Link layer protocol parameters | 7.67 | 0110 1100 | +| Location number | 7.68 | 0011 1111 | +| Loop prevention indicators | 7.69 | 0100 0100 | +| Maximum end-to-end transit delay | 7.70 | 0000 0111 | +| MCID response indicators | 7.71 | 0011 1100 | +| MCID request indicators | 7.72 | 0011 1011 | +| Minimum ATM cell rate | 7.73 | 0101 0010 | +| MLPP precedence | 7.74 | 0011 1010 | +| MLPP user information | 7.75 | 0100 1001 | +| Narrow-band bearer capability | 7.76 | 0001 1101 | +| Narrow-band high layer compatibility | 7.77 | 0011 0100 | +| Narrow-band low layer compatibility | 7.78 | 0010 0101 | +| National/international call indicator | 7.79 | 0010 1001 | +| Network call correlation identifier | 7.80 | 0110 1000 | + +**Table 2/Q.2763 – Parameter name codes (continued)** + +| Parameter name | Reference (subclause) | Code | +|------------------------------------------|-----------------------|------------------------------| +| Network look ahead indicator | 7.81 | 0101 1111 | +| Network management controls | 7.82 | 0101 1011 | +| Notification | 7.83 | 0010 1100 | +| OAM traffic descriptor | 7.84 | 0100 1000 | +| Original called number | 7.85 | 0010 1000 | +| Origination connection link identifier | 7.86 | 0101 0101 | +| Origination ISC point code | 7.87 | 0010 1011 | +| Origination signalling identifier | 7.88 | 0000 0010 | +| Priority | 7.89 | 0110 0111 | +| Progress indicator | 7.90 | 0011 0101 | +| Propagation delay counter | 7.91 | 0011 0001 | +| Quality of Service | 7.92 | 0101 0011 | +| Redirecting number | 7.93 | 0000 1011 | +| Redirection information | 7.94 | 0001 0011 | +| Redirection number | 7.95 | 0000 1100 | +| Redirection number restriction | 7.96 | 0100 0000 | +| Remote operations (national use) | 7.97 | 0011 0010 | +| Report type | 7.98 | 0110 0100 | +| Report type prime | 7.99 | 1001 0100 | +| Resource identifier | 7.100 | 0011 1001 | +| SCF ID | 7.101 | 0110 0110 | +| Segmentation indicator (national use) | 7.102 | 0011 1110 | +| Service activation | 7.103 | 0011 0011 | +| Soft PVC called endpoint | 7.104 | 0111 0110 | +| Soft PVC calling endpoint | 7.105 | 1001 1000 | +| Subsequent number | 7.106 | 0000 0101 | +| Suspend/resume indicators | 7.107 | 0010 0010 | +| Transit network selection (national use) | 7.108 | 0010 0011 | +| UID action indicators | 7.109 | 0111 0100 | +| UID capability indicators | 7.110 | 0111 0101 | +| User-to-user indicators | 7.111 | 0010 1010 | +| User-to-user information | 7.112 | 0010 0000 | +| Reserved for FPH | | 0101 0001 | +| Reserved for look result | | 0101 1110 | +| Reserved, used in N-ISUP | | 0000 0000 | +| Reserved, used in N-ISUP | | 0000 0001 | +| Reserved, used in N-ISUP | | 0000 1101
to
0000 1111 | +| Reserved, used in N-ISUP | | 0001 1000 | +| Reserved, used in N-ISUP | | 0001 1110 | +| Reserved, used in N-ISUP | | 0010 1111 | +| Reserved, used in N-ISUP | | 0011 0000 | + +**Table 2/Q.2763 – Parameter name codes (*concluded*)** + +| Parameter name | Reference
(subclause) | Code | +|-------------------------------------|--------------------------|-----------| +| Reserved, used in N-ISUP | | 0011 1000 | +| Reserved, used in N-ISUP | | 0100 0001 | +| Reserved, used in N-ISUP | | 0100 0010 | +| Reserved, used in N-ISUP | | 0100 1110 | +| Reserved used in N-ISUP | | 0111 0111 | +| Reserved used in N-ISUP | | 0111 1010 | +| | | to | +| | | 0111 1101 | +| Reserved used in N-ISUP | | 0111 1111 | +| | | to | +| | | 1000 1110 | +| Reserved used in N-ISUP | | 1010 0000 | +| | | to | +| | | 1010 1111 | +| Reserved, used in N-ISUP | | 1100 0000 | +| Reserved, used in N-ISUP | | 1100 0001 | +| Reserved for extension of name code | | 1111 1111 | + +| | +|-------------------------------------| +| Parameter name | +| Length indicator | +| | +| Parameter compatibility information | +| Parameter content | + +**Figure 2/Q.2763 – B-ISDN User Part parameter format** + +The detailed format of the length indicator and the parameter compatibility information is described in clause 6. + +The detailed format of the parameter content is uniquely defined for each parameter as described in clause 7. + +Between parameters there should be no unused (i.e. dummy) octets. + +### 5.6 Encoding principles for subfields + +The content of each parameter contains a number of subfields. Within each subfield, the least significant bit of the field is represented by the lowest-numbered bit and the most significant bit is represented by the highest-numbered bit. In case a subfield exceeds one octet, the significance of the bits, if applicable, is indicated in clause 7. + +### 5.7 Order of transmission + +Since all the fields consist of an integral number of octets, the formats are presented as a stack of octets. The first octet transmitted to the underlying layer/level is the one shown at the top of the stack and the last is the one at the bottom. + +Unless otherwise indicated, within each octet and subfield the bits are transmitted to the underlying layer/level with the least significant bit first. + +### 5.8 Coding of spare bits + +Spare bits are coded "0" unless indicated otherwise. + +Any parameter values marked as "spare", "reserved", or "national use" may be regarded as unrecognised. + +### 5.9 National message types and parameters + +If messages type codes and parameters are required for national uses not included in this Recommendation, the codes chosen should be from the highest code downwards, that is, starting at code 11111110. Message type codes in the range 11111110 to 11100000 and parameter name codes in the range 11111110 to 11000001 are reserved exclusively for this purpose. + +### 5.10 Rules for the allocation of message, parameter name, and parameter subfield codes + +- a) Existing N-ISUP message and parameter name codes used in B-ISUP should have the same name codes in B-ISUP. +- b) Existing N-ISUP message and parameter name codes not used in B-ISUP should be marked reserved in B-ISUP. +- c) B-ISUP message and parameter name codes not used in N-ISUP should be marked reserved in N-ISUP. +- d) The code point 11111111 for both message and parameter name codes is reserved in B-ISUP to indicate extension of the name code: + - a second parameter name octet shall appear as the first octet in the parameter content (see Figure 2); + - a second message name octet shall be encoded in a new parameter. +- e) Allocation of codes for subfields of parameters used in both B-ISUP and N-ISUP must avoid overlapping and be coordinated. + +### 5.11 Formats and codes of parameters originated from the access protocol + +The formats and codes of the parameters which are originated from the access protocol are the same as specified in Recommendation ITU-T Q.2931. The coding standard subfield for such parameters shall be coded as specified in Recommendation ITU-T Q.2931. + +## 6 Parameter formats and codes + +### 6.1 Message type codes + +The encoding of the message type is shown in Table 1. + +### 6.2 Coding of the message length indicator + +The format of the message length indicator field is shown in Figure 3. + +![Diagram of the message length indicator field showing two octets. Octet 1 contains bits 8 through 1, and Octet 2 contains bits 1 through 0. The entire 16-bit field is labeled 'Length indicator'.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +| | | +|----------------------------------------------------|--------| +| 8      7      6      5      4      3      2      1 | Octets | +| Length indicator | 1 | +| | 2 | + +Diagram of the message length indicator field showing two octets. Octet 1 contains bits 8 through 1, and Octet 2 contains bits 1 through 0. The entire 16-bit field is labeled 'Length indicator'. + +**Figure 3/Q.2763 – Message length indicator field** + +The message length indicator field is binary coded to indicate the number of octets in the message content field and the message compatibility information field (see Figure 1). The length indicated does not include the routing label octets, the message type code octets or the message length indicator octets. + +The following codes are used in the message length indicator subfield: + +- a) *Length indicator* + A code expressing in pure binary representation the number of octets (see Note). Bit 8 of octet 1 is the most significant and bit 1 of octet 2 is the least significant respectively. + NOTE – The actual maximum message length is given by the lower levels. + +### 6.3 Coding of the parameter length indicator + +The format of the parameter length indicator subfield corresponds to the format shown in Figure 3. + +The parameter length indicator subfield is binary coded to indicate the number of octets in the parameter content and parameter compatibility information fields (see Figure 2). The length indicated does not include the parameter name octet or the parameter length indicator octets. + +### 6.4 Coding of the message compatibility information + +The format of the message compatibility information is shown in Figure 4. + +![Diagram of the message compatibility information field showing 8 subfields in a single octet. Bit 8 is 'ext.', bit 7 is 'Broadband/narrow-band interworking indicator', bit 6 is 'Pass on not possible ind.', bit 5 is 'Discard message ind.', bit 4 is 'Send notification ind.', bit 3 is 'Release call indicator', bit 2 is 'Transit at inter-med. exch. ind.', and bit 1 is empty.](aa9441a5971655a79987d70fc551b26a_img.jpg) + +| | | +|--------------------------------------------------------|-------| +| 8      7      6      5      4      3      2      1 | Octet | +| ext. | 1 | +| Broadband/
narrow-band
interworking
indicator | | +| Pass on
not
possible
ind. | | +| Discard
message
ind. | | +| Send
notifi-
cation
ind. | | +| Release
call
indi-
cator | | +| Transit
at inter-
med.
exch.
ind. | | + +Diagram of the message compatibility information field showing 8 subfields in a single octet. Bit 8 is 'ext.', bit 7 is 'Broadband/narrow-band interworking indicator', bit 6 is 'Pass on not possible ind.', bit 5 is 'Discard message ind.', bit 4 is 'Send notification ind.', bit 3 is 'Release call indicator', bit 2 is 'Transit at inter-med. exch. ind.', and bit 1 is empty. + +**Figure 4/Q.2763 – Message compatibility information field** + +The following codes are used in the subfields of the message compatibility information field: + +- a) *Extension indicator (ext.)* + 0 Octet continues through the next octet (e.g. octet 1 to 1a). + 1 Last octet. +- b) *Broadband/narrow-band interworking indicator (octet 1)* + 00 Pass on. + 01 Discard message. + 10 Release call. + 11 Reserved, assume "00". + +- c) *Pass on not possible indicator (octet 1)* + - 0 Release call. + - 1 Discard information. +- d) *Discard message indicator (octet 1)* + - 0 Do not discard message (pass on) (see Note 1). + - 1 Discard message. + +NOTE 1 – If "pass on" is set (discard message indicator = 0) but not possible, then the send notification indicator and the pass on not possible indicator are checked. + +- e) *Send notification indicator (octet 1)* (see Note 2) + - 0 Do not send notification. + - 1 Send notification. + +NOTE 2 – Notification by Confusion message. + +- f) *Release call indicator (octet 1)* + - 0 Do not release call. + - 1 Release call. +- g) *Transit at intermediate exchange indicator (octet 1)* + - 0 Transit interpretation. + - 1 End node interpretation. + +### 6.5 Coding of the parameter compatibility information + +The format of the parameter compatibility information subfield is shown in Figure 5. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------|--------------------------------|------------------------|----------------------|------------------------|-------------------|------------------------------------|----------------------------------------------|--------| +| ext.
0 | Pass on not possible indicator | Discard parameter ind. | Discard message ind. | Send notification ind. | Release call ind. | Transit at intermediate exch. ind. | | 1 | +| ext.
1 | Spare | | | | | | Broadband/narrow-band interworking indicator | 1a | + +**Figure 5/Q.2763 – Parameter compatibility information subfield** + +The following codes are used in the parameter compatibility information subfield: + +- a) *Extension indicator (ext.)* + - 0 Octet continues through the next octet (e.g. octet 1 to 1a). + - 1 Last octet. +- b) *Pass on not possible indicator (octet 1)* + - 00 Release call. + - 01 Discard message. + - 10 Discard parameter. + - 11 Reserved, assume "00". + +- c) *Discard parameter indicator (octet 1)* + 0 Do not discard parameter (pass on) (see Note 1). + 1 Discard parameter. + NOTE 1 – If "pass on" is set (discard parameter indicator = 0) but not possible, then the send notification indicator and the pass on not possible indicator are checked. +- d) *Discard message indicator (octet 1)* + 0 Do not discard message (pass on) (see Note 2). + 1 Discard message. + NOTE 2 – If "pass on" is set (discard message indicator = 0) but not possible, then the send notification indicator and the pass on not possible indicator are checked. +- e) *Send notification indicator (octet 1)* (see Note 3) + 0 Do not send notification. + 1 Send notification. + NOTE 3 – Notification by Confusion or Release Complete message. +- f) *Release call indicator (octet 1)* + 0 Do not release call. + 1 Release call. +- g) *Transit at intermediate exchange indicator (octet 1)* + 0 Transit interpretation. + 1 End node interpretation. +- h) *Broadband/narrow-band interworking indicator (octet 1a)* + 00 Pass on. + 01 Discard message. + 10 Release call. + 11 Discard parameter. + +## 7 B-ISDN User Part parameters + +### 7.1 Parameter names + +The parameter name codes are given in Table 2 together with references to the subclauses in which they are described. + +### Parameter descriptions + +### 7.2 AAL parameters + +The format of the AAL parameters parameter field is shown in Figure 6. + +![](e636d7ccca0ad14c6b95201404324823_img.jpg) + +| | | | | | | | | | | +|--|-------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| | ext.
1 | Coding standard | | Reserved | | | | | 1 | +| | Further contents as in Rec. Q.2931
starting with octet 5 | | | | | | | | 2 | + +Figure 6/Q.2763 – AAL parameters parameter field + +The codes to be used in the subfields of the AAL parameters parameter field are defined in the AAL parameters information element in Recommendation ITU-T Q.2931 and in Amendment 2 to Q.2931. + +Coding of the AAL parameters parameter field for Frame Relay is as defined in ITU-T Recommendation Q.2933 with an additional octet and will include selection of AAL Type 5, indication of Forward and Backward Maximum CPCS-SDU size, and selection of Frame Relay SSCS. + +### 7.3 AAL prime parameters + +The format of the AAL prime parameters parameter field is shown in Figure 7. + +![](a3472689858b068ef469213682965325_img.jpg) + +| | | | | | | | | | +|--------------------------|---|---|------------------|----------|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Spare | | | Repeat indicator | Priority | | | | 1 | +| AAL information elements | | | | | | | | 2 | +| | | | | | | | | : | +| | | | | | | | | n | + +Figure 7/Q.2763 – AAL prime parameters field + +The following codes are used in the subfields of the AAL prime parameter field: + +#### a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated. +- 1 Information element repeated. + +#### b) *Priority (octet 1)* + +- 0000 No prioritized order. + - 0001 Prioritized list for selecting one possibility: ascending order. + - 0010 Prioritized list for selecting one possibility: descending order. + - 0011 + - to + - 1111 +- } Reserved. + +#### c) *AAL information element (octets 2 to n)* + +This field contains the AAL information element received from DSS2, which is assigned with the lowest order of priority. The format of the AAL information elements is the same as specified in ITU-T Recommendation Q.2931 and in Amendment 2 of Q.2931. + +### 7.4 Access delivery information + +The format of the access delivery information parameter field is shown in Figure 8. + +![](a7835229df7a34816e1d35b5bbbc8c9e_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|----------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | Access delivery ind. | 1 | + +Figure 8/Q.2763 – Access delivery information parameter field + +The following codes are used in the subfields of the access delivery information parameter field: + +- a) *Access delivery indicator* +- 0 Setup message generated. + - 1 No setup message generated. + +### 7.5 Additional ATM cell rate + +The format of the additional ATM cell rate parameter field is shown in Figure 9. + +![](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|------------------------------|---|---|---|---|---|---|---|--------| +| Cell rate identifier | | | | | | | | a | +| Cell rate/Maximum burst size | | | | | | | | a + 1 | +| | | | | | | | | a + 2 | +| | | | | | | | | a + 3 | +| Cell rate identifier | | | | | | | | : | +| Cell rate/Maximum burst size | | | | | | | | | +| | | | | | | | | | +| Cell rate identifier | | | | | | | | I | +| Cell rate/Maximum burst size | | | | | | | | I + 1 | +| | | | | | | | | I + 2 | +| | | | | | | | | I + 3 | + +**Figure 9/Q.2763 – Additional ATM cell rate parameter field** + +NOTE 1 – Octet groups (or subfields) may be included in any order within the parameter. This general encoding rule applies to all B-ISUP Recommendations whenever octet groups (or subfields) are identified or tagged by a one octet identifier within a parameter. + +NOTE 2 – Octet groups (or subfields) tagged by a one octet identifier are not extensible. Although some older B-ISUP Recommendations may include octet groups (or subfields) tagged by a one octet field with bit 8 shown as an extension bit, no requirements for their future extension is foreseen. Implementations may therefore safely handle such a bit 8 of an identifier octet as an integral part of the octet group identifier. To ensure backward compatibility, subfield identifier shall not be defined with bit 8 set to 0. + +The following codes are used in the subfields of the additional ATM cell rate parameter field: + +- a) *Cell rate identifier* + +See Recommendations Q.2961.1 to Q.2961.6 for the coding. The codes given here are just for information. + +- 1000 1000 Forward sustainable cell rate for cell loss priority = 0 +- 1000 1001 Backward sustainable cell rate for cell loss priority = 0 +- 1001 0000 Forward sustainable cell rate for cell loss priority = 0 + 1 +- 1001 0001 Backward sustainable cell rate for cell loss priority = 0 + 1 +- 1010 0000 Forward maximum burst size for cell loss priority = 0 +- 1010 0001 Backward maximum burst size for cell loss priority = 0 +- 1011 0000 Forward maximum burst size for cell loss priority = 0 + 1 +- 1011 0001 Backward maximum burst size for cell loss priority = 0 + 1 +- 1001 0010 Forward ABR minimum cell rate for cell loss priority = 0 + 1 +- 1001 0011 Backward ABR minimum cell rate for cell loss priority = 0 + 1 +- 1100 0000 Forward resource management peak cell rate + +1100 0001 Backward resource management peak cell rate +1011 1110 Reserved (used for best effort indication) +1011 1111 Reserved (used for traffic management options in ITU-T Recommendation Q.2961) + +Other codepoints are reserved. + +b) *Cell rate* +The number of cells per second is coded in 3-octet binary representation. Bit 8 of the first octet (e.g. a + 1) is the most significant and bit 1 of the 3rd octet (e.g. a + 3) is the least significant respectively. + +c) *Maximum burst size* +The maximum burst size in cells is coded in 3-octet binary representation. Bit 8 of the first octet (e.g. a + 1) is the most significant and bit 1 of the third octet (e.g. a + 3) is the least significant respectively. + +NOTE 3 – The CLP bit of the resource management cell is always set to 0. + +NOTE 4 – The forward/backward RM PCRs are not included in the forward/backward PCR values specified in the ATM cell rate parameter. + +NOTE 5 – For details on the use of cell loss priority, see ITU-T Recommendation I.371. + +### 7.6 Additional calling party number + +The format of the additional calling party number parameter field is shown in Figure 10. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------|-----------------------------|---|---|---------------------------|---|---------------------|---|--------| +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Spare | Numbering plan indicator | | | Presentation
indicator | | Screening indicator | | 2 | +| 2nd address signal | | | | 1st address signal | | | | 3 | +| | | | | | | | | | +| Filler (if necessary) | | | | Nth address signal | | | | n | + +**Figure 10/Q.2763 – Additional calling party number parameter field** + +The following codes are used in the subfields of the additional calling party number parameter field: + +a) *Odd/even indicator* + +- 0 Even number of address signals. +- 1 Odd number of address signals. + +b) *Nature of address indicator* + +- 0000000 Spare. +- 0000001 Subscriber number. +- 0000010 Unknown. +- 0000011 National (significant) number. +- 0000100 International number. + +**ITU-T Q.2763 (12/1999)**      15 + +0000101 +to +1101111 } Spare. + +1110000 +to +1111110 } Reserved for national use. + +1111111 Spare. + +#### c) *Numbering plan indicator* + +000 Spare. + +001 ISDN (telephony) numbering plan (see Recommendation E.164). + +010 Spare. + +011 Reserved for national use. + +100 Reserved for national use. + +101 Private numbering plan. + +110 Reserved for national use. + +111 Spare. + +#### d) *Presentation indicator* + +00 Presentation allowed. + +01 Presentation restricted. + +10 Address not available. + +11 Spare. + +#### e) *Screening indicator* + +00 User provided, not verified. + +01 User provided, verified and passed. + +10 User provided, verified and failed. + +11 Network provided. + +#### f) *Address signal* + +0000 Digit 0. + +0001 Digit 1. + +0010 Digit 2. + +0011 Digit 3. + +0100 Digit 4. + +0101 Digit 5. + +0110 Digit 6. + +0111 Digit 7. + +1000 Digit 8. + +1001 Digit 9. + +1010 +to +1111 } Spare. + +g) *Filler* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### 7.7 Additional connected number + +The format of the additional connected number parameter field corresponds to the format for the additional calling party parameter. + +The encoding is identical to the encoding of the additional calling party number parameter field. + +### 7.8 AESA for additional calling party + +The format for the AESA for calling party parameter field is shown in Figure 11. + +![](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Further contents as in Q.2931 calling party number IE starting with octet 5 | | | | | | | | 2 | + +**Figure 11/Q.2763 – AESA for additional calling party parameter field** + +The codes to be used in the subfields of the AESA for additional calling party parameter field are defined in the calling party number information element in ITU-T Recommendation Q.2931. + +### 7.9 AESA for additional connected party + +The format for the AESA for connected party parameter field is shown in Figure 12. + +![](b6b53a74ad203c01b81e5427e9d6a898_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Further contents as in Q.2931 calling party number IE starting with octet 5 | | | | | | | | 2 | + +**Figure 12/Q.2763 – AESA for additional connected party parameter field** + +The codes to be used in the subfields of the AESA for additional connected party parameter field are defined in the calling party number information element in ITU-T Recommendation Q.2931. + +### 7.10 AESA for called party + +The format of the AESA for called party parameter field is shown in Figure 13. + +![](8facb5a02c64e245808bafc005e65032_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Further contents as in Q.2931 calling party number IE starting with octet 5 | | | | | | | | 2 | + +**Figure 13/Q.2763 – AESA for called party parameter field** + +The codes to be used in the subfields of the AESA for called party parameter field are defined in the called party number information in ITU-T Recommendation Q.2931. + +### 7.11 AESA for calling party + +The format for the AESA for calling party parameter field is shown in Figure 14. + +![](5a1abd59a95fa47ae192807de151e9eb_img.jpg) + +| | | | | | | | | | | +|-----------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Coding standard | | Reserved | | | | | | 1 | +| Further contents as in Q.2931 calling party number IE starting with octet 5 | | | | | | | | | 2 | + +**Figure 14/Q.2763 – AESA for calling party parameter field** + +The codes to be used in the subfields of the AESA for calling party parameter field are defined in the calling party number information element in ITU-T Recommendation Q.2931. The values "user provided, not screened", and "user provided, verified and failed" of the screening indicator are not applicable. + +### 7.12 AESA for connected party + +The format for the AESA for connected party parameter field is shown in Figure 15. + +![](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +| | | | | | | | | | | +|-----------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Coding standard | | Reserved | | | | | | 1 | +| Further contents as in Q.2931 calling party number IE starting with octet 5 | | | | | | | | | 2 | + +**Figure 15/Q.2763 – AESA for connected party parameter field** + +The codes to be used in the subfields of the AESA for connected party parameter field are defined in the calling party number information element in ITU-T Recommendation Q.2931. The values "user provided, not screened", and "user provided, verified and failed" of the screening indicator are not applicable. + +### 7.13 Alternative ATM cell rate + +The format for the alternative ATM cell rate parameter field corresponds to the format of the additional ATM cell rate parameter. + +The following codes are used in the subfields of the alternative ATM cell rate parameter field: + +#### a) *Cell rate identifier (octet 1)* + +See ITU-T Recommendations Q.2931 and Q.2962 for the coding. The codes given here are just for information. + +- 10000010 Forward peak cell rate for cell loss priority = 0 +- 10000011 Backward peak cell rate for cell loss priority = 0 +- 10000100 Forward peak cell rate for cell loss priority = 0 + 1 +- 10000101 Backward peak cell rate for cell loss priority = 0 + 1 +- 10001000 Forward sustainable cell rate for cell loss priority = 0 +- 10001001 Backward sustainable cell rate for cell loss priority = 0 +- 10010000 Forward sustainable cell rate for cell loss priority = 0 + 1 +- 10010001 Backward sustainable cell rate for cell loss priority = 0 + 1 + +- 10100000 Forward maximum burst size for cell loss priority = 0 +- 10100001 Backward maximum burst size for cell loss priority = 0 +- 10110000 Forward maximum burst size for cell loss priority = 0 + 1 +- 10110001 Backward maximum burst size for cell loss priority = 0 + 1 +- 10111111 Reserved (used for traffic management options in ITU-T Recommendation Q.2961) + +Other codepoints are reserved. + +- b) *Cell rate* +The encoding is identical to the encoding of the additional ATM cell rate parameter field. +- c) *Maximum burst size* +The encoding is identical to the encoding of the additional ATM cell rate parameter field. + +### **7.14 Application generated identifier** + +The format of the application generated identifier is shown in Figure 16. + +![Diagram of the application generated identifier parameter field structure. It shows a header with 8 bits: Spare (bits 8-6), Repeat indicator (bit 5), and Priority (bits 4-1). Below the header are one or more instances of the generic identifier transport information element, starting with octet 1 and continuing through octet n.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +| | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------|---|---|------------------|----------|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Spare | | | Repeat indicator | Priority | | | | 1 | +| One or more instances of the generic identifier transport information element defined in ITU-T Q.2941.1 starting with octet 1 | | | | | | | | 2 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | n | + +Diagram of the application generated identifier parameter field structure. It shows a header with 8 bits: Spare (bits 8-6), Repeat indicator (bit 5), and Priority (bits 4-1). Below the header are one or more instances of the generic identifier transport information element, starting with octet 1 and continuing through octet n. + +**Figure 16/Q.2763 – Application generated identifier parameter field** + +The following codes are used in the subfields of the application generated identifier parameter field. + +- a) *Repeat indicator (octet 1)* + - 0 Information element not repeated. + - 1 Information element repeated. +- b) *Priority (octet 1)* + - 0000 No prioritized order. + - 0001 Prioritized list for selecting one possibility: ascending order. + - 0010 Prioritized list for selecting one possibility: descending order. + - 0011 to 1111 Reserved. + +### 7.15 Application transport + +The format for the application transport parameter field is shown in Figure 17. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|------|---------------------------------------------------------|---|---|---|---|---|---|--------| +| ext. | Application Context Identifier | | | | | | | 1 | +| ext. | Further contents as in Rec. Q.763 starting with octet 2 | | | | | | | 2 | + +**Figure 17/Q.2763 – Application transport parameter field** + +### 7.16 ATC setup parameters + +The format of the ATC setup parameters parameter field is shown in Figure 18. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|--------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Coding as in Rec. Q.2961.3 starting with octet 5 | | | | | | | | 2 | + +**Figure 18/Q.2763 – ATC setup parameters parameter field** + +### 7.17 ATM cell rate + +The format of the ATM cell rate parameter field corresponds to the format of the additional ATM cell rate parameter. + +The following codes are used in the subfields of the additional ATM cell rate parameter field: + +#### a) *Cell rate identifier* + +See ITU-T Recommendation Q.2931 for the encoding. The codes given here are just for information. + +- 10000010 Forward peak cell rate for Cell Loss Priority = 0. +- 10000011 Backward peak cell rate for Cell Loss Priority = 0. +- 10000100 Forward peak cell rate for Cell Loss Priority = 0 + 1. +- 10000101 Backward peak cell rate for Cell Loss Priority = 0 + 1. + +#### b) *Cell rate* + +The encoding is identical to the encoding of the additional ATM cell rate parameter field. + +### 7.18 Automatic congestion level + +The format of the automatic congestion level parameter field is shown in Figure 19. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|----------------------------|---|---|---|---|---|---|---|-------| +| Automatic congestion level | | | | | | | | 1 | + +**Figure 19/Q.2763 – Automatic congestion level parameter field** + +The following codes are used in the automatic congestion level parameter field: + +- a) *Automatic congestion level* +- 00000000 Spare. + - 00000001 Congestion level 1 exceeded. + - 00000010 Congestion level 2 exceeded. + - 00000011 to 11111111 Spare. + +### **7.19 Automatic re-routing (crankback)** + +The format of the automatic re-routing parameter field is shown in Figure 20. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-------------|--------------------|---|---|---|---|----------------------|---|--------| +| ext.
0/1 | Spare | | | | | Re-routing indicator | | 1 | +| ext.
1 | Re-routing counter | | | | | | | 1a | + +**Figure 20/Q.2763 – Automatic re-routing parameter field** + +The following codes are used in the subfields of the automatic re-routing parameter field: + +- a) *Extension indicator (ext.)* +- 0 Octet continues through the next octet (e.g. octet 1 to 1a). + - 1 Last octet. +- b) *Re-routing inhibit indicator* +- 00 No indication. + - 01 Do not crankback. + - 10 Do crankback. + - 11 Spare. +- c) *Re-routing counter* +- Number of automatic re-routing attempts performed on that call/connection expressed as a binary number between 1 and 127. +- 000000 Not used. + - 000001 1st crankback attempt. + - 000010 to 111111 2nd crankback attempt. 127th crankback attempt. + +### **7.20 Backward GVNS** + +The format of the backward GVNS parameter field is shown in Figure 21. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|-----------|-------|---|---|---|---|------------------------------|---|-------| +| ext.
1 | Spare | | | | | Terminating access indicator | | 1 | + +**Figure 21/Q.2763 – Backward GVNS parameter field** + +The following codes are used in the backward GVNS parameter field: + +- bits 1-2    Terminating access indicator. + - 0 0    No information. + - 0 1    Dedicated terminating access. + - 1 0    Switched terminating access. + - 1 1    Spare. +- bits 3-7    Spare. +- bit 8    Extension indicator. + - 0    Information continues through the next octet. + - 1    Last octet. + +### 7.21    Backward narrow-band interworking indicator + +The format of the backward narrow-band interworking indicator parameter field is shown in Figure 22. + +![](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|------------------------|---------------------------|---------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | ISDN
access
ind. | ISDN
user part
ind. | Inter-
working
ind. | 1 | + +**Figure 22/Q.2763 – Backward narrow-band interworking indicator parameter field** + +The following codes are used in the subfields of the backward narrow-band interworking indicator parameter field: + +- a)    *ISDN access indicator* + - 0    Terminating access non-ISDN. + - 1    Terminating access ISDN. +- b)    *ISDN user part indicator* + - 0    ISDN user part not used all the way. + - 1    ISDN user part used all the way. +- c)    *Interworking indicator* + - 0    No interworking encountered (No. 7 signalling all the way). + - 1    Interworking encountered. + +### 7.22    Broadband bearer capability + +The format of the broadband bearer capability parameter field is shown in Figure 23. + +![](17a1ba23b641c01871b08f0a4f08ef48_img.jpg) + +| | | | | | | | | | +|----------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Further contents as in Rec. Q.2931 starting with octet 5 | | | | | | | | 2 | + +**Figure 23/Q.2763 – Broadband bearer capability parameter field** + +The codes to be used in the subfields of the broadband bearer capability parameter field are defined in the broadband bearer capability information element in 4.5.7/Q.2931 and extended as indicated in ITU-T Recommendation Q.2961.2 to enable the explicit indication of ATM transfer capability. + +The coding of subfields for ABR services is given in ITU-T Recommendation Q.2961.3. The code of subfields for ABT ATC is given in ITU-T Recommendation Q.2961.4. The additional codepoints for SBR2 and SBR3 ATM transfer capabilities are specified in ITU-T Recommendation Q.2961.6. + +The coding of subfields for Frame Relay call/connections is given in ITU-T Recommendation Q.2933. + +### 7.23 Broadband high layer information + +The format of the broadband high layer information parameter field is shown in Figure 24. + +![](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +| | | | | | | | | | +|----------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Further contents as in Rec. Q.2931 starting with octet 5 | | | | | | | | 2 | + +Figure 24/Q.2763 – Broadband high layer information parameter field + +The codes to be used in the subfields of the broadband high layer information parameter field are defined in the broadband high layer information elements in ITU-T Recommendation Q.2931. + +### 7.24 Broadband low layer information + +The format of the broadband low layer information parameter field is shown in Figure 25. + +![](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +| | | | | | | | | | +|------------------------------------------------------|---|---|---------------------|----------|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Spare | | | Repeat
indicator | Priority | | | | 1 | +| Broadband low layer information information elements | | | | | | | | 2 | +| | | | | | | | | : | +| | | | | | | | | n | + +Figure 25/Q.2763 – Broadband low layer information parameter field + +The following codes are used in the subfields of the broadband low layer information parameter field. + +#### a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated. +- 1 Information element repeated. + +#### b) *Priority (octet 1)* + +- 0000 No prioritized order. +- 0001 Prioritized list for selecting one possibility: ascending order. +- 0010 Prioritized list for selecting one possibility: descending order. +- 0011 to 1111 Reserved. + +#### c) *Broadband low layer information information elements (octets 2 to n)* + +This field contains all broadband low layer information elements as received from DSS2. The format of the broadband low layer information elements is the same as specified in ITU-T Recommendation Q.2931. The order of the information elements is not changed. + +### 7.25 Call diversion information + +The format of the call diversion information parameter field is shown in Figure 26. + +![](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +| | | | | | | | | | +|-------|--------------------|---|---|---|-----------------------------------|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | Redirection reason | | | | Notification subscription options | | | 1 | + +**Figure 26/Q.2763 – Call diversion information parameter field** + +The following codes are used in the call diversion information parameter field: + +#### a) *Redirection reason* + +| | | +|--------------------|----------------------------------| +| 0000 | Unknown. | +| 0001 | User busy. | +| 0010 | No reply. | +| 0011 | Unconditional. | +| 0100 | Deflection during alerting. | +| 0101 | Deflection immediate response. | +| 0110 | Mobile subscriber not reachable. | +| 0011
to
1111 | Spare. | + +#### b) *Notification subscription options* + +| | | +|------------------|--------------------------------------------------| +| 000 | Unknown. | +| 001 | Presentation not allowed. | +| 010 | Presentation allowed with redirection number. | +| 011 | Presentation allowed without redirection number. | +| 100
to
111 | Spare. | + +### 7.26 Call diversion may occur + +The format of the call diversion may occur parameter field is shown in Figure 27. + +![](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|-------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | Call diversion may occur ind. | 1 | + +**Figure 27/Q.2763 – Call diversion may occur parameter field** + +The following codes are used in the subfields of the call diversion may occur parameter field: + +a) *Call diversion may occur indicator* + +- 0 No indication. +- 1 Call diversion may occur. + +### 7.27 Call diversion treatment indicators + +The format of the call diversion treatment indicators parameter field is shown in Figure 28. + +![](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +| | | | | | | | | +|-----------|-------|---|---|---|---|-------------------------------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| ext.
1 | Spare | | | | | Call to be diverted indicator | | + +**Figure 28/Q.2763 – Call diversion treatment indicators parameter field** + +The following codes are used in the call diversion treatment parameter field: + +- bits 1-2 Call to be diverted indicator. + - 0 0 No indication. + - 0 1 Call diversion allowed. + - 1 0 Call diversion not allowed. + - 1 1 Spare. +- bits 3-7 Spare. +- bit 8 Extension indicator. + - 0 Information continues through the next octet. + - 1 Last octet. + +### 7.28 Call history information + +The format of the call history information parameter field is shown in Figure 29. + +![](e4a14961bdc9882e296b25f7ae5f9760_img.jpg) + +| | | | | | | | | | +|-------------|---|---|---|---|---|---|--------|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Delay value | | | | | | | 1
2 | | + +**Figure 29/Q.2763 – Call history information parameter field** + +The following codes are used in the subfields of the call history information parameter field: + +#### a) *Delay value (octets 1 to 2)* + +The delay value expresses in pure binary representation the propagation delay value of a call in ms. Bit 8 of octet 1 is the most significant and bit 1 of octet 2 is the least significant respectively. + +### 7.29 Call offering treatment indicators + +The format of the call offering treatment indicators parameter field is shown in Figure 30. + +![](a4b963a07cc368283154762c4b156fe7_img.jpg) + +| | | | | | | | | +|-----------|-------|---|---|---|---|---------------------------------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| ext.
1 | Spare | | | | | Call to be offered
indicator | | + +**Figure 30/Q.2763 – Call offering treatment indicators parameters field** + +The following codes are used in the call offering treatment parameter field: + +bits 1-2 Call to be offered indicator. + +0 0 No indication. + +0 1 Call offering not allowed. + +1 0 Call offering allowed. + +1 1 Spare. + +bits 3-7 Spare. + +bit 8 Extension indicator. + +0 Information continues through the next octet. + +1 Last octet. + +### 7.30 Call transfer number + +The format of the call transfer number parameter field is shown in Figure 31. + +![](8093331dcf2cec58ddacf15bc3622b2e_img.jpg) + +| | | | | | | | | | +|--------------------------|-----------------------------|---|-------------------------------------------------|---|---------------------|---|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Spare | Numbering
plan ind. | | Address
presentation
restricted indicator | | Screening indicator | | | 2 | +| 2nd address
signal | | | 1st address
signal | | | | | 3 | +| : | | | | | | | | : | +| Filler
(if necessary) | | | N th address
signal | | | | | n | + +**Figure 31/Q.2763 – Call transfer number parameter field** + +The following codes are used in the subfields of the call transfer number parameter field: + +#### a) *Odd/Even indicator* + +0 Even number of address signals. + +1 Odd number of address signals. + +- b) *Nature of address indicator* +- | | | +|---------|-----------------------------------------------| +| 0000000 | Spare. | +| 0000001 | Subscriber number (national use). | +| 0000010 | Unknown (national use). | +| 0000011 | National (significant) number (national use). | +| 0000100 | International number. | +| 0000101 | Spare. | +| to | | +| 1101111 | | +| 1110000 | Reserved for national use. | +| to | | +| 1111110 | | +| 1111111 | Spare. | +- c) *Numbering plan indicator* +- | | | +|-----|------------------------------------------------------------------| +| 000 | Spare. | +| 001 | ISDN (Telephony) numbering plan (ITU-T Recommendation E.164). | +| 010 | Spare. | +| 011 | Data numbering plan (ITU-T Recommendation X.121) (national use). | +| 100 | Telex numbering plan (ITU-T Recommendation F.69) (national use). | +| 101 | Private numbering plan (national use). | +| 100 | Reserved for national use. | +| 110 | Spare. | +- d) *Address presentation restricted indicator* +- | | | +|----|--------------------------| +| 00 | Presentation allowed. | +| 01 | Presentation restricted. | +| 10 | Spare. | +| 11 | Spare. | +- e) *Screening indicator* +- | | | +|----|-------------------------------------| +| 00 | User provided, not verified | +| 01 | User provided, verified and passed. | +| 10 | User provided, verified and failed. | +| 11 | Network provided. | +- f) *Address signal* +- | | | +|------|----------| +| 0000 | Digit 0. | +| 0001 | Digit 1. | +| 0010 | Digit 2. | +| 0011 | Digit 3. | +| 0100 | Digit 4. | +| 0101 | Digit 5. | +| 0110 | Digit 6. | + +| | | +|--------------------|----------| +| 0111 | Digit 7. | +| 1000 | Digit 8. | +| 1001 | Digit 9. | +| 1010 | Spare. | +| 1011 | Code 11. | +| 1101 | Code 12. | +| 1101
to
1111 | Spare. | + +The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit fields. + +g) *Filler* + +In case of an odd number of digits, the filler code 0000 is inserted after the last digit. + +### 7.31 Call transfer reference + +The format of the call transfer reference parameter is shown in Figure 32. + +![](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Call transfer identity | | | | | | | | 1 | + +Figure 32/Q.2763 – Call transfer reference parameter field + +The call transfer identity is a pure binary representation of the integer (0 to 255) assigned unambiguously to the particular ECT supplementary service invocation (see clause 7/Q.732). + +### 7.32 Called IN number + +The format of the called IN number parameter corresponds to the format of the original called party number parameter. + +### 7.33 Called party number + +The format of the called party number parameter field is shown in Figure 33. + +![](dec689324b075952626a86da862b9549_img.jpg) + +| | | | | | | | | | +|---------------------------------|-----------------------------|---|---|--------------------|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Internal
network
no. ind. | Numbering plan indicator | | | Spare | | | | 2 | +| 2nd address signal | | | | 1st address signal | | | | 3 | +| : | | | | : | | | | : | +| Filler (if necessary) | | | | Nth address signal | | | | n | + +Figure 33/Q.2763 – Called party number parameter field + +The following codes are used in the subfields of the called party number parameter field: + +- a) *Odd/Even indicator (octet 1)* + +| | | +|---|---------------------------------| +| 0 | Even number of address signals. | +| 1 | Odd number of address signals. | +- b) *Nature of address indicator (octet 1)* + +| | | +|--------------------------|-----------------------------------| +| 0000000 | Spare. | +| 0000001 | Subscriber number (national use). | +| 0000010 | Unknown (national use). | +| 0000011 | National (significant) number. | +| 0000100 | International number. | +| 0000101
to
1101111 | Spare. | +| 1110000
to
1111110 | Reserved for national use. | +| 1111111 | Spare. | +- c) *Internal network number indicator (octet 2)* + +| | | +|---|-------------------------------------------------| +| 0 | Routing to internal network number allowed. | +| 1 | Routing to internal network number not allowed. | +- d) *Numbering plan indicator (octet 2)* + +| | | +|-----|-------------------------------------------------------------------| +| 000 | Spare. | +| 001 | ISDN (telephony) numbering plan (see ITU-T Recommendation E.164). | +| 010 | Spare. | +| 011 | Reserved for national use. | +| 100 | Reserved for national use. | +| 101 | Reserved for national use. | +| 110 | Reserved for national use. | +| 111 | Spare. | +- e) *Address signal (octets 3 to n)* + +| | | +|------|----------| +| 0000 | Digit 0. | +| 0001 | Digit 1. | +| 0010 | Digit 2. | +| 0011 | Digit 3. | +| 0100 | Digit 4. | +| 0101 | Digit 5. | +| 0110 | Digit 6. | +| 0111 | Digit 7. | +| 1000 | Digit 8. | +| 1001 | Digit 9. | + +| | | +|------|----------| +| 1010 | Spare. | +| 1011 | Code 11. | +| 1100 | Code 12. | +| 1101 | Spare. | +| 1110 | Spare. | +| 1111 | ST. | + +The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit fields. + +#### f) *Filler (octet n)* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### **7.34 Called party sub-address** + +The format of the called party sub-address parameter field is shown in Figure 34. + +![](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +| | | | | | | | | | | +|----------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Coding standard | | Reserved | | | | | | 1 | +| Further contents as in Rec. Q.2931 starting with octet 5 | | | | | | | | | 2 | + +**Figure 34/Q.2763 – Called party sub-address parameter field** + +The codes to be used in the subfields of the called party sub-address parameter field are defined in the called party sub-address information element in ITU-T Recommendation Q.2931. + +### **7.35 Called party's indicators** + +The format of the called party's indicators parameter field is shown in Figure 35. + +![](187bba66c887c745c512add37a577c5e_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|--------------------------------------|---|---|-------------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | Called party's
category indicator | | | Called
party's
status
ind. | 1 | + +**Figure 35/Q.2763 – Called party's indicators parameter field** + +The following codes are used in the subfields of the called party's indicators parameter field: + +#### a) *Called party's category indicator* + +| | | +|----|----------------------| +| 00 | No indication. | +| 01 | Ordinary subscriber. | +| 10 | Payphone. | +| 11 | Spare. | + +#### b) *Called party's status indicator* + +| | | +|---|----------------| +| 0 | No indication. | +| 1 | Alerting. | + +### 7.36 Calling party number + +The format of the calling party number parameter field is shown in Figure 36. + +![](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------------------|-----------------------------|---|---|--------------------------------------|---|---------------------|---|----------| +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Calling party no. incomplete ind. | Numbering plan indicator | | | Address presentation restricted ind. | | Screening indicator | | 2 | +| 2nd address signal | | | | 1st address signal | | | | 3 | +| | | | | | | | | ⋮ | +| Filler (if necessary) | | | | N th address signal | | | | n | + +**Figure 36/Q.2763 – Calling party number parameter field** + +NOTE 1 – When the address presentation restricted indicator indicates address not available, octets 3 to *n* are omitted. + +The following codes are used in the calling party number parameter field: + +- a) *Odd/Even indicator (octet 1)* + +| | | +|---|---------------------------------| +| 0 | Even number of address signals. | +| 1 | Odd number of address signals. | + +- b) *Nature of address indicator (octet 1)* + +| | | +|--------------------------|-----------------------------------------------| +| 0000000 | Spare. | +| 0000001 | Subscriber number (national use). | +| 0000010 | Unknown (national use). | +| 0000011 | National (significant) number (national use). | +| 0000100 | International number. | +| 0000101
to
1101111 | Spare. | +| 1110000
to
1111110 | Reserved for national use. | +| 1111111 | Spare. | + +- c) *Calling party number incomplete indicator (octet 2) (national use)* + +| | | +|---|----------------------------| +| 0 | Complete. | +| 2 | Incomplete (national use). | + +#### d) *Numbering plan indicator (octet 2)* + +| | | +|-----|-------------------------------------------------------------------| +| 000 | Spare. | +| 001 | ISDN (telephony) numbering plan (see ITU-T Recommendation E.164). | +| 010 | Spare. | +| 011 | Reserved for national use. | +| 100 | Reserved for national use. | +| 101 | Reserved for national use. | +| 111 | Spare. | + +#### e) *Address presentation restricted indicator (octet 2)* + +| | | +|----|----------------------------------------------------| +| 00 | Presentation allowed. | +| 01 | Presentation restricted | +| 10 | Address not available (see Note 2) (national use). | +| 11 | Spare | + +NOTE 2 – When the address is unavailable, the subfields in items a), b), c) and d) are coded with 0's. + +#### f) *Screening indicator (octet 2)* + +| | | +|----|-------------------------------------| +| 00 | Reserved (see Note 3). | +| 01 | User provided, verified and passed. | +| 10 | Reserved (see Note 3). | +| 11 | Network provided. | + +NOTE 3 – Code 00 and 10 are reserved for "user provided, not verified" and "user provided, verified and failed" respectively. Codes 00 and 10 are for national use. + +#### g) *Address signal (octets 3 to n)* + +| | | +|------|----------| +| 0000 | Digit 0. | +| 0001 | Digit 1. | +| 0010 | Digit 2. | +| 0011 | Digit 3. | +| 0100 | Digit 4. | +| 0101 | Digit 5. | +| 0110 | Digit 6. | +| 0111 | Digit 7. | +| 1000 | Digit 8. | +| 1001 | Digit 9. | +| 1010 | Spare. | +| 1011 | Code 11. | +| 1100 | Code 12. | +| 1101 | Spare. | +| to | | +| 1111 | | + +#### h) *Filler (octet n)* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### 7.37 Calling party sub-address + +The format of the calling party sub-address parameter field corresponds to the format shown for the called party sub-address parameter. + +The codes to be used in the subfields of the calling party sub-address parameter field are defined in the calling party sub-address information element in ITU-T Recommendation Q.2931. + +### 7.38 Calling party's category + +The format of the calling party's category parameter field is shown in Figure 37. + +![Diagram of Figure 37 showing the Calling party's category parameter field structure as a single octet with bits 8 to 1.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Calling party's category | | | | | | | | 1 | + +Diagram of Figure 37 showing the Calling party's category parameter field structure as a single octet with bits 8 to 1. + +**Figure 37/Q.2763 – Calling party's category parameter field** + +The following codes are used in the calling party's category parameter field: + +- a) *Calling party's category* +- | | | +|----------|---------------------------------------------------------------------------------------| +| 00000000 | Calling party's category unknown at this time (national use). | +| 00000001 | Operator, French language. | +| 00000010 | Operator, English language. | +| 00000011 | Operator, German language. | +| 00000100 | Operator, Russian language. | +| 00000101 | Operator, Spanish language. | +| 00000110 | Available to Administrations for selecting a particular language by mutual agreement. | +| to | | +| 00001000 | | +| 00001001 | Reserved (see ITU-T Recommendation Q.104) (see Note) (national use). | +| 00001010 | Ordinary calling subscriber. | +| 00001011 | Calling subscriber with priority. | +| 00001100 | Data call (voice band data). | +| 00001101 | Test call. | +| 00001110 | Spare. | +| 00001111 | Payphone. | +| 00010000 | Spare. | +| to | | +| 11011111 | | +| 11100000 | Reserved for national use. | +| to | | +| 11111110 | | +| 11111111 | Spare. | + +NOTE – In national networks, code 00001001 may be used to indicate that the calling party is a national operator. + +### 7.39 Cause indicators + +The encoding of the cause indicators parameter field is shown in ITU-T Recommendation Q.2610. + +### 7.40 CSS + +The format of the CSS parameter field is shown in Figure 38. + +![](838c31609fac483fa2c01c7896a2fd6d_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|---|--------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | | 1 | +| | | | | | | | | CCSS
call
indica-
tor | + +**Figure 38/Q.2763 – CSS parameter field** + +The following codes are used in the CSS parameter field: + +- bit 1        CCSS call indicator. + - 0        No indication. + - 1        CCSS call. +- bits 2-8    Spare. + +### 7.41 CDVT + +The format of the CDVT parameter field is shown in Figure 39. + +![](63a2519518616620ef0e53d98b923c05_img.jpg) + +| | | | | | | | | | | +|--------------------------------------------------|-----------------|---|----------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Coding standard | | Reserved | | | | | | 1 | +| Coding as in Rec. Q.2691.5 starting with octet 5 | | | | | | | | | 2 | + +**Figure 39/Q.2763 – CDVT parameter field** + +### 7.42 Charge indicator + +The format of the charge indicator parameter field is shown in Figure 40. + +![](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|---|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | | 1 | +| | | | | | | | | Charge
ind. | + +**Figure 40/Q.2763 – Charge indicator parameter field** + +The following codes are used in the charge indicator parameter field: + +- a)        *Charge indicator* + - 0    No charge. + - 1    Charge. + +NOTE – The interpretation of these bits depends only on the charging exchange. + +### 7.43 Charged party identification (national use) + +The format of the charged party identification parameter is national network specific. The format is similar to the format of the corresponding INAP parameter in the "FurnishChargingInformation" operation (see ITU-T Recommendation Q.1218). + +### 7.44 Closed User Group information + +The format of the Closed User Group (CUG) information parameter field is shown in Figure 41. + +![](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +| | | | | | | | | | | +|--------------|---|---|---|--------------|---|---|---|------------------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| Spare | | | | | | | | CUG
call ind. | 1 | +| 1st NI digit | | | | 2nd NI digit | | | | | 2 | +| 3rd NI digit | | | | 4th NI digit | | | | | 3 | +| Binary code | | | | | | | | | 4 | +| | | | | | | | | | 5 | + +**Figure 41/Q.2763 – Closed User Group information parameter field** + +The following codes are used in the subfields of the Closed User Group information parameter field: + +#### a) *CUG call indicator (octet 1)* + +- 0 Closed User Group call, outgoing access allowed. +- 1 Closed User Group call, outgoing access not allowed. + +#### b) *Network identity (NI) (octets 2 and 3)* + +Each digit is coded in binary coded decimal representation from 0 to 9. + +If the first digit of this field is coded 0 or 9, the TCC (Telephony Country Code) follows in the second to fourth NI digits (the most significant TCC digit is in the 2nd NI digit). If the TCC is one or two digits long, the excess digit(s) is inserted with the code for ROA or network identification, if necessary. If octet 3 is not required, it is coded all zeros. + +Coding of the first digit as 1 or 8 is excluded. + +If the first digit is not 0, 9, 1 or 8, this field contains a DNIC (Data Network Identification Code) as defined in ITU-T Recommendation X.121. + +#### c) *Binary code (octets 4 and 5)* + +A code allocated to a Closed User Group administered by a particular ISDN or data network. Bit 8 of octet 4 is the most significant and bit 1 of octet 5 is the least significant respectively. + +NOTE – Octets 2 to 5 constitute the Closed User Group interlock code. + +### 7.45 Collect call request + +The format of the collect call request parameter field is shown in Figure 42. + +![](9ce4cea40cb397e866dfe193b947f4df_img.jpg) + +| | | | | | | | | | | +|-------|---|---|---|---|---|---|---|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +| Spare | | | | | | | | CCRI | 1 | + +**Figure 42/Q.2763 – Collect call request parameter field** + +The following codes are used in the collect call request parameter field: + +| | | | +|------|-----|---------------------------------| +| bit | 1 | Collect call request indicator. | +| | 0 | No indication. | +| | 1 | Collect call requested. | +| bits | 2-8 | Spare. | + +### 7.46 Conference treatment indicators + +The format of the conference treatment indicators parameter field is shown in Figure 43. + +![](cf8bd014a50b7c69435e804f67f9617f_img.jpg) + +| | | | | | | | | | +|-----------|-------|---|---|---|---|---------------------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| ext.
1 | Spare | | | | | Conference acceptance indicator | | 1 | + +**Figure 43/Q.2763 – Conference treatment indicators parameter field** + +The following codes are used in the conference treatment parameter field: + +| | | | +|------|-----|-----------------------------------------------------------------------------| +| bits | 1-2 | Conference acceptance indicator (Note). | +| | 0 0 | No indication. | +| | 0 1 | Accept conference request. | +| | 1 0 | Reject conference request. | +| | 1 1 | Spare. | +| | | NOTE – Applicable to the conference and three-party supplementary services. | +| bits | 3-7 | Spare. | +| bit | 8 | Extension indicator. | +| | 0 | Information continues through the next octet. | +| | 1 | Last octet. | + +### 7.47 Connected line identity request + +The format of the connected line identity request parameter field is shown in Figure 44. + +![](8d8c758885b4f754ff071bf3b572ab3c_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|--------------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | Connected line identity request ind. | 1 | + +**Figure 44/Q.2763 – Connected line identity request parameter field** + +The following codes are used in the connected line identity request parameter field: + +| | | +|----|--------------------------------------------------| +| a) | Connected line identity request indicator | +| | 0 Not requested. | +| | 1 Requested. | + +### 7.48 Connected number + +The format of the connected number parameter field corresponds to the format shown in Figure 45. + +![](e8e818455bb0d1a6153299a388b94868_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|---------------------|-----------------------------|---|--------------------------------------|----------------------------|---------------------|---|---|----------| +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Spare | Numbering plan indicator | | Address presentation restricted ind. | | Screening indicator | | | 2 | +| 2nd address signal | | | | 1st address signal | | | | 3 | +| | | | | | | | | : | +| Fill (if necessary) | | | | N th address signal | | | | n | + +**Figure 45/Q.2763 – Connected number parameter field** + +NOTE 1 – When the address presentation restricted indicator indicates address not available, octets 3 to *n* are omitted, and the screening indicator is set to 11 network provided. + +The following codes are used in the subfields of the connected number parameter field: + +- a) *Odd/Even indicator (octet 1)* + - 0 Even number of address signals. + - 1 Odd number of address signals. +- b) *Nature of address indicator (octet 1)* + +See Called party number parameter for coding. +- c) *Numbering plan indicator (octet 2)* + +See Called party number parameter for coding. +- d) *Address presentation restricted indicator (octet 2)* + - 00 Presentation allowed. + - 01 Presentation restricted. + - 10 Address not available (see Note 2). + - 11 Spare. + +NOTE 2 – When the address is unavailable, the subfields in items a), b), and c) are coded with 0's. + +- e) *Screening indicator (octet 2)* + +See Calling party number parameter for coding. +- f) *Address signal (octets 2 to *n*)* + +See Calling party number parameter for coding. +- g) *Filler (octet *n*)* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### 7.49 Connected sub-address + +The format of the connected sub-address parameter field corresponds to the format shown for the called party sub-address parameter. + +The codes to be used in the subfields of the connected sub-address parameter field are defined in the connected sub-address information element in ITU-T Recommendation Q.2951. + +### 7.50 Connection element identifier + +The format of the connection element identifier parameter field is shown in Figure 46. + +![](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-------------------------------------------|---|---|---|---|---|---|---|--------| +| Virtual Path Connection Identifier (VPCI) | | | | | | | | 1 | +| Virtual Channel Identifier (VCI) | | | | | | | | 2 | +| | | | | | | | | 3 | +| | | | | | | | | 4 | + +**Figure 46/Q.2763 – Connection element identifier parameter field** + +The following codes are used in the subfields of the connection element identifier parameter field: + +#### a) *Virtual Path Connection Identifier (octets 1 and 2)* + +A code expressing in pure binary representation the identifier of the virtual path connection (see Note 1). Bit 8 of octet 1 is the most significant and bit 1 of octet 2 is the least significant respectively. + +NOTE 1 – The VPCI is an identifier that represents a VPC on a given interface. The value of this field is not identical to the value used in the VPI field of the corresponding ATM cell header. + +#### b) *Virtual Channel Identifier (octets 3 and 4)* + +A code expressing in pure binary representation the identifier of the virtual channel (see Notes 2 and 3). Bit 8 of octet 3 is the most significant and bit 1 of octet 4 is the least significant respectively. + +NOTE 2 – The value of this field is the same as the value used in the VCI field of the corresponding ATM cell header. + +NOTE 3 – Octets 3 and 4 are omitted if the entire virtual path connection is addressed. + +NOTE 4 – Consistency with ITU-T Recommendation I.361 for pre-assigned VPI/VCI values should be assured. + +### 7.51 Connection identifier + +The format of the connection identifier parameter field is shown in Figure 47. + +![](5391e1303dec02a02e7e42b5a4ffe58a_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------|---|---|---|---|---|---|---|--------| +| Connection Identifier | | | | | | | | 1 | +| | | | | | | | | 2 | + +**Figure 47/Q.2763 – Connection identifier parameter field** + +The following codes are used in the subfields of the connection identifier parameter field: + +#### a) *Connection Identifier* + +A bit string representing the identification allocated to the connection within a call. + +### 7.52 Consistency check result information + +The format of the consistency check result information parameter field is shown in Figure 48. + +![](c1df61cc3717e878a48e530218403403_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|-----------------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | VPCI check result indicator | | 1 | + +**Figure 48/Q.2763 – Consistency check result information parameter field** + +The following codes are used in the subfields of the consistency check result information parameter field: + +- a) *VPCI check result indicator* +- 00 Virtual Path Connection Identifier check NOT successful. + - 01 Virtual Path Connection Identifier check successful. + - 10 Virtual Path Connection Identifier check not performed. + - 11 Spare. + +### 7.53 Correlation ID + +The format of the correlation ID parameter field is shown in Figure 49. + +![](683f755e8456c884716de4fce48c7e63_img.jpg) + +| | | | | | | | | | +|----------------|---|---|---|---|---|---|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Correlation ID | | | | | | | | 1 | +| | | | | | | | | : | +| | | | | | | | | n | + +**Figure 49/Q.2763 – Correlation ID parameter field** + +The correlation ID is coded as described in ITU-T Recommendation Q.1218. + +### 7.54 Destination connection link identifier + +The format of the destination connection link identifier field is shown in Figure 50. + +![](659a041a7997f9eea79f4e2f3ba265a5_img.jpg) + +| | | | | | | | | | +|------------|---|---|---|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Control ID | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | 3 | +| | | | | | | | | 4 | + +**Figure 50/Q.2763 – Destination connection link identifier parameter field** + +The following codes are used in the subfields of the destination connection link identifier parameter field: + +- a) *Control ID* +- A bit string representing the identification of the connection link association. + +### 7.55 Destination signalling identifier (DSID) + +The format of the destination signalling identifier parameter field is shown in Figure 51. + +![](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +| | | | | | | | | | +|------------|---|---|---|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Control ID | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | 3 | +| | | | | | | | | 4 | + +**Figure 51/Q.2763 – Destination signalling identifier parameter field** + +The following codes are used in the subfields of the destination signalling identifier parameter field: + +#### a) *Control ID* + +A bit string representing the identification allocated to the signalling association. + +### **7.56 Display information** + +The format of the display information parameter field is shown in Figure 52. + +![](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +| | | | | | | | | | +|---------------------|---|---|---|---|---|---|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Display information | | | | | | | | 1 | +| | | | | | | | | : | +| | | | | | | | | n | + +**Figure 52/Q.2763 – Display information parameter field** + +The display information is coded as described in ITU-T Recommendation Q.931. + +### **7.57 Echo control information** + +The format of the echo control information parameter field is shown in Figure 53. + +![](a89d151b67109378baed0c117830cf78_img.jpg) + +| | | | | | | | | | +|-------------------------------------------|---|------------------------------------------------|---|----------------------------------------|---|----------------------------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Incoming half echo control device request | | Outgoing half echo control device request ind. | | Incoming half echo control device ind. | | outgoing half echo control device ind. | | 1 | + +**Figure 53/Q.2763 – Echo control information parameter field** + +The following codes are used in the echo control information parameter field: + +#### a) *Incoming echo control device request indicator* + +- 00 No information. +- 01 Incoming echo control device activation request. +- 10 Incoming echo control device deactivation request. +- 11 Spare. + +#### b) *Outgoing echo control device request indicator* + +- 00 No information. +- 01 Outgoing echo control device activation request. +- 10 Outgoing echo control device deactivation request. +- 11 Spare. + +- c) *Incoming echo control device indicator* +- 00 No information. + - 01 Incoming echo control device not included. + - 10 Incoming echo control device included. + - 11 Spare. +- d) *Outgoing echo control device indicator* +- 00 No information. + - 01 Outgoing echo control device not included. + - 10 Outgoing echo control device included. + - 11 Spare. + +### 7.58 End-to-end transit delay network generated indicator + +The format of the end-to-end transit delay network generated indicator parameter field is shown in Figure 54. + +![](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +| | | | | | | | | +|------------------------------------------------------|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| End-to-end Transit Delay Network Generated Indicator | | | | | | | | + +**Figure 54/Q.2763 – End-to-end transit delay network generated indicator parameter field** + +The following codes are used in the End-to-end Transit Delay Network Generated Indication: + +- 00000000 No indication. +- 00000001 Network generated. +- 00000010 User generated. +- 00000011 to 11111111 } Spare. + +### 7.59 Exclusive connection element identifier + +The format of the exclusive connection element identifier parameter is shown in Figure 55. + +![](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +| | | | | | | | | | +|-------------------------------------------|---|---|---|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Virtual Path Connection Identifier (VPCI) | | | | | | | | 1 | +| | | | | | | | | 2 | + +**Figure 55/Q.2763 – Exclusive connection element identifier parameter field** + +The following codes are used in the subfields of the Exclusive connection element identifier parameter field: + +- a) *Virtual Path Connection Identifier VPCI (octets 1 and 2)* + +A code expressing in pure binary representation the identifier of the virtual path connection (see Note). Bit 8 of octet 1 is the most significant and bit 1 of octet 2 is the least significant respectively. + +NOTE – The VPCI is an identifier that represents a VPC on a given interface. The value of this field is not identical to the value used in the VPI field of the corresponding ATM cell header. + +### 7.60 Extended Quality of Service + +The extended quality of service parameter field is shown in Figure 56. + +![](8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg) + +| | | | | | | | | | | +|----------------------------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Coding Standard | | Reserved | | | | | | 1 | +| Content is as the Extended Quality
of Service IE in Rec. Q.2965.2, starting with octet 5. | | | | | | | | | 2 | + +**Figure 56/Q.2763 – Extended Quality of Service parameter field** + +In addition to the notes associated with Figure 2/Q.2965.2, the following comment apply to the Extended Quality of Service parameter. + +The Acceptable Forward/Backward Cell Delay Variation and Cell Loss Ratio are not used for routing purpose and are carried transparently. + +### 7.61 Forward GVNS + +The format of the forward GVNS parameter field is shown in Figures 57-1 to 57-4. + +![](5c3dd31372f59e15250f0ab1613ca485_img.jpg) + +| | | | | | | | | | | +|---------------------------------------------------|---|---|---|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| Originating participating service provider (OPSP) | | | | | | | | | 1 | +| GVNS user group (GUG) | | | | | | | | | 2 | +| Terminating network routing number (TNRN) | | | | | | | | | 3 | + +**Figure 57-1/Q.2763 – Forward GVNS parameter field** + +The following codes are used in the subfields of the forward GVNS parameter: + +a) *Originating participating service provider* + +![](981668c6be5792b778cccb1af38477e2_img.jpg) + +| | | | | | | | | | | +|-----------------------|-------|---|---|-----------------------|---|---|---|--------|----| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| Odd/
Even | Spare | | | OPSP length indicator | | | | | 1 | +| 2nd digit | | | | 1st digit | | | | | 1a | +| ... | | | | ... | | | | | : | +| Filler (if necessary) | | | | Nth digit | | | | | 1n | + +**Figure 57-2/Q.2763 – Originating participating service provider subfield** + +1) *Odd/Even indicator (O)* + +0 Even number of digits. + +1 Odd number of digits. + +2) *OPSP length indicator* + +Number of octets to follow. The maximum number of octets is 4 allowing for a maximum number of digits to 7. + +3) *Digit* + +Digit string in BCD encoding of flexible length representing the originating participating service provider (OPSP) identification. + +#### 4) *Filler* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +#### b) *GVNS User Group* + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | | | +|-----------------------|-------|---|---|----------------------|---|---|---|--------|--|--|--| +| Odd/
Even | Spare | | | GUG length indicator | | | | 2 | | | | +| 2nd digit | | | | 1st digit | | | | 2a | | | | +| ... | | | | ... | | | | : | | | | +| Filler (if necessary) | | | | Nth digit | | | | 2n | | | | + +**Figure 57-3/Q.2763 – GVNS user group subfield** + +##### 1) *Odd/Even indicator (O)* + +0 Even number of digits. + +1 Odd number of digits. + +##### 2) *GUG length indicator* + +Number of octets to follow. The maximum number of octets is 8 allowing for a maximum number of digits to 16. + +##### 3) *Digit* + +Digit string in BCD encoding of flexible length representing the GVNS user group (GUG) identification. + +##### 4) *Filler* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +#### c) *Terminating network routing number (TNRN)* + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | | | +|-----------------------|--------------------------|---|---|-----------------------------|---|---|---|--------|--|--|--| +| Odd/
Even | Numbering plan indicator | | | TNRN length indicator | | | | 3 | | | | +| Spare | | | | Nature of address indicator | | | | 3a | | | | +| 2nd digit | | | | 1st digit | | | | 3b | | | | +| ... | | | | ... | | | | : | | | | +| Filler (if necessary) | | | | Nth digit | | | | 3n | | | | + +**Figure 57-4/Q.2763 – Terminating network routing number subfield** + +##### 1) *Odd/Even indicator (O)* + +0 Even number of digits. + +1 Odd number of digits. + +##### 2) *Numbering plan indicator* + +See 3.9 d)/Q.763. + +##### 3) *(TNRN) length indicator* + +Number of octets to follow. The maximum number of octets is 9 allowing for a maximum number of digits to 15. + +##### 4) *Nature of address indicator* + +| | | +|--------------------------|-----------------------------------| +| 0000000 | Spare. | +| 0000001 | Subscriber number (national use). | +| 0000010 | Unknown (national use). | +| 0000011 | National (significant) number. | +| 0000100 | International number. | +| 0000101 | Network specific number. | +| 0000110
to
1101111 | Spare. | +| 1110000
to
1111110 | Reserved for national use. | +| 1111111 | Spare. | + +##### 5) *Digit* + +See 3.9 e)/Q.763. + +The most significant digit is sent first. Subsequent digits are sent in successive 4-bit fields. + +##### 6) *Filler* + +In case of an odd number of digits, the filler code 0000 is inserted after the last digit. + +### **7.62 Forward narrow-band interworking indicator** + +The format of the forward narrow-band interworking indicator parameter field is shown in Figure 58. + +![](9e9104f9ba7eec1259a7893c6380ca1b_img.jpg) + +| | | | | | | | | | +|-------|---|---|--------------------------------|---|------------------|---------------------|--------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | ISDN user part preference ind. | | ISDN access ind. | ISDN user part ind. | Inter-working ind. | 1 | + +**Figure 58/Q.2763 – Forward narrow-band interworking indicator parameter field** + +The following codes are used in the forward narrow-band interworking indicator parameter field: + +#### a) *ISDN user part preference indicator* + +- 00 ISDN user part preferred all the way. +- 01 ISDN user part not required all the way. +- 10 ISDN user part required all the way. +- 11 Spare. + +#### b) *ISDN access indicator* + +- 0 Originating access non-ISDN. +- 1 Originating access ISDN. + +#### c) *ISDN user part indicator* + +- 0 ISDN user part not used all the way. +- 1 ISDN user part used all the way. + +#### d) *Interworking indicator* + +- 0 No interworking encountered (No. 7 signalling all the way). +- 1 Interworking encountered. + +### 7.63 Hop counter + +The format of the hop counter parameter field is shown in Figure 59. + +![](bccc028d0e75bc30c41528056f581545_img.jpg) + +| | | | | | | | | | +|-------|---|---|-------------|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | Hop Counter | | | | | 1 | + +**Figure 59/Q.2763 – Hop counter parameter field** + +The following codes are used in the hop counter parameter field: + +- bits 1-5 Hop counter. +- bits 6-8 Spare. + +The hop counter contains the binary value of the number of contiguous SS7 inter-exchange channels that are allowed to complete the call. + +### 7.64 In-band information indicator + +The format of the in-band information indicator parameter field is shown in Figure 60. + +![](f5d2a88925807080157c7cfb1d41cf0b_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|--------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | In-band information Ind. | 1 | + +**Figure 60/Q.2763 – In-band information indicator parameter field** + +The following codes are used in the in-band information indicator parameter field: + +#### a) *In-band information indicator* + +- 0 No indication. +- 1 In-band information or an appropriate pattern is now available. + +### 7.65 Leaf party type + +The format of the leaf party type parameter field is shown in Figure 61. + +![](6581999464852ba0d46ad0c8bc2ea192_img.jpg) + +| | | | | | | | | | +|------------|---|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Party type | | | | | | | | 1 | + +**Figure 61/Q.2763 – Leaf party type parameter field** + +The following codes are used in the subfields of the leaf party type parameter field: + +#### a) *Party type* + +- 00000000 First endpoint of type 2 connection. +- 00000001 Subsequent endpoint of type 2 connection. + +### 7.66 Link layer core parameters + +The format of the link layer core parameters parameter field is shown in Figure 62. + +![](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) + +| | | | | | | | | | +|------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Coding as in Rec. Q.2933 starting with octet 5 | | | | | | | | 2 | + +**Figure 62/Q.2763 – Link layer core parameters parameter field** + +The codes to be used in the subfields of the link layer core parameters parameter field are defined in the link layer core parameters information element in ITU-T Recommendation Q.2933. + +### 7.67 Link layer protocol parameters + +The format of the link layer protocol parameters parameter field is shown in Figure 63. + +![](db5deafdae53dbc7d5972957f708c691_img.jpg) + +| | | | | | | | | | +|------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Coding as in Rec. Q.2933 starting with octet 5 | | | | | | | | 2 | + +**Figure 63/Q.2763 – Link layer protocol parameters parameter field** + +The codes to be used in the subfields of the link layer protocol parameters parameter field are defined in the link layer core parameters information element in ITU-T Recommendation Q.2933. + +### 7.68 Location number + +The format of the Location number field is shown in Figure 64. + +![](86692d82da6655813b5acf58a767a38c_img.jpg) + +| | | | | | | | | | +|---------------------------------|-----------------------------|---|---|--------------------------------------------|---|---------------------|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Internal
network
no. ind. | Numbering plan indicator | | | Address
presentation
restricted ind. | | Screening indicator | | 2 | +| 2nd address signal | | | | 1st address signal | | | | 3 | +| ⋮ | | | | ⋮ | | | | ⋮ | +| Filler (if necessary) | | | | N th address signal | | | | n | + +**Figure 64/Q.2763 – Location number parameter field** + +The following codes are used in the subfields of the location number parameter field: + +- a) *Odd/Even indicator (octet 1)* + - 0 Even number of address signals. + - 1 Odd number of address signals. + +- b) *Nature of address indicator (octet 1)* +- | | | +|--------------------------|------------------------------------------------| +| 0000000 | Spare. | +| 0000001 | Reserved for subscriber number (national use). | +| 0000010 | Reserved for unknown (national use). | +| 0000011 | National (significant) number (national use). | +| 0000100 | International number. | +| 0000101
to
1101111 | Spare. | +| 1110000
to
1111110 | Reserved for national use. | +| 1111111 | Spare. | +- c) *Internal network number indicator (octet 1)* +- | | | +|---|-----------------------------------------| +| 0 | Routing to internal number allowed. | +| 1 | Routing to internal number not allowed. | +- NOTE 1 – Default set to 1. +- d) *Numbering plan indicator (octet 2)* +- | | | +|-----|-------------------------------------------------------------------| +| 000 | Spare. | +| 001 | ISDN (telephony) numbering plan (see ITU-T Recommendation E.164). | +| 010 | Spare. | +| 011 | Reserved for national use. | +| 100 | Reserved for national use. | +| 101 | Private numbering plan. | +| 110 | Reserved for national use. | +| 111 | Spare. | +- NOTE 2 – Default set to 001. +- e) *Address presentation restricted indicator (octet 2)* +- | | | +|----|---------------------------------------| +| 00 | Presentation allowed. | +| 01 | Presentation restricted. | +| 10 | Address not available (national use). | +| 11 | Spare. | +- NOTE 3 – Default set to 01. +- f) *Screening indicator (octet 2)* +- | | | +|----|-------------------------------------| +| 00 | Reserved. | +| 01 | User provided, verified and passed. | +| 10 | Reserved. | +| 11 | Network provided. | +- NOTE 4 – Default set to 11. + +g) *Address signals (octets 3 to n)* + +| | | +|------|----------| +| 0000 | Digit 0. | +| 0001 | Digit 1. | +| 0010 | Digit 2. | +| 0011 | Digit 3. | +| 0100 | Digit 4. | +| 0101 | Digit 5. | +| 0110 | Digit 6. | +| 0111 | Digit 7. | +| 1000 | Digit 8. | +| 1001 | Digit 9. | +| 1010 | } Spare. | +| to | | +| 1111 | | + +h) *Filler (octet n)* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### 7.69 Loop prevention indicators + +The format of the loop prevention indicators parameter field is shown in Figure 65. + +![](408c4798ea60469e0728a7cbbd598668_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|--------------------------|---|------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | Response ind. (or Spare) | | Type | | 1 | + +**Figure 65/Q.2763 – Loop prevention indicators parameter field** + +The following codes are used in the loop prevention indicators parameter field: + +bits 1 Type. + +0 Request. + +1 Response. + +If bit 1 equals to 0 (request). + +bits 2-8 Spare. + +If bit 1 equals to 1 (response). + +bits 2-3 Response indicator. + +00 Insufficient information (Note). + +01 No loop exist. + +10 Simultaneous transfer. + +11 Spare. + +bits 4-8 Spare. + +NOTE – The value "insufficient information" may be received due to interworking. + +### 7.70 Maximum end-to-end transit delay + +The format of the maximum end-to-end transit delay parameter field corresponds to the format for the call history parameter. + +The encoding is identical to the encoding of the call history information parameter. + +### 7.71 MCID response indicators + +The format of the MCID response indicators parameter is shown in Figure 66. + +![](c419b566d720267c499087add1506018_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|-------|---|---|---|---|---|--------------------------|-------------------------|-------| +| Spare | | | | | | Hold provided (national) | MCID response indicator | 1 | + +Figure 66/Q.2763 – MCID response indicators parameter field + +The following codes are used in the MCID response indicators parameter field: + +- bit 1 MCID response indicator. + - 0 MCID not included + - 1 MCID included. +- bit 2 Hold provided indicator (national use) + - 0 Holding not provided. + - 1 Holding provided. +- bits 3-8 Spare. + +### 7.72 MCID request indicators + +The format of the MCID request indicators parameter field is shown in Figure 67. + +![](a78db21022e0687c18d97ed547dd7ecb_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|-------|---|---|---|---|---|--------------------------|-------------------------|-------| +| Spare | | | | | | Hold provided (national) | MCID response indicator | 1 | + +Figure 67/Q.2763 – MCID request indicators parameter field + +The following codes are used in the MCID request indicators parameter field: + +- bit 1 MCID request indicator. + - 0 MCID not requested. + - 1 MCID requested. +- bit 2 Holding indicator (national use) + - 0 Holding not requested. + - 1 Holding requested. +- bits 3-8 Spare. + +### 7.73 Minimum ATM cell rate + +The format of the minimum ATM cell rate parameter field corresponds to the format of the additional ATM cell rate parameter. + +The following codes are used in the subfields of the minimum ATM cell rate parameter field: + +#### a) *Cell rate identifier* + +See ITU-T Recommendation Q.2931.1 to Q.2961.2 and Q.2962 for the coding. The codes are given here are just for information. + +| | | +|----------|---------------------------------------------------------------| +| 10000010 | Forward peak cell rate for cell loss priority = 0 | +| 10000011 | Backward peak cell rate for cell loss priority = 0 | +| 10000100 | Forward peak cell rate for cell loss priority = 0 + 1 | +| 10000101 | Backward peak cell rate for cell loss priority = 0 + 1 | +| 10010010 | Forward ABR minimum cell rate for cell loss priority = 0 + 1 | +| 10010011 | Backward ABR minimum cell rate for cell loss priority = 0 + 1 | +| 10001000 | Forward sustainable cell rate for cell loss priority = 0 | +| 10001001 | Backward sustainable cell rate for cell loss priority = 0 | +| 10010000 | Forward sustainable cell rate for cell loss priority = 0 + 1 | +| 10010001 | Backward sustainable cell rate for cell loss priority = 0 + 1 | +| 10100000 | Forward maximum burst size for cell loss priority = 0 | +| 10100001 | Backward maximum burst size for cell loss priority = 0 | +| 10110000 | Forward maximum burst size for cell loss priority = 0 + 1 | +| 10110001 | Backward maximum burst size for cell loss priority = 0 + 1 | +| 11000000 | Forward resource management peak cell rate | +| 11000001 | Backward resource management peak cell rate | + +#### b) *Cell rate* + +The encoding is identical to the encoding of the additional ATM cell rate parameter. + +#### c) *Maximum burst size* + +The encoding is identical to the encoding of the additional ATM cell rate parameter. + +### 7.74 MLPP precedence + +The format of the Multi-level Precedence and Preemption (MLPP) precedence parameter field is shown in Figure 68. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | | +|---------------------|-------------------------------|---|-------|------------------|---|---|---|--------|--|--| +| Spare | Look-ahead for busy indicator | | Spare | Precedence level | | | | 1 | | | +| 1st NI digit | | | | 2nd NI digit | | | | 2 | | | +| 3rd NI digit | | | | 4th NI digit | | | | 3 | | | +| MLPP service domain | | | | | | | — | 4 | | | +| | | | | | | | — | 5 | | | +| | | | | | | | — | 6 | | | + +Figure 68/Q.2763 – MLPP precedence parameter field + +The following codes are used in the subfields of the MLPP precedence parameter field. + +#### a) *Look-ahead For Busy (LFB) indicator* + +| | | +|----|-------------------------------| +| 00 | LFB allowed. | +| 01 | Path reserved (national use). | +| 10 | LFB not allowed. | +| 11 | Spare. | + +#### b) *Precedence level* + +| | | +|--------------------|-----------------| +| 0000 | Flash override. | +| 0001 | Flash. | +| 0010 | Immediate. | +| 0011 | Priority. | +| 0100 | Routine. | +| 0011
to
1111 | Spare. | + +#### c) *Network identity NI (octets 2 and 3)* + +Each digit is coded in binary coded decimal representation from 0 to 9. + +The first digit of this field is coded 0. The TCC (Telephony Country Code) follows in the second to fourth NI digits (the most significant TCC digit is in the 2nd NI digit). If the TCC is one or two digits long, the excess digit(s) is(are) inserted with the code for ROA or network identification, if necessary. If octet 3 is not required, it is coded all zeros. + +#### d) *MLPP service domain (octets 4, 5 and 6)* + +A pure binary code allocated to a MLPP service domain administered by a particular ISDN. Bit 8 of octet 4 is the most significant and bit 1 of octet 6 is the least significant respectively. + +### 7.75 MLPP user information + +The format of the Multi-level Precedence and Preemption (MLPP) user information parameter field is shown in Figure 69. + +![](ccf6853c7291703cb04568057fef5849_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|---------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | MLPP user indicator | 1 | + +Figure 69/Q.2763 – MLPP user information parameter field + +The following codes are used in the subfields of the MLPP user information parameter field. + +#### a) *MLPP user indicator* + +| | | +|---|----------------| +| 0 | No indication. | +| 1 | MLPP user. | + +### 7.76 Narrow-band bearer capability + +The format of the narrow-band bearer capability parameter field is shown in Figure 70. + +![](cac61a60141d0335b4ae7a081f6b18d4_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|----------------------------------------------------|---|---|------------------|----------|---|---|---|----------| +| Spare | | | Repeat indicator | Priority | | | | 1 | +| Narrow-band bearer capability information elements | | | | | | | | 2 | +| | | | | | | | | : | +| | | | | | | | | n | + +Figure 70/Q.2763 – Narrow-band bearer capability parameter field + +The following codes are used in the subfields of the narrow-band bearer capability parameter field. + +#### a) *Repeat indicator (octet 1)* + +- | | | +|---|-----------------------------------| +| 0 | Information element not repeated. | +| 1 | Information element repeated. | + +#### b) *Priority (octet 1)* + +- | | | +|------|-------------------------------------------------------------------| +| 0000 | No prioritized order. | +| 0001 | Prioritized list for selecting one possibility: ascending order. | +| 0010 | Prioritized list for selecting one possibility: descending order. | +| 0011 | Spare. | +| to | | +| { | | +| 1111 | | + +#### c) *Narrow-band bearer capability information elements (octets 2 to *n*)* + +This field contains all narrow-band bearer capability information elements as received from DSS2 or as obtained in case of interworking with N-ISUP. The format of the narrow-band bearer capability elements is the same as specified in ITU-T Recommendation Q.2931. The order of the information elements is not changed. + +### 7.77 Narrow-band high layer compatibility + +The format of the narrow-band high layer compatibility parameter field is shown in Figure 71. + +![](9dd03da031e134bfc9ecc730dd5f6583_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------------------------------------------|---|---|------------------|----------|---|---|---|----------| +| Spare | | | Repeat indicator | Priority | | | | 1 | +| Narrow-band high layer compatibility information elements | | | | | | | | 2 | +| | | | | | | | | : | +| | | | | | | | | n | + +Figure 71/Q.2763 – Narrow-band high layer compatibility parameter field + +The following codes are used in the subfields of the narrow-band high layer compatibility parameter field. + +#### a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated. +- 1 Information element repeated. + +#### b) *Priority (octet 1)* + +- 0000 No prioritized order. +- 0001 Prioritized list for selecting one possibility: ascending order. +- 0010 Prioritized list for selecting one possibility: descending order. + +#### c) *Narrow-band high layer compatibility information elements (octets 2 to n)* + +This field contains all narrow-band high layer compatibility information elements as received from DSS 2 or as obtained in case of interworking with N-ISUP. The format of the narrow-band high layer compatibility elements is the same as specified in ITU-T Recommendation Q.2931. The order of the information elements is not changed. + +### 7.78 Narrow-band low layer compatibility + +The format of the narrow-band low layer compatibility parameter field is shown in Figure 72. + +![Diagram of the narrow-band low layer compatibility parameter field structure. It shows a table with 8 columns (numbered 8 to 1) and multiple rows (numbered 1 to n). Row 1 contains 'Spare' (columns 8-5), 'Repeat indicator' (column 4), and 'Priority' (columns 3-1). Rows 2 to n contain 'Narrow-band low layer compatibility information elements'.](8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|----------------------------------------------------------|---|---|---|------------------|----------|---|---|--------| +| Spare | | | | Repeat indicator | Priority | | | 1 | +| Narrow-band low layer compatibility information elements | | | | | | | | 2 | +| | | | | | | | | : | +| | | | | | | | | n | + +Diagram of the narrow-band low layer compatibility parameter field structure. It shows a table with 8 columns (numbered 8 to 1) and multiple rows (numbered 1 to n). Row 1 contains 'Spare' (columns 8-5), 'Repeat indicator' (column 4), and 'Priority' (columns 3-1). Rows 2 to n contain 'Narrow-band low layer compatibility information elements'. + +Figure 72/Q.2763 – Narrow-band low layer compatibility parameter field + +The following codes are used in the subfields of the narrow-band low layer compatibility parameter field. + +#### a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated. +- 1 Information element repeated. + +#### b) *Priority (octet 1)* + +- 0000 No prioritized order. +- 0001 Prioritized list for selecting one possibility: ascending order. +- 0010 Prioritized list for selecting one possibility: descending order. +- 0011 to 1111 Spare. + +#### c) *Narrow-band low layer compatibility information elements (octets 2 to n)* + +This field contains all narrow-band low layer compatibility information elements as received from DSS2 or as obtained in case of interworking with N-ISUP. The format of the narrow-band low layer compatibility elements is the same as specified in ITU-T Recommendation Q.2931. The order of the information elements is not changed. + +### 7.79 National/international call indicator + +The format of the national/international call indicator parameter field is shown in Figure 73. + +![](fed4a04822c24fb22cca3a14f4ddae83_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|----------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | National/international call ind. | 1 | + +**Figure 73/Q.2763 – National/international call indicator parameter field** + +The following codes are used in the national/international call indicator parameter field: + +- a) *National/international call indicator* + - 0 Call to be treated as national call. + - 1 Call to be treated as international call. + +### 7.80 Network call correlation identifier + +The format of the network call correlation identifier parameter field is shown in Figure 74. + +![](8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|--------------|---|---|---|------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| 1st NI digit | | | | 2nd NI digit | | | | 1 | +| 3rd NI digit | | | | 4th NI digit | | | | 2 | +| Point code | | | | | | | | 3
4
5 | +| Call identifier | | | | | | | | 6
7
8
9 | + +**Figure 74/Q.2763 – Network call correlation identifier parameter field** + +The following codes are used in the subfields of the network call correlation identifier parameter field: + +- a) *Network identity (NI) (octets 1 and 2)* + Coding as specified for the MLPP precedence parameter subfield in this ITU-T Recommendation. +- b) *Point code* + Point code of the exchange generating the Network Call Correlation Identifier. Bit 1 of octet 3 is the least significant bit and bit 8 of octet 5 is the most significant bit. Unused bits shall be coded as 0's. + NOTE – This format supports a 3-octet field for the point code of the generating node to allow for national point code arrangements. International point code would use octet 3 and bits 1 to 6 of octet 4. +- c) *Call Identifier* + A bit string representing the identification allocated to the call. + +### 7.81 Network look ahead indicator + +The format of the network look ahead indicator parameter field is shown in Figure 75. + +![](107c8e1abcb7033ad244e30e7a910045_img.jpg) + +| | | | | | | | | | +|-----------|-------|---|---|---|---|------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| ext.
1 | Spare | | | | | LA
ind. | | 1 | + +**Figure 75/Q.2763 – Network look ahead indicator parameter field** + +The following codes are used in the network look ahead indicator parameter field: + +- a) *Extension indicator* + - 0 Octet continues through the next octet. + - 1 Last octet. +- b) *Look Ahead indicator* + - 00 No indication. + - 01 Network Look Ahead invoked – no indication. + - 10 Reserved. + - 11 Network Look Ahead invoked – an answer received from the terminating exchange or private network. + +### 7.82 Network management controls + +The format of the network management controls parameter field is shown in Figure 76. + +![](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +| | | | | | | | | | +|-----------|-------|---|---|---|---|---------------------------------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| ext.
1 | Spare | | | | | Temporary
alternative
routing
ind. | | 1 | + +**Figure 76/Q.2763 – Network management controls parameter field** + +The following codes are used in the network management controls parameter field: + +- bit 1 Temporary Alternative Routing (TAR) indicator. + - 0 No indication. + - 1 TAR controlled call. +- bits 3-7 Spare. +- bit 8 Extension indicator. + - 0 Information continues through the next octet. + - 1 Last octet. + +### 7.83 Notification + +The format of the notification parameter field is shown in Figure 77. + +![](22e0e0864e0bf015260feabd4bebec60_img.jpg) + +| | | | | | | | | | +|------|------------------------|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| ext. | Notification indicator | | | | | | | 1 | + +**Figure 77/Q.2763 – Notification parameter field** + +The following codes are used in the notification indicator parameter field. + +#### a) *Extension indicator (ext.)* + +- 0 Information continues in the next octet (e.g. octet 1 to 1a). +- 1 Last octet. + +#### b) *Notification indicator* + +- 0000000 User suspended. +- 0000001 User resumed. +- 0000010 Bearer service change } (Used in DSS1) +- 0000011 Discriminator for extension to ASN.1 encoded component (Used in DSS1) +- 0000100 Call completion delay. +- 1000010 Conference established. +- 1000011 Conference disconnected. +- 1000100 Other party added. +- 1000101 Isolated. +- 1000110 Reattached. +- 1000111 Other party isolated. +- 1001000 Other party reattached. +- 1001001 Other party split. +- 1001010 Other party disconnected. +- 1001011 Conference floating. +- 1100000 Call is a waiting call. +- 1101000 Diversion activated (used in DSS1). +- 1101001 Call transfer, alerting. +- 1101010 Call transfer, active. +- 1111001 Remote hold. +- 1111010 Remote retrieval. +- 1111011 Call is diverting. + +All other values are currently reserved for further extensions. + +### **7.84 OAM traffic descriptor** + +The format of the OAM traffic descriptor parameter field is shown in Figure 78. + +![](a057800564be3506d2d87b6a4daee25b_img.jpg) + +| | | | | | | | | | | +|--|----------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| | ext.
1 | Coding standard | | Reserved | | | | | 1 | +| | Further contents as in Rec. Q.2931 starting with octet 5 | | | | | | | | 2 | + +**Figure 78/Q.2763 – OAM traffic descriptor parameter field** + +The codes to be used in the subfields of the OAM traffic descriptor parameter field are defined in the OAM traffic descriptor information element in ITU-T Recommendation Q.2931. + +### 7.85 Original called number + +The format of the original called number parameter field corresponds to the format shown in Figure 79. + +![](3ce04f1c7128814978c6b34d654a25cc_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------|-----------------------------|---|--------------------------------------------|--------------------|-------|---|---|----------| +| Odd/
Even | Nature of address indicator | | | | | | | 1 | +| Spare | Numbering plan indicator | | Address
presentation
restricted ind. | | Spare | | | 2 | +| 2nd address signal | | | | 1st address signal | | | | 3 | +| : | | | | : | | | | : | +| | | | | | | | | : | +| Filler (if necessary) | | | | Nth address signal | | | | n | + +**Figure 79/Q.2763 – Original called number parameter field** + +The following codes are used in the subfields of the original called number parameter field: + +- a) *Odd/Even indicator (octet 1)* + - 0 Even number of address signals. + - 1 Odd number of address signals. +- b) *Nature of address indicator (octet 1)* + +See Called party number parameter for coding. +- c) *Numbering plan indicator (octet 2)* + +See Called party number parameter for coding. +- d) *Address presentation restricted indicator (octet 2)* + - 00 Presentation allowed. + - 01 Presentation restricted. + - 10 Spare. + - 11 Spare. +- e) *Address signal (octets 3 to *n*)* + +See Calling party number parameter for coding. +- f) *Filler (octet *n*)* + +See 7.33 f). In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### 7.86 Origination connection link identifier + +The format of the origination connection link identifier parameter field corresponds to the format shown for the destination connection link identifier parameter field. + +### 7.87 Origination ISC point code + +The format of the origination ISC point code parameter field is shown in Figure 80. + +![](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) + +| | | | | | | | | | | +|--|-----------------------|---|---|---|---|---|---|---|--------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| | Signalling point code | | | | | | | | 1 | +| | Spare | | | | | | | | 2 | + +**Figure 80/Q.2763 – Origination ISC point code parameter field** + +The following codes are used in the subfields of the origination ISC point code parameter field: + +#### a) *Signalling point code (octets 1 and 2)* + +The signalling point code is a pure binary representation of the code allocated to a node in the signalling network. Bit 6 of octet 2 is the most significant and bit 1 of octet 1 is the least significant respectively. + +### 7.88 Origination signalling identifier + +The format of the origination signalling identifier parameter field corresponds to the format shown for the destination signalling identifier parameter. + +The encoding is identical to the encoding of the destination signalling identifier parameter field. + +### 7.89 Priority + +The format of the priority parameter field is shown in Figure 81. + +![](7355f66b8620d44cf566215621addb74_img.jpg) + +| | | | | | | | | | | +|--|--------------------------------------------------------------|-------|---|---|--------------|---|---|---|--------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| | ext.
1 | Spare | | | Priority | | | | 1 | +| | 1st II digit | | | | 2nd II digit | | | | 2 | +| | 3rd II digit | | | | 4th II digit | | | | 3 | +| | Most significant
National domain
Least significant bit | | | | | | | | 4 | +| | | | | | | | | | 5 | +| | | | | | | | | | 6 | + +**Figure 81/Q.2763 – Priority parameter field** + +#### *Priority (octet 1)* + +Four binary coded bits indicating priority coded as follows: + +0000 Level 1 (highest). + +0001 Level 2. + +0010 Level 3. + +0011 Level 4. + +0100 Level 5 (lowest). + +Other values are reserved. + +#### *Domain (octets 2-6)* + +The domain consists of four International identification digits, followed by a pure binary coded national domain. + +#### *International Identification (II) (octets 2-3)* + +Each II digit is coded in a binary coded decimal representation from 0 to 9. The first digit is coded 0. The Telephony Country Code (TCC) follows in the 2nd to the 4th II digits (the most significant TCC digit is in the 2nd II digit). If octet 3 is not required, it is coded all zeros. + +#### *National domain (octets 4-6)* + +National domain contains a code expressing in pure binary the number allocated to a national-specific domain to uniquely identify a customer domain across multiple ISDN networks. Bit 8 of octet 4 is the most significant bit and bit 1 of octet 6 is the least significant bit. + +### **7.90 Progress indicator** + +The format of the progress indicator parameter field is shown in Figure 82. + +![Diagram of the progress indicator parameter field structure. It shows a table with 8 bits per octet. Octet 1 contains Spare (bits 8-6), Repeat indicator (bit 5), and Priority (bits 4-1). Octets 2 through n contain Progress indicator information elements.](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +| | | | | | | | | | | +|---|-----------------------------------------|---|---|------------------|----------|---|---|---|--------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| 1 | Spare | | | Repeat indicator | Priority | | | | | +| 2 | Progress indicator information elements | | | | | | | | | +| : | | | | | | | | | | +| n | | | | | | | | | | + +Diagram of the progress indicator parameter field structure. It shows a table with 8 bits per octet. Octet 1 contains Spare (bits 8-6), Repeat indicator (bit 5), and Priority (bits 4-1). Octets 2 through n contain Progress indicator information elements. + +**Figure 82/Q.2763 – Progress indicator parameter field** + +The following codes are used in the subfields of the progress indicator parameter field: + +#### a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated. +- 1 Information element repeated. + +#### b) *Priority (octet 1)* + +- 0000 No prioritized order. +- 0001 Prioritized list for selecting one possibility: ascending order. +- 0010 Prioritized list for selecting one possibility: descending order. +- 0011 to 1111 Reserve. + +#### c) *Progress indicator information elements (octets 2 to n)* + +This field contains all progress indicator information elements as received from DSS2 or as obtained in case of interworking with N-ISUP. The format of the progress indicator elements is the same as specified in ITU-T Recommendation Q.2931. The order of the information elements is not changed. + +### **7.91 Propagation delay counter** + +The format of the propagation delay counter parameter field corresponds to the format shown for the call history information parameter. + +The encoding is identical to the encoding of the call history information parameter field. + +### 7.92 Quality of service (QoS) + +The format of the QoS parameter field is shown in Figure 83. + +![](27788c2a26d9641e68232a4eff1299b9_img.jpg) + +| | | | | | | | | | +|-----------------------------------|-----------------|---|----------|---|---|---|---|--------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Quality of Service class forward | | | | | | | | 2 | +| Quality of Service class backward | | | | | | | | 3 | + +**Figure 83/Q.2763 – QoS parameter field** + +The following codes are used in the subfields of the QoS parameter field: + +#### a) *Coding standard* + +00 ITU standard codes. + +01 Reserved for ISO/IEC standard codes. + +10 Reserved for national use. + +11 Reserved for network specific use. + +The following codepoints are assigned for Coding standard = 00: + +##### i) *Quality of Service class forward* + +The coding of this subfield is defined in the QoS parameter information element in ITU-T Recommendation Q.2965.1. + +##### ii) *Quality of Service class backward* + +The coding of this subfield is defined in the QoS parameter information element in ITU-T Recommendation Q.2965.1. + +### 7.93 Redirecting number + +The format of the redirecting number parameter field corresponds to the format shown for the original called number. + +The following codes are used in the subfields of the redirecting number parameter field: + +#### a) *Odd/Even indicator (octet 1)* + +0 Even number of address signals. + +1 Odd number of address signals. + +#### b) *Nature of address indicator (octet 1)* + +See Called party number parameter for coding. + +#### c) *Numbering plan indicator (octet 2)* + +See Called party number parameter for coding. + +#### d) *Address presentation restricted indicator (octet 2)* + +See Original called number parameter for coding. + +#### e) *Address signal (octets 3 to n)* + +See Calling party number parameter for coding. + +#### f) *Filler (octet n)* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +### 7.94 Redirection information + +The format of the redirection information parameter field is shown in Figure 84. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------------|---|---|---|-------|-----------------------|---|---|--------| +| Original redirection reason | | | | Spare | Redirecting indicator | | | 1 | +| Redirecting reason | | | | Spare | Redirection counter | | | 2 | + +**Figure 84/Q.2763 – Redirection information parameter field** + +NOTE – Octet 2 is omitted if the redirection counter is coded 001. + +The following codes are used in the redirection information parameter field: + +#### a) *Original redirection reason (octet 1)* + +- 0000 Unknown/not available. +- 0001 User busy (national use). +- 0010 No reply (national use). +- 0011 Unconditional (national use). +- 0100 } Spare. +- to } +- 1111 } + +#### b) *Redirecting indicator (octet 1)* + +- 000 No redirection (national use). +- 001 Call re-routed (national use). +- 010 Call re-routed, all redirection information presentation restricted (national use). +- 011 Call diversion. +- 100 Call diversion, all redirection information presentation restricted. +- 101 Call re-routed, redirection number presentation restricted (national use). +- 110 Call diversion, redirection number presentation restricted. +- 111 Spare. + +#### c) *Redirecting reason (octet 2)* + +- 0000 Unknown/not available. +- 0001 User busy. +- 0010 No reply. +- 0011 Unconditional. +- 0100 Deflection during alerting. +- 0101 Deflection immediate response. +- 0110 Mobile subscriber not reachable. +- 0111 } Spare. +- to } +- 1111 } + +#### d) *Redirection counter (octet 2)* + +Number of redirections the call has undergone expressed as a binary number between 1 and 5. + +### 7.95 Redirection number + +The format of the redirection number parameter field corresponds to the format shown for the called party number parameter. + +The following codes are used in the subfields of the redirection number parameter field: + +- a) *Odd/Even indicator (octet 1)* +0 Even number of address signals. +1 Odd number of address signals. +- b) *Nature of address indicator (octet 1)* +See Called party number parameter for coding. +- c) *Internal network number indicator (octet 2)* +See Called party number parameter for coding. +- d) *Numbering plan indicator (octet 2)* +See Called party number parameter for coding. +- e) *Address signal (octets 3 to n)* +See calling party number parameter for coding. +- f) *Filler (octet n)* +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signals. + +### 7.96 Redirection number restriction + +The format of the redirection number restriction parameter field is shown in Figure 85. + +![](6707cae4df136f92a0c9f3a4676f91a6_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|------------------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | Presentation restricted ind. | | 1 | + +Figure 85/Q.2763 – Redirection number restriction parameter field + +The following codes are used in the redirection number restriction parameter field: + +- a) *Presentation restricted indicator* +00 Presentation allowed. +01 Presentation restricted. +10 Spare. +11 Spare. + +### 7.97 Remote operations (national use) + +The format of the remote operations parameter field is shown in Figure 86. + +![](c3254408eadbf152632a8faf16310722_img.jpg) + +| | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---|------------------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Spare | | Protocol profile | | | | | | 1 | +| Component (s) | | | | | | | | | 2 | +| NOTE – The component may be repeated any number of times within the remote operations parameter. In case of multiple service requests, the receiving entity shall treat the repetition of Invoke components identical to the case where multiple remote operations parameters are received in a single message. | | | | | | | | | | + +**Figure 86/Q.2763 – Remote operations parameter field** + +The following codes are used in the remote operations parameter field: + +- a) *Extension indicator (ext.)* + - 0 Information continues through the next octet. + - 1 Last octet. +- b) *Protocol profile field* + - 00000 to 10000 Spare. + - 10001 Remote operations protocol. + - 10010 to 11111 Spare. +- c) *Components* + +See 3.48/Q.763 for the format and coding of the elements in the components. + +### 7.98 Report type + +The format of the report type parameter field is shown in Figure 87. + +![](ff7977984f2552f326b2089d7595fff3_img.jpg) + +| | | | | | | | | | | +|----------------------------------------------------------------------------|-----------------|---|----------|---|---|---|---|--------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +| ext.
1 | Coding standard | | Reserved | | | | | | 1 | +| Coding as in Rec. Q.2963.1 and Amendment 4 to Q.2931 starting with octet 5 | | | | | | | | | 2 | + +**Figure 87/Q.2763 – Report type parameter field** + +The codes to be used in the subfields of the report type parameter field are defined in the Broadband report type information element in ITU-T Recommendation Q.2963.1 and Amendment 4/Q.2931. + +### 7.99 Report type prime + +The format of the report type prime parameter field is shown in Figure 88. + +![Figure 88/Q.2763 – Report type prime parameter field diagram. It shows a table with 8 columns (bits 8-1) and multiple rows (octets 1 to n). Octet 1 contains Spare (bits 8-6), Repeat indicator (bit 5), and Priority (bits 4-1). Octets 2 to n contain Broadband report type information elements.](24ca460ee3381aee781887e9e586ec67_img.jpg) + +| | | | | | | | | | | +|---|--------------------------------------------|---|---|------------------|----------|---|---|---|-------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| 1 | Spare | | | Repeat indicator | Priority | | | | 1 | +| 2 | Broadband report type information elements | | | | | | | | 2 | +| ⋮ | | | | | | | | | ⋮ | +| n | | | | | | | | | n | + +Figure 88/Q.2763 – Report type prime parameter field diagram. It shows a table with 8 columns (bits 8-1) and multiple rows (octets 1 to n). Octet 1 contains Spare (bits 8-6), Repeat indicator (bit 5), and Priority (bits 4-1). Octets 2 to n contain Broadband report type information elements. + +Figure 88/Q.2763 – Report type prime parameter field + +The following codes are used in the subfields of the report type prime parameter field: + +a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated. +- 1 Information element repeated. + +b) *Priority (octet 1)* + +- 0000 No priority order. +- 0001 Prioritized list for selecting one possibility: ascending order. +- 0010 Prioritized list for selecting one possibility: descending order. +- 0011 to 1111 Reserved. + +c) *Broadband report type information elements (octets 2 to n)* + +This field contains the broadband report type information elements as received from DSS2 starting with the second one. The first one should be contained in the report type parameter. The format of the broadband report type information elements is the same as specified in Amendment 4/Q.2931. The order of the information elements is not changed. + +### 7.100 Resource identifier + +The format of the resource identifier parameter field is shown in Figure 89. + +![Figure 89/Q.2763 – Resource identifier parameter field diagram. It shows a table with 8 columns (bits 8-1) and multiple rows (octets 1 to n). Octet 1 contains ext. 1 (bit 8), Spare (bits 7-4), and Resource indicator (bits 3-1). Octets 2 to n contain Resource value.](54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg) + +| | | | | | | | | | | +|---|----------------|-------|---|---|---|--------------------|---|---|--------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| 1 | ext. 1 | Spare | | | | Resource indicator | | | 1 | +| 2 | Resource value | | | | | | | | 2 | +| ⋮ | | | | | | | | | ⋮ | +| n | | | | | | | | | n | + +Figure 89/Q.2763 – Resource identifier parameter field diagram. It shows a table with 8 columns (bits 8-1) and multiple rows (octets 1 to n). Octet 1 contains ext. 1 (bit 8), Spare (bits 7-4), and Resource indicator (bits 3-1). Octets 2 to n contain Resource value. + +Figure 89/Q.2763 – Resource identifier parameter field + +The following codes are used in the subfields of the resource identifier parameter field: + +#### a) *Extension indicator (ext.) (octet 1)* + +- 0 Octet continues through the next octet (e.g. octet 1 to 1a). +- 1 Last octet. + +#### b) *Resource indicator* + +- 000 Local signalling identifier. +- 001 Remote signalling identifier. +- 010 Connection element identifier: VPCI/VCI. +- 011 Connection element identifier: VPCI. +- 100 VPC pool: VPCI. +- 101 to 111 Spare. + +#### c) *Resource value (octets 2 to n)* + +A code representing the identifier of the resource to be reset. + +NOTE 1 – This value will be equal to a signalling identifier control ID value if the resource indicator is coded "000" or "001". + +NOTE 2 – This value will be equal to a VPCI/VCI value if the resource indicator is coded "010". + +NOTE 3 – This value will be equal to a VPCI value if the resource indicator is coded "011" or "100". + +NOTE 4 – The maximum length of the resource value is 4 octets. + +### 7.101 SCF ID + +The format of the SCF id parameter field is shown in Figure 90. + +![Figure 90/Q.2763 – SCF ID parameter field diagram. It shows a rectangular box representing the parameter field. Above the box, bits 8 through 1 are labeled. To the right of the box, the word 'Octets' is followed by a vertical list: 1, :, n. Inside the box, the text 'SCF ID' is centered.](df94f7807f02e218ee3c66b9cbd829e5_img.jpg) + +Figure 90/Q.2763 – SCF ID parameter field diagram. It shows a rectangular box representing the parameter field. Above the box, bits 8 through 1 are labeled. To the right of the box, the word 'Octets' is followed by a vertical list: 1, :, n. Inside the box, the text 'SCF ID' is centered. + +Figure 90/Q.2763 – SCF ID parameter field + +The SCF ID is coded as described in ITU-T Recommendation Q.1218. + +### 7.102 Segmentation indicator (national use) + +The format of the segmentation indicator parameter field is shown in Figure 91. + +![Figure 91/Q.2763 – Segmentation indicator parameter field diagram. It shows a rectangular box divided into two parts. Above the box, bits 8 through 1 are labeled. The left part (bits 8-2) is labeled 'Spare'. The right part (bit 1) is labeled 'Simple segmentation ind.'. To the right of the box, the word 'Octet' is followed by the number 1.](4f50daa1723a6a80a6c8694054638192_img.jpg) + +Figure 91/Q.2763 – Segmentation indicator parameter field diagram. It shows a rectangular box divided into two parts. Above the box, bits 8 through 1 are labeled. The left part (bits 8-2) is labeled 'Spare'. The right part (bit 1) is labeled 'Simple segmentation ind.'. To the right of the box, the word 'Octet' is followed by the number 1. + +Figure 91/Q.2763 – Segmentation indicator parameter field + +The following codes are used in the subfields of the segmentation indicator parameter field: + +#### a) *Simple segmentation indicator* + +- 0 No additional information will be sent. +- 1 Additional information will be sent in a segmentation message. + +### **7.103 Service activation** + +The format of the service activation parameter field is shown in Figure 92. + +![Diagram of Service activation parameter field showing a single octet with bit positions 8-1 and the label 'Feature code'.](a634891d16b60b21df90a35c2af72c67_img.jpg) + +The diagram shows a single octet structure. Above the box are bit positions 8, 7, 6, 5, 4, 3, 2, 1. Inside the box is the text 'Feature code'. To the right of the box, the word 'Octets' is followed by a vertical list: 1, :, n. + +Diagram of Service activation parameter field showing a single octet with bit positions 8-1 and the label 'Feature code'. + +**Figure 92/Q.2763 – Service activation parameter field** + +The following feature codes are used in the service activation parameter field: + +- 00000000 Spare. +- 00000001 Reserved for call transfer. +- 00000010 to 01111011 Reserved for international use. +- 01111100 to 11111110 Reserved for national use. +- 11111111 Reserved for extension. + +### **7.104 Soft PVC called endpoint** + +The format of the soft PVC called endpoint parameter field is shown in Figure 93. + +![Diagram of Soft PVC called endpoint parameter field showing multiple octets with subfields: ext. 1, Coding standard, Reserved, Selection type, Subfield indicator, VPCI value, Subfield indicator, VCI value.](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg) + +The diagram shows a multi-octet structure. The first octet is split into three subfields: 'ext.' (bit 8), 'Coding standard' (bits 7-4), and 'Reserved' (bits 3-1). The subsequent octets are: Octet 2: 'Selection type'; Octet 3: 'Subfield indicator'; Octet 4: 'VPCI value'; Octet 5: 'Subfield indicator'; Octet 6: 'VCI value'. To the right, the word 'Octets' is followed by a vertical list: 1, 2, 3, 4, 5, 6. + +Diagram of Soft PVC called endpoint parameter field showing multiple octets with subfields: ext. 1, Coding standard, Reserved, Selection type, Subfield indicator, VPCI value, Subfield indicator, VCI value. + +**Figure 93/Q.2763 – Soft PVC called endpoint parameter field** + +Subfields are coded as follows: + +#### a) *Selection type* + +- 00000000 Any value. +- 00000010 Required value. +- 00000100 Assigned value. + +All other values reserved. + +#### b) *Subfield indicator* + +00000001 VPCI value. + +00000010 VCI value. + +All other values reserved. + +#### c) *VPCI value* + +Two-octet value coded as in the Connection Element Identifier. + +#### d) *VCI value* + +Two-octet value coded as in the Connection Element Identifier. + +### 7.105 Soft PVC calling endpoint + +The format of the soft PVC calling endpoint parameter field is shown in Figure 94. + +![](22bc7139d3987c61ddefffa08036a923_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|--------------------|-----------------|---|----------|---|---|---|---|--------| +| ext.
1 | Coding standard | | Reserved | | | | | 1 | +| Subfield indicator | | | | | | | | 2 | +| VPCI value | | | | | | | | 3 | +| Subfield indicator | | | | | | | | 4 | +| VCI value | | | | | | | | 5 | + +**Figure 94/Q.2763 – Soft PVC calling endpoint parameter field** + +Subfields are coded as follows: + +#### a) *Subfield indicator* + +00000001 VPCI value. + +00000010 VCI value. + +All other values reserved. + +#### b) *VPCI value* + +Two-octet value coded as in the Connection Element Identifier. + +#### c) *VCI value* + +Two-octet value coded as in the Connection Element Identifier. + +### 7.106 Subsequent number + +The format of the subsequent number parameter field is shown in Figure 95. + +![](ba5b48e32c0ac38c3e2e81078066c16d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------------------|-------|---|---|--------------------|---|---|---|--------| +| Odd/
Even | Spare | | | | | | | 1 | +| 2nd address signal | | | | 1st address signal | | | | 2 | +| | | | | | | | | ⋮ | +| Filler (if necessary) | | | | Nth address signal | | | | n | + +**Figure 95/Q.2763 – Subsequent number parameter field** + +The following codes are used in the subfields of the subsequent number parameter field: + +- a) *Odd/Even indicator (octet 1)* + - 0 Even number of address signals. + - 1 Odd number of address signals. +- b) *Address signal (octets 2 to n)* +See Called party number parameter for coding. +- c) *Filler (octet n)* +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +**7.107 Suspend/resume indicators** + +The format of the suspend/resume indicators parameter field is shown in Figure 96. + +![](c21fe89d8034ec5b80bd47c1cd710202_img.jpg) + +| | | | | | | | | | +|-------|---|---|---|---|---|---|----------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Spare | | | | | | | Suspend /resume ind. | 1 | + +**Figure 96/Q.2763 – Suspend/resume indicators parameter field** + +The following codes are used in the suspend/resume indicators parameter field: + +- a) *Suspend/resume indicator* + - 0 ISDN subscriber initiated. + - 1 Network initiated. + +**7.108 Transit network selection (national use)** + +The format of the transit network selection parameter field is shown in Figure 97. + +![](35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg) + +| | | | | | | | | | +|------------------------|--------------------------------|---|---|-----------------------------|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| Odd/ Even | Type of network identification | | | Network identification plan | | | | 1 | +| Network identification | | | | | | | | 2
:
n | + +**Figure 97/Q.2763 – Transit network selection parameter field** + +The following codes are used in the subfields of the transit network selection parameter field: + +- a) *Odd/Even indicator (octet 1)* + - 0 Even number of digits. + - 1 Odd number of digits. + +68 **ITU-T Q.2763 (12/1999)** + +- b) *Type of network identification (octet 1)* +- 000 ITU-T (CCITT) – Standardized identification. + 010 National network identification. + Other Spare. +- c) *Network identification plan (octet 1)* +- i) For ITU-T (CCITT) – Standardized identification: + 0000 Unknown. + 0011 Public Data Network Identification Code (DNIC), ITU-T Recommendation X.121. + 0110 Public land Mobile Network Identification Code (MNIC), ITU-T Recommendation E.212. + Other Spare. +- ii) For national network identification: + This information is coded according to national specifications. +- d) *Network identification (octets 2 to n)* +- This information is organized according to the network identification plan and the coding principle given in 7.33 e). + +### 7.109 UID action indicators + +The format of the UID action indicators parameter field is shown in Figure 98. + +![](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +| | | | | | | | | | +|-----------|-------|---|---|---|---|------------------------------|--------------------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| ext.
1 | Spare | | | | | T9 timer
instruc.
ind. | Through-
connection
instruc.
ind. | 1 | + +**Figure 98/Q.2763 – UID action indicators parameter field** + +The following codes are used in the UID action indicators parameter field: + +- bit 1 Through-connection instruction indicator. + 0 No indication. + 1 Through connect in both directions. +- bit 2 T9 timer instruction indicator. + 0 No indication. + 1 Stop or do not start T9 timer. +- bits 3-7 Spare. +- bit 8 Extension indicator. + 0 Information continues through the next octet. + 1 Last octet. + +### 7.110 UID capability indicators + +The format of the UID capability indicators parameter field is shown in Figure 99. + +![](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) + +| | | | | | | | | | +|-----------|-------|---|---|---|---|------------------------------|--------------------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| ext.
1 | Spare | | | | | T9 timer
instruc.
ind. | Through-
connection
instruc.
ind. | 1 | + +**Figure 99/Q.2763 – UID capability indicators parameter field** + +The following codes are used in the UID capability indicators parameter field: + +- bit 1      Through-connection indicator. + - 0      No indication. + - 1      Through-connection modification possible. +- Bit 2      T9 timer indication. + - 0      No indication. + - 1      Stopping of T9 timer possible. +- Bits 3-7    Spare. +- Bit 8      Extension indicator. + - 0      Information continues through the next octet. + - 1      Last octet. + +### 7.111 User-to-user indicators + +The format of the user-to-user indicators parameter field is shown in Figure 100. + +![](dfe74512a9c9fb620f72c9dbc22874aa_img.jpg) + +| | | | | | | | | | +|----------------------------|-----------|---|-----------|---|-----------|---|------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| Network
discard
ind. | Service 3 | | Service 2 | | Service 1 | | Type | 1 | + +**Figure 100/Q.2763 – User-to-user indicators parameter field** + +The following codes are used in the user-to-user indicators parameter field: + +- 1)      If type (bit 1) equals 0 (request): + - a)    *Network discard indicator* +Not used for request, set to "0". + - b)    *Service 3* + - 00      No information. + - 01      Spare. + - 10      Request, not essential. + - 11      Request, essential. + +- c) *Service 2* + - 00 No information. + - 01 Spare. + - 10 Request, not essential. + - 11 Request, essential. + - d) *Service 1* + - 00 No information. + - 01 Spare. + - 10 Request, not essential. + - 11 Request, essential. +- 2) If type (bit 1) equals 1 (response): +- a) *Network discard indicator* + - 0 No information. + - 1 User-to-user information discarded by the network. + - b) *Service 3* + - 00 No information. + - 01 Not provided. + - 10 Provided. + - 11 Spare. + - c) *Service 2* + - 00 No information. + - 01 Not provided. + - 10 Provided. + - 11 Spare. + - d) *Service 1* + - 00 No information. + - 01 Not provided. + - 10 Provided. + - 11 Spare. + +### 7.112 User-to-user information + +The format of the user-to-user information parameter field is shown in Figure 101. + +![](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | +|--------------------------|-----------------|---|----------|---|---|---|--------------|----------|---| +| ext.
1 | Spare | | | | | | More
data | 1 | | +| ext.
1 | Coding standard | | Reserved | | | | | | 2 | +| User-to-user information | | | | | | | | 3 | | +| | | | | | | | | : | | +| | | | | | | | | n | | + +Figure 101/Q.2763 – User-to-user information parameter field + +The following codes are used in the subfields of the user-to-user information parameter field: + +#### a) *Extension indicator (ext.)* + +- 0 Octet continues through the next octet (e.g. octet 1 to 1a). +- 1 Last octet. + +#### b) *More data identifier (octet 1)* + +- 0 No more data following. +- 1 More data following. + +#### c) *Coding standard (octet 2)* + +The codes to be used in the coding standard subfield are defined in the user-to-user information element in clause 1/Q.2957. + +#### d) *User-to-user information (octets 3 to n)* + +The codes to be used in the user-to-user information subfield are defined in the user-to-user information element in clause 1/Q.2957. + +# 8 B-ISDN User Part messages and codes + +In Tables 3 to 36, the format and coding of B-ISDN user part messages is specified. For each message, a list of the relevant parameters is given and for each parameter: + +- a reference to where the formatting and coding of the parameter content is specified; +- the length of the parameter. The value in the table includes the length, in octets, of the parameter name, length indicator, parameter compatibility information and parameter content. For variable length parameters the minimum and maximum length is indicated (see Note). + +NOTE – The length given for Q.2931 information elements is only informative. + +For each message type, the parameters need not be sent in the order specified in the tables. + +The routing label field, the message type field, the message length field and the message compatibility field belong to the general message format and are not shown explicitly in Tables 3 to 25. + +**Table 3/Q.2763 – Message type: Address complete** + +| Parameter | Reference
(subclause) | Length
(octets) | +|---------------------------------------------|----------------------------------|----------------------------| +| Access delivery information | 7.4 | 6 | +| Application generated identifier | 7.14 | 11 | +| Application transport (Note 2) | 7.15 | 6-? | +| Backward narrow-band interworking indicator | 7.21 | 6 | +| Call diversion information | 7.25 | 6 | +| Call diversion may occur | 7.26 | 6 | +| Called party's indicators | 7.35 | 6 | +| Cause indicators | 7.39 | 6 | +| Charge indicator | 7.42 | 5 | +| Conference treatment indicators | 7.46 | 6 | +| Connection identifier | 7.51 | 7 | +| Destination signalling identifier | 7.55 | 9 | +| Echo control information | 7.57 | 5 | +| In-band information indicator | 7.64 | 5 | +| MLPP user information | 7.75 | 5 | +| Narrow-band bearer capability | 7.76 | 11 | +| Narrow-band high layer compatibility | 7.77 | 11-? | +| Notification (Note 1) | 7.83 | 5 | +| Progress indicator | 7.90 | 11-? | +| Redirection number | 7.95 | 7-15 | +| Redirection number restriction | 7.96 | 5 | +| Report type | 7.98 | 7 | +| Segmentation indicator (national use) | 7.102 | 5 | +| Service activation | 7.103 | 6-? | +| UID action indicators | 7.109 | 6 | +| User-to-user indicators | 7.111 | 6 | +| User-to-user information | 7.112 | 8-137 | + +NOTE 1 – This parameter may be repeated. + +NOTE 2 – The message may contain one or more Application Transport Parameters (APP) referring to different Application Context Identifiers. + +**Table 4/Q.2763 – Message type: Answer** + +| Parameter | Reference
(subclause) | Length
(octets) | +|---------------------------------------------|----------------------------------|----------------------------| +| AAL parameters | 7.2 | 7-26 | +| Access delivery information | 7.4 | 6 | +| Additional ATM cell rate | 7.5 | 9-45 | +| Additional connected number | 7.7 | 7-15 | +| AESA for additional connected party | 7.9 | 27-? | +| AESA for connected party | 7.12 | 27-? | +| Application generated identifier | 7.14 | 11 | +| Application transport (Note 2) | 7.15 | 6-? | +| ATC setup parameters | 7.16 | 6-37 | +| ATM cell rate | 7.17 | 9-21 | +| Backward GVNS | 7.20 | 6 | +| Backward narrow-band interworking indicator | 7.21 | 6 | +| Broadband low layer information | 7.24 | 11-? | +| Call history information | 7.28 | 7 | +| Called party's indicators | 7.35 | 6 | +| CDVT | 7.41 | 6-23 | +| Charge indicator | 7.42 | 6 | +| Connected number | 7.48 | 7-16 | +| Connected sub-address | 7.49 | 8-28 | +| Connection identifier | 7.51 | 7 | +| Destination signalling identifier | 7.55 | 9 | +| Display information | 7.56 | 6-? | +| Echo control information | 7.57 | 65 | +| Extended Quality of Service | 7.60 | 7-26 | +| In-band information indicator | 7.64 | 6 | +| Link layer core | 7.66 | 6-30 | +| Link layer protocol | 7.67 | 6-12 | +| Narrow-band bearer capability | 7.76 | 12-? | +| Narrow-band high layer compatibility | 7.77 | 12-? | +| Narrow-band low layer compatibility | 7.78 | 12-? | +| Notification (Note 1) | 7.83 | 6 | +| OAM traffic descriptor | 7.84 | 7 | +| Progress indicator | 7.90 | 12-? | +| Redirection number | 7.95 | 8-15 | +| Redirection number restriction | 7.96 | 6 | +| Remote operations (national use) | 7.97 | 12-? | +| Report type | 7.98 | 7 | +| Report type prime | 7.99 | 11-? | +| Segmentation indicator (national use) | 7.102 | 6 | +| Service activation | 7.103 | 6 | +| Soft PVC called endpoint | 7.104 | 7-? | +| User-to-user indicators | 7.111 | 5 | +| User-to-user information | 7.112 | 8-137 | + +NOTE 1 – This parameter may be repeated. + +NOTE 2 – The message may contain one or more Application Transport Parameters (APP) referring to different Application Context Identifiers. + +**Table 5/Q.2763 – Message type: Application Transport** + +| Parameter | Reference (subclause) | Length (octets) | +|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------| +| Application transport (Note) | 7.15 | 8-? | +| NOTE – The message may contain one or more Application Transport Parameters (APP) referring to different Application Context Identifiers. | | | + +**Table 6/Q.2763 – Message type: Blocking/Reset/Unblocking** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Origination signalling identifier | 7.88 | 9 | +| Resource identifier | 7.100 | 8-11 | + +**Table 7/Q.2763 – Message type: Blocking acknowledgement/Reset acknowledgement/Unblocking acknowledgement** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 8 | + +**Table 8/Q.2763 – Message type: Call progress** + +| Parameter | Reference (subclause) | Length (octets) | +|---------------------------------------------|------------------------------|------------------------| +| Access delivery information | 7.4 | 5 | +| Additional connected number | 7.7 | 7-15 | +| Application generated identifier | 7.14 | 11 | +| Application transport (Note 2) | 7.15 | 6-? | +| Backward GVNS | 7.20 | 6 | +| Backward narrow-band interworking indicator | 7.21 | 5 | +| Call diversion information | 7.25 | 5 | +| Call diversion may occur | 7.26 | 5 | +| Call history information | 7.28 | 7 | +| Call transfer number | 7.30 | 8-? | +| Called party's indicators | 7.35 | 5 | +| Cause indicators | 7.39 | 7-? | +| Charge indicator | 7.42 | 6 | +| Conference treatment indicators | 7.46 | 6 | +| Connected number | 7.48 | 8-? | +| Destination signalling identifier | 7.55 | 8 | +| Echo control information | 7.57 | 6 | +| In-band information indicator | 7.64 | 5 | +| Narrow-band bearer capability | 7.76 | 12-? | +| Narrow-band high layer compatibility | 7.77 | 12-? | + +**Table 8/Q.2763 – Message type: Call progress (concluded)** + +| Parameter | Reference (subclause) | Length (octets) | +|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------| +| Notification (Note 1) | 7.83 | 6 | +| Progress indicator | 7.90 | 12-? | +| Redirection number | 7.95 | 8-16 | +| Redirection number restriction | 7.96 | 5 | +| Remote operations (national use) | 7.97 | 12-? | +| Report type | 7.98 | 7 | +| Segmentation indicator (national use) | 7.102 | 6 | +| Service activation | 7.103 | 6 | +| UID action indicators | 7.109 | 6 | +| User-to-user indicators | 7.111 | 6 | +| User-to-user information | 7.112 | 8-137 | +| NOTE 1 – This parameter may be repeated. | | | +| NOTE 2 – The message may contain one or more Application Transport Parameters (APP) referring to different Application Context Identifiers. | | | + +**Table 9/Q.2763 – Message Type: Call transfer** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------|------------------------------|------------------------| +| Call transfer number | 7.30 | 8-? | +| Calling party sub-address | 7.37 | 8-28 | +| Destination signalling identifier | 7.55 | 9 | +| Notification (Note) | 7.83 | 6 | +| NOTE – This parameter may be repeated. | | | + +**Table 10/Q.2763 – Message type: Connection Available (Note 1)** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| Notification (Note 2) | 7.83 | 6 | +| Report type | 7.98 | 6 | +| NOTE 1 – The former name of the message was Modify Confirm. Existing procedures are not influenced by this editorial change. However, the message may be used in additional procedure. | | | +| NOTE 2 – This parameter may be repeated. | | | + +**Table 11/Q.2763 – Message type: Confusion** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Cause indicators | 7.39 | 7-? | +| Destination signalling identifier | 7.55 | 9 | + +**Table 12/Q.2763 – Message type: Consistency check request** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Origination signalling identifier | 7.88 | 9 | +| Resource identifier | 7.100 | 7-11 | + +**Table 13/Q.2763 – Message type: Consistency check request acknowledgement** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| Origination signalling identifier | 7.88 | 9 | + +**Table 14/Q.2763 – Message type: Consistency check end** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | + +**Table 15/Q.2763 – Message type: Consistency check end acknowledgement** + +| Parameter | Reference (subclause) | Length (octets) | +|--------------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| Consistency check result information | 7.52 | 6 | + +**Table 16/Q.2763 – Message Type: Facility** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9-? | +| Notification | 7.83 | 6 | +| Remote operations (national use) | 7.97 | 12-? | + +**Table 17/Q.2763 – Message type: Forward transfer** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | + +**Table 18/Q.2763 – Message Type: Identification request** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| MCID request indicators | 7.72 | 6 | + +**Table 19/Q.2763 – Message Type: Identification response** + +| Parameter | Reference (subclause) | Length (octets) | +|---------------------------------------------|------------------------------|------------------------| +| Additional calling party number | 7.6 | 8-16 | +| Calling party number | 7.36 | 8-16 | +| Calling party sub-address | 7.37 | 8-28 | +| Charged party identification (national use) | 7.43 | 6-? | +| Destination signalling identifier | 7.55 | 9 | +| MCID response indicators | 7.71 | 6 | + +**Table 20/Q.2763 – Message type: Initial address** + +| Parameter | Reference (subclause) | Length (octets) | +|-------------------------------------|------------------------------|------------------------| +| AAL parameters | 7.2 | 7-26 | +| AAL prime parameters | 7.3 | 7-23 | +| Additional ATM cell rate | 7.5 | 9-45 | +| Additional calling party number | 7.6 | 7-16 | +| AESA for additional calling party | 7.8 | 27-? | +| AESA for called party | 7.10 | 27-? | +| AESA for calling party | 7.11 | 27-? | +| Alternative ATM cell rate | 7.13 | 9-28 | +| Application generated identifier | 7.14 | 11-? | +| Application transport (Note 2) | 7.15 | 6-? | +| ATC setup parameters | 7.16 | 6-37 | +| ATM cell rate | 7.17 | 9-22 | +| Automatic re-routing | 7.19 | 6 | +| Broadband bearer capability | 7.22 | 8-12 | +| Broadband high layer information | 7.23 | 7-? | +| Broadband low layer information | 7.24 | 11-? | +| Call diversion treatment indicators | 7.27 | 6 | +| Call offering treatment indicators | 7.29 | 6 | +| Called IN number | 7.32 | 8-15 | +| Called party number | 7.33 | 8-16 | +| Called party sub-address | 7.34 | 8-28 | +| Calling party number | 7.36 | 7-16 | +| Calling party sub-address | 7.37 | 8-28 | + +**Table 20/Q.2763 – Message type: Initial address (continued)** + +| Parameter | Reference (subclause) | Length (octets) | +|------------------------------------------------------|------------------------------|------------------------| +| Calling party's category | 7.38 | 6 | +| CCSS | 7.40 | 6 | +| CDVT | 7.41 | 6-23 | +| Closed User Group information | 7.44 | 10 | +| Collect call request | 7.45 | 6 | +| Conference treatment indicators | 7.46 | 6 | +| Connected line identity request | 7.47 | 6 | +| Connection element identifier | 7.50 | 7-9 | +| Connection identifier | 7.51 | 7 | +| Correlation ID | 7.53 | 6-? | +| Echo control information | 7.57 | 6 | +| End-to-end transit delay network generated indicator | 7.58 | 8-12 | +| Exclusive connection element identifier | 7.59 | 7 | +| Extended Quality of Service | 7.60 | 7-26 | +| Forward GVNS | 7.61 | 8 | +| Forward narrow-band interworking indicator | 7.62 | 6 | +| Hop counter | 7.63 | 6 | +| Leaf party type | 7.65 | 6 | +| Link layer core | 7.66 | 6-30 | +| Link layer protocol | 7.67 | 6-12 | +| Location number | 7.68 | 8-16 | +| Maximum end-to-end transit delay | 7.70 | 7 | +| Minimum ATM cell rate | 7.73 | 9-65 | +| MLPP precedence | 7.74 | 11 | +| Narrow-band bearer capability | 7.76 | 12-? | +| Narrow-band high layer compatibility | 7.77 | 12-? | +| Narrow-band low layer compatibility | 7.78 | 12-? | +| National/international call indicator | 7.79 | 6 | +| Network call correlation identifier | 7.80 | 14 | +| Network management controls | 7.82 | 6 | +| Notification (Note 1) | 7.83 | 5-6 | +| OAM traffic descriptor | 7.84 | 6-7 | +| Original called number | 7.85 | 6-15 | +| Origination connected link identifier | 7.86 | 9 | +| Origination ISC point code | 7.87 | 7 | +| Origination signalling identifier | 7.88 | 9 | +| Priority | 7.89 | 11 | +| Progress indicator | 7.90 | 12-? | +| Propagation delay counter | 7.91 | 7 | +| Quality of Service | 7.92 | 8 | + +**Table 20/Q.2763 – Message type: Initial address (concluded)** + +| Parameter | Reference (subclause) | Length (octets) | +|------------------------------------------|------------------------------|------------------------| +| Redirecting number | 7.93 | 7-16 | +| Redirection information | 7.94 | 6-8 | +| Remote operations | 7.97 | 12-? | +| Report type | 7.98 | 7 | +| Report type prime | 7.99 | 11-? | +| SCF ID | 7.101 | 6-? | +| Segmentation indicator (national use) | 7.102 | 6 | +| Service activation | 7.103 | 6 | +| Soft PVC called endpoint | 7.104 | 7-? | +| Soft PVC calling endpoint | 7.105 | 6-? | +| Transit network selection (national use) | 7.108 | 7-? | +| UID capabilities indicators | 7.110 | 6 | +| User-to-user indicators | 7.111 | 6 | +| User-to-user information | 7.112 | 8-137 | + +NOTE 1 – This parameter may be repeated. +NOTE 2 – The message may contain one or more Application Transport Parameters (APP) referring to different Application Context Identifiers. + +**Table 21/Q.2763 – Message type: IAM acknowledgement** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Connection element identifier | 7.50 | 7-9 | +| Destination signalling identifier | 7.55 | 9 | +| Origination signalling identifier | 7.88 | 9 | + +**Table 22/Q.2763 – Message type: IAM reject** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Automatic congestion level | 7.18 | 6 | +| Cause indicators | 7.39 | 7-? | +| Destination signalling identifier | 7.55 | 9 | + +**Table 23/Q.2763 – Message Type: Loop prevention** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Call transfer reference | 7.31 | 6 | +| Destination signalling identifier | 7.55 | 9 | +| Loop prevention indicators | 7.69 | 6 | + +**Table 24/Q.2763 – Message type: Modify acknowledgement** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------|------------------------------|------------------------| +| Additional ATM cell rate | 7.5 | 9-45 | +| ATM cell rate | 7.17 | 9-21 | +| Destination signalling identifier | 7.55 | 9 | +| Notification (Note) | 7.83 | 6 | +| Report type | 7.98 | 7 | +| NOTE – This parameter may be repeated. | | | + +**Table 25/Q.2763 – Message type: Modify reject** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------|------------------------------|------------------------| +| Cause indicators | 7.39 | 7 | +| Destination signalling identifier | 7.55 | 9 | +| Notification (Note) | 7.83 | 6 | +| NOTE – This parameter may be repeated. | | | + +**Table 26/Q.2763 – Message type: Modify request** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------|------------------------------|------------------------| +| Additional ATM cell rate | 7.5 | 9-45 | +| Alternative ATM cell rate | 7.13 | 9-45 | +| ATM cell rate | 7.17 | 9-21 | +| Destination signalling identifier | 7.55 | 9 | +| Minimum ATM cell rate | 7.73 | 9-65 | +| Notification (Note) | 7.83 | 6 | +| NOTE – This parameter may be repeated. | | | + +**Table 27/Q.2763 – Message type: Network resource management** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| Echo control information | 7.57 | 6 | + +**Table 28/Q.2763 – Message type: Release** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------|------------------------------|------------------------| +| Access delivery information | 7.4 | 6 | +| Application generated identifier | 7.14 | 11 | + +**Table 28/Q.2763 – Message type: Release (concluded)** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------|------------------------------|------------------------| +| Automatic congestion level | 7.18 | 6 | +| Automatic re-routing (crankback) | 7.19 | 6 | +| Cause indicators | 7.39 | 7-? | +| Destination signalling identifier | 7.55 | 9 | +| Display information | 7.56 | 6-? | +| Notification (Note) | 7.83 | 6 | +| Progress indicator | 7.90 | 12-? | +| Redirection information | 7.94 | 6-8 | +| Redirection number (national use) | 7.95 | 8-16 | +| Redirection number restriction | 7.96 | 6 | +| Remote operations (national use) | 7.97 | 8-? | +| Segmentation indicator (national use) | 7.102 | 6 | +| User-to-user indicators | 7.111 | 6 | +| User-to-user information | 7.112 | 8-137 | +| NOTE – This parameter may be repeated. | | | + +**Table 29/Q.2763 – Message type: Release complete** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Cause indicators | 7.39 | 7-? | +| Destination signalling identifier | 7.55 | 9 | + +**Table 30/Q.2763 – Message type: Segmentation (national use)** + +| Parameter | Reference (subclause) | Length (octets) | +|----------------------------------------|------------------------------|------------------------| +| Additional calling party number | 7.6 | 7-16 | +| Additional connected number | 7.7 | 7-16 | +| Broadband high layer information | 7.23 | 7-? | +| Broadband low layer information | 7.24 | 11-? | +| Called party sub-address | 7.34 | 8-28 | +| Calling party sub-address | 7.37 | 7-28 | +| Connected sub-address | 7.49 | 7-28 | +| Destination signalling identifier | 7.55 | 9 | +| Narrow-band high layer compatibility | 7.77 | 12-? | +| Narrow-band low layer compatibility | 7.78 | 12-? | +| Notification (Note) | 7.83 | 6 | +| Progress indicator | 7.90 | 12-? | +| User-to-user information | 7.112 | 8-137 | +| NOTE – This parameter may be repeated. | | | + +**Table 31/Q.2763 – Message type: Subsequent address** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| Subsequent number | 7.106 | 7-15 | + +**Table 32/Q.2763 – Message type: Suspend Resume** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| Suspend/Resume indicators | 7.107 | 6 | + +**Table 33/Q.2763 – Message type: User part available** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | + +**Table 34/Q.2763 – Message type: User part test** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Origination signalling identifier | 7.88 | 9 | + +**Table 35/Q.2763 – Message type: User-to-user information** + +| Parameter | Reference (subclause) | Length (octets) | +|-----------------------------------|------------------------------|------------------------| +| Destination signalling identifier | 7.55 | 9 | +| User-to-user indicators | 7.111 | 6 | +| User-to-user information | 7.112 | 8-136 | + +**Table 36/Q.2763 – Message type: Pre-release information** + +| Parameter | Reference (subclause) | Length (octets) | +|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------| +| Application transport (Note) | 7.15 | 8-? | +| NOTE – The message may contain one or more Application Transport Parameters (APP) referring to different Application Context Identifiers. | | | + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0317016f1967843fe2643d09bd7bee9d_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0317016f1967843fe2643d09bd7bee9d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49372c3f1dcc554d39837963d46bc8733a3de2e5 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0317016f1967843fe2643d09bd7bee9d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b02bfd7b673a4cb8a9d84499f2436d769e17d5402d02c4c9e5f2f90f09976a +size 169673 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/09797d4289ec96309d21a9a993153dab_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/09797d4289ec96309d21a9a993153dab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec606e3b2534a02dadf7792532f828f2ab8887e --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/09797d4289ec96309d21a9a993153dab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc86b44daa232a8ba9f8d60a1caf49d96bc71b9f6336df71d583fa56880735f +size 90490 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0ad1b90f313a822e42d66a872e981b42_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0ad1b90f313a822e42d66a872e981b42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79e27e949d70644ff4c8ccbde5140155d8fe2f49 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0ad1b90f313a822e42d66a872e981b42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27db8458d50c3dc46f27f6fe0e9c6ee0d4d978f5a8227b0c1e80229282ff0f7a +size 15118 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0fa729588727923c923952d3401a049d_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0fa729588727923c923952d3401a049d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44962bbcfb31ca199ff666691c156a0391dc5589 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/0fa729588727923c923952d3401a049d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d44f79e5a4bc65da8d1ad31f4e5dbac2bf670e0989cc6713a65dc2f4fbe284c +size 1947 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1187dbd674a100960ed23efa54ccd6c1_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1187dbd674a100960ed23efa54ccd6c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78ee10e6509ea92e81a9f4e2fcd2a122620f9c07 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1187dbd674a100960ed23efa54ccd6c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd1ecdded4b5a5fa2c263125d9b5c2b861e0966c8ced3ce83858343a9fa1462b +size 3537 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1582c665ca9405e127473c291eaed480_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1582c665ca9405e127473c291eaed480_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..208f492150081bc23e1099b9b6f8bd21ca15819c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1582c665ca9405e127473c291eaed480_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e3bb07682b9a0efe451072146d597b2fe0693beb000e93537159b35889e8d40 +size 35896 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/176d27d455c3c2238fb11a27b63276fd_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/176d27d455c3c2238fb11a27b63276fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..664d2b4a7dbeb9e3a9445f81d96d7c95be7d5e13 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/176d27d455c3c2238fb11a27b63276fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dfb83ae59da3442dfa97dac61169d3d7c0c814d021cb243c086a8a8aff97375 +size 1947 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1d9db146e81fd7b66f1a05cce57c7112_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1d9db146e81fd7b66f1a05cce57c7112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8bd244d6fad409dcb6304b56db55617c5a5ebe2 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1d9db146e81fd7b66f1a05cce57c7112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbafb06df8ca387372142a8cbd596d43e3b5b1f783d7806f4417ec08a6e261b0 +size 167315 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..991c30454b452c13d57735ed93ef5f7e89f88908 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e737a5f4152004b23aeb7e817ea1066b11760023a1fcb907db146405ce5a036 +size 123287 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02c6c5f9eade3657a4ab472286aa57170f6d8c9c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4f38a2a8fa53ca95f17d8fae591316d3716634f9e93609479ec2409e56f9d8e +size 121531 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/23e6f8e908eb73b54a419d58740a33bb_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/23e6f8e908eb73b54a419d58740a33bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62700846dda8db7e5d3372b4859ebc989adf6c51 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/23e6f8e908eb73b54a419d58740a33bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b3313e41f9c1ab8423b7c44caa5c7e71c2df34aa328dc3372f9c47981c82946 +size 32491 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e9e86a8a5ba5aec457b0b7b1d9db236abe32eb3 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb03831354d2879d16e03ab9b93c4632b1214958f462fba9c0b5b5301a63e9fa +size 105959 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6738daa4c63ab61f41881657b0076cb6fb7d764 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f0c2520323bfec6255808c9f245cd2d44bd6c5d87aac95343a9927be97fda23 +size 80765 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84bdf05a64224190b9de2f7465800ac252f8c6e7 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3dd98b5cb2f3cd4097c7add4b8a9659ed243cf0823402294c2ba2a31f07af59 +size 141223 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2afb714545e5b9b7365878ba1006e9ff_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2afb714545e5b9b7365878ba1006e9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422cbbdf7e97b77aa8b74d70047777c05ee32b51 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2afb714545e5b9b7365878ba1006e9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdb3d775c9c02bdf14ec0d9f8200bd25da71fe7a0b14cd182a77348597eded64 +size 1591 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66e575fb2a3f743d1f988d658ae8d752fbf4fb8b --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7749de28e2b26d93c59dcfd2a7e2aac18eab47013aaead2c6d3f5bc5cd156ee +size 117817 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daccb0dcbc4e6217a00e811f35f4e6d953a24a1c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cb7746097e062fe3cc0910334b52ed71f3e605b091a73fdbe7dfb6c9b4ac235 +size 84507 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1565b51fbf0082fa80188c6b6bef4abc335b8ca --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f67c8686f7cbd4fe6588d30d10ee5e2ecef089fea369fbb5a9bbf3602386386c +size 87646 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01b4a30fd8b85a28556f62a54719e5145abb0d99 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:458be2695c47241f5d3291441123e4c5dccb9a98fe0871cb0aa3ef35b24f5e94 +size 88803 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3d13999d5257e24e629f65f28bf10251_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3d13999d5257e24e629f65f28bf10251_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c7888ee54b24a823feae49c25dfa641245a5908 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3d13999d5257e24e629f65f28bf10251_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c7ab9b8f18c2342d84bc0fd64117d865ccdb9a252d649442a190ca5c7aac43 +size 97621 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3e69d35c155565a8549acb37ee9f80be_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3e69d35c155565a8549acb37ee9f80be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55beb2a388d92f2d262f8b2aecb6e49d41e2b4c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3e69d35c155565a8549acb37ee9f80be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476c468ce78cd940441aea240ae1d91f5d2e1b916a18fc47f729014d4c1c82ba +size 1736 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c49b78f6630b47d38650dc9a5becc6b77420459e --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe695df0f42e49d4211290a32b8502569fcf80a1f98ff9a4ff5a3e45847a0bc0 +size 57430 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63b1159915cf60735a806cb6fc825cd31fc7fd2f --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ada46a48f716a0ee6a43d3e2526a22e9dcaed6e4bac8e9cec761713eae11fd14 +size 24125 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd39da68e3d1fade68e11b00a76782357a933f9d --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43e26f3f12e0337edfab11835feedb994480cafb48b0337e9bc89d6773e61d10 +size 106214 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f7d65fcd38a5c09967474a16bc0184a03374894 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02f84efab3f96363596a28c5e9a42cfeb5b4282f03407c05610d267e5c47c4f7 +size 36320 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef85ab6f5834db3c5712c3cd2158065b7e7bffe0 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42dc03ee012a62ed50c36be69a19b9fe2453a452a0ca6eb448821ea14409e2a9 +size 76095 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5496c3d362352cb64af48bb3a5dd20f5_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5496c3d362352cb64af48bb3a5dd20f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a297bc9213bacc6f1247d7129c2d6b1217ba2d12 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5496c3d362352cb64af48bb3a5dd20f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db0f834c03755fa53af24edcd98c6323f6e5a6c32023bb73bf72584459bfd703 +size 49209 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91c9917fa2f750b9a9b3459ca166045ebba4b6c1 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbab401d419cf02158f9bcc7c61abaf7633cf8994dac378fb03461ca657e4487 +size 85931 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5924b46d5505f278351a0c1fa29202c6_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5924b46d5505f278351a0c1fa29202c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23d5dd83ab0ba0c3dcee3c5f1ad5054d5e80411a --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5924b46d5505f278351a0c1fa29202c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9b7b07c551826495a42bc74da302b5998946e434e5cb0d64e92d17777d942ef +size 65541 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5f7b02749ab85c5e65d6762767ab6d97_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5f7b02749ab85c5e65d6762767ab6d97_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39a26e6bc362d3ab6f99e5c6ead2d5368db7eda9 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/5f7b02749ab85c5e65d6762767ab6d97_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfcf45b2ae6caaa9fa45ce5204e4e93353724b121196f193919ef42a7332fdf3 +size 120532 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/625d1a3f96b1d8f99a23fdaf0720608a_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/625d1a3f96b1d8f99a23fdaf0720608a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55beb2a388d92f2d262f8b2aecb6e49d41e2b4c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/625d1a3f96b1d8f99a23fdaf0720608a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476c468ce78cd940441aea240ae1d91f5d2e1b916a18fc47f729014d4c1c82ba +size 1736 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d6f984552594ea4bcbb154d8ef6db599c41369 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee4d7e607563c0cf79bf1edb41d02d43571f03a72fd3977ecfd3d9228e0fbca7 +size 119939 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d10ac550acd113c200c1947a5ccb644149af2de6 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a077ffe745e22262851762bdae637a0245ae41ba0f474a9fdca3654b39d9218a +size 70374 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb825d4333f9392bbb1329aac556c96e5871a015 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a9be1ac91104c19a8ee35ffddbc39d77cb782b94618603203d0d5d285b10c62 +size 45479 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ae1e890c85d35668059ca72af4f1652_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ae1e890c85d35668059ca72af4f1652_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422cbbdf7e97b77aa8b74d70047777c05ee32b51 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ae1e890c85d35668059ca72af4f1652_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdb3d775c9c02bdf14ec0d9f8200bd25da71fe7a0b14cd182a77348597eded64 +size 1591 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ba19a99fb96f0139505f0992544a2cf_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ba19a99fb96f0139505f0992544a2cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbc14818d4dbcec9a0658159f2766ffc40e49dba --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ba19a99fb96f0139505f0992544a2cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2070fa521117f219dd42b0f1a42023b9448754582b20679f6602f9d3cd0a104 +size 42082 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6c952ad721b91d47590055bdc347541f_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6c952ad721b91d47590055bdc347541f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b315c2258c6ef41eaf4aed9d6df1e74efa0020ce --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6c952ad721b91d47590055bdc347541f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e8a9de07fa01c2e8ff7c77acfb63afdaf95b2ff3a8f279c21ecbed4bca3470d +size 1800 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9fba18234afc6284c11abf738611f0ae2e4bf85 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4840986b954fb9e18df141d235f00d286547e5f4061118192fa68e4fd2253b2f +size 108172 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b29c03b0b64c4f8704a714b29cb0930d37b8088 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d28945925d4b06a075fd0d9657d40ce864927fe33da27b16b2be1d968ba9b3be +size 37480 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97add025a2aea8fbc4f6a687ec6c1f8e87a2ed19 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c40bdbe6ca94e8877ae26143d3784ac216d2571095adb8f20b5c83811df2e56d +size 113034 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7e5f0aeb4d1adb2bbeed7cdd265a1707_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7e5f0aeb4d1adb2bbeed7cdd265a1707_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c14bd4288a144e8c2a3553aae3e20f0e213a0dd --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7e5f0aeb4d1adb2bbeed7cdd265a1707_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0516860858f17c93a6185c3ef77dd146be9188759dd0acf7309567f256a5b3c +size 36811 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7fbe26b3cdf18151ed643c6b00861743_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7fbe26b3cdf18151ed643c6b00861743_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55beb2a388d92f2d262f8b2aecb6e49d41e2b4c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/7fbe26b3cdf18151ed643c6b00861743_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476c468ce78cd940441aea240ae1d91f5d2e1b916a18fc47f729014d4c1c82ba +size 1736 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/851844cd254cc8d327dc1782d2d79a6b_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/851844cd254cc8d327dc1782d2d79a6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edce314cfdd87e68968a7f33004e5dcdf1d6f736 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/851844cd254cc8d327dc1782d2d79a6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a07c36c8f0e44388d21ee6bb4250375d1f8e8c220aa60aaa13235f8c698710d6 +size 26688 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0a8f0ab87656ea13d5c1917272af03fd6d823c3 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c85ca65c5e7cd83a99d3e6cdf6c6bfcb2b3cb869635f084ba079b172b2279429 +size 83034 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1565fea0501db30dd5a81f67f066e8d274e2019 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a01be443a7576e24e05e9ccbdfc856ae63fe49780ea299643738e498cded137 +size 103128 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/893d65bf826925a7283359b1672010a0_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/893d65bf826925a7283359b1672010a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6e17c097440007f9a02e1a3c111fc0237fc6891 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/893d65bf826925a7283359b1672010a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:457dc2068a493fa38f7e5e737235a25ad76e41f90f9d2bcb3bc15aebf6121bb9 +size 49834 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00db40a553b56a65085d95201b37f30ca5cf382c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30691a4f492a4f78511da73c6221b57b3a2c21e4a1c275271ed0df3bd977b367 +size 65802 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/9958beca8f65818eb0ff893647af94de_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/9958beca8f65818eb0ff893647af94de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ba2576eba642c0656e90a94cd12f1b05e0291a7 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/9958beca8f65818eb0ff893647af94de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14948da9eafb64ba3c91315669bd770c6276b44d6878d64a9a60d379a4bbc537 +size 47423 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd5cb355a36bfce209d7122e5230bda986544034 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:396608afd1040c382abb5569e355e5971d8b5bbc7eec2aae7e33242b3a284003 +size 116856 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a4f38f6d6671e2e60ea445998e982deb_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a4f38f6d6671e2e60ea445998e982deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6beed782e042cde7de42cfd10cb8ddc886d5defd --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a4f38f6d6671e2e60ea445998e982deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59c68f77f44f008afcf3dda6247cc13cd26a553b319ea094c85140ba9fef75e0 +size 34000 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a95e1cadd35043c9df8d30c640620d6c8a998350 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d246d552b16de32c5004a079b3d09233129f57bbf47c53c8c77b7b3d1cd60625 +size 115563 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99e81dc1e8429168578fde32612d867e8c74d364 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21caa38cc410fbab4f1e1f6ebf6da09bf14c43f31bb7c10620f84ba4cf1120eb +size 32137 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9c39ed02b52f4e2746bfd8643bd3da2971e1517 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18a60bd73d2e60cbb3ce6648b648632e6294afb15ab3a2db78450ea3e5e1a761 +size 49585 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b1123ddbaa09fda65dcdf91d8caaa0f2_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b1123ddbaa09fda65dcdf91d8caaa0f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c22b25cd5544666e6289ffe0dbd2c337a2566ee3 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b1123ddbaa09fda65dcdf91d8caaa0f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:192523f6cba0e6144fa6db2ac21e84250c9f54b97e88d4402843f477ca8d5716 +size 40793 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b54b769d67164910c7c5b2a0ea74257b_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b54b769d67164910c7c5b2a0ea74257b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde765f17eb8fecbebb1ad4765ad793868bd72d2 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/b54b769d67164910c7c5b2a0ea74257b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f67ca3b78f6e7ad53eb2a4112c5e1b6919d59a66d3c0f15c7bd105117cb218c9 +size 84937 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45d64393d6a82354cef41eae07a4cb560301477b --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29dae14f193718e52ff56824aa0c3c909a2abee6d3214193f966416f609b89e1 +size 123557 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/bc38deb2fec0ea26c5b2e0ed8884d852_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/bc38deb2fec0ea26c5b2e0ed8884d852_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efbf3ac766ff5a2998108e3a29482ef07aa0744b --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/bc38deb2fec0ea26c5b2e0ed8884d852_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30eefffbf7f318bbdd172283b3db2a4e8bdfd35469c7e81cac08adc74edf4c34 +size 173700 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/c355b8056bdd4728357d7d5ed18792ca_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/c355b8056bdd4728357d7d5ed18792ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3775e713f77045e93723c32ea5adba6f70a5ba74 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/c355b8056bdd4728357d7d5ed18792ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffe9d4d11c204140f4581a0d6b28aaedd4241db20f631dd0d05e9a326263b2c7 +size 116340 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d09f5b5442d0077fc561f51279aa3797e2468376 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:325ca6ea4591fe047247a136eb1bb55b902f00e498c39853470977fceba3876d +size 43263 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/ced908d57017bef4ba4425b7b4212120_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/ced908d57017bef4ba4425b7b4212120_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aebcf9a5c4eb404711e8eade88a3c6df7189f31 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/ced908d57017bef4ba4425b7b4212120_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5e59ef11f898c39a58d4af00599c24f7ba2722dc2c6c51f7197f6daced35bb2 +size 35290 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/cf03eff1218a8cc1be6b05de892162de_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/cf03eff1218a8cc1be6b05de892162de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7ee9804402e36c6d1dba906af7a0af375f09614 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/cf03eff1218a8cc1be6b05de892162de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f81aabf3451d86e4136bced2720da493db7ccac715fedcab678554cca58185b7 +size 100565 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d2be8ff93d90c237c2e257213d8be3ba8dda7c1 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8770cc95f7e5f3369a9514a4c1e0f773e27dcce713aed2cc01118519affbdda8 +size 105572 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f1fe9f26f80376bfd424f8097391505e881fc3 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6905063c3c2801911d004897e8a8d06d3a444d1719de9e6c4c2f33aff1263042 +size 28325 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d455e47a6d660a3cc29a125a2cbe355b_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d455e47a6d660a3cc29a125a2cbe355b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf80e7b97350eb5d66fd50582e698c80036534dc --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d455e47a6d660a3cc29a125a2cbe355b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bda3edc755a93cd3530f890a22f0a469ac419d758b2e8ab4dd6f1c87d1644b18 +size 30143 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d694ab7c4f5cde0f1f80de3ff765700d_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d694ab7c4f5cde0f1f80de3ff765700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55beb2a388d92f2d262f8b2aecb6e49d41e2b4c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d694ab7c4f5cde0f1f80de3ff765700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476c468ce78cd940441aea240ae1d91f5d2e1b916a18fc47f729014d4c1c82ba +size 1736 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec3a62629ab3bc905b0de57f606ed923f42e0952 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a0730ea82c60fff522907a2a52580b53482761ddde3fb49e555d165efebf57f +size 106930 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0931d88658d98bc31bd65dc38c0ae21bf195370c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3994baf08419453e78d43e47f832cda4ac3b9146dbb35e4ff650d98c00aa1dda +size 128308 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/e67401bb970e10780dd4086d67c8195f_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/e67401bb970e10780dd4086d67c8195f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..067b2b13ca3e0044a12f4a9fe35cc268908dc9a3 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/e67401bb970e10780dd4086d67c8195f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82edd72351d4b1494580f1c7abb7c43b9d6cafc2dff98a0775436e87809ff862 +size 109789 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..396f6f7faf4ffb8a99851339ef03947bae7ee505 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16d523c06fafe6bb4f352aa4aad3f4d1f88358d1d895b8b2aad5e0a5c1dbc12e +size 71619 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/ecae674475cecdd0962200a5d1e2591e_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/ecae674475cecdd0962200a5d1e2591e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..134565d7a7e4be1dcdbdda7df18a90c5aaf34161 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/ecae674475cecdd0962200a5d1e2591e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec16ce6032e2a9b444c620a81fd09bf0f86262cb2a5c9720e916c77f79c65510 +size 81138 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/f97782852c7474fa58fcf5cd0bd96a7e_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/f97782852c7474fa58fcf5cd0bd96a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb709bd6cbb93327bfda633cd5841b4202134f93 --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/f97782852c7474fa58fcf5cd0bd96a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:350245fa5bbfd9311138fba56c1343558d056de5cca8593578594ac3ceff937f +size 50102 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/fce98b99e3d48dca71e6e002cb885ccd_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/fce98b99e3d48dca71e6e002cb885ccd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55beb2a388d92f2d262f8b2aecb6e49d41e2b4c --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/fce98b99e3d48dca71e6e002cb885ccd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476c468ce78cd940441aea240ae1d91f5d2e1b916a18fc47f729014d4c1c82ba +size 1736 diff --git a/marked/Q/T-REC-Q.2764-199912-I_PDF-E/fdf88c2e46b55435592798baf44ac02d_img.jpg b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/fdf88c2e46b55435592798baf44ac02d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dd0b1ec15479d8b0a177551791608b30cf1c3ef --- /dev/null +++ b/marked/Q/T-REC-Q.2764-199912-I_PDF-E/fdf88c2e46b55435592798baf44ac02d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:855438aa77f2ec6d42a91922f98296169a1828575ac45e054869994d0ddb0f8f +size 46409 diff --git a/marked/Q/T-REC-Q.28-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.28-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.28-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ded81cab931598f1dbd479ae8af3642261aba6a6 --- /dev/null +++ b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:033f75d358bba673f890ff8c1d3a43d89be710a07223bdd3bee8a1128bf4cb15 +size 47413 diff --git a/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c17b38d4929f980db005c87f90ee5a68bb93d15e --- /dev/null +++ b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1eedc9c17ca261c3ac5d7f3620b46148d9e2e1ade175ca581dc84dc1ccdf5f5b +size 8246 diff --git a/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/b05a8a3551db31147979064952179990_img.jpg b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/b05a8a3551db31147979064952179990_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..309fc1ebfe3e0024eb32885eb969f27ecc9a1bb4 --- /dev/null +++ b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/b05a8a3551db31147979064952179990_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcc1e93f41490f16ec0f1739e0036fc82f63d6e3ce484b773e014ade0ba2e43c +size 30880 diff --git a/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96f5e98afaaa2c6362df54c1d8b0eff584e793a8 --- /dev/null +++ b/marked/Q/T-REC-Q.2941.1-199709-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a55db73bf0492fb403cfedec4e71dee2d7b776b212db2a0e5a3d7b9c94b442f +size 87534 diff --git a/marked/Q/T-REC-Q.2962D-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2962D-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22ae9ebdea9b51453430f8f1eec96d3dbc3b7c43 --- /dev/null +++ b/marked/Q/T-REC-Q.2962D-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e10c8f5c58c1323c42c6cd1928d748c09cc309115dcd821f1e68faff41795380 +size 8357 diff --git a/marked/Q/T-REC-Q.2962D-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2962D-200012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9d1f5f7b0c843ef3d46f19421bc744ef41f19d7b --- /dev/null +++ b/marked/Q/T-REC-Q.2962D-200012-I_PDF-E/raw.md @@ -0,0 +1,257 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2962 D** + +(12/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Digital subscriber signalling system No. 2 – +Connection characteristics negotiation +during call/connection establishment phase: +Abstract test suite (ATS) and partial protocol +implementation extra information for +testing (PIXIT) proforma for the user** + +ITU-T Recommendation Q.2962 D + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| General aspects | Q.2000-Q.2099 | +| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 | +| Signalling network protocols | Q.2200-Q.2299 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 | +| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma for the user** + +## **Summary** + +This Recommendation specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [6]) of implementations conforming to the procedures for the handling of the connection characteristics negotiation during call/connection establishment phase of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2962 [1]. + +Other Recommendations of the Q.2962 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation. + +NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in English. + +###### **Source** + +ITU-T Recommendation Q.2962 D was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +| | Page | +|----------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References ..... | 1 | +| 3 Endorsement..... | 2 | +| 4 Coverage ..... | 2 | +| 5 Modifications ..... | 2 | +| 5.1 General modifications..... | 2 | +| 5.2 Technical modifications..... | 3 | +| 5.2.1 AAL parameters IE..... | 3 | +| Appendix I – Bibliography ..... | 3 | + +###### **Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma for the user** + +# 1 Scope + +This Recommendation specifies the Test Suite Structure and Test Purposes (TSS & TP) for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [6]) of implementations conforming to the procedures for the handling of the connection characteristics negotiation during call/connection establishment phase of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2962 [1]. + +Other Recommendations of the Q.2962 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation. + +This Recommendation is applicable to equipment, supporting connection characteristics negotiation during call/connection establishment phase, to be attached at either side of a TB reference point or coincident SB and TB reference point when used as an access to the public B-ISDN. + +The ATS realizes test purposes identified in the TSS & TP part of the Recommendation and groups them according to the test suite structure given in the TSS & TP. Test purposes defined in the TSS & TP part but not testable are identified in this Recommendation. + +The supplier of a protocol implementation that is claimed to conform to ITU-T Q.2962 [1] is required to complete a copy of the PICS proforma and the PIXIT proforma provided by the testlab. The PIXIT proforma shall contain the tables identified in the partial PIXIT proforma part of this Recommendation and may contain additional information required by the testlab to be able to appropriately execute the test campaign. + +# 2 References + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.2962 (1998), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase.* +- [2] ITU-T Q.2962 B (2000), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Protocol implementation conformance statement (PICS) proforma.* +- [3] ITU-T Q.2962 C (2000), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Test suite structure and test purposes (TSS & TP) for the user.* +- [4] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control.* + +- [5] ITU-T Q.2931 B (2000), Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control: Protocol implementation conformance statement (PICS) proforma. +- [6] ITU-T I.413 (1993), *B-ISDN user-network interface*. +- [7] ETSI EN 301 067-4 V2.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) Protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user*. + +# 3 Endorsement + +The text of ETSI EN 301 067-4 [7] was approved by ITU-T as Recommendation Q.2962 D with agreed modifications as given below. + +NOTE – Underlining and/or strike-out is used to highlight new or deleted text where detailed indication of modifications is necessary. + +# 4 Coverage + +This part of the Recommendation covers ITU-T Q.2962 [1]. + +# 5 Modifications + +## 5.1 General modifications + +Throughout the text of ETSI EN 301 067-4 [7] replace references and text as shown in the following table: + +| Reference in ETSI EN 301 067-4 | Modified reference | +|--------------------------------|--------------------| +| EN 300 443-1 | ITU-T Q.2931 | +| EN 300 443-2 | ITU-T Q.2931 B | +| EN 301 067-1 | ITU-T Q.2962 | +| EN 301 067-2 | ITU-T Q.2962 B | +| EN 301 067-3 | ITU-T Q.2962 C | +| EN 301 067-4 | ITU-T Q.2962 D | +| Standard | Recommendation | + +###### Page 5, Intellectual Property Rights + +Delete the whole section. + +### Page 5, Foreword + +Delete the whole Foreword. + +NOTE 1 – It is replaced by the Foreword of this Recommendation. + +### Page 6, Clause 1 Scope + +Replace the whole clause with the following: + +#### **"1 Scope** + +See clause 1 Scope of this Recommendation above." + +###### **Page 19, Bibliography** + +Delete the whole clause "Bibliography". + +NOTE 2 – Replaced by Appendix I "Bibliography" of this Recommendation. + +###### **Page 20, History** + +Delete the whole clause "History". + +## **5.2 Technical modifications** + +NOTE – Modifications in the TTCN part of this Recommendation are described in terms of changes in the TTCN.GR representation. + +#### **5.2.1 AAL parameters IE** + +In the TTCN, Declarations Part, Test Suite Type Definitions, ASN.1 Type Definitions alter definition for the type "AAL\_contents" as below: + +"OCTET STRING(SIZE(1.. ~~20~~ 17))". + +NOTE – This limitation may be removed in later versions of the TTCN part. + +# **APPENDIX I** + +## **Bibliography** + +- [A] ETSI EN 300 443-1 V1.3.5 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 1: Protocol specification.* +- [B] ETSI EN 301 067-1 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 1: Protocol specification.* +- [C] ETSI EN 301 067-2 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 2: Protocol Implementation Conformance Statement (PICS) proforma.* +- [D] ETSI EN 301 067-3 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.* +- [E] ETSI EN 301 067-5 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.* + +- [F] ETSI EN 301 067-6 V2.1.1 (2000), Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network. +- [G] ETSI ETS 300 406 (1995), *Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology.* + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2971C-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2971C-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f6080ab08347bd3ec724aa3bffdb331135d08a71 --- /dev/null +++ b/marked/Q/T-REC-Q.2971C-199912-I_PDF-E/raw.md @@ -0,0 +1,285 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2971 C** + +(12/1999) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Digital Subscriber signalling system No. 2 – +User-network interface layer 3 specification for +point-to-multipoint call/connection control: Test +Suite Structure and Test Purposes (TSS & TP) +for the user** + +ITU-T Recommendation Q.2971 C + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| General aspects | Q.2000-Q.2099 | +| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 | +| Signalling network protocols | Q.2200-Q.2299 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 | +| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **Digital subscriber signalling system No. 2 – User-network interface layer 3 specification for point-to-multipoint call/connection control: Test Suite Structure and Test Purposes (TSS & TP) for the user** + +## **Summary** + +This ITU-T Recommendation specifies Test Suite Structure and Test Purposes (TSS & TP) for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T Recommendation I.413 [2]) of implementations conforming to the procedures for the support of point-to-multipoint switched virtual channel connections, between a root and multiple leaves of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Recommendation Q.2971 [1]. + +Further parts of this ITU-T Recommendation specify the Protocol Implementation Conformance Statement (PICS) proforma and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this ITU-T Recommendation. + +###### **Source** + +ITU-T Recommendation Q.2971 C was prepared by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 3 December 1999. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|--------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Endorsement ..... | 1 | +| 4 Coverage ..... | 2 | +| 5 Modifications ..... | 2 | +| Appendix I – Bibliography..... | 4 | + + + +###### **Digital subscriber signalling system No. 2 – User-network interface layer 3 specification for point-to-multipoint call/connection control: Test Suite Structure and Test Purposes (TSS & TP) for the user** + +# 1 Scope + +This ITU-T Recommendation specifies Test Suite Structure and Test Purposes (TSS & TP) for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T Recommendation I.413 [2]) of implementations conforming to the procedures for the support of point-to-multipoint switched virtual channel connections, between a root and multiple leaves of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Recommendation Q.2971 [1]. + +Further parts of this ITU-T Recommendation specify the Protocol Implementation Conformance Statement (PICS) proforma and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this ITU-T Recommendation. + +This Recommendation is applicable to equipment, supporting point-to-multipoint calls/connections, to be attached at either side of a TB reference point or coincident SB and TB reference point when used as an access to the public B-ISDN. + +The test suite structure provides the grouping of tests in the test suite, the test purposes part is a list of test purposes realized in the ATS part of the Recommendation. Test purposes are generated from the protocol specification, refers to observable events only but gives no guarantee that all test purpose defined is testable. Untestable test purposes are identified in the ATS part. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation Q.2971 (1995), *Digital subscriber signalling system No. 2 – User-Network interface layer 3 specification for point-to-multipoint call/connection control.* +- [2] ITU-T Recommendation I.413 (1993), *B-ISDN user-network interface.* +- [3] ETSI ETS 300 771-3 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for point-to-multipoint call/bearer control; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.* + +# 3 Endorsement + +The text of ETS 300 771-3 [3] was approved by ITU-T as Recommendation Q.2971 C with agreed modifications as given below. + +--- + +1 ITU-T Recommendation Q.2971 C was previously numbered as Q.2971 *ter* during the approval process. + +NOTE – New or modified text is indicated using sidebars. In addition, double underlining and/or strike-out are used to highlight detailed modifications where necessary. + +# 4 Coverage + +This ITU-T Recommendation covers protocol specification of Q.2971 [1] as modified by Q.2971 Corrigendum 1 (12/99). + +# 5 Modifications + +Throughout the text of ETSI Standard ETS 300 771-3 [3] replace references and expressions as shown in the following table: + +| Reference in ETS 300 771-3 | Modified reference | +|----------------------------|-------------------------------------| +| ETS 300 771 | Recommendation of the Q.2971-series | +| ETS 300 771-1 | ITU-T Recommendation Q.2971 (10/95) | +| ETS | Recommendation | +| standard | Recommendation | + +### Other modifications + +###### Page 5, Foreword + +Delete the whole Foreword. + +NOTE – It is replaced by the Foreword of this ITU-T Recommendation. + +###### Page 7, clause 1 Scope + +Replace the whole clause with the following: + +###### "1 Scope + +See clause 1 Scope of this Recommendation above." + +###### Page 7, clause 2 Normative References + +Modify reference [2] as below: + +[2] ~~Void"ETS 300 771-2: 2: Broadband Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B ISDN user network interface layer 3 specification for point to multipoint call/bearer control; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".~~ + +###### Page 11, subclause 6.1.3 + +Modify the subclause as below: + +#### "6.1.3 Test strategy + +As the base standard ETS 300 771-1 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base ~~ITU-T Recommendation~~ standard and PICS specification ETS 300 771-2 [2]. The criteria applied include the following: + +- only the requirements from the point of view of the TB or coincident SB and TB reference point are considered; +- whether or not a test case can be built from the TP is not considered." + +###### **Pages 52 to 53, subclause 6.2.1.5.9, test purposes L3MU\_21\_37 to L3MU\_21\_39** + +Modify test purposes as below: + +###### **"L3MU\_21\_37** + +Ensure that the IUT in U4 and P4 for party 1 and P4 for party 2, on receipt of a DROP PARTY message (Optional information element with content error present, IE instruction field flag = IE instruction field not significant, Endpoint reference value = party 2), + +optionally sends a STATUS message (Cause = value 100 and optional diagnostics field carrying correct IE identifier, Call state value = 4, Endpoint reference value = party 2, Endpoint reference party state = 6) followed by a DROP PARTY ACKNOWLEDGE message and optionally sends a STATUS message (Cause value = 100, Call state value = 4, Endpoint reference value = party 2, Endpoint reference party state = 6 or 0 dependant on the order of transmission), remains in P4 for party 1, enters P0 for party 2 and remains in U4. + +###### **L3MU\_21\_38** + +Ensure that the IUT in U10 and P7 for party 1 and P4 for party 2, on receipt of a DROP PARTY message (Optional information element with content error present, IE instruction field flag = IE instruction field not significant, Endpoint reference value = party 2), + +optionally sends a STATUS message (Cause = value 100 and optional diagnostics field carrying correct IE identifier, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6) followed by a DROP PARTY ACKNOWLEDGE message and optionally sends a STATUS message (Cause value = 100, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6 or 0 dependant on the order of transmission), remains in P7 for party 1, enters P0 for party 2 and remains in U10. + +###### **L3MU\_21\_39** + +Ensure that the IUT in U10 and P7 for party 1 and P7 for party 2, on receipt of a DROP PARTY message (Optional information element with content error present, IE instruction field flag = IE instruction field not significant, Endpoint reference value = party 2), + +optionally sends a STATUS message (Cause = value 100 and optional diagnostics field carrying correct IE identifier, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6) followed by a DROP PARTY ACKNOWLEDGE message and optionally sends a STATUS message (Cause value = 100, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6 or 0 dependant on the order of transmission), remains in P7 for party 1, enters P0 for party 2 and remains in U10." + +###### **Page 86, subclause 6.2.2.4.8, test purposes L3MU\_43\_25 to L3MU\_43\_27** + +Modify test purposes as below: + +###### **"L3MU\_43\_25** + +Ensure that the IUT in U7 and P3 for party 1 and P3 for party 2, on receipt of a DROP PARTY message (Optional information element with content error present, IE instruction field flag = IE instruction field not significant, Endpoint reference value = party 2), + +optionally sends a STATUS message (Cause = value 100 and optional diagnostics field carrying correct IE identifier, Call state value = 7, Endpoint reference value = party 2, Endpoint reference party state = 6) followed by a DROP PARTY ACKNOWLEDGE message and optionally sends a STATUS message (Cause value = 100, Call state value = 7, Endpoint reference value = party 2, Endpoint reference party state = 6 or 0 dependant on the order of transmission), remains in P3 for party 1, enters P0 for party 2 and remains in U7. + +Selection: IUT stable in U7 and P3. + +###### L3MU\_43\_26 + +Ensure that the IUT in U10 and P7 for party 1 and P3 for party 2, on receipt of a DROP PARTY message (Optional information element with content error present, IE instruction field flag = IE instruction field not significant, Endpoint reference value = party 2), + +optionally sends a STATUS message (Cause = value 100 and optional diagnostics field carrying correct IE identifier, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6) followed by a DROP PARTY ACKNOWLEDGE message and optionally sends a STATUS message (Cause value = 100, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6 or 0 dependant on the order of transmission), remains in P7 for party 1, enters P0 for party 2 and remains in U10. + +Selection: IUT stable in U7 and P3. + +###### L3MU\_43\_27 + +Ensure that the IUT in U10 and P7 for party 1 and P7 for party 2, on receipt of a DROP PARTY message (Optional information element with content error present, IE instruction field flag = IE instruction field not significant, Endpoint reference value = party 2), + +optionally sends a STATUS message (Cause = value 100 and optional diagnostics field carrying correct IE identifier, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6) followed by a DROP PARTY ACKNOWLEDGE message and optionally sends a STATUS message (Cause value = 100, Call state value = 10, Endpoint reference value = party 2, Endpoint reference party state = 6 or 0 dependant on the order of transmission), remains in P7 for party 1, enters P0 for party 2 and remains in U10." + +###### Page 94, History + +Delete the whole clause "History". + +# APPENDIX I + +## Bibliography + +- [A] ETSI Standard ETS 300 771-1 (1997), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for point-to-multipoint call/bearer control; Part 1: Protocol specification.* + + + +### **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2971D-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2971D-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2971D-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/Q/T-REC-Q.2971E-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2971E-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2971E-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/Q/T-REC-Q.2983-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/Q/T-REC-Q.2983-199912-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84b10d19783845f34be169e44ae1aa0cdbbca422 --- /dev/null +++ b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c33da1b748d7d7088eaa200634ea7479874a6a8f03e3517a05e7f80c043e99d0 +size 68239 diff --git a/marked/Q/T-REC-Q.2983-199912-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76da9bf6873e4696ce7d6c7ff64b0c948e09a7d2 --- /dev/null +++ b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58c8a4ffb8c9dac2609937620b3e0420c75e376f19a733722e67a54bb47a9a29 +size 61345 diff --git a/marked/Q/T-REC-Q.2983-199912-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ffa96b6c9d81f4bce048c7b69543be4f264e45a --- /dev/null +++ b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20ddf606d4c8d9da6d53b70e57e06ec0d3f9bd38ce5df792e03907ca58e00126 +size 57523 diff --git a/marked/Q/T-REC-Q.2983-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3c0a47ecb61048cb7f5b5f141b0c08150bad375a --- /dev/null +++ b/marked/Q/T-REC-Q.2983-199912-I_PDF-E/raw.md @@ -0,0 +1,570 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2983** + +(12/99) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Broadband integrated services digital network +(B-ISDN) – Digital subscriber signalling No. 2 +(DSS2) – Bearer control protocol** + +ITU-T Recommendation Q.2983 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| General aspects | Q.2000–Q.2099 | +| Signalling ATM adaptation layer (SAAL) | Q.2100–Q.2199 | +| Signalling network protocols | Q.2200–Q.2299 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 | +| B-ISDN application protocols for the network signalling | Q.2700–Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **BROADBAND INTEGRATED SERVICES DIGITAL NETWORK (B-ISDN) – DIGITAL SUBSCRIBER SIGNALLING No. 2 (DSS2) – BEARER CONTROL PROTOCOL** + +## **Summary** + +This Recommendation belongs to the DSS2 family of ITU-T Recommendations and specifies extensions to Recommendation Q.2931 to specify the additional DSS2 protocol elements (messages, information elements, procedures and functions) required to support the separated control (establishment, modification, clearing) of bearers associated to a call controlled independently by means of a separated call control protocol. The separated call control protocol may be either the generic functional protocol-based separated call control protocol defined in Recommendation Q.2981 or the Q.2931-based separated call control protocol defined in Recommendation Q.2982. + +## **Source** + +ITU-T Recommendation Q.2983 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 1999. + +## **Keywords** + +Bearer control, call control, separation. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2000 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Description..... | 3 | +| 5.1 | Application to interface structure..... | 3 | +| 5.2 | Capabilities supported by this Recommendation..... | 3 | +| 5.3 | General overview ..... | 4 | +| 6 | Operational requirements..... | 4 | +| 6.1 | Provision and withdrawal ..... | 4 | +| 6.2 | Requirements on the originating network side ..... | 4 | +| 6.3 | Requirements on the destination network side ..... | 4 | +| 7 | Primitive definitions and state definitions ..... | 4 | +| 7.1 | Primitive definitions ..... | 4 | +| 7.2 | Bearer state definitions ..... | 5 | +| 8 | Coding requirements..... | 5 | +| 8.1 | Messages ..... | 5 | +| 8.1.1 | Modification to messages defined in Q.2931 ..... | 5 | +| 8.2 | Information elements ..... | 6 | +| 8.2.1 | Call association..... | 6 | +| 8.2.2 | Bearer identifier ..... | 7 | +| 8.2.3 | Other information elements ..... | 7 | +| 9 | Signalling procedures at the coincident S B and T B reference point..... | 8 | +| 9.1 | Introduction..... | 8 | +| 9.2 | Establishment of a bearer..... | 8 | +| 9.2.1 | Additional procedures at a preceding side..... | 8 | +| 9.2.2 | Additional procedures at a succeeding side..... | 9 | +| 9.3 | Clearing of a connection ..... | 10 | +| 10 | Signalling procedures at the T B reference point ..... | 10 | +| 11 | Interworking with other networks..... | 10 | +| 12 | Interactions with supplementary services ..... | 10 | +| 13 | Parameter values ..... | 10 | + +| | Page | +|----------------------------------------------------------------------------------------------------------------------|-------------| +| 14     Dynamic description SDLs ..... | 10 | +| Appendix I – Guidelines for the use of the instruction indicator ..... | 10 | +| Appendix II – Significance and use of the bearer identifier and call association at the user-network interface ..... | 11 | + +# Recommendation Q.2983 + +## **BROADBAND INTEGRATED SERVICES DIGITAL NETWORK (B-ISDN) – DIGITAL SUBSCRIBER SIGNALLING No. 2 (DSS2) – BEARER CONTROL PROTOCOL** + +(Geneva, 1999) + +# 1 Scope + +This Recommendation specifies a signalling protocol for the purpose of bearer control at the B-ISDN user-network interface. The protocol operates between two adjacent bearer control entities. + +This Recommendation specifies the essential features, procedures, and messages required for controlling bearers associated to calls in a functionally separated call and bearer control environment. + +The procedures specified by this Recommendation are applicable at the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point as defined in Recommendation I.413 [1] by means of the Digital Subscriber Signalling System No. 2 (DSS2). + +The bearer control protocol defined by this Recommendation is applicable to control bearers associated to a call which is controlled independently by means of a separated call control protocol. + +NOTE – The separate call control protocol may be either the generic functional protocol-based separated call control protocol defined by Recommendation Q.2981 [2] or the Q.2931-based separated call control protocol defined by Recommendation Q.2982 [3]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation I.413 (1993), *B-ISDN user-network interface*. +- [2] ITU-T Recommendation Q.2981 (1999), *Broadband integrated services digital network (B-ISDN) and broadband private integrated services network (B-PISN) – Call control protocol*. +- [3] ITU-T Recommendation Q.2982 (1999), *Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – Q.2931-based separated call control protocol*. +- [4] ITU-T Recommendation Q.2931 (1995), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control*. +- [5] ITU-T Recommendation I.327 (1993), *B-ISDN functional architecture*. +- [6] ITU-T Recommendation Q.2130 (1994), *B-ISDN signalling ATM adaptation layer – Service specific coordination function for support of signalling at the user-network interface (SSCF at UNI)*. + +- [7] ITU-T Recommendation Q.2961.1 (1995), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable cell rate parameter set.* +- [8] ITU-T Recommendation Q.2961.2 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Support of ATM transfer capability in the broadband bearer capability information element.* +- [9] ITU-T Recommendation Q.2961.3 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the available bit rate (ABR) ATM transfer capability.* +- [10] ITU-T Recommendation Q.2961.4 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the ATM Block Transfer (ABT) ATM transfer capability.* +- [11] ITU-T Recommendation Q.2961.5 (1999), *Digital subscriber signalling system No. 2: Additional traffic parameters: DSS2 additional traffic parameters for cell delay variation tolerance indication.* +- [12] ITU-T Recommendation Q.2961.6 (1998), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling procedures for the support of the SBR2 and SBR3 ATM transfer capabilities.* +- [13] ITU-T Recommendation Q.2965.1 (1999), *Digital subscriber signalling system No. 2 – Support of quality of service classes.* +- [14] ITU-T Recommendation Q.2962 (1998), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase.* +- [15] ITU-T Recommendation Q.2963.1 (1996), *Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner.* +- [16] ITU-T Recommendation Q.2963.2 (1997), *Digital subscriber signalling system No. 2 – Connection modification: Modification procedures for sustainable cell rate parameters.* +- [17] ITU-T Recommendation Q.2963.3 (1998), *Digital subscriber signalling system No. 2 – Connection modification: ATM traffic descriptor modification with negotiation by the connection owner.* + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 bearer state:** State for each bearer (see 7.2) which is known by the layer 3 Bearer Control (BC) entity. The different bearer states correspond to the call/connection states defined in clause 2/Q.2931 [4], i.e. the states of the Q.2931 protocol entities on both sides of the UNI and relate to each call-associated bearer. + +**3.2 bearer:** A connection for the transport of user plane information between users involved in a call. + +**3.3 bearer control:** Functionality and signalling in and between networks and terminals to effect the control of a bearer, that bearer being part of a call. + +**3.4 bearer control entity (BC entity):** An entity that is located in a terminal or a network and that participates in bearer control. + +**3.5 call:** An association between two or more users using a telecommunication service to communicate through one or more networks. + +**3.6 call control:** Functionality and signalling in and between networks and terminals to effect the control of a call. + +**3.7 call control entity (CC entity):** An entity that is located in a terminal or a network and that participates in call control. + +**3.8 bearer identifier:** The identifier used to identify a bearer instance to which a particular bearer establishment request relates between two CC entities. The value of the bearer identifier is significant between two adjacent CC entities. The value is unique within a call between two adjacent CC entities. + +**3.9 call association:** The identifier used to identify a call instance to which a particular bearer establishment request relates between two CC entities. The value of a call identifier is significant between two adjacent call control entities. The value carried in the call association is significant between two adjacent CC entities. + +**3.10 preceding side:** With respect to a given bearer, the side of a user-network interface from which bearer establishment across the interface originates. + +**3.11 succeeding side:** With respect to a given bearer, the side (opposite to the preceding side) of a user-network interface which receives bearer establishment request across the interface. + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|--------|---------------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband Integrated Services Digital Network | +| DSS2 | Digital Subscriber Signalling System No. 2 | +| QoS | Quality of Service | +| SAAL | Signalling ATM Adaptation Layer | +| SDL | Specification and Description Language | +| TE | Terminal Equipment (see Recommendation I.327 [5]) | +| UNI | User-Network Interface | + +# **5 Description** + +## **5.1 Application to interface structure** + +The bearer control procedures apply to the interface structures defined in Recommendation I.413 [1]. They use the functions and services provided by layer 2 (i.e. the SAAL). The layer 3 procedures request the services of layer 2 and receive information from layer 2 using the primitives defined in Recommendation Q.2130 [6]. These primitives are used to illustrate the communication between the protocol layers and are not intended to specify or constrain implementations. + +## **5.2 Capabilities supported by this Recommendation** + +This Recommendation builds upon the basic point-to-point combined call/bearer control protocol defined in Recommendation Q.2931 [4] for DSS2 (see 1.5/Q.2931) to enable the separated control of bearers being associated to a call. + +## **5.3 General overview** + +This Recommendation provides the procedures, messages and information elements needed for establishing, maintaining and clearing of bearers being associated to a call. + +After a call has been initiated or has progressed to the active state, bearers can be added to the call by individual bearer establishment requests from the calling party or the called party, using the bearer control protocol specified in this Recommendation, which are based on the procedures in Recommendation Q.2931 [4]. Each new bearer establishment request shall use a new call reference (see clause 4/Q.2931). Bearers may be established or released from the call at any time while not modifying the call state. New bearers can be established by the calling party or the called party by sending a SETUP message as defined in Recommendation Q.2931, which in addition contains the call association information element in order to associate that bearer to the call. Bearers can be released from the call by the calling party or the called party by sending a RELEASE message as defined in Recommendation Q.2931. + +The individual bearers are controlled independently. In particular, multiple bearer establishment requests may be initiated in parallel (i.e. the requesting party does not need to wait for a response related to one bearer establishment request before issuing another one). Similarly, multiple bearer release requests may be pending at the same time (i.e. the requesting party does not need to wait for a response related to one release bearer request before issuing the next one). + +Any ATM transfer capability available at the interface may be requested independently for each of the bearers associated to a call, using appropriate connection characteristics parameters indication as specified in the Q.2961 series of Recommendations (see [7], [8], [9], [10], [11] and [12]). Any QoS class available at the interface may be requested independently for each of the bearers associated to a call, using appropriate QoS class indication as specified in Recommendation Q.2965.1 [13]. Furthermore, the ATM traffic parameter negotiation features defined in Recommendation Q.2962 [14] apply independently to each bearer at establishment time, as well as ATM traffic parameter modification during the active state of the bearer do, using the features defined in the Q.2963 series of Recommendations (see [15], [16] and [17]). + +# **6 Operational requirements** + +## **6.1 Provision and withdrawal** + +A bilateral agreement between the user and the network provider concerning the availability of the separated call and bearer capabilities is assumed to exist. This may be the subject of a subscription option or may be made generally available. + +## **6.2 Requirements on the originating network side** + +None beyond the support of the separated call and bearer capability related control protocols. + +## **6.3 Requirements on the destination network side** + +None beyond the support of the separated call and bearer capability related control protocols. + +# **7 Primitive definitions and state definitions** + +## **7.1 Primitive definitions** + +Clause 8/Q.2931 shall apply. No additional primitives between DSS2 layer 3 and the signalling ATM adaptation layer are defined for the purpose of this Recommendation. + +## 7.2 Bearer state definitions + +The bearer states that may exist on the user or network side of the user-network interface coincide with the call/connection states defined in clause 2/Q.2931. The Bearer Control (BC) entity maintains the current state of each individual bearer independently. + +The bearer states defined in 2.2/Q.2931 (corresponding to the additional call/connection states) relating to interworking requirements are not applicable although they may be available if the point-to-point combined call/bearer control capability (using the Q.2931 basic call control protocol [4]) inter-working with existing services or networks (i.e. operating exclusively the combined call/bearer control protocol) is supported. However, such interworking requirements are beyond the scope of the present Recommendation. + +# 8 Coding requirements + +## 8.1 Messages + +Messages are defined in accordance with the principles given by the introductory paragraph in clause 3/Q.2931. Only changes to messages defined in clause 3/Q.2931 are specified in this subclause. + +### 8.1.1 Modification to messages defined in Q.2931 + +The following modifications apply to the messages defined in 3.1/Q.2931. However, they do not apply, unless otherwise explicitly stated, to the messages relating to the support of 64 kbit/s-based ISDN circuit mode services (see 3.2/Q.2931) even if the interworking of the separated call and bearer capability with these services (or interworking with networks providing these services) is supported. + +Table 8-1 lists the existing clause 3/Q.2931 messages that have their contents modified to support the establishment/release of bearers in a call control environment by means of separated call and bearer control protocols. + +**Table 8-1/Q.2983 – Modified Q.2931 messages** + +| Message | Reference | +|---------|-----------| +| SETUP | 8.1.1.1 | + +#### 8.1.1.1 SETUP + +This message is sent by the user to the network and by the network to the user to initiate an individual bearer establishment. + +See Table 8-2 for additions to the structure of this message shown in Table 3-8/Q.2931. + +**Table 8-2/Q.2983 – SETUP message additional contents** + +| Message type: SETUP
Significance: Global
Direction: Both | | | | | +|----------------------------------------------------------------------|-----------|-----------|----------|--------| +| Information element | Reference | Direction | Type | Length | +| Call association | 8.2.1 | both | O (Note) | 8-9 | +| Bearer identifier | 8.2.2 | both | O (Note) | 7 | +| NOTE – Mandatory when the message is used to add a bearer to a call. | | | | | + +#### 8.1.1.2 Other messages + +If interworking between services supported in a separated call and bearer control environment and 64 kbit/s-based ISDN circuit mode services is supported, the messages defined in 3.2/Q.2931 apply. In addition the SETUP ACKNOWLEDGE (see 3.2.8/Q.2931) message and the INFORMATION message (see 3.2.4/Q.2931) is not applicable although they may be used to support the Q.2931 combined call/connection control capability at the same interface. + +## 8.2 Information elements + +The information elements and coding rules of 4.1/Q.2931, 4.2/Q.2931, 4.3/Q.2931, 4.4/Q.2931, and 4.5/Q.2931 shall apply with the additions or modifications identified in the following subclauses. + +### 8.2.1 Call association + +The purpose of the call association information element is to identify the call to which the bearer in the process of being established relates. The call identifier value carried in the call association information element has significance between the two peer call control entities between which the bearer is being established. + +NOTE – The assignment of the call association value is initiated by the originating side of the first message referring to the establishment of the call. + +The call association information element is coded as shown in Figure 8-1 and Table 8-3. + +![](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-------------------------------------------------|--------------------|---|-------------|---|---------------------------------------|---|---|------------| +| Call association | | | | | | | | 1 | +| 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | | +| Information element identifier | | | | | | | | 2 | +| ext.
1 | Coding
standard | | Flag Res. | | IE instruction field
IE action ind | | | | +| Length of call association contents | | | | | | | | 3 | +| Length of call association contents (continued) | | | | | | | | 4 | +| Identifier for Call identifier value | | | | | | | | 5 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | | +| Call identifier value | | | | | | | | 5.1 to 5.3 | +| or | | | | | | | | | +| Identifier for Call segment identifier value | | | | | | | | 6 | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | | +| Call segment identifier value | | | | | | | | 6.1 to 6.4 | + +**Figure 8-1/Q.2983 – Call association information element** + +**Table 8-3/Q.2983 – Call association information element coding** + +- Octets 1 through 4 are coded according to the coding rules specified in clause 4/Q.2931. Either a call identifier (octet group 5) or a call segment identifier (octet group 6) shall be included but not both. This depends on the method of call identification employed in the related call control protocol. +- The call identifier value field (octets 5.1 to 5.3), if present, contains the call identifier value if provided by the associated CC entity. +- The call segment identifier value field (octets 6.1 to 6.4), if present, contains the call segment identifier value if provided by the associated CC entity. + +### 8.2.2 Bearer identifier + +The purpose of the bearer identifier information element is to relate a bearer in the process of being established to a bearer object known to peer call control entities within the context of a call. The bearer identifier value has significance only between the two peer call control entities between which the bearer is being established. + +The bearer identifier information element is coded as shown in Figure 8-2 and in Table 8-4. + +![](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-------------------------------------------------|-------------------------|---|----------------------|------|---|---|---------------|--------| +| Bearer identifier | | | | | | | | 1 | +| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | | +| Information element identifier | | | | | | | | 2 | +| ext.
1 | Coding
standard | | IE instruction field | | | | | | +| | | | Flag | Res. | | | IE action ind | 3 | +| Length of bearer identifier contents | | | | | | | | | +| Length of bearer reference contents (continued) | | | | | | | | 4 | +| 0/1
bearer
identi-
fier flag | Bearer identifier value | | | | | | | 5 | +| Bearer identifier value (continued) | | | | | | | | 6 | +| Bearer identifier value (continued) | | | | | | | | 7 | + +**Figure 8-2/Q.2983 – Bearer identifier information element** + +**Table 8-4/Q.2983 – Bearer identifier information element coding** + +- Octets 1 through 4 are coded according to the coding rules specified in clause 4/Q.2931 [4]. + - Bearer identifier flag (octet 5) + Bit +8 + 0 The message is sent from the side that originated the bearer reference. + 1 The message is sent to the side that originated the bearer reference. + - Bearer identifier value (octets 5, 6 and 7) +- The bearer identifier is a 23-bit integer (coded in binary) to uniquely identify a bearer within a call. + +### 8.2.3 Other information elements + +The broadband sending complete information element (see 4.5.21/Q.2931) is not applicable. However, its use is optional and its presence or absence in the SETUP message shall not incur an error situation. + +The information elements defined for the support of 64 kbit/s-based ISDN circuit mode services (see 4.6/Q.2931) apply only when their interworking with services supported in a separated call and bearer control environment is provided. + +# 9 Signalling procedures at the coincident SB and TB reference point + +## 9.1 Introduction + +Before the procedures described in this subclause are invoked, an assured mode SAAL connection shall be established as specified in 5.1/Q.2931 [4] and clause 8/Q.2931 [4]. + +The procedures specified in this subclause cover the following capabilities: + +- a) addition of bearers to call being established or having progressed to the active state; +- b) release of bearers from an existing call, while maintaining the call active, including when no more bearer exists. + +NOTE – Any of the users may initiate bearer establishment or clearing. + +The procedures for basic (and simultaneous) call/connection control as defined in clause 5/Q.2931 [4] shall apply as the basis for the separated bearer control. Only additional procedures required to handle the separated bearer control functions of a call are described in the following subclauses. + +## 9.2 Establishment of a bearer + +As soon as the call has been initiated and the initiating call control entity has received an indication that call establishment is proceeding, one or more bearer addition to the call may be initiated. + +### 9.2.1 Additional procedures at a preceding side + +When sending a SETUP message, a preceding side that is a point of call/bearer coordination shall place in the called party number information element the called party number supplied by the call control signalling service user. + +The Bearer Control (BC) entity requesting the addition of a bearer to a call shall send a SETUP message with a new call reference and containing a call association information element specifying the call to which the bearer establishment request relates. + +The SETUP message shall contain the called party number and called party subaddress information element containing addresses provided by the Call Control (CC) entity. + +The Bearer Control (BC) entity receiving a SETUP message specifying a call association value which is not recognized as relating to an existing call, shall reject the bearer establishment request by sending a RELEASE COMPLETE message with cause #101, "*message not compatible with call state*". + +Upon receipt of an indication that the bearer establishment request has been accepted and proceeds, the network shall associate the bearer (identified by the call reference in the received message) to the call (identified by the value carried in the call association information element). + +#### 9.2.1.1 Additional procedures at a preceding side that is a point of call/bearer coordination + +When sending a SETUP message, a preceding side that is a point of call/bearer coordination shall place in the called party number information element the called party number supplied by the local call control signalling service user. + +It shall also include in the SETUP message a call association information element containing a call identifier value or a call segment identifier value supplied by the local call control signalling service user. + +In addition, it shall include in the SETUP message a bearer identifier information element containing a bearer identifier value supplied by the local call control signalling service user. + +#### **9.2.1.2 Additional procedures at a preceding side that is not a point of call/bearer coordination** + +When sending a SETUP message, a preceding side that is not a point of call/bearer coordination shall place in the called party number information element the called party number received in the bearer establishment request from the previous point of call/bearer coordination. + +It shall also include in the SETUP message a call association information element containing a call identifier value or a call segment identifier value that has been received in the bearer establishment request message from the previous point of call/bearer coordination. + +In addition, it shall include in the SETUP message a bearer identifier information element contained in the bearer establishment request message received from the previous point of call/bearer coordination. + +### **9.2.2 Additional procedures at a succeeding side** + +Upon receipt of a SETUP message containing a call association information element, the succeeding side shall determine whether it is the point of call/bearer coordination addressed by the called party number information element. If so, the procedures of 9.2.2.2 shall apply; otherwise, the procedures of 9.2.2.1 shall apply. + +#### **9.2.2.1 Additional procedures at a succeeding side that is not a point of call/bearer coordination** + +A succeeding side that is not a point of call/bearer coordination shall forward the bearer establishment request based on information in the received SETUP message towards the next point of call/bearer coordination, as addressed by the number in the received called party number information element. + +It shall also pass forward in the SETUP bearer establishment request message towards the next point of call/bearer coordination the call identifier value or the call segment identifier value received in the call association information element present in the received SETUP message. + +In addition, it shall pass forward in the SETUP bearer establishment request message towards the next point of call/bearer coordination the bearer identifier value received in the bearer identifier information element. + +#### **9.2.2.2 Additional procedures at a succeeding side that is a point of call/bearer coordination** + +A succeeding side that is a point of call/bearer coordination shall forward the bearer establishment request based on information in the received SETUP message to the local call control signalling service user. + +It shall also pass to the local call control signalling service user the call identifier value or the call segment identifier value received in the call association information element present in the received SETUP message. + +NOTE 1– The call control service user can use this value to relate the bearer to an existing call. Failure to relate the bearer to an existing call can result in a rejection by the call control signalling service user of the bearer being requested to be established. + +In addition, it shall pass to the local call control signalling service user the bearer identifier value in the bearer identifier information element. + +NOTE 2 – The call control service user can use this value to correlate the bearer against the call's object model. Failure to correlate can result in the call control signalling service user to reject the bearer being requested to be established. + +## **9.3 Clearing of a connection** + +Clearing procedures as specified in 5.4/Q.2931 shall apply. Clearing of a bearer does not affect the call state. + +NOTE – The bearer clearing message does not contain the call association information element. + +# **10 Signalling procedures at the TB reference point** + +Clause 9 applies. + +# **11 Interworking with other networks** + +Interworking with user or network entities not supporting the separated call and bearer capability is an implementation option. The interworking specifications are beyond the scope of the present Recommendation. + +NOTE – If supported, the interworking function shall map each bearer of a separated call to a call/connection in networks not supporting the separated call and bearer capability. + +# **12 Interactions with supplementary services** + +Beyond the scope of the present Recommendation. + +# **13 Parameter values** + +No additional parameter required in addition to those defined in Recommendation Q.2931. + +# **14 Dynamic description SDLs** + +None required beyond those in Annex A/Q.2931. + +# **APPENDIX I** + +## **Guidelines for the use of the instruction indicator** + +This appendix provides guidelines for the setting of the instruction indicator field in the call association and bearer identifier information elements. An implementation may choose to set the instruction indicator differently, depending on possible specific requirements beyond those covered explicitly within the present Recommendation. + +Recommended setting of the instruction indicator in the call association information element: + +Flag: "ignore explicit instructions" + +Action indicator: "not significant" + +Recommended setting of the instruction indicator in the bearer identifier information element: + +Flag: "ignore explicit instructions" + +Action indicator: "not significant" + +# APPENDIX II + +## Significance and use of the bearer identifier and call association at the user-network interface + +This appendix provides further information on the use of the bearer identifier value included in the bearer identifier information element to enable the association of a bearer to a call through the use of the call identifier or call segment identifier value contained in the call association information element. + +Figure II.1 shows the peer-to-peer call and bearer control elements at the user-network interface and their relationships. + +![Figure II.1: Call and bearer control elements relationships at UNI](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +The diagram illustrates the architecture of DSS2 call and bearer control elements at the User-Network Interface (UNI). It is divided into two main sides by a central vertical line labeled $S_B/T_B$ or $T_B$ reference point. + +- User side DSS2 terminating entity (left):** Contains a box labeled "DSS2 call/bearer control" at the top. Below it are two boxes: "CC entity" on the left and "BC entity" on the right. At the bottom is a box labeled "DSS2 coordination function". Lines connect the "DSS2 call/bearer control" box to both the "CC entity" and the "BC entity". The "CC entity" and "BC entity" both have lines connecting them to the "DSS2 coordination function" box. Lines from the "CC entity" and "BC entity" extend downwards through the coordination function to the reference point. +- Network side DSS2 terminating entity (right):** Contains a box labeled "DSS2 call/bearer control" at the top. Below it are two boxes: "BC entity" on the left and "CC entity" on the right. At the bottom is a box labeled "DSS2 coordination function". Lines connect the "DSS2 call/bearer control" box to both the "BC entity" and the "CC entity". The "BC entity" and "CC entity" both have lines connecting them to the "DSS2 coordination function" box. Lines from the "BC entity" and "CC entity" extend downwards through the coordination function to the reference point. + +A horizontal line at the bottom connects the two sides at the $S_B/T_B$ or $T_B$ reference point. The text "T11102910-99" is located in the bottom right corner of the diagram area. + +Figure II.1: Call and bearer control elements relationships at UNI + +**Figure II.1/Q.2983 – Call and bearer control elements relationships at UNI** + +The call identifier or the call segment identifier value provides the means to establish the required association between corresponding peer call object instances and the bearer identifier value is used to explicitly associate corresponding peer bearer object instances at each side of the user-network interface. + +The call state machine is maintained by the CC entity. Each call state machine instance is identified by the call identifier or the call segment identifier, depending on the separated call control protocol used to operate the call. + +The bearer state machine is maintained by the BC entity. Each bearer state machine instance is identified by the bearer identifier. + +The call/bearer coordination function uses the call identifier or the call segment identifier value contained in the call association information element in the received bearer establishment SETUP message to relate the bearer, identified by the bearer identifier value, with an existing call. + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a328d7178a259eb9aa2d2c6c1aac196701577f27 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bbe3fd8ab38dd7e410ec83c07f1f24c2e589c591596eedc2db05175560da2bc +size 44828 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc8166def1e7deb2e1998a088c708f98787b47a4 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e42416898d64902725ce4af6058b31adf7ed99c66cfed2906cc976f17b11ac49 +size 48445 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4ad14d5c21901b3978995015cc973de06ccd3f3 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7660d1ea883f468b0fb5a6080a5371c2659dc1ac6245a1493588e9fd1aa1e30b +size 35262 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..769e57d176e59b6d3176a600c2f640dfbca30ee5 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b89aed74457708d8e122ebb3ba9b78fe688ac29ebdb1c187a0bd7f3f47ed7f +size 35131 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34c6c5effffe5b707be618b48e1cc2e829d5f2ff --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2234a797c1a6cc762fca02b47d7a3aa37f3dc776814f250cffa5fea2d04640cf +size 125122 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92c30275859639ce91adb2e149f6310d7fd8d750 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b68037464141b3424721792ed7925154b5afe696178b6ad808aa4c8443a65b6 +size 63823 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3b9e0f40e6d1a21a0c85016ebbabbf0532706dc --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b818853707ebb49a86a41ab74939acd088e1df9a6b64d874fcbc073a0ccd6ab6 +size 87086 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bf7cb2c6b39df4409a1f92f513fa363882eb085 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00c37fa2bdd58fa5eafe0ed947b429c4bd25b87c0820a44db2a7294ddb5e1822 +size 70617 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdf4c9cb62e23691d2fdda64c4c07d8445d3390a --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c12a85a799632c5c659f0d4253f3266702f5396ae9393b5b75e2461793447ad3 +size 64737 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d63fad4c6f5bb79098c377d2066513cb8ec8b9a5 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6375bb385a578641aa6b130cbdae3ede19242b25cefac0e8de2c02505c67f4c +size 52726 diff --git a/marked/Q/T-REC-Q.3064-202406-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3711714a6a36f8c87e21acc46302af8178999a2 --- /dev/null +++ b/marked/Q/T-REC-Q.3064-202406-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000204fae479881795c39351e81f0e5f126a7f04504bfb11c1a9bac40792054c +size 68159 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f77eaa7a3fe641adf54cacad224e2c85fbef0c28 --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e47ba30192a7e29ce82211eb1b44604a31a969939105f9cec5bf282abf2f89c7 +size 4357 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebf44834e179f154670b2ec596d9d6f35c3d23c1 --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae2e04b4aea838963c022d3fc391856af1452389c4d0be5948ada8a2b7b48614 +size 60417 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e346e14e905a6d1d4f3c7c1d05f69323f518b9a --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73c067fd8abbf96024b7f434d47dbd399b051b11a5f8f1e45e8ef322c0407262 +size 52142 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f4344280940ebfb3ce7750aff99cb8bcdf881d3 --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9336f626e6336f4c13829a648d56a38ef8cc6915d12e229566cd01d7ade7189b +size 118662 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a4204cb34fe0d31fa5cfdb67f4687ca935eaa56 --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:318f3fdd437670e3cbaa37c61de0d8d249b7c5c50d4eb87edb0c2d3ff7c1856c +size 115278 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e102c0d43a3039ce7691e8dedec6c873b0573896 --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66207b5f6a8c820481e32e5aa0c400f6322d3ce593d78218256d284c868ebc72 +size 94488 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..336202c15fc234977c8eb8626435707408401c7f --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a72fd245822b0f975ffe9abd7aa70d9cde36ffa4576b50738920764ba3f814a8 +size 61718 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73cc5fb4a2f2b643d1465be2677f0e803c9502c9 --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8040765eabd1e2f1e6ef7c335efd11c7b8b9e0654d2d96a7fd9850827a7b39c +size 119497 diff --git a/marked/Q/T-REC-Q.3222-201004-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9f1d8f6cebdd2b315246ff203365a2bbf2fba8ef --- /dev/null +++ b/marked/Q/T-REC-Q.3222-201004-I_PDF-E/raw.md @@ -0,0 +1,1166 @@ + + +**ITU-T** + +**Q.3222** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/2010) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Signalling requirements and protocols for the NGN – +Signalling and control requirements and protocols to +support attachment in NGN environments + +## --- **Requirements and protocol at the interface between transport location management physical entities (Ng interface)** + +Recommendation ITU-T Q.3222 + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------------|---------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3649 | +| NGN applications | Q.3700–Q.3849 | +| Testing for NGN networks | Q.3900–Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T Q.3222** + +## **Requirements and protocol at the interface between transport location management physical entities (Ng interface)** + +# **Summary** + +Recommendation ITU-T Q.3222 provides the signalling requirements and protocol for the interface between the local transport location management physical entity and the home transport location management physical entity in the network attachment control function (NACF) block of the next generation network (NGN) release 1. When the local and the home transport location management physical entities (TLM-PEs) are the different access networks, this protocol can be used for communication between both TLM-PE instances. This Recommendation satisfies the requirements for information flows across the Ng reference point as specified in Recommendation ITU-T Y.2014. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3222 | 2010-04-30 | 11 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|-------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Ng interface ..... | 3 | +| 5.1 Overview ..... | 3 | +| 5.2 Ng reference model ..... | 4 | +| 5.3 Physical entities and capabilities ..... | 4 | +| 6 Signalling requirements ..... | 5 | +| 6.1 Location registration..... | 7 | +| 6.2 Information query ..... | 8 | +| 7 Description of procedure ..... | 9 | +| 7.1 General ..... | 9 | +| 7.2 Procedure on the Ng interface ..... | 9 | +| 8 Use of Diameter-based protocol ..... | 12 | +| 8.1 Securing Diameter messages ..... | 12 | +| 8.2 Accounting functionality ..... | 12 | +| 8.3 Use of sessions ..... | 12 | +| 8.4 Transport protocol ..... | 13 | +| 8.5 Routing considerations ..... | 13 | +| 8.6 Advertising application support ..... | 13 | +| 9 Message specification..... | 14 | +| 9.1 Commands ..... | 14 | +| 9.2 Experimental-Result-Code AVP values ..... | 16 | +| 9.3 Attribute value pairs (AVPs) ..... | 16 | +| 9.4 Use of namespaces ..... | 19 | +| 10 Security considerations ..... | 19 | +| Appendix I – Scenarios using Ng interface ..... | 20 | +| I.1 Location information service from the home network with DHCP-based network attachment ..... | 20 | +| I.2 NACE-SCE bundled authentication ..... | 22 | +| Bibliography..... | 26 | + + + +# Recommendation ITU-T Q.3222 + +## Requirements and protocol at the interface between transport location management physical entities (Ng interface) + +# 1 Scope + +This Recommendation defines the requirements and protocol for the Ng interface between transport location management physical entities. The Ng reference point enables communication between local and home transport location management physical entities (TLM-PEs). + +NOTE – Work for this Recommendation is based on the context of [ITU-T Y.2012] and [ITU-T Y.2014]; this Recommendation satisfies the requirements for information flows across the Ng reference point as specified in [ITU-T Y.2014] and the functional requirement and architecture specified in [ITU-T Y.2012]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. +- [ITU-T Y.2014] Recommendation ITU-T Y.2014 (2010), *Network attachment control functions in next generation networks*. +- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [ETSI ES 283 034] ETSI ES 283 034 (2008), *e4 interface based on the Diameter protocol*. +- [ETSI ES 283 035] ETSI ES 283 035 (2008), *e2 interface based on the Diameter protocol*. +- [ETSI TS 129 229] ETSI TS 129 229 (2010), *Cx and Dx interfaces based on the Diameter protocol; Protocol details*. +- [ETSI TS 129 329] ETSI TS 129 329 (2006), *Sh interface based on the Diameter protocol; Protocol details*. +- [IETF RFC 2960] IETF RFC 2960 (2000), *Stream Control Transmission Protocol*. +- [IETF RFC 3046] IETF RFC 3046 (2001), *DHCP Relay Agent Information Option*. +- [IETF RFC 3309] IETF RFC 3309 (2002), *Stream Control Transmission Protocol (SCTP) Checksum Change*. +- [IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 authentication** [ITU-T Y.2014]: A property by which the correct identifier of an entity or party is established with a required assurance. The party being authenticated could be a user, subscriber, home environment or serving network. + +**3.1.2 location information** [b-ITU-T Q.1001]: The location register should, as a minimum, contain the following information about a mobile station: + +- international mobile station identity; +- actual location of the mobile station (e.g., PLMN, MSC area, location area, as required). + +**3.1.3 location registration (LR)** [b-ITU-T Q.1741.3]: The UE registers its presence in a registration area, for instance, regularly or when entering a new registration area. + +**3.1.4 nomadism** [b-ITU-T Q.1761]: Ability of the user to change his network access point after moving; when changing the network access point, the user's service session is completely stopped and then started again, i.e., there is no handover possible. It is assumed that the normal usage pattern is that users shut down their service session before moving to another access point or changing terminal. This is the mobility alluded to in the case of fixed mobile convergence. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 session data:** IP-connectivity related data consisting of globally unique IP address information, transport subscriber identifier, type of access transport, transport resource subscription profile information and physical/logical connection identifier. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------| +| ABNF | Augmented Backus-Naur Form | +| AM-PE | Access Management Physical Entity | +| ATM | Asynchronous Transfer Mode | +| AVP | Attribute-Value Pair | +| CEA | Capability Exchange Answer | +| CER | Capability Exchange Request | +| CPE | Customer Premises Equipment | +| FQDN | Fully Qualified Domain Name | +| GTP | GPRS Tunnelling Protocol | +| IMPI | IMS Private User Identity | +| IMPU | IMS Public User Identity | +| MAC | Media Access Control | +| MPLS | MultiProtocol Label Switching | +| MSC | Mobile Switching Centre | +| NACE | Network Attachment Control Entity | + +| | | +|----------|------------------------------------------------------------| +| NACF | Network Attachment Control Functions | +| NAC-PE | Network Access Configuration Physical Entity | +| P-CSC-PE | Proxy-Call Session Control Physical Entity | +| PD-PE | Policy Decision Physical Entity | +| PE-FE | Policy Enforcement Functional Entity | +| PLMN | Public Land Mobile Network | +| PNA | Push Notification Answer | +| PNR | Push Notification Request | +| PPP | Point-to-Point Protocol | +| RACE | Resource and Admission Control Entity | +| RACF | Resource and Admission Control Functions | +| SCE | Service Control Entity | +| SCTP | Stream Control Transport Protocol | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| TAA-PE | Transport Authentication and Authorization Physical Entity | +| TLM-PE | Transport Location Management Physical Entity | +| UDA | User Data Answer | +| UDR | User Data Request | +| UE | User Equipment | +| VPN | Virtual Private Network | +| WLAN | Wireless Local Area Network | +| xDSL | x Digital Subscriber Line | + +# 5 Ng interface + +## 5.1 Overview + +The network attachment control entity (NACE) maintains information on IP-connectivity access sessions associated with user equipment connected to the NGN network. This information is stored in the transport location management physical entity (TLM-PE), and can be retrieved by other control functions and applications through the following three interfaces: + +- The S-TC1 interface enables service control entity (SCE) to retrieve IP-connectivity related session data. +- The Ru interface enables the IP-connectivity related session data to be exchanged between the NACE and the resource and admission control entity (RACE) defined in [ITU-T Y.2012]. +- The Ng interface enables the home TLM-PE to retrieve session data related to IP-connectivity from the local TLM-PE. + +This Recommendation specifies the protocol for the Ng interface. + +The Ng interface enables the home TLM-PE to retrieve session data related to IP-connectivity from the local TLM-PE. + +When the user/customer premises equipment (CPE) moves in a different access domain, the location binding information of the local TLM-PE needs to be registered. On the other hand, when the user/CPE moves within the same access domain, only the location binding information of the local TLM-PE needs to be updated; the location binding information of the home TLM-PE does not need to be updated. + +The service control entities (SCEs) can retrieve information about the characteristics of the IP-connectivity session used to access (e.g., network location information) from the TLM-PE. The form of location information that is provided by the TLM-PE depends on the requestor. When the user/CPE moves in a different access domain, the service control functions of the home network access the TLM-PE in the visited network for location information via a proxy-TLM-PE in the home network. + +Therefore, two operations may occur at the Ng interface as following: + +- location registration, in the direction from the local TLM-PE to the home TLM-PE; +- information query, in the direction from the home TLM-PE to the local TLM-PE. + +## 5.2 Ng reference model + +This clause describes the reference architecture. As the initial architecture, the illustration below can be used: + +![Figure 5-1 – Ng reference model diagram showing the network architecture between a Visited NACE and a Home NACE.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The diagram illustrates the Ng reference model architecture. It is divided into two main domains: **Visited NACE** (left) and **Home NACE** (right), connected by the **Ng** interface. A dashed blue rectangle labeled "Scope of this Specification" highlights the Ng interface and the Home TLM-PE. + +**Visited NACE (Left):** Contains several network entities: + + +- HGWC-PE** (HGWC-PE) connected to **Local TLM-PE** via the **Nx** interface. +- TUP-PE** (TUP-PE) connected to **TAA-PE** via the **Nb** interface. +- TAA-PE** (TAA-PE) connected to **Local TLM-PE** via the **Nc** interface. +- TAA-PE** (TAA-PE) connected to **NAC-PE** via the **Nk** interface. +- TAA-PE** (TAA-PE) connected to **AM-PE** via the **Na** interface. +- TAA-PE** (TAA-PE) has a self-loop labeled **Ni**. +- NAC-PE** (NAC-PE) connected to **Local TLM-PE** via the **Ne** interface. +- NAC-PE** (NAC-PE) connected to **AM-PE** via the **Nd** interface. + +**Home NACE (Right):** Contains: + + +- SCE** (SCE) connected to **S-TC1** (S-TC1). +- S-TC1** (S-TC1) connected to **Home TLM-PE** (Home TLM-PE). + +The **Ng** interface is a dashed blue rectangle connecting the **Local TLM-PE** in the Visited NACE to the **Home TLM-PE** in the Home NACE. + +Figure 5-1 – Ng reference model diagram showing the network architecture between a Visited NACE and a Home NACE. + +Figure 5-1 – Ng reference model + +## 5.3 Physical entities and capabilities + +### 5.3.1 Transport location management physical entity (TLM-PE) + +TLM-PE responds to location queries from service control functions and applications. The actual information delivered by TLM-PE may take various forms (e.g., network location, geographical coordinates, postal address, etc.) depending on the agreement with the requester and on the user's preferences regarding the privacy of its location. + +The TLM-PE may play several roles, i.e., the home role, the local role, or both. In its home role, the TLM-PE stores a pointer to the TLM-PE instance that is playing the local role for the attachment. The current location information of the user/CPE in the access domain is stored and bound in the local TLM-PE. So when the user/CPE moves in the same access domain, only the location binding information of the local TLM-PE needs to be updated; the location binding information of the home TLM-PE does not need to be updated. + +The local TLM-PE is in the access network to which the terminal equipment is attached. The home TLM-PE is in the network designated by the TUP-TE. Where these networks differ, communication between the local and the home TLM-PE instances takes place over the Ng reference point. Namely, the home TLM-PE may provide the SCE with user network profile information through the local TLM-PE of the visited network to support mobility when the user is nomadic. + +Similarly, the home TLM-PE is able to provide the SCE with user network profile information through the local TLM-PE of another service provider for roaming on such access network. + +The functionality of the TLM-PE is further detailed in clause 7.2.3 of [ITU-T Y.2014]. + +# **6 Signalling requirements** + +The Ng reference point enables the home TLM-PE to retrieve network location information from the local TLM-PE. The primary parameter for retrieving the location information shall be the assigned IP address allocated to the terminal. + +The form of location information provided by the local TLM-PE depends on the home TLM-PE. + +The following information flows are used on this interface: + +- Location Registration Request/Response; +- Information Query Request/Response. + +![Sequence diagram showing high-level information flows between a UE, NACE in visited network, NACE in home network, and SCE in home network. The diagram illustrates the interaction for network attachment, authentication, IP configuration, binding updates, location registration, and information queries.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph NACE_in_visited_network [NACE in visited network] + AM-PE + NAC-PE + TAA-PE + TLM-PE + end + subgraph NACE_in_home_network [NACE in home network] + TAA-PE_TUP-PE [TAA-PE/TUP-PE] + TLM-PE + end + subgraph SCE_in_home_network [SCE in home network] + P-CSC-PE + I-CSC-PE + S-CSC-PE + end + + UE->>AM-PE: 1. Network attachment + AM-PE->>TAA-PE: 2-1. Authentication request + TAA-PE->>TAA-PE_TUP-PE: 2-2. Authentication request + TAA-PE_TUP-PE->>TAA-PE: 2-3. Authentication + TAA-PE->>NAC-PE: 2-4. Authentication response + NAC-PE->>UE: 2-5. Attachment ack + UE->>NAC-PE: 3-1. IP configuration + NAC-PE->>UE: 3-2. IP address + UE->>TAA-PE: 4-1. Binding update + TAA-PE->>TLM-PE: 4-2. Store IP address + TLM-PE->>TAA-PE: 4-3. Binding ack + TAA-PE->>TLM-PE: 5-1. Location registration request + TLM-PE->>TAA-PE: 5-2. Location registration response + UE->>P-CSC-PE: 6. SIP register + P-CSC-PE->>TLM-PE: 7-1. Information query request + TLM-PE->>TAA-PE: 7-2. Information query request + TAA-PE->>TLM-PE: 7-3. Information query response + TLM-PE->>P-CSC-PE: 7-4. Information query response + +``` + +Sequence diagram showing high-level information flows between a UE, NACE in visited network, NACE in home network, and SCE in home network. The diagram illustrates the interaction for network attachment, authentication, IP configuration, binding updates, location registration, and information queries. + +Figure 6-1 – High-level information flows + +This generic case describes a scenario in which the service control entity (SCE) is located in its home network, not in the visited network. In x digital subscriber line (xDSL) access network or WLAN hotspot environment, a service control entity (SCE) requires the UE's line identifier or access point location to provide location-based services. Because the service control entity (SCE) knows only the TLM-PE in its home network, it should request its own home TLM-PE to acquire location information. But, the real association information of IP address and location is stored in and accessible to the TLM-PE of the visited network. + +However, the service control entity has no idea about the TLM-PE in the visited network. The TLM-PE in the home network should proxy the request to the TLM-PE in the visited network and gets the response back. + +- 1) The UE gets a network attachment after the authentication at the NACE level in the visited network. +- 2-1) The AM-PE sends an authentication and authorization request to the TAA-PE in the visited network. +- 2-2) The TAA-PE forwards a NACE authentication and authorization request to the TAA-PE in the home network by proxy, because it does not have the user's network level database in its TUP-PE. The proxy request is delivered to the TAA-PE in the home network. +- 2-3) The TAA-PE in the home network authenticates and authorizes at the NACE level. It returns the NACE authentication data back. + +- 2-4) The TAA-PE sends the authentication response to the AM-PE in order to configure the forwarding table in the AM-PE. +- 2-5) The AM-PE sends the attachment ACK to inform of the starting of the packet forwarding at the AM-PE. +- 3-1) The UE sends IP configuration request to the NAC-PE after authentication. +- 3-2) The NAC-PE performs IP configuration procedure and returns the IP address. +- 4-1) The NAC-PE sends binding update to the TLM-PE by using the assigned IP address. +- 4-2 to 4-3) The TLM-PE stores the association of the IP address and line identifier. The TLM-PE in the NACE holds a binding between the IP address and the location information (contains the line identifier or the access point location information), which the user holds per the xDSL or WLAN connectivity. +- 5-1) The TLM-PE in the visited network registers its location to the TLM-PE in the home network in order to indicate its location. +- 5-2) The TLM-PE in the home network sends the result to the TLM-PE in the visited network. +- 6) The UE sends a SIP REGISTER message to the SCE to use services. +- 7-1) The SCE requests the location information to its home TLM-PE. +- 7-2) The TLM-PE in the home network sends a request of location to the TLM-PE in the visited network by proxy. +- 7-3) The TLM-PE in the visited network sends the location information of the UE. +- 7-4) The TLM-PE in the home network sends the location information to the SCE. + +## 6.1 Location registration + +The location registration request information flow contains the following information (see Table 6-1). + +**Table 6-1 – Location registration request (local TLM-PE → home TLM-PE)** + +| Information element | Explanation | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Globally Unique IP Address Information | A set of IP address information used for locating the access network in which the CPE is attached. | +| – Unique IP Address | The IP address for identifying the attached CPE. | +| – Address Realm | The addressing domain of the IP address (e.g., Subnet prefix or VPN ID). | +| Transport Subscriber Identifier | A globally unique identifier of the attached CPE. This identifier can be used for locating the transport subscription information for the CPE. | +| Attached Access Domain Name | The access domain name or the provider's name of the network. | +| Index of Local NACE | The address of the local NACE the user belongs to, which is registered by TLM-PE. | + +The location registration response information flow contains the following information (see Table 6-2). + +**Table 6-2 – Location registration response (home TLM-PE → local TLM-PE)** + +| Information element | Explanation | +|----------------------------------------|----------------------------------------------------------------------------------------------------| +| Globally Unique IP Address Information | A set of IP address information used for locating the access network in which the CPE is attached. | +| – Unique IP Address | The IP address for identifying the attached CPE. | +| – Address Realm | The addressing domain of the IP address (e.g., Subnet prefix or VPN ID). | +| Transport Subscriber Identifier | A globally unique identifier for the attached CPE. | +| Result | Result code (e.g., success, permanent failure, etc.). | + +## 6.2 Information query + +The information query request information flow contains the following information (see Table 6-3). + +**Table 6-3 – Information query request (home TLM-PE → local TLM-PE)** + +| Information element | Explanation | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Globally Unique IP Address Information | A set of IP address information used for locating the access network in which the CPE is attached. | +| – Unique IP Address | The IP address for identifying the attached CPE. | +| – Address Realm | The addressing domain of the IP address (e.g., Subnet prefix or VPN ID). | +| Transport Subscriber Identifier | A globally unique identifier of the attached CPE. This identifier can be used for locating the transport subscription information for the CPE. | +| Requested Items | The item list to the requested information. | +| Attached Access Domain Name | The access domain name or the provider's name of the network. | +| Index of Local NACE | The address of the local NACE the user belongs to, which is registered by TLM-PE. | + +The information query response information flow contains the following information (see Table 6-4). + +**Table 6-4 – Information query response (local TLM-PE → home TLM-PE)** + +| Information element | Explanation | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Transport Subscriber Identifier (optional) | A globally unique identifier for the attached CPE (see Note 1). | +| Location Information (optional) (see Note 2) | Location information (or a pointer to such information) in a form that is suitable for the requesting service control entity. | +| RACE Contact Point (optional) | The FQDN or IP address of the RACE where resource request shall be sent (i.e., PD-PE address). | +| CPE Type (optional) | The type of CPE. | +| Type of Access Transport (optional) | The type of access network to which the CPE is attached. | +| IP Connectivity Status (optional) | Whether IP connectivity to/from the user equipment is currently available. | + +**Table 6-4 – Information query response (local TLM-PE → home TLM-PE)** + +| Information element | Explanation | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Physical Connection Identifier (optional) | A local identifier for physical connection of access transport network that the CPE is attached to (e.g., IP address of PE-FE device, and MAC address or link ID and physical port). | +| Logical Connection Identifier (optional) | A local identifier for logical connection of access transport network to which the CPE is connected (e.g., ATM VPI/VCI, PPP, MPLS label, GTP tunnel and logical port). It can be used to locate the layer 2 connection and pertinent network devices for a particular CPE requesting the access transport resource. | +| NOTE 1 – This identifier may be used by the SCE when interacting with the RACE.
NOTE 2 – Location information disclosure depends on the requesting application and the subscriber's privacy restrictions. Privacy restrictions are defined in the privacy indicator stored in the TLM-PE. | | + +# 7 Description of procedure + +## 7.1 General + +The following clauses describe the realization of the functional procedures defined in the NACE specifications, using Diameter commands described in clause 9. This involves describing a mapping between information elements defined in the NACE specification and Diameter AVPs. + +In the tables that describe this mapping, each information element is marked as (M) mandatory, (C) conditional or (O) optional [ETSI ES 283 035]. + +## 7.2 Procedure on the Ng interface + +### 7.2.1 Location registration + +#### 7.2.1.1 Overview + +Location registration procedure is used by a local TLM-PE to notify the home TLM-PE of the occurrence of the location binding information. + +Location registration request/answer is mapped to the commands Push-Notifications-Request/Answer in the Diameter application specified in Sh interface [ETSI TS 129 329]. Tables 7-1 and 7-2 detail the involved information elements as defined in the NACE and their mapping to Diameter AVPs. + +**Table 7-1 – Mapping of location registration request to Diameter AVP** + +| Information element name | Diameter AVP | Category | +|---------------------------------|--------------------------|----------| +| Unique IP Address | Globally-Unique-Address | C | +| Address Realm | | | +| Transport Subscriber Identifier | User-Name | C | +| Attached Access Domain Name | Access-Domain-Name | M | +| Index of Local NACE | Local-NACE-Contact-Point | M | + +**Table 7-2 – Mapping of location registration response to Diameter AVP** + +| Information element name | Diameter AVP | Category | +|--------------------------|---------------------------------|----------| +| Result | Result-Code/Experimental_Result | M | + +#### 7.2.1.2 Procedure at the local TLM-PE + +The local TLM-PE shall request the Location Registration Request by including the following information elements: + +- 1) At least, a Globally-Unique-Address or a User-Name AVP shall be included. The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and an Address-Realm AVP. +- 2) The Access-Domain-Name AVP and the Local-NACE-Contact-Point shall be present. + +#### 7.2.1.3 Procedure at the home TLM-PE + +Upon reception of a Location Registration Request, the home TLM-PE shall: + +- 1) Check both the Globally-Unique-Address AVP and the User-Name AVP. +- 2) If the Globally-Unique-Address AVP is present, go to step 6). Otherwise, go to the next step. +- 3) If the Globally-Unique-Address AVP is absent, but the User-Name AVP is present, go to step 5). Otherwise, go to the next step. +- 4) Because both the Globally-Unique-Address AVP and the User-Name AVP are absent, return a Location Registration Response with Result-Code set to DIAMETER\_MISSING\_AVP and stop this procedure. If the Access-Domain-Name AVP and the Local-NACE-Contact Point AVP are absent, return a Location Registration Response with Result-Code set to DIAMETER\_MISSING\_AVP and stop this procedure. +- 5) If more than one record includes the same subscriber identity matching the value of the User-Name AVP and no Globally-Unique-Address AVP is included, return a Location Registration Response with Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY and stop this procedure. Otherwise, go to the next step. +- 6) Under temporary overload conditions, the home TLM-PE shall stop processing the request and return a Location Registration Response with the Experimental-Result-Code set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE and stop this procedure. Otherwise, go to the next step. +- 7) If the home TLM-PE cannot fulfill the received request for reasons not stated in the above steps, e.g., due to database error, it shall stop processing the request and set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. +- 8) The Access-Domain-Name AVP and the Local-NACE-Contact Point AVP are stored in the home TLM-PE and the home TLM-PE shall return the Result-Code AVP set to DIAMETER\_SUCCESS in the Location Registration Response and stop this procedure. + +### 7.2.2 Information query + +#### 7.2.2.1 Overview + +The information query procedure is used by a home TLM-PE to retrieve, from the local TLM-PE, location information and other data related to an access session. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in Sh interface [ETSI TS 129 329]. Tables 7-3 and 7-4 detail the involved information elements as defined in the NACE and their mapping to Diameter AVPs. + +**Table 7-3 – Mapping of information query request to Diameter AVP** + +| Information element name | Diameter AVP | Category | +|---------------------------------|--------------------------|----------| +| Unique IP Address | Globally-Unique-Address | C | +| Address Realm | | | +| Transport Subscriber Identifier | User-Name | C | +| Requested Items | Requested-Information | O | +| Attached Access Domain Name | Access-Domain-Name | M | +| Index of Local NACE | Local-NACE-Contact-Point | M | + +**Table 7-4 – Mapping of information query response to Diameter AVP** + +| Information element name | Diameter AVP | Category | +|---------------------------------|---------------------------------|----------| +| Result | Result-Code/Experimental-Result | M | +| Transport Subscriber Identifier | User-Name | O | +| Location Information | Location-Information | O | +| RACE contact point | RACE-Contact-Point | O | +| Access Transport Network Type | Access-Network-Type | O | +| CPE Type | CPE-Type | O | +| IP Connectivity status | IP-connectivity-status | O | +| Physical Connection Identifier | Physical-Connection-Identifier | O | +| Logical Connection Identifier | Logical-Connection-Identifier | O | + +#### **7.2.2.2 Procedure at the home TLM-PE** + +The home TLM-PE shall request the Information Query Request by including the following information elements: + +- 1) Either a Globally-Unique-Address AVP or a User-Name AVP will be present. The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value and an Address-Realm AVP. +- 2) The Access-Domain-Name AVP and the Local-NACE-Contact-Point shall be present. +- 3) The Requested-Information AVP shall be present if specific information is requested, and shall be absent if all available information is requested. + +#### **7.2.2.3 Procedure at the local TLM-PE** + +Upon reception of an Information Query Request, the home TLM-PE shall: + +- 1) Check both the Globally-Unique-Address AVP and the User-Name AVP. +- 2) If the Globally-Unique-Address AVP is present, go to step 6) to use this information as a key to retrieve the requested session information. Otherwise, go to the next step. +- 3) If the Globally-Unique-Address AVP is absent, but the User-Name AVP is present, go to step 5) to use the latter information as a key to retrieve the requested session information. Otherwise, go to the next step. +- 4) Because both the Globally-Unique-Address AVP and the User-Name AVP are absent, return an Information Query Response with a Result-Code set to DIAMETER\_MISSING\_AV and stop this procedure. If the Access-Domain-Name AVP and the Local-NACE-Contact-Point AVP are absent, return an Information Query Response with Result-Code set to DIAMETER\_MISSING\_AV and stop this procedure. + +- 5) If more than one record includes the same subscriber identity matching the value of the User-Name AVP and no Globally-Unique-Address AVP is included, return an Information Query Response with Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY and stop this procedure. Otherwise, go to the next step. +- 6) If no session record is stored for the Globally-Unique-Address AVP or the User-Name AVP, return an Information Query Response with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_USER\_UNKNOWN and stop this procedure. Otherwise, go to the next step. +- 7) Under temporary overload conditions, the local TLM-PE shall stop processing the request and return an Information Query Response with the Experimental-Result-Code set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE and stop this procedure. Otherwise, go to the next step. +- 8) If the local TLM-PE cannot fulfill the received request for reasons not stated in the above steps, e.g., due to database error, it shall stop processing the request and set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. +- 9) Check which session data can be returned to the home TLM-PE, based on local policy rules and per-subscriber privacy information stored in the local TLM-PE. If the session data to be retrieved is currently being updated by another entity, the local TLM-PE may delay the response message until the update has been completed and shall include in the response message the updated data requested. The requested operation shall take place and the local TLM-PE shall return the Result-Code AVP set to DIAMETER\_SUCCESS and the session data in the Information Query Response and stop this procedure. + +# **8 Use of Diameter-based protocol** + +With the clarifications listed in the following clauses, the Diameter Base Protocol defined by [IETF RFC 3588] shall apply. + +## **8.1 Securing Diameter messages** + +For secure transport of Diameter messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found in [b-IETF RFC 3554]. + +## **8.2 Accounting functionality** + +Accounting functionality (accounting session state machine, related command codes and AVPs) is not used at the Ng interface. + +## **8.3 Use of sessions** + +Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server [IETF RFC 3588]. + +The Diameter-based protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests or responses the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in [IETF RFC 3588]. As a consequence, the server does not maintain any state information about this session and the client does not need to send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +## 8.4 Transport protocol + +Diameter messages over the Ng interface shall make use of stream control transport protocol (SCTP) [IETF RFC 2960] and shall utilize the new SCTP checksum method specified in [IETF RFC 3309]. + +## 8.5 Routing considerations + +This clause specifies the use of the Diameter routing AVPs, Destination-Realm and Destination-Host. + +With regard to the Diameter protocol used at the Ng interface, the local TLM-PE acts as a Diameter server and the home TLM-PE acts as the Diameter client. + +Requests initiated by the local TLM-PE towards a home TLM-PE shall include both Destination-Host and Destination-Realm AVPs. The local TLM-PE obtains the Destination-Host AVP to use in requests towards a home TLM-PE from configuration data and/or the subscriber profile. Consequently, the Destination-Host AVP is declared as mandatory in the Augmented Backus-Naur Form (ABNF) for all requests initiated by the TLM-PE. Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +## 8.6 Advertising application support + +The Capabilities-Exchange-Request (CER) and the Capabilities-Exchange-Answer (CEA) commands are specified in [IETF RFC 3588]. The Diameter-base application identifier (0) shall be used in the Diameter message header of these messages. + +If both home and local TLM-PE indicate support of the Ng application, then the Ng application identifier (16777263) shall be used in the Diameter message header of all subsequent messages exchanged within this association. + +Support of the Ng application within the CER/CEA is indicated by supplying an instance of the Vendor-Specific-Application-Id containing a Vendor-Id AVP set to ITU-T (11502) and an Auth-Application-Id AVP set to Ng (16777263). + +The home TLM-PE and the local TLM-PE are required to advertise the support of AVPs specified in the Diameter related documents of 3GPP, ETSI and ITU-T, by including the values 10415 (3GPP), 13019 (ETSI) and 11502 (ITU-T) in three different instances of the Supported-Vendor-Id AVP in the CER and CEA commands respectively. + +**Table 8-1 – Vendor identifiers for Ng** + +| Vendor | Vendor identifier | +|--------|-------------------| +| 3GPP | 10415 | +| ETSI | 13019 | +| ITU-T | 11502 | + +NOTE – The Vendor-Id AVP included in Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) commands that are not included in the Vendor-Specific-Application-Id AVPs, as described above, shall indicate the manufacturer of the Diameter node as per [IETF RFC 3588]. + +# 9 Message specification + +## 9.1 Commands + +This Recommendation re-uses the four Diameter commands identified in Table 9-1 which are defined in [ETSI TS 129 329]. Other commands are ignored by the local TLM-PE and the home TLM-PE. + +**Table 9-1 – Command code** + +| Command | Abbreviation | Defining reference | Command code | See clause | +|---------------------------|--------------|--------------------|--------------|------------| +| Push-Notification-Request | PNR | [ETSI TS 129 329] | 309 | 9.1.1 | +| Push-Notification-Answer | PNA | [ETSI TS 129 329] | 309 | 9.1.2 | +| User-Data-Request | UDR | [ETSI TS 129 329] | 306 | 9.1.3 | +| User-Data-Answer | UDA | [ETSI TS 129 329] | 306 | 9.1.4 | + +### 9.1.1 Push-Notification-Request (PNR) command + +The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the "R" bit set in the Command Flags field, is sent by a Diameter server to a Diameter client in order to notify changes in the user data in the server. This command is defined in [ETSI TS 129 329] and used with additional AVPs defined in this Recommendation. + +*Message format:* + +``` +< Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777263> + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ Globally-Unique-Address ] + [ User-Name ] + { Access-Domain-Name } + { Local-NACE-Contact-Point } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 9.1.2 Push-Notification-Answer (PNA) command + +The Push-Notification-Answer (PNA) command, indicated by the Command-Code field set to 309 and the "R" bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request (PNR) command. The Experimental-Result AVP may contain one of the values defined in clause 9.2. + +*Message format:* + +``` +< Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777263> + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ AVP ] +``` + +``` + +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 9.1.3 User-Data-Request (UDR) command + +The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the "R" bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request user data. This command is defined in [ETSI TS 129 329] and used with additional AVPs defined in this Recommendation. + +*Message format:* + +``` + +< User-Data-Request > ::= < Diameter Header: 306, REQ, PXY, 16777263> + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ Globally-Unique-Address ] + [ User-Name ] + [ Requested-Information ] + { Access-Domain-Name } + { Local-NACE-Contact-Point } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 9.1.4 User-Data-Answer (UDA) command + +The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the "R" bit cleared in the Command Flags field, is sent by a server in response to the User-Data-Request command. This command is defined in [ETSI TS 129 329] and used with additional AVPs defined in this Recommendation. The Experimental-Result AVP may contain one of the values defined in clause 9.2. + +*Message format:* + +``` + +< User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777263> + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Physical-Connection-Identifier ] + [ Logical-Connection-Identifier ] + [ Access-Network-Type ] + [ Location-Information ] + [ RACE-Contact-Point ] + [ CPE-Type ] + [ IP-Connectivity-status ] + *[ AVP ] + *[ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +## 9.2 Experimental-Result-Code AVP values + +This clause defines specific values of the Experimental-Result-Code AVP used in this Recommendation. Most of these are imported from 3GPP and ETSI specifications, as indicated in the clauses below. + +### 9.2.1 Experimental-Result-Code AVP values imported from [ETSI TS 129 229] + +This clause defines the specific values of the Experimental-Result-Code AVP imported from [ETSI TS 129 229] (the vendor-id is ETSI): + +DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +The request failed because the IP address or Globally-Unique Address is not found. + +DIAMETER\_USER\_DATA\_NOT\_AVAILABLE (4100) + +The requested data is not available at this time to satisfy the requested operation. + +## 9.3 Attribute value pairs (AVPs) + +The following tables summarize the AVPs used in this Recommendation. These are, in addition to the AVPs, defined in [IETF RFC 3588]. + +Table 9-2 describes the Diameter AVPs that are used within this Recommendation that have been defined by ETSI [ETSI ES 283 035], providing their AVP code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-Id header of all AVPs identified in the following table shall be set to ETSI (13019). These AVPs are described in this Recommendation for information; however, the normative detail for these AVPs is contained in [ETSI ES 283 035]. + +**Table 9-2 – Diameter AVPs imported from [ETSI ES 283 035]** + +| Attribute name | AVP code | Clause defined | Value type (Note 2) | AVP flag rules (Note 1) | | | | May encrypt | +|-----------------------|----------|----------------|---------------------|-------------------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | | +| Location-Information | 350 | 9.3.4 | Grouped | V | M | | | Y | +| RACE-Contact-Point | 351 | 9.3.5 | DiameterIdentity | V | M | | | Y | +| CPE-Type | 352 | 9.3.6 | OctetString | V | M | | | Y | +| Requested-Information | 353 | 9.3.2 | Enumerated | V | | | M | Y | + +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 3588]. + +NOTE 2 – The value types are defined in [IETF RFC 3588]. + +Table 9-3 describes the Diameter AVPs defined by the e4 interface protocol [ETSI ES 283 034] and used within this Recommendation. These AVPs are described in this Recommendation for information; however, the normative detail for these AVPs is contained in [ETSI ES 283 034]. The Vendor-Id header of all AVPs defined in Table 9-3 shall be set to ETSI (13019). + +**Table 9-3 – Diameter AVPs imported from [ETSI ES 283 034]** + +| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt | +|--------------------------------|----------|----------------|-------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | | +| Globally-Unique-Address | 300 | 9.3.1 | Grouped | M,V | | | | Y | +| Logical-Connection-Identifier | 302 | 9.3.9 | OctetString | V | M | | | Y | +| Access-Network-Type | 306 | 9.3.3 | Grouped | V | M | | | Y | +| IP-Connectivity-Status | 305 | 9.3.7 | Enumerated | V | M | | | Y | +| Physical-Connection-Identifier | 313 | 9.3.8 | UTF8String | V | M | | | Y | + +Table 9-4 describes the AVPs defined solely within this Recommendation. The ITU-T Vendor-Id (11502) shall be used in the Vendor-Id field of the AVP header. + +**Table 9-4 – Diameter AVPs defined in this Recommendation** + +| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt | +|--------------------------|----------|----------------|------------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | | +| Access-Domain-Name | 1030 | 9.3.10 | OctetString | M,V | | | | Y | +| Local-NACE-Contact-Point | 1031 | 9.3.11 | DiameterIdentity | M,V | | | | Y | + +### 9.3.1 Globally-Unique-Address AVP + +The Globally-Unique-IP-Address AVP (AVP code 300 13019) is of type Grouped. + +*AVP format:* + +``` +Globally-Unique-Address ::= < AVP Header: 300 13019 > + [Framed-IP-Address] + [Framed-IPv6-Prefix] + [Address-Realm] +``` + +### 9.3.2 Requested-Information AVP + +The Requested-Information AVP (AVP code 353 13019) is of type Enumerated. The following values are defined: + +- SUBSCRIBER-ID (0). +- LOCATION-INFORMATION (1). +- RACE-CONTACT-POINT (2). +- ACCESS-NETWORK-TYPE (3). +- CPE-TYPE (4). +- LOGICAL-CONNECTION-IDENTIFIER (5). +- PHYSICAL-CONNECTION-IDENTIFIER (6). +- ACCESS-NETWORK-TYPE (7). + +- DEFAULT-CONFIGURATION (8). +- TRANSPORT-RESOURCE-SUBSCRIPTION (9). +- IP-CONNECTIVITY-STATUS (10). + +### 9.3.3 Access-Network-Type AVP + +The Access-Network-Type AVP (AVP code 306 13019) is of type Grouped; it indicates the type of port on which the user equipment is connected and the type of aggregation network. + +*AVP format:* + +``` +Access-Network-Type ::= < AVP Header: 306 13019 > + {NAS-Port-Type} + [Aggregation-Network-Type] +``` + +### 9.3.4 Location-Information AVP + +The Location-Information AVP (AVP code 350 13019) is of type Grouped. + +*AVP format:* + +``` +Location-Information ::= < AVP Header: 350 13019 > + [Line-Identifier] + * [AVP] +``` + +### 9.3.5 RACE-Contact-Point AVP + +The RACE-Contact-Point AVP (AVP code 351 13019) is of type DiameterIdentity and identifies the RACE element to which the resource reservation requests shall be sent. + +### 9.3.6 CPE-Type AVP + +The CPE-Type AVP (AVP code 352 13019) is of type OctetString and contains a value of the User Class DHCP Option (77). + +### 9.3.7 IP-Connectivity-Status AVP + +The IP-Connectivity-Status AVP (AVP code 305 13019) is of type Enumerated. + +The following values are defined: + +- IP-CONNECTIVITY-ON (0). +- IP-CONNECTIVITY-LOST (1). + +### 9.3.8 Physical-Connection-Identifier AVP + +The Physical-Connection-Identifier AVP (AVP code 313 13019) is of type UTF8String and identifies the physical access to which the user equipment is connected. It includes a port identifier and the identity of the access node where the port resides. + +### 9.3.9 Logical-Connection-Identifier AVP + +The Logical-connection-identifier AVP (AVP code 302 13019) is of type OctetString. This AVP contains either a Circuit-ID (as defined in [IETF RFC 3046]) or a technology independent identifier. + +NOTE – In the xDSL/ATM case, the logical access ID may explicitly contain the identity of the VP and the VC carrying the traffic. + +### 9.3.10 Access-Domain-Name AVP + +The Access-Domain-Name AVP (ITU-T AVP code 1030 11502) is of type OctetString, and provides information about the access domain name or the provider's name of the network. + +### **9.3.11 Local-NACE-Contact-Point AVP** + +The Local-NACE-Contact-Point AVP (ITU-T AVP code 1031 11502) is of type DiameterIdentity and identifies the Local NACE the user belongs to which is registered by the TLM-PE. + +## **9.4 Use of namespaces** + +This clause contains the namespaces that have either been created in this Recommendation, or the values assigned to existing namespaces managed by the Internet Assigned Numbers Authority (IANA). + +### **9.4.1 AVP codes** + +This Recommendation uses AVP values from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. In addition, this Recommendation assigns AVP code values within the Diameter AVP Code namespace managed by ITU-T. See clause 9.3. + +### **9.4.2 Experimental-Result-Code AVP values** + +This Recommendation assigns the Experimental-Result-Code AVP values from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. See clause 9.2. + +### **9.4.3 Command code values** + +This Recommendation does not assign command code values but uses existing commands defined by the Internet Engineering Task Force (IETF), including those requested by 3GPP. + +### **9.4.4 Application-ID value** + +This Recommendation defines the Ng Diameter application with application ID 16777263. The vendor identifier assigned by IANA to ITU-T () is 11502. + +# **10 Security considerations** + +These security requirements within the functional requirements and architecture of the NACF are addressed by the security requirements for NGN [ITU-T Y.2701]. The Ng interface shall follow the security requirements of the network attachment control functions (NACF) [ITU-T Y.2014]. + +Clause 8.1 recommends the use of IPSec to ensure secure transport of Diameter messages. Guidelines on the use of SCTP with IPSec can be found in [b-IETF RFC 3554]. + +Further considerations are provided in the security considerations section of [IETF RFC 3588]. + +# Appendix I + +## Scenarios using Ng interface + +(This appendix does not form an integral part of this Recommendation) + +## I.1 Location information service from the home network with DHCP-based network attachment + +### I.1.1 Access scenarios for location registration request/response + +This clause provides high-level information flows using Ng interface that define the location registration and the information query between the home TLM-PE and the local TLM-PE. + +The NACE relies on several stages in the network attachment process. Figure I.1 shows the high-level information flows and the procedures of NACE. This figure also shows the basic network attachment procedure in the home access domain. Depending on the access domain, some additional stages for the location registration at the home TLM-PE can be applied as shown in Figure I.2. + +![Figure I.1: Information flows for location registration. This sequence diagram shows interactions between CPE, AM-PE, NAC-PE, TAA-PE, TLM-PE, and RACE. The process starts with 802.1x/PANA authentication, followed by access requests and responses. DHCP requests and responses are exchanged between CPE and NAC-PE via AM-PE. Network location information is passed from NAC-PE to TLM-PE, which then pushes the profile to RACE.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant AM-PE + participant NAC-PE + participant TAA-PE + participant TLM-PE + participant RACE + + Note left of CPE: 1. 802.1x/PANA implicit authentication + CPE->>AM-PE: + Note right of AM-PE: 2. Access request (Authentication with no IP address) + AM-PE->>TAA-PE: + Note right of TAA-PE: 3. Access response (Authentication with no IP address) + TAA-PE->>AM-PE: + Note left of AM-PE: 5.1 DHCP request + AM-PE->>NAC-PE: + Note right of NAC-PE: 5.2 Forward the DHCP request and option 120 (RFC 3861) + NAC-PE->>AM-PE: + Note left of AM-PE: 6.1 DHCP response (IP address and P-CSCF address) + AM-PE->>CPE: + Note right of NAC-PE: 6.2 Network location information + NAC-PE->>TLM-PE: + Note right of TLM-PE: 4. Transport subscription profile information + TLM-PE->>RACE: + Note right of RACE: 7. Profile push + +``` + +Figure I.1: Information flows for location registration. This sequence diagram shows interactions between CPE, AM-PE, NAC-PE, TAA-PE, TLM-PE, and RACE. The process starts with 802.1x/PANA authentication, followed by access requests and responses. DHCP requests and responses are exchanged between CPE and NAC-PE via AM-PE. Network location information is passed from NAC-PE to TLM-PE, which then pushes the profile to RACE. + +Figure I.1 – Information flows for location registration + +![Figure I.2: Additional information flows for location registration at the home TLM-PE. This sequence diagram extends Figure I.1 by adding the 'local TLM-PE', 'SCE', and 'home TLM-PE'. It shows the flow of information from the visited network's TAA-PE through the local TLM-PE and SCE to the home TLM-PE, where a location registration request and response are exchanged over the Ng interface. The profile push to RACE occurs after the home TLM-PE is updated.](bb3354f497635d15bef873577125c48d_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant AM-PE as AM-PE In visited network + participant NAC-PE as NAC-PE In visited network + participant TAA-PE as TAA-PE In visited network + participant local_TLM-PE as local TLM-PE + participant RACE as RACE In visited network + participant SCE + participant home_TLM-PE as home TLM-PE + participant TAA-PE-home as TAA-PE In home network + + Note left of CPE: 1. 802.1x/PANA implicit authentication + CPE->>AM-PE: + Note right of AM-PE: 2.1 Access request (Authentication with no IP address) + AM-PE->>TAA-PE: + Note right of TAA-PE: 2.2 Access request (Authentication with no IP address) + TAA-PE->>local_TLM-PE: + Note right of local_TLM-PE: 3.1 Access response (Authentication with no IP address) + local_TLM-PE->>TAA-PE: + Note right of TAA-PE: 3.2 Access response (Authentication with no IP address) + TAA-PE->>AM-PE: + Note left of AM-PE: 5.1 DHCP request + AM-PE->>NAC-PE: + Note right of NAC-PE: 5.2 Forward the DHCP request and option 120 (RFC 3861) + NAC-PE->>AM-PE: + Note left of AM-PE: 6.1 DHCP response (IP address and P-CSCF address) + AM-PE->>CPE: + Note right of NAC-PE: 6.2 Network location information + NAC-PE->>local_TLM-PE: + Note right of local_TLM-PE: 4. Transport subscription profile information + local_TLM-PE->>SCE: + Note right of SCE: 7.1 Location registration request + SCE->>home_TLM-PE: + Note right of home_TLM-PE: 7.2 Location registration response + home_TLM-PE->>SCE: + Note right of SCE: Ng I/F + local_TLM-PE->>RACE: + Note right of RACE: 8. Profile push + +``` + +Figure I.2: Additional information flows for location registration at the home TLM-PE. This sequence diagram extends Figure I.1 by adding the 'local TLM-PE', 'SCE', and 'home TLM-PE'. It shows the flow of information from the visited network's TAA-PE through the local TLM-PE and SCE to the home TLM-PE, where a location registration request and response are exchanged over the Ng interface. The profile push to RACE occurs after the home TLM-PE is updated. + +Figure I.2 – Additional information flows for location registration at the home TLM-PE + +In the first stage of the network attachment process, the CPE will be authenticated and authorized. In step 1, CPE initiates authentication based on [b-IETF RFC 5191]. In step 2, AM-PE relays and translates PPP request to an access request to the TAA-PE for authentication. It occurs prior or during the IP address allocation procedure (step 2). The authentication process relies on the mechanisms and identities described in clauses 6, 7 and 8 in [ITU-T Y.2014]. Step 2 involves the authorization for access to the network based on the transport subscription profile. In step 2.1, a specific transport subscription profile, related e.g., to QoS, may be also downloaded from the home NGN network to the visited NGN network (from the TAA-PE-server to the TAA-PE-proxy mode). + +When the authentication is successful and the CPE is authorized to use access network resources, configuration of access network based on the transport subscription profile is performed in step 5. During step 6.1, the NAC-PE allocates the IP configuration information and provides it to the user equipment/CPE. This mapping information between the allocated IP configuration information and the logical connection identifier is forwarded to the TLM-PE (via the Ne reference point) in step 6.2, which correlates this with the transport subscriber identifier and the transport subscription profile. It also implies that the specific transport subscription profile information for the authenticated user be required to be forwarded to the TLM-PE via the Nc reference point. The profile information includes at least the logical connection identifier (i.e., line ID), the transport subscriber identifier and the transport resource subscription information, which may be the QoS profile downloaded from the home NGN network or a default configuration profile, and the identification of the edge PE-PE device. + +The local TLM-PE may also register to the home TLM-PE, the association between the transport location information received from the NAC-PE and the geographical location information in step 7.1. In step 8, the TLM-PE pushes the binding information to the RACE via the TC-TC1 reference point to configure the line with the transport subscription profile information. + +### I.1.2 Access scenarios for information query request/response + +The service control entities (SCEs) can retrieve information about the characteristics of the IP-connectivity session used to access (e.g., network location information) from the TLM-PE. When the user/CPE moves in the different access domain, the service control functions access the TLM-PE in the visited network for location information via a proxy-TLM-PE in the home network as shown in Figure I.3. The form of location information that is provided by the TLM-PE depends on the requestor. + +![Sequence diagram showing information flows for an information query request/response between SCE, home TLM-PE, and local TLM-PE.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant AM-PE as AM-PE
In visited
network + participant NAC-PE as NAC-PE
In visited
network + participant TAA-PE as TAA-PE
In visited
network + participant local_TLM-PE as local
TLM-PE + participant RACE as RACE
In visited
network + participant SCE + participant home_TLM-PE as home
TLM-PE + participant TAA-PE_home as TAA-PE
In home
network + + SCE->>home_TLM-PE: 1. Information query request + home_TLM-PE->>local_TLM-PE: 2. Information query request + Note over local_TLM-PE, home_TLM-PE: Ng I/F + local_TLM-PE-->>home_TLM-PE: 3. Information query response + home_TLM-PE-->>SCE: 4. Information query response + +``` + +Sequence diagram showing information flows for an information query request/response between SCE, home TLM-PE, and local TLM-PE. + +**Figure I.3 – Information flows for information query** + +## I.2 NACE-SCE bundled authentication + +### I.2.1 Case 1: NACE-SCE bundled authentication based on line information + +![Sequence diagram for NACE-SCE bundled authentication for fixed access network only. The diagram shows interactions between NGN UE, Visited NACE (AM-PE, TAA-PE/TUP-PE, TLM-PE), Home NACE (TAA-PE/TUP-PE, TLM-PE), and SCE (P-CSC-PE, I-CSC-PE, S-CSC-PE, SAA-PE/SUP-PE).](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +The sequence diagram illustrates the NACE-SCE bundled authentication process for a fixed access network. The participants are grouped into three domains: Visited NACE, Home NACE, and SCE. + +- NGN UE**: Initiates the process with **NACF Authentication & Network Attachment** and **Trying service authentication**. +- Visited NACE**: Contains **AM-PE**, **TAA-PE/TUP-PE**, and **TLM-PE**. The **TLM-PE** sends a **1. REGISTER** message to the SCE. +- Home NACE**: Contains **TAA-PE/TUP-PE** and **TLM-PE**. It receives a **2.1 UDR** from the SCE and responds with **2.2 UDR (IP address)** and **3.1 UDA (location info=line id)** via the **Ng I/F**. +- SCE**: Contains **P-CSC-PE**, **I-CSC-PE**, **S-CSC-PE**, and **SAA-PE/SUP-PE**. + - The **P-CSC-PE** receives **1. REGISTER** and checks if a **Security association required?** + - If **Yes**, it sends **2.1 UDR** to the Home NACE. + - It receives **3.2 UDA** from the Home NACE and sends **4. REGISTER (P-Access Network-info = line id)** to the I-CSC-PE. + - The I-CSC-PE sends **5. UAR** to the S-CSC-PE. + - The S-CSC-PE performs **6. UAA** and **7. REGISTER (P-Access Network-info = line id)** to the SAA-PE/SUP-PE. + - The SAA-PE/SUP-PE sends **8. MAR** and performs a **Check User profile**. + - It sends **9. MAA (line id)** back to the S-CSC-PE. + - The S-CSC-PE performs a **Compare line id?** check. + - If **equal**, it sends **10. SAR** and **11. SAA** to the SAA-PE/SUP-PE. + - The SAA-PE/SUP-PE responds with **12. 200 Ok** to the S-CSC-PE. + - The S-CSC-PE then sends **13. 200 Ok** to the P-CSC-PE. + - Finally, the P-CSC-PE sends **14. 200 Ok** back to the NGN UE. + +Sequence diagram for NACE-SCE bundled authentication for fixed access network only. The diagram shows interactions between NGN UE, Visited NACE (AM-PE, TAA-PE/TUP-PE, TLM-PE), Home NACE (TAA-PE/TUP-PE, TLM-PE), and SCE (P-CSC-PE, I-CSC-PE, S-CSC-PE, SAA-PE/SUP-PE). + +Figure I.4 – NACE-SCE bundled authentication for the fixed access network only + +This clause describes how UEs undergo authentication in NACE and simultaneously gain service layer authentication using the single sign-on NACE-SCE bundled authentication with line information. + +- 0) The UE gets network attachment following the authentication at the NACE level. The TLM-PE in the NACE holds a binding between the IP address and the location information (contains the line identifier), held by the user as per the xDSL connectivity. The selection of the authentication (whether NACE-SCE bundled authentication is possible or not) is done at the SUP-PE level on an SCE-user basis. +- 1) The SIP REGISTER message reaches P-CSC-PE. + +2.1-2.2) The P-CSC-PE knows whether or not security association is required at this point, based on the SIP signalling, presence of local policies and L3/L2 address. During the SIP registration, the P-CSC-PE locates the TLM-PE based on the UE's IP address or/and based on the information of the access network from which the P-CSC-PE receives the IP packet. P-CSC-PE performs a UDR request with the local TLM-PE via the home TLM-PE over the S-TC1 interface and the Ng interface. The key for the query is the IP address used by the UE. + +3.1-3.2) The local TLM-PE sends the UDA response to the P-CSC-PE via the home TLM-PE including the location information of the UE. + +4) The P-CSC-PE appends the NACE location information to the SIP REGISTER message and forwards the REGISTER message to the I-CSC-PE. + +5) The I-CSC-PE queries the SUP-PE using the UAR request. + +6) The SUP-PE returns a UAA message for selecting the S-CSC-PE. + +7) The I-CSC-PE forwards the REGISTER message to the S-CSC-PE. + +8) The S-CSC-PE queries the SUP-PE using the MAR request. + +9) If line-based NACE bundling is the preferred authentication scheme, the SUP-PE returns a message with the location information of the user identified by IMPI and IMPU. + +The S-CSC-PE performs final authentication by comparing the location information embedded in the REGISTER message with the location information received from the SUP-PE. If they match, the user is successfully authenticated. + +10-14) If the UE is successfully authenticated, the S-CSC-PE assigns a unique IP address to the SUP-PE using the SAR message, and a SIP 200 OK message is then sent to the UE. + +### I.2.2 Case 2: NACE-SCE bundled authentication based on the authentication context + +![Sequence diagram for NACE-SCE bundled authentication. Lifelines: NGN UE, Visited NACE (AM-PE, TAA-PE/TUP-PE, TLM-PE), Home NACE (TAA-PE/TUP-PE, TLM-PE), and SCE (P-CSC-PE, I-CSC-PE, S-CSC-PE, SAA-PE/SUP-PE). The process starts with NACF Authentication & Network Attachment and Trying service authentication at the UE. 0.1 push information (subscriber id, authentication context) is sent from Home NACE to SCE. 1. REGISTER is sent from UE to P-CSC-PE. A decision 'Security association required?' is made at P-CSC-PE. If 'Yes', 2.1 UDR is sent to TAA-PE/TUP-PE, which responds with 2.2 UDR (IP address) and 3.1 UDA (authentication context) via the Ng I/F. 3.2 UDA is sent from TAA-PE/TUP-PE to P-CSC-PE. 4. REGISTER (authentication context) is sent from P-CSC-PE to S-CSC-PE. 5. UAR, 6. UAA, 7. REGISTER (authentication context), 8. MAR, 9. MAA (authentication context) are exchanged between S-CSC-PE and SAA-PE/SUP-PE. A decision 'Compare authentication context?' is made at SAA-PE/SUP-PE. If 'equal', 10. SAR, 11. SAA, 12. 200 Ok are sent from SAA-PE/SUP-PE to S-CSC-PE. 13. 200 Ok is sent from S-CSC-PE to P-CSC-PE. 14. 200 Ok is sent from P-CSC-PE to NGN UE.](5414f65867392f05ba0063b208eeb5e1_img.jpg) + +Sequence diagram for NACE-SCE bundled authentication. Lifelines: NGN UE, Visited NACE (AM-PE, TAA-PE/TUP-PE, TLM-PE), Home NACE (TAA-PE/TUP-PE, TLM-PE), and SCE (P-CSC-PE, I-CSC-PE, S-CSC-PE, SAA-PE/SUP-PE). The process starts with NACF Authentication & Network Attachment and Trying service authentication at the UE. 0.1 push information (subscriber id, authentication context) is sent from Home NACE to SCE. 1. REGISTER is sent from UE to P-CSC-PE. A decision 'Security association required?' is made at P-CSC-PE. If 'Yes', 2.1 UDR is sent to TAA-PE/TUP-PE, which responds with 2.2 UDR (IP address) and 3.1 UDA (authentication context) via the Ng I/F. 3.2 UDA is sent from TAA-PE/TUP-PE to P-CSC-PE. 4. REGISTER (authentication context) is sent from P-CSC-PE to S-CSC-PE. 5. UAR, 6. UAA, 7. REGISTER (authentication context), 8. MAR, 9. MAA (authentication context) are exchanged between S-CSC-PE and SAA-PE/SUP-PE. A decision 'Compare authentication context?' is made at SAA-PE/SUP-PE. If 'equal', 10. SAR, 11. SAA, 12. 200 Ok are sent from SAA-PE/SUP-PE to S-CSC-PE. 13. 200 Ok is sent from S-CSC-PE to P-CSC-PE. 14. 200 Ok is sent from P-CSC-PE to NGN UE. + +Figure I.5 – NACE-SCE bundled authentication for both the fixed and the mobile access network + +This clause describes how UEs authenticate the NACE and simultaneously also gain a service layer authentication using the single sign-on NACE-SCE bundled authentication with a unique context information (for one example, we can use authentication context). + +Here, the NACE-SCE bundle authentication scenario example, that is applicable to networks including the mobile access network, will be considered unlike the scenario in I.2.1. + +As to the mobile subscriber, the line information does not exist like the fixed user. Therefore, the subscriber id and the access authentication context need to be delivered towards SUP-PE in case of being authenticated. + +- 0) The UE gets network attachment after authentication at the NACE level. +- 0.1) The TUP-PE delivers subscriber id and authentication context to the SUP-PE. The selection of the authentication (whether NACE-SCE bundled authentication is possible or not) is done at the SUP-PE level on a SCE-user basis. The relation between the subscriber identity and the SCE-user identities (IMPI and IMPU) is already known to the SUP-PE. +- 1) The SIP REGISTER message reaches P-CSC-PE. + +- 2.1-2.2) The P-CSC-PE knows whether or not a security association is required at this point, based on the SIP signalling, presence of local policies and L3/L2 address. During the SIP registration, the P-CSC-PE locates the TLM-PE based on the UE's IP address or/and based on the information of the access network from which the P-CSC-PE receives the IP packet. P-CSC-PE performs the UDR request toward the local TLM-PE via the home TLM-PE over the S-TC1 interface and the Ng interface. The key for the query is the IP address used by the UE. +- 3.1-3.2) The local TLM-PE sends the UDA response to the P-CSC-PE via the home TLM-PE including the authentication context of the UE. +- 4) The P-CSC-PE appends the authentication context to the SIP REGISTER message and forwards the REGISTER message to the I-CSC-PE. + - 5) The I-CSC-PE queries the SUP-PE using the UAR request. + - 6) The SUP-PE returns a UAA message for selecting the S-CSC-PE. + - 7) The I-CSC-PE forwards the REGISTER message to the S-CSC-PE. + - 8) The S-CSC-PE queries the SUP-PE using the MAR request. + - 9) The SUP-PE returns a message with the authentication context of the user identified by the IMPI and IMPU, if Authentication Context-based NACE bundling is the preferred authentication scheme. +- The S-CSC-PE finally authenticates by comparing the authentication context embedded in the REGISTER message with the authentication context received from the SUP-PE. If they match, the user is successfully authenticated. +- 10-14) If the UE is successfully authenticated, the S-CSC-PE assigns its own IP address to the SUP-PE using the SAR message, and a SIP 200 OK message is then sent to the UE. + +# Bibliography + +- [b-ITU-T Q.1001] Recommendation ITU-T Q.1001 (1988), *General aspects of public land mobile networks.* +- [b-ITU-T Q.1741.3] Recommendation ITU-T Q.1741.3 (2003), *IMT-2000 references to release 5 of GSM evolved UMTS core network.* +- [b-ITU-T Q.1761] Recommendation ITU-T Q.1761 (2004), *Principles and requirements for convergence of fixed and existing IMT-2000 systems.* +- [b-ITU-T Q.3221] Recommendation ITU-T Q.3221 (2008), *Requirements and protocol at the interface between the service control entity and the transport location management physical entity (S-TCI interface).* +- [b-IETF RFC 3554] IETF RFC 3554 (2003), *On the Use of Stream Control Transmission Protocol (SCTP) with IPSec.* +- [b-IETF RFC 4005] IETF RFC 4005 (2005), *Diameter Network Access Server Application.* +- [b-IETF RFC 5191] IETF RFC 5191 (2008), *Protocol for Carrying Authentication for Network Access (PANA).* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3303.1-201208-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3303.1-201208-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..561fcf0e9cb733e39857445593f7363edeeae92e --- /dev/null +++ b/marked/Q/T-REC-Q.3303.1-201208-I_PDF-E/raw.md @@ -0,0 +1,3588 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3303.1** + +(08/2012) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Resource control protocols + +--- + +**Resource control protocol No. 3 – Protocol at +the interface between a Policy Decision Physical +Entity (PD-PE) and a Policy Enforcement +Physical Entity (PE-PE): COPS alternative +version 2** + +Recommendation ITU-T Q.3303.1 + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|---------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3649 | +| NGN applications | Q.3700–Q.3849 | +| Testing for next generation networks | Q.3900–Q.3999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **Recommendation ITU-T Q.3303.1** + +## **Resource control protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE): COPS alternative version 2** + +# **Summary** + +Recommendation ITU-T Q.3301.1 specifies the resource control protocol No. 3 (rcp3) COPS profile at the Rw interface, i.e., between the policy decision physical entity (PD-PE) and the policy enforcement physical entity (PE-PE) in the resource and admission control function block. This protocol profile allows the final admission policy decisions to be installed (i.e., either push or pull mode) to a PE-PE from a PD-PE, supports resource control for both fixed and mobile networks and supports the network address port translation (NAPT) control and network address translation (NAT) traversal at PE-PEs as needed. It satisfies the requirements for information flows across the Rw reference point as specified in clause 9.2 of ITU-T Y.2111 and in Supplement 51 to the ITU-T Q-series. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|-------------------|------------|-------------| +| 1.0 | ITU-T Q.3303.1 | 2007-08-06 | 11 | +| 2.0 | ITU-T Q.3303.1 v2 | 2012-08-13 | 11 | + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Resource control procedures..... | 4 | +| 6.1 SCE-requested resource control procedures..... | 4 | +| 6.2 UE-requested resource control procedures..... | 9 | +| 7 Protocol profile specification..... | 11 | +| 7.1 Protocol support..... | 11 | +| 7.2 Modifications to COPS-PR ..... | 11 | +| 7.3 COPS basic message ..... | 13 | +| 8 Rw message description ..... | 14 | +| 8.1 Request (REQ PE-PE→PD-PE)..... | 14 | +| 8.2 Decision (DEC PD-PE→PE-PE) ..... | 14 | +| 8.3 Report state (RPT PE-PE→ PD-PE) ..... | 15 | +| 8.4 Delete request state (DRQ PE-PE→ PD-PE)..... | 16 | +| 9 COPS parameters reused ..... | 16 | +| 9.1 Client handle..... | 16 | +| 9.2 Flow ID..... | 16 | +| 9.3 Flow information ..... | 16 | +| 9.4 Traffic information ..... | 16 | +| 9.5 Connection information..... | 17 | +| 10 Application of PIB..... | 17 | +| 10.1 Role of PIB ..... | 17 | +| 10.2 Encoding of PIB ..... | 17 | +| 10.3 Definition of PIB ..... | 18 | +| 11 Security considerations..... | 18 | +| Annex A – Rw policy information base..... | 19 | +| Appendix I – Rw stage 2 message to COPS message mapping..... | 57 | +| Appendix II – Rw stage 2 message parameters to COPS Object-PIB-PRC-Attribute mapping ..... | 58 | +| Bibliography..... | 61 | + + + +## Recommendation ITU-T Q.3303.1 + +### Resource control protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE): COPS alternative version 2 + +# 1 Scope + +This Recommendation provides the stage 3 technical specifications for the common open policy service (COPS) profile at the interface between the policy decision physical entity (PD-PE) and the policy enforcement physical entity (PE-PE). The functional requirements and the stage 2 specifications for this interface are defined in clause 9.2 of [ITU-T Y.2111] and in [b-ITU-T Q.Sup51]. + +This protocol profile allows the final admission decisions to be installed (i.e., either push or pull mode) to a PE-PE from a PD-PE, supports the resource control for both fixed and mobile access networks, and supports the network address port translation (NAPT)/firewall control and network address translation (NAT) traversal at the PE-PE as needed. + +This Recommendation provides resource control procedure, protocol profile, modifications to COPS, messages and the definition and application of the policy information base (PIB). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Y.2111] ITU-T Y.2111 (2011), *Resource and admission control functions in next generation networks*. +- [ETSI TS 129 212] ETSI TS 129 212 V8.16.0 (2012), *Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control (PCC) over Gx/Sd reference point (3GPP TS 29.212 version 8.16.0 Release 8)*. +- [IETF RFC 2748] IETF RFC 2748 (2000), *The COPS (Common Open Policy Service) Protocol*. +- [IETF RFC 3084] IETF RFC 3084 (2001), *COPS Usage for Policy Provisioning (COPS-PR)*. +- [IETF RFC 3159] IETF RFC 3159 (2001), *Structure of Policy Provisioning Information (SPPI)*. +- [IETF RFC 3289] IETF RFC 3289 (2002), *Management Information Base for the Differentiated Services Architecture*. +- [IETF RFC 3318] IETF RFC 3318 (2003), *Framework Policy Information Base*. +- [IETF RFC 4001] IETF RFC 4001 (2005), *Textual Conventions for Internet Network Addresses*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 client handle** [IETF RFC 2748]: The client handle is used to identify a specific request state. + +**3.1.2 policy information base** [IETF RFC 3084]: The database of policy information. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 COPS connection:** The term "connection" is used in this Recommendation to refer to a COPS signalling relationship established between the PD-PE, acting in the role of a COPS Policy Decision Point (PDP), and the PE-PE, acting in the role of a COPS Policy Enforcement Point (PEP). + +**3.2.2 policy decision physical entity (PD-PE):** The PD-PE is an implemented instance of the Policy Decision Functional Entity (PD-FE) as defined in [ITU-T Y.2111]. + +**3.2.3 policy enforcement physical entity (PE-PE):** The PE-PE is an implemented instance of the Policy Enforcement Functional Entity (PE-FE) as defined in [ITU-T Y.2111]. + +**3.2.4 flow ID:** Identifier for the individual media flow within a session. + +NOTE – A flow ID is usually created by the PD-PE. + +**3.2.5 flow information:** Describes the features of the media flow (e.g., filter and filter status) as specified in clause 9.3. + +**3.2.6 traffic information:** Describes the features of the media flow (e.g., peak bandwidth, average bandwidth, and max package length) as specified in clause 9.4. + +**3.2.7 label stack:** Label stack is used to record the multiprotocol label switching (MPLS) network path for a bearer network employing MPLS technology. The information contained in the stack is the labels through a path; the last in first out (LIFO) algorithm is used. + +**3.2.8 connection information:** The core network ingress/egress path information at the PE-PE for a media flow (e.g., label stack or VLAN ID) as specified in clause 9.5. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|-------------------------------------| +| AVP | Attribute Value Pair | +| CAR | Committed Access Rate | +| COPS | Common Open Policy Service | +| COPS-PR | COPS usage for Policy Provisioning | +| CPE | Customer Premises Equipment | +| CPERR | Class Provisioning Error (of a PRC) | +| DEC | Decision message | +| Diffserv | Differentiated Services | +| DRQ | Delete Request state message | +| DSCP | Differentiated Services Code Point | + +| | | +|--------|----------------------------------------------| +| DS-TE | Differentiated Services-Traffic Engineering | +| EPD | Encoded Provisioning Instance Data | +| GPERR | Global Provisioning Error | +| GPRS | General Packet Radio Service | +| IP | Internet Protocol | +| LIFO | Last In First Out | +| LSP | Label Switched Path | +| MAC | Media Access Control | +| MPLS | Multiprotocol Label Switching | +| NACE | Network Attachment Control Entity | +| NAPT | Network Address Port Translation | +| NAT | Network Address Translation | +| PDP | Policy Decision Point | +| PD-PE | Policy Decision Physical Entity | +| PEP | Policy Enforcement Point | +| PE-PE | Policy Enforcement Physical Entity | +| PIB | Policy Information Base | +| PRC | Provisioning Class | +| PRI | Provisioning Instance (of a PRC) | +| PRID | Provisioning Instance Identifier | +| QinQ | 802.1Q in 802.1Q | +| QoS | Quality of Service | +| REQ | Request message | +| RPT | Report state message | +| RTCP | Real-Time Control Protocol | +| RTP | Real-Time Protocol | +| SCE | Service Control Entity | +| SPPI | Structure of Policy Provisioning Information | +| TRC-PE | Transport Resource Control Physical Entity | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| VLAN | Virtual Local Area Network | + +# 5 Conventions + +None. + +# **6 Resource control procedures** + +## **6.1 SCE-requested resource control procedures** + +### **6.1.1 Procedures at the PD-PE** + +#### **6.1.1.1 Session initiation** + +##### **6.1.1.1.1 Transport subscription profile verification** + +The policy decision physical entity (PD-PE) shall verify the transport subscription profile received from the network attachment control entity (NACE) using the globally unique IP address information or transport subscriber identifier as the index. + +The PD-PE shall derive the quality of service (QoS) class, reservation priority, and maximum uplink/downlink bandwidth based on the resource requestor identifier, resource request priority and media profile of the resource initiation request received from the service control entity (SCE). The PD-PE shall also verify the transport subscription profile to which the request applies for each IP media flow. In this verification process the derived parameters shall match the information obtained from the NACE. If the transport subscription profile does not contain any data, the PD-PE shall apply a default profile to the request. + +NOTE – The Ru interface is out of the scope of this Recommendation. + +##### **6.1.1.1.2 Transport resource detection and admission** + +The PD-PE shall request the transport resource control physical entity (TRC-PE) for transport resource availability detection and for an admission decision via the Rt interface. The PD-PE shall utilize the result of transport resource availability detection and the admission decision to make the policy decision. + +NOTE – The Rt interface is out of the scope of this Recommendation. + +##### **6.1.1.1.3 Initial policy decisions** + +The PD-PE shall make initial policy decisions for all IP media flows conveyed by the resource initiation request from the SCE based on all information described in clause 8.2.5.2 of [ITU-T Y.2111], including: + +- service information received from the SCE; +- transport subscription profiles; +- service based network policies; +- transport resource availability and admission decision information received from the TRC-PE. + +An initial request from the SCE can be accepted by the PD-PE if all conditions are met for all IP media flows in the session. If the request is accepted, the PD-PE shall send a resource initiation response back to the SCE and include a successful Resource Request Result code. Otherwise, the PD-PE may include the available resource information in the resource initiation response if the reason for authorization failure is due to insufficient resources. + +The PD-PE will process simultaneous requests from the SCE based on the priority level specified in the Resource Request Priority, which is also sent to the PE-PE. If the Resource Request Priority is not specified, the requested priority is set to the default value. + +The PD-PE will create a group of provisioning instances for each IP media flow in the session and request installation in the PE-PE by issuing a DEC message to the PE-PE. The details of the DEC message are described in clause 8.2. The PD-PE is notified that the decision has been carried out successfully, or has failed in the PE-PE. + +In addition, the policy decisions shall contain the following information: + +###### **IP media flow description** + +The PD-PE shall derive the uplink and downlink packet classifiers from the IP addresses and port numbers for uplink and downlink IP flows provided by the SCE. The PD-PE shall not modify the address and port information received from the SCE. + +###### **QoS information** + +The QoS information (consisting of maximum QoS class and bandwidth requirements) for IP media flows is extracted from the service information received from the SCE (e.g., from the media type, bandwidth information, service class and the SCE application ID). + +The PD-PE may select the QoS class that is the highest class applicable for the media. The PD-PE shall use the same QoS class for both the uplink and the downlink directions when both directions are used. The selection of network class is also dependent on network policies. + +The PD-PE shall authorize the contained bandwidth value in the resource initiation request received from the SCE according to network policies, transport subscription profile and resource availability. By default, the bandwidth value contains all overhead from the IP-layer and the upper layers (e.g., IP, UDP, RTP and RTP payload). + +###### **Resource control actions** + +Based on the flow status in the resource initiation request received from the SCE, the PD-PE shall decide what resource control actions to take: either Reservation only or ReservationandCommitment together. + +The Reservation only action requests the PE-PE to enforce the initial policy decisions (e.g., to reserve the authorized bandwidth) without forwarding the packets. It is used when the RwFlowInfoFilterStatus attribute of RwFlowInfoEntry is "closed." The ReservationandCommitment action requests the PE-PE to enforce the initial policy decisions (e.g., reserve the authorized bandwidth) and forward the packets. It is used when the RwFlowInfoFilterStatus attribute of RwFlowInfoEntry is "open." + +The RwFlowInfoEntry instance in the DEC message indicates the resource control action for each individual IP media flow or group of IP media flows if needed and applicable. + +###### **Path selection information** + +The PD-PE locates core networks that are involved to offer the requested QoS resources and the PE-PE instances that are involved to enforce the final admission decisions based on the information including service information received from the SCE, access information from the NACE, and service based network policies involved in the PD-PE. The path between ingress and egress points is selected by the TRC-PE. The PD-PE may send the path selection information for a media flow received from the TRC-PE to ingress and egress PE-PEs in a DEC message. + +Path selection information is based on the bearer network technology and will contain LSP information if MPLS is employed, otherwise it will contain the VLAN ID information. + +###### **NAT traversal and NAPT information** + +In order to request the address latching and address translation operations in the PE-PE, when hosted NAT traversal is detected by the SCE (e.g., the Latching-Indication AVP is set to LATCH (0) by the SCE), the PD-PE will include the type of NAT or latching indication (or both), together with the address information of each flow terminated in the access and core network to the PE-PE. + +###### Firewall working mode selection information + +Based on the service information provided by the SCE, the PD-PE shall facilitate appropriate dynamic firewall working mode selection. The PD-PE pushes the dynamic firewall working mode selection for a media flow to the PE-PE on the Rw interface. The following four packet inspection modes could be identified :static packet filtering, dynamic packet filtering, stateful inspection and deep packet inspection. The PE-PE shall inspect and drop packets based on security policy rules and gates which are received from the PD-PE. + +#### 6.1.1.2 Session modification + +Upon receipt of the resource modification request from the SCE with modified service information or local triggers due to network policies, configuration and conditions, the PD-PE shall perform the transport subscription verification and transport resource detection and admission, and update the policy decision as described in clauses 6.1.1.1.1 to 6.1.1.1.3 for all new or modified media components, based on the state information stored locally. + +The updated policy decision is sent to the PE-PE using a DEC message with an existing Client Handle, which contains the install decisions. + +Depending on the value of flow-status AVP received from the SCE, the PD-PE shall interpret the session modification as one of the following: + +- 1) modification of requested resources; +- 2) commitment of requested resources; +- 3) removal of requested resources. + +The modification of requested resources may request the addition of IP media flows or the modification of the attributes of existing IP media flows (e.g., bandwidth or the lifetime of a resource control session (or both) in case of soft-state reservation) without forwarding the packets (i.e., when the gate is closed). When an IP media flow is put on hold, the PD-PE shall retain all session state information and may send the request to the PE-PE to close the gate. The real-time control protocol (RTCP) gate shall be left open to keep the connection alive. The commitment of requested resources may request the allocation or activation of previously reserved resources, or of additional requested resources, or both, (e.g., new media components) and open the gates for all related IP media flows. The removal of requested resources may request the revocation of previously committed or reserved resources, or both, and close the gates for all related IP media flows. + +The corresponding resource control actions shall be included in the updated policy decision according to modification requests detailed above. + +#### 6.1.1.3 Session termination + +The session termination may be initiated by the PD-PE upon receipt of a termination request from the SCE or, when triggered by pre-defined static policies inside the PD-PE. + +Upon receipt of the resource release request from the SCE, the PD-PE shall release all relevant resources and provisioning instances and send a DEC remove message, with the Decision Flag set to push-state, to the PE-PE in order to revoke all requested resources and close the gates for all related IP media flows. + +When session termination is triggered by local policies and conditions, the PD-PE shall release all relevant resources and session states and send an Abort Resource request to the SCE. The PD-PE will also send a DEC remove message to the PE-PE, (as described in clause 7.2.2), if the request state was originally created by the PD-PE or when the request state was originally created by the PE-PE (as described in clause 3.2 of [IETF RFC 3084]). + +#### 6.1.1.4 Event notification + +The PD-PE may request notification of certain events (e.g., bearer failure) by specifying them in the RwEventIndicatorGroup in ITU-T Rw PIB, which includes event notifications such as: + +- 1) Charging correlation exchange; +- 2) Indication of loss of bearer; +- 3) Indication of recovery of bearer; +- 4) Indication of release of bearer; +- 5) deviceoverload; +- 6) devicerecoverfromoverload. + +Extra events can be added. + +### 6.1.2 Procedures at the PE-PE + +#### 6.1.2.1 Session initiation + +Upon receipt of a DEC message from the PD-PE, the PE-PE shall map them into its local QoS mechanisms, install the initial policing decision and inform the PD-PE if the policy data is installed (Report-Type = 'Success') or not (Report-Type = 'Failure'). + +When the RwFlowInfoFilterStatus attribute value is set to "close" in the DEC message, the PE-PE shall install the initial policy decisions without any commitment operations, and the gates shall be closed for the related IP media flow. When the RwFlowInfoFilterStatus attribute value is set to "open" in the initial DEC install message, the PE-PE shall commit the requested resources and open the gates for the related IP media flow using the packet filters defined in the RwFlowInfoFilter attribute. + +When the RwFlowBasedDecInfoNatAction attribute value is not set to zeroDotZero, the PE-PE shall populate the address translation information to RwFlowDescSingleFlowGroup and include them in the RPT message to the PD-PE. + +The PE-PE shall inspect and drop packets based on security policy rules and gates which are indicated in the RwSingleFlowInfoFirewallmodeIndication attribute received from the PD-PE. + +#### 6.1.2.2 Session modification + +Upon receipt of a DEC message with an existing client handle received from the PD-PE, and when the command-code is set to "install" in the Decision Flags, the PE-PE will reinstall the policy decision. When the command-code is set to "install" in the Decision Flags and the PRID in the named decision data object is an existing one, the PE-PE will reinstall and update the policy decision. + +The PE-PE may perform the following operations: + +- Install policy decision for a new IP media flow without committing the requested resources if the RwFlowInfoFilterStatus attribute is set to "close". +- Install policy decision and commit the requested resources for a new IP media flow if the RwFlowInfoFilterStatus attribute is set to "open". +- Modify policy decision for an existing IP media flow without committing the requested resources if the RwFlowInfoFilterStatus attribute is set to "close" (e.g., increase or decrease the allocated bandwidth, but the RTCP gate may remain in the open status). +- Modify policy decision and commit the requested resources for an existing IP media flow if the RwFlowInfoFilterStatus attribute is set to "open" (e.g., open the gates with modified bandwidth). + +- Commit the requested resources for an existing IP media flow if the *RwFlowInfoFilterStatus* attribute is set to "close" (e.g., open the gates with reserved bandwidth). +- Revoke the installed policy decisions and release the committed or reserved resources for all related IP media flows which are not included in *RwFlowbasedDecInfoGroup*. + +The PE-PE may also disable the commitment of requested resources by closing the gate but retaining the session state information and transport resources if the *RwFlowInfoFilterStatus* attribute is set to "close" for a prior enabled IP media flow. + +#### 6.1.2.3 Session termination + +If the session termination is initiated by the PD-PE, upon receipt of resource release request from the SCE, the PE-PE shall disable the relevant gates and release the network resources. + +#### 6.1.2.4 Event notification + +The PE-PE may send a notification to the PD-PE if the event specified by the *RwEventIndicatorGroup* occurs. + +The event notification is sent to the PD-PE through an RPT message. + +#### 6.1.2.5 Policy enforcement operations + +##### QoS mapping + +When QoS information (e.g., QoS Class, peak bandwidth of UL and DL) is received from the PD-PE, the PE-PE shall perform the mapping between the network QoS and the transport QoS by the translation/mapping function, which maps the generic QoS class into the transport QoS class for a specific network technology (e.g., translation into UMTS QoS class for GPRS access networks, or translation into DiffServ code point for DS-TE enabled MPLS). The mapping rules are subject to relevant standards and network operator's local policy (e.g., the table for UMTS QoS mapping). Typically, the mapping rules can be preconfigured in the PE-PE and may be updated via the policy provisioning system or via the *Rw* interface as needed. + +The PE-PE shall select a transport bearer to carry the requested traffic based on the matching transport QoS class. + +In addition, the PE-PE shall select an existing transport bearer to allocate the resource for corresponding IP media flows or make a decision to create a new transport bearer for the corresponding IP media flows based on the matching QoS class. + +##### Gate operation + +The policy decision to open or close the gate shall lead to the enabling or disabling of the passage of corresponding IP packets. When the gate is closed all packets of the related IP flows shall be dropped. When the gate is opened the packets of the related IP flows are allowed to pass through. The *RwFlowInfoFilterStatus* attribute in the DEC message indicates the resource control action for each individual IP media flow or group of IP media flows if needed and applicable. + +Upon receipt of the DEC message, from the PD-PE, for the initiation or modification of a policy decision, the PE-PE shall perform the gate operation for each IP media flow as follows: + +- Open the gate for IP flows specified in *RwFlowInfoFilter* if the *RwFlowInfoFilterStatus* attribute is set to "open". +- Close the gate if the *RwFlowInfoFilterStatus* attribute is set to "close", but the RTCP gate may be kept open. +- Close all relevant gates including the RTCP gate if the command-code in the decision flags is set to "remove". + +##### **User plane operation** + +The PE-PE shall enforce the policy decision of resource control-based "gating" functionality according to additional information received from the PD-PE. + +When the policy decision is installed and activated, the PE-PE shall evaluate the packets against IP media flow filters provided by the PD-PE or predefined in static policy rules for all transport bearers in order of precedence of the policy decisions or the predefined static policy rules. + +When a packet matches an IP media flow filter, the policy decisions for that filter shall be applied, as follows: + +- Bandwidth allocation/policing information provided by the *RwFlowDirDescFluxInfo* attribute; +- Packet marking/remarking information provided by the *RwFlowDirDescInfo* attribute; +- NAPT translation and address latching/translation information provided by the *RwSingleFlowInfoFlowTermination*, *RwSingleFlowInfoAddressRealm*, *RwSingleFlowInfoLatchingIndication* attributes; +- Firewall working mode information provided by the *RwSingleFlowInfoFirewallmodeIndication* attribute. + +The IP packets shall be transported within the specific transport bearer (e.g., a VLAN or LSP) where the selected policy decision is mapped. + +The IP packets that do not match any IP media flow filters provided by the policy decisions shall be silently discarded. + +## **6.2 UE-requested resource control procedures** + +### **6.2.1 Procedures at the PD-PE** + +#### **6.2.1.1 Initial reservation** + +When the UE requests a transport resource via the transport signalling message, the pull mode shall be employed in support of resource control procedures. + +Upon receipt of a Request from the PE-PE with a new client Handle, the PD-PE shall send a resource action request to the SCE to retrieve the service information of the flow if the SCE previously requested the QoS initial authorization related to that flow. + +The PD-PE shall perform the binding operation to establish the association between the Request and the pre-authorized resource control session or pre-configured policy based on the binding information provided by the request. Detailed bearer binding mechanisms are described in clause 6.2.1.5. + +If the request is authorized, the PD-PE should perform the relevant operations described in clauses 6.1.1.1.1 and 6.1.1.1.2. Only when all conditions are satisfied will the PD-PE create a group of provisioning instances for each IP media flow or each user requested by the PE-PE. The PD-PE will then send a DEC message with the initial policy decisions and the same client handle specified in the REQ message to the PE-PE. + +The PD-PE is notified that the decision has been carried out successfully, or has failed in the PE-PE. + +#### **6.2.1.2 Session modification** + +Upon receipt of the Request with an existing client Handle, the PD-PE shall perform the same reservation procedure as described in clause 6.2.1.1, including resource action request to the SCE if necessary, the binding operation, transport subscription profile verification, and transport resource detection and admission. As a response, the PD-PE shall send a DEC message to the PE-PE with + +the policy decision for new or modified IP media flows including IP media flow descriptions, QoS information, path selection information and NAT traversal/NAPT information. + +Additionally, the PD-PE shall be able to push down updated policy decisions triggered by the SCE or local policies without explicit request of the PE-PE in the pull mode. The relevant procedures are the same as session modification of push mode described in clause 6.1.1.2. + +Depending on the value of the flow status received from the SCE or the RwFlowInfoEntry instance received from the PE-PE through the AA-Request or Request, the PD-PE shall interpret the session modification as one of the following: + +- 1) modification of requested resources; +- 2) commitment of requested resources; +- 3) removal of requested resources. + +The detailed procedures are described in clause 6.1.1.2. For certain access networks, such as GPRS, alternative approaches may be used such as those described in [ETSI TS 129 212]. + +#### **6.2.1.3 Session termination** + +Upon receipt of a DRQ message from the PE-PE, the PD-PE shall release all relevant resources and session state and notify the SCE of the session termination. + +#### **6.2.1.4 Event notification** + +The detailed procedures are described in clause 6.1.1.4. + +#### **6.2.1.5 Binding operations** + +Upon receipt of a Request, the PD-PE shall perform the binding operation to identify the pre-authorized resource control session along with policy decisions. The PD-PE may compare the flow identifier conveyed by the request from the PE-PE with the pre-authorized flow filter information stored in the PD-PE. If more than one flow identifier is included, the PD-PE shall also verify that the media components identified by the flow identifiers are allowed to be transferred in the same UE transport session. The PD-PE may also utilize information such as the user identification, globally unique IP address, etc., to acquire corresponding policy. + +The flow identifier can be provided by the RwFlowInfoFilter instance of Request, which includes the source/destination IP addresses and port numbers. + +The pre-authorized flow filter in the PD-PE is obtained from the media profile of the resource initiation request received from the SCE during the initial authorization. + +### **6.2.2 Procedures at the PE-PE** + +#### **6.2.2.1 Session initiation** + +Upon receipt of an initial transport signalling message from the UE for establishing a new UE transport session, the PE-PE shall send a REQ message with a new client handle. + +The PE-PE shall provide flow identifiers to allow the PD-PE to identify the policy decisions to be applied. In addition, the PD-PE may provide other information such as user identification and the physical or logical (or both) connection of the access transport network to which the CPE is attached. + +#### **6.2.2.2 Session modification** + +Upon receipt of a transport signalling message from the UE to modify an existing UE transport session, the PE-PE shall send a REQ message to the PD-PE with an existing client handle. + +#### **6.2.2.3 Session termination** + +When the request state is no longer needed, (e.g., when an interface goes down or when the last transport bearer or IP media flow within an UE transport session is being terminated), the PE-PE shall send a DRQ message with a proper reason object to inform the PD-PE that the request state specified by the client handle is to be deleted. + +#### **6.2.2.4 Event notification** + +The detailed procedures are described in clause 6.1.2.4. + +#### **6.2.2.5 Policy enforcement operations** + +The detailed procedures are described in clause 6.1.2.5. + +In addition, the PE-PE may make local decisions based on stored policy decision information of an active UE transport session, when the UE requests a UE transport session modification via the transport signalling message. + +#### **6.2.2.6 Binding operations** + +The binding operations are performed by the PE-PE to identify the correct PD-PE and subsequently to allow policy decision information to be requested from the PD-PE. + +The PE-PE shall determine the IP address of the corresponding PD-PE from information in the transport signalling message received from the UE. This information may include flow identifier or other information such as the user identification, globally unique IP address, etc. + +# **7 Protocol profile specification** + +## **7.1 Protocol support** + +The Rw interface shall conform to the IETF COPS framework as a requirement and guideline for stage 3 specifications, and shall also conform to the COPS-PR procedures and data models defined in [IETF RFC 3084]. + +This Recommendation makes use of a modified version of the COPS protocol specified in [IETF RFC 2748] and [IETF RFC 3084]. The modification is described below. Unless explicitly indicated, the procedures and data models defined in [IETF RFC 3084] remain unmodified. The COPS protocol supports a client/server interface between the PD-PE and the PE-PE. The PE-PE serves as a PEP and a client, and the PD-PE serves as a PDP and a server. + +COPS implementations supporting this Recommendation shall support the COPS client type 0x800c (ITU-T Rw PIB) and shall support the PIB defined in Annex A. + +## **7.2 Modifications to COPS-PR** + +In order to implement push mode operation more efficiently for the ITU-T Rw PIB client type, this Recommendation provides a means whereby the PD-PE can create a new state and can also associate that state with a new client handle value, both within the same message. The PD-PE can also delete state and corresponding client handle values via a COPS DEC message. + +A mechanism to assign the client handle in the PD-PE and the PE-PE is required to avoid collisions. + +These modifications are implemented by means of new decision flag values in the COPS DEC message, as follows: + +- The flag value 0x03 is referred to as the "request-prefix" flag. +- The flag value 0x04 is referred to as the "push-state" flag. + +### 7.2.1 Creating new state in push mode + +In push mode, the DEC install message is used by the PD-PE to create a request state. + +The PD-PE sends a DEC install message with the decision flag set to push-state and the client handle set to "remote" to the PE-PE. When the PE-PE receives the DEC message, it associates a request state with the client handle value in the DEC message as if it had explicitly sent an REQ message using that client handle value, although it had never sent that REQ message at all. The client handle in the DEC install message shall use a new value in the PD-PE. It may reuse a value which was active in the past, but has been explicitly removed. However, this usage is not recommended. An aging period, in the order of minutes, is recommended before reuse of a deactivated client handle value. + +The DEC message containing the push-state flag may contain a named decision data object defining state to be associated with the given client handle value. The result of sending such a DEC message is equivalent to the result of sending a DEC message with request state set, receiving a REQ message with a new client handle value, and sending another DEC message to install the named decision data. The message sequence for creation of a new state in push mode is shown in Figure 7-1. + +![Sequence diagram for creating a new state in push mode between PD-PE and PE-PE.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` +sequenceDiagram + participant PD-PE + participant PE-PE + Note right of PD-PE: DEC(Install, push-state, client Handle = new value) + PD-PE->>PE-PE: DEC(Install, push-state, client Handle = new value) + Note right of PD-PE: Named decision data + PD-PE->>PE-PE: Named decision data + Note right of PE-PE: RPT(Client Handle = new value) + PE-PE->>PD-PE: RPT(Client Handle = new value) + Note right of PE-PE: Q.3303.1 v2(12)_F7-1 +``` + +The diagram illustrates the message sequence for creating a new state in push mode. It features two vertical lifelines: PD-PE on the left and PE-PE on the right. The sequence begins with a message from PD-PE to PE-PE labeled "DEC(Install, push-state, client Handle = new value)". A second message, "Named decision data", is sent from PD-PE to PE-PE. In response, PE-PE sends a message back to PD-PE labeled "RPT(Client Handle = new value)". The diagram is identified by the text "Q.3303.1 v2(12)\_F7-1" at the bottom right. + +Sequence diagram for creating a new state in push mode between PD-PE and PE-PE. + +**Figure 7-1 – Message sequences for creation of new state in push mode** + +### 7.2.2 Delete state in push mode + +In push mode, the DEC remove message is used by the PD-PE to delete a request state. + +A DEC remove message with the decision flag set to push-state and a client handle value which is originally created by the PD-PE, commands the PE-PE to delete the state as identified by the client handle value. The PE-PE deletes the associated state and sends a RPT message to the PD-PE with the result of the operation. Upon receipt a DEC remove message with the decision flag set to push-state and a client handle value which is new or was originally created by itself, the PE-PE should report an error. + +The message sequence for deletion of a state in push mode is shown in Figure 7-2. + +![Sequence diagram for deleting a state in push mode between PD-PE and PE-PE.](124c6108c63173818afb8ed49521e22d_img.jpg) + +``` +sequenceDiagram + participant PD-PE + participant PE-PE + Note right of PD-PE: DEC(Remove, push-state, CH = X, which is created by PD-PE) + PD-PE->>PE-PE: DEC(Remove, push-state, CH = X, which is created by PD-PE) + Note right of PE-PE: RPT(CH = X) + PE-PE->>PD-PE: RPT(CH = X) + Note right of PE-PE: Q.3303.1 v2(12)_F7-2 +``` + +The diagram illustrates the message sequence for deleting a state in push mode. It features two vertical lifelines: PD-PE on the left and PE-PE on the right. The sequence begins with a message from PD-PE to PE-PE labeled "DEC(Remove, push-state, CH = X, which is created by PD-PE)". In response, PE-PE sends a message back to PD-PE labeled "RPT(CH = X)". The diagram is identified by the text "Q.3303.1 v2(12)\_F7-2" at the bottom right. + +Sequence diagram for deleting a state in push mode between PD-PE and PE-PE. + +**Figure 7-2 – Message sequences for delete state in push mode** + +### 7.2.3 Client handle collision solution + +To avoid possible collisions between the client handle values allocated, by the PE-PE in pull mode and the PD-PE in push mode, it is recommended that all the client handle values allocated by the PD-PE be a sequence of complete client handle values containing a prefix. The prefix can be pre-configured by network operators or allocated dynamically by the PE-PE through message exchanges. + +When using pre-configuration, the network operator may pre-configure the identifiers such as IP address, hostname, or domain name of the PD-PE and PE-PE, as the prefix of their allocated client handle values. + +When using dynamic allocation, the PD-PE can request a prefix from the PE-PE. A DEC install message, with the request-prefix flag set in the COPS Decision Flags object, will cause the PE-PE to issue a new REQ message with a new client handle, in the same way it responds to a request-state flag (see clause 3.2 in [IETF RFC 3084]). However, the client handle is actually a prefix, which the PD-PE may use to generate a sequence of complete client handle values that are guaranteed to be unique to the PE-PE. + +![Sequence diagram showing messages exchanged between PD-PE and PE-PE to create and delete a client handle prefix.](10781f43062bf3e9601a1e086710556c_img.jpg) + +``` +sequenceDiagram + participant PD-PE + participant PE-PE + Note left of PD-PE: DEC(Client Handle = old value, flag = request-prefix) + PD-PE->>PE-PE: DEC(Client Handle = old value, flag = request-prefix) + PE-PE-->>PD-PE: RPT(Client Handle = old value) + PE-PE-->>PD-PE: REQ(Client Handle = prefix) + Note right of PD-PE: Other operations creating Client Handle values using prefix (see clause 7.2.1) + PD-PE->>PE-PE: Other operations creating Client Handle values using prefix + PE-PE-->>PD-PE: Other operations creating Client Handle values using prefix +``` + +The diagram illustrates the message exchange between a PD-PE and a PE-PE. The sequence starts with the PD-PE sending a DEC message to the PE-PE with the parameters 'Client Handle = old value' and 'flag = request-prefix'. The PE-PE responds with an RPT message containing 'Client Handle = old value'. Next, the PE-PE sends a REQ message with 'Client Handle = prefix'. Below these, a section labeled 'Other operations creating Client Handle values using prefix (see clause 7.2.1)' shows bidirectional message exchanges between the two entities. The diagram is labeled 'Q.3303.1 v2(12)\_F7-3' at the bottom right. + +Sequence diagram showing messages exchanged between PD-PE and PE-PE to create and delete a client handle prefix. + +**Figure 7-3 – Messages exchanged to create and delete a client handle prefix** + +The complete sequence of messages exchanged during the life cycle of a sequence is shown in Figure 7-3. The initial DEC message requesting the prefix uses a client handle value created by an earlier REQ message (e.g., during session start-up). As always in COPS, the PE-PE first returns a RPT message in response to the DEC message, using the earlier client handle value. The PE-PE then sends an REQ message with the desired prefix value. The PD-PE creates a new state associated with the client handle value equal to the prefix value concatenated with some sequence of octets xyz, in the manner described in clause 7.2.1. + +## 7.3 COPS basic message + +All message formats specified in [IETF RFC 3084] are to be applied at the Rw interface. The client open, client accept, client close, keep alive, synchronize state request and synchronize state complete messages are used for setting up the connection, maintaining the connection, and synchronization of the request state between the PD-PE and the PE-PE. + +The request (REQ), delete request state (DRQ), decision install (DEC install) and decision remove (DEC remove), and the RPT messages, supported by the COPS layer for Rw interface, are used for policy control operations. + +# 8 Rw message description + +## 8.1 Request (REQ PE-PE→PD-PE) + +The REQ message is sent by the PE-PE to the PD-PE to request a configuration decision. + +During state synchronization, the REQ message is generated and sent by the PE-PE to the PD-PE after receiving a synchronize state request (SSQ) message from the PD-PE. See clause 3.1 of [IETF RFC 3084]. + +The PE-PE may send information such as the physical or logical connection (or both) of the access transport network to which the CPE is attached (e.g., IP and MAC address of the CPE, User Id, and other physical information) in order to assist the PD-PE in deciding what types of policy the PE-PE shall install and enforce. The information is described in the RwReqInfoGroup in ITU-T Rw PIB and is carried in the named clientSI object of the REQ message. + +## 8.2 Decision (DEC PD-PE→PE-PE) + +The PD-PE pushes the final admission decisions to the PE-PE and requests NAT information or query event notification from the PE-PE using the install operation. + +This information is carried in the named decision data object and is described by the following PRCs: + +### Flow-based policy: + +The RwFlowbasedDecInfoGroup together with RwNatActionGroup, RwAppChrgInfoGroup, RwEventIndicatorGroup and RwFlowDescGroup are used for this purpose and include the following information: + +- Resource request priority: described by the RwFlowBasedDecInfoRequestPriority attribute. +- Type of NAT: described by the RwFlowBasedDecInfoNatAction attribute. +- Charging ID of application layer: described by the RwFlowBasedDecAppChrgIds attribute. +- Event notification indication: described by the RwFlowBasedDecInfoEventIndicator attribute. +- Description of groups of the media flow within a session: described by the RwFlowBasedDecInfoFlowDesc attribute. + +The individual media flow is described by RwFlowDescGroup together with RwFlowFirewallModeIndicationGroup, RwSingleFlowInfoGroup, RwFlowDirDescGroup, RwFlowInfoGroup, RwFilterGroup, RwFluxInfoGroup, RwVSWITCHFluxInfoGroup, RwMPLSConnectInfoGroup, RwMPLSLabelGroup, RwVSWITCHConnectInfoGroup, RwFlowTerminationGroup, RwFlowAddressRealmGroup and RwFlowLatchingIndicationGroup, including the following information: + +- Flow ID: described by the RwSingleFlowInfoFlowId attribute. +- Dynamic firewall working mode: described by the RwSingleFlowInfoFirewallmodeIndication attribute. +- Flow information such as flow direction, the standard 5-tuple, gate status and service type: described by the RwFlowInfoGroup. +- Bandwidth and traffic descriptor (uplink and/or downlink): described by the RwFlowDirDescFluxInfo attribute. +- Path selection information (such as LSP or VLANId): described by the RwFlowDescConnectInfo attribute. + +The PE-PE can create and store the bindings of media flow and path selection information in order to route media flows. + +When the PD-PE requests the PE-PE to implement NAT for the groups of media flow, the control information may include: + +- Termination indicator: indicating which side a media flow is terminated (access or core network) for the PE-PE, and is described by the `RwSingleFlowInfoFlowTermination` attribute. +- Address realm: described by the `RwSingleFlowInfoAddressRealm` attribute. +- Latching Indication: described by the `RwSingleFlowInfoLatchingIndication` attribute. + +### **User-based policy:** + +The `RwUserBasedDecInfoGroup` together with the `RwNetworkClassGroup` and the `RwDirFluxGroup` are used for this purpose and includes the following information: + +- User identifier: described by the `RwUserBasedDecInfoUserId` attribute; +- Network class of service: described by the `RwUserBasedDecInfoNetworkClass` attribute; +- Bandwidth and traffic descriptor (uplink and/or downlink): described by the `RwDirFluxGroup`. + +In push mode, the `RwDecCapGroup` is used for providing the following PD-PE capabilities and limitations in the configuration DEC message: + +- Indication of the maximum number of flow identifiers: +The PD-PE may notify the PE-PE how many flow identifiers the PD-PE is able to send with an install DEC message. +- Indication of the maximum number of application charging identifiers: +The PD-PE may notify the PE-PE how many applications charging IDs the PD-PE is able to send with a DEC install message. + +The PD-PE can also request the PE-PE to delete an existing request state in the manner described in clause 7.3 when the request state is originally created by PD-PE, or in the manner described in clause 3.2 of [IETF RFC3084] when the request state is originally created by the PE-PE. + +## **8.3 Report state (RPT PE-PE→ PD-PE)** + +The RPT message is used to report processing results or resource status from the PE-PE to the PD-PE. After the PE-PE finishes processing service messages, the result will be reported to the PD-PE. There are two scenarios related to the sending of an RPT message: The first is a response to any kind of DEC message (such as install and remove); the second is an unsolicited report to the PD-PE when the PE-PE detects an event which requires notification to the PD-PE. A flag in the RPT message header will be set to 1 and 0, respectively. + +The information is carried in the named `clientSI` object and is described by the following PRCs: + +### **NAT response:** + +The `RwStateReportGroup` together with `RwFlowDescGroup`, `RwSingleFlowInfoGroup`, `RwFlowTerminationGroup`, `RwFlowAddressRealmGroup`, `RwFlowDirDescGroup`, `RwFlowInfoGroup` and `RwFilterGroup` is used for NAT response. + +Named `clientSI` object will contain one or more `GPERR` object, `ErrorPRID` object, `CPERR` object, `PRID` and `EPD` object. + +### **Bearer charging ID:** + +The `RwStateReportGroup` together with `RwRprtBearChrgInfoGroup` are used to provide bearer charging information. + +### **Event notification:** + +The RwStateReportGroup together with RwEventIndicatorGroup are used to provide event notification to the PD-PE. + +This Recommendation requires that the standard COPS-PR error handling mechanism and error objects, such as GPERR object, ErrorPRID object and CPERR object be applied. + +## **8.4 Delete request state (DRQ PE-PE→ PD-PE)** + +The PE-PE informs the PD-PE via a DRQ message that the state identified by the client handle is no longer available and shall be removed by the PD-PE. + +The DRQ message includes the reason why the request state was deleted. + +# **9 COPS parameters reused** + +## **9.1 Client handle** + +When a new request state is created (user requests online or the PD-PE installs a configuration for a user in push mode), either the PE-PE or the PD-PE allocates a new client handle value for that request state and ensures its uniqueness in a COPS connection. It is carried in a client handle object, uniquely identifying one request state and then used by subsequent REQ, DEC, and RPT messages to reference the same user's request state. In subsequent service handling, users exchange information with the same client handle value. When the user service is finished, the user will delete the client handle. + +During the synchronization process no new client handles are allocated, however existing client handles are used. + +## **9.2 Flow ID** + +Flow ID is used to identify the media flow within a session. Each session may contain multiple media flows, and each media flow is identified by a unique flow ID. Usually flow IDs are created by the PD-PEs. + +## **9.3 Flow information** + +Flow information is included in DEC install messages and includes the following information: + +- Direction +- Filter + - Address type + - IP addresses + - Ports + - Protocol number + - DSCP +- Filter status +- Service type. + +## **9.4 Traffic information** + +Traffic information is included in DEC install messages. The characteristics of the traffic information include the following and shall also address the uplink traffic information and the downlink traffic information: + +- Bandwidth unit + +- Peak bandwidth +- Average bandwidth +- Max package length. + +The following traffic information may also be provided when the bearer network employs Non-MPLS technology: + +- Direction +- Base traffic information +- Flow priority +- CAR flag +- Broadcast bate flag +- Path backup flag. + +## **9.5 Connection information** + +The connection information is included in the installation information. Since the network employs different technologies, it may have different descriptions depending on the technology employed. + +### **9.5.1 Bearer network employing MPLS technology** + +MPLS based networks include the following installation information: + +- Maximum transport unit in the path +- Label stack (Maximum with 16 labels). + +### **9.5.2 Bearer network employing Non-MPLS technology** + +Non-MPLS based networks that use the Diffserv model of QoS, such as LAN and IP, include the following installation information: + +- Source interface address information +- Source VlanID +- Source VlanID QinQ +- Destination interface address information +- Destination VlanID +- Destination VlanID QinQ. + +# **10 Application of PIB** + +## **10.1 Role of PIB** + +PIB provides a solution to interworking between different production vendors. PIB defines a collection of PRCs that can be accessed by COPS and provides the data instances (PRIs) for any given data structure (PRC). Instances of the provisioning classes are each identified by a PRID in the PIB. Thus, the PIB is similar to a virtual database of the PRC. + +A PIB is defined and it inherits part of its data definitions from other PIBs, including the PIBs defined in [IETF RFC 3159], [IETF RFC 4001] and [IETF RFC 3318]. + +## **10.2 Encoding of PIB** + +Adopt ASN.1 BER to encode the PRID and policy data as described in clause 2.2.1 in [IETF RFC 3084]. + +## **10.3 Definition of PIB** + +PIB is based on the IP network of QoS guaranteed. See Annex A for detailed information. + +# **11 Security considerations** + +The security mechanisms described in COPS [IETF RFC 2748] and COPS-PR [IETF RFC 3084] should be reused in this Recommendation. + +# Annex A + +## Rw policy information base + +(This annex forms an integral part of this Recommendation.) + +``` +ITUT-RwPib PIB-DEFINITIONS ::= BEGIN +IMPORTS + Unsigned32, + Integer32, + MODULE-IDENTITY, + MODULE-COMPLIANCE, + OBJECT-TYPE, + OBJECT-GROUP +FROM COPS-PR-SPPI -- Defined in RFC 3159 + + InstanceId, + Prid +FROM COPS-PR-SPPI-TC -- Defined in RFC 3159 + + DscpOrAny +FROM DIFFSERV-DSCP-TC -- Defined in RFC 3289 + + zeroDotZero +FROM SNMPv2-SMI + + InetAddress, + InetAddressType, + InetAddressPrefixLength, + InetPortNumber +FROM INET-ADDRESS-MIB; -- Defined in RFC 4001 + +iTUT-RwPib MODULE-IDENTITY + SUBJECT-CATEGORIES { Rw(0x800c) } -- ITU-T Rw COPS Client Type + LAST-UPDATED "2012061300000Z" + ORGANIZATION "ITU-T Study Group 11" + CONTACT-INFO "huanghexian@ ritt.cn" + DESCRIPTION + "A PIB module containing the set of provisioning + classes that are required for support of policies for + RW Cops interface" + REVISION "2005111000000Z" + DESCRIPTION + "The ITU-T RW PIB for Rec. Q.3303.1 version 2" +::= { 0.0.17.3303.127.1.2.1 } +-- itu-t(0) recommendation(0) q(17) q3303(3303) hyphen(127) <...>(1) ??pib(2) +version2 (1). + +-- +-- The root OID for PRCs in the ITU-T Rw PIB +-- + +rwCapabilityClasses OBJECT IDENTIFIER ::= { iTUT-RwPib 1} +rwEventInfoClasses OBJECT IDENTIFIER ::= { iTUT-RwPib 2} +rwServiceInfoClasses OBJECT IDENTIFIER ::= { iTUT-RwPib 3} +rwReqInfoClasses OBJECT IDENTIFIER ::= { iTUT-RwPib 4} +rwDecInfoClasses OBJECT IDENTIFIER ::= { iTUT-RwPib 5} +rwReportClasses OBJECT IDENTIFIER ::= { iTUT-RwPib 6} +rwConformance OBJECT IDENTIFIER ::= { iTUT-RwPib 7} + +----- +-- Capability and Limitation Policy Rule Classes +``` + +``` + +-- Rw Decision Capability Table +-- +rwDecCapTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwDecCapEntry + PIB-ACCESS notify + STATUS current + DESCRIPTION + "PRC from PD-PE to PE-PE carried by DEC during initial capability +negotiation, indicating the PD-PE's capability." + ::= { rwCapabilityClasses 1 } + +rwDecCapEntry OBJECT-TYPE + SYNTAX RwDecCapEntry + STATUS current + DESCRIPTION + "An instance of the RwDecCap class identifies a specific PRC and +associated attributes as supported by the device." + PIB-INDEX { RwDecCapPrId } + UNIQUENESS { } + ::= { rwDecCapTable 1 } + +RwDecCapEntry ::= SEQUENCE { + rwDecCapPrId InstanceId, + rwDecCapAppChrgIds Unsigned32, + rwDecCapFlowIds Unsigned32 +} + +rwDecCapPrId OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an +instance of the RwDecCap class." + ::= { rwDecCapEntry 1 } + +rwDecCapAppChrgIds OBJECT-TYPE + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + "Indication of the maximum number of Application Charging Id possible +in a single Dec message. + The value of zero indicates limit is not specified." + DEFVAL { 0 } + ::= { rwDecCapEntry 2 } + +rwDecCapFlowIds OBJECT-TYPE + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + "Indication of the maximum number of Flow Id possible in a single Dec +message. + The value of zero indicates limit is not specified." + DEFVAL { 0 } + ::= { rwDecCapEntry 3 } + +----- + +-- Rw Decision Capability Acknowledge Table +-- +rwDecCapACKTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwDecCapACKEntry + PIB-ACCESS install + STATUS current + +``` + +``` + +DESCRIPTION + "PRC from PD-PE to PE-PE carried by COPS-PR RPT messages indicating +the result of the capability negotiation." +::= { rwCapabilityClasses 2 } + +rwDecCapACKEntry OBJECT-TYPE + SYNTAX RwDecCapACKEntry + STATUS current + DESCRIPTION + "An instance of the RwDecCapACK class sent by the PE-PE to the PD-PE." + PIB-INDEX { RwDecCapACKPrid } + UNIQUENESS { } +::= { rwDecCapACKTable 1 } + +RwDecCapACKEntry ::= SEQUENCE { + rwDecCapACKPrid InstanceId, + rwDecCapACKEnable INTEGER, + rwDecCapACKChrgIds Unsigned32, + rwDecCapACKFlowIds Unsigned32 +} + +rwDecCapACKPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +this class." +::= { rwDecCapACKEntry 1 } + +rwDecCapACKEnable OBJECT-TYPE + SYNTAX INTEGER { + enable(1), + disable(2) + } + STATUS current + DESCRIPTION + "Controls the usage of PD-PE capability negotiation." + DEFVAL { enable } +::= { rwDecCapACKEntry 2 } + +rwDecCapACKChrgIds OBJECT-TYPE + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + "Indication of the maximum number of Application Charging Id in a DEC +message which is acceptable to PE-PE. + The value of zero indicates limit is not specified." + DEFVAL { 0 } +::= { rwDecCapACKEntry 3 } + +rwDecCapACKFlowIds OBJECT-TYPE + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + "Indication of the maximum number of Flow Id in a DEC message which is +acceptable to PE-PE. + The value of zero indicates limit is not specified." + DEFVAL { 0 } +::= { rwDecCapACKEntry 4 } + +----- +-- +--Rw Event Info Classes + +``` + +``` + +-- +--Rw Event Notification Indication Table + +rwEventIndicatorTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwEventIndicatorEntry + PIB-ACCESS install-notify + STATUS current + DESCRIPTION + "PRC representing event notification indicator. In COPS-PR install + decision object and sent by PD-PE to PE-PE indicate the PD-PE requests the PE-PE + to provide a notification at the transport event. In PRT message and sent by + PE-PE to PD-PE indicate the PE-PE report the transport event to PD-PE." + ::= { rwEventInfoClasses 1 } + +rwEventIndicatorEntry OBJECT-TYPE + SYNTAX RwEventIndicatorEntry + STATUS current + DESCRIPTION + "An entry in the Event Indicator Table describing a transport event. + Each entry is referenced by RwDecInfoEventIndicator." + PIB-INDEX { RwEventIndicatorPrid } + UNIQUENESS { } + ::= { rwEventIndicatorTable 1 } + +RwEventIndicatorEntry ::= SEQUENCE { + rwEventIndicatorPridInstanceId, + rwEventIndicator Integer32, + rwEventIndicatorNextPrid +} + +rwEventIndicatorPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwEventIndicator class." + ::= { rwEventIndicatorEntry 1 } + +rwEventIndicator OBJECT-TYPE + SYNTAX Integer32{ + chargingCorrelationExchange (1), + indicationOfLossOfBearer (2), + indicationOfRecoveryOfBearer (3), + indicationOfReleaseOfBearer (4), + deviceoverload (5), + devicerecoverfromoverload (6) + } + STATUS current + DESCRIPTION + "an integer indicating the query and notification of a transport + event." + ::= { rwEventIndicatorEntry 2 } + +rwEventIndicatorNext OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "References the next of a list of RwEventIndicator instances. A value + of zeroDotZero indicates this is the last of a list RwEventIndicator instances." + DEFVAL { zeroDotZero } + ::= { rwEventIndicatorEntry 3 } + +----- + +``` + +``` + +--Rw Service Info Classes + +-- +-- RW Flow Desc Table +-- +rwFlowDescTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowDescEntry + PIB-ACCESS install-notify + STATUS current + DESCRIPTION + "PRC representing the information of flows involved in a session. + Referenced by the RwFlowBasedDecInfoFlowDesc and RwFlowDescNext." + ::= { rwServiceInfoClasses 1 } + +rwFlowDescEntry OBJECT-TYPE + SYNTAX RwFlowDescEntry + STATUS current + DESCRIPTION + "An entry in the Flow Desc Table describing the information of a list + flows. + It is referenced by RwFlowBasedDecInfoFlowDesc and RwFlowDescNext. It + may be carried by COPS-PR Install decision from PD-PE to PE-PE, or by COPS-PR RPT + responding to the NAT request from PD-PE." + PIB-INDEX { RwFlowDescPrid } + UNIQUENESS { } + ::= { rwFlowDescTable 1 } + +RwFlowDescEntry ::= SEQUENCE { + rwFlowDescPrid InstanceId, + rwFlowDescSingleFlowInfo Prid, + rwFlowDescConnectInfo Prid, + rwFlowDescNext Prid +} + +rwFlowDescPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of + the RwFlowDesc class." + ::= { rwFlowDescEntry 1 } + +rwFlowDescSingleFlowInfo OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that references the first of a list of + RwSingleFlowInfo Instances. In COPS-PR install decision and RPT of responding to + the NAT request from PD-PE. There is at least one RwSingleFlowDesc Instance in + the COPS-PR install decision." + ::= { rwFlowDescEntry 2 } + +rwFlowDescConnectInfo OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies + an instance of the RwMPLSConnectionInfo or RwVSWITCHConnectInfo. A + value of zeroDotZero indicates there are no Flow Connection Information + included. It is not required in the COPS-PR RPT message responding to the NAT + request from PD-PE." + DEFVAL { zeroDotZero } + ::= { rwFlowDescEntry 3 } + +``` + +``` + +rwFlowDescNext OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "References the next of a list of RwFlowDesc instances. A value of +zeroDotZero indicates this is the last of a list RwFlowDesc instances." + DEFVAL { zeroDotZero } + ::= { rwFlowDescEntry 4 } + +----- + +-- +-- Rw Single Flow Info Table +-- + +rwSingleFlowInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwSingleFlowInfoEntry + PIB-ACCESS install-notify + STATUS current + DESCRIPTION + "PRC representing the information of flow, which is identified with a +Flow ID." + ::= { rwServiceInfoClasses 2 } + +rwSingleFlowInfoEntry OBJECT-TYPE + SYNTAX RwSingleFlowInfoEntry + STATUS current + DESCRIPTION + "An entry in the Single Flow Info Table describing the information of +a flow. + It is referenced by RwFlowDescSingleFlowInfo. There should be two +entries when the NAT is implemented, one for the access side flow and the +other for core side flow. Otherwise one entry for each flow." + PIB-INDEX { RwSingleFlowInfoPrid } + UNIQUENESS { } + ::= { rwSingleFlowInfoTable 1 } + +RwSingleFlowInfoEntry ::= SEQUENCE { + rwSingleFlowInfoPrid InstanceId, + rwSingleFlowInfoFlowId Integer32, + rwSingleFlowInfoFlowTermination Prid, + rwSingleFlowInfoAddressRealm Prid, + rwSingleFlowInfoLatchingIndication Prid, + rwSingleFlowInfoFirewallModeIndicationPrid, + rwSingleFlowInfoFlowDirDesc Prid +} + +rwSingleFlowInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an +instance of the RwSingleFlowInfo entry." + ::= { rwSingleFlowInfoEntry 1 } + +rwSingleFlowInfoFlowId OBJECT-TYPE + SYNTAX Integer32 + STATUS current + DESCRIPTION + "The FlowId itself." + ::= { rwSingleFlowInfoEntry 2 } + +rwSingleFlowInfoFlowTermination OBJECT-TYPE + +``` + +``` + + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +RwFlowTermination. A value of zeroDotZero indicates there are no NAT +implementation in the PE-PE." + DEFVAL { zeroDotZero } + ::= { rwSingleFlowInfoEntry 3 } + +rwSingleFlowInfoAddressRealm OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +RwFlowAddressRealm. A value of zeroDotZero indicates there are no Address Realm +information associated with this Single Flow Info." + DEFVAL { zeroDotZero } + ::= { rwSingleFlowInfoEntry 4 } + +rwSingleFlowInfoLatchingIndication OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +RwFlowLatchingIndication. A value of zeroDotZero indicates there are no Latching +Indication information associated with this Single Flow Info." + DEFVAL { zeroDotZero } + ::= { rwSingleFlowInfoEntry 5 } + +rwSingleFlowInfoFirewallModeIndication OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +RwFlowFirewallModeIndication. A value of zeroDotZero indicates the default +firewall working mode will be applied." + DEFVAL { zeroDotZero } + ::= { rwSingleFlowInfoEntry 6 } + +rwSingleFlowInfoFlowDirDesc OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "References the first of a list of RwFlowDirDesc associated with this +instance of Single Flow Info. There is one RwFlowDirDesc instance per +direction(uplink or downlink)." + ::= { rwSingleFlowInfoEntry 7 } + +----- +-- +-- Rw Flow Termination Table +-- + +rwFlowTerminationTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowTerminationEntry + PIB-ACCESS install-notify + STATUS current + DESCRIPTION + "PRC representing the side(access or core network) of the flow, which +is identified with a Flow ID." + ::= { rwServiceInfoClasses 3 } + +rwFlowTerminationEntry OBJECT-TYPE + SYNTAX RwFlowTerminationEntry + +``` + +``` + + STATUS current + DESCRIPTION + "An entry in the Flow Termination Table describing the side +information of a flow. + It is referenced by RwSingleFlowInfoFlowTermination." + PIB-INDEX { RwFlowTerminationPrid } + UNIQUENESS { } +::= { rwFlowTerminationTable 1 } + +RwFlowTerminationEntry ::= SEQUENCE { + rwFlowTerminationPrid InstanceId, + rwFlowTermination Integer32, +} + +rwFlowTerminationPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +the RwFlowTermination entry." +::= { rwFlowTerminationEntry 1 } + +rwFlowTermination OBJECT-TYPE + SYNTAX Integer32 { + access (0), + core (1) } + STATUS current + DESCRIPTION + "an integer indicating the side of the flow is terminated." +::= { rwFlowTerminationEntry 2 } + +-- +--Rw Flow Address Realm Table +-- + +rwFlowAddressRealmTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowAddressRealmEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + "PRC representing the address realm of the flow's IP address." +::= { rwServiceInfoClasses 4 } + +rwFlowAddressRealmEntry OBJECT-TYPE + SYNTAX RwFlowAddressRealmEntry + STATUS current + DESCRIPTION + " An entry in the Flow Address Realm Table describing the realm +information of a flow's source and destination address. + It is referenced by RwSingleFlowInfoAddressRealm." + PIB-INDEX { RwFlowAddressRealmPrid } + UNIQUENESS { } +::= { rwFlowAddressRealmTable 1 } + +RwFlowAddressRealmEntry ::= SEQUENCE { + rwFlowAddressRealmPrid InstanceId, + rwFlowAddressRealm OCTET STRING, +} + +rwFlowAddressRealmPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + +``` + +``` + + "An arbitrary integer index that uniquely identifies an + instance of the RwFlowAddressRealm entry." + ::= { rwFlowAddressRealmEntry 1 } + +rwFlowAddressRealm OBJECT-TYPE + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + " indicate the address realm of the flow's source and destination + address." + ::= { rwFlowAddressRealmEntry 2 } + + +-- +--Rw Flow Latching Indication Table +-- + +rwFlowLatchingIndicationTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowLatchingIndicationEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + "PRC representing the latching indication of the flow, which is + identified with a Flow ID." + ::= { rwServiceInfoClasses 5 } + +rwFlowLatchingIndicationEntry OBJECT-TYPE + SYNTAX RwFlowLatchingIndicationEntry + STATUS current + DESCRIPTION + " An entry in the Flow Latching Indication Table describing the + latching information of a flow. + It is referenced by RwSingleFlowInfoLatchingIndication." + PIB-INDEX { RwFlowLatchingIndicationPrid } + UNIQUENESS { } + ::= { rwFlowLatchingIndicationTable 1 } + +RwFlowLatchingIndicationEntry ::= SEQUENCE { + rwFlowLatchingIndicationPrid InstanceId, + rwFlowLatchingIndication Integer32, +} + +rwFlowLatchingIndicationPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwFlowLatchingIndication entry." + ::= { rwFlowLatchingIndicationEntry 1 } + +rwFlowLatchingIndication OBJECT-TYPE + SYNTAX Integer32{ + latching(0), + relatching(1) } + STATUS current + DESCRIPTION + " indicate the latch action of the flow in the PE-PE." + ::= { rwFlowLatchingIndicationEntry 2 } + + +-- Rw Flow Firewall working mode Indication Table +-- + +rwFlowFirewallModeIndicationTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowFirewallModeIndicationEntry + +``` + +``` + +PIB-ACCESS install +STATUS current +DESCRIPTION + "PRC representing the latching indication of the flow, which is +identified with a Flow ID." +::= { rwServiceInfoClasses 6} + +rwFlowFirewallModeIndicationEntry OBJECT-TYPE + SYNTAX RwFlowFirewallModeIndicationEntry + STATUS current + DESCRIPTION + " An entry in the Flow Firewall Mode Indication Table describing the +information for dynamic firewall working mode selection. + It is referenced by RwSingleFlowInfoFirewallModeIndication." + PIB-INDEX { RwFlowFirewallModeIndicationPrid } + UNIQUENESS { } +::= { rwFlowFirewallModeIndicationTable 1 } + +RwFlowFirewallModeIndicationEntry ::= SEQUENCE { + rwFlowFirewallModeIndicationPridInstanceId, + rwFlowFirewallModeIndication Integer32 +} + +rwFlowFirewallModeIndicationPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an +instance of the RwFlowFirewallModeIndication entry." +::= { rwFlowFirewallModeIndicationEntry 1 } + +rwFlowFirewallModeIndication OBJECT-TYPE + SYNTAX Integer32{ + staticPacketFiltering (0), + dynamicPacketFiltering (1), + statefulInspection(2), + deepPacketInspection(3) } + STATUS current + DESCRIPTION + " indicate the information for dynamic firewall working mode +selection." + DEFVAL { 0 } +::= { rwFlowFirewallModeIndicationEntry 2 } + +----- +-- +-- Rw Flow Direction Description Table +-- + +rwFlowDirDescTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowDirDescEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + "PRC representing the information of flow in the direction of uplink +and/or downlink." +::= { rwServiceInfoClasses 7} + +rwFlowDirDescEntry OBJECT-TYPE + SYNTAX RwFlowDirDescEntry + STATUS current + DESCRIPTION + +``` + +``` + + " An entry in the Flow Dec Table describing the information of a flow. + It is referenced by RwSingleFlowInfoFlowDirDesc and +RwFlowDirDescNext." + PIB-INDEX { RwFlowDirDescPrid } + UNIQUENESS { } + ::= { rwFlowDirDescTable 1 } + +RwFlowDirDescEntry ::= SEQUENCE { + rwFlowDirDescPrid InstanceId, + rwFlowDirDescInfo Prid, + rwFlowDirDescFluxInfo Prid, + rwFlowDirDescNext Prid + } + +rwFlowDirDescPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwFlowDirDesc entry." + ::= { rwFlowDirDescEntry 1 } + +rwFlowDirDescInfo OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that references the RwFlowInfo Instances." + ::= { rwFlowDirDescEntry 2 } + +rwFlowDirDescFluxInfo OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "An arbitrary integer index that references the RwFluxInfo Instances." + ::= { rwFlowDirDescEntry 3 } + +rwFlowDirDescNext OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " References the next of a list of RwFlowDirDesc instances. A value of + zeroDotZero indicates this is the last of a list RwFlowDirDesc instances." + DEFVAL { zeroDotZero } + ::= { rwFlowDirDescEntry 4 } + +----- +-- +-- Rw FlowInfo Table +-- + +rwFlowInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC representing the information of flow in the direction of uplink + or ownlink." + ::= { rwServiceInfoClasses 8 } + +rwFlowInfoEntry OBJECT-TYPE + SYNTAX RwFlowInfoEntry + STATUS current + DESCRIPTION + +``` + +``` + + " An entry in the Flow Info Table describing the information of a flow +in the direction of uplink or downlink. + It is referenced by RwFlowDirDec." + PIB-INDEX { RwFlowInfoPrid } + UNIQUENESS { } +::= { rwFlowInfoTable 1 } + +RwFlowInfoEntry ::= SEQUENCE { + rwFlowInfoPrid InstanceId, + rwFlowInfoDirection INTEGER, + rwFlowInfoFilter Prid, + rwFlowInfoFilterStatus INTEGER, + rwFlowInfoServiceType INTEGER +} + +rwFlowInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwFlowInfo." +::= { rwFlowInfoEntry 1 } + +rwFlowInfoDirection OBJECT-TYPE + SYNTAX INTEGER { + uplink (1), + downlink (2) + } + STATUS current + DESCRIPTION + "Indicates the direction the flow." +::= { rwFlowInfoEntry 2 } + +rwFlowInfoFilter OBJECT-TYPE -- filter + SYNTAX Prid + STATUS current + DESCRIPTION + "References an entry of RwFilterTable + that describes the applicable classification filter. + A value of zeroDotZero indicates no filter is + used with this RwFlowInfoTable." +::= { rwFlowInfoEntry 3 } + +rwFlowInfoFilterStatus OBJECT-TYPE --filter status + SYNTAX INTEGER { + close(0), + open(1) + } + STATUS current + DESCRIPTION + "Indicates if this gate will allow traffic to flow." + DEFVAL { open } +::= { rwFlowInfoEntry 4 } + +rwFlowInfoServiceType OBJECT-TYPE --service type + SYNTAX INTEGER { + audio(1), + video(2) + } + STATUS current + DESCRIPTION + "service type" +::= { rwFlowInfoEntry 5 } + +``` + +----- +-- Rw Filter Table + +-- + +rwFilterTable OBJECT-TYPE +SYNTAX SEQUENCE OF RwFilterEntry +PIB-ACCESS install +STATUS current +DESCRIPTION +"The Filter class. A packet has to match all fields in an Filter. +Wildcards may be specified for those fields that are not relevant." +::= { rwServiceInfoClasses 9 } + +rwFilterEntry OBJECT-TYPE +SYNTAX RwFilterEntry +STATUS current +DESCRIPTION +" An entry in the Filter Table describing the information of a +filter." +PIB-INDEX { RwFilterPrid } +UNIQUENESS { } +::= { rwFilterTable 1 } + +RwFilterEntry ::= SEQUENCE { +    rwFilterPrid                    InstanceId, +    rwFilterDstAddrType            InetAddressType, +    rwFilterDstAddr                    InetAddress, +    rwFilterDstPrefixLength        InetAddressPrefixLength, +    rwFilterSrcAddrType            InetAddressType, +    rwFilterSrcAddr                    InetAddress, +    rwFilterSrcPrefixLength        InetAddressPrefixLength, +    rwFilterDscp                    DscpOrAny, +    rwFilterProtocol                Unsigned32, +    rwFilterDstL4PortMin            InetPortNumber, +    rwFilterDstL4PortMax            InetPortNumber, +    rwFilterSrcL4PortMin            InetPortNumber, +    rwFilterSrcL4PortMax            InetPortNumber +} + +rwFilterPrid OBJECT-TYPE +SYNTAX InstanceId +STATUS current +DESCRIPTION +"An arbitrary integer index that uniquely identifies an +instance of the Rw Filter class." +::= { rwFilterEntry 1 } + +rwFilterDstAddrType OBJECT-TYPE +SYNTAX InetAddressType +STATUS current +DESCRIPTION +"The address type enumeration value to specify the type of +the packet's destination IP address. " +REFERENCE +"Textual Conventions for Internet Network Addresses. +RFC 4001." +::= { rwFilterEntry 2 } + +rwFilterDstAddr OBJECT-TYPE +SYNTAX InetAddress +STATUS current +DESCRIPTION + +"The IP address to match against the packet's destination IP address. If the address type is 'ipv4', 'ipv6', 'ipv4z' or 'ipv6z' then, the attribute RwFilterDstPrefixLength indicates the number of bits that are relevant. " + +### REFERENCE + +"Textual Conventions for Internet Network Addresses. +RFC 4001." + +::= { rwFilterEntry 3 } + +### rwFilterDstPrefixLength OBJECT-TYPE + +SYNTAX InetAddressPrefixLength + +STATUS current + +### DESCRIPTION + +" The length of a mask for the matching of the destination IP address. This attribute is interpreted only if the InetAddressType is 'ipv4', 'ipv4z', 'ipv6' or 'ipv6z'. Masks are constructed by setting bits in sequence from the most-significant bit downwards for RwFilterDstPrefixLength bits length. All other bits in the mask, up to the number needed to fill the length of the address RwFilterDstAddr are cleared to zero. A zero bit in the mask then means that the corresponding bit in the address always matches. + +In IPv4 addresses, a length of 0 indicates a match of any address; a length of 32 indicates a match of a single host address, and a length between 0 and 32 indicates the use of a CIDR Prefix. IPv6 is similar, except that prefix lengths range from 0..128." + +### REFERENCE + +"Textual Conventions for Internet Network Addresses. +RFC 4001." + +DEFVAL { 0 } + +::= { rwFilterEntry 4 } + +### rwFilterSrcAddrType OBJECT-TYPE + +SYNTAX InetAddressType + +STATUS current + +### DESCRIPTION + +"The address type enumeration value to specify the type of the packet's source IP address. " + +### REFERENCE + +"Textual Conventions for Internet Network Addresses. +RFC 4001." + +::= { rwFilterEntry 5 } + +### rwFilterSrcAddr OBJECT-TYPE + +SYNTAX InetAddress + +STATUS current + +### DESCRIPTION + +"The IP address to match against the packet's source IP address. If the address type is 'ipv4', 'ipv6', 'ipv4z' or 'ipv6z' then, the attribute RwFilterSrcPrefixLength indicates the number of bits that are relevant. " + +### REFERENCE + +"Textual Conventions for Internet Network Addresses. +RFC 4001." + +::= { rwFilterEntry 6 } + +### rwFilterSrcPrefixLength OBJECT-TYPE + +SYNTAX InetAddressPrefixLength + +STATUS current + +DESCRIPTION + +" The length of a mask for the matching of the source IP address. This attribute is interpreted only if the InetAddressType is 'ipv4', 'ipv4z', 'ipv6' or 'ipv6z'. Masks are constructed by setting bits in sequence from the most-significant bit downwards for RwFilterSrcPrefixLength bits length. All other bits in the mask, up to the number needed to fill the length of the address RwFilterDstAddr are cleared to zero. A zero bit in the mask then means that the corresponding bit in the address always matches. + +In IPv4 addresses, a length of 0 indicates a match of any address; a length of 32 indicates a match of a single host address, and a length between 0 and 32 indicates the use of a CIDR Prefix. IPv6 is similar, except that prefix lengths range from 0..128." + +REFERENCE + +"Textual Conventions for Internet Network Addresses. RFC 4001." + +DEFVAL { 0 } + +::= { rwFilterEntry 7 } + +rwFilterDscp OBJECT-TYPE + +SYNTAX DscpOrAny + +STATUS current + +DESCRIPTION + +"The value that the DSCP in the packet can have and match this filter. A value of -1 indicates that a specific DSCP value has not been defined and thus all DSCP values are considered a match." + +REFERENCE + +"Management Information Base for the Differentiated Services Architecture. RFC 3289." + +DEFVAL { -1 } + +::= { rwFilterEntry 8 } + +rwFilterProtocol OBJECT-TYPE + +SYNTAX Unsigned32 (0..255) + +STATUS current + +DESCRIPTION + +"The layer-4 protocol Id to match against the IPv4 protocol number or the IPv6 Next-Header number in the packet. A value of 255 means match all. Note the protocol number of 255 is reserved by IANA, and Next-Header number of 0 is used in IPv6." + +DEFVAL { 255 } + +::= { rwFilterEntry 9 } + +rwFilterDstL4PortMin OBJECT-TYPE + +SYNTAX InetPortNumber + +STATUS current + +DESCRIPTION + +"The minimum value that the packet's layer 4 destination port number can have and match this filter. This value must be equal to or lesser than the value specified for this filter in RwFilterDstL4PortMax. + +COPS-PR error code 'attrValueInvalid' must be returned if the RwFilterDstL4PortMin is greater than RwFilterDstL4PortMax" + +REFERENCE + +``` + + "COPS Usage for Policy Provisioning. RFC 3084, error + codes section 4.5." + DEFVAL { 0 } + + ::= { rwFilterEntry 10 } + +rwFilterDstL4PortMax OBJECT-TYPE + SYNTAX InetPortNumber + STATUS current + DESCRIPTION + "The maximum value that the packet's layer 4 destination + port number can have and match this filter. This value must + be equal to or greater that the value specified for this + filter in RwFilterDstL4PortMin. + + COPS-PR error code 'attrValueInvalid' must be returned if + the RwFilterDstL4PortMax is less than + RwFilterDstL4PortMin" + REFERENCE + "COPS Usage for Policy Provisioning. RFC 3084, error + codes section 4.5." + DEFVAL { 65535 } + ::= { rwFilterEntry 11 } + +rwFilterSrcL4PortMin OBJECT-TYPE + SYNTAX InetPortNumber + STATUS current + DESCRIPTION + "The minimum value that the packet's layer 4 source port + number can have and match this filter. This value must + be equal to or lesser that the value specified for this + filter in RwFilterSrcL4PortMax. + + COPS-PR error code 'attrValueInvalid' must be returned if + the RwFilterSrcL4PortMin is greater than + RwFilterSrcL4PortMax" + REFERENCE + "COPS Usage for Policy Provisioning. RFC 3084, error + codes section 4.5." + DEFVAL { 0 } + ::= { rwFilterEntry 12 } + +rwFilterSrcL4PortMax OBJECT-TYPE + SYNTAX InetPortNumber + STATUS current + DESCRIPTION + "The maximum value that the packet's layer 4 source port + number can have and match this filter. This value must be + equal to or greater that the value specified for this filter + in RwFilterSrcL4PortMin. + + COPS-PR error code 'attrValueInvalid' must be returned if + the RwFilterSrcL4PortMax is less than + RwFilterSrcL4PortMin" + REFERENCE + "COPS Usage for Policy Provisioning. RFC 3084, error codes + section 4.5." + DEFVAL { 65535 } + ::= { rwFilterEntry 13 } +----- +-- +-- RW Flux Info Table +-- + +``` + +``` + +rwFluxInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFluxInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC representing the bandwidth information ." + ::= { rwServiceInfoClasses 10 } + +rwFluxInfoEntry OBJECT-TYPE + SYNTAX RwFluxInfoEntry + STATUS current + DESCRIPTION + " An entry in the Flux Info Table describing the bandwidth + information of a flow in the direction of uplink or downlink. + It is referenced by RwFlowDirDec, RwVSWITCHFluxInfoBaseFluxInfo and + RwUserbasedDecInfo. " + PIB-INDEX { RwFluxInfoPrid } + UNIQUENESS { } + ::= { rwFluxInfoTable 1 } + +RwFluxInfoEntry ::= SEQUENCE { + rwFluxInfoPrid InstanceId, + rwFluxInfoBandwidthUnit INTEGER, + rwFluxInfoPeakBandwidth Unsigned32, + rwFluxInfoAverageBandwidth Unsigned32, + rwFluxInfoMaxPktLength Unsigned32 +} + +rwFluxInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the Rw Flux class." + ::= { rwFluxInfoEntry 1 } + +rwFluxInfoBandwidthUnit OBJECT-TYPE --bandwidth unit + SYNTAX INTEGER { + bps (1), + kbps (2), + mbps (3) + } + STATUS current + DESCRIPTION + "Indication of the unit of measure for RwFluxPeakBandwidth and + RwFluxAverageBandwidth, in bits per second, kilo bits per second, + or mega bits per second." + ::= { rwFluxInfoEntry 2 } + +rwFluxInfoPeakBandwidth OBJECT-TYPE --peak bandwidth + SYNTAX Unsigned32 + STATUS current + DESCRIPTION "The Flux peak bandwidth." + ::= { rwFluxInfoEntry 3 } + +rwFluxInfoAverageBandwidth OBJECT-TYPE --average bandwidth + SYNTAX Unsigned32 + STATUS current + DESCRIPTION "The Flux average bandwidth." + ::= { rwFluxInfoEntry 4 } + +rwFluxInfoMaxPktLength OBJECT-TYPE -- Max package length + SYNTAX Unsigned32 + +``` + +``` + +STATUS current +DESCRIPTION "The Flux max packet length." +::= { rwFluxInfoEntry 5 } + +----- +-- +-- RW VSWITCH Flux Table +-- + +rwVSWITCHFluxInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwVSWITCHFluxInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION " PRC representing the flux information." +::= { rwServiceInfoClasses 11 } + +rwVSWITCHFluxInfoEntry OBJECT-TYPE + SYNTAX RwVSWITCHFluxInfoEntry + STATUS current + DESCRIPTION + " An entry in the VSWITCH Flux Info Table describing the flux + information of a flow in the direction of uplink or downlink. + It is referenced by RwFlowDirDec." + PIB-INDEX { RwVSWITCHFluxInfoPrid } + UNIQUENESS { } +::= { rwVSWITCHFluxInfoTable 1 } + +RwVSWITCHFluxInfoEntry ::= SEQUENCE { + rwVSWITCHFluxInfoPrid InstanceId, + rwVSWITCHFluxInfoBaseFluxInfo Prid, + rwVSWITCHFluxInfoFlowPriority INTEGER, + rwVSWITCHFluxInfoCarFlag INTEGER, + rwVSWITCHFluxInfoBroadcastBateFlag INTEGER, + rwVSWITCHFluxInfoPathBackupFlag INTEGER, +} + +rwVSWITCHFluxInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the Rw VSWITCH Flux class." +::= { rwVSWITCHFluxInfoEntry 1 } + +rwVSWITCHFluxInfoBaseFluxInfo OBJECT-TYPE -- base traffic information + SYNTAX Prid + STATUS current + DESCRIPTION + "Reference the instances of the RwFluxInfoTable, + contain the basic bandwidth information " +::= { rwVSWITCHFluxInfoEntry 2 } + +rwVSWITCHFluxInfoFlowPriority OBJECT-TYPE -- flow Priority + SYNTAX INTEGER + STATUS current + DESCRIPTION + "Indication of the flow's priority. + Can be divided to 8. level0 - 7" +::= { rwVSWITCHFluxInfoEntry 3 } + +rwVSWITCHFluxInfoCarFlag OBJECT-TYPE --car flag + SYNTAX INTEGER + +``` + +``` + + STATUS current + DESCRIPTION + "Indicate whether the route will do car." + ::= { rwVSWITCHFluxInfoEntry 4 } + +rwVSWITCHFluxInfoBroadcastBateFlag OBJECT-TYPE --broadcast bate flag + SYNTAX INTEGER + STATUS current + DESCRIPTION + "The flag indicates the bate of broadcast, if true, + make car." + ::= { rwVSWITCHFluxInfoEntry 5 } + +rwVSWITCHFluxInfoPathBackupFlag OBJECT-TYPE -- Path backup flag + SYNTAX INTEGER + STATUS current + DESCRIPTION + "The flag indicates whether there is backup path" + ::= { rwVSWITCHFluxInfoEntry 6 } + +----- +-- Path Selection Information in the core network +-- +-- MPLS Connection Table +-- + +rwMPLSConnectInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwMPLSConnectInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC representing the MPLS LSP information.." + ::= { rwServiceInfoClasses 12 } + +rwMPLSConnectInfoEntry OBJECT-TYPE + SYNTAX RwMPLSConnectInfoEntry + STATUS current + DESCRIPTION + " An entry in the MPLS Connection Table describing the MPLS LSP +information. + It is referenced by RwFlowDescConnectInfo." + PIB-INDEX { RwMPLSConnectInfoPrid } + UNIQUENESS { } + ::= { rwMPLSConnectInfoTable 1 } + +RwMPLSConnectInfoEntry ::= SEQUENCE { + rwMPLSConnectInfoPrid InstanceId, + rwMPLSConnectInfoPathMTU Unsigned32, + rwMPLSConnectInfoMPLSStack Prid +} + +rwMPLSConnectInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the Rw Connection Info class." + ::= { rwMPLSConnectInfoEntry 1 } + +rwMPLSConnectInfoPathMTU OBJECT-TYPE --Maximum transport unit in the path + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + +``` + +``` + + "The MTU in the path." + ::= { rwMPLSConnectInfoEntry 2 } + +rwMPLSConnectInfoMPLSStack OBJECT-TYPE --label stack + SYNTAX Prid + STATUS current + DESCRIPTION + "References the first of a list of Rw MPLS Label. + + A value of zeroDotZero indicates an empty list which is an error +condition." + DEFVAL { zeroDotZero } + ::= { rwMPLSConnectInfoEntry 3 } + +-- +-- Rw MPLS Label Table +-- + +rwMPLSLabelTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwMPLSLabelEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + "PRC representing the MPLS label stack.." + ::= { rwServiceInfoClasses 13 } + +rwMPLSLabelEntry OBJECT-TYPE + SYNTAX RwMPLSLabelEntry + STATUS current + DESCRIPTION + "An entry in the MPLS Label Table describing the MPLS label stack. + It is referenced by RwMPLSConnectInfoMPLSStack. " + PIB-INDEX { RwMPLSLabelPrid } + UNIQUENESS { } + ::= { rwMPLSLabelTable 1 } + +RwMPLSLabelEntry ::= SEQUENCE { + rwMPLSLabelPrid InstanceId, + rwMPLSLabelValue Prid, + rwMPLSLabelNext Prid +} + +rwMPLSLabelPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the Rw label class." + ::= { rwMPLSLabelEntry 1 } + +rwMPLSLabelValue OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "The label value, reference the frwkILabelMarkerTable in RFC3318 " + ::= { rwMPLSLabelEntry 2 } + +rwMPLSLabelNext OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "References the next RwLabelEntry of a list RwLabel + class." + ::= { rwMPLSLabelEntry 3 } + +``` + +``` + + DEFVAL { zeroDotZero } +::= { rwMPLSLabelEntry 3 } + +----- +-- VSwitch Connection Table +-- + +rwVSWITCHConnectInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwVSWITCHConnectInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC representing the information of the VSWITCH connection." +::= { rwServiceInfoClasses 14 } + +rwVSWITCHConnectInfoEntry OBJECT-TYPE + SYNTAX RwVSWITCHConnectInfoEntry + STATUS current + DESCRIPTION + " An entry in the MPLS Connection Table describing the information of +the VSWITCH connection. + It is referenced by RwFlowDescConnectInfo." + PIB-INDEX { RwVSWITCHConnectInfoPrid } + UNIQUENESS { } +::= { rwVSWITCHConnectInfoTable 1 } + +RwVSWITCHConnectInfoEntry ::= SEQUENCE { + rwVSWITCHConnectInfoPrid InstanceId, + rwVSWITCHConnectInfoSrcIFName OCTET STRING, + rwVSWITCHConnectInfoSrcVlanID Unsigned32, + rwVSWITCHConnectInfoSrcVlanIDQinQ Unsigned32, + rwVSWITCHConnectInfoDstIFName OCTET STRING, + rwVSWITCHConnectInfoDstVlanID Unsigned32, + rwVSWITCHConnectInfoDstVlanIDQinQ Unsigned32 +} + +rwVSWITCHConnectInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an +instance of the Rw VSWITCH Connection Info class." +::= { rwVSWITCHConnectInfoEntry 1 } + +rwVSWITCHConnectInfoSrcIFName OBJECT-TYPE +--source interface address information + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + "Source Interface Name." +::= { rwVSWITCHConnectInfoEntry 2 } + +rwVSWITCHConnectInfoSrcVlanID OBJECT-TYPE --source VlanID + SYNTAX Unsigned32(0..64535) + STATUS current + DESCRIPTION + "Source VlanID." +::= { rwVSWITCHConnectInfoEntry 3 } + +rwVSWITCHConnectInfoSrcVlanIDQinQ OBJECT-TYPE --source VlanID QinQ + SYNTAX Unsigned32(0..64535) + STATUS current + DESCRIPTION + +``` + +``` + + "It's the normal 802.1Q when the value is illegal or invalid. + If the value is valid ,it's the QinQ, the value is inner + VlanID and RwVSWITCHConnectInfoSrcVlanID is the outer VlanID" + ::= { rwVSWITCHConnectInfoEntry 4 } + +rwVSWITCHConnectInfoDstIFName OBJECT-TYPE + --destination interface address information + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + "Dest Interface Name." + ::= { rwVSWITCHConnectInfoEntry 5 } + +rwVSWITCHConnectInfoDstVlanID OBJECT-TYPE --destination VlanID + SYNTAX Unsigned32(0..64535) + STATUS current + DESCRIPTION + "Dest VlanID." + ::= { rwVSWITCHConnectInfoEntry 6 } + +rwVSWITCHConnectInfoDstVlanIDQinQ OBJECT-TYPE --destination VlanID QinQ + SYNTAX Unsigned32(0..64535) + STATUS current + DESCRIPTION + "It's the normal 802.1Q when the value is illegal or invalid. + If the value is valid ,it's the QinQ, the value is inner + VlanID and RwVSWITCHConnectInfoSrcVlanID is the outer VlanID" + ::= { rwVSWITCHConnectInfoEntry 7 } + +----- +-- +-- Rw Request Info Classes +-- +-- +-- Rw Request Info Table +-- + +rwReqInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwReqInfoEntry + PIB-ACCESS notify + STATUS current + DESCRIPTION + "PRC from PE-PE to PD-PE, indicating the physical and/or logical + connection of the access transport network that the CPE is attached to, + requesting user-based policy." + ::= { rwReqInfoClasses 1 } + +rwReqInfoEntry OBJECT-TYPE + SYNTAX RwReqInfoEntry + STATUS current + DESCRIPTION + " An instance of the RwReqInfo class sent by PE-PE to PD-PE. " + PIB-INDEX { RwReqInfoPrid } + UNIQUENESS { } + ::= { rwReqInfoTable 1 } + +RwReqInfoEntry ::= SEQUENCE { + rwReqInfoPrid InstanceId, + rwReqInfoIPAddrType InetAddressType, + rwReqInfoIPAddress InetAddress, + rwReqInfoUserID OCTET STRING, + rwReqInfoMacAddr OCTET STRING, + rwReqInfoPhyInfo OCTET STRING, + rwReqBindingTokenRefPrid Prid +} + +``` + +``` + + } + +rwReqInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwReqInfo entry." + ::= { rwReqInfoEntry 1 } + +rwReqInfoIPAddrType OBJECT-TYPE + SYNTAX InetAddressType + STATUS current + DESCRIPTION + "The address type enumeration value to specify the type of the CPE's +IP address(Ipv4, Ipv6 or DNS etc.)." + ::= { rwReqInfoEntry 2 } + +rwReqInfoIPAddress OBJECT-TYPE + SYNTAX InetAddress + STATUS current + DESCRIPTION + "CPE's Ip Address." + ::= { rwReqInfoEntry 3 } + +rwReqInfoUserId OBJECT-TYPE + SYNTAX OCTET STRING(SIZE (0..67)) + STATUS current + DESCRIPTION + "User ID uniquely identifies the CPE, in a format consistent with the +NAI specification." + ::= { rwReqInfoEntry 4 } + +rwReqInfoMacAddr OBJECT-TYPE + SYNTAX OCTET STRING(SIZE (0..16)) + STATUS current + DESCRIPTION + "CPE's Mac Address. " + ::= { rwReqInfoEntry 5 } + +rwReqInfoPhyInfo OBJECT-TYPE + SYNTAX OCTET STRING(SIZE (0..63)) + STATUS current + DESCRIPTION + "CPE's physics information." + ::= { rwReqInfoEntry 6 } + +rwReqBindingTokenRefPrid OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "This shall be used for pull mode supporting Authorization token for +binding purposes. This shall refer to instance of RwReqBindingToken class. Value +zeroDotZero shall refer to absence of authorization token and this value could +be used when different mechanism other than authorization token is used for +binding purposes in pull mode" + DEFVAL { zeroDotZero } + ::= { rwReqInfoEntry 7 } + +``` + +``` + + + -- + -- Rw Binding Token Table + -- + +``` + +``` + +rwReqBindingTokenTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwReqBindingTokenEntry + PIB-ACCESS notify + STATUS current + DESCRIPTION + "PRC from PE-PE to PD-PE, containing the authorization token which is used for + pull scenario using this authorization token as binding mechanism." + ::= { rwReqInfoClasses 2 } + +rwReqBindingTokenEntry OBJECT-TYPE + SYNTAX RwReqBindingTokenEntry + STATUS current + DESCRIPTION + " An instance of the RwReqBinding class sent by PE-PE to PD-PE. " + PIB-INDEX { RwReqBindingTokenPrid } + UNIQUENESS { } + ::= { rwReqBindingTokenTable 1 } + +RwReqBindingTokenEntry ::= SEQUENCE { + rwReqBindingTokenPrid InstanceId, + rwReqBindingTokenValue OCTET STRING +} + +rwReqBindingTokenPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwReqBindingToken entry." + ::= { rwReqBindingTokenEntry 1 } + +rwReqBindingTokenValue OBJECT-TYPE + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + "Contains authorization token for pull mode binding purposes." + ::= { rwReqBindingTokenEntry 2 } + +----- +-- Rw Decision Info classes + +-- Rw Flow-based Decision Information Table +-- + +rwFlowBasedDecInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwFlowBasedDecInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC from PD-PE to PE-PE carried by COPS-PR Install decision, + providing flow-based policy and/or NAT request." + ::= { rwDecInfoClasses 1 } + +rwFlowBasedDecInfoEntry OBJECT-TYPE + SYNTAX RwFlowBasedDecInfoEntry + STATUS current + DESCRIPTION + " An instance of the RwFlowBasedDecInfo class sent by PD-PE to + PE-PE, carrying the QoS policy and/or NAT request." + PIB-INDEX { RwFlowBasedDecInfoPrid } + UNIQUENESS { } + ::= { rwFlowBasedDecInfoTable 1 } + +RwFlowBasedDecInfoEntry ::= SEQUENCE { + rwFlowBasedDecInfoPrid InstanceId, +} + +``` + +``` + + rwFlowBasedDecInfoRequestPriority Integer32, + rwFlowBasedDecInfoFlowDesc Prid, + rwFlowBasedDecInfoNatAction Prid, + rwFlowBasedDecInfoEventIndicator Prid, + rwFlowBasedDecAppChrgIds Prid + } + + rwFlowBasedDecInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwFlowBasedDecInfo Entry." + ::= { rwFlowBasedDecInfoEntry 1 } + + rwFlowBasedDecInfoRequestPriority OBJECT-TYPE + SYNTAX Integer32(0-7) + STATUS current + DESCRIPTION + " The indication of the importance of a resource control request. It + can be used for processing simultaneous requests by PE-PE based on the priority + level. 0 is the lowest level of priority by default." + DEFVAL { 0 } + ::= { rwFlowBasedDecInfoEntry 2 } + + rwFlowBasedDecInfoFlowDesc OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "References the first of a list of RwFlowDesc associated + with this instance of RwFlowBasedDecInfo. + A value of zeroDotZero indicates an empty list which is an error + condition." + ::= { rwFlowBasedDecInfoEntry 3 } + + rwFlowBasedDecInfoNatAction OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " An arbitrary integer index that references the first of a list of + RwNatAction Instances. + References the first of a list of RwNatAction class instances that are + associated with this decision. + A value of zeroDotZero indicates there are no RwNatAction class + instance associated with this decision." + ::= { rwFlowBasedDecInfoEntry 4 } + + rwFlowBasedDecInfoEventIndicator OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " an arbitrary integer that uniquely identifies an instance of the + RwEventIndicator Entry." + ::= { rwFlowBasedDecInfoEntry 5 } + + rwFlowBasedDecAppChrgIds OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " An arbitrary integer index that uniquely identifies an instance of + the RwAppChrgInfo. + +``` + +There should be one Application Charging ID for each session identified by a Client Handle value. A value of zeroDotZero indicates an empty list and there is no Application Charging Info associated with this Decision." + +``` + DEFVAL { zeroDotZero } +::= { rwFlowBasedDecInfoEntry 6 } +``` + +----- + +-- + +--Rw NAT action Table + +-- + +**rwNatActionTable** OBJECT-TYPE + +SYNTAX SEQUENCE OF **RwNatActionEntry** + +PIB-ACCESS install + +STATUS current + +DESCRIPTION + +" PRC representing NAT Action information. Sent by PD-PE to indicate which type of NAT is requested in PE-PE. In a COPS-PR install decision object." + +``` +::= { rwDecInfoClasses 2 } +``` + +**rwNatActionEntry** OBJECT-TYPE + +SYNTAX **RwNatActionEntry** + +STATUS current + +DESCRIPTION + +" An entry in the NAT Action Table describing a single NAT type. + +Each entry is referenced by **RwDecInfoNatAction** or **RwNatActionNext**." + +PIB-INDEX { **RwNatActionPrid** } + +UNIQUENESS { } + +``` +::= { rwNatActionTable 1 } +``` + +**RwNatActionEntry** ::= SEQUENCE { + +**rwNatActionPrid** InstanceId, + +**rwNatAction** Integer32, + +**rwNatActionNext** Prid, + +} + +**rwNatActionPrid** OBJECT-TYPE + +SYNTAX InstanceId + +STATUS current + +DESCRIPTION + +"An arbitrary integer index that uniquely identifies an instance of the **RwNatAction** class." + +``` +::= { rwNatActionEntry 1 } +``` + +**rwNatAction** OBJECT-TYPE + +SYNTAX Integer32{ + +addressTranslation(1), + +portTranslation(2), + +protocolTranslation(3) + +} + +STATUS current + +DESCRIPTION + +" The basic type of Nat which the PD-PE request the PE-PE to perform." + +``` +::= { rwNatActionEntry 2 } +``` + +**rwNatActionNext** OBJECT-TYPE + +SYNTAX Prid + +STATUS current + +DESCRIPTION + +" References the next **RwNatActionEntry** of a list **NatAction**. There should be one NAT action on this list for each service install in the COPS-PR install decision. A value of zeroDotZero indicates the end of the list of NAT action." + +``` +::= { rwNatActionEntry 3 } +``` + +``` + +----- +-- +-- Rw Application Charging Information Table +-- + +rwAppChrgInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwAppChrgInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + "Represents Application Charging Info" + ::= { rwDecInfoClasses 3 } + +rwAppChrgInfoEntry OBJECT-TYPE + SYNTAX RwAppChrgInfoEntry + STATUS current + DESCRIPTION + " An entry in the App Chrg Info Table describing the Application +charging Info. + It is referenced by RwFlowBasedDecAppChrgIds. " + PIB-INDEX { RwAppChrgInfoPrInfo } + UNIQUENESS { } + ::= { rwAppChrgInfoTable 1 } + +RwAppChrgInfoEntry ::= SEQUENCE { + rwAppChrgInfoPrInfo InstanceId, + rwAppChrgInfoValue OCTET STRING +} + +rwAppChrgInfoPrInfo OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwAppChrgInfo class." + ::= { rwAppChrgInfoEntry 1 } + +rwAppChrgInfoValue OBJECT-TYPE + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + "The Application charging Id. " + ::= { rwAppChrgInfoEntry 2 } + +----- +-- +-- Rw User-based Decision Information Table +-- + +rwUserBasedDecInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwUserBasedDecInfoEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC from PD-PE to PE-PE carried by COPS-PR install decision, +provision user-based policy." + ::= { rwDecInfoClasses 4 } + +rwUserBasedDecInfoEntry OBJECT-TYPE + SYNTAX RwUserBasedDecInfoEntry + STATUS current + +``` + +``` + +DESCRIPTION + " An entry in the User based Dec Info Table describing the policy +information." + PIB-INDEX { RwUserBasedDecInfoPrid } + UNIQUENESS { } +::= { rwUserBasedDecInfoTable 1 } + +RwUserBasedDecInfoEntry ::= SEQUENCE { + rwUserBasedDecInfoPrid InstanceId, + rwUserBasedDecInfoUserId Unsigned32, + rwUserBasedDecInfoPolicyId Unsigned32, + rwUserBasedDecInfoNetworkClass Prid, + rwUserBasedDecInfoDirFlux Prid +} + +rwUserBasedDecInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwUserBasedDecInfo class." + ::= { rwUserBasedDecInfoEntry 1 } + +rwUserBasedDecInfoUserId OBJECT-TYPE + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + "User ID uniquely identifies the user for which + the policy is applied." + ::= { rwUserBasedDecInfoEntry 2 } + +rwUserBasedDecInfoPolicyId OBJECT-TYPE + SYNTAX Unsigned32 + STATUS current + DESCRIPTION + "PolicyID is the handle of one policy. The PolicyID is + assigned by PDP. Since there can be a many to many relationship + between PDP and PEP, the PolicyID allocated by different PDP can + not be guaranteed to be unique across network. So PEP can use IP + address of the PDP along with PolicyID to uniquely identify a + dedicated policy." + ::= { rwUserBasedDecInfoEntry 3 } + +rwUserBasedDecInfoNetworkClass OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " An arbitrary integer index that uniquely identifies an instance of + the NetworkClass. A value of zeroDotZero indicates the default network service + class ." + DEFVAL { zeroDotZero } + ::= { rwUserBasedDecInfoEntry 4 } + +rwUserBasedDecInfoDirFlux OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " An arbitrary integer index that uniquely identifies an instance of + the RwDirFlux. A value of zeroDotZero indicates the default bandwidth ." + DEFVAL { zeroDotZero } + ::= { rwUserBasedDecInfoEntry 5 } + +``` + +``` + +----- +-- + +``` + +``` + +--Rw Network Class Table +-- +rwNetworkClassTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwNetworkClassEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC representing network service class subscribed by a CPE sent by +PD-PE to PE-PE. In a COPS-PR install decision object." + ::= { rwDecInfoClasses 5 } + +rwNetworkClassEntry OBJECT-TYPE + SYNTAX RwNetworkClassEntry + STATUS current + DESCRIPTION + " An entry in the Network Class Table describing network service class +subscribed by a CPE. + Referenced by RwUserBasedDecInfoNetworkClass." + PIB-INDEX { RwNetworkClassPrid } + UNIQUENESS { } + ::= { rwNetworkClassTable 1 } + +RwNetworkClassEntry ::= SEQUENCE { + rwNetworkClassPrid InstanceId, + rwNetworkClass OCTET STRING +} + +rwNetworkClassPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an +instance of the RwNetworkClass." + ::= { rwNetworkClassEntry 1 } + +rwNetworkClass OBJECT-TYPE + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + " the network service class subscribed by a CPE (e.g., Premium, Gold, +Silver, and Regular)." + ::= { rwNetworkClassEntry 2 } + +----- +-- +-- Rw Dir Flux Table +-- + +rwDirFluxTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwDirFluxEntry + PIB-ACCESS install + STATUS current + DESCRIPTION + " PRC representing uplink and/or downlink bandwidth information, sent +by PD-PE to PE-PE. In a COPS-PR install decision object." + ::= { rwDecInfoClasses 6 } + +rwDirFluxEntry OBJECT-TYPE + SYNTAX RwDirFluxEntry + STATUS current + DESCRIPTION + " An entry in the Direction Flux Table describing uplink and/or +downlink bandwidth information subscribed by a CPE. + Referenced by RwUserBasedDecInfoDirFlux." + +``` + +``` + + PIB-INDEX { RwDirFluxPrid } + UNIQUENESS { } +::= { rwDirFluxTable 1 } + +RwDirFluxEntry ::= SEQUENCE { + rwDirFluxPrid InstanceId, + rwDirFluxDirection Integer32, + rwDirFluxInfo Prid, + rwDirFluxNext Prid +} + +rwDirFluxPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of +the RwDirFlux." +::= { rwDirFluxEntry 1 } + +rwDirFluxDirection OBJECT-TYPE + SYNTAX Integer32 { + uplink(1), + downlink(2) + } + STATUS current + DESCRIPTION + "Indicates the direction the flow." +::= { rwDirFluxEntry 2 } + +rwDirFluxInfo OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " An arbitrary integer index that references the RwFluxInfo Instances +." +::= { rwDirFluxEntry 3 } + +rwDirFluxNext OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + " References the next RwDirFluxEntry. There should be at most two +Directional Flux per COPS-PR install decision. A value of zeroDotZero indicates +the end of the list of DirFlux." +::= { rwDirFluxEntry 4 } + +``` + +----- + +-- Rw Report Classes + +-- Rw State Report Table + +-- + +``` + +rwStateReportTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwStateReportEntry + PIB-ACCESS notify + STATUS current + DESCRIPTION + " PRCs from PE-PE to PD-PE carried by the COPS-PR RPT message, carrying the +Decision enforcement result or the notification of transport event." +::= { rwReportClasses 1 } + +rwStateReportEntry OBJECT-TYPE + SYNTAX RwStateReportEntry + STATUS current + +``` + +``` + +DESCRIPTION + " An entry in the State Report Table describing the Decision +enforcement result or the notification of transport event." + PIB-INDEX { RwStateReportPrid } + UNIQUENESS { } +::= { rwStateReportTable 1 } + +RwStateReportEntry ::= SEQUENCE { + rwStateReportPrid InstanceId, + rwStateReportStatus INTEGER, + rwStateReportDetails Prid, + rwStateReportNATInfoFlowDesc Prid +} + +rwStateReportPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an + instance of the RwDecResultRpt class." + ::= { rwStateReportEntry 1 } + +rwStateReportStatus OBJECT-TYPE + SYNTAX INTEGER { + success (1), + failure (2), + event (3) } + STATUS current + DESCRIPTION + "When Status is: + success: Indicates the successful implementation of the + decision. + RwStateReportDetails: + Reference an instance of RwRprtBearChrgInfo for the a + successful session; or the + References nothing otherwise (contains the value zeroDotZero). + Failure: Indicates the failure of implementing the decision. + RwStateReportDetails may references an Error object, + or may have the value zeroDotZero when no error + object is needed, in which case COPS and COPS-PR + error codes and error objects are sufficient. + Event: RwStateReportDetails references an instance of + RwEventIndicator." + ::= { rwStateReportEntry 2 } + +rwStateReportDetails OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "May reference an instance of RwRprtBearChrgInfo, RwEventIndicator, or + may have the value of zeroDotZero depending on the value of + RwStateReportStatus." + ::= { rwStateReportEntry 3 } + +rwStateReportNATInfoFlowDesc OBJECT-TYPE + SYNTAX Prid + STATUS current + DESCRIPTION + "Refers to an instance of RwFlowDesc class. This attribute shall refer to + this PRC only if NAT information is requested by PD-PE otherwise this attribute + shall hold value zeroDotZero." + DEFVAL { zeroDotZero } + ::= { rwStateReportEntry 4 } +----- + +``` + +``` + +-- +--Rw report Bearer charging information Table +-- + +rwRprtBearChrgInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF RwRprtBearChrgInfoEntry + PIB-ACCESS notify + STATUS current + DESCRIPTION + "PRC representing the bearer charging information" + ::= { rwReportClasses 2 } + +rwRprtBearChrgInfoEntry OBJECT-TYPE + SYNTAX RwRprtBearChrgInfoEntry + STATUS current + DESCRIPTION + " An entry in the Rprt Bearer Chrg Info Table describing the + information of the bearer Charging Identifier and PE-PE address. + It is referenced by RwStateReportDetails " + PIB-INDEX { RwRprtBearChrgInfoPrid } + UNIQUENESS { } + ::= { rwRprtBearChrgInfoTable 1 } + +RwRprtBearChrgInfoEntry ::= SEQUENCE { + rwRprtBearChrgInfoPrid InstanceId, + rwRprtBearChrgInfoAddrTypeInetAddressType, + rwRprtBearChrgInfoAddr InetAddress, + rwRprtBearChrgInfoChrgId OCTET STRING +} + +rwRprtBearChrgInfoPrid OBJECT-TYPE + SYNTAX InstanceId + STATUS current + DESCRIPTION + "An arbitrary integer index that uniquely identifies an instance of + the RwRprtBearChrgInfo class." + ::= { rwRprtBearChrgInfoEntry 1 } + +rwRprtBearChrgInfoAddrType OBJECT-TYPE + SYNTAX InetAddressType + STATUS current + DESCRIPTION + "The address type enumeration value to specify the type of the + charging device's IP address." + ::= { rwRprtBearChrgInfoEntry 2 } + +rwRprtBearChrgInfoGGSNAddr OBJECT-TYPE + SYNTAX InetAddress + STATUS current + DESCRIPTION + "Contains the IP Address of the device providing the bearer charging + Id." + ::= { rwRprtBearChrgInfoEntry 3 } + +rwRprtBearChrgInfoChrgId OBJECT-TYPE + SYNTAX OCTET STRING + STATUS current + DESCRIPTION + "The bearer Charging ID related to the session." + ::= { rwRprtBearChrgInfoEntry 4 } + +----- +-- +-- Conformance Section + +``` + +-- + +rwCompliances OBJECT IDENTIFIER ::= { rwConformance 1 } +rwGroups OBJECT IDENTIFIER ::= { rwConformance 2 } + +rwCompliance MODULE-COMPLIANCE +STATUS current +DESCRIPTION +"Describes the requirements for conformance to the ITUT-RwPIB." +MODULE FRAMEWORK-PIB -- Defined in RFC 3318 +MANDATORY-GROUPS { +frwkPrcSupportGroup, +frwkILabelMarkerGroup +} +MODULE RW-PIB -- this module +MANDATORY-GROUPS { +rwDecCapGroup, +rwDecCapACKGroup, +rwEventIndicatorGroup, +rwFlowDescGroup, +rwSingleFlowInfoGroup, +rwFlowTerminationGroup, +rwFlowAddressRealmGroup, +rwFlowLatchingIndicationGroup, +rwFlowFirewallModeIndicationGroup, +rwFlowDirDescGroup, +rwFlowInfoGroup, +rwFilterGroup, +rwFluxInfoGroup, +rwVSWITCHFluxInfoGroup, +rwMPLSConnectInfoGroup, +rwMPLSLabelGroup, +rwVSWITCHConnectInfoGroup, +rwReqInfoGroup, +rwReqBindingTokenGroup, +rwFlowbasedDecInfoGroup, +rwNatActionGroup, +rwAppChrgInfoGroup, +rwUserBasedDecInfoGroup, +rwNetworClassGroup, +rwDirFluxGroup, +rwStateReportGroup, +rwRprtBearChrgInfoGroup} +::= { rwCompliances 1 } + +rwDecCapGroup OBJECT-GROUP +OBJECTS { +RwDecCapAppChrgIds, +RwDecCapFlowIds +} +STATUS current +DESCRIPTION +"This Group defines the PIB Objects that describe the Decision +capabilities." +::= { rwGroups 1 } + +rwDecCapACKGroup OBJECT-GROUP +OBJECTS { +RwDecCapACKEnable, +RwDecCapACKChrgIds, +RwDecCapACKFlowIds +} +STATUS current +DESCRIPTION + +``` + + "This Group defines the PIB Objects that describe capabilities which +PE-PE is acceptable." +::= { rwGroups 2 } + +rwEventIndicatorGroup OBJECT-GROUP + OBJECTS { + rwEventIndicator, + rwEventIndicatorNext + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the query and +notification of a transport event." + ::= { rwGroups 3 } + +rwFlowDescGroup OBJECT-GROUP + OBJECTS { + rwFlowDescSingleFlowInfo, + rwFlowDescConnectInfo, + rwFlowDescNext + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the information of a +list flows in a session." + ::= { rwGroups 4 } + +rwSingleFlowInfoGroup OBJECT-GROUP + OBJECTS { + rwSingleFlowInfoFlowId, + rwSingleFlowInfoFlowTermination, + rwSingleFlowInfoAddressRealm, + rwSingleFlowInfoLatchingIndication, + rwSingleFlowInfoFirewallModeIndication, + rwSingleFlowInfoFlowDirDesc + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the information of a +flow, including QoS information, NAT information and path selection information, +etc." + ::= { rwGroups 5 } + +rwFlowTerminationGroup OBJECT-GROUP + OBJECTS { + rwFlowTermination + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the side information +of a flow(access or core)." + ::= { rwGroups 6 } + +rwFlowAddressRealmGroup OBJECT-GROUP + OBJECTS { + rwFlowAddressRealmAddressRealm + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the realm +information of a flow's source and destination address." + ::= { rwGroups 7 } + +rwFlowLatchingIndicationGroup OBJECT-GROUP + +``` + +``` + +OBJECTS { + rwFlowLatchingIndicationLatchingIndication +} +STATUS current +DESCRIPTION + "This Group defines the PIB Objects that describe the latching +information of a flow(latching or relatch)." +::= { rwGroups 8 } + +rwFlowFirewallModeIndicationGroup OBJECT-GROUP +OBJECTS { + rwFlowFirewallModeIndication +} +STATUS current +DESCRIPTION + "This Group defines the PIB Objects that describe the information for +dynamic firewall working mode selection." +::= { rwGroups 9 } + +rwFlowDirDescGroup OBJECT-GROUP +OBJECTS { + rwFlowDirDescInfo, + rwFlowDirDescFluxInfo, + rwFlowDirDescNext +} +STATUS current +DESCRIPTION + "This Group defines the PIB Objects that describe the Qos and NAT +information of flow." +::= { rwGroups 10 } + +rwFlowInfoGroup OBJECT-GROUP +OBJECTS { + rwFlowInfoDirection, + rwFlowInfoFilter, + rwFlowInfoFilterStatus, + rwFlowInfoServiceType +} +STATUS current +DESCRIPTION + "This Group defines the PIB Objects that describe the filter +information of a flow." +::= { rwGroups 11 } + +rwFilterGroup OBJECT-GROUP +OBJECTS { + rwFilterDstAddrType, + rwFilterDstAddr, + rwFilterDstPrefixLength, + rwFilterSrcAddrType, + rwFilterSrcAddr, + rwFilterSrcPrefixLength, + rwFilterDscp, + rwFilterProtocol, + rwFilterDstL4PortMin, + rwFilterDstL4PortMax, + rwFilterSrcL4PortMin, + rwFilterSrcL4PortMax +} +STATUS current +DESCRIPTION + "This Group defines the PIB Objects that describe the information of a +filter." +::= { rwGroups 12 } + +``` + +``` + +rwFluxInfoGroup OBJECT-GROUP + OBJECTS { + rwFluxInfoBandwidthUnit, + rwFluxInfoPeakBandwidth, + rwFluxInfoAverageBandwidth, + rwFluxInfoMaxPktLength + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the bandwidth +information." + ::= { rwGroups 13 } + +rwVSWITCHFluxInfoGroup OBJECT-GROUP + OBJECTS { + rwVSWITCHFluxInfoBaseFluxInfo, + rwVSWITCHFluxInfoFlowPriority, + rwVSWITCHFluxInfoCarFlag, + rwVSWITCHFluxInfoBroadcastBateFlag, + rwVSWITCHFluxInfoPathBackupFlag + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the flux information +of a flow." + ::= { rwGroups 14 } + +rwMPLSConnectInfoGroup OBJECT-GROUP + OBJECTS { + rwMPLSConnectInfoPathMTU, + rwMPLSConnectInfoMPLSStack + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the MPLS LSP +information." + ::= { rwGroups 15 } + +rwMPLSLabelGroup OBJECT-GROUP + OBJECTS { + rwMPLSLabelValue, + rwMPLSLabelNext + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the MPLS label +stack." + ::= { rwGroups 16 } + +rwVSWITCHConnectInfoGroup OBJECT-GROUP + OBJECTS { + rwVSWITCHConnectInfoSrcIFName, + rwVSWITCHConnectInfoSrcVlanID, + rwVSWITCHConnectInfoSrcVlanIDQinQ, + rwVSWITCHConnectInfoDstIFName, + rwVSWITCHConnectInfoDstVlanID, + rwVSWITCHConnectInfoDstVlanIDQinQ + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the information of +the VSWITCH connection." + +``` + +``` + +::= { rwGroups 17 } + +rwReqInfoGroup OBJECT-GROUP + OBJECTS { + rwReqInfoIPAddrType, + rwReqInfoIPAddress, + rwReqInfoUserId, + rwReqInfoMacAddr, + rwReqInfoPhyInfo + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the physical and/or +logical connection of the access transport network that the CPE is attached to." + ::= { rwGroups 18 } + +rwReqBindingTokenGroup OBJECT-GROUP + OBJECTS { + rwReqBindingTokenValue + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the authorization +token which is used for pull scenario using this authorization token as binding +mechanism." + ::= { rwGroups 19} + +rwFlowbasedDecInfoGroup OBJECT-GROUP + OBJECTS { + rwFlowBasedDecInfoRequestPriority, + rwFlowBasedDecInfoFlowDesc, + rwFlowBasedDecInfoNatAction, + rwFlowBasedDecInfoEventIndicator, + rwFlowBasedDecAppChrgIds + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the information QoS +policy and/or NAT request." + ::= { rwGroups 20 } + +rwNatActionGroup OBJECT-GROUP + OBJECTS { + rwNatAction, + rwNatActionNext + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the NAT type." + ::= { rwGroups 21} + +rwAppChrgInfoGroup OBJECT-GROUP + OBJECTS { + rwAppChrgInfoValue + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the Application +charging Info." + ::= { rwGroups 22 } + +rwUserBasedDecInfoGroup OBJECT-GROUP + OBJECTS { + rwUserBasedDecInfoUserId, + +``` + +``` + + rwUserBasedDecInfoPolicyId, + rwUserBasedDecInfoNetworkClass, + rwUserBasedDecInfoDirFlux + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the user-based +policy." + ::= { rwGroups 23 } + +rwNetworClassGroup OBJECT-GROUP + OBJECTS { + rwNetworkClass + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe network service +class subscribed by a CPE " + ::= { rwGroups 24 } + +rwDirFluxGroup OBJECT-GROUP + OBJECTS { + rwDirFluxDirection, + rwDirFluxInfo, + rwDirFluxNext + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe uplink and/or +downlink bandwidth information subscribed by a CPE." + ::= { rwGroups 25 } + +rwStateReportGroup OBJECT-GROUP + OBJECTS { + rwStateReportStatus, + rwStateReportDetails + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the Decision +enforcement result or the notification of transport event." + ::= { rwGroups 26 } + +rwRprtBearChrgInfoGroup OBJECT-GROUP + OBJECTS { + rwRprtBearChrgInfoAddrType, + rwRprtBearChrgInfoAddr, + rwRprtBearChrgInfoChrgId + } + STATUS current + DESCRIPTION + "This Group defines the PIB Objects that describe the information of +the bearer Charging Identifier and PE-PE address." + ::= { rwGroups 27 } + +END + +``` + +# Appendix I + +## Rw stage 2 message to COPS message mapping + +(This appendix does not form an integral part of this Recommendation.) + +Rw stage 2 message to COPS message mapping is shown in Table I.1. + +**Table I.1 – Rw stage 2 message to COPS message mapping** + +| Rw Stage 2 Message | Source | Destination | COPS Message Name | Abbreviation | +|--------------------------------|---------------|--------------------|--------------------------|-----------------------------------| +| Resource Initiation Request | PD-PE | PE-PE | Decision | DEC | +| Resource Initiation Response | PE-PE | PD-PE | Report state | RPT | +| Resource Modification Request | PD-PE | PE-PE | Decision | DEC | +| Resource Modification Response | PE-PE | PD-PE | Report state | RPT | +| Resource Action Request | PE-PE | PD-PE | Request | REQ | +| Resource Action Response | PD-PE | PE-PE | Decision | DEC | +| Resource Notification | PE-PE | PD-PE | Report state | RPT | +| Resource Decision Request | PE-PE | PD-PE | Request | REQ | +| Resource Decision Response | PD-PE | PE-PE | Decision | DEC | +| Resource Release Request | PD-PE | PE-PE | Decision | DEC | +| Resource Release Response | PE-PE | PD-PE | Report state | RPT | +| Abort Resource Request | PE-PE | PD-PE | Delete request state | DRQ | +| Abort Resource Response | PD-PE | PE-PE | – | –
(No response to DRQ in COPS) | + +## Appendix II + +## Rw stage 2 message parameters to COPS Object-PIB-PRC-Attribute mapping + +(This appendix does not form an integral part of this Recommendation.) + +Rw stage 2 message parameters to COPS Object-PIB-PRC-Attribute mapping is shown in Table II.1. + +**Table II.1 – Rw stage 2 message parameters to COPS +Object-PIB-PRC-Attribute mapping** + +| Rw Stage 2 Message Parameter | Object/PIB-PRC-Attribute | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| PD-FE Identifier | | +| Resource Control Session Identifier | Client Handle(Object) | +| Resource Requestor Identifier | | +| Resource Request Priority | RwDecInfoClasses – RwFlowbasedDecInfoTable –
RwFlowBasedDecInfoRequestPriority | +| Reservation Holding Time | – | +| Resource Control Session Information | – | +| Dynamic firewall working mode | RwServiceInfoClasses – RwFlowFirewallModeIndicationTable –
RwFlowFirewallModeIndication | +| Charging correlation information | RwDecInfoClasses – RwAppChrgInfoTable – RwAppChrgInfoValue
RwReportClasses – RwRprtBearChrgInfoTable –
RwRprtBearChrgInfoChrgId | +| PD-FE Identifier | | +| Resource Control Session Identifier | Client Handle(Object) | +| Resource Requestor Identifier | | +| Resource Request Priority | RwDecInfoClasses – RwFlowbasedDecInfoTable –
RwFlowBasedDecInfoRequestPriority | +| Reservation Holding Time | – | +| Resource Control Session Information | – | +| Dynamic firewall working mode | RwServiceInfoClasses – RwFlowFirewallModeIndicationTable –
RwFlowFirewallModeIndication | +| Resource Requestor Identifier | | +| Resource Request Priority | RwDecInfoClasses – RwFlowbasedDecInfoTable –
RwFlowBasedDecInfoRequestPriority | +| Reservation Holding Time | – | +| Resource Control Session Information | – | +| Dynamic firewall working mode | RwServiceInfoClasses – RwFlowFirewallModeIndicationTable –
RwFlowFirewallModeIndication | + +**Table II.1 – Rw stage 2 message parameters to COPS +Object-PIB-PRC-Attribute mapping** + +| Rw Stage 2 Message
Parameter | Object/PIB-PRC-Attribute | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Resource Requestor Identifier | | +| Resource Request Priority | RwDecInfoClasses – RwFlowbasedDecInfoTable –
RwFlowBasedDecInfoRequestPriority | +| Reservation Holding Time | – | +| Resource Control Session
Information | – | +| Dynamic firewall working
mode | RwServiceInfoClasses – RwFlowFirewallModeIndicationTable –
RwFlowFirewallModeIndication | +| Resource Requestor Identifier | | +| Resource Request Priority | RwDecInfoClasses – RwFlowbasedDecInfoTable –
RwFlowBasedDecInfoRequestPriority | +| Reservation Holding Time | – | +| Charging correlation
information | RwDecInfoClasses – RwAppChrgInfoTable – RwAppChrgInfoValue
RwReportClasses – RwRprtBearChrgInfoTable –
RwRprtBearChrgInfoChrgId | +| Media Profile | RwServiceInfoClasses – RwFlowDescTable | +| Media Number | RwServiceInfoClasses – RwFlowDescTable (Position of the current
PRID in the list) | +| Network Class of Service | RwDecInfoClasses – RwNetworClassTable – RwNetworkClass | +| Media Priority | RwDecInfoClasses – RwFlowbasedDecInfoTable –
RwFlowBasedDecInfoRequestPriority | +| Path Selection Information | RwServiceInfoClasses – RwMPLSConnectInfoTable/
RwVSWITCHConnectInfoTable | +| Media Flow Description | RwServiceInfoClasses – RwSingleFlowInfoTable | +| Flow direction | RwServiceInfoClasses – RwFlowInfoTable – RwFlowInfoDirection | +| Flow Number | RwServiceInfoClasses – RwSingleFlowInfoTable –
RwSingleFlowInfoFlowId | +| Gate Status | RwServiceInfoClasses – RwFlowInfoTable – RwFlowInfoFilterStatus | +| Protocol Version | RwServiceInfoClasses – RwFilterTable –
RwFilterDstAddrType/RwFilterSrcAddrType | +| IP Addresses | RwServiceInfoClasses – RwFilterTable –
RwFilterDstAddr/RwFilterSrcAddr | +| Ports | RwServiceInfoClasses – RwFilterTable –
RwFilterDstL4PortMin/RwFilterDstL4PortMax/RwFilterSrcL4PortMin/
RwFilterSrcL4PortMax | +| Protocol Number | RwServiceInfoClasses – RwFilterTable – RwFilterProtocol | +| Bandwidth | RwServiceInfoClasses – RwFluxInfoTable –
RwFluxInfoPeakBandwidth/RwFluxInfoAverageBandwidth | +| IP QoS handling class | RwServiceInfoClasses – RwFilterTable – RwFilterDscp | +| Traffic Descriptor | RwServiceInfoClasses – RwFluxInfoTable/
RwVSWITCHFluxInfoTable | +| Physical Connection Identifier | RwReqInfoClasses – RwReqInfoTable | + +**Table II.1 – Rw stage 2 message parameters to COPS +Object-PIB-PRC-Attribute mapping** + +| Rw Stage 2 Message
Parameter | Object/PIB-PRC-Attribute | +|-----------------------------------------|----------------------------------------------------------------------------------------------------------| +| Logical Connection Identifier | – | +| Resource Reservation Mode | – | +| Event Notification Indication | RwEventInfoClasses – RwEventIndicatorTable – RwEventIndicator | +| Resource Information Indicator | RwEventInfoClasses – RwEventIndicatorTable – RwEventIndicator | +| Transport Loss Indicator | RwEventInfoClasses – RwEventIndicatorTable –
RwEventIndicator(Value=Indication_of loss of bearer) | +| Transport Recovery Indicator | RwEventInfoClasses – RwEventIndicatorTable –
RwEventIndicator(Value=Indication of recovery of bearer) | +| Transport Release Indicator | RwEventInfoClasses – RwEventIndicatorTable –
RwEventIndicator(Value= Indication of Release of bearer) | +| NAPT control and NAT traversal | RwDecInfoClasses – RwNatActionTable | +| Address Binding Information Request | RwServiceInfoClasses – RwFlowInfoTable – RwFlowInfoFilter | +| Address Translation Command | RwDecInfoClasses – RwNatActionTable – RwNatAction | +| Address Binding Information Response | RwServiceInfoClasses – RwFlowInfoTable – RwFlowInfoFilter | +| Resource Request Result | RwReportClasses – RwStateReportTable – RwStateReportStatus
or Report – Type(Object) | +| Authorization Token | RwReqInfoClasses – RwReqBindingTokenTable –
RwReqBindingTokenValue | +| Timestamp | – | +| Reason | Reason(Object) | + +# Bibliography + +- [b-ITU-T Q.Sup51] ITU-T Q-series Recommendations – Supplement 51 (2004), *Signalling Requirements for IP QoS*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dba41bef1bdc3da519696a9b6705ad8074b52031 --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5de58318ff8fa78c687dbcec07f6c84620c48e0ea014b5e7be42cd3dc17cb32 +size 79422 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/37806e0fc150d857046ebc7e47893d7a_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/37806e0fc150d857046ebc7e47893d7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e89e3f0085d9a9945c2e058458b44694df35b32c --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/37806e0fc150d857046ebc7e47893d7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7968b7d5470bd8c5c857060f610c8eaee7bbf08766a6ffd63a063bca9161c22 +size 140845 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462732498ab70e406ddfbcfbfc36c10d1215c846 --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f507e167832f48a635c64f561062770e6dc91f055b2571b5437ce1108579397 +size 60671 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..842a3a8c65231382d739ce668afb8e2b8d4f05da --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7085526dd07314b6201da7f05b0af8e3067327382ed3ab2bda4a04c0ea8d478 +size 95752 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89bc34952d8c589fab4f19cb8ac9c2c92c1c7182 --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1e4323e7a32a9546dc2b18ae899f165219ce6adb7ad7b3ec36025491cb6f181 +size 6534 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/967e98a12645f89cb4a7620f42bf8c2e_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/967e98a12645f89cb4a7620f42bf8c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5337b028732998193e00ac623a24ccba974d0547 --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/967e98a12645f89cb4a7620f42bf8c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8af28227c3dea4124caba0cb8680aea4a9e7cd5c473cc875fcbfe7677953f51 +size 111036 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59a438203f82c55ff43fe662588acb627876d1c3 --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1031bee27fb1520b5968c900c6a1265135571d2159b9966093d9953fced5649 +size 44242 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d73d98ab17306e08889b72c87d2f143b0c22eafc --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd94516627379254efad6fb4d11b7013e66db6e5948f4aa78e0067f3f5072cdf +size 122116 diff --git a/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e70c3ff8bae28035cae315352bd2673d04ea8ad4 --- /dev/null +++ b/marked/Q/T-REC-Q.3303.2-201403-I_PDF-E/raw.md @@ -0,0 +1,3044 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3303.2** + +(03/2014) + +# SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Resource control protocols + +--- + +**Resource control protocol No. 3 – Protocol at +the interface between a policy decision physical +entity (PD-PE) and a policy enforcement +physical entity (PE-PE) (Rw interface): +ITU-T H.248 alternative version 2** + +Recommendation ITU-T Q.3303.2 + +![ITU logo: International Telecommunication Union](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a stylized globe with a red lightning bolt striking through it, and the text "ITU International Telecommunication Union" to its right. + +ITU logo: International Telecommunication Union + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|---------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3649 | +| NGN applications | Q.3700–Q.3849 | +| Testing for next generation networks | Q.3900–Q.3999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.3303.2 + +## **Resource control protocol No. 3 – Protocol at the interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE) (Rw interface): ITU-T H.248 alternative version 2** + +# **Summary** + +Recommendation ITU-T Q.3303.2 specifies the resource control protocol No. 3 (rcp3) ITU-T H.248 profile used at the Rw interface, i.e., between the policy decision physical entity (PD-PE) and the policy enforcement physical entity (PE-PE) in the resource and admission control functional block. + +This protocol profile allows the final admission policy decisions to be installed (either push or pull mode) to a PE-PE from a PD-PE, supports resource control for both fixed and mobile networks and supports the network address and port translation (NAPT) control and network address translation (NAT) traversal at the PE-PEs as needed. It satisfies the requirements for information flows across the Rw reference point as specified in clause 8.2 of Recommendation ITU-T Y.2111. It is also used to control the PE-PE in transport devices, including quality of service (QoS) resource control (e.g., packet marking, filtering and policing) and gate control. + +This version of the Recommendation improves the published version 1 in 2007 and adds additional features to satisfy the full requirements as defined in Recommendation ITU-T Y.2111, based on the developments and progresses of both ITU-T Y.2111 and ITU-T H.248 protocols. New functional packages as well as their procedures are introduced in this version such as "hanging termination detection", "statistics conditional reporting", "IP realm availability" and "Pull mode". Meanwhile, a number of changes are made to refine the profile definitions and the details. + +# **History** + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3303.2 | 2007-08-06 | 11 | 11.1002/1000/9120 | +| 2.0 | ITU-T Q.3303.2 v2 | 2014-03-29 | 11 | 11.1002/1000/12165 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2014 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# Table of Contents + +| | | Page | +|------|------------------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 5 | +| 6 | Rw interface protocol specification (ITU-T H.248 profile description)..... | 6 | +| 6.1 | Profile identification..... | 6 | +| 6.2 | Gateway control protocol version ..... | 6 | +| 6.3 | Connection model..... | 6 | +| 6.4 | Context attributes..... | 6 | +| 6.5 | Terminations..... | 7 | +| 6.6 | Descriptors..... | 10 | +| 6.7 | Command API ..... | 14 | +| 6.8 | Generic command syntax and encoding..... | 18 | +| 6.9 | Transactions..... | 19 | +| 6.10 | Messages..... | 19 | +| 6.11 | Transport..... | 20 | +| 6.12 | Security ..... | 20 | +| 6.13 | Packages ..... | 20 | +| 6.14 | Mandatory support of SDP and Annex C information elements..... | 48 | +| 6.15 | Optional support of SDP and Annex C information elements ..... | 50 | +| 6.16 | Overview of procedures ..... | 52 | +| 6.17 | Session dependent procedures (command level details) ..... | 73 | +| 6.18 | Non-session related use cases..... | 73 | +| 6.19 | Session independent procedures (command level details) ..... | 73 | +| 7 | Security considerations ..... | 73 | +| | Appendix I – Overview of specific policing functions in the policy enforcement physical entity ..... | 75 | +| I.1 | Categorization attempt..... | 75 | +| I.2 | Support by Rw ITU-T H.248 profile version 2 ..... | 76 | +| | Appendix II – Overview of statistics in the policy enforcement physical entity ..... | 77 | +| II.1 | Introduction ..... | 77 | +| II.2 | Overview of ITU-T H.248 statistics ..... | 77 | +| II.3 | Mapping statistics on the IP-to-IP interworking model ..... | 79 | +| | Appendix III – Differences between [ETSI ES 283 018] and this Recommendation ..... | 80 | +| | Bibliography..... | 84 | + + + +## Recommendation ITU-T Q.3303.2 + +## Resource control protocol No. 3 – Protocol at the interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE) (Rw interface): ITU-T H.248 alternative version 2 + +# 1 Scope + +This Recommendation provides the stage 3 technical specifications for the ITU-T H.248 profile of the Rw interface. The functional requirements and the stage 2 specifications of the Rw interface are contained in [ITU-T Y.2111]. The Rw interface is the interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. +- [ITU-T H.248.4] Recommendation ITU-T H.248.4 (2009), *Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP)*. +- [ITU-T H.248.8] Recommendation ITU-T H.248.8 (2013), *Gateway control protocol: Error code and service change reason description*. +- [ITU-T H.248.11] Recommendation ITU-T H.248.11 (2013), *Gateway control protocol: Media gateway overload control package*. +- [ITU-T H.248.14] Recommendation ITU-T H.248.14 (2009), *Gateway control protocol: Inactivity timer package*. +- [ITU-T H.248.36] Recommendation ITU-T H.248.36 (2013), *Gateway control protocol: Hanging Termination Detection package*. +- [ITU-T H.248.37] Recommendation ITU-T H.248.37 (2008), *Gateway control protocol: IP NAPT traversal package*. +- [ITU-T H.248.40] Recommendation ITU-T H.248.40 (2013), *Gateway control protocol: Application data inactivity detection package*. +- [ITU-T H.248.41] Recommendation ITU-T H.248.41 (2013), *Gateway control protocol: IP domain connection package*. +- [ITU-T H.248.43] Recommendation ITU-T H.248.43 (2008), *Gateway control protocol: Packages for gate management and gate control*. +- [ITU-T H.248.45] Recommendation ITU-T H.248.45 (2006), *Gateway control protocol: MGC information package*. +- [ITU-T H.248.47] Recommendation ITU-T H.248.47 (2008), *Gateway control protocol: Statistic conditional reporting package*. + +| | | +|------------------|------------------------------------------------------------------------------------------------------------------------------------| +| [ITU-T H.248.48] | Recommendation ITU-T H.248.48 (2008), Gateway control protocol: Statistic conditional reporting package. | +| [ITU-T H.248.49] | Recommendation ITU-T H.248.49 (2007), Gateway control protocol: Session description protocol RFC and capabilities packages. | +| [ITU-T H.248.52] | Recommendation ITU-T H.248.52 (2008) Amendment 1 (2009), Gateway control protocol: QoS Support packages. | +| [ITU-T H.248.53] | Recommendation ITU-T H.248.53 (2009), Gateway control protocol: Traffic Management packages. | +| [ITU-T H.248.54] | Recommendation ITU-T H.248.54 (2007), Gateway control protocol: MPLS support package. | +| [ITU-T H.248.55] | Recommendation ITU-T H.248.55 (2008), Gateway control protocol: Generic pull mode package. | +| [ITU-T H.248.56] | Recommendation ITU-T H.248.56 (2007), Gateway control protocol: Packages for virtual private network support. | +| [ITU-T H.248.57] | Recommendation ITU-T H.248.57 (2013), Gateway control protocol: RTP control protocol package. | +| [ITU-T H.248.58] | Recommendation ITU-T H.248.58 (2008), Gateway control protocol: Packages for application level H.248 statistics. | +| [ITU-T H.248.65] | Recommendation ITU-T H.248.65 (2009) Gateway control protocol: Support of the resource reservation protocol. | +| [ITU-T Y.2012] | Recommendation ITU-T Y.2012 (2010), Functional requirements and architecture of next generation networks I. | +| [ITU-T Y.2111] | Recommendation ITU-T Y.2111 (2011), Resource and admission control functions in next generation networks. | +| [IETF RFC 1123] | IETF RFC 1123 (1989), Requirements for Internet Hosts -- Application and Support. | +| [IETF RFC 3264] | IETF RFC 3264 (2002), An Offer/Answer Model with Session Description Protocol (SDP). | +| [IETF RFC 4566] | IETF RFC 4566 (2006), SDP: Session Description Protocol. | +| [IETF RFC 5234] | IETF RFC 5234 (2008), Augmented BNF for Syntax Specifications: ABNF. | + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 gate:** A construct used to enable or disable the forwarding of IP packets based on the policy decision. A gate is identified by the classifier (e.g., IPv4 5-tuple) and direction of a media flow or a group of media flows that in conformance to the same set of policy decisions. + +NOTE – The ITU-T H.248 gate (and pinhole) concept is depicted in Annex A of [b-ETSI ES 283 018]. + +**3.2.2 gate control:** The operation of opening or closing a gate. When a gate is open, the packets in the media flows are allowed to pass through; when a gate is closed, the packets in the media flows are not allowed to pass through. + +**3.2.3 IP-to-IP interworking modes:** The available session description protocol (SDP) information elements and values in the signalled SDP "media description" (mainly "m=" and "a=" lines) by the policy decision entity (MGC), may be used to categorize following interworking modes from policy enforcement entity (MG) perspective: + +- (1) **"Media-agnostic":** the "m=" line values of *media type* () and *media format* () are not allowing to terminate the PE-PE (MG) on the transported "media" information. +- (2) **"Media-aware":** the "m=" line values of *media type* (), *transport protocol* () and *media format* () unambiguously define the entire protocol stack of the ITU-T H.248 IP termination, i.e., the PE-PE (MG) is cognizant of transported "media" information and the underlying transport protocol type. +- (3) **"Transport protocol-agnostic" (or briefly "transport-agnostic"):** the PE-PE (MG) may not conclude from signalled SDP information elements on the transported IP payload information (Note 1). +- (4) **"Transport protocol-aware" (or briefly "transport-aware"):** the value of the IP *protocol* field is indicated by the signalled SDP information elements, e.g., by the "m=" line value of the *transport protocol* () field. + +NOTE – The PE-PE (MG) could principally derive the used transport protocol by analysing the protocol field () in the IP header, but such a function is beyond ITU-T H.248. The PE-PE (MG) is still transport protocol-agnostic from ITU-T H.248 point of view. + +**3.2.4 media flow:** A unidirectional media stream, which is specified by two endpoint identifiers and bandwidth, as well as class of service if needed. + +**3.2.5 pinhole:** Configuration of two associated ITU-T H.248 IP terminations within the same ITU-T H.248 context, which allows and prohibits unidirectional forwarding of IP packets under specified conditions. + +NOTE 1 – A pinhole may also be referred to as a "gate". + +NOTE 2 – E.g., address tuple. + +NOTE 3 – See [ITU-T H.248.37]. + +**3.2.6 policy decision physical entity (PD-PE):** The PD-PE is an implemented instance of the policy decision functional entity (PD-FE) as identified in [ITU-T Y.2111]. + +**3.2.7 policy enforcement physical entity (PE-PE):** The PE-PE is an implemented instance of the policy enforcement functional entity (PE-FE) as identified in [ITU-T Y.2111]. + +**3.2.8 transcoding:** Translation from one type of encoded media format to another media format (examples: G.711 A-law to $\mu$ -law or vice versa; ITU-T G.711 to ITU-T G.726-40K; ITU-T G.729 to adaptive multi-rate (AMR) with 4.75 rate; ITU-T G.711 to a broadband codec that operates at 256 kbps, etc.). + +NOTE – The definition of 'transcoding' is based on the definition in clause 3 of [b-ITU-T V.152]. + +Transcoding belongs to the category of "media aware" IP-to-IP interworking (see above). + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +ABNF      Augmented Backus-Naur Form + +AC          Admission Control + +| | | +|----------|-------------------------------------------| +| AH | Authentication Header | +| AMR | Adaptive Multi-Rate | +| API | Application Programming Interface | +| AVP | Attribute-Value Pair | +| B2BIH | Back-to-Back IP Host | +| B2BRE | Back-to-Back RTP Endsystem | +| BGF | Gateway Function | +| BGW | Border Gateway | +| CBR | Constant Bit Rate | +| CNAME | Canonical Name | +| CoAC | Context Admission Control | +| CPE | Customer Premises Equipment | +| DiffServ | Differentiated Services | +| ESP | Encapsulation Security Payload | +| GoS | Grade of Service | +| HW | Hardware | +| ID | Identifier | +| IBCF | Interconnection Border Control Function | +| ICMP | Internet control message protocol | +| IEPS | International Emergency Preference Scheme | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| IPR | IP Router | +| IPsec | IP security | +| LAN | Local Area Network | +| LCD | LocalControl Descriptor | +| LD | Local Descriptor | +| LSP | Label Switched Path | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MIB | Management Information Base | +| MID | Message Identifier (ITU-T H.248) | +| MPLS | Multi-Protocol Label Switching | +| NAPT | Network Address and Port Translation | +| NAPT-PT | NAPT and Protocol Translation | +| NAT | Network Address Translation | +| PCI | Protocol Control Information | + +| | | +|---------|--------------------------------------| +| PD-PE | Policy Decision Physical Entity | +| PDU | Protocol Data Unit | +| PE-PE | Policy Enforcement Physical Entity | +| PHB | Per-Hop Behaviour | +| QoS | Quality of Service | +| RD | Remote Descriptor | +| RP | Reporting Point | +| RSVP | Resource Reservation Protocol | +| RTCP | RTP Control Protocol | +| RTCP XR | RTP Control Protocol extended Report | +| RTP | Real-time Transport Protocol | +| SCF | Service Control Functions | +| SCTP | Stream Control Transmission Protocol | +| SDES | Source Description | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| SLA | Service Level Agreement | +| SNMP | Simple Network Management Protocol | +| SPDF | Service Policy Decision Function | +| SRTP | Secure RTP | +| StAC | Stream Admission Control | +| SSRC | Synchronization Source | +| THF | Topology Hiding Function | +| THIG | Topology Hiding Gateway | +| TLS | Transport Level Security | +| TTL | Time-To-Live | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| VBR | Variable Bit Rate | +| VLAN | Virtual LAN | +| VPN | Virtual Private Network | +| XR | Extended Report | + +# 5 Conventions + +None. + +# 6 Rw interface protocol specification (ITU-T H.248 profile description) + +The protocol specification relates to the definition of an ITU-T H.248 profile applicable for use at an ITU-T H.248-based Rw interface. The profile concept is inherently part of ITU-T H.248 (see clause 13 of [ITU-T H.248.1]). This profile is based on [b-ETSI TS 183 018] and follows the same structure (which is in line with the profile definition template according to Appendix III of [ITU-T H.248.1]). + +The PD-PE has the "H.248 MGC" role in the scope of this ITU-T H.248 profile. + +NOTE 1 – The function of PD-PE corresponds to the service policy decision function (SPDF) in [b-ETSI TS 183 018]. + +The PE-PE has the "H.248 MG" role in the scope of this ITU-T H.248 profile. + +NOTE 2 – The function of PE-PD corresponds to the border gateway function (BGF) in [b-ETSI TS 183 018]. + +## 6.1 Profile identification + +**Table 6-1 – Profile identification** + +| | | +|----------------------|------------------| +| Profile name: | ITU_PE-PE | +| Version: | 2 | + +This ITU-T H.248 Profile for Rw interface is based on Profile "ETSI\_BGF/3" as defined in [b-ETSI TS 183 018]. + +## 6.2 Gateway control protocol version + +Recommendation ITU-T H.248.1 Version 3 should be applied to the Rw interface. + +NOTE – Version 3 of the ITU-T H.248 protocol is needed, due to the possible usage of stream statistics and large size user datagram protocol (UDP) payload. + +## 6.3 Connection model + +**Table 6-2 – Connection model** + +| | | +|---------------------------------------------------|-------------| +| Maximum number of contexts | Provisioned | +| Maximum number of terminations per context | At least 2 | +| Allowed terminations type combinations | (IP, IP) | + +## 6.4 Context attributes + +**Table 6-3 – Context attributes** + +| Context attribute | Supported | Values supported | +|------------------------------------|------------------|-------------------------| +| Topology | No | NA | +| Priority indicator | Yes | 0-15 | +| Emergency indicator | Yes | ON/OFF | +| IEPS indicator | No | NA | +| ContextAttribute descriptor | No | NA | +| ContextIdList parameter | No | NA | +| AND/OR context attribute | No | NA | + +## 6.5 Terminations + +### 6.5.1 Termination names + +#### 6.5.1.1 IP termination + +##### 6.5.1.1.1 Overview and prose specification + +The TerminationID structure shall follow the guidelines of ITU-T H.248 and shall be based on four fields: + +- "ip///". + +The individual fields are described and defined in Table 6-4. + +**Table 6-4 – IP termination fields** + +| Name | Description | Values | CHOOSE wildcard | ALL wildcard | +|-----------|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------------|--------------| +| Ip | 'ip' is a fixed prefix identifying the termination | 'ip' | No | No | +| Group | Group of Interface and Id | Integer (0-65 535) | No | Yes | +| Interface | Logical or physical interface to a network to/from which the termination will be sending/receiving media (Notes 1 and 2). | String of maximum 51 alphanumeric characters | Yes
(Note 5) | Yes | +| Id | Termination specific identifier (Note 3) | Non-zero 32-bit integer | Yes
(Note 4) | Yes | + +NOTE 1 – A specific may be used together with different groups. + +NOTE 2 – The generic field may relate specifically to an "IP interface", "protocol layer 2 interface" or others. + +NOTE 3 – The combination of Interface and Id is unique. + +NOTE 4 – In version 1 of this profile, there was a tacit assumption that the media gateway controller (MGC) used a CHOOSE wildcard in an ADD request command. In this version, the MGC shall always use CHOOSE in an ADD request command. If not, the media gateway (MG) shall reply with an error descriptor using error code #501 "Not Implemented". See also clause 6.5.1.1.1.3. + +NOTE 5 – The MGC shall always use CHOOSE in an ADD request command. If not, the MG shall reply with an error descriptor using error code #501 "Not Implemented". + +NOTE – A specific address space may be associated with each interface or group of interfaces. In such cases, by specifying a partially wildcarded TerminationID in an ADD command, the PD-PE has the ability to choose the address space in which the PE-PE will allocate an IP address for the termination (e.g., ip///\$). The association of a TerminationID with a dedicated address space is related to "IP domain indication", which is also provided by the ipdc/realm property, see clause 6.16.1.7. + +ITU-T H.248 wildcarding may be applied on IP termination identifiers. Wildcarding is limited according to the two columns on the right hand side. + +###### 6.5.1.1.1 Combined usage of fields group and interface + +There are two potential relationships between and within the TerminationID structure (see Figure 6-1): + +- strictly hierarchical*: a single "interface" is completely associated to a dedicated "group" e.g., may be driven for instance by hardware architecture or addressing schemes with the goal of minimizing ServiceChange command load by using wildcards such as ip//\* for potential hardware (HW) failures that may lead to issuing a single ServiceChange command rather than multiple ServiceChange commands. + +- b) *partially hierarchical*: an "interface" is distributed over multiple "groups" + e.g., A logical partition concept may be driven for instance for selective auditing with the goal of minimizing the AuditReply to be of a manageable size by having the MGC to allocate an adequate number of terminations within a . Therefore, audits could be paced for example: ip/1/\*, ip/2/\*, ..., ip/n/\*. + +![Diagram illustrating Group/Interface relationships for the structure of terminationIDs. It shows two structures: (A) Strict hierarchical structure and (B) Partial hierarchical structure. Both show an IP block connected to multiple Groups, which are then connected to multiple Interfaces, each with an ID. In (A), the hierarchy is strict. In (B), the hierarchy is partial, with multiple groups sharing a single interface.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +Ip/// + +(A) Strict hierarchical structure + +(B) Partial hierarchical structure + +Q.3303.2 v2(14)\_F6-1 + +Diagram illustrating Group/Interface relationships for the structure of terminationIDs. It shows two structures: (A) Strict hierarchical structure and (B) Partial hierarchical structure. Both show an IP block connected to multiple Groups, which are then connected to multiple Interfaces, each with an ID. In (A), the hierarchy is strict. In (B), the hierarchy is partial, with multiple groups sharing a single interface. + +**Figure 6-1 – Group/Interface relationships for the structure of terminationIDs** + +The following examples in Tables 6-5 and 6-6 depict the advantages that each group/interface relationship may facilitate. + +**Table 6-5 – Examples of group/interface relationship in ServiceChange** + +| Semantic of termination name | ServiceChange command (e.g., due to a HW failure) | | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Strictly hierarchical | Upon a HW failure the command issued is (by MG):
ServiceChange=ip/1/*{Services{Method=Restart,Reason="906"Version=3,Profile = ITU_PE-PE_2}}},
a single wildcarded command is possible (facilitated by a strict hierarchical relationship). | | +| Partially hierarchical | Upon a HW failure the command issued is (by MG):
ServiceChange=ip/*/1/*{Services{Method=Forced,Reason="906" }},
ServiceChange=ip/*/2/*{Services{Method=Forced,Reason="906" }},
...
ServiceChange=ip/*/x/*{Services{Method=Forced,Reason="906" }},
... a single wildcarded command is not always possible when not using a strict hierarchical relationship | | + +**Table 6-6 – Examples of termination ID usage in AuditValue** + +| Usage of termination ID structure | AuditValue command
(e.g., Requesting a list of context IDs present in the MG where n and N are number of contexts in the AuditValue replies and n<<N) | +|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Neither group nor interface levels specified in request |

The command (from MGC):

Context=*{AuditValue=Root{Audit{}}}

Returns:

Context=1{AuditValue=ip/1/11/101{},AuditValue=ip/1/12/102{}},
Context=2{AuditValue=ip/1/21/201{},AuditValue=ip/1/22/202{}},
Context=3{AuditValue=ip/1/31/301{},AuditValue=ip/1/32/302{}},
...
Context=N{AuditValue=ip/256/11/504{},AuditValue=ip/256/12/534{}}

... this could potentially return very large AuditValue Replies.

| +| Group level specified in request |

The command (by MGC):

Context=*{AuditValue=ip/1/*{Audit{}}}

Returns:

Context=1{AuditValue=ip/1/11/101{},AuditValue=ip/1/12/102{}},
...
Context=n{AuditValue=ip/1/51/121{},AuditValue=ip/1/52/122{}}

... and this command would be repeated for each group.
(facilitated by loose hierarchical relationship).

| + +###### **6.5.1.1.1.2 Optimization of call-independent procedures** + +The CHOOSE wildcard for "Interface" is introduced by this version of the profile. + +The MGC may optimize (Note 1) call-independent procedures, e.g., based on the AuditValue command, by fully controlling the value allocation for the field Group. + +NOTE 1 – "Optimization" could e.g., mean a load shaping function concerning ITU-T H.248 processing load. + +The MG may optimize (Note 2) call-independent procedures, e.g., based on the ServiceChange command, via full control over the value allocation for field Interface. + +NOTE 2 – "Optimization" may allow single wildcarded commands, see discussion in Tables 6-5 and 6-6. + +###### **6.5.1.1.1.3 Field "Id": Usage of wildcard CHOOSE or not** + +The CHOOSE wildcard for "Id" must be applied in the ADD.request command. It is the MGs responsibility for managing the value range of this logical resource. + +##### 6.5.1.1.2 Syntactical specification + +###### 6.5.1.1.2.1 ABNF grammar for ITU-T H.248 text encoding mode + +Augmented Backus-Naur form (ABNF) [IETF RFC 5234] is used for the syntax specification. The ABNF for TerminationID and relation to pathNAME is defined in Annex B.2 of [ITU-T H.248.1]. + +ABNF coding: + +``` +pathNAME = EphToken SLASH EPHsystem +EphToken = "ip" ; prefix +EPHsystem = WildcardALL + / WildcardALL SLASH Interface + / Group SLASH WildcardALL + / Group SLASH Interface SLASH (Identifier/ + WildcardALL/WildcardCHOOSE) +Group = %d0-65535 ; data type: INT16 +Interface = 1*51ALPHANUM +Identifier = %d1-4294967295 ; data type: INT32 +ALPHANUM = ALPHA/DIGIT +WildcardCHOOSE = "$" +WildcardALL = "*" +``` + +#### 6.5.2 Multiplexed terminations + +Table 6-7 – Multiplexed terminations + +| | | +|-----------------------------------------|----| +| MultiplexTerminations supported? | No | +|-----------------------------------------|----| + +## 6.6 Descriptors + +#### 6.6.1 TerminationState Descriptor + +Table 6-8 – ServiceState property + +| | | +|------------------------------------|----| +| ServiceState property used: | No | +|------------------------------------|----| + +NOTE 1 – All ITU-T H.248 Terminations have a ServiceState property according to [ITU-T H.248.1], but explicit usage of the TerminationState Descriptor ServiceState property is not required by this profile. ServiceState changes can still occur, however, and be indicated in ServiceChange commands. + +NOTE 2 – The value of the ServiceState property may be implicitly changed by ServiceChange procedures, or the value may be read by audit procedures, i.e., "Yes" for ServiceStates "InService" and "OutOfService" due to AuditValue and ServiceChange commands or "No" for ServiceState "Test". + +Table 6-9 – EventBufferControl property + +| | | +|------------------------------------------|----| +| EventBufferControl property used: | No | +|------------------------------------------|----| + +### 6.6.2 Stream Descriptor + +Table 6-10 – Stream Descriptor + +| | | | +|-------------------------------------------------------|----|---| +| Maximum number of streams per termination type | IP | 5 | +|-------------------------------------------------------|----|---| + +Table 6-11 – Stream configuration + +| | | +|-----------------------------|---------------------------------| +| Stream configuration | All configurations are allowed. | +|-----------------------------|---------------------------------| + +#### 6.6.2.1 LocalControl Descriptor (LCD) + +**Table 6-12 – LocalControl Descriptor** + +| If not generic list appropriate termination and stream types | | Termination type | Stream type | +|--------------------------------------------------------------|----|------------------|-------------| +| ReserveGroup used | No | – | – | +| ReserveValue used | No | – | – | + +**Table 6-13 – Termination type** + +| Termination type | Stream type | Allowed StreamMode values | +|--------------------------------------------------|-------------|----------------------------------------| +| IP | RTP/AVP | SendOnly, RecvOnly, SendRecv, Inactive | +| | TCP | SendRecv, Inactive | +| | UDPTL | SendRecv, Inactive | +| | UDP | SendOnly, RecvOnly, SendRecvInactive | +| NOTE – Other stream types are for further study. | | | + +### 6.6.3 Events Descriptor + +**Table 6-14 – Events Descriptor** + +| Events that can be set based on termination types and stream types | Yes | | | +|--------------------------------------------------------------------|-----------------------------------------------------|------------------|----------------| +| | Event ID | Termination type | Stream type | +| If Yes | See clause 6.13.2.1
• g/cause | All except ROOT | Any | +| | See clause 6.13.2.3
• nt/netfail
• nt/qualert | All except ROOT | Any | +| | See clause 6.13.2.11
• it/ito | Only ROOT | Not applicable | +| | See clause 6.13.2.16
• adid/ipstop | All except ROOT | Any | +| | See clause 6.13.2.14
• ocp/mg_overload | Only ROOT | Not applicable | +| | See clause 6.13.2.17
• hangterm/thb | All except ROOT | Not applicable | +| | See clause 6.13.2.18
• scr/cr | All except ROOT | Not applicable | +| | See clause 6.13.2.1
• ipra/arc | Only ROOT | Not applicable | +| | | | | + +**Table 6-15 – EventBuffer control** + +| | | +|---------------------------------|----| +| EventBuffer control used | No | +|---------------------------------|----| + +**Table 6-16 – KeepActive** + +| | | +|----------------------------------|----| +| KeepActive used on events | No | +|----------------------------------|----| + +**Table 6-17 – Embedded events and signals** + +| | | +|-------------------------------------------------|----| +| Embedded events in an Events Descriptor | No | +| Embedded signals in an Events Descriptor | No | + +**Table 6-18 – Regulated embedded events** + +| | | +|---------------------------------------------------|------| +| Regulated embedded events are triggered on | None | +|---------------------------------------------------|------| + +**Table 6-19 – ResetEventsDescriptor** + +| | | +|-----------------------------------------------|------| +| ResetEventsDescriptor used with events | None | +|-----------------------------------------------|------| + +**Table 6-20 – NotifyImmediate, NotifyRegulated and NeverNotify** + +| | | +|------------------------|------------| +| NotifyImmediate | All events | +| NotifyRegulated | None | +| NeverNotify | None | + +### 6.6.4 EventBuffer Descriptor + +**Table 6-21 – EventBuffer Descriptor** + +| | | +|------------------------------------|----| +| EventBuffer Descriptor used | No | +|------------------------------------|----| + +### 6.6.5 Signals Descriptor + +**Table 6-22 – Signals Descriptor** + +| | | | | +|----------------------------------------------------------------------------------|------------------|-------------------------|-----------------------| +| Signals that can be set and are dependent on termination or streams types | Yes | | | +| If yes | Signal ID | Termination type | Stream type/ID | +| | ipnapt/* | All except ROOT | Any | + +**Table 6-23 – Signals lists** + +| | | +|--------------------------------|----| +| Signals lists supported | No | +|--------------------------------|----| + +**Table 6-24 – Signals type and duration** + +| | | +|-------------------------------------------|----| +| Signal type and duration supported | No | +|-------------------------------------------|----| + +**Table 6-25 – Signals direction** + +| | | +|-----------------------------------|----| +| Signal direction supported | No | +|-----------------------------------|----| + +**Table 6-26 – NotifyCompletion and RequestID** + +| | | +|--------------------------------------|----| +| NotifyCompletion supported | No | +| RequestID parameter supported | No | + +**Table 6-27 – Simultaneously played signals** + +| | | +|--------------------------------------|----| +| Signals played simultaneously | No | +|--------------------------------------|----| + +**Table 6-28 – KeepActive** + +| | | +|-----------------------------------|----| +| KeepActive used on signals | No | +|-----------------------------------|----| + +#### **6.6.6 DigitMap Descriptor** + +**Table 6-29 – DigitMap Descriptor** + +| | | +|----------------------------|----| +| DigitMaps supported | No | +|----------------------------|----| + +#### **6.6.7 Statistics Descriptor** + +**Table 6-30 – Statistics Descriptor** + +| | | +|--------------------------------|--------| +| Statistics supported on | Stream | +|--------------------------------|--------| + +**Table 6-31 – Statistics reported on subtract** + +| | | | +|----------------------------------------|-------------------------------|--------------------------------------| +| Statistics reported on subtract | Yes | | +| If yes | Statistic IDs reported | All
(see clause 6.13 for details) | + +### **6.6.8 ObservedEvents Descriptor** + +**Table 6-32 – ObservedEvents Descriptor** + +| | | +|---------------------------------------|----| +| Event detection time supported | No | +|---------------------------------------|----| + +### **6.6.9 Topology Descriptor** + +**Table 6-33 – Topology Descriptor** + +| | | +|------------------------|-----------------| +| Allowed triples | Not applicable. | +|------------------------|-----------------| + +#### 6.6.10 Error Descriptor + +**Table 6-34 – Error codes sent by MGC** + +| | | +|--------------------------------------------------|---------------------------------------------------------------------| +| Supported ITU-T H.248.8 error codes | All | +| Supported error codes defined in packages | All error codes defined in supported packages need to be supported. | + +**Table 6-35 – Error codes sent by MG** + +| | | +|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported ITU-T H.248.8 error codes | All
with exception of
  • #514 "Media gateway cannot send the specified announcement"
  • #518 "Event buffer full"
  • #519 "Out of space to store digit map"
  • #520 "Digit map undefined in the MG"
  • #522 "Functionality requested in topology triple not supported"
| +| Supported error codes defined in packages | All error codes defined in supported packages need to be supported. | + +## 6.7 Command API + +Introductory note: + +Tables 6-36 to 6-38 provide a summary overview of clauses 6.6 and 6.7 concerning descriptors and commands respectively. Where there are discrepancies between these tables and the corresponding text in clauses 6.6 and 6.7, the text takes precedence over those described in these tables. + +Table 6-36 shows in which direction commands are sent, with which terminations they can be associated with and which wildcard options are supported for the specific command. + +**Table 6-36 – Commands and terminations** + +| Command | Sent by | Used on termination type | | Wildcard support | | +|----------------------------------------------------------|---------|--------------------------|------|------------------|-----| +| | | IP | ROOT | W– | O– | +| Add | PD–PE | Yes | No | No | No | +| AuditCapabilities | – | – | – | – | – | +| AuditValue | PD–PE | Yes | Yes | No | Yes | +| Modify | PD–PE | Yes | Yes | No | No | +| Move | – | – | – | – | – | +| Notify | PE–PE | Yes | Yes | No | No | +| ServiceChange | PE–PE | Yes | Yes | No | No | +| Subtract | PD–PE | Yes | No | Yes | No | +| NOTE 1 – O– indicates an optional command | | | | | | +| NOTE 2 – W– indicates a wildcarded response to a command | | | | | | + +Table 6-36 shows for which termination types a specific descriptor can be applied and Tables 6-37 and 6-38 show with which commands and replies the descriptor can be used, respectively. + +**Table 6-37 – Descriptors and requests** + +| Descriptor type
(Note 1) | Termination type | | | | | | | | +|-----------------------------|------------------|-----|--|--|--|--|-----|--| +| | Root | IP | | | | | | | +| Audit | Yes | Yes | | | | | | | +| Error | | | | | | | | | +| Events | Yes | Yes | | | | | | | +| Local | | Yes | | | | | | | +| LocalControl | | Yes | | | | | | | +| Media | Yes
(Note 2) | Yes | | | | | | | +| ObservedEvents | Yes | Yes | | | | | | | +| Packages | Yes | | | | | | | | +| ServiceChange | Yes | Yes | | | | | Yes | | +| Signals | | Yes | | | | | | | +| Statistics | | Yes | | | | | | | +| Stream | | Yes | | | | | | | +| TerminationState | Yes
(Note 2) | | | | | | | | + +NOTE 1 – Only ITU-T H.248 descriptors supported within this ITU-T H.248 profile specification are shown. +NOTE 2 – E.g., Base Root package properties. + +**Table 6-38 – Descriptors and replies** + +| Descriptor type
(Note 1) | Termination type | | Add | | | | | | +|-----------------------------|------------------|-----|-----|--|--|--|--|--| +| | Root | IP | | | | | | | +| Audit | | | | | | | | | +| Error | Yes | Yes | | | | | | | +| Events | Yes | Yes | | | | | | | +| Local | | | | | | | | | +| LocalControl
(Note 2) | | Yes | | | | | | | +| Media | Yes | Yes | | | | | | | +| ObservedEvents | | | | | | | | | +| Packages | Yes | | | | | | | | +| Remote | | | | | | | | | +| ServiceChange | Yes | Yes | | | | | | | +| Signals (Note 3) | | | | | | | | | + +**Table 6-38 – Descriptors and replies** + +| Descriptor type
(Note 1) | Termination type | | Add | | | | | | +|-----------------------------|------------------|-----|-----|--|--|--|--|--| +| | Root | IP | | | | | | | +| Statistics | | Yes | | | | | | | +| Stream | | Yes | | | | | | | +| TerminationState | Yes | | | | | | | | + +NOTE 1 – Only ITU-T H.248 descriptors supported within this ITU-T H.248 profile specification are shown. +NOTE 2 – According to clause 6.7.5, **auditing** of mgcinfo/db ITU-T H.248 property in LocalControl is required. +NOTE 3 – According to clause 6.7.5, **auditing** of ITU-T H.248 signals descriptors is not required. + +It is seen that an Error Descriptor may be returned in any command reply and thus the Error Descriptor is not included in any subsequent command reply table. + +### 6.7.1 Add + +**Table 6-39 – Descriptors used by Add request** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| Descriptors used by Add request | Media (Stream(LocalControl, Statistics, Local, Remote)), Event, Signals | +| NOTE – Statistics are enabled by default. The MGC may explicitly request or suppress statistics generation for individual streams or terminations by inclusion of the Statistics Descriptor in the Add request command (see clause 7.1.15 of [ITU-T H.248.1]). | | + +**Table 6-40 – Descriptors used by Add reply** + +| | | +|--------------------------------------|-----------------------| +| Descriptors used by Add reply | Media (Stream(Local)) | +|--------------------------------------|-----------------------| + +### 6.7.2 Modify + +**Table 6-41 – Descriptors used by Modify request** + +| | | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Modify request | Media (TerminationState, Stream(LocalControl, statistics, Local, Remote)),
Audit(Media(Stream(Statistics))), Signals, Event | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| + +**Table 6-42 – Descriptors used by Modify reply** + +| | | +|-----------------------------------------|---------------------------------| +| Descriptors used by Modify reply | Media(Stream(Local Statistics)) | +|-----------------------------------------|---------------------------------| + +### 6.7.3 Subtract + +**Table 6-43 – Descriptors used by Subtract request** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| Descriptors used by Subtract request | Audit () OR NONE | +| NOTE – This profile version supports reporting of statistics on all streams or none of the streams. Reporting and disabling of statistics from a subset of the streams in case of multiple streams is not supported by this profile version. Termination level statistics are not supported. | | + +**Table 6-44 – Descriptors used by Subtract reply** + +| | | +|-------------------------------------------|-----------------------------------| +| Descriptors used by Subtract reply | Media(Stream(Statistics)) or None | +|-------------------------------------------|-----------------------------------| + +### **6.7.4 Move** + +**Table 6-45 – Descriptors used by Move command** + +| | | +|--------------------------|----| +| Move command used | No | +|--------------------------|----| + +### **6.7.5 AuditValue** + +**Table 6-46 –AuditValue** + +| | | +|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| Audited properties | Media(Termination state) (Note 1)
Media(Stream(local control)) (Note 2) | +| Audited statistics | All | +| Audited signals | None | +| Audited events: | None | +| Packages audit possible | Yes | +| NOTE 1 – These are the root/*, seg/* and ipra/* properties.
NOTE 2 – This is the mgcininfo/db property. | | + +### **6.7.6 AuditCapabilities** + +**Table 6-47 – Descriptors used by AuditCapabilities command** + +| | | +|---------------------------------------|----| +| AuditCapabilities command used | No | +|---------------------------------------|----| + +### **6.7.7 Notify** + +**Table 6-48 – Descriptors used by Notify request** + +| | | +|-------------------------------------------|----------------| +| Descriptors used by Notify request | ObservedEvents | +|-------------------------------------------|----------------| + +**Table 6-49 – Descriptors used by Notify reply** + +| | | +|-----------------------------------------|------| +| Descriptors used by Notify reply | None | +|-----------------------------------------|------| + +### **6.7.8 ServiceChange** + +**Table 6-50 – ServiceChangeMethods and ServiceChangeReasons sent by MGC** + +| Service change methods supported | ServiceChange reasons supported | +|-----------------------------------------|----------------------------------------| +| Restart | 900, 901 | +| Handoff | 903 | + +**Table 6-51 – ServiceChangeMethods and ServiceChangeReasons sent by MG** + +| Service change methods supported | ServiceChange reasons supported | +|-----------------------------------------|----------------------------------------| +| Restart | 900, 901, 902 | +| Forced | 904, 905, 906, 915 | +| Disconnected | 900 | +| Graceful | 905, 908 | +| Failover | 909 | +| Handoff | 903 | + +**Table 6-52 – ServiceChangeAddress** + +| | | +|----------------------------------|----| +| ServiceChangeAddress used | No | +|----------------------------------|----| + +**Table 6-53 – ServiceChangeDelay** + +| | | | +|--------------------------------|-------------------|-------------| +| ServiceChangeDelay used | Yes | | +| If yes | Valid time period | Provisioned | + +**Table 6-54 – ServiceChange incomplete flag** + +| | | +|-------------------------------------------|----| +| ServiceChange incomplete flag used | No | +|-------------------------------------------|----| + +**Table 6-55 – ServiceChangeVersion** + +| | | +|---------------------------------------------|---| +| Version used in ServiceChangeVersion | 3 | +|---------------------------------------------|---| + +**Table 6-56 – Profile negotiation** + +| | | +|--------------------------------------------------|----| +| Profile negotiation as per ITU-T H.248.18 | No | +|--------------------------------------------------|----| + +**Table 6-57 – ServiceChangeMGCid** + +| | | +|--------------------------------|-----| +| ServiceChangeMGCid used | Yes | +|--------------------------------|-----| + +### 6.7.9 Manipulating and auditing context attributes + +**Table 6-58 – Context attributes manipulation and auditing** + +| | | +|---------------------------------------|---------------------| +| Context attributes manipulated | Emergency, Priority | +| Context attributes audited | None | + +## 6.8 Generic command syntax and encoding + +**Table 6-59 – Command encoding** + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Supported encodings | Text (Notes 1 and 2) | +| NOTE 1 – The receiver shall be capable of receiving both short token notation and long token notation on an ITU-T H.248 control association.
NOTE 2 – The transmitter may select between long and short token forms per ITU-T H.248 control association. | | + +## 6.9 Transactions + +**Table 6-60 – Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Replies per message** + +| | | +|----------------------------------------------------------------------------------------------|---| +| Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Replies per message | 1 | +|----------------------------------------------------------------------------------------------|---| + +**Table 6-61 – Maximum number of commands per Transaction request** + +| | | +|----------------------------------------------------|---| +| Maximum number of commands per Transaction request | 2 | +|----------------------------------------------------|---| + +**Table 6-62 – Maximum number of commands per Transaction reply** + +| | | +|--------------------------------------------------|---| +| Maximum number of commands per Transaction reply | 2 | +|--------------------------------------------------|---| + +**Table 6-63 – Optional commands** + +| | | +|---------------------------------------|------------| +| Commands able to be marked "Optional" | AuditValue | +|---------------------------------------|------------| + +**Table 6-64 – Wildcarded commands** + +| | | +|-----------------------------------------|----------| +| Commands able to be marked "Wildcarded" | Subtract | +|-----------------------------------------|----------| + +**Table 6-65 – Transaction timer** + +| Transaction timer | Value | +|-----------------------------------|--------------------------------------------------------------------| +| normalMGExecutionTime | Provisioned, changeable with Base Root package (see clause 6.13.2) | +| normalMGCExecutionTime | Provisioned, changeable with Base Root package (see clause 6.13.2) | +| MGOriginatedPendingLimit | Provisioned, changeable with Base Root package (see clause 6.13.2) | +| MGCOOriginatedPendingLimit | Provisioned, changeable with Base Root package (see clause 6.13.2) | +| MGProvisionalResponseTimerValue | Provisioned, changeable with Base Root package (see clause 6.13.2) | +| MGCPProvisionalResponseTimerValue | Provisioned, changeable with Base Root package (see clause 6.13.2) | + +## 6.10 Messages + +It is recommended that MGC and MG names are formatted as fully qualified domain names. For example the domain name of the MGC may be formatted as `mgc1.whatever.net` and the name of the MG may be formatted as `mg1.whatever.net`. + +The fully qualified domain name will be used by the MGC and MG as part of the "Message Identifier" in the ITU-T H.248 messages, which identifies the originator of the message. + +## 6.11 Transport + +**Table 6-66 – Transport** + +| | | +|-----------------------------|-----------------------------------| +| Supported transports | SCTP (Recommended) UDP (Optional) | +|-----------------------------|-----------------------------------| + +**Table 6-67 – Segmentation** + +| | | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Segmentation supported | SCTP:
Inherent in transport
UDP: Optional (dependent on support of Segmentation package, see clause 6.13.2.12) | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------| + +**Table 6-68 – Control association** + +| | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Control association monitoring supported: | Monitoring mechanism is dependent on used ITU-T H.248 transport (see Table 6-66):
SCTP:
Inherent capability of SCTP.
UDP:
ITU-T H.248.14 (MG-driven monitoring).
Empty AuditValue on ROOT (MGC-driven monitoring). | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 6.12 Security + +**Table 6-69 – Security** + +| | | +|---------------------------|------| +| Supported security | None | +|---------------------------|------| + +## 6.13 Packages + +This clause includes details of the mandatory and optional ITU-T H.248 packages that are included in this profile. A MG supporting this profile must support all the mandatory packages and may support zero, some or all of the optional packages. The MGC may use the ITU-T H.248 packages audit mechanism to determine which of the optional packages are supported by the MG. The meaning of mandatory and optional packages and their properties, signals, events, and statistics is provided in Appendix III of [ITU-T H.248.1]. + +### 6.13.1 Overview + +**Table 6-70 – Mandatory packages** + +| Mandatory packages | | | +|--------------------------------------------------|-------------------|----------------| +| Package name | Package ID | Version | +| Generic (clause E.1 of [ITU-T H.248.1]) | g | 2 | +| Base Root (clause E.2 of [ITU-T H.248.1]) | root | 2 | +| Network (clause E.11 of [ITU-T H.248.1]) | nt | 1 | +| Differentiated services [ITU-T H.248.52] | ds | 2 | +| Gate management (Appendix I of [ITU-T H.248.43]) | gm | 1 | +| Traffic management [ITU-T H.248.53] | tman | 1 | +| IP NAPT traversal [ITU-T H.248.37] | ipnapt | 1 | +| IP domain connection [ITU-T H.248.41] | ipdc | 1 | +| Generic pull mode package [ITU-T H.248.55] | plm | 1 | + +**Table 6-71 – Optional packages** + +| Optional packages | | | | +|--------------------------------------------------------|-------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Package name | Package ID | Version | Support dependent on | +| MPLS [ITU-T H.248.54] | mpls | 1 | Support for MPLS label stacks, i.e., label switched paths (LSPs) terminated by the MG and related to the ITU-T H.248 termination. | +| VLAN [ITU-T H.248.56] | vlan | 1 | Support for virtual LAN (VLAN) tags and/or Ethernet priorities. | +| MGC information [ITU-T H.248.45] | mgcinfo | 1 | Support for MGC related recovery. | +| Inactivity timer [ITU-T H.248.14] | it | 1 | Applicable only for UDP transport (because UDP does not support any inherent keep alive mechanism). | +| Segmentation (clause E.14 of [ITU-T H.248.1]) | seg | 1 | Applicable for UDP transport where sufficiently large messages are required to be supported. | +| RTP (clause E.12 of [ITU-T H.248.1]) | rtp | 1 | Support of usage metering and statistics reporting. Particular package capabilities are only applicable for "media-aware" bearer connections. | +| Media gateway overload control [ITU-T H.248.11] | ocp | 1 | Support of message throttling, based on rate limitation, from MGC towards MG | +| Application data inactivity detection [ITU-T H.248.40] | adid | 1 | MGC requires to be explicitly informed of a cessation of an application data flow. | + +**Table 6-71 – Optional packages** + +| Optional packages | | | | +|----------------------------------------------------------|-------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package name | Package ID | Version | Support dependent on | +| Hanging termination detection
[ITU-T H.248.36] | hangterm | 1 | Support of hanging termination detection | +| Statistics conditional reporting
[ITU-T H.248.47] | scr | 2 | Support of real time reporting of specific statistics based on a particular condition. This package may be supported as an operator option. | +| Gate management
[ITU-T H.248.43] | gm | 2 | Support of filtering based on source port range | +| IP realm availability
[ITU-T H.248.41] | ipra | 1 | Complements the IP domain connection package. Support of a mechanism allowing the MGC to discover the IP realms that are available at the MG at a certain time and on a mechanism allowing the MG to inform the MGC about change of availability of realms. | +| RTP application data package
[ITU-T H.248.58] | rtpad | 1 | Support of usage metering and statistics reporting.
Scope on traffic-volume based measurement of real-time transport protocol (RTP) application data (i.e., the media stream). | +| IP domain connectionLatch statistics
[ITU-T H.248.37] | ipdclstat | 1 | MGC to address specific IP realm
NOTE – Complements the IP NAPT traversal package to enable the recording of discarded packets due to implicit filtering by the latching function. | +| Traffic policing statistics
[ITU-T H.248.53] | tmanr | 2 | Complements the traffic management package, allowing the recording of the number of packets and octets that did not conform to the traffic parameters, and the number of packets that were dropped due to such violations. | +| RSVP extension package
[ITU-T H.248.65] | rsvp | 1 | Support of resource reservation protocol (RSVP) based on Pull mode resource control. | + +### 6.13.2 Package usage information + +##### 6.13.2.1 Generic (g) + +Table 6-72 – Generic package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | | | +|-----------------|------------------------------|--------------------|------------------|----------------------------|--|--| +| None | | | | | | | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | | | +| None | | | | | | | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | | | +| | | | | | | | +| Events | Mandatory/Optional | Used in command | | | | | +| Cause (g/cause) | M | ADD, NOTIFY | | | | | +| | Event parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | None. | | | | | | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | General cause (Generalcause) | M | All | Not applicable | | | +| | Failure cause (Failurecause) | M | All | Not applicable | | | +| Statistics | Mandatory/Optional | Used in command | Supported values | | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +#### 6.13.2.2 Base root (root) + +Table 6-73 – Base root package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | +|------------------------------------------------------------|--------------------|-----------------|------------------|-------------------| +| MaxNrOfContexts (root/maxNumber OfContexts) | O | AUDITVALUE | All | Yes | +| MaxTerminationsPerContext (root/maxTermination PerContext) | O | AUDITVALUE | All | Yes | + +**Table 6-73 – Base root package** + +| Properties | Mandatory/
Optional | Used in command | Supported
values | Provisioned
value | | | +|----------------------------------------------------------------------------------------|-------------------------------------|--------------------------------|-----------------------------|-------------------------------------------|--|--| +| normalMGExecutionTime
(root/normalMG
ExecutionTime) | O | MODIFY,
AUDITVALUE | All | Yes | | | +| normalMGCExecutionTime
(root/normalMGC
ExecutionTime) | O | MODIFY,
AUDITVALUE | All | Yes | | | +| MGProvisional
ResponseTimer Value
(root/MGProvisionalResponse
TimerValue) | O | MODIFY,
AUDITVALUE | All | Yes | | | +| MGCPProvisional
ResponseTimer Value
(root/MGCPProvisional
ResponseTimerValue) | O | MODIFY,
AUDITVALUE | All | Yes | | | +| MGCOriinatedPendingLimit
(root/MGCOriinated
PendingLimit) | O | MODIFY,
AUDITVALUE | All | Yes | | | +| MGOrriinatedPendingLimit
(root/MGOrriinated
PendingLimit) | O | MODIFY,
AUDITVALUE | All | Yes | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned
value | | | +| None | | | | | | | +| | Signal
parameters | Mandatory/
optional | Supported
values | Duration
provisioned
value | | | +| | | | | | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| None | | | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| Statistics | Mandatory/
Optional | Used in command | | Supported Values | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +#### 6.13.2.3 Network (nt) + +Table 6-74 – Network package + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | | | +|--------------------------------|-------------------------------------|-----------------------------------|-----------------------------|---------------------------------------|--|--| +| Maximum jitter buffer (nt/jit) | O | ADD, MODIFY | All | Yes | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned value | | | +| None | | | | | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned value | | | +| | | | | | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| Network failure (nt/netfail) | O | ADD, MODIFY, NOTIFY | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | None | – | – | – | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | Cause (cs) | O | For further study (Note) | For further study (Note) | | | +| Quality alert (nt/qualert) | O | ADD, MODIFY, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | Threshold (th) | O | All | Not applicable | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
Value: | | | +| | Threshold (th) | O | All | Not applicable | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| Duration (nt/dur) | O | ADD, SUBTRACT, MODIFY, AUDITVALUE | All | | | | +| Octets sent (nt/os) | M | ADD, SUBTRACT | All | | | | +| | O | MODIFY, AUDITVALUE | All | | | | +| Octets received (nt/or) | M | ADD, SUBTRACT | All | | | | +| | O | MODIFY, AUDITVALUE | All | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +**Table 6-74 – Network package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------|-------------------------|------------------------------| +| NOTE – This event may be overloaded in order to address multiple failure causes (see clause E.11.5.1.2 of [ITU-T H.248.1]). An unambiguous distinction on MGC and MG sides implies mutually agreed cause code points. This is a provisioning activity. | | | | | + +#### 6.13.2.4 Differentiated services (ds) + +**Table 6-75 – Differentiated services package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | | | +|----------------------------------------------|-------------------------------------|--------------------------------|-----------------------------|---------------------------------------|--|--| +| Differentiated services code point (ds/dscp) | M | ADD, MODIFY | All | Yes | | | +| Tagging behaviour (ds/tb) | O | ADD, MODIFY | All | Yes | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned value | | | +| None | | | | | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned value | | | +| | | | | | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| None | | | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +#### 6.13.2.5 Gate management (gm) + +Table 6-76 – Gate management package + +| Properties | Mandatory/
Optional | Used in
command | Supported
values | Provisioned value | +|--------------------------------------------|------------------------|------------------------|---------------------|----------------------------| +| Remote source address filtering (gm/saf) | M | ADD, MODIFY | All | Not applicable (Note 1) | +| Remote source address mask (gm/sam) | O | ADD, MODIFY | All | Not applicable | +| Remote source port filtering (gm/spf) | M | ADD, MODIFY | All | Note 1 | +| Remote source port (gm/spr) | O | ADD, MODIFY | All | Not applicable | +| Remote source port range (gm/spr) (Note 3) | O | ADD, MODIFY | All | Not applicable | +| Explicit source address setting (gm/esas) | O | ADD, MODIFY | All | (Note 1) | +| Local source address (gm/lsa) | O | ADD, MODIFY | All | Not applicable | +| Explicit source port setting (gm/esps) | O | ADD, MODIFY | All | (Note 1) | +| Local source port (gm/lsp) | O | ADD, MODIFY | All | Not applicable | +| RTP specific behaviour (gm/rsb) (Note 4) | M | ADD, MODIFY | All | OFF (Note 2) | +| Signals | Mandatory/
Optional | Used in command | | Duration provisioned value | +| None | – | – | | – | +| | Signal parameters | Mandatory/
Optional | Supported values | Duration provisioned value | +| | – | – | – | – | + +**Table 6-76 – Gate management package** + +| Events | Mandatory/
Optional | Used in command | | | | | +|-------------------------------|-----------------------------|--------------------------------------------|---------------------|-------------------|--|--| +| | | | | | | | +| None | – | – | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned value | | | +| | – | – | – | – | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned value | | | +| | – | – | – | – | | | +| Statistics | Mandatory/
Optional | Used in
command | Supported values | | | | +| Discarded
packets
gm/dp | O | ADD,
MODIFY,
SUBTRACT,
AUDITVALUE | All | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +NOTE 1 – Default value is 'OFF' in gm/1 (see clause B.2 of [ITU-T H.248.43]). + +NOTE 2 – Default value must be provisioned in gm/1 (see clause B.2 of [ITU-T H.248.43]). The provisioned value in this profile shall be OFF. + +NOTE3 – This property is defined in gm/2 while all other properties exist in gm/1. + +NOTE 4 – The *gm/rsb* property is identical to the *rtcph/rsb* property (see Figure II.1 in [ITU-T H.248.43]) and defined by [ITU-T H.248.57]. The *rtcph* package defines *rsb* property semantics for the session description protocol (SDP) attribute according to [b-IETF RFC 3605] (see in particular clause 6.6.1.4.1 of [ITU-T H.248.57]). There are following package usage details for this profile specification: the SDP attribute "a=rtcph:" may be used in the ITU-T H.248 RD and shall **not** be used in the ITU-T H.248 LD. + +##### 6.13.2.6 Traffic management (tman) + +**Table 6-77 – Traffic management package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | +|------------|------------------------|------------------------|---------------------|-------------------------------| +| Tman/pol | M | ADD, MODIFY | All | Yes | +| tman/pdr | M | ADD | All | Not applicable | +| tman/dvt | M | ADD | All | Yes | +| tman/sdr | M | ADD | All | Not applicable | +| tman/mbs | M | ADD | All | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned value | +| None | | | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned value | +| | | | | | + +**Table 6-77 – Traffic management package** + +| Events | Mandatory/
Optional | Used in command | | | | | +|--------------------|-------------------------------------|--------------------------------|-----------------------------|------------------------------|--|--| +| None | | | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +##### **6.13.2.7 IP NAPT traversal (ipnapt)** + +**Table 6-78 – IP NAPT traversal package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | +|----------------------------|-------------------------------------|--------------------------------|-----------------------------|---------------------------------------| +| None | | | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned value | +| Latching
(ipnapt/latch) | M | ADD, MODIFY | | Not applicable | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned value | +| | NAPT traversal
processing (napt) | M | All | Not applicable | +| Events | Mandatory/
Optional | Used in command | | | +| None | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | +| | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | +| | | | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | +| None | | | | | + +**Table 6-78 – IP NAPT traversal package** + +| Error codes | Mandatory/Optional | +|--------------------|---------------------------| +| None | | + +##### **6.13.2.8 MPLS (mpls)** + +**Table 6-79 – MPLS package** + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | | | +|--------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| Mpls/stack | M | ADD, MODIFY | All | Not applicable (Note) | | | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | | | +| None | | | | | | | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | | | +| | | | | | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | | | | | | | +| | Event parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | | | | | | | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | | | | | | | +| Statistics | Mandatory/Optional | Used in command | Supported values | | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +NOTE – "Not applicable" means that in case the *mpls/stack* property is absent, the MG shall not apply any MPLS label to the given termination/stream. + +##### 6.13.2.9 VLAN (vlan) + +Table 6-80 – VLAN package + +| Properties | Mandatory/
Optional | Used in command | Supported
Values | Provisioned
Value | | | +|---------------------------------|-------------------------------------|--------------------------------|-----------------------------|-------------------------------------------|--|--| +| VLAN tags
(vlan/tags) | O | ADD, MODIFY | All (Note) | Yes | | | +| Ethernet priority
(vlan/pri) | O | ADD, MODIFY | All | Yes | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned
value | | | +| None | | | | | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | | | +| | | | | | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| None | | | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +NOTE – "All" means value range "0 to 4 095" of property VLAN tags used for VLAN tagging; value "4 096" of property VLAN tags defines the semantic for "no VLAN tagging". + +##### 6.13.2.10 MGC information (mgcinfo) + +Table 6-81 – MGC information package + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | +|--------------------|-------------------------------------|--------------------------------|-----------------------------|---------------------------------------| +| All | M | ADD, MODIFY,
AUDITVALUE | All | Not applicable | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned value | +| None | | | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned value | +| | | | | | +| Events | Mandatory/
Optional | Used in command | | | +| None | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | +| | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | +| | | | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | +| None | | | | | +| Error codes | Mandatory/Optional | | | | +| None | | | | | + +#### 6.13.2.11 Inactivity timer (it) + +Table 6-82 – Inactivity timer package + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | +|----------------|--------------------------------|--------------------------------|-----------------------------|---------------------------------------| +| None | | | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned value | +| None | | | | | +| | Signal parameters | Mandatory/
Optional | Supported
values | Duration
provisioned value | +| | | | | | + +**Table 6-82 – Inactivity timer package** + +| Events | Mandatory/
Optional | Used in command | | | | | +|-----------------------------|-------------------------------------|--------------------------------|-----------------------------|------------------------------|--|--| +| Inactivity timeout
(ito) | M | MODIFY,
NOTIFY | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | Maximum
inactivity time
(mit) | O | All | Yes | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | None | | | | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | | | | | | | + +##### 6.13.2.12 Segmentation (seg) + +**Table 6-83 – Segmentation package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned
value | +|-----------------------------------------------------------------------|--------------------------------|------------------------|-------------------------|------------------------------| +| MGSegmentation
TimerValue (seg/
MGSegmentation
TimerValue) | M | MODIFY,
AUDITVALUE | All | Yes | +| MGCSegmentation
TimerValue (seg/
MGCSegmentation
TimerValue) | M | MODIFY,
AUDITVALUE | All | Yes | +| MGMaxPDUSize
(seg/
MGMaxPDUSize) | M | MODIFY,
AUDITVALUE | All | Yes | +| MGCMMaxPDUSize
(seg/
MGCMMaxPDUSize) | M | MODIFY,
AUDITVALUE | All | Yes | + +**Table 6-83 – Segmentation package** + +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned
value | | | +|--------------------|-------------------------------------|--------------------------------|-----------------------------|-------------------------------------------|--|--| +| None | | | | | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | | | +| | | | | | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| None | | | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | | | | | | | +| Statistics | Mandatory/
Optional | Used in command | | Supported values | | | +| None | | | | | | | +| Error codes | Mandatory/Optional | | | | | | +| 459 | M | | | | | | + +##### **6.13.2.13 RTP package (rtp)** + +**Table 6-84 – RTP package** + +| Properties | Mandatory/
Optional | Used in
command | Supported values | Provisioned
value | +|-------------------|--------------------------------|--------------------------------|-----------------------------|-------------------------------------------| +| None | | | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned
value | +| None | | | | | +| | Signal parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | +| | | | | | + +**Table 6-84 – RTP package** + +| Events | Mandatory/
Optional | Used in command | | +|------------------------------------------|--------------------------------|--------------------------------------------|-------------------------| +| None | | | | +| | | | | +| Statistics | Mandatory/
Optional | Used in
command | Supported values | +| Packets sent (rtp/ps) | M | ADD,
SUBTRACT,
AUDITVALUE | All | +| | O | MODIFY | | +| Packets received
(rtp/pr) | M | ADD,
SUBTRACT
AUDITVALUE | All | +| | O | MODIFY | | +| Packet loss
(rtp/pl) | M | ADD,
SUBTRACT
AUDITVALUE | All | +| | O | MODIFY | | +| Jitter (rtp/jit) | O | ADD,
SUBTRACT
AUDITVALUE,
MODIFY | All | +| Delay (rtp/delay) | O | ADD,
SUBTRACT
AUDITVALUE,
MODIFY | All | +| Octets sent, (rtp/os)
(Note 1) | O | ADD,
AUDITVALUE,
SUBTRACT,
MODIFY | All | +| Octets received,
(rtp/or)
(Note 2) | O | ADD,
AUDITVALUE,
SUBTRACT,
MODIFY | All | +| Error codes | Mandatory/Optional | | | +| None | | | | + +NOTE 1 – Inherited statistic from nt package. Value of rtp/os must be identical to nt/os (see clause E.12.5.2 of [ITU-T H.248.1]). + +NOTE 2 – Inherited statistic from nt package. Value of rtp/or must be identical to nt/or (see clause E.12.5.2 of [ITU-T H.248.1]). + +##### 6.13.2.14 Media gateway overload control (ocp) package + +Table 6-85 – Media gateway overload control package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | | | +|--------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| None | – | – | – | – | | | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | | | +| None. | – | – | | – | | | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | | | +| | – | – | – | – | | | +| Events | Mandatory/Optional | Used in command | | | | | +| MG_Overload (ocp/mg_overload) (Note) | M | MODIFY, NOTIFY | | | | | +| | Event parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | None | – | – | – | | | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | None | – | – | – | | | +| Statistics | Mandatory/Optional | Used in command | Supported values | | | | +| None. | – | – | – | | | | +| Error codes | Mandatory/Optional | | | | | | +| None. | – | | | | | | + +NOTE –When the MG is overloaded, overload events may be sent **either** only following the **first ADD.request** which creates a new Context, **or** following **all ADD.request** commands (see [ITU-T H.248.11]). + +These two options result in different normalisations of the overload event rate as an indicator of the level of MG overload (see clause 6.16.2.3). + +##### 6.13.2.15 IP domain connection (ipdc) + +Table 6-86 – IP domain connection package + +| Properties | Mandatory/
Optional | Used in command | Supported
values | Provisioned
value | | | +|-------------------------------------|-------------------------------------|--------------------------------|-----------------------------|-------------------------------------------|--|--| +| IP realm identifier
(ipdc/realm) | M | ADD, MODIFY | All | Yes | | | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned
value | | | +| None | – | – | | – | | | +| | Signal
parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | | | +| | – | – | – | – | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| None | – | – | | | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | – | – | – | – | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | – | – | – | – | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| None | – | – | – | | | | +| Error codes | Mandatory/Optional | | | | | | +| No | – | | | | | | + +NOTE – [ITU-T H.248.41] does specify a length limit for the ipdc/realm string, i.e., "Length limitation: Where the IP realm identifier property uses a domain name format, it shall handle names of up to 63 characters and should handle domain names of up to 255 characters in accordance with section 2.1 of [IETF RFC 1123]". In case the MGC uses an ipdc/realm property exceeding the above defined length limitation, the MG shall reply with an error descriptor using error code #4449: "Unsupported or Unknown Parameter or Property Value ". + +##### 6.13.2.16 Application data inactivity detection (adid) + +Table 6-87 – Application data inactivity detection package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | +|--------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------| +| None | | | | | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | +| None | | | | | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | +| | | | | | +| Events | Mandatory/Optional | Used in command | | | +| IP flow stop detection (adid/ipstop) | M | ADD, MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/Optional | Supported values | Provisioned value | +| | Detection time (dt) | O | All | Yes | +| | Direction (dir) | O | All | Yes | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | +| | None | | | | +| Statistics | Mandatory/Optional | Used in command | | Supported values | +| None | | | | | +| Error codes | Mandatory/Optional | | | | +| None | | | | | + +##### 6.13.2.17 Hanging termination detection (Hangterm) + +Table 6-88 – Hanging termination detection package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | +|----------------|---------------------------|---------------------------|-------------------------|-----------------------------------| +| None | – | – | – | – | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | +| None | – | – | | – | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | +| | – | – | – | – | +| Events | Mandatory/Optional | Used in command | | | +| Termination | M | ADD, MODIFY, NOTIFY | | | + +**Table 6-88 – Hanging termination detection package** + +| heartbeat
(hangterm/-thb) | Event parameters | Mandatory/
Optional | Supported values | Provisioned value | | | +|------------------------------|---------------------------------|--------------------------------|-------------------------|--------------------------|--|--| +| | Timerx (timerx) | O | 0,1 up | Yes | | | +| | ObservedEvent parameters | Mandatory/
Optional | Supported values | Provisioned value | | | +| | – | – | – | – | | | +| Statistics | Mandatory/
Optional | Used in command | | Supported values | | | +| None | – | – | | – | | | +| Error codes | Mandatory/Optional | | | | | | +| No | – | | | | | | + +##### 6.13.2.18 Statistic conditional reporting (scr) + +**Table 6-89 – Statistic conditional reporting package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned value | +|-------------------------------|--------------------------------|--------------------------------|-------------------------|-----------------------------------| +| None | – | – | – | – | +| Signals | Mandatory/
Optional | Used in command | | Duration provisioned value | +| None | – | – | | – | +| | Signal parameters | Mandatory/
Optional | Supported values | Duration provisioned value | +| | – | – | – | – | +| Events | Mandatory/
Optional | Used in command | | | +| Conditional reporting, scr/cr | M | ADD, MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/
Optional | Supported values | Provisioned value | +| | Statistic identifier, si | M | All | Yes | +| | Duration, dur | O | All | Yes | +| | Period, per | O | All | Yes | +| | Maximum, max | O | All | Yes | +| | Minimum, min | O | All | Yes | +| | Normal, nor | O | All | Yes | +| | Request timestamp (rt) | O | All | Yes | +| | Value type (typ) | O | All | Yes | +| | Deviation (dev) | O | All | Yes | + +**Table 6-89 – Statistic conditional reporting package** + +| | | | | | | | +|--------------------|---------------------------------|---------------------------|-------------------------|--------------------------|--|--| +| | Compliance (com) | O | All | Yes | | | +| | Direction (dir) | O | All | Yes | | | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | | | +| | Statistic identifier, si | M | All | – | | | +| | Value, val | M | All | – | | | +| Statistics | Mandatory/Optional | Used in command | | Supported values | | | +| None | – | – | | – | | | +| Error codes | Mandatory/Optional | | | | | | +| None | – | | | | | | + +##### **6.13.2.19 IP realm availability (ipra)** + +**Table 6-90 – IP realm availability package** + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | +|--------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------| +| Available realms, (ipra/ar) | M | AUDITVALUE | All | Not applicable | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | +| None | – | – | | – | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | +| | – | – | – | – | +| Events | Mandatory/Optional | Used in command | | | +| Available realms changed, (ipra/arc) | M | MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/Optional | Supported Values | Provisioned value | +| | – | – | – | – | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | +| | Newly available realms (nar) | O (Note) | All | Not applicable | +| | Newly unavailable realms (nur) | O (Note) | All | Not applicable | + +**Table 6-90 – IP realm availability package** + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | | | +|--------------------|---------------------------|------------------------|-------------------------|--------------------------|--|--| +| Statistics | Mandatory/Optional | Used in command | | Supported values | | | +| None | – | – | | – | | | +| Error codes | Mandatory/Optional | | | | | | +| None | – | | | | | | + +NOTE – Although the ObservedEvent parameters ipr/nar and ipra/nur are optional as such, at least one parameter must be included in an ipra/arc ObservedEvent. + +##### **6.13.2.20 RTP application data (rtpad)** + +**Table 6-91 – RTP application data package** + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | | | +|------------------------------------------------|---------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| None | – | – | – | – | | | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | | | +| None | – | – | | – | | | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | | | +| | – | – | – | – | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | | | | | | | +| Statistics | Mandatory/Optional | Used in command | | Supported values | | | +| RTP payload octets sent, (rtpad/payloados) | M | ADD, AUDITVALUE, SUBTRACT | | All | | | +| | O | MODIFY | | | | | +| RTP payload octets received, (rtpad/payloador) | M | ADD, AUDITVALUE, SUBTRACT | | All | | | +| | O | MODIFY | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | – | | | | | | + +##### 6.13.2.21 Latch statistics (lstat) + +Table 6-92 – Latch statistics package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | | | +|-------------------------------|--------------------|---------------------------|------------------|----------------------------|--|--| +| None | – | – | – | – | | | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | | | +| None | – | – | | – | | | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | | | +| | – | – | – | – | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | | | | | | | +| Statistics | Mandatory/Optional | Used in command | | Supported values | | | +| Discarded packets, (lstat/dp) | M | ADD, AUDITVALUE, SUBTRACT | | All | | | +| | O | MODIFY | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | – | | | | | | + +##### 6.13.2.22 Traffic policing statistics (tmanr) + +Table 6-93 – Traffic policing statistics package + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | +|--------------------|--------------------|---------------------------|------------------|----------------------------| +| None | – | – | – | – | +| Signals | Mandatory/Optional | Used in command | | Duration provisioned value | +| None | – | – | | – | +| | Signal parameters | Mandatory/Optional | Supported values | Duration provisioned value | +| | – | – | – | – | +| Events | Mandatory/Optional | Used in command | | | +| None | | | | | +| Statistics | Mandatory/Optional | Used in command | | Supported values | +| Discarded packets, | M | ADD, AUDITVALUE, SUBTRACT | | All | + +**Table 6-93 – Traffic policing statistics package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned value | | | +|-----------------------------------------------|--------------------------------|---------------------------|-------------------------|--------------------------|--|--| +| (tmanr/dp) | O | MODIFY | | | | | +| Peak-rate violating packets, (tmanr/pvp) | O | ADD, AUDITVALUE, SUBTRACT | All | | | | +| | O | MODIFY | | | | | +| Peak-rate violating octets, (tmanr/pvo) | O | ADD, AUDITVALUE, SUBTRACT | All | | | | +| | O | MODIFY | | | | | +| Sustained-rate violating packets, (tmanr/svp) | O | ADD, AUDITVALUE, SUBTRACT | All | | | | +| | O | MODIFY | | | | | +| Sustained-rate violating octets, (tmanr/svo) | O | ADD, AUDITVALUE, SUBTRACT | All | | | | +| | O | MODIFY | | | | | +| Error codes | Mandatory/Optional | | | | | | +| None | – | | | | | | + +NOTE – The statistic tmanr/dp is mandatory because independent of the applied policing mechanism. The other four statistics are optional because dependent on peak- or sustained-rate policing. + +#### 6.13.2.23 Generic pull mode package (plm) + +**Table 6-94 – Generic pull mode package** + +| Properties | Mandatory/
Optional | Used in command | Supported values | Provisioned value | +|-------------------------------------------------------------|--------------------------------|--------------------------------|-------------------------|-----------------------------------| +| Path coupled request domains under MGC ownership (plm/rdmo) | M | MODIFY, AUDITVALUE | All | Provisioned | +| Signals | Mandatory/
Optional | Used in command | | Duration provisioned value | +| None. | – | – | | – | +| | Signal parameters | Mandatory/
Optional | Supported values | Duration provisioned value | +| | – | – | – | – | +| Events | Mandatory/
Optional | Used in command | | | +| Decision request for QoS resource reservation (plm/rdrr) | M | ADD, MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/
Optional | Supported values | Provisioned value | + +**Table 6-94 – Generic pull mode package** + +| Properties | Mandatory/
Optional | Used in command | Supported
values | Provisioned
value | | | +|----------------------------------------------------------------|-------------------------------------|--------------------------------|-----------------------------|------------------------------|--|--| +| | Bearer request address value (brav) | O | – | – | | | +| | Bearer request port value (brpv) | O | – | – | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | Authorization token (authtok) | M | – | – | | | +| Decision request for QoS
resource modification
(plm/rdm) | M | ADD, MODIFY,
NOTIFY | – | – | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | None. | – | – | – | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | Authorization token (authtok) | M | – | – | | | +| Events | Mandatory/
Optional | Used in command | | | | | +| Decision request for QoS
resource release
(plm/rdl) | M | ADD, MODIFY,
NOTIFY | – | – | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | None. | – | – | – | | | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | Provisioned
value | | | +| | Authorization token (authtok) | M | – | – | | | +| Statistics | Mandatory/
Optional | Used in command | Supported values | | | | +| None. | – | – | – | | | | +| Error codes | Mandatory/Optional | | | | | | +| None. | – | | | | | | + +##### 6.13.2.24 RSVP extension package (rsvp) + +Table 6-95 –RSVP extension package + +| Properties | Mandatory/
Optional | Used in command | Supported
values | Provisioned
value | +|-----------------------------|--------------------------------|--------------------------------|-----------------------------|-------------------------------------------| +| None | – | – | – | – | +| Signals | Mandatory/
Optional | Used in command | | Duration
provisioned
value | +| Send path (rsvp/path) | M | ADD, MODIFY | | – | +| | Signal parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | +| | Session ID (session) | M | – | – | +| | Sender TSpec (stspec) | O | – | – | +| | Ad spec (adspec) | O | – | – | +| | Policy data (policy) | O | – | – | +| | Data TTL (dttl) | O | – | – | +| | Time value (time) | O | – | – | +| Send Resv (rsvp/resv) | M | MODIFY | | – | +| | Signal parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | +| | Session ID (session) | M | – | – | +| | Style (style) | M | FF, SE, WF
(Note) | Provisioned | +| | Flow spec (flowspec) | O | – | – | +| | Filter spec (filterspec) | O | – | – | +| | Policy data (policy) | O | – | – | +| | Confirm flag (confirm) | O | ON, OFF | Provisioned | +| | Time value (time) | O | – | – | +| RSVP release (rsvp/release) | M | MODIFY | | – | +| | Signal parameters | Mandatory/
Optional | Supported
values | Duration
provisioned
value | +| | Session ID (session) | M | – | – | + +**Table 6-95 –RSVP extension package** + +| Properties | Mandatory/Optional | Used in command | Supported values | Provisioned value | +|----------------------------|---------------------------------|---------------------------|-------------------------|---------------------------------| +| | Message Type (mtype) | O | PathTear, ResvTear | – | +| Events | Mandatory/Optional | Used in command | | | +| Path received (rsvp/pathr) | M | ADD, MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/Optional | Supported value: | Provisioned value | +| | None. | – | – | – | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | Provisioned value | +| | Session ID (session) | M | – | – | +| | Sender TSpec (stspec) | O | – | – | +| | Ad Spec (adspec) | O | – | – | +| | Policy data (policy) | O | – | – | +| Resv received (rsvp/resvr) | M | ADD, MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/Optional | Supported values | Event parameters | +| | None. | □– | – | – | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | ObservedEvent parameters | +| | Session ID (session) | M | – | – | +| | Style (style) | M | FF, SE, WF (Note) | Provisioned | +| | Flow Spec (flowspec) | O | – | – | +| | Filter Spec (filterspec) | O | – | – | +| | Policy data (policy) | O | – | – | +| Path error (rsvp/patherr) | M | ADD, MODIFY, NOTIFY | | | +| | Event parameters | Mandatory/Optional | Supported values | Event parameters | +| | None. | – | – | – | +| | ObservedEvent parameters | Mandatory/Optional | Supported values | ObservedEvent parameters | +| | Session ID (session) | M | – | – | +| | Error spec (errspec) | M | – | – | +| | Policy data (policy) | O | – | – | + +**Table 6-95 –RSVP extension package** + +| Properties | Mandatory/
Optional | Used in command | Supported
values | Provisioned
value | +|----------------------------------|-------------------------------------|--------------------------------|-----------------------------|-------------------------------------| +| Resv Error
(rsvp/resverr) | M | ADD, MODIFY,
NOTIFY | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Event
parameters | +| | None. | – | – | – | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | ObservedEvent
parameters | +| | Session ID (session) | M | – | – | +| | Error specification
(errspec) | M | – | – | +| | Flow spec
(flowspec) | O | – | – | +| | Filter spec
(filterspec) | O | – | – | +| | Policy data (policy) | O | – | – | +| Resv Confirm
(rsvp/resvconf) | M | ADD, MODIFY,
NOTIFY | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Event
parameters | +| | None. | – | – | – | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | ObservedEvent
parameters | +| | Session ID (session) | M | – | – | +| | Style (style) | M | FF, SE, WF
(Note) | Provisioned | +| | Flow spec
(flowspec) | O | – | – | +| | Filter spec
(filterspec) | O | – | – | +| | Policy data (policy) | O | – | – | +| RSVP teardown
(rsvp/teardown) | M | ADD, MODIFY,
NOTIFY | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Event
parameters | +| | None. | – | – | – | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | ObservedEvent
parameters | +| | Session ID (session) | M | – | – | + +**Table 6-95 –RSVP extension package** + +| Properties | Mandatory/
Optional | Used in command | Supported
values | Provisioned
value | +|---------------------------------------------------------------------|-------------------------------------|--------------------------------|-----------------------------|-------------------------------------| +| State expiration (rsvp/se) | M | ADD, MODIFY,
NOTIFY | | | +| | Event
parameters | Mandatory/
Optional | Supported
values | Event
parameters | +| | State expiration
interval (sei) | O | – | – | +| | ObservedEvent
parameters | Mandatory/
Optional | Supported
values | ObservedEvent
parameters | +| | Session ID (session) | M | – | – | +| Error codes | Mandatory/Optional | | | | +| None | – | | | | +| NOTE – FF = Fixed-Filter, SE=Shared-Explicit and WF=Wildcard-Filter | | | | | + +## 6.14 Mandatory support of SDP and Annex C information elements + +Elements listed as mandatory shall be supported by MGC and MG but does not have to be present in all commands containing SDP. Details of which elements are included in each command are provided in clause 6.17. + +NOTE – "Annex C" relates to [ITU-T H.248.1] Annex C, "Tags for media stream properties". Annex C information elements are not required in ITU-T H.248 text encoding mode. + +**Table 6-96 – Supported SDP information elements** + +| SDP information element | Mandatory | Description | +|-------------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Protocol version
"v=" line | Mandatory | The value must always be equal to zero:
v=0 | +| Connection
"c=" line | Mandatory | The network type must always be "IN".
The address type value must be "IP4" or "IP6".
The connection address value may be underspecified with CHOOSE wildcard ("\$"). | +| Media
"m=" line | Mandatory | There are four fields (or SDP values) , , and in the "m=" line (see [IETF RFC 4566]; (Note 3)).
The "m=" line may be omitted from SDP (Note 6) | +| Media type | Mandatory if "m=" line included | "-" may be used for the media value.
Other values shall be ignored, unless media specific information is required.
The media value shall be specified in case of media-aware interworking.
(Note 2) | + +**Table 6-96 – Supported SDP information elements** + +| SDP information element | | Mandatory | Description | | +|-------------------------|----------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| | Transport port | Mandatory if "m=" line included | The port value may be underspecified with CHOOSE wildcard ("\$"). | | +| | Transport protocol | Mandatory if "m=" line included | udp | Allow only L4 protocol = UDP. | +| | | | tcp | Allow only L4 protocol = TCP. | +| | | | RTP/AVP | Allow only L4 protocol = UDP. (Note 1) | +| | | | udptl | Allow only L4 protocol = UDP. | +| | | | – | No transport protocol specific behaviour is required by the MG. | +| | Media format | Mandatory if "m=" line included | "-" may be used for the format list value, e.g., in case of media-agnostic interworking. Other values may be used for media-aware interworking (e.g., transcoding; see clause 6.16.1.13). (Note 2) | | +| Bandwidth "b=" line | | Mandatory

NOTE – MUST not be used without a "m=" line. | The modifier value must always be "AS". This implies that the bandwidth-value represents the ""maximum bandwidth" (see section 5.8 of [IETF RFC 4566]). The bandwidth-value relates therefore to the peak bit-rate (Note 7).

The bandwidth-value defines the IP layer bandwidth for the specific ITU-T H.248 Stream. (Notes 4 and 5).

For RTP flows, where RTP control protocol (RTCP) resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the bandwidth value will include the bandwidth used by the RTP and the RTCP together. | | + +NOTE 1 – Even if the transport value is RTP, the "RTP Specific Behaviour" property of the Gate Management package (gm) shall be used to indicate whether RTCP resource reservation is also requested. + +NOTE 2 – For Ia profile version 2 ITU-T H.248 profile [IETF RFC 4566] shall be used as basis. [IETF RFC 4566] enables "-" as a valid character (Ia profile version 1 uses [b-IETF RFC2327], which does not allow the "-" in place of media type, transport and media format fields. However, in the scope of Ia profile version 1, this was considered as an admitted SDP extension). + +NOTE 3 – RFC 4566 obsoleted RFC 2327, but the augmented Backus-Naur form (ABNF) grammar did slightly change for the "m=" line: + +- a) RFC 2327: m= +- b) RFC 4566: m= . . .There is a syntactical change for the last two fields, but the semantical meaning is unchanged. + +See also [ITU-T H.248.49], Appendix I "Comparison of SDP variants between RFC 4566 and RFC 2327" + +**Table 6-96 – Supported SDP information elements** + +| SDP information element | Mandatory | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------------| +|

and in particular: Table I.7 of [ITU-T H.248.49] "RFC 4566 versus RFC 2327 – SDP specification – "m=" line".

NOTE 4 – This semantic is consistent for RTP traffic (see section 6.2 of [IETF RFC 3550]) and non-RTP traffic (see section 5.8 of [IETF RFC 4566]).

NOTE 5 – It has to be noted that Ia profile version 1 has a different semantic (see Table 81 in [ETSI ES 283 018]) defined, which incorporates also layer 2 bit-rate.

A transformation between both "b=" line usages (in case of IP-over-L2) is not straightforward because the transformation parameters are based on L2-PCI and the IP packet rate. The L2-PCI is typically constant for a dedicated L2 technology (like IP-over-IEEE 802.3), but the packet rate is application-specific. E.g., the IP packet rate is usually unknown at Ia for media-agnostic IP-to-IP interworking.

NOTE 6 – The "m=" and "b=" lines may be omitted in certain procedures, which are further described in clause 6.16.1.11.

NOTE 7 – The unit for the bandwidth-value (peak bit rate) is "kbit/s". The unit for the peak data rate (tman/pdr) is "byte/s". The "b=" line is not providing any information about the traffic characteristic, i.e., whether the traffic flow has a constant bit rate (CBR) or variable bit rate (VBR). The bandwidth-value is thus independent of the traffic characteristic and relates to the peak bit rate for CBR and VBR traffic (see also clause 6.16.1.5).

| | | + +## 6.15 Optional support of SDP and Annex C information elements + +NOTE – "Annex C" relates to [ITU-T H.248.1] Annex C, "Tags for media stream properties". Annex C information elements are not required in H.248 text encoding mode. + +Table 6-97 summarizes the "optional" SDP information elements, based on their specific usage according to clause 7.1.8 of [ITU-T H.248.1]. Their usage may depend on the direction from MGC towards MG or vice versa. + +**Table 6-97 – Optional SDP information elements** + +| SDP information element | Mandatory/optional | Description | +|---------------------------|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Origin
"o=" line | Optional for MGC,
Mandatory for MG |

The origin line consists of six fields (<username>, <session id>, <version>, <network type>, <address type>, and <address>).

The MGC is not required to supply this line, but shall accept it (see clause 7.1.8 of [ITU-T H.248.1]).

The MG shall populate this line as follows, e.g.,:

o=- 0 0 IN IP4 11.9.19.65

or use the value received from the MGC.

| +| Session name
"s=" line | Optional for MGC,
Mandatory for MG |

The session name "s=" line contains a single field (<session name>).

The MGC is not required to supply this line, but shall accept it (see clause 7.1.8 of [ITU-T H.248.1]).

The MG shall populate this line as

| + +**Table 6-97 – Optional SDP information elements** + +| SDP information element | Mandatory/optional | Description | +|-------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | follows, e.g.,:
s = -
or use the value received from the MGC | +| Times, repeat times and time zones
"t=" line | Optional for MGC,
Mandatory for MG | The time "t=" line consists of two fields ( and ).
The MGC is not required to supply this line but shall accept it (see clause 7.1.8 of [ITU-T H.248.1]).
The MG shall populate this line as follows, e.g.,:
t=0 0
or use the value received from the MGC. | +| Attribute
"a=" line | Optional for MGC,
Recommended for MG | 1) Application "RTCP port control":
The attribute "a=" line may either contain (a=rtcp: ) or (a=rtcp:
) when the "a=" line is used for RTCP port transmission.
The MGC shall supply the "a=" line in the Remote Descriptor (RD) when non-default RTCP port values are used by the peer media entity.
The "a=" line is ignored by the MG if received from the MGC with a request for latching (ipnapt/latching) or if property gm/rsb=OFF (see clause 6.16.1.7). | +| | Optional for MGC,
Optional for MG | 2) Application "Media-aware interworking (transcoding)":
The "a=" line provides the complementary information for the "m=" line (see Table 6-15) with regards to a specified media type/format.
For a dynamic RTP payload type, for each media information on the codec type shall be provided in a separate SDP "a=rtpmap" line and possibly additional SDP "a=fmtp"-line(s). | + +## 6.16 Overview of procedures + +Details of session dependent procedures are provided in clauses 6.17. Details of session independent procedures are provided in clauses 6.18 and 6.19. + +### 6.16.1 Overview of session dependent procedures + +The various policing functions of the PE-PE are summarized in Appendix I. The specific types of *address* policing and *traffic* policing are in scope of clauses 6.16.1.1 and 6.16.1.5 respectively. + +The general procedures are related to session-dependent (also known as ITU-T H.248 call-dependent) procedures. There are procedures in following categories: + +- Address allocation and translation is in scope of clauses 6.16.1.2. The adaptation of addresses (latching) is the subject of clause 6.16.1.2. +- Session-dependent policing is applicable to this profile. The specific types of address policing and traffic policing are in scope of clauses 6.16.1.1 and 6.16.1.5 respectively. Media type policing is discussed in clause 6.16.1.8. +- QoS support mechanisms are discussed in clause 6.16.1.4. +- Measurement and reporting of statistics are discussed in clause 6.16.1.6. +- RTCP handling (e.g., IP port allocation rules for RTCP) is discussed in clause 6.16.1.7. +- Detection of inactive bearer connections is in scope of clauses 6.16.1.9. +- IP realm/domain indication is discussed in clause 6.16.1.10. +- Two-stage MG resource reservation is discussed in clause 6.16.1.11. +- Detection of hanging ITU-T H.248 terminations is discussed in clause 6.16.1.12. +- Real time statistics reporting 6.16.1.13. +- Transcoding is discussed in clause 6.16.1.14. +- Virtual private network (VPN) identification is discussed in clause 6.16.1.15. +- Topology hiding is discussed in clause 6.16.1.16. + +#### 6.16.1.1 Gate control + +##### 6.16.1.1.1 Streams, terminations and gates + +The realization of a gate requires two ephemeral terminations. An ephemeral termination sources and/or sinks one or more media streams. Gates are direction and stream dependent. + +In this Profile, RTP traffic shall also be controlled through a single ITU-T H.248 stream, representing both the RTP and RTCP flows, if the RTP Specific Behaviour property of the Gate Management package is set to ON. In such a case, when the MG is requested to allocate a port for an RTP flow, a consecutive port for the associated RTCP flow is automatically allocated (see also clause 6.16.7). + +In this case, mono-media sessions require one bidirectional ITU-T H.248 stream on a termination, while a multi-media sessions (e.g., audio and video) would require multiple ITU-T H.248 streams on a termination (one stream per media type). + +##### 6.16.1.1.2 Assignment of L3 address and L4 port values + +The ITU-T H.248 base protocol enables the PD-PE to choose the IP address and port on which a termination will receive media flows. In addition, the Gate Management package enables the PD-PE to explicitly provide the following information: + +- expected IP source address and port of received packets; +- IP source address and port of sent packets. + +The relationship between ITU-T H.248 descriptors in this Profile and the addresses used in packets sent and received by the gate is indicated in Table 6-98. Figure 6-2 illustrates the used naming conventions for the IP transport connection endpoints in the PE-PE and remote IP node. + +**Table 6-98 – Relation between packet direction, IP address/port and ITU-T H.248 descriptor/information** + +| Packet direction | IP Address/L4 Port | Source of information for transport address values | +|-------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Received by termination | Source:
• RS (A)
• RS (P) | The source of information for the expected remote source transport address RS (A, P) value is dependent on the usage of remote source filtering and hosted NAP(T) traversal as per Table 6-99. | +| | Destination :
• LS (A)
• LS (P) | Local destination transport address LD (A, P):
Local Descriptor | +| Sent by termination | Source :
• LS (A)
• LS (P) | Local source transport address LS (A, P):
1. Availability of LS information due to explicit setting of local source transport address:
LocalControl Descriptor/gate management/local source address + local source port or, if not present:
2. Availability of LS information in ITU-T H.248 Local Descriptor SDP:
Source address not explicitly enforced/signalled via "gm" package. The source address is determined from the local SDP (which implies a symmetrical local network address, i.e., LD (A) = LS (A)). | +| | Destination :
• RD (A)
• RD (P) | The source of information for the remote destination transport address RD (A, P) value is dependent on the usage of hosted NAP(T) traversal as per Table 6-100. | + +**Table 6-99 – Expected remote source transport address** + +| Expected remote source transport address RS (A, P): | Hosted NA(P)T traversal | | +|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | No | Yes | +| No | As no source filtering activated no specific RS (A, P) is expected. The PE-PE may determine actual RS (A) and RS (P) values by monitoring incoming IP packets. | The expected remote source transport address is determined by the NAPT traversal process as described in [ITU-T H.248.37]. Even if no filtering is ordered, the NAPT traversal process implies source filtering on the transport address after latching has occurred. | +| Filtering on remote source address(es)
Yes | Alt 1. LocalControl Descriptor/gate management/remote source address mask AND/OR remote source port or remote source port range is used to determine the expected. RS(A) and RS(P) values, which allows for the peer IP node to use asymmetric network address (RS(A) $\neq$ RD(A)).
Alt 2. Combination of gate management and Remote Descriptor, which assumes symmetrical remote network address (RS(A) = RD(A)). | First stage (before latching):
Same as in cell to the left.

Second stage (after latching):
Same as in above cell. | + +**Table 6-100 – Source of information for the remote destination transport address** + +| Remote destination transport address RD (A, P): | Hosted NA(P)T traversal | | +|-------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | No | Yes | +| Source of information | The remote destination transport address is determined by the Remote Descriptor. | The remote destination transport address is determined by the NAPT traversal process as described in [ITU-T H.248.37]. This implies a symmetrical remote network address, i.e., RD(A) = RS(A). | + +###### *a) Endpoint naming convention* + +![Diagram (a) showing endpoint naming conventions for ITU-T H.248 media gateways. It illustrates the flow of data between a Local destination, Remote source, Local source, and Remote destination through an IP transport connection endpoint. The diagram shows the mapping of Local Destination (LD), Local Source (LS), Remote Source (RS), and Remote Destination (RD) to IP headers (DA, SA, DP, SP) and L4 headers (SP, DP, SA, DA).](3766b291e69420b0437ae278b057b5ee_img.jpg) + +The diagram illustrates the naming convention for endpoints within an ITU-T H.248 media gateway. On the left, the gateway contains four endpoint types: LD(A), LD(P), LS(P), and LS(A). On the right, the peer entity (e.g., IP host, IP next hop, ITU-T H.248 MGC) contains four corresponding endpoint types: RS(A), RS(P), RD(P), and RD(A). Arrows show the mapping from local/remote entities to these endpoints and then into the IP and L4 headers. For example, a 'Local destination' maps to LD(A) and LD(P), which then map to the DA and DP fields of the IP and L4 headers respectively. A 'Perspective' arrow indicates the view from the media gateway. + +Diagram (a) showing endpoint naming conventions for ITU-T H.248 media gateways. It illustrates the flow of data between a Local destination, Remote source, Local source, and Remote destination through an IP transport connection endpoint. The diagram shows the mapping of Local Destination (LD), Local Source (LS), Remote Source (RS), and Remote Destination (RD) to IP headers (DA, SA, DP, SP) and L4 headers (SP, DP, SA, DA). + +###### *b) Protocol layering* + +![Diagram (b) showing protocol layering for Context C1 and Stream S1. It details the mapping of Stream S1 components (LD(P), LD(A), LS(P), LS(A)) to L4 and L3 addresses (RS(P), RS(A), RD(P), RD(A)) and their corresponding layers (L1, L2, L3, L4).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +This diagram shows the protocol layering for a specific context (Context C1) and stream (Stream S1). It maps the stream's internal components to external network addresses. The left side shows Stream S1 components grouped into two sets: one with LS(P), LS(A) and another with LD(P), LD(A). These map to the right side, which shows RS(P), RS(A) and RD(P), RD(A). Each of these four components is associated with a specific layer: RS(P) and RD(P) map to L4, RS(A) and RD(A) map to L3. Below these are layers L2 and L1. A legend at the bottom defines the naming abbreviations (LD, LS, RD, RS) and address types (DA, DP, SA, SP) and their corresponding symbols (circle for L3 address, diamond for L4 port). + +Diagram (b) showing protocol layering for Context C1 and Stream S1. It details the mapping of Stream S1 components (LD(P), LD(A), LS(P), LS(A)) to L4 and L3 addresses (RS(P), RS(A), RD(P), RD(A)) and their corresponding layers (L1, L2, L3, L4). + +Q.3303.2 v2(14)\_F6-2 + +**Figure 6-2 – Naming conventions for IP transport connection endpoints (from PE-PE perspective; in line with ITU-T H.248.1 conventions)** + +NOTE – ITU-T H.248.1 may in the future provide a general overview of IP transport connection endpoints similar to Figure 6-2. Figure 6-2 will be then replaced by a reference to [ITU-T H.248.1]. + +##### **6.16.1.1.3 Opening and closing gates** + +Opening and closing gates is achieved by setting the Stream mode parameter of the associated termination(s) to the appropriate values. Subtracting a termination from a context also closes the gate for all ITU-T H.248 streams in the termination. + +In the context of conversational services, an active session requires that the gates in both directions be opened (terminations in bi-directional mode). + +##### **6.16.1.1.4 Filtering due to conditions on L3 address and/or L4 port values** + +Filtering on the IP source address and/or port might be implemented using the Gate Management package, or using the SDP information in the Remote Descriptor. In case the filtering is done based on the Remote Descriptor, the activation/deactivation of the filtering is configured in the PE-PE. If the Gate Management package is used, it shall override the configured value in the PE-PE. + +NOTE – It should be noticed that the IP source address and port may not always be available to the PD-PE. When session initiation protocol (SIP) signalling is used, the session description does not contain this information (i.e., according to [IETF RFC 3264], the IP address and port present in an SDP offer indicate + +nothing about the source IP address and source port of RTP and RTCP packets that will be sent by the offerer). Any other protocol that uses SDP as a session description mechanism (e.g., RTSP) has the same constraints. + +In such configurations, the Gate Management package may be used as follows: + +- in an IPv6 environment, the Source Address Mask property contains the 64 bits prefix of the IP address that is set in the termination's Remote Descriptor; +- in an IPv4 environment, the Source Address Mask property contains the IP address that is set in the termination's Remote Descriptor, except that a number of trailing digits may be wildcarded; +- in both cases above, Source Port filtering should not be activated. + +The gate concept, together with ITU-T H.248 Stream/Termination handling, is further illustrated in Annex A of [b-ETSI ES 283 018]. + +#### **6.16.1.2 Allocation and translation of IP addresses, ports and versions (NAPT-PT)** + +##### **6.16.1.2.1 Allocation methods** + +The procedures of this clause support the following NAPT and protocol translation (NAPT-PT) functionality: + +- NAPT-PT functionality with "double" addresses and ports translation (both source and destination addresses and ports are translated), or; +- optional NAPT-PT functionality with "single" address and port translation (either source or destination address and port translation) – applicable if the PE-PE has router functionality, or direct L2 connectivity with user terminals. + +The ITU-T H.248 base protocol enables the PD-PE to either choose the addresses and ports associated with a termination or to request the PE-PE to allocate these IP addresses and ports. NAPT control on destination addresses and ports is achieved by setting the Local and Remote Descriptors according to the following principles: + +- The IP and port address in the Remote Descriptors are set by the PD-PE according to the information received in call/session signalling (e.g., SDP in SIP INVITE and 200 OK). +- The address and port in the Local Descriptor are selected by the PE-PE within the indicated IP address realm from PD-PE side (see also below). + +If the PE-PE has router functionality, or direct L2 connectivity with the user terminals, the address and port of the Local Descriptor towards the private network may optionally be set according to the following principles: + +- The IP and port address in the Local Descriptor towards the private network is provided by the PD-PE (instead of being selected by the PE-PE). The PD-PE shall copy the Remote Descriptor of the public network into the Local Descriptor towards the private network. + +The PD-PE has the ability to choose the address space in which the PE-PE allocates an IP address. This is achieved by setting the IP realm identifier in the Domain Connection package to the appropriate value (see clause 6.5.1.1). The association of dedicated "IP address spaces" (also known as "IP address realms" or briefly "IP realms", see [b-IETF RFC 2663]) with the IP realm identifier requires a mutual agreement between PD-PE and PE-PE. This is realized via provisioning, thus beyond the scope of this Profile. However the PD-PE can discover which realms are supported by the PE-PE through the use of the IP realm availability package (see clause 6.16.1.10.5). + +##### **6.16.1.2.2 "Double" NA(P)T** + +The term "double" NA(P)T relates to the translation of source *and* destination address information: + +- "double" NAT = translation of 2-tuple (DA, SA) is *not* supported by this profile (because it would require the L4-port agnostic mode); +- "double" NAPT = translation of 4-tuple (DA, SA, DP, SP), i.e., L4-port aware mode. + +Example: (here "double" NAPT): + +Figure 6-3 provides an example of "double" network address and port translation, where a session is to be established between IPv4 addresses 10.140.120.10 (private address) and 156.106.192.33 (public address). + +![ITU-T H.248 IP-to-IP context C1 diagram showing two terminations, T1(S1) and T2(S1), connected via a central switching element. Arrows indicate bidirectional traffic flow. Protocol layering diagram showing Stream S1 passing through Context C1. It details the mapping of Local Descriptor (LD) and Remote Descriptor (RD) fields to Layer 4 (L4) and Layer 3 (L3) protocol headers. On the left, RD(P) and RD(A) are shown. In the center, Stream S1 contains LS(P), LS(A), LD(P), and LD(A) fields. On the right, RS(P), RS(A), LD(P), LD(A), and RD(P), RD(A) are shown, with labels L4, L3, L2, L1 indicating their respective layers.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +*a) ITU-T H.248 context model* + +*b) Stream descriptors* + +Stream Descriptor for T1 + +Local Descriptor: +LD(A) = 10.200.30.20 +LD(P) = 334 + +Remote Descriptor: +RD(A) = 10.140.120.10 +RD(P) = 222 + +Stream Descriptor for T2 + +Local Descriptor: +LD(A) = 139.100.0.121 +LD(P) = 334 + +Remote Descriptor: +RD(A) = 156.106.192.33 +RD(P) = 556 + +*c) Protocol layering* + +NOTE – There is only one ITU-T H.248 Stream (S1) per Termination in this example + +ITU-T H.248 IP-to-IP context C1 diagram showing two terminations, T1(S1) and T2(S1), connected via a central switching element. Arrows indicate bidirectional traffic flow. Protocol layering diagram showing Stream S1 passing through Context C1. It details the mapping of Local Descriptor (LD) and Remote Descriptor (RD) fields to Layer 4 (L4) and Layer 3 (L3) protocol headers. On the left, RD(P) and RD(A) are shown. In the center, Stream S1 contains LS(P), LS(A), LD(P), and LD(A) fields. On the right, RS(P), RS(A), LD(P), LD(A), and RD(P), RD(A) are shown, with labels L4, L3, L2, L1 indicating their respective layers. + +**Figure 6-3 – Network address and port translation (NAPT) – Example for bidirectional ("double") translation** + +##### 6.16.1.2.3 "Single" NA(P)T + +The term "single" NA(P)T relates to the translation of either source-only or destination-only address information: + +- "single" NAT = translation of 1-tuple (SA) or (DA) is not supported by this profile (because it would require the L4-port agnostic mode); +- "single" NAPT = translation of 2-tuple (SA, SP) or (DA, DP), i.e., L4-port aware mode. + +Example (here "single" NAPT on (DA, DP)-tuple elements): + +For "single" network address and port translation applications, the T1 Local Descriptor address and port in Figure 6-3 has to be changed to 156.106.192.33: 556 (equal to the T2 Remote Descriptor address and port). + +T1-to-T2 IP flow direction: + +- The (DA, DP)-tuple values will be then *not* changed (called "destination NAPT-less"), whereas the (SA, SP)-tuple values are translated ("source NAPT-full" mode). += single NAPT + +T2-to-T1 IP flow direction: + +- The (DA, DP)-tuple values *and* the (SA, SP)-tuple values are both translated ("source and destination NAPT-full" mode). += double NAPT + +##### 6.16.1.2.4 NA(P)T-less case + +See also Annex H.3 of [b-ETSI TR 183 068] + +###### 6.16.1.2.4.1 NA(P)T-less B2BIH mode + +For NA(P)T-less applications, the T1 Local Descriptor address and port in Figure 3 has to be changed to 156.106.192.33: 556 (equal to the T2 Remote Descriptor address and port) and the T2 Local Descriptor address and port in Figure 6-3 has to be changed to 10.140.120.10: 222 (equal to the T1 Remote Descriptor address and port). + +Further aspects from ITU-T H.248 control perspective: + +- there is either a "source and destination NAT-less" mode (briefly NAT-less), +- or a "source and destination NAPT-less" mode (briefly NAPT-less); +- all other combinations may be mapped on NA(P)T-full scenarios (e.g., L3 NAT-less but L4 port translation). +- The NAT-less back-to-back IP host (B2BIH) and NAPT-less B2BIH mode using both the same ITU-T H.248 control method, i.e., the RD(A,P) address value from the ITU-T H.248 RD is copied by the PD-PE in the LD(A,P) value of the ITU-T H.248 LD of the other ITU-T H.248 IP Termination. This can only be done once the RD of both terminations are known to the PD-PE and the profile thus allows for a LD to be absent in the ADD request command. + +###### 6.16.1.2.4.2 NA(P)T-less IP router (IPR) mode + +See Annex H of [b-ETSI TR 183 068], not supported by this profile. + +##### 6.16.1.2.5 NA(P)T and explicit local source transport address settings + +NAPT control on source addresses and ports (i.e., source NAPT) is achieved by setting the local source address and local source port properties defined in the Gate Management package to a value that differs from the actual source address of the packets received from the remote entity. + +The *gm* package capabilities may be also used for source NAT control only, i.e., without explicit L4 port settings. + +The explicit local source setting capabilities will lead to an overall: + +- "single NA(P)T" mode in case of a destination NA(P)T-less mode; or +- "double NA(P)T" mode in case of a destination NA(P)T-full mode. + +##### 6.16.1.2.6 Protocol translation (between V4 and V6) + +Protocol translation (NAPT-PT) can be controlled by the PD-PE by adding to the same ITU-T H.248 context, two terminations whose media descriptors have different address-type values in the "c=" line. + +NOTE – It is recommended that the PD-PE takes precaution if setting up streams with both fully specified and under specified address and/or port towards the same realm in a PE-PE, as this could otherwise lead to + +conflicting address or port assignments. The exact mechanism for how clashes are avoided is beyond the scope of this profile. + +#### 6.16.1.3 Support of hosted NAT traversal + +"Hosted NAT Traversal" relates to "assisting remote NAT/NAPT traversal" for the remote (peer) IP connection endpoints from PE-PE/PD-PE point of view. This relates to an interim NA(P)T device from border gateway (BGW) perspective. The remote IP address information cannot be retrieved from the Remote Descriptor. The "Hosted NAT Traversal" function is controlled by the PD-PE using the IP NAPT Traversal package (ipnapt). Using the napt package, the PE-PE is requested to perform media latching, i.e., listen for incoming media and latch to the remote address information of that media. + +When Hosted NAT Traversal is applied to a stream associated with multiple flows (for example RTP and RTCP), the PE-PE shall perform individual latching and/or re-latching on the various flows. This means that an RTP and an RTCP flow of a single stream can be latched to different remote addresses and/or ports. + +#### 6.16.1.4 QoS marking + +The Differentiated Services package enables the PD-PE to control the setting of the DSCP value for all packets leaving the PE-PE. + +##### 6.16.1.4.1 Copying DSCP/ToS values from the ingress to egress + +The copy mechanism is specified in Amendment 1 to ITU-T H.248.52 + +##### 6.16.1.4.2 Auditing the "Per-Hop Behaviour" + +The per-hop behaviour (PHB) concerning "MGC-signalled QoS marking" versus "copying of QoS values" may be explicitly controlled (and audited) using *Differentiated Services package version 2*, see Amendment 1 to H.248.52. + +The *Differentiated Services package version 1* does not allow to audit the behaviour, see the note at the end of clause 7.6.1.3 in Amendment 1 to [ITU-T H.248.52]. + +#### 6.16.1.5 Bandwidth control-reservation, allocation and policing + +The PD-PE should support different *resource control modes* in order to handle different types of user equipment (UE), customer premises equipment (CPE) and/or transport QoS capabilities (see clause 6 of [ITU-T Y.2111]). + +There are two basic *resource control modes* (see clause 6.1.1 of [ITU-T Y.2111]): + +- 1) Push mode: The PD-PE makes the authorization and resource control decision based on policy rules and autonomously instructs the PE-PE to enforce the policy decision. +- 2) Pull mode: The PD-PE makes the authorization decision based on policy rules and, *upon the request* of the PE-PE, re-authorizes the resource request and responds with the final policy decision for enforcement. + +The support of the "push mode" is typically inherent for ITU-T H.248 controlled resource (e.g., QoS) control mechanisms. The "pull mode" requires the support of the "pull mode package" [ITU-T H.248.55] in order for the PD-PE to determine the correct policy request (see clause 6.16.1.17 for further information). The remainder of this clause deals with how the PD-PE requests policy enforcement. + +Resources are reserved independently per gate. For each gate, reservation of local resources for handling incoming and outgoing traffic is achieved by setting the appropriate properties in the Local and Remote Descriptors. Only one session description shall be included in each Stream Descriptor. Hence, the ReserveValue and ReserveGroup properties should not be used. + +The function of bandwidth control (which relates to bit- and byte rate control in this profile) is structured in following clauses: + +- admission control (AC; clause 6.16.1.5.1); +- traffic descriptor (clause 6.16.1.5.2); +- bandwidth reservation and allocation (clause 6.16.1.5.3); and +- traffic policing (clause 6.16.1.5.4). + +##### 6.16.1.5.1 Admission control + +Admission control (AC) is defined in [ITU-T Y.2111] for the PE-PE (MG role) level. There is no concept of a call in ITU-T H.248 MGs due to the separation of call and bearers in the ITU-T H.248 model, which means that AC translates in a context admission control (CoAC; see also [b-ITU-T H-Sup.6]) and stream admission control (StAC) on PE-PE side. + +The StAC and CoAC are triggered with the first incoming ADD.request command. At that point a decision is taken on whether the new context can be established or not. + +The StAC is triggered whenever a modification of an existing ITU-T H.248 context, e.g., in terms of traffic descriptor, is requested. At that point a decision is taken on whether the context modification can be accepted or not. + +###### 6.16.1.5.1.1 Admission control in this profile + +The PE-PE AC is based on the requested ITU-T H.248 stream level usage parameters and already established Contexts. The stream level usage parameters are given by the ITU-T H.248 Media Descriptor in the ADD.request (and MODIFY.request) commands. The "usage parameters" as input for the AC of this profile are mainly related to "bandwidth" information (see next clause on "traffic descriptor"). + +Specific AC algorithms could principally follow a deterministically or a statistically based multiplexing model. Concrete algorithms are implementation specific, thus out of scope of this profile. + +The *result* of an admission control (here CoAC or StAC) is either an *accept* or a *reject* decision. + +NOTE – Step 2 in Figure 4 of [b-ETSI TS 183 018] shows an accept decision, which is implicitly given by the command reply on the ADD.request for the IP termination. A reject decision would be indicated by an appropriate ITU-T H.248.8 error code in the reply. + +##### 6.16.1.5.2 Traffic descriptor + +A *traffic descriptor* is the set of traffic parameters that is used to capture the traffic characteristics of an IP flow (see clause 3.2.10 of [b-ITU-T Y.1221]). The traffic parameters for an ITU-T H.248 Stream of an ITU-T H.248 IP Termination are direction-independent and given by either: + +- 1) an explicit specification via: +the "b=" line in the SDP description of the Local Descriptor and Remote Descriptor; or +the properties of the Traffic Management package, or +- 2) an implicit specification via: +the "m=" line in the SDP description of the Local Descriptor and Remote Descriptor (e.g., traffic usage estimate based on SDP media type and further mode of operation information). + +NOTE – There is no concept of a *traffic contract* explicitly used in the scope of this Profile version, because specific QoS classes (see [b-ITU-T Y.1541]) are not signalled per termination. Nevertheless, the "QoS marking" information (see clause 6.16.1.4) could be used for QoS class indications, but such concepts are orthogonal to profile specifications, therefore out of scope of this Recommendation. + +##### 6.16.1.5.3 Bandwidth reservation and allocation + +###### 6.16.1.5.3.1 SDP "b=" line for constant bit-rate traffic + +The amount of required bandwidth for sending packets is expressed using the "b=" line of the SDP description contained in the Remote Descriptors. + +The amount of required bandwidth for receiving packets is expressed using the "b=" line of SDP description contained in the Local Descriptors or using one of the properties (*tman/pdr* or *tman/sdr*) of the traffic management package. + +###### 6.16.1.5.3.2 Properties of the Traffic Management package for variable bit-rate traffic + +The Traffic Management package (*tman* version 1) should be used in case of variable bit rate traffic. There are then two semantics for some *tman* properties. *All* properties may be applied for bandwidth *policing*. The two properties *tman/pdr* and *tman/sdr* would be used additionally for bandwidth *reservation* (see note). + +NOTE – The property *tman/pol* indicates whether just reservation is applied ('OFF'), or whether both semantics are in use ('ON'). The semantic for 'OFF' is going beyond the property definition in *tman* version 1 package. These *tman* properties may be considered as elements of a *traffic descriptor*, i.e., information elements used for admission control (besides policing). + +###### 6.16.1.5.3.3 Resource reservation protocol + +When the PD-PE and PE-PE are operating in a pull mode the RSVP protocol for bandwidth reservation may be supported through the use of the RVSP Extension package (*rsvp* version 1). + +###### 6.16.1.5.3.4 Examples for bandwidth reservation + +See Annex F of [b-ETSI TR 183 068]. + +##### 6.16.1.5.4 Bandwidth policing + +Policing of incoming traffic can be enabled using the Traffic Management package. Policing on incoming traffic can be set independently for each gate. + +The properties of the Traffic Management package shall be set to values that are compatible (see note) with the "b=" line value of the Local Descriptor. + +NOTE – The term "compatible" means that the b-line and the traffic management represent identical bandwidth value with respect to the protocol layer they are defined upon: + +- Constant bit rate: "b=" line = *tman/pdr* = *tman/sdr*; +- Variable bit rate: "b=" line = *tman/pdr*. + +###### 6.16.1.5.4.1 Statistics for bandwidth policing + +Policing of incoming traffic is related to policy rules based on the following: + +- policy *conditions* on: + - "IP byte-rate" parameter(s) (peak-rate and/or sustainable-rate); and/or + - "IP packet size" parameter(s) (see [ITU-T H.248.53]; signalling method not supported by this profile); and +- policy *actions*: + - *accept* conforming IP packet; or + - *silently discard* non-conforming IP packet (in case that profile is not supporting the *tmanr* package); or + - *discard* non-conforming IP packet *and record* event by *tmanr* statistics (see clause 6.16.1.6.3.3). + +The policy actions are executed per IP packet. + +##### 6.16.1.5.5 Non-specification of tman properties + +If no properties of the Traffic Management package are provided, the PE-PE will not perform traffic policing. If only the tman/pol property set to ON is present, traffic policing shall not be done based on the b-line value, i.e., the policing function cannot be activated at this stage. + +Summary on bandwidth control actions: + +**Table 6-101 – Bandwidth control actions in relationship to *tman* version 1 properties** + +| ITU-T H.248 property usage | | | | | Semantic | +|-------------------------------|----------|--------------------------------|----------|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tman/pol | tman/pdr | tman/dvt | tman/sdr | tman/mbs | Bandwidth control actions | +| ON | Not sent | Not sent (use default) | Not sent | Not sent (use default) | No traffic management. | +| OFF or not sent (default=OFF) | Not sent | Sent or not sent (use default) | Not sent | Sent or not sent (use default) | No traffic management. | +| OFF or not sent (default=OFF) | Sent | Sent or not sent (use default) | Not sent | Sent or not sent (use default) | No traffic management
The property tman/pdr may be used for bandwidth reservation and allocation in the receiving direction in accordance to clause 6.16.1.5.3. | +| OFF or not sent (default=OFF) | Not sent | Sent or not sent (use default) | Sent | Sent or not sent (use default) | No traffic management
The property tman/sdr may be used for bandwidth reservation and allocation in the receiving direction in accordance to clause 6.16.1.5.3. | +| OFF or not sent (default=OFF) | Sent | Sent or not sent (use default) | Sent | Sent or not sent (use default) | No traffic management
The property tman/pdr or tman/sdr may be used for bandwidth reservation and allocation in the receiving direction in accordance to clause 6.16.1.5.3. | +| ON or not sent (default=ON) | Sent | Sent or not sent (use default) | Not sent | Sent or not sent (use default) | Single stage policer (pdr, dvt)
The property tman/pdr may be used for bandwidth reservation and allocation in the receiving direction in accordance to clause 6.16.1.5.3. | +| ON or not sent (default=ON) | Not sent | Sent or not sent (use default) | Sent | Sent or not sent (use default) | Single stage policer (sdr, mbs)
The property tman/sdr may be used for bandwidth reservation and allocation in the receiving direction in accordance to clause 6.16.1.5.3. | +| ON or not sent (default=ON) | Sent | Sent or not sent (use default) | Sent | Sent or not sent (use default) | Dual stage policer ((pdr, dvt); (sdr, mbs))
The property tman/pdr or | + +**Table 6-101 – Bandwidth control actions in relationship to *tman* version 1 properties** + +| ITU-T H.248 property usage | | | | | Semantic | +|----------------------------|-----------------|-----------------|-----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------| +| tman/pol | tman/pdr | tman/dvt | tman/sdr | tman/mbs | Bandwidth control actions | +| | | | | | tman/sdr may be used for bandwidth reservation and allocation in the receiving direction in accordance to clause 6.16.1.5.3. | + +#### 6.16.1.6 Usage metering and statistics reporting + +Usage metering is supported by the statistics defined in the network and other packages. Such statistics may be notified to the PD-PE when a stream is removed (and stats explicitly requested by the PD-PE) or a termination is subtracted from a context (e.g., at the end of a session). They provide information about: + +- 1) resource usage, e.g.,: + - the duration of the time a termination has been in a context; + - the traffic volume, e.g., number of octets sent and received. +- 2) grade of service (GoS)/quality of service (QoS), e.g.,: + - the packet delay variation or packet transfer delay. + +The "number of octets" for the case of *nt* package based measurement is calculated as defined in clause E.11.4 of [ITU-T H.248.1] . + +The number of discarded packets due to ITU-T H.248.43-based, explicit source filtering may be reported on basis of the *gm/dp* statistic. + +The number of discarded packets due to ITU-T H.248.37-based, implicit source filtering may be reported on basis of the *lstat/dp* statistic. + +The number of discarded packets and octets due to ITU-T H.248.53-based, explicit traffic filtering may be reported on basis by the *tmanr* statistics. + +##### 6.16.1.6.1 Statistics for media/transport-agnostic IP packets + +The available statistics for the IP streams and terminations of a dedicated context are dependent of the IP-to-IP interworking mode (see clause 3.2.6). + +##### 6.16.1.6.2 Traffic volume related Statistics + +Figure 6-4 provides an overview of different traffic volume related statistics, which might be useful for the various IP-to-IP interworking modes (e.g., media-agnostic, media-aware, transport-protocol agnostic). + +###### 6.16.1.6.2.1 General case + +The general case relates to media-agnostic IP-to-IP interworking (NOTE – this relates to [b-ETSI ES 283 018], the ITU-T H.248 Ia profile version 1). Traffic volume related statistics are only accessible by the *nt* package. + +![Figure 6-4: Overview of supported statistics – Traffic volume related statistics on different protocol layers. The diagram shows five vertical bars (a-e) representing different traffic volume statistics across six protocol layers (L1-L6). Bar 'a' shows transport overhead at L1-L3. Bar 'b' shows reported traffic volume at L1-L3. Bar 'c' shows reported traffic volume at L1-L4. Bar 'd' shows transport overhead at L1-L3. Bar 'e' shows reported traffic volume at L1-L4. A legend indicates that red dotted patterns represent 'Transport overhead' and green cross-hatched patterns represent 'Reported traffic volume'. A table on the right lists the protocol stack layers and their corresponding protocols.](6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg) + +| Principal protocol stack for ITU-T H.248 IP terminations | | +|----------------------------------------------------------|------------------------------------| +| e.g., audio codec | Application data | +| RTP, UDPTL, ... | Application level framing protocol | +| L4: UDP, TCP, ... | Transport protocol | +| L3: IP | Network protocol | +| L2 | | +| L1 | | + +Q.3303.2 v2(14)\_F6-4 + +Legend: █ Transport overhead █ Reported traffic volume + +Figure 6-4: Overview of supported statistics – Traffic volume related statistics on different protocol layers. The diagram shows five vertical bars (a-e) representing different traffic volume statistics across six protocol layers (L1-L6). Bar 'a' shows transport overhead at L1-L3. Bar 'b' shows reported traffic volume at L1-L3. Bar 'c' shows reported traffic volume at L1-L4. Bar 'd' shows transport overhead at L1-L3. Bar 'e' shows reported traffic volume at L1-L4. A legend indicates that red dotted patterns represent 'Transport overhead' and green cross-hatched patterns represent 'Reported traffic volume'. A table on the right lists the protocol stack layers and their corresponding protocols. + +**Figure 6-4 – Overview of supported statistics – Traffic volume related statistics on different protocol layers** + +###### 6.16.1.6.2.2 RTP case (general) + +"Media-aware" IP terminations with RTP as application level framing protocol may use traffic volume based statistics via the RTP package: + +- packet granularity: +RTP packets sent and/or received (NOTE – packet level statistics could already provide useful volume measurements in case of RTP packets with constant length). +- octet granularity: +RTP octets sent/received statistics are coupled with *nt* package statistics, i.e., these statistics also include RTP padding, RTP header information and UDP transport overheads. Such overhead is excluded in the RTP application data specific statistics (see clause 6.16.1.6.2.3). + +###### 6.16.1.6.1.2.3 RTP case: Application data + +The RTP Application data package provides support for explicit octet count statistics concerning media traffic, i.e., the RTP payload volume. + +The IP layer octets count statistics package provides traffic volume statistics on IP layer for IP version 4 or 6. The ITU-T H.248 *ipocs* package (see clause 6.16.1.6.2.1) is *not* supported by this profile version. + +##### 6.16.1.6.3 Statistics for packet filtering + +###### 6.16.1.6.3.1 Address policing: explicit remote source transport address filtering + +Filter conditions based on source transport address information for remote IP endpoints may be enabled with gate management properties (see also clause 6.16.1.1). The number of discarded packets due to remote source filtering may be reported on the basis of the *gm/dp* statistic. + +###### 6.16.1.6.3.2 Address policing: implicit remote transport address filtering due to latching + +The *lstat/dp* statistic is used for recording the number of discard packets due to implicit filtering of the latching function. See also clauses 1.3 and 6.6.7.2 of [ITU-T H.248.37]. + +###### **6.16.1.6.3.3 Traffic policing: byte-rate policing** + +See clause 7.4 of [ITU-T H.248.53]. + +###### **6.16.1.6.3.4 Traffic policing: packet-size policing** + +Not supported by this profile specification. + +#### **6.16.1.7 RTCP handling** + +Handling of RTCP is already partially addressed by clause 6.16.1.1. This clause defines further procedures for RTCP. + +##### **6.16.1.7.1 RTCP transport address allocation** + +###### **6.16.1.7.1.1 Local RTCP IP transport address allocation** + +In line with the recommendations of [b-IETF RFC 3605], non-contiguous RTCP port numbers (identified via the "a=rtcp" media attribute) shall not be used by the PE-PE in its Local Descriptor (LD). + +Local ports for RTCP are implicitly allocated by the PE-PE whenever instructed to do so by the PD-PE via the gm/rsb=ON property. The PE-PE must follow the port allocation rules as defined in section 11 of [b-IETF RFC 3550], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream. . + +If the gm/rsb property is set to OFF, then no RTCP port is allocated in conjunction with an RTP stream. This behaviour is irrespective of the presence of the "a=rtcp" attribute in the related RD. + +###### **6.16.1.7.1.2 Remote RTCP transport address representation/usage, implicit allocation of IP transport address for RTCP** + +RTCP ports are allocated either implicitly or explicitly when support of RTCP is required. RTCP support and RTCP transport address and allocation is controlled as by the gm/rsb property and the "a=rtcp" media attribute line in the Remote Descriptor. If RTCP is sent within the same stream as RTP then RTCP port allocation is handled as follows: + +- gm/rsb=OFF or gm/rsb omitted. + +RTCP support is not required. No pinhole is opened for received RTCP packets. No RTCP packets are sent and any received RTCP packets are silently discarded. This is irrespective of whether the "a=rtcp" attribute is present in the Remote Descriptor. + +- gm/rsb=ON & "a=rtcp" media attribute line not present. + +RTCP support is required. A pinhole is opened for received RTCP packets. The PE-PE must follow the port allocation rules as defined in section 11 of [b-IETF RFC 3550], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream in the Local Descriptor (see clause 6.16.1.7.1.1). RTCP packets are sent to the same address and contiguous port number to the RTP port as specified in the Remote Descriptor. + +- gm/rsb=ON & "a=rtcp" media attribute line present. + +RTCP support is required. A pinhole is opened for received RTCP packets. The RTCP port and optionally address are explicitly identified by the included "a=rtcp" media attribute line. The MG must follow the port allocation rules as defined in section 11 of [b-IETF RFC 3550], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream in the Local Descriptor (see clause 6.16.1.7.1.1). If the "a=rtcpmap" media attribute line in the Remote Descriptor contains an address it is used as destination when sending RTCP packets. The destination port for RTCP packets is always explicitly identified via the "a=rtcp" media attribute line in the Remote Descriptor. + +###### 6.16.1.7.1.3 Unsuccessful transport address allocation + +In line with clause 6.16.1.7.1.1, neither a fully specified RTCP port nor RTCP address are ever used by the PD-PE in the Local Descriptor. Therefore, unsuccessful port/address allocation can only occur due to there being insufficient resources on the PE-PE to allocate the (contiguous) RTCP port. Unsuccessful scenarios result in the PE-PE responding with ITU-T H.248 error code #510 ("Insufficient Resources"). + +##### 6.16.1.7.2 RTP/RTCP to ITU-T H.248 stream mapping + +In line with clause 6.16.1.7.1.1, a single common ITU-T H.248 stream is always used for RTP and its associated RTCP flow. + +##### 6.16.1.8 RTCP forwarding + +Every RTP session may be accompanied by RTCP control flows. Blocking (by the PE-PE) of such RTCP packets may violate the end-to-end RTP/RTCP protocol and/or the served applications. However, security threats or specific RTCP reports types may request for dedicated RTCP packet policing rules. + +##### 6.16.1.8.1 Conditions for RTCP packet policing + +Conditions for RTCP packet policing are typically based on following n-tuple elements: + +- IP *port* for RTCP flow, +- RTCP *packet type* codepoint, +- RTCP synchronization source (*SSRC*) codepoint, +- RTCP source description information element (e.g., canonical name (*CNAME*) codepoint), and/or +- RTCP *block type* codepoint in the case of RTCP extension reports (XR, HR). + +##### 6.16.1.8.2 Forwarding of regular RTCP traffic + +"Regular" RTCP packets shall be understood in the scope of this Recommendation as packet units with a packet type value equal to a value from the range of {192, 193, 200 to 206}. Thus, regular traffic excludes extended report (XR) and HR RTCP packets. Regular RTCP packets must be basically forwarded towards the RTP endpoint. + +Regular RTCP packets are unambiguously identified by the 3-tuple of {packet type, SSRC, CNAME}. + +Thus, RTCP packets with e.g., an incorrect {SSRC, CNAME} combination may be blocked. + +##### 6.16.1.8.3 Handling of RTCP XR/HR traffic + +Extended reports (XRs) and XR-based high resolution reports, – i.e., RTCP reports with a packet type value equal to 207 –, carry measurement data from measurement points (PE-PE) to reporting points (RPs). Such measurement reports do not have necessarily an end-to-end significance; their scope may be e.g., limited to a single IP domain or "RTP network segment". The MG may have to apply dedicated forwarding policy rules for such RTCP packets. Concrete policy rules are for further studies. + +##### 6.16.1.9 Media inactivity + +Application data inactivity detection (also known as media inactivity detection) may have multiple, different use cases as cited in [12] e.g.,: + +- detection of interrupted IP routes, +- detection of released RTP endpoints, +- detection of hanging SIP/RTP sessions (see note), or + +- detection of deadlocks in IP latching scenarios. + +NOTE – The notation of "SIP/RTP session" relates to a SIP-controlled RTP session, which implies a RTP session on PE-PE level and a SIP session on PD-PE level. There might be a hanging RTP session (leg) or a SIP session (leg). The application of [ITU-T H.248.40] is able to address both failure scenarios. + +In all use cases, the *adid v1* package (with possible different *timing* and/or *direction* configurations of the detection logic) is used to report the detected inactivity. + +The *adid/ipstop* event is enabled on a per ITU-T H.248 IP termination basis, i.e., not on ITU-T H.248 stream level. The PE-PE monitors all IP transport ports associated with the termination. + +##### 6.16.1.10 IP domain/realm indication + +##### 6.16.1.10.1 Codepoint and format/encoding + +The IP realm identifier (i.e., ITU-T H.248 property *ipdc/realm*) may be sent to the PE-PE in order to indicate the IP domain/realm of the ITU-T H.248 IP termination. The IP realm identifier is a flexible string and may convey a numerical IP address, domain name or mutually understood name (e.g., "in" and "out", "1" and "2", etc.) (see Note). The ephemeral termination string layout ("*ip///*") is still used in this version of the profile but the "interface" field is always set to CHOOSE by the PD-PE in an Add request command and is assigned by the PE-PE. The PE-PE may use the "interface" field to denote a physical or logical interface on the PE-PE. + +NOTE –The usage of the IP realm identifier in this version of the profile is generalized and goes somewhat beyond the original definition (by [ITU-T H.248.41]) of the identifier. This is due to the following reasons: + +- syntax: backward compatibility with Ia profile version 1 (format/encoding syntax by field "Interface" in TerminationID); and +- semantic: generic "domain identifier" for "domain concepts" beyond IP address spaces. Such "domain concepts" could be related to specific technologies, specific protocol layers, virtual private network types, etc. + +##### 6.16.1.10.2 Unsuccessful indication + +If the value of the IP realm identifier sent by the PD-PE within the [ITU-T H.248.41] package property cannot be recognized by the PE-PE, the PE-PE will fail to create the IP based ITU-T H.248 termination and replies with an error descriptor using the error code 449 (Unsupported or unknown parameter or property value). + +##### 6.16.1.10.3 Fix assignment per termination lifetime + +The PD-PE may or may not choose to assign IP realm identifier when communicating with the PE-PE e.g., not sent if IP Realm configured on the PE-PE. If the PD-PE assigns IP Realm, then this must be communicated at termination seizure (Add). The value of IP Realm shall be applied to all streams associated with the termination. The IP Realm identifier indicates the IP domain/realm of the ITU-T H.248 termination and cannot therefore be changed after the initial assignment at Add. + +The IP Realm identifier cannot be subsequently changed in a Modify command once assigned to a termination. Only an identical/unchanged setting of IP realm identifier may be sent in a Modify command. If the PD-PE attempts to change the IP realm on an existing termination via a Modify command, the PE-PE will reply with an error descriptor using the error code 501 (Not implemented). + +##### 6.16.1.10.4 Number of IP realms/domains + +The PE-PE supports typically multiple logical IP interfaces, which may belong to different IP address realms. Following principal use cases may be distinguished: + +- Single realm: + +All IP interfaces of the PE-PE, and therefore all created ITU-T H.248 IP terminations, belong to the same IP address space. + +2) Multiple realms (N private realms and M public realms with $N + M \geq 2$ ): + +- The two ITU-T H.248 IP terminations of an ITU-T H.248 context may belong to the same IP address space or different realms. +- The PE-PE may be principally connected to many IP address realms. For instance, N private domains or one public and M private domains. Furthermore, there could be overlapping address spaces between multiple private domains (see note). The ITU-T H.248.41 package property is used to indicate each realm. + +In general, if [ITU-T H.248.41] property is omitted, according to the ITU-T H.248.41 procedures the configured default IP realm is applied by the PE-PE. + +NOTE – Overlapping IP address spaces could be discriminated by separation e.g., via physical (IP) interfaces, via a L3VPN technology (e.g., IP security (IPsec) in tunnel mode), or via a L2VPN technology (e.g., VLANs). + +All above use cases are related to specific PE-PE deployment scenarios due to the static nature of a connection of a particular IP domain with the PE-PE. + +##### 6.16.1.10.5 IP realm availability + +The PE-PE may support IP realm availability (*ipra*) package to facilitate the detection of available IP realms by the PD-PE. + +The PD-PE can audit the "Available realms" (*ipra/ar*) property with the AuditValue command to get the information regarding the available realms. If the "Available realms changed" (*ipra/arc*) event is set, whenever the available realms change the information regarding the change is reported by the PE-PE. + +#### 6.16.1.11 One-stage and two-stage PE-PE resource reservation + +The SDP offer/answer model allows offers and answers to be generated with or without "m=" and "b=" lines. + +The normal case is when both information contained in SDP "c=" and "m=" lines is available to the PD-PE and at the time it requests the PE-PE to create a termination, it is referred to as one-stage reservation. This means both "c=" and "m=" line information can be passed to the PE-PE in a single step. + +If information contained in SDP "c=" line, but "m=" and "b=" lines are not available to the PD-PE at the time it requests the PE-PE to create a termination, the PD-PE refrains from sending "m=" and "b=" lines to the PE-PE. In order for media plane communication to take place through the PE-PE, the PD-PE must, at a later stage, come back with at least "m=" lines to the PE-PE. This would typical happen at a subsequent offer/answer exchange on the SIP plane. Such a reservation procedure is referred to as two-stage reservation. + +These actions at the Rw interface can be described with the following two-stage PE-PE resource reservation procedure: + +1. PD-PE requests the PE-PE to reserve an IP address (via the LD) in accordance with the specified IP realm and may also optionally reserve an IP port. In the former case, the SDP in Local and/or Remote Descriptors does not contain "m=" nor "b=" lines. In the latter case, the SDP in Local and/or Remote Descriptors does contain an underspecified "m=" line. The PD-PE does not request the PE-PE to open any pinhole at this stage. +2. PD-PE requests the PE-PE, in addition to the previously assigned IP address, to also allocate port(s) (if not done at stage 1) and optionally bandwidth or to optionally further specify the previously allocated port together with an optional bandwidth. The SDP in + +Local and/or Remote Descriptors does contain "m=" and optionally "b=" lines. The PD-PE may request the PE-PE to open pinholes at this stage. + +The command level details of one-stage and two-stage reservation procedures are specified in clause 6.17, where one-stage is considered the default scenario and thus only the specifics of two-stage reservation are called out. + +Both stages in two-stage reservation are part of the overall session establishment phase. + +##### 6.16.1.12 Hanging termination detection + +For the correct operation of a PE-PE, synchronization of termination information between the PD-PE and PE-PE is essential for the traffic, maintenance and charging purposes. In some cases, the PD-PE may have lost a record of a termination but the termination is not subtracted on PE-PE. The *hangterm/thb* event defined in [ITU-T H.248.36] may be used to solve this problem. After a period of message inactivity the PE-PE may issue a periodic Notify command on the concerned termination and the PD-PE may use this to check if it has a record of the termination or not. The time period for this Notify may be parameter driven. Optionally the hangterm/thb event may result in an audit of *PD-PEinfo/db* property in order to determine the PD-PE information string. + +##### 6.16.1.13 Real time statistics reporting + +##### 6.16.1.13.1 Overview of conditional reporting + +A PD-PE normally obtains bearer related statistics through periodic auditing of the ITU-T H.248 Statistics Descriptor or at the time of deletion of a stream or subtraction of a termination. However, in both cases, there is an interval of delay between when a reporting condition occurs on a PE-PE (e.g., a statistic threshold being passed) and when the PD-PE learns of the statistic. In many cases, such a delay is of no consequence. However, in some cases, the PD-PE may require to be immediately informed of a given statistical threshold condition occurring. In this case, the PD-PE must use the [ITU-T H.248.47] Statistic Conditional Reporting package. This package may be applied to multiple statistics. The PD-PE should set the reporting thresholds and ranges as appropriate and must specify at least one "condition" for conditional reporting (i.e., the PD-PE must signal at least one condition per requested packageID/statisticID item). + +The exact statistics and reporting conditions are determined by the operator's configuration based on the application/service required. + +##### 6.16.1.13.2 Basic conditional reporting + +Basic conditional reporting uses the protocol elements of the *Statistic Conditional Reporting* package version 1 (i.e., in the 2007 edition of ITU-T H.248.47 which is has now been superseded by the 2008 edition). This allows the definition of many, but limited reporting conditions. + +##### 6.16.1.13.3 Extended conditional reporting + +Extended conditional reporting uses the protocol elements of the *Statistic Conditional Reporting* package version 2 [ITU-T H.248.47]. This package allows in addition: + +- to control whether a timestamp is reported with the detection of the (conditional reporting) events; and +- extends the reporting conditions with value-based metric conditions. + +#### 6.16.1.14 Transcoding + +Definition see clause 3.2.8. + +##### 6.16.1.14.1 Media types and formats (codecs) + +[b-ETSI TS 181 005] defines the codec services for TISPAN NGNs. It provides codec recommendations for *narrowband audio*, *wideband audio* and *video* media. + +##### 6.16.1.14.2 Decision for transcoding + +The decision for transcoding may be principally reached at the beginning or later during the lifetime of a call/session. The corresponding triggers (for transcoding decisions) from PE-PE side would be either related to ADD or MODIFY request commands. + +###### 6.16.1.14.2.1 Decision at stream/termination creation + +The first ADD.request (of a new Context) for a new stream/termination provides either a full specification (by the PD-PE) of the media type and format, or an under-specification, which is then completed by the PE-PE. + +The subsequent request for the peer stream/termination (within this Context) is then leading to a possible transcoding decision. The PE-PE is comparing the SDP information elements for media description of the two ITU-T H.248 Stream Descriptors: + +- In case of identical media type and formats then there will be no transcoding. The PE-PE may even handle this stream in media-agnostic mode. +- In case of different media type or/and formats then the PE-PE may decide for transcoding support, or reject the request with an appropriate ITU-T H.248.8 error code (e.g., due to temporarily lacking resources for transcoding). + +###### 6.16.1.14.2.2 Decision at stream/termination modification + +MODIFY.request commands for existing streams/terminations may lead to a decision for transcoding. + +#### 6.16.1.15 VPN identification + +##### 6.16.1.15.1 VLAN marking + +The PE-PE VLAN tagging behaviour is summarized in the following table: + +**Table 6-102 – VLAN marking using *vlan* version 1 package** + +| ITU-T H.248 property usage | | Semantic | +|------------------------------------------|------------------------------------------|--------------------------------| +| vlan/pri | vlan/tags | Action | +| Sent | Value smaller than "4 096" sent | Apply VLAN tagging accordingly | +| Sent | Not sent (use provisioned default value) | Apply VLAN tagging accordingly | +| Not sent (use provisioned default value) | Value smaller than "4 096" sent | Apply VLAN tagging accordingly | +| Not sent | Not sent | Do not apply VLAN tagging | +| Sent or not sent | Value "4 096" sent | Do not apply VLAN tagging | + +#### 6.16.1.16 Topology hiding function + +Topology hiding may basically be related to the: + +- hiding of "*remote* topology information", i.e., the PE-PE provides *local* support for topology hiding to network elements "*behind*" the PE-PE; +- hiding of "*local* topology information", i.e., the PE-PE provides *local* support for topology hiding of the PE-PE *itself* in one-way direction for the egress media-path. + +Topology hiding functions (THFs) are required on PD-PE (MGC) level for the IP signalling-path and on PE-PE (MG) level for the IP media-path, see [ETSI TS 187 003] + +NOTE 1 – THF relates basically to the hiding of (network element) local address information ("network topology hiding"). Address information is primarily related to the L3 addresses, which are used in the IP layer and by IP application protocols (like SIP). + +NOTE 2 – PE-PE related THF scenarios are e.g., outlined by clause A.2 of [b-ETSI TS 187 003] . For instance, the so-called topology hiding gateway (THIG) function relates to a THF on interconnection border control function (IBCF) (MGC) level for the IP signalling-path and on I-PE-PE (MG) level for the IP media-path in the IP multimedia subsystem (IMS) interconnect scenario (Figure A.6 of [b-ETSI TS 187 003] ). + +##### 6.16.1.16.1 THF for the IP signalling path + +The assumption by this ITU-T H.248 profile specification (and decomposed gateway architecture) is a media-path decoupled signalling path. Any THF for the IP signalling-path is thus out of scope of this Recommendation. + +##### 6.16.1.16.2 THF for the IP media /bearer path + +This clause introduces topology hiding functions (THF) for the IP media/bearer path on different protocol layers. + +###### 6.16.1.16.2.1 THF on IP network protocol layer (L3) + +THF on IP network protocol layer (L3) includes IP address information and other IP protocol control information (PCI) elements and Internet control message protocol (ICMP). + +###### 6.16.1.16.2.1.1 THF on IP address information elements + +THF in the IP media-path may be basically achieved by NAT within the end-to-end IP connection. *Remote* NAT devices may support the hiding of PE-PE local IP addresses, i.e., LS (A) and LD (A) information (see also Figure 6-2). + +PE-PE-local THF support: + +- hiding of "*remote* topology information" via PE-PE-local NA(P)T (see clause 6.16.1.2) may used for hiding of remote IP address information (i.e., RS(A) or/and RD(A) information). +- hiding of "*local* topology information" via explicit source address setting capability (via *gm* package properties, see e.g., clause 6.17) with regards to the LS (A) value. + +NOTE – Properties *gm/esas* and *gm/lsa* for LS (A) control, and *gm/esps* and *gm/lsp* for LS (P) control. + +###### 6.16.1.16.2.1.2 THF on other IP PCI elements and ICMP + +THF on L3 is furthermore supported by: + +- IP time-to-live (TTL) value reset in B2BIH mode + +NOTE – Not in IPR mode. + +- ICMP: there is an ICMP traffic flow for each IP interface, however, the ICMP flow does *not* appear as a flow component within ITU-T H.248 IP streams (because ICMP is an IP layer service, out of control of ITU-T H.248). + +###### 6.16.1.16.2.2 THF above the IP layer + +IP address information may be carried by media-path protocols above the IP layer. + +RTP packets may be forwarded transparently (e.g., in transport-protocol agnostic mode) or terminated like in media-aware PE-PE mode. Termination implies a *Back-to-Back RTP Endsystem* (B2BRE mode) because each ITU-T H.248 IP termination provides an IP host and RTP endsystem function. Thus, RTCP packets are sourced/sinked by the PE-PE in that mode. The source description (SDES) RTCP packet is mandatory, as well as the SDES item 'CNAME' (*Canonical End-Point Identifier*). + +[b-IETF RFC 3550] recommends that: + +"The CNAME item SHOULD have the format "user@host", or "host" if a user name is not available as on single-user systems. For both formats, "host" is either the **fully qualified domain name** of the host from which the real-time data originates ... **or** the standard ASCII representation of the host's **numeric address** on the interface used for the RTP communication." + +Such a CNAME format would advertise topology information via RTCP. THF for RTP/RTCP could be achieved e.g., either via secure RTP (SRTP) [b-IETF RFC 3711] or by just encrypting the SDES CNAME item (see section 9.1 of [b-IETF RFC 3550]). + +##### 6.16.1.17 Pull Mode QoS resource control + +If a PE-PE supports pull mode operation, the PD-PE may utilise this functionality through the use of the "Pull mode package" [ITU-T H.248.55]. + +In order that the PE-PE may detect and forward resource requests to the PD-PE, the QoS resource reservation event shall be set. When the *plm/rdrr* event is set on the ROOT termination of the PE-PE, the *brav* and *brpv* parameters should be also included in order to specify the signalling address that the resource reservation signalling will be received. + +In the case where a PE-PE and PD-PE may serve multiple domains where requests may be received from, in order to indicate the appropriate domain, the PD-PE shall also send the 'Path coupled requests domains under MGC ownership' parameter (i.e., ITU-T H.248 property *plm/rdmo*) within the event. The pull mode QoS resource control is invoked when the PE-PE receives a QoS request over dedicated path-coupled QoS signalling from the CPE to create a media stream. The PE-PE resolves the source identifier of the message and matches it with the *plm/rdmo* information to select the correct PE-PE for the service. The PE-PE then notifies the request via the QoS resource reservation event (i.e., ITU-T H.248 Event *plm/rdrr*) to the PD-PE in order to request the resource decision for the service. On receipt of the authorization token carried in the event, the PD-PE shall send a resource action request to the service control function (SCF) to retrieve the service information associated with the flow. The PD-PE makes the resource decision based on the service information and resource availability and then responds the PE-PE to enforce the policy decision (see clause 6.16.1.5). + +In order to support a CPE-requested QoS resource modification procedure the QoS resource modification event (i.e., ITU-T H.248 Event *plm/rdrm*) is set by the PD-PE. As in the request case above upon reception of a QoS resource modification from the CPE, the PE-PE resolves the source and if it matches sends the notification to the PD-PE via the *plm/rdrm* event. + +In order to support a CPE-requested QoS resource release procedure QoS resource release event (i.e., ITU-T H.248 Event *plm/rdrl*) is set by the PD-PE. As in the request case above upon reception of a QoS resource release from the CPE, the PE-PE resolves the source and if it matches the PE-PE sends the notification to the PD-PE via the *plm/rdrl* event. + +#### 6.16.1.18 RSVP handling + +When the CPE uses RSVP to initiate the QoS resource reservation for the service flow, the PE-PE and the PD-PE are required to support the RSVP extension package for RSVP message handling. The PE-PE acts in different roles as sender and receiver for the corresponding two unidirectional data flows in the same session. + +The procedures specified in clause 6.6.2 of [ITU-T H.248.65] are applied when the PE-PE and the PD-PE are involved in the pull mode QoS resource control scenario using RSVP protocol. + +### 6.16.2 Overview of call independent procedures + +"Call independent" procedures are also known as "session independent" or "non-call related" procedures. + +#### 6.16.2.1 Introduction – Relation to ETSI TR 183 025 + +Session-independent procedures for [b-ETSI ES 283 018] are defined in [b-ETSI TR 183 025], which is an overall description for all ETSI defined ITU-T H.248 profile specifications, i.e., [b-ETSI TR 183 025] complements each profile specification. + +The set of profile-applicable call-independent procedures is primarily given by the supported ITU-T H.248 command API capabilities for AuditValue (see clause 6.7.5), AuditCapabilities (see clause 6.7.6) and ServiceChange (see clause 6.7.8), and supported packages (e.g., for overload control), by each profile. + +#### 6.16.2.2 Session-independent procedures + +Session-independent procedures are described in clauses 6.18 and 6.19. + +#### 6.16.2.3 PE-PE (MG) overload control + +[ITU-T H.248.11] may be used for controlling MG overload, by throttling and limiting the rate of ITU-T H.248 messages from MGC to MG. + +See clause 5.19.14 of [b-ETSI TS 183 018] for the procedure and for the command level details. + +#### 6.16.2.4 Failure handling procedures: interface failure + +Background: + +As an example clause 10.1.1.2.1 of [ITU-T Y.2111]: *"During the running of a media flow, if the PE-FE cannot provide the reserved QoS resource any longer for the media flow due to its interface failure, the PE-FE shall send a Resource Notification to the PD-FE on its own initiative."* + +Interface failures (e.g., failures of logical or physical IP interfaces, or physical Ethernet interfaces) could be generally addressed by ServiceChange procedures, for instance, ServiceChange with Method 'Forced', Reason '904', '905', or '907' (dependent on failure type) and on ephemeral terminations (see clause F.4.1.3 of [ITU-T H.248.1]). Clause 5.19 for MG failure, MG Termination failure and user plan failure of [ETSI TS 183 018] shall be applied. + +NOTE – Specific failure types could be addressed by dedicated ITU-T H.248 protocol elements, like for instance clause E.11.2 of [ITU-T H.248.1], [b-ITU-T H.248.13], [ITU-T H.248.36] or [ITU-T H.248.40]. This is for further study. + +## 6.17 Session dependent procedures (command level details) + +Clause 5.18 of [ETSI TS 183 018] shall be applied. + +## 6.18 Non-session related use cases + +Clause 5.19 of [ETSI TS 183 018] shall be applied. + +## 6.19 Session independent procedures (command level details) + +Clause 5.20 of [ETSI TS 183 018] shall be applied. + +# 7 Security considerations + +There might be several possible security threats at the Rw interface, such as denial of service, message disclosure by unauthorized snooping, unauthorized message creation and modification. + +In general, an attacker can surreptitiously intercept information, attempt to create unauthorized information, send modified or reordered information or all of the above. There might be a risk that an attacker can impersonate a MGC or a MG illicitly acquire (or both) and tamper the information. Even though the information is encrypted, reply attack might be possible. For these security threats, operators need to aware that sufficient authentication and encryption mechanisms are needed + +between MGC and MG as described in [ITU-T H.248.1]. To minimize the risk, the MG is needed to be properly configured so that only authorized MGC can access and exchange information each other, and particular attention on the credence and information integrity is necessary. + +In the case where ITU-T H.248 messages are open to an insecure domain, there is a risk that an attacker can impersonate, illicitly acquire and tamper information and execute replay attacks. To ensure the security of ITU-T H.248 messages, it is recommended to consider using IPSec or the interim authentication header (AH) scheme described in clause 10 of [ITU-T H.248.1]. + +If IPSec is used, IPSec authentication header (AH) provides data origin authentication, connectionless integrity and optional anti-replay protection of messages passed between the PD-PE and the PE-PE. Optionally, the IPSec encapsulation security payload (ESP) can be used to provide confidentiality of messages. + +If IPSec is not provided in transport, the interim AH scheme can be used to provide similar functions as those of IPSec AH. The interim AH scheme extends the ITU-T H.248.1 protocol header by adding an AH header. Note that the interim AH scheme cannot provide protection against eavesdropping and replay attacks. + +This version of the Rw ITU-T H.248 profile does not specify any security support, see clause 6.12. + +# Appendix I + +## Overview of specific policing functions in the policy enforcement physical entity + +(This appendix does not form an integral part of this Recommendation.) + +PE-PE is responsible for both session-dependent and session-independent policing. Session-independent policing through the Rw interface is out of scope of this Recommendation, although the categorization described in clause I.1 could apply to session-independent as well as session-dependent policing. + +Rw ITU-T H.248 profile version 2 only supports session-dependent policing. + +### **I.1 Categorization attempt** + +The PE-PE provides specific policy types, which could be categorized into following policing areas: + +#### **1. Address policing** + +Policy conditions are based on L3/L4 protocol control information (PCI) elements. + +#### **2. Traffic policing** + +Policy conditions are based on 'traffic descriptors', e.g., like sizes of protocol data units or/and correspondent data rates. + +#### **3. Media flow policing** + +Policy conditions are based on application level framing protocol (e.g., RTP) control information elements, e.g., RTP sequence numbers, timestamps, SSRCs, CNAME in case of RTP. The "general condition" is a "syntactically and semantically" correct PCI block. + +#### **4. Media type policing** + +Policy conditions are based on protocol control information elements for the indication of specific "media types" (e.g., RTP payload type codepoint, RTCP packet type codepoint, etc.) and/or "media areas" (e.g., RTP/AVP). + +NOTE – The differentiation between "media flow" and "media type" policing is debatable. The motivation here was driven by ITU-T H.248, which provides dedicated capabilities for each policing type. + +All supported policing functions at Rw interface by Rw ITU-T H.248 profile version 1 are related to "packet filters", i.e., policing is acting at packet level and not on octet or even bit level. This might be a relevant aspect when considering statistics for the recording of "negative" policing actions (e.g., packet discard action). + +The following policing areas are for further study but mentioned for completeness: + +#### **5. Authorization policing** + +See [ITU-T H.248.65] regarding the use of authorisation and RSVP when used in a pull mode. + +#### **6. Transport security policing** + +Policy conditions are based on transport related encryption information elements (e.g., transport level security (TLS), IPSec). + +#### **7. Media security policing** + +Policy conditions are based on application data related encryption information elements (e.g., SRTP). + +#### **8. Others** + +There might be further policing types, e.g., due to the monitoring/processing of in-band signalling. + +### I.2 Support by Rw ITU-T H.248 profile version 2 + +Table I.1 provides a summary with scope on Rw ITU-T H.248 profile version 2. + +**Table I.1 – Overview of policer types in the policy enforcement physical entity** + +| Policy category | Examples | Support by Rw ITU-T H.248 profile version 2 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| Address policing |
  • • Source filtering
  • • Destination filtering
| Yes, with gm/1 package.
No. | +| Traffic policing |
  • • Traffic descriptor based policing (Note 1)
  • • Traffic contract based policing (Note 1)
| Yes, with tman/1 package (Note 2).
No. | +| Media flow policing |
  • • Validity checks of RTP packed headers
| Yes, e.g., in case of RTP-transported media inherently due to RTP protocol termination (in case of an "RTP endsystem" as ITU-T H.248 IP termination). | +| Media type policing |
  • • Check of valid media formats
| No. | +| NOTE 1 – The concept of traffic "descriptor" and "contract" is defined in ITU-T Recommendations with particular scope on technology-dependent traffic policing (e.g., Y.1221 for IP, I.371 for ATM or I.378 for AAL2).
NOTE 2 – Traffic descriptor elements related to packet size (e.g., average packet size, maximum packet size) may be not signalled with Rw ITU-T H.248 profile version 2, but could be partially supported on provisioning basis. | | | + +# Appendix II + +## Overview of statistics in the policy enforcement physical entity + +(This appendix does not form an integral part of this Recommendation.) + +## II.1 Introduction + +Figure II.1 recalls again the gate concept (see Annex A of [b-ETSI ES 283 018]) and the relation to a general IP-to-IP interworking model. The general model is based on a bidirectional IP connection, comprised by two unidirectional IP flows. The PE-PE/MG provides generally a pipeline with four or five stages per direction in the user plane. Every pipeline stage could be optional in real instances and Rw deployments. Dedicated ITU-T H.248 packages (inclusive of their statistics) are used for specific stages of the "processing pipeline". Statistics may be used at ITU-T H.248 stream- or termination-level. + +![Diagram of the PE-PE general IP-to-IP interworking model showing traffic flows, gates, and processing stages.](967e98a12645f89cb4a7620f42bf8c2e_img.jpg) + +The diagram illustrates the PE-PE general IP-to-IP interworking model. At the top, a box labeled "ITU-T H.248 Context" contains "IP ITU-T H.248 Termination" points T1 and T2, connected by a stream labeled "IP ITU-T H.248 Stream". Two "Gate" symbols, one with a right arrow and one with a left arrow, are positioned between the terminations and the main processing pipeline. Below this, a "Bidirectional IP connection" is shown as a horizontal line. The main part of the diagram consists of two horizontal processing paths. The top path (rightward flow) includes: "Packet filtering: filterin", "Packet header processing", a central box for "Media processing" containing "(1) media-aware path" and "(2) media-agnostic path", another "Packet header processing", and "Packet filtering: filterout". The bottom path (leftward flow) includes: "Packet filtering: filterout", "Packet header processing", "Media processing" (with "(1) media-aware path" and "(2) media-agnostic path"), "Packet header processing", and "Packet filtering: filterin". These stages are grouped into three dashed boxes labeled "L3/L4 functions", "L4+ functions", and "L3/L4 functions" respectively. The "Gate" symbols are connected to the "Media processing" stages. A small text "Q.3303.2 v2(14)\_F\_II.1" is in the bottom right corner. + +Diagram of the PE-PE general IP-to-IP interworking model showing traffic flows, gates, and processing stages. + +**Figure II.1 – PE-PE – general IP-to-IP interworking model +(Example with a single ITU-T H.248 stream per termination)** + +Clause II.2 is summarizing PE-PE relevant statistics. Clause II.3 provides a statistics mapping on the PE-PE model. + +### II.2 Overview of ITU-T H.248 statistics + +Statistics are required to be supported at the Rw reference point. They could be categorized into the following main areas: + +1. Usage metering (relates typically to the traffic volume on application level) +2. Reporting of QoS related metrics +3. Recording of "negative" policing actions (see Table II.1) +4. Validation of network capacity allocations (relates typically to the traffic volume on the lowest layer of transport capacity reservation, e.g., could be Layer 2, 3 or other; dependent on the specific LD/RD information) + +It has to be recalled again that the above list items are only the call or session dependent statistics, intended to be signalled between PE-PE and PD-PE. There are, in addition, typically further statistics supported by PE-PEs like the ones related to performance management with a served user located in the management plane (e.g., counters defined by simple network management protocol (SNMP) management information bases (MIBs)). + +**Table II.1 – Overview of statistics in the policy enforcement physical entity** + +| Statistics category | Examples | Support by Rw ITU-T H.248 Profile version 2 | +|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1. Usage metering | Metering of application data e.g., for
  • service level agreement (SLA) verification or
  • charging.
| Usage metering implies a "media-aware" mode of interworking in order to obtain direct statistics (see clause in 6.16.1.6 on RTP application data related statistics). Indirect measurements are supported in V1, e.g., by nt/os , nt/or , rtp/ps or rtp/pr statistics. | +| 2. Reporting of QoS related metrics | Media-agnostic QoS metrics like
  • packet loss rate,
  • packet delay variation or
  • round trip delays.
| Supported in V1. | +| | Media-aware QoS metrics like
  • RFC 3611 VoIP metrics.
| Out of scope of V1. Such statistics would relate to dedicated metrics as defined for RTCP XR and/or HR. See also [b-ITU-T H.248.30] and [ITU-T H.248.48]. | +| 3. Recording of "negative" policing actions | The element of policy enforcement is a "packet", which is either accepted and forwarded (a) unmodified or (b) modified (e.g., tagged), or (c) rejected and discarded.

The number of discarded packets may be recorded in statistics. The specific statistic may depend on the specific policing type. | V1 supports statistics for "address policing" (see statistic gm/dp ) and partially for "media flow policing" (as part of rtp/pl ).

Statistics related to "traffic policing" or "media type policing" could be subject of a later profile version.

Statistics in egress direction are not supported (NOTE – could be a subject of next gm package version). | +| 4. Validation of network capacity allocations | Transport capacity could be e.g., requested explicitly via SDP "b=" lines or implicitly via SDP "m="/"a=" field elements (e.g., codec type and codec mode of operation; disabled silence suppression).

The finally used network capacity could be recorded in statistics.

NOTE – "Traffic policing" parameters are also related to network capacity parameters. These statistics could be then complementary information, indicating the difference between reserved and used capacity. | V1 provides some initial support by the nt traffic volume statistics (NOTE – recorded volume does correspond to IP packet payloads only in case of IP terminations).

Statistics related to the IP packet level for IP terminations, or other statistics for other transport technologies could be subject of a later profile version. | + +## II.3 Mapping statistics on the IP-to-IP interworking model + +Figure II.2 shows how the various statistics types could be mapped into the IP-to-IP interworking model. The majority of statistics is in the ingress path. + +![Schematic mapping of ITU-T H.248 statistics on the IP-to-IP interworking model. The diagram shows a PE-FE: ITU-T H.248 media gateway with L3/L4 functions and L4+ functions. It details ingress and egress paths with various statistics mapping points.](37806e0fc150d857046ebc7e47893d7a_img.jpg) + +The diagram illustrates the mapping of ITU-T H.248 statistics onto the IP-to-IP interworking model within a PE-FE: ITU-T H.248 media gateway. The gateway is divided into two main functional blocks: **L3/L4 functions** and **L4 + functions**. + +- Ingress Path (Left side):** + - Statistics 4 (Network capacity - received traffic volume) and 3 (Recording policing: a) address policing) are mapped to the ingress path. + - Packet filtering blocks $F_{in, 1}$ and $F_{in, k}$ are shown, with arrows indicating traffic flow. + - Statistics 4 (Network capacity - sent traffic volume), 3 (Recording policing: b) traffic policing), 1 (Usage metering - sent traffic vol.), and 2 (QoS reporting - media-agnostic QoS metrics) are mapped to the path after packet filtering. + - Recording policing sub-types c) media flow policing and d) media type policing are shown as nested components within the ingress path. + - Packet header processing is the next stage in the ingress path. +- Egress Path (Right side):** + - Statistics 1 (Usage metering - received traffic volume) and 2 (QoS reporting - media-aware QoS metrics) are mapped to the egress path. + - Media processing blocks are shown in the L4+ functions area. + - Packet header processing is shown in the L3/L4 functions area. + - Packet filtering blocks $F_{out, j}$ and $F_{out, 1}$ are shown, with arrows indicating traffic flow. + +Callouts at the top of the diagram list the statistics types and their corresponding metrics: + +- 4. Network capacity (received traffic volume) +- 3. Recording policing: a) address policing +- 1. Usage metering (received traffic volume) +- 2. QoS reporting (media-aware QoS metrics) +- 4. Network capacity (sent traffic volume) +- 3. Recording policing: b) traffic policing +- 1. Usage metering (sent traffic vol.) +- 2. QoS reporting (media-agnostic QoS metrics) +- 3. Recording policing: c) media flow policing +- 3. Recording policing: d) media type policing + +The diagram is labeled **PE-FE: ITU-T H.248 media gateway** and the reference code **Q.3303.2 v2(14)\_F.II.2** is shown in the bottom right corner. + +Schematic mapping of ITU-T H.248 statistics on the IP-to-IP interworking model. The diagram shows a PE-FE: ITU-T H.248 media gateway with L3/L4 functions and L4+ functions. It details ingress and egress paths with various statistics mapping points. + +**Figure II.2 – Schematic mapping of ITU-T H.248 statistics on the IP-to-IP interworking model** + +NOTE – The policing related statistics are distributed over the (ingress and egress) IP forwarding paths, dependent on the policer type. + +# Appendix III + +## Differences between [ETSI ES 283 018] and this Recommendation + +(This appendix does not form an integral part of this Recommendation.) + +Table III.1 provides an overview of the differences between [b-ETSI ES 283 018] and this Recommendation. + +**Table III.1 – Difference between [b-ETSI ES 283 018] and this Recommendation** + +| Topic | [b-ETSI ES 283 018] | Recommendation ITU-T Q.3303.2 | +|-------------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Required ITU-T H.248 gateway control protocol version | ITU-T H.248 Version 3 | ITU-T H.248 Version 3
ITU-T H.248.1 Version 2 may be chosen as the minimum protocol version if no capabilities specific to Version 3 are used. | +| Connection model | Maximum number of terminations per context: up to 2 | Maximum number of terminations per context: at least 2 | +| Termination ID structure | ip///
Group Values : 0-255 | ip///
Group Values : 0-65535 | +| TerminationState Descriptor | ServiceState property used: No | ServiceState property used: No
NOTE – The value of the ServiceState property may be implicitly changed by ServiceChange procedures, or the value may be read by audit procedures, i.e., "Yes" for ServiceStates "InService" and "OutOfService" due to AuditValue and ServiceChange commands or "No" for ServiceState "Test". | +| Stream Descriptor | Termination type: IP
Maximum number: 5 | Termination type: IP
Maximum number: 5 (Note)
NOTE – Five ITU-T H.248 streams are sufficient to handle various combinations of flows associated with media including possible separation of RTP from RTCP and possible control streams. | +| LocalControl Descriptor | ReserveGroup used: No
ReserveValue used: No | ReserveGroup used: Yes
ReserveValue used: Yes
NOTE – This profile is "media aware", i.e., ReserveGroup and/or ReserveValue may be principally applied for ALL termination and stream types. | + +**Table III.1 – Difference between [b-ETSI ES 283 018] and this Recommendation** + +| Topic | [b-ETSI ES 283 018] | Recommendation ITU-T Q.3303.2 | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Events Descriptor | – | Event ID: rtp/pltrans
Termination type: All except ROOT
Stream type: Any

Event ID: it/ito
Termination type: Only ROOT
Stream type: not applicable

Event ID: ocp/mg_overload
Termination type: Only ROOT
Stream Type: not applicable | +| Topology Descriptor | Allowed triples: NA | Allowed triples: Not applicable (Note)
NOTE – Optional in the case of more than two terminations (see also clause 6.3). | +| Command API | Notify command used on termination type
ROOT: No | Notify command used on termination type
ROOT: Yes | +| | Subtract command wildcard support
O-: No | Subtract command wildcard support
O-: Yes | +| Add | Descriptors used by Add request:
Media (Stream(LocalControl, Local, Remote)), Event, Signals | Descriptors used by Add request:
Media(TerminationState, (Stream(LocalControl, Local, Remote))), Statistics (Note), Event, Signals | +| | Descriptors used by Add reply:
Media (Stream(Local)) | Descriptors used by Add reply:
Media (TerminationState, (Stream(Local, Remote))) | +| Modify | Descriptors used by Modify request:
Media (Stream (LocalControl, Local, Remote)),
Audit(Media (Stream (Statistics))),
Statistics, Signals, Event | Descriptors used by Modify request:
Media (TerminationState, (Stream (LocalControl, Local, Remote))),
Audit(Media (Stream (Statistics))),
Statistics, Signals, Event | +| | Descriptors used by Modify reply:
Media(Stream(Local)), Statistics | Descriptors used by Modify reply:
Media(Stream(Local, Remote)),
Statistics | + +**Table III.1 – Difference between [b-ETSI ES 283 018] and this Recommendation** + +| Topic | [b-ETSI ES 283 018] | Recommendation ITU-T Q.3303.2 | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceChange | MGC: – | MGC: Handoff (909) | +| | MG:
Forced(904, 905, 906, 915)
Graceful,
Failover,
Handoff: None | MG:
Forced (904, 905, 906, 908, 915)
Graceful (905)
Failover (908 909, 919, 920)
Handoff (903) | +| | ServiceChangeAddress used:
No | ServiceChangeAddress used:
Yes | +| | ServiceChangeDelay used: No | ServiceChangeDelay used: Yes | +| | ServiceChangeVersion: 3 | ServiceChangeVersion: 3 or 2
(Note)
NOTE – Version 2 is also
supported, see clause 6.2. | +| | ServiceChangeProfile
ServiceChangeProfile parameter
mandatory: None | ServiceChangeProfile
ServiceChangeProfile parameter
mandatory: Yes, with ProfileID
according to clause 6.1. | +| Transport | Supported transports:
SCTP (Recommended)
UDP (Optional) | Supported transports:
Either SCTP or
UDP must be supported | +| Transactions | Maximum number of commands per
transaction request: 2 | Maximum number of commands
per transaction request: Not
specified | +| | Maximum number of commands per
transaction reply: 2 | Maximum number of commands
per transaction reply: Not specified | +| | Commands able to be marked
"Optional": AuditValue | Commands able to be marked
"Optional": AuditValue,
AuditCapabilities, Subtract | +| SDP Usage ("o=", "s=",
"t=" lines) | – | Optional support | +| Usage metering and
statistics reporting | RTP statistics is out of scope of this
version 1 of the Profile. | The "number of octets" excludes all
transport overhead (see
clause E.11.4 of [ITU-T H.248.1]),
i.e., IP header is excluded in case of
an IP-based ITU-T H.248
Termination (see clause E.11.5.1.5
of [ITU-T H.248.1]).
RTP statistics are in scope of
version 1 of the Profile.
More detail on statistics described
in clause 6.16.1.6.1 | +| IP domain/realm indication | Supported, but [ETSI ES 283 018]
does not provide any explicit
description for that function. | Described in clause 6.16.1.10 | + +**Table III.1 – Difference between [b-ETSI ES 283 018] and this Recommendation** + +| Topic | [b-ETSI ES 283 018] | Recommendation ITU-T Q.3303.2 | +|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call independent procedures |

Call-independent procedures for [ETSI ES 283 018] are defined in a separate document [ETSI TR 183 025], which is an overall description for all ETSI defined ITU-T H.248 profile specifications, i.e., [b-ETSI TR 183 025] complements each profile specification.

The set of profile-applicable call-independent procedures is primarily given by the supported ITU-T H.248 command API capabilities for AuditValue (see clause 6.7.5), AuditCapabilities (see clause 6.7.6) and ServiceChange (see clause 6.7.8), and supported packages (e.g., for overload control), by each profile.

| As [ETSI ES 283 018]. Further details are described in clause 6.16.2 | +| Overview of specific policing functions in the policy enforcement physical entity | – | Described in Appendix I | +| Overview of statistics in the policy enforcement physical entity | – | Described in Appendix II | +| Packages | | | +| Network (nt/1) |

Supported

ObservedEvent

Parameters: None

Statistics:

Duration: Optional

|

Supported

ObservedEvent

Parameters: Cause (Optional)

Statics:

Duration: Mandatory

| +| VLAN (vlan/1) |

Optional

Properties:

All: Optional

|

Optional

Properties:

All: Mandatory

| +| Segmentation (seg/1) |

Optional

Properties:

MGSegmentationTimerValue, MGCSegmentationTimerValue, MGMaxPDUSize, MGCMAXPDUSize

Used in command:

NOTIFY

|

Optional

Properties:

MGSegmentationTimerValue, MGCSegmentationTimerValue, MGMaxPDUSize, MGCMAXPDUSize

Used in command:

MODIFY, AUDITVALUE

| +| RTP (rtp/1) | Not supported | Optional | +| Media gateway overload control (ocp/1) | Not supported | Optional | +| IP domain connection (ipdc/1) | Not supported | Optional | + +# Bibliography + +- [b-ITU-T H.248.13] Recommendation ITU-T H.248.13 (2002), *Gateway control protocol: Quality Alert Ceasing package*. +- [b-ITU-T H.248.30] Recommendation ITU-T H.248.30 (2007), *Gateway control protocol: RTCP extended performance metrics packages*. +- [b-ITU-T H-Sup.6] ITU-T H-series Recommendations – Supplement 6 (2006), *Control load quantum for decomposed gateways*. +- [b-ITU-T V.152] Recommendation ITU-T V.152 (2010), *Procedures for supporting voice-band data over IP networks*. +- [b-ITU-T Y.1221] Recommendation ITU-T Y.1221 (2010), *Traffic control and congestion control in IP based networks*. +- [b-ITU-T Y.1541] Recommendation ITU-T Y.1541 (2011), *Network performance objectives for IP-based services*. +- [b-ETSI TR 183 025] ETSI TR 183 025 V2.2.0 (2008), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-Call Related Procedures and Management System Interaction*. +- [b-ETSI TR 183 068] ETSI TR 183 068 V3.1.1 (2009), *Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Guidelines on using Ia H.248 profile for control of Border Gateway Functions (BGF); Border Gateway Guidelines*. +- [b-ETSI TS 181 005] ETSI TS 181 005 V3.3.1 (2009), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements*. +- [b-ETSI TS 183 018] ETSI TS 183 018 V3.5.1 (2009), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile Version 3 for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification*. +- [b-ETSI TS 187 003] ETSI TS 187 003 V3.4.1 (2011), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture*. +- [b-ETSI ES 283 018] ETSI ES 283 018 V1.1.4 (2007), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification*. +- [b-IETF RFC 2327] IETF RFC 2327 (1998), *SDP: Session Description Protocol*. +- [b-IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations*. +- [b-IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [b-IETF RFC 3605] IETF RFC 3605 (2003), *Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)*. + +- [b-IETF RFC 3611] IETF RFC 3611 (2003), *RTP Control Protocol Extended Reports (RTCP XR)*. +- [b-IETF RFC 3711] IETF RFC 3711 (2004), *The Secure Real-time Transport Protocol (SRTP)*. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..217155fefa26edc021a498c7228ed1349a563ec8 --- /dev/null +++ b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d5d58979f859b0bc3c74ccbae80adac361fa3c70545e8d1238d7fc94b9b6ffc +size 23123 diff --git a/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..676408fe32878131fffd56288970267f7cac242a --- /dev/null +++ b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b5f48a78ce67445f84f33b89182e3fdc1719306198d24144f06b433809a7e8 +size 22056 diff --git a/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04ed0575fb17e6faeb57d9d81b58c3b85f7e21df --- /dev/null +++ b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3223bb567d6cdfacad7ced972fc4eab63d7b0659969b11a4801458bec7649f19 +size 3852 diff --git a/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ee370b6940f405b574ce1864e8d0927cd28153f --- /dev/null +++ b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e069ad1475a3fecd3bda09b59be2ebd2c62b1ff4ff5503b3a43c8f7c51088ed +size 74696 diff --git a/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01f90a3a65dec1a752e6121365128e6836f1a763 --- /dev/null +++ b/marked/Q/T-REC-Q.3307.1-200906-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:162a39e3685984f531865c3bb9d8757aae3544bf5f30ef3bbf4b3950accb4349 +size 32195 diff --git a/marked/Q/T-REC-Q.3309-200910-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3309-200910-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c686162532c788cca9c34419f2007038e14d4296 --- /dev/null +++ b/marked/Q/T-REC-Q.3309-200910-I_PDF-E/raw.md @@ -0,0 +1,447 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3309** + +(10/2009) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Resource control protocols + +--- + +**QoS coordination protocol** + +Recommendation ITU-T Q.3309 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. The text "International Telecommunication Union" is written in blue to the right of the globe. + +ITU logo + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|---------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3649 | +| NGN applications | Q.3700–Q.3849 | +| Testing for NGN networks | Q.3900–Q.3999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# **Recommendation ITU-T Q.3309** + +## **QoS coordination protocol** + +## **Summary** + +Recommendation ITU-T Q.3309 defines an admission control coordination protocol for NGN and includes the definition of interfaces between the admission control coordination layer and higher-layer signalling systems, and between the admission control coordination layer and lower-layer transport networks. + +## **Source** + +Recommendation ITU-T Q.3309 was approved on 29 October 2009 by ITU-T Study Group 11 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## **Keywords** + +QoS coordination, RSVP. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|---------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 High-level description ..... | 2 | +| 6.1 Admission control coordination models..... | 3 | +| 7 Protocol description..... | 4 | +| 7.1 Design guidelines and basic protocol operation..... | 4 | +| 7.2 RSVP extensions to support coordination mode ..... | 6 | +| 7.3 QoS reservation types..... | 7 | +| 7.4 Aggregation ..... | 8 | +| Appendix I..... | 10 | +| I.1 List of different QoS reservation types ..... | 10 | +| I.2 Dynamic aggregation..... | 10 | +| Bibliography..... | 11 | + + + +## Recommendation ITU-T Q.3309 + +## QoS coordination protocol + +# 1 Scope + +This Recommendation defines an admission control coordination protocol. Major design aspects of the protocol considered include the definition of interfaces between the admission control coordination layer and higher-layer signalling systems, and the admission control coordination layer and lower-layer transport networks. Protocol semantics are also included in the definition. + +NOTE – This Recommendation is a specification of protocol requirements; it can functionally be part of different architectures. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[IETF RFC 1633] IETF RFC 1633 (1994), *Integrated Services in the Internet Architecture: an Overview*. + +[IETF RFC 2205] IETF RFC 2205 (1997), *Resource ReSerVation Protocol (RSVP), Version 1 Functional Specification*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 Adspec** [IETF RFC 2205]: A Path message may carry a package of OPWA advertising information, known as an "Adspec". + +NOTE – An Adspec received in a Path message is passed to the local traffic control, which returns an updated Adspec; the updated version is then forwarded in Path messages sent downstream. + +**3.1.2 flowspec** [IETF RFC 2205]: Defines the QoS to be provided for a flow. The flowspec is used to set parameters in the packet scheduling function to provide the requested quality of service. A flowspec is carried in a FLOWSPEC object. The flowspec format is opaque to RSVP and is defined by the Integrated Services Working Group of the IETF. + +**3.1.3 Rspec** [IETF RFC 2205]: The component of a flowspec that defines a desired QoS. + +NOTE – The Rspec format is opaque to RSVP and is defined by the Integrated Services Working Group of the IETF. + +**3.1.4 Tspec** [IETF RFC 2205]: A traffic parameter set that describes a flow. + +NOTE – The format of a Tspec is opaque to RSVP and is defined by the Integrated Service Working Group of the IETF. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 forwarder:** A node that is responsible – within a domain – to receive end-to-end QoS coordination requests, dispatch them to the admission control layer through the admission controller interface, process them and forward them to the next domain on the end-to-end path. + +**3.2.2 last forwarder:** The forwarder of the last domain along the end-to-end path. + +**3.2.3 QoS requester:** The node where the session control function or the end-user equipment requests QoS treatment to the network. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +OPWA One-Pass With Advertising + +QCP QoS Coordination Protocol + +RSVP Resource ReSerVation Protocol + +YESSIR YEt another Sender Session Internet Reservations + +# 5 Conventions + +None. + +# 6 High-level description + +In order to define the admission control coordination protocol, four layers are identified as illustrated in Figure 6-1: session control layer, coordination layer, admission control layer and QoS enforcement layer. + +![Figure 6-1: Layer sketch of end-to-end QoS architecture. The diagram shows a hierarchy of layers. At the top, a single grey box labeled 'Session control layer coordination layer' is bracketed on the left as 'End-to-end'. Below this, the space is divided into two identical vertical columns. Each column contains two stacked grey boxes: the top one is 'Admission control layer' and the bottom one is 'QoS enforcement layer'. These two columns are bracketed together on the left as 'Domain'.](ef7a88e04d1939ee09bafd5c3072adf8_img.jpg) + +Q.3309(09)\_F6-1 + +Figure 6-1: Layer sketch of end-to-end QoS architecture. The diagram shows a hierarchy of layers. At the top, a single grey box labeled 'Session control layer coordination layer' is bracketed on the left as 'End-to-end'. Below this, the space is divided into two identical vertical columns. Each column contains two stacked grey boxes: the top one is 'Admission control layer' and the bottom one is 'QoS enforcement layer'. These two columns are bracketed together on the left as 'Domain'. + +**Figure 6-1 – Layer sketch of end-to-end QoS architecture** + +The QoS enforcement layer is instantiated at each admission controlled domain. It sends the necessary information to the upper admission control layer, so that when the admission control layer accepts to deliver a particular service to a flow or a user, the domain is able to provide it. + +The admission control layer is instantiated at each admission controlled domain; it lies on top of the QoS enforcement layer and uses the information the QoS enforcement layer provides to act as a decision point for each admission controlled domain. Its task is to offer an interface to perform end-to-end requests for QoS treatment. The admission control layer interprets these requests for end-to-end QoS treatment, and supplies an answer on behalf of the whole domain whether or not the request can be accepted and the requested service can be delivered. + +The coordination layer lies on top of the admission control layer. This common layer links together the admission controlled domains, giving end-to-end control to a set of local controllers. + +The session control layer lies on top of the coordination layer and uses its services to enhance a session with the assurance of a certain type of service from the network. A session is made by a set of participants who engage themselves in a communication. Identifying these participants as well as transporting the information about the agreement on the QoS requirements among all the participants are two of the tasks of this layer. After this, QoS requirements are communicated to the coordination layer that triggers the mechanisms to create the end-to-end service. + +## 6.1 Admission control coordination models + +The basic building block of the network is the admission controlled domain, which is an interconnection of network elements that provides an admission controller interface. A subject (flow, packet, etc.) can request QoS treatments and receive a positive or negative response to their request. The admission control coordination protocol acts as a bridge between a single end-to-end request and the heterogeneity of the admission control mechanisms that are already deployed in the network; it provides all the means to locate, contact, query and coordinate the responses of the admission controllers on the path. The coordination protocol interacts with an actor called the coordination daemon. + +There are many ways to design the coordination protocol. It can be: + +- a) Path-coupled vs. path-decoupled: A coordination protocol is path-coupled if it is part of the data path, path-decoupled otherwise; there are no assumptions on the location of the coordination daemon; if it is tightly coupled with its admission controller, it will be a matter of inter-process communication, whereas if they are loosely-coupled, an additional message will be sent across the network. +- b) Stateless vs. stateful, with respect to the QoS request information: In a stateful scenario, the coordination daemon keeps a list of all the subject-treatment couples for the subjects that use part of the resources in that coordination daemon's scope; whereas in a stateless scenario, the coordination daemon does not keep a list of any subject. + +The overall scheme can be proactive or reactive: this applies in the presence of failures, re-routes, mobility or other exceptional events. In these cases, subjects may have changed their path; hence the coordination phase may have to be performed again, as well as the admission control phase. If this is done proactively, the coordination mechanism is triggered periodically to refresh the state and to react to exceptional events. In a reactive scenario, the coordination daemon is aware of changes that cause exceptional events, and it reacts by re-triggering the coordination mechanism. + +From such a characterization, we can sketch different possible architectures, summarized in Figure 6-2, where each oval represents an admission controlled domain; a spot represents an admission controller interface and a square represents a coordination daemon (note that they might overlap and be instantiated at the same node). + +![Figure 6-2: Admission control coordination models. The diagram shows four scenarios (i-iv) of coordination between a coordination daemon (square) and an admission controller interface (dot) within an admission controlled domain (oval). (i) shows both path-coupled. (ii) shows path-decoupled coordination daemon and path-coupled admission controller. (iii) shows both path-decoupled. (iv) shows path-coupled coordination daemon and path-decoupled admission controller. A legend defines the symbols: oval for Admission controlled domain, dot for Admission controller interface, square for Coordination daemon, dashed arrow for End-to-end request, and solid arrow for Local coordination. The text Q.3390(09)F6-2 is present.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Q.3390(09)F6-2 + +○ Admission controlled domain      ----> End-to-end request + ● Admission controller interface      ———> Local coordination + □ Coordination daemon + +Figure 6-2: Admission control coordination models. The diagram shows four scenarios (i-iv) of coordination between a coordination daemon (square) and an admission controller interface (dot) within an admission controlled domain (oval). (i) shows both path-coupled. (ii) shows path-decoupled coordination daemon and path-coupled admission controller. (iii) shows both path-decoupled. (iv) shows path-coupled coordination daemon and path-decoupled admission controller. A legend defines the symbols: oval for Admission controlled domain, dot for Admission controller interface, square for Coordination daemon, dashed arrow for End-to-end request, and solid arrow for Local coordination. The text Q.3390(09)F6-2 is present. + +**Figure 6-2 – Admission control coordination models** + +Among all the possible solutions, we might have (i) a scenario where the coordination daemon and the admission controller are both path-coupled: the coordination daemon receives an end-to-end request, in turn, it both propagates on to the next coordination daemon, and pushes down to the admission controllers; (ii) a situation in which the coordination daemon is path-decoupled and the admission controller is path-coupled; (iii) a scenario where the coordination daemon and the admission controller are both path-decoupled; and finally, (iv) a path-coupled coordination daemon and path-decoupled admission controller solution. + +This model could be further extended to introduce the concept of hierarchy. The four models presented above could in turn be seen as basic building blocks. The most general approaches from Figure 6-2 are (ii) and (iii). (i) is the same as (ii) with the introduction of hierarchy; (iv) is the same as (ii), since no assumptions can be made on whether the admission controller and the coordination daemon are tightly or loosely coupled. + +# 7 Protocol description + +Clause 6 details the main models for arranging the admission control coordination. In this clause, a set of design guidelines for an admission control coordination protocol for the Internet is formulated. RSVP is extended in order to make it suitable as an admission control coordination protocol. + +## 7.1 Design guidelines and basic protocol operation + +An instantiation of such a coordination protocol consists of a protocol initiator, a terminator, and a sequence of coordination daemons. From initiator to terminator, the protocol follows the data path, communicating one by one with every coordination daemon along this path. Both a path-coupled approach and path-decoupled approach are allowed. The use of RSVP means that a separate routing mechanism is not necessary. Coordination daemons first trigger their local resource management mechanism (within their admission control domain) and then propagate the outcome of such a process until every coordination daemon along the path has provided its outcome. This communication occurs via the admission controller interface. The coordination protocol allows the various outcomes to be merged together into a single response to the QoS requester. + +### 7.1.1 Interfaces + +In general, the protocol daemon can have up to four interfaces: the application interface, the routing interface, the admission controller interface, and the coordination interface. + +![Diagram of Protocol interfaces showing a central coordination block connected to routing, application, and admission control blocks via specific interfaces.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +The diagram illustrates the central 'coordination' block and its four interfaces: + +- Routing interface:** Connects the 'coordination' block to the 'routing' block. It uses 'route\_res' (downward arrow) and 'route\_query' (upward arrow). +- Application interface:** Connects the 'coordination' block to the 'application' block. It uses 'qos\_req' (rightward arrow) and 'qos\_res' (leftward arrow). +- Admission controller interface:** Connects the 'coordination' block to the 'admission control/coordination' block. It uses 'ac\_req' (downward arrow) and 'ac\_res' (upward arrow). +- Coordination interface:** Connects the 'coordination' block to another 'coordination' block. It uses 'qos\_req' (rightward arrow) and 'qos\_res' (leftward arrow). + +Reference: Q.3309(09)\_F7-1 + +Diagram of Protocol interfaces showing a central coordination block connected to routing, application, and admission control blocks via specific interfaces. + +**Figure 7-1 – Protocol interfaces** + +The admission controller interface is invoked by the coordination function and is implemented by either another coordination function (i.e., recursively) or by an admission control function. When it is implemented by an admission control function, this will allocate the necessary resources, if available. A successful allocation returns a positive admission control outcome, whereas a failure returns a negative outcome. + +On the other hand, when the admission control function is implemented by a coordination function, the interface recursively looks for all the lower layer admission control functions, queries them and coordinates an outcome in one domain. + +The routing interface uses RSVP to determine the path to forward on. It also receives route change notifications. The coordination interface is used to communicate to other coordination daemons or to the application or call agent at the end of the protocol chain. + +### 7.1.2 Recursion + +Since the invocation of the admission controller interface is transparent, the coordination protocol is unaware of the nature of the layer below. In particular, the layer below can be a protocol implementing either an admission control function or another coordination function. If an admission control function is implemented, then the recursion ceases; otherwise, if a further coordination function is implemented, then the current domain is further divided and coordinated within the divided domains. This process of recursively invoking the admission controller interface iterates until each domain configures its local elements' traffic control and reports the outcome of the admission control. Thus an admission controlled domain could be divided into sub-domains, where admission control is decided at the lower level. Optionally, the original semantics of RSVP could be maintained in a domain or sub-domain so that an RSVP reservation is made on routers, which is out of scope of this Recommendation. + +### 7.1.3 Protocol semantics + +Provided a coordination protocol shows the properties discussed in the previous clauses, the semantics of the message exchange are similar to those of resource reservation protocols such as RSVP [IETF RFC 1633] and YESSIR. Two models are supported: + +- A two-stage commit-reserve: A coordination daemon receives a QoS request which is passed to the resource management system with the aim to reserve resources without committing them. +- A one-stage commit: A coordination daemon receives a QoS request which is passed to the resource management system with the aim of committing resources. + +The difference between both cases is when resources are committed, i.e., when the admission control decision has been made. With respect to this, the protocol can operate in two ways, depending on whether a QoS request is in (non-)blocking mode for a coordination daemon. + +- Blocking mode: A coordination daemon passes a commit request to the resource management system, waits for a response, and then forwards on both the commit request and the response. +- Non-blocking mode: A coordination daemon passes a commit request to the resource management system, forwards the commit request on, and waits for an upstream response to come back. + +## 7.2 RSVP extensions to support coordination mode + +RSVP [IETF RFC 2205] provides QoS signalling for application data streams. QoS requesters can use RSVP to request a specific QoS from the network for particular application flows. The admission control domain uses RSVP to deliver QoS requests to all nodes along the data path. RSVP can also maintain and refresh states for a requested QoS application flow. + +The design of RSVP is distinguished in a number of fundamental ways, including soft state management, two-stage reserve-commit message exchanges, and separation of signalling from routing. + +RSVP carries QoS signalling messages through the network, visiting each node along the data path, while following normal IP routing. To make a resource reservation at a node, the RSVP daemon communicates with two local decision modules: admission control and policy control. Admission control determines whether the node has sufficient available resources to provide the requested QoS. Policy control provides authorization for the QoS request. If either check fails, the RSVP module returns an error notification to the application process that originated the request. If both checks succeed, the RSVP module sets parameters in a packet classifier and packet scheduler to obtain the desired QoS. + +RSVP is suitable to support admission control coordination because it shows most of the properties the QoS coordination protocol needs: + +- 1) RSVP can be path-coupled, and +- 2) can be used recursively. + +Nevertheless, there are a number of substantial features that RSVP is not designed for, including: + +- Domain-awareness – RSVP is not domain aware. +- Admission controller interface – RSVP daemons support an admission controller interface. Although, while in coordination mode, this interface would likely be different and more generic. +- Protocol semantics – RSVP message exchange is based on a 2-stage reserve-commit model. A 1-stage exchange model is needed to support a coordination mode. + +- Mode field – RSVP needs to support a message header field in order to distinguish when it is used in reservation mode from when it is used in coordination mode. An admission controlled domain could use an extended RSVP by handling coordination mode in the same way as reservation mode. This would be an internal choice by the domain. +- Recursion field – RSVP could be used recursively; however, it does not have an explicit message header field explicitly stating the level of recursion. This would be required to handle recursive protocol instantiations. +- QoS pre-booking – This is when QoS is requested for a future time period rather than for immediate use. RSVP does not support pre-booking of QoS. +- Sender initiation – RSVP is receiver initiated. Sender initiation is needed as is the ability of initiation by proxies of the sender or receiver. + +The extended version of RSVP combines both resource reservation and coordination functions. When used in reservation mode, RSVP operates in the traditional way. When used in coordination mode, RSVP operates as follows. The message exchange involves one node per admission control domain, i.e., the data traverses each ingress node. Upon receipt of a request, the ingress node initiates its local resource management mechanism, and forwards the request to the next ingress node along the data path. This process iterates until the request reaches the terminator. The terminator replies with a response that traverses the same ingress nodes, collecting and merging the outcomes of the various admission control processes (success/failure). Once at the initiator, the response carries the overall, initiator-to-terminator, admission control response + +Ingress nodes represent the default point of contact for that domain by running an instance of the admission control coordination protocol. When it is not necessary for the admission controller to represent the default point of contact for that domain, the coordination daemon forwards (via the admission controller interface) the request to the appropriate, locally configured, entity. + +## 7.3 QoS reservation types + +There are different possible semantics of reservation: One-pass mechanism (commit-error), Two-pass mechanism (reserve-commit), and One-pass with advertising (OPWA). For the reservation type OPWA, the advertising messages from the QoS requester are delivered to each admission controller interface in the domains along the end-to-end path. When they reach the receiver, they contain all the Rspec metrics resulting in the reservation of the given subject (defined by its Tspec) under the different types of services that the network can deliver. The decision can then be taken, choosing among all the different services and knowing all the Rspec metrics. + +OPWA is used in this Recommendation since this is the method that allows complete flexibility. The QoS coordination protocol is recommended to contain a third message flow to deal with the situation where, at the endpoint, advertising of network services is available (most likely the receiver) and the endpoint is not the point where the decision of which service to choose is made. In such a case, the entity that takes the decision is recommended to be contacted, given the information about the different service and asked which service to choose. + +![Diagram illustrating the scenario of One-pass with advertising (OPWA). The diagram shows a network architecture with a Sender (blue cylinder) and a Receiver (blue cylinder) connected via a path of Admission control entities (red cylinders). A QoS requester (green cylinder) is connected to the Sender. Two Session control entities (grey server icons) are shown at the top. The process involves: 1. Sender to Session control entity; 2. Session control entity to QoS requester; 3. QoS requester to first Admission control entity; 4. First Admission control entity to second; 5. Second Admission control entity to QoS requester; 6. Second Admission control entity to Receiver. Red curved lines with '1' indicate connections between the Sender and Receiver to the Session control entities. A label 'Q.3309(09)_F7-2' is in the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram illustrating the scenario of One-pass with advertising (OPWA). The diagram shows a network architecture with a Sender (blue cylinder) and a Receiver (blue cylinder) connected via a path of Admission control entities (red cylinders). A QoS requester (green cylinder) is connected to the Sender. Two Session control entities (grey server icons) are shown at the top. The process involves: 1. Sender to Session control entity; 2. Session control entity to QoS requester; 3. QoS requester to first Admission control entity; 4. First Admission control entity to second; 5. Second Admission control entity to QoS requester; 6. Second Admission control entity to Receiver. Red curved lines with '1' indicate connections between the Sender and Receiver to the Session control entities. A label 'Q.3309(09)\_F7-2' is in the bottom right. + +**Figure 7-2 – Scenario of One-pass with advertising (OPWA)** + +A sketch of the above scenario is shown in Figure 7-2: + +- 1) The sender contacts the session signalling overlay that differentiates the participants and negotiates the type of media. +- 2) The session control entity initiates the QoS coordination mechanisms via the application interface (as described in Figure 7-1), contacting the QoS requester. +- 3) If RSVP is assumed as the signalling protocol, the QoS requester sends a PATH message downstream (passing through all the admission control entities via the admission controller interfaces), with the Tspec of the flow. The PATH message collects advertising data in the ADSPEC object; the complete Adspec is present at the last forwarder (i.e., admission controller interface). +- 4) The Adspec information is then sent back to the QoS requester (assuming that the QoS requester is the suitable decision maker). +- 5) The QoS requester makes the decision and sends it to the last forwarder. +- 6) The last forwarder can then send back the RESV message to reserve the resource for the chosen service. + +## 7.4 Aggregation + +The model of coordination presented in clause 6 is explicitly per-flow and seeks end-to-end agreement on the treatment. This results in the scheduling of a single message exchange for each request. + +Aggregation is a way to reduce the number of messages, the amount of information stored and the processing time for the coordination layer, when such tasks become excessive in the inner domains of the network. Generally, aggregation presumes an effort by the edges (i.e., where per-flow handling of QoS is possible) to aggregate flows so that they share a common path in the core and similar QoS requirements. This causes them to be treated together, reducing, therefore, the cost of individual treatment, without reducing the efficiency to obtain services. + +In general, two different solutions can be identified to determine the boundaries of an aggregation area: static aggregation and dynamic aggregation. + +Static aggregation is where an aggregation area is identified so that, within its boundaries, flows are treated as aggregates. In this solution, the scope of the domain is decided by network administrators so as to get the best out of the aggregation process. This may be complicated by the presence of multiple domains. + +Dynamic aggregation is used dynamically, depending on different factors such as the direction of the flow, the number of flows and the position in the network of the domains handling a particular flow. Dynamic aggregation is out of scope of this Recommendation since it is complex to realize in practice. + +### 7.4.1 Marking method + +In the case when MPLS is used as a tunnelling technique, different label switched paths can be used to differentiate the QoS treatment among flows that follow the same aggregated path. A second encapsulated header is used to take care of the multiplexing of different QoS treatments among an aggregate. For example, compliant with the FILTER\_SPEC classification of packets, a UDP header could be used for the aggregated traffic; the UDP source port field could be used to multiplex different packet treatments, the UDP destination port could be used for other purposes. This can be seen in Figure 7-3. + +| | | | | +|------------------------|-------------------------|-----------|------------------------| +| Encapsulated IP header | Encapsulated UDP header | IP header | Transport layer packet | +|------------------------|-------------------------|-----------|------------------------| + +Q.3309(09)\_F7-3 + +**Figure 7-3 – Packets for aggregated traffic** + +# Appendix I + +(This appendix does not form an integral part of this Recommendation) + +## I.1 List of different QoS reservation types + +Table I.1 gives informational explanation of different QoS reservation types to help understand the texts in clause 7.3. + +**Table I.1 – QoS reservation types** + +| QoS reservation types | Definitions | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| One-pass mechanism (commit-error) | Reservation requests from the sender are delivered to each admission controller interface in the domains along the end-to-end path. The reservation is either admitted, in which case the process goes on, or it is not, in which case a cascade of errors is propagated upstream to tear down the already admitted reservations. In this scenario though, there is no reasonable way, in which at the end of the reservation path, the coordination layer can know metrics such as end-to-end delay or jitter bound, for instance; hence, with this mechanism, the coordination layer can just instruct all the domains about the desired per-domain service. | +| Two-pass mechanism (reserve-commit) | Reservation requests from the sender are delivered to each admission controller interface in the domains along the end-to-end path in two passes. With the first pass, the sender inserts the Rspec, the network reserves the service that fits the request with the tightest metrics. At the receiver end, the global reservation is received; if the service characteristics that the network can offer are less than the requested ones, the reservation is rejected and torn down; in case they are even tighter, the service characteristics can be relaxed containing information about the excess resources. This scenario allows the specification of all the Rspec metrics. | +| One-pass with advertising (OPWA) | See clause 7.3. | + +## I.2 Dynamic aggregation + +In the dynamic aggregation, aggregation is used dynamically, depending on different factors such as the direction of the flow, the number of flows and the position in the network of the domains handling a particular flow. Dynamic aggregation area creation is not a straightforward task, and can be carried out as a result of coordination between local decisions of the admission controlled domains. Each domain in the path decides whether to use aggregation based on local policies. Consequently, the local decisions are shared with the help of the coordination layer and aggregation areas are dynamically built. This does not pose a problem in the intra-domain situation, but may pose a problem in the inter-domain situation between neighbouring nodes where less information may be available. In addition, this approach may lead to a bigger number of messages exchanged and to a more expensive computation for the communication of the local decisions and the coordination of different domains. + +# Bibliography + +- [b-ITU-T H.360] Recommendation ITU-T H.360 (2004), *An architecture for end-to-end QoS control and signalling*. +- [b-ETSI RACS] ETSI RACS Release 1 (2005), *NGN functional architecture; Resource and Admission Control Subsystem (RACS)*. +- [b-IETF RFC 2638] IETF RFC 2638 (1999), *A Two-bit Differentiated Services Architecture for the Internet*. +- [b-IETF RFC 2702] IETF RFC 2702 (1999), *Requirements for Traffic Engineering Over MPLS*. +- [b-IETF RFC 2814] IETF RFC 2814 (2000), *A Protocol for RSVP-based Admission Control over IEEE 802-style networks*. +- [b-IETF RFC 3312] IETF RFC 3312 (2002), *Integration of Resource Management and Session Initiation Protocol (SIP)*. +- [b-IETF WG Charter] IETF WG Charter (1996), *Integrated Services over Specific Link Layers, IETF Working Group charter*, <>. +- [b-IETF WG Charter 1] IETF WG Charter (2009), *Next Steps In Signalling, IETF Working Group charter*, <>. +- [b-3GPP TR23.802] 3GPP TR23.802 (2007), *Architectural enhancements for end-to-end Quality of Service*. +- [b-ACM Tussle] ACM SIGCOMM Tussle in Cyberspace (2002), *Tussle in Cyberspace: Defining Tomorrow's Internet*. +- [b-ATM forum TM V4.0] The ATM Forum Technical Committee (1996), *Traffic Management Specification Version 4.0*. +- [b-BTTJSE Guaranteed QoS synthesis] Hovell, P., Briscoe, R., Corliano, G., (2005), *Guaranteed QoS synthesis – An example of a scalable core IP quality of service solution*, British Telecommunications Technical Journal Special Edition on IP Quality of Service. +- [b-IFIP TC6 EuQoS] IFIP TC6 Conference EuQoS (2005), *End to End Quality of Service over Heterogeneous Networks (EuQoS)*, In Proc. Network Control and Engineering for QoS, Security and Mobility, IFIP TC6 Conference, NetCon'05, Lannion, France. +- [b-MSF-TR-ARCH-005-FINAL] Gallon, C., Schelén, O., (2005), *Bandwidth management in next generation packet networks*, MSF Technical Report ARCH-005-FINAL. +- [b-PacketCable 050812] pkt-sp-dqos-I12-050812 (1999), *PacketCable Dynamic Quality of Service Specification*. + +[b-QBBB] + +QBBB, Internet2 Bandwidth Broker Working Group, +QBone Bandwidth Broker Architecture. +<>. + +[b-YESSIR] + +YESSIR (1999), YESSIR: *A Simple Reservation +Mechanism for the Internet*, Computer Communication +Review, vol. 29. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3640-201801-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3640-201801-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..66168f0f832931e70de484a3379bfd1ffcf4e423 --- /dev/null +++ b/marked/Q/T-REC-Q.3640-201801-I_PDF-E/raw.md @@ -0,0 +1,827 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3640** + +(01/2018) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for the NGN – +VoLTE/ViLTE network signalling + +# --- **Framework of interconnection of VoLTE/ViLTE-based networks** + +Recommendation ITU-T Q.3640 + +## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|---------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3616 | +| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 | +| VoLTE/ViLTE network signalling | Q.3640–Q.3655 | +| NGN applications | Q.3700–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.3640 + +# Framework of interconnection of VoLTE/ViLTE-based networks + +## Summary + +Recommendation ITU-T Q.3640 specifies the high-level framework of interconnection of long-term evolution (LTE)-based networks for providing interoperable voice and video services. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3640 | 2018-01-13 | 11 | 11.1002/1000/13482 | + +## Keywords + +Framework, interconnection, networks, LTE, ViLTE, VoLTE. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------------|------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 4 | +| 6 | Rationale ..... | 4 | +| 7 | Key issues of interconnection..... | 5 | +| 8 | General principles of interconnection of VoLTE-based networks ..... | 5 | +| 9 | E2E scenarios in terms of interconnection and roaming ..... | 6 | +| 9.1 | E2E scenarios in terms of interconnection and roaming ..... | 6 | +| 9.2 | VoLTE consideration ..... | 12 | +| 9.3 | Device and U/ISIM consideration ..... | 12 | +| 10 | IMS roaming and interworking guidelines ..... | 14 | +| 11 | Services for e2e VoLTE/ViLTE interconnection scenarios ..... | 17 | +| 12 | Interconnection for Inter-IMS scenario ..... | 18 | +| 12.1 | Scenario 1 ..... | 18 | +| 12.2 | Protocol implementation statement (PICS) ..... | 19 | +| Appendix I | – The current standards, guidelines and other documents related to VoLTE interconnection ..... | 23 | +| I.1 | GSMA..... | 23 | +| I.2 | ITU ..... | 24 | +| | Bibliography..... | 25 | + + + +# Recommendation ITU-T Q.3640 + +# Framework of interconnection of VoLTE/ViLTE-based networks + +# 1 Scope + +This Recommendation describes the framework and procedures that should be implemented by operators for establishing an interconnection between voice over long-term evolution / video over long-term evolution (VoLTE/ViLTE)-based networks to achieve worldwide interoperability. + +This Recommendation identifies additional scenarios and requirements for VoLTE/ViLTE interconnection which have not been defined in existing 3GPP standards and GSMA guidelines, as follows: + +- possible E2E scenarios in terms of interconnection and roaming; +- description of the EPC functions which should be supported; +- EPC configuration requirements; +- device and U/ISIM requirements; +- comparison of VoLTE roaming architecture; +- list of mandatory and optional services which should be supported by operators for interconnection and roaming scenarios; +- protocol implementation statement (PICS) needed for the service level agreement (SLA). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.1912.5] Recommendation ITU-T Q.1912.5 (2018), *Interworking between session initiation protocol (SIP) and bearer independent call control protocol or ISDN user part.* +- [ITU-T Q.3403] Recommendation ITU-T Q.3403 v.1 (2016), *IP multimedia call control protocol based on the session initiation protocol and the session description protocol – Basic call: Requirements for the user side and the network side.* +- [ITU-T Q.3617] Recommendation ITU-T Q.3617 v.1 (2015), *Terminating identification presentation and terminating identification restriction using IP multimedia core network subsystem. Protocol specification.* +- [ITU-T Q.3618] Recommendation ITU-T Q.3618 v.1 (2016), *Originating identification presentation and originating identification restriction using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3619] Recommendation ITU-T Q.3619 v.1 (2016), *Communication HOLD using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3620] Recommendation ITU-T Q.3620 v.1 (2016), *Communication diversion using IP multimedia core network subsystem – Protocol specification.* + +- [ITU-T Q.3621] Recommendation ITU-T Q.3621 v.1 (2016), *CONF using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3622] Recommendation ITU-T Q.3622 v.1 (2016), *Communication waiting using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3623] Recommendation ITU-T Q.3623 v.1 (2016), *Explicit communication transfer using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3624] Recommendation ITU-T Q.3624 v.1 (2016), *Malicious communication identification using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3625] ITU-T Q.3625 v.1 (2016), *Completion of communications to busy subscriber and completion of communications by no reply using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3626] Recommendation ITU-T Q.3626 v.1 (2016), *Message waiting indication using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3627] Recommendation ITU-T Q.3627 v.1 (2016), *Closed user group using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3628] Recommendation ITU-T Q.3628 v.1 (2016), *Anonymous communication rejection and communication barring using IP multimedia core network subsystem – Protocol specification.* +- [ITU-T Q.3630] Recommendation ITU-T Q.3630 v.1 (2017), *Inter-IMS network to network interface – Protocol specification.* +- [ITU-T T.38] Recommendation ITU-T T.38 (2015), *Procedures for real-time Group 3 facsimile communication over IP networks.* +- [ITU-T V.152] Recommendation ITU-T V.152 (2010), *Procedures for supporting voice-band data over IP networks.* +- [ETSI TS 124 229] ETSI TS 124 229 (2016-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 10).* +- [ETSI TS 124 604] ETSI TS 124 604 V10.11.0 (2015-10), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS24.604 version 10.11.0 Release 10).* +- [ETSI TS 124 605] ETSI TS 124 605 V10.1.0 (2013-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 Release 10).* +- [ETSI TS 124 606] ETSI TS 124 606 V10.2.0 (2012-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.606 Release 10).* + +- [ETSI TS 124 607] ETSI TS 124 607 V10.1.0 (2014-03), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.607 Release 10)*. +- [ETSI TS 124 608] ETSI TS 124 608 V10.1.0 (2013-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10)*. +- [ETSI TS 124 610] ETSI TS 124 610 V10.2.0 (2013-10), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 Release 10)*. +- [ETSI TS 124 611] ETSI TS 124 611 V10.2.0 (2012-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.611 Release 10)*. +- [ETSI TS 124 615] ETSI TS 124 615 V10.6.0 (2015-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.615 Release 10)*. +- [ETSI TS 124 616] ETSI TS 124 616 V10.0.0 (2011-03), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 Release 10)*. +- [ETSI TS 124 629] ETSI TS 124 629 V10.2.0 (2013-04), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPPTS 24.629 Release 10)*. +- [ETSI TS 124 642] ETSI TS 124 642 V10.7.0 (2013-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.642 Release 10)*. +- [ETSI TS 124 654] ETSI TS 124 654 V10.3.0 (2013-04), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification (3GPP TS 24.654 Release 10)*. + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|------------------------------------------| +| ENUM | telephone Number Mapping | +| GRX/IPX | GPRS Roaming exchange / IP exchange | +| HPMN | Home Public Mobile Network | +| IBCF | Interconnection Border Control Functions | +| II-IMS | Inter-IMS | +| II-NNI | Inter-IMS Network to Network Interface | +| IMS | IP Multimedia Subsystem | +| LBO | Local Breakout | +| LI | Lawful Interception | +| LTE | Long-Term Evolution | +| NNI | Network Network Interface | +| OTT | Over The Top | +| PS | Packet Switched | +| R-NNI | Roaming Network to Network Interface | +| SAE | System Architecture Evolution | +| SIP | Session Initiation Protocol | +| SLA | Service Level Agreement | +| ViLTE | Video over LTE | +| VoLTE | Voice over LTE | +| VoPS | IMS voice over PS Session | +| VPMN | Visited Public Mobile Network | + +# 5 Conventions + +None. + +# 6 Rationale + +The LTE is a popular wireless technology used for providing customers access to IP core networks. By using broadband wireless technology such as LTE, telecommunication operators have finally reached the concept of "all over IP networks" and may provide with a wireless interface any telecommunication service using an all IP environment. + +Among others, LTE may have been used for providing the most popular services such as real-time voice and video (e.g., telephony). However, the implementation of VoLTE/ViLTE poses some challenges to the operators, which aim to establish end-to-end connections between calling parties, because there is only a packet-switched (PS) network and the service control is provided by an IP multimedia subsystem (IMS). + +Different VoLTE/ViLTE solutions are available for operators. However these solutions are not always interoperable and VoLTE/ViLTE roaming procedures are not agreed and therefore may not be implemented. + +This Recommendation aims to specify common requirements to the interconnection of VoLTE/ViLTE-based networks. + +# **7 Key issues of interconnection** + +There are the following key issues of interconnection among VoLTE/ViLTE-based networks: + +- different options for signalling protocols used for Inter-IMS interconnection, which can support all existing services (basic call and supplementary services); +- different options for roaming scenarios (there are no strict requirements for operators and no default option); +- charging (e.g., roaming charges, calls using interconnection networks); +- numbering/addressing (e.g., ENUM resolution, ITU-T E.164 → SIP-URI conversion); +- floating delay (problem of providing legacy services and applications, e.g., Fax/Modem over IP); +- lawful interception; +- data retention; +- emergency services (e.g., emergency call 112). + +# **8 General principles of interconnection of VoLTE-based networks** + +The voice over LTE (VoLTE) and video over LTE (ViLTE) services are the services that aim to deliver voice and video communication over packet-based networks which include LTE technology, on the access stratum. It means that VoLTE/ViLTE services might be provided by either traditional fixed or mobile telecommunication operators who implemented LTE technology as access technology to its core IP network. + +Also, VoLTE/ViLTE services are so-called "managed" voice and video services which are based on standardized SIP/IMS signalling and provided by telecommunication operators, while over-the-top (OTT) applications are services which are basically provided in public Internet by independent third parties, without standardized signalling protocols, traffic prioritization and guaranteed quality of services. + +An IMS platform is used as a service control stratum which is used for managing VoLTE/ViLTE sessions. The reference architecture of IMS is shown in Figure 8-1. + +![Figure 8-1 – Reference architecture of the IP multimedia core network subsystem [b-ETSI TS 123 002]](36ac3e730a00d3f42d3400f5709f641a_img.jpg) + +The diagram illustrates the reference architecture of the IP multimedia core network subsystem (IMS). It is enclosed in a red dashed box labeled 'IMS Subsystem'. + - Top level: 'IP multimedia networks' connected via interfaces like Izi, Mm, Ici, and Mm to internal nodes. + - External networks: 'CS network' and 'Legacy mobile signalling networks' are shown at the top. + - Internal nodes within the IMS Subsystem include: + - Control Plane: P-CSCF, I-CSCF, S-CSCF, IBCF, BGCF, MGCF, MRFC, AS (Application Server). + - User Plane/Media: TrGW, IM MGW, MRFP. + - Databases: HSS (Home Subscriber Server), SLB (Subscription Locator Function). + - User Equipment: UE. + - Interfaces are labeled with standard codes: Mb, Izi, Mm, Ici, Ix, Mx, Ma, ISC, Sh, Cx, Mw, Mi, Mg, Mn, Mr, Cr, Mr', Rc, Ut, Dx, Gm, CS, Mk, Mj. + - Connections are represented by solid lines (user plane/media) and dashed lines (signalling/control plane). + +Figure 8-1 – Reference architecture of the IP multimedia core network subsystem [b-ETSI TS 123 002] + +**Figure 8-1 – Reference architecture of the IP multimedia core network subsystem +[b-ETSI TS 123 002]** + +VoLTE/ViLTE interconnection implies interconnection of IMS platforms for providing VoLTE/ViLTE and legacy e2e sessions. + +There are the following types of interconnection between IMS-based telecommunication operators: + +- interconnection for delivering sessions among users of different operators (hereafter interworking scenarios); +- interconnection for providing roaming of users of the home networks in visited networks (hereafter roaming scenarios). + +There are also options for interconnection between the VoLTE/ViLTE and IMS-based networks with existing legacy networks (e.g., PSTN, PLMN). + +The ENUM/DNS translation mechanism as specified in [b-IETF RFC 3761] can be used by all IMS nodes that require ITU-T E.164 address to SIP URI resolution. Subsequently, the GSMA published [b-GSMA PRD IR.67] and [b-GSMA PRD NG.105]. + +### 9 E2E scenarios in terms of interconnection and roaming + +#### 9.1 E2E scenarios in terms of interconnection and roaming + +According to general principles there are the following key e2e scenarios: + +Interworking scenarios (established connection): + +6 Rec. ITU-T Q.3640 (01/2018) + +![Diagram of VoLTE/ViLTE - IMS/MMTel interconnection scenarios. A smartphone on the left is connected to a cloud labeled 'VoLTE/ViLTE', which is connected via a thick double-headed arrow to another cloud labeled 'IMS/MMTel'. This second cloud is connected to a desktop phone on the right. The text 'Q.3640(18)_F9-1' is below the desktop phone.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Diagram of VoLTE/ViLTE - IMS/MMTel interconnection scenarios. A smartphone on the left is connected to a cloud labeled 'VoLTE/ViLTE', which is connected via a thick double-headed arrow to another cloud labeled 'IMS/MMTel'. This second cloud is connected to a desktop phone on the right. The text 'Q.3640(18)\_F9-1' is below the desktop phone. + +**Figure 9-1 – VoLTE – IMS/MMTel interconnection scenarios** + +![Diagram of VoLTE - Legacy network interconnection scenarios. A smartphone on the left is connected to a cloud labeled 'VoLTE/ViLTE', which is connected via a thick double-headed arrow to another cloud labeled 'Legacy network'. This second cloud is connected to a desktop phone on the right. The text 'Q.3640(18)_F9-2' is below the desktop phone.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +Diagram of VoLTE - Legacy network interconnection scenarios. A smartphone on the left is connected to a cloud labeled 'VoLTE/ViLTE', which is connected via a thick double-headed arrow to another cloud labeled 'Legacy network'. This second cloud is connected to a desktop phone on the right. The text 'Q.3640(18)\_F9-2' is below the desktop phone. + +**Figure 9-2 – VoLTE – Legacy network interconnection scenarios** + +![Diagram of VoLTE/ViLTE - VoLTE/ViLTE interconnection scenarios. A smartphone on the left is connected to a cloud labeled 'VoLTE/ViLTE', which is connected via a thick double-headed arrow to another cloud also labeled 'VoLTE/ViLTE'. This second cloud is connected to another smartphone on the right. The text 'Q.3640(18)_F9-3' is below the second smartphone.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Diagram of VoLTE/ViLTE - VoLTE/ViLTE interconnection scenarios. A smartphone on the left is connected to a cloud labeled 'VoLTE/ViLTE', which is connected via a thick double-headed arrow to another cloud also labeled 'VoLTE/ViLTE'. This second cloud is connected to another smartphone on the right. The text 'Q.3640(18)\_F9-3' is below the second smartphone. + +**Figure 9-3 – VoLTE/ViLTE – VoLTE/ViLTE interconnection scenarios** + +**Table 9-1 – E2E scenarios in terms of interconnection and roaming** + +| No. | Scenario | Description | Roaming options | +|-------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VoLTE – IMS interworking scenarios | | | | +| 1 | Scenario 1 | User UE1 (a) is in the IMS network A, UE2 (a) in HPMN (a) | | +| 2 | Scenario 1A | User UE 1 (a) is in the IMS network A, UE2 (a) in HPMN (a) with CSFB (circuit switched fallback)
NOTE – Occurs only in the case if IMS voice over PS Session (VoPS) is not supported in the home public mobile network (HPMN)'s LTE networks | | +| 3 | Scenario 1B | User UE1 (a) is in the IMS network A, UE2 (a) in HPMN (a) is moving from 4G to 3G coverage with SRVCC | | +| 4 | Scenario 1C | User UE1 (a) is in the IMS network A, UE2 (a) roamed in VPMN (b) |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| +| 5 | Scenario 1D | User UE1 (a) is in the IMS network A, UE2 (a) roamed in VPMN (b) moving from 4G to 3G coverage with SRVCC |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| +| VoLTE – Legacy network scenarios | | | | +| 6 | Scenario 2 | User UE1 (a) is in the legacy network A, UE2 (a) is in HPMN (a) | | +| 7 | Scenario 2A | User UE1 (a) is in the legacy network A, UE2 (a) is in HPMN (a), with CSFB (circuit switched fallback)
NOTE – occurs only in the case if VoPS is not supported in the HPMN's LTE N/W | | +| 8 | Scenario 2B | User UE1 (a) is in the legacy network A , UE2 (a) is in HPMN (a), roamed in VPMN (b) moving from 4G to 3G coverage with SRVCC | | + +**Table 9-1 – E2E scenarios in terms of interconnection and roaming** + +| No. | Scenario | Description | Roaming options | +|------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 9 | Scenario 3 | User UE1(a) is in the legacy network A , UE2 (a) is in VPMN (b) |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| +| VoLTE – VoLTE and ViLTE – ViLTE interconnection scenarios | | | | +| 10 | Scenario 4 | UE1 (a) is in HPMN (a), UE2 (b) is in HPMN (b) | | +| 11 | Scenario 4A | UE1 (a) is in HPMN (a), UE2 (b) is in HPMN (b) with CSFB (circuit switched fallback).
NOTE – occurs only in the case if VoPS is not supported in HPMN. | | +| 12 | Scenario 4B | UE1 (a) is in HPMN (a), UE2 (b) is in HPMN (b) moving from 4G to 3G coverage with SRVCC | | +| 13 | Scenario 4C | UE1 (a) is in HPMN (a) with CSFB (circuit switched fallback). UE2 (b) is in HPMN (b). | | +| 14 | Scenario 4D | UE1 (a) is in HPMN (a) moving from 4G to 3G coverage with SRVCC, UE2 (b) is in HPMN (b). | | +| VoLTE – VoLTE and ViLTE – ViLTE roaming scenarios | | | | +| 15 | Scenario 5 | UE1 (a) is in HPMN (a), UE3 (a) roamed in VPMN (b) |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| +| 16 | Scenario 5A | UE1 (a) is in HPMN (a), UE3 (a) roamed in VPMN (b) with CSFB (circuit switched fallback).
NOTE – Occurs only in the case if VoPS is not supported in VPMN. | | +| 17 | Scenario 5B | UE1 (a) is in HPMN (a), UE3 (a) roamed in VPMN (b) moving from 4G to 3G coverage with SRVCC |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| + +**Table 9-1 – E2E scenarios in terms of interconnection and roaming** + +| No. | Scenario | Description | Roaming options | +|-----|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| 18 | Scenario 5C | UE1 (a) in HPMN (a) with CSFB (circuit switched fallback), UE3 (a) roamed in VPMN (b) | Roaming options:
– Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 19 | Scenario 5D | UE1 (a) is in HPMN (a) moving from 4G to 3G coverage with SRVCC, UE3 (a) roamed in VPMN (b) | Roaming options:
– Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 20 | Scenario 6 | UE1 (a) calls UE3 (a), both roamed in VPMN (b) | – Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 21 | Scenario 6A | UE1 (a) calls UE3 (a), both roamed in VPMN (b), UE1 (a) with CSFB (circuit switched fallback)
NOTE – occurs only in the case if VoPS is not supported in VPMN of UE1. | – Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 22 | Scenario 6B | UE1 (a) calls UE3 (a), both roamed in VPMN (b), UE1 (a) is moving from 4G to 3G coverage with SRVCC | – Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 23 | Scenario 6C | UE1 (a) calls UE3 (a), both roamed in VPMN (b), UE2 (a) is moving from 4G to 3G coverage with SRVCC | – Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 24 | Scenario 7 | UE1 (a) roamed in VPMN (b), UE2 (b) roamed in VPMN (a) | – Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | +| 25 | Scenario 8A | UE1 (a) roamed in VPMN (b), UE2 (b) roamed in VPMN (a), UE1 (a) with CSFB (circuit switched fallback) | – Local breakout VPMN routing architecture (LBO-VR)
– LBO home routing architecture (LBO-HR)
– S8HR VoLTE roaming architecture | + +**Table 9-1 – E2E scenarios in terms of interconnection and roaming** + +| No. | Scenario | Description | Roaming options | +|-----|-------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 26 | Scenario 7B | UE1 (a) roamed in VPMN (b), UE2 (b) roamed in VPMN (a) and UE2 (b) is moving from 4G to 3G coverage with SRVCC |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| +| 27 | Scenario 7C | UE1 (a) roamed in VPMN (b), UE2 (b) roamed in VPMN (a), and UE1 (a) is moving from 4G to 3G coverage with SRVCC |
  • – Local breakout VPMN routing architecture (LBO-VR)
  • – LBO home routing architecture (LBO-HR)
  • – S8HR VoLTE roaming architecture
| +| 28 | Scenario 8 | The VoLTE subscriber UE1 (a) in the HPMN (a) is calling the 2G/3G user UE2 (b) in HPMn (b) | | +| 29 | Scenario 9 | The VoLTE subscribers UE1 (a) and UE 2(a) are subscribed in the HPMN (a). Subscribers UE1 (a) is roaming in 2G/3G VPMN (b). | | +| 30 | Scenario 10 | The VoLTE subscribers UE1 (a) and UE 2(a) are subscribed in the HPMN (a). Subscribers UE1 (a) and UE2 (a) are roaming in 2G/3G VPMN (b). | | + +## **9.2 VoLTE consideration** + +### **9.2.1 EPC consideration** + +An EPC network should support general VoLTE related functions, for example, basic voice and video call. These are: + +- The visited network MME shall support VoLTE capability indication to UE, "IMS voice over PS" in order to select voice solution. +- The visited network MME may support the Sv interface and eSRVCC handover control function. +- SAE-GW should support the establishment of the dedicated bearer with QCI=8/9, QCI=1 and QCI=2. +- SAE-GW should support IPv6 PDN type. +- P-GW shall support the P-CSCF discovery function and allocate the P-CSCF IP address to the UE. +- PCRF shall guarantee end-to-end QoS by interworking with the IMS and AF via Rx interface. + +### **9.2.2 EPC configuration requirements** + +#### **MME** + +- The MME in the visit network shall configure the PLMN for the inbound roamer, so that the inbound roamer could attach to the network. +- The MME in the visit network shall configure "IMS voice over PS" for the inbound roamer. +- LBO VR: The MME in the visit network shall be able to resolve IMS APN to the PGW address in the visit network. +- S8 HR: The MME in the visit network should resolve IMS APN into the PGW address in the home network instead of the visit network. If the home network cannot resolve IMS APN to P-GW, manually configuring it to the MME in the visited network would be also acceptable for this trial. + +## **9.3 Device and U/ISIM consideration** + +### **9.3.1 Multi-Mode and Multi-band Terminal** + +To meet the requirements for domestic frequency access and international roaming, five radio modes including LTE FDD, TD-LTE, TD-SCDMA, WCDMA, and GSM should be supported. The multi-mode and multi-band requirements are as follow. + +- GSM: Band3, Band8 and Band2 are mandatory. Besides, Band5 is recommended. +- TD-SCDMA: Band34 and Band39 are mandatory. +- TD-LTE: Band39, Band40 and Band41 (at least supporting 2575-2635 MHz) are mandatory. If the terminals support Band41 without Band38, it must support the frequency mutual identification via mFBI. +- WCDMA: Band1, Band2 and Band5 are mandatory. +- LTE FDD: Band3 and Band7 are mandatory. Besides, Band1, Band17, Band4 and Band20 are recommended. + +Additionally, compatible bands based on bilateral/multi-lateral discussions will be supported by the Device. Other multimode and multiband terminals could also be introduced in accordance with demand. + +### **9.3.2 General requirements for VoLTE terminal** + +To achieve excellent user experience, VoLTE terminals shall have performance requirements that are comparable with mainstream commercial terminals in the following aspects: operation system, hardware, software, MTBF, standby time, communication duration. + +Regarding the outbound roaming requirement, VoLTE handsets should support CSFB from LTE to WCDMA/GSM and support four kinds of functions for VoLTE. + +#### **9.3.2.1 RAN features** + +- Support SPS, TTI-Bundling, RoHC, Connected-DRX and its combinations; support interoperation from LTE to GSM via eSRVCC, aSRVCC, mid-call SRVCC; support SRVCC related measurement capability and capability report; +- support UE-based fast return to LTE after SRVCC CS call ends; +- support IPv4, IPv6 and IPv4v6 dual-stacks; +- support multi-PDN connections; delete IMS PDN when moving out of VoLTE coverage; +- support EPS bearer combinations for VoLTE service; support end-to-end QoS. + +#### **9.3.2.2 IMS function on control plane** + +- Support the standard SIP/IMS protocol in order to interwork with the global IMS networks; +- support derivation of IMS identifiers from USIM, if ISIM is not introduced; +- support IMS exceptions handling; +- support RTP/RTCP; +- support IMS authorization and authentication etc; +- support early media; +- support precondition; +- support upgrade and downgrade between voice and video call; +- support supplementary service configuration via Ut/XCAP. + +#### **9.3.2.3 IMS function on media plane** + +- Audio Codec: Entities in the IMS core network that terminate the user plane supporting speech communication and supporting TFO and/or TrFO shall support AMR speech codec modes 12.2, 7.4, 5.9 and 4.75. Entities in the IMS core network that terminate the user plane supporting wideband speech communication and supporting TFO and/or TrFO shall support AMR-WB speech codec modes 12.65, 8.85 and 6.60. +- Video Codec: H.264 640\*480@30fps; 720P@30fps is recommended. +- Quality enhanced features: Noise Suppression, Echo Cancellation, jitter buffer, lip sync. + +#### **9.3.2.4 Services requirements** + +- Voice call + - Support standard voice calls and HD voice calls; + - support voice domain transition between VoLTE and CSFB; support voice continuity among different scenarios; + - support SilentRedial. +- Message + - Support SMS over IP, SMS over CS; + - support MMS. +- Video call + +- Support video call when UE within VoLTE coverage. +- Supplementary services + - Supported enhanced conference calls; + - support IMS supplementary services. +- IMS emergency services. + +# 10 IMS roaming and interworking guidelines + +According to [b-GSMA PRD IR.65] there are different possible options for IMS interconnection which should meet the following requirements: + +- 1) The routing of media for voice and video over IMS when call originator is roaming should be at least as optimal as that of current circuit switched (CS) domains. +- 2) The charging model for roaming used in the CS domain shall be maintained in VoIMS. +- 3) Allow the HPMN to decide, based on service and commercial considerations and regulatory obligations, to enforce the routing of the originated traffic to itself (home routing). + +The UE has obtained IP connectivity in the visited network and might have access to home network's IMS services via one of the following options: + +**Option 1** – Target IMS roaming solution, IMS is required in both VPLMN and HPLMN + +The UE has obtained IP connectivity from the visited network and is connected to the P-CSCF in the visited network which establishes connections using the home IMS platform; traffic is routed directly by the visited network. + +**Option 2** – Data local breakout, but IMS home routed, IMS is not needed in VPLMN + +The UE has obtained IP connectivity from the visited network and is connected to the P-CSCF in the visited network which itself is connected to the home IMS platform; traffic is routed via the home network. + +**Option 3** – The UE has obtained IP connectivity from the home network and is directly connected to the home IMS platform; traffic is routed via the home network. Data and IMS are both home routed, IMS is not needed in VPLMN. + +![Figure 10-1: Local breakout VPMN routing architecture (LBO-VR). This diagram illustrates the network architecture for local breakout in a VPMN. It is divided into four main sections: VPMN of A party, HPMN of A party, VPMN of B party, and HPMN of B party. In the VPMN of A party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of A party. In the HPMN of A party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of A party. In the VPMN of B party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of B party. In the HPMN of B party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of B party. A legend at the bottom indicates that blue lines represent the User plane and red lines represent the Control plane. The diagram is labeled Q.3640(18)_F10-1.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 10-1: Local breakout VPMN routing architecture (LBO-VR). This diagram illustrates the network architecture for local breakout in a VPMN. It is divided into four main sections: VPMN of A party, HPMN of A party, VPMN of B party, and HPMN of B party. In the VPMN of A party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of A party. In the HPMN of A party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of A party. In the VPMN of B party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of B party. In the HPMN of B party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of B party. A legend at the bottom indicates that blue lines represent the User plane and red lines represent the Control plane. The diagram is labeled Q.3640(18)\_F10-1. + +**Figure 10-1 – Local breakout VPMN routing architecture (LBO-VR)** +**[b-GSMA PRD IR.65]** + +![Figure 10-2: LBO home routing architecture (LBO-HR). This diagram illustrates the network architecture for LBO home routing. It is divided into four main sections: VPMN of A party, HPMN of A party, VPMN of B party, and HPMN of B party. In the VPMN of A party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of A party. In the HPMN of A party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of A party. In the VPMN of B party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of B party. In the HPMN of B party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of B party. A legend at the bottom indicates that blue lines represent the User plane and red lines represent the Control plane. The diagram is labeled Q.3640(18)_F10-2.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Figure 10-2: LBO home routing architecture (LBO-HR). This diagram illustrates the network architecture for LBO home routing. It is divided into four main sections: VPMN of A party, HPMN of A party, VPMN of B party, and HPMN of B party. In the VPMN of A party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of A party. In the HPMN of A party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of A party. In the VPMN of B party, a UE is connected to a P-GW, which is connected to an IMS-AGW (TrGW). The P-GW is also connected to a P-CSCF, which is connected to an IBCF. The IBCF is connected to the HPMN of B party. In the HPMN of B party, the IBCF is connected to an S-CSCF, which is connected to a TAS and an HSS. The IMS-AGW (TrGW) is connected to the HPMN of B party. A legend at the bottom indicates that blue lines represent the User plane and red lines represent the Control plane. The diagram is labeled Q.3640(18)\_F10-2. + +**Figure 10-2 – LBO home routing architecture (LBO-HR)** +**[b-GSMA PRD IR.65]** + +![Figure 10-3 – S8HR VoLTE Roaming architecture diagram. The diagram shows the network architecture for VoLTE roaming. On the left, the VPLMN of A party contains an E-UTRAN connected to an MME, which is connected to an SGW. The SGW is connected to the IPX. The IPX connects to the HPLMN of A party. In the HPLMN, the SGW connects to a PGW, which is connected to an IMS AGW/TrGW. The IMS AGW/TrGW is connected to an IBCF/BGCF/MGCF, which is connected to a B-PARTY via TDM or IPX. The IMS AGW/TrGW is also connected to a P-CSCF, which is connected to an S-CSCF. The S-CSCF is connected to a TAS. The HSS is connected to the MME and the P-CSCF. The PCRF is connected to the HSS and the PGW. A legend at the bottom indicates that blue lines represent the User plane (RTP media) and red lines represent the Control plane (SIP). The diagram is labeled Q.3640(18)_F10-3.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Figure 10-3 – S8HR VoLTE Roaming architecture diagram. The diagram shows the network architecture for VoLTE roaming. On the left, the VPLMN of A party contains an E-UTRAN connected to an MME, which is connected to an SGW. The SGW is connected to the IPX. The IPX connects to the HPLMN of A party. In the HPLMN, the SGW connects to a PGW, which is connected to an IMS AGW/TrGW. The IMS AGW/TrGW is connected to an IBCF/BGCF/MGCF, which is connected to a B-PARTY via TDM or IPX. The IMS AGW/TrGW is also connected to a P-CSCF, which is connected to an S-CSCF. The S-CSCF is connected to a TAS. The HSS is connected to the MME and the P-CSCF. The PCRF is connected to the HSS and the PGW. A legend at the bottom indicates that blue lines represent the User plane (RTP media) and red lines represent the Control plane (SIP). The diagram is labeled Q.3640(18)\_F10-3. + +**Figure 10-3 – S8HR VoLTE Roaming architecture [b-GSMA PRD IR.65]** + +For S8HR VoLTE roaming architecture, regulatory requirements (legal interception and emergency calling) have triggered additional specification work currently being performed in 3GPP. Deliverables are confirmed to be included in 3GPP Release 14. + +**Table 10-1 – Comparison of VoLTE roaming architecture** + +| Item | Option 1 LBO-VR
(target IMS roaming solution, IMS is required in both VPLMN and HPLMN) | Option 2, LBO-HR
(data local breakout, but IMS home routed, IMS is not needed in VPLMN) | Option 3 S8HR
Data and IMS are both home routed, IMS is not needed in VPLMN | +|---------------------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| HPLMN with VoLTE implementation | Required | Required | Required | +| VPLMN with VoLTE implementation | Required | Not required | Not required | +| IMS service over GRX | Not required | Required | Required | +| Charging depending on evolved packet core (EPC) | Optional (charge on IMS service layer) | Required | Required | +| Policy and charging control mode | HPLMN hPCRF can control the VPLMN vPCRF via S9 Interface (S9 interface is optional) | HPLMN hPCRF controls VPLMN vPCRF via S9 Interface or via roaming agreement and support of common QCIs | HPLMN hPCRF controls HPLMN PGW, 2/3G and 4G (e.g., web browsing) data roaming via S8 | +| Single radio voice call continuity (SRVCC) support capability | Fully supported | Supported | Partially supported | +| VoLTE local emergency call | Supported | Supported | Not supported | +| VoLTE local LI | Supported | Supported | Not supported (LI will be possible at the S-GW (under development in Rel. 14 of 3GPP)). | +| LBO with optimal media routing (OMR) | Supported | Not supported | Not supported | + +![Figure 10-4: Roaming architecture scenario with home routed traffic. The diagram shows a UE connected to E-UTRAN, which is connected to an MME. The MME is connected to a Serving gateway, which is connected to a PDN gateway. The PDN gateway is connected to Operator's IP services. The MME is also connected to SGSN, which is connected to UTRAN and GERAN. The SGSN is connected to the PDN gateway via S3, S4, and S12 interfaces. The MME is connected to the HSS via S6a. The PDN gateway is connected to the HSS via S6a. The PDN gateway is connected to the PCRF via Gx. The PCRF is connected to the Operator's IP services via Rx. The diagram is divided into HPLMN and VPLMN by a dashed orange line.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure 10-4 illustrates a roaming architecture scenario with home routed traffic. The diagram shows the following components and interfaces: + +- UE** (User Equipment) connected to **E-UTRAN** via "LTE-Uu". +- E-UTRAN** connected to **MME** via S1-MME. +- MME** connected to **Serving gateway** via S1-U. +- Serving gateway** connected to **PDN gateway** via S8. +- PDN gateway** connected to **Operator's IP services (e.g., IMS, PSS etc.)** via SGi. +- PDN gateway** connected to **PCRF** via Gx. +- PCRF** connected to **Operator's IP services** via Rx. +- MME** connected to **HSS** via S6a. +- MME** connected to **SGSN** via S3. +- SGSN** connected to **UTRAN** and **GERAN**. +- SGSN** connected to **PDN gateway** via S4 and S12. +- MME** connected to **Serving gateway** via S10 and S11. + +The diagram is divided into **HPLMN** (Home PLMN) and **VPLMN** (Visited PLMN) by a dashed orange line. The HPLMN contains the HSS, PCRF, and PDN gateway. The VPLMN contains the UTRAN, GERAN, SGSN, MME, and Serving gateway. + +Q.3640(18)\_F10-4 + +Figure 10-4: Roaming architecture scenario with home routed traffic. The diagram shows a UE connected to E-UTRAN, which is connected to an MME. The MME is connected to a Serving gateway, which is connected to a PDN gateway. The PDN gateway is connected to Operator's IP services. The MME is also connected to SGSN, which is connected to UTRAN and GERAN. The SGSN is connected to the PDN gateway via S3, S4, and S12 interfaces. The MME is connected to the HSS via S6a. The PDN gateway is connected to the HSS via S6a. The PDN gateway is connected to the PCRF via Gx. The PCRF is connected to the Operator's IP services via Rx. The diagram is divided into HPLMN and VPLMN by a dashed orange line. + +**Figure 10-4 – Roaming architecture scenario with home routed traffic** + +![Figure 10-5: Roaming architecture for local breakout, with home operator's application functions only. The diagram shows a UE connected to E-UTRAN, which is connected to an MME. The MME is connected to a Serving gateway, which is connected to a PDN gateway. The PDN gateway is connected to Visited operator's IP services. The MME is also connected to SGSN, which is connected to UTRAN and GERAN. The SGSN is connected to the PDN gateway via S3, S4, and S12 interfaces. The MME is connected to the HSS via S6a. The PDN gateway is connected to the HSS via S6a. The PDN gateway is connected to the V-PCRF via Gx. The V-PCRF is connected to the Visited operator's IP services via Rx. The V-PCRF is connected to the H-PCRF via S9. The diagram is divided into HPLMN and VPLMN by a dashed orange line.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +Figure 10-5 illustrates a roaming architecture for local breakout, with home operator's application functions only. The diagram shows the following components and interfaces: + +- UE** (User Equipment) connected to **E-UTRAN** via "LTE-Uu". +- E-UTRAN** connected to **MME** via S1-MME. +- MME** connected to **Serving gateway** via S1-U. +- Serving gateway** connected to **PDN gateway** via S5. +- PDN gateway** connected to **Visited operator's IP services** via SGi. +- PDN gateway** connected to **V-PCRF** via Gx. +- V-PCRF** connected to **Visited operator's IP services** via Rx. +- V-PCRF** connected to **H-PCRF** via S9. +- MME** connected to **HSS** via S6a. +- MME** connected to **SGSN** via S3. +- SGSN** connected to **UTRAN** and **GERAN**. +- SGSN** connected to **PDN gateway** via S4 and S12. +- MME** connected to **Serving gateway** via S10 and S11. + +The diagram is divided into **HPLMN** (Home PLMN) and **VPLMN** (Visited PLMN) by a dashed orange line. The HPLMN contains the HSS, H-PCRF, and PDN gateway. The VPLMN contains the UTRAN, GERAN, SGSN, MME, Serving gateway, and V-PCRF. + +Q.3640(18)\_F10-5 + +Figure 10-5: Roaming architecture for local breakout, with home operator's application functions only. The diagram shows a UE connected to E-UTRAN, which is connected to an MME. The MME is connected to a Serving gateway, which is connected to a PDN gateway. The PDN gateway is connected to Visited operator's IP services. The MME is also connected to SGSN, which is connected to UTRAN and GERAN. The SGSN is connected to the PDN gateway via S3, S4, and S12 interfaces. The MME is connected to the HSS via S6a. The PDN gateway is connected to the HSS via S6a. The PDN gateway is connected to the V-PCRF via Gx. The V-PCRF is connected to the Visited operator's IP services via Rx. The V-PCRF is connected to the H-PCRF via S9. The diagram is divided into HPLMN and VPLMN by a dashed orange line. + +**Figure 10-5 – Roaming architecture for local breakout, with home operator's application functions only** + +# 11 Services for e2e VoLTE/ViLTE interconnection scenarios + +Among others there are some key services which have to be provided over the IMS-based networks for the e2e interconnection scenarios (see clause 9). + +Table 11-1 specifies the list of mandatory and optional services which should be supported by operators for interconnection and roaming scenarios. + +**Table 11-1 – List of mandatory and optional services which should be supported by operators for interconnection and roaming scenarios** + +| # | Service | ITU-T Recommendation | Relevant standard developed by other SDO | Status | +|-------------------------------|---------------------------------------|----------------------|------------------------------------------|--------| +| 1 | Basic call (voice and video sessions) | Q.3403 v.1 | ETSI TS 124.229 | M | +| Supplementary services | | | | | +| 2 | TIP/TIR | Q.3617 v.1 | ETSI TS 124.608 | O | +| 3 | OIP/OIR | Q.3618 v.1 | ETSI TS 124.607 | M | +| 4 | HOLD | Q.3619 v.1 | ETSI TS 124.610 | O | +| 5 | CDIV | Q.3620 v.1 | ETSI TS 124.604 | O | +| 6 | CONF | Q.3621 v.1 | ETSI TS 124.605 | O | +| 7 | CW | Q.3622 v.1 | ETSI TS 124.615 | O | +| 8 | ECT | Q.3623 v.1 | ETSI TS 124.629 | O | +| 9 | MCID | Q.3624 v.1 | ETSI TS 124.616 | O | +| 10 | CC | Q.3625 v.1 | ETSI TS 124.642 | O | +| 11 | MWI | Q.3626 v.1 | ETSI TS 124.606 | O | +| 12 | CUG | Q.3627 v.1 | ETSI TS 124.654 | M | +| 13 | ACR-CB | Q.3628 v.1 | ETSI TS 124.611 | O | + +NOTE – M: mandatory; O: optional. + +# 12 Interconnection for Inter-IMS scenario + +## 12.1 Scenario 1 + +The Inter-IMS scenario is used for establishing service sessions between users of two IMS platforms (e.g., long distance call). + +The reference configuration is depicted in Figure 12-1. + +![Figure 12-1 – Reference configuration for interconnection. The diagram shows a 3GPP network on the left connected to three different network types on the right. The 3GPP network contains three main components: CS-IBCF (CS-TrGW), IBCF (TrGW), and S-CSCF (GW). The CS-IBCF connects to a SIP-I network via TS 29.235 (nodes), TS 23.231; TS 29.231 (protocol), and ITU-T Q.1912.5. The IBCF connects to a 3GPP IMS network via an II-NNI/R-NNI interface, with TS 23.228 (architecture) and TS 29.165 (profile). The S-CSCF connects to a SIP network or IMS network without IBCF via TS 29.162. The 3GPP IMS network also contains an IBCF (TrGW).](171115f072e42b379238ed0dd438e9d7_img.jpg) + +Figure 12-1 illustrates the reference configuration for interconnection between a 3GPP network and other networks. The 3GPP network (left) contains three main components: CS-IBCF (CS-TrGW), IBCF (TrGW), and S-CSCF (GW). The CS-IBCF connects to a SIP-I network (top right) via TS 29.235 (nodes), TS 23.231; TS 29.231 (protocol), and ITU-T Q.1912.5. The IBCF connects to a 3GPP IMS network (middle right) via an II-NNI/R-NNI interface, with TS 23.228 (architecture) and TS 29.165 (profile). The S-CSCF connects to a SIP network or IMS network without IBCF (bottom right) via TS 29.162. The 3GPP IMS network also contains an IBCF (TrGW). The diagram is labeled Q.3640(18)\_F12-1. + +Figure 12-1 – Reference configuration for interconnection. The diagram shows a 3GPP network on the left connected to three different network types on the right. The 3GPP network contains three main components: CS-IBCF (CS-TrGW), IBCF (TrGW), and S-CSCF (GW). The CS-IBCF connects to a SIP-I network via TS 29.235 (nodes), TS 23.231; TS 29.231 (protocol), and ITU-T Q.1912.5. The IBCF connects to a 3GPP IMS network via an II-NNI/R-NNI interface, with TS 23.228 (architecture) and TS 29.165 (profile). The S-CSCF connects to a SIP network or IMS network without IBCF via TS 29.162. The 3GPP IMS network also contains an IBCF (TrGW). + +**Figure 12-1 – Reference configuration for interconnection** + +The architecture of IMS interconnection for Inter-IMS scenario is shown in Figure 12-2. + +![Figure 12-2: Interconnection for inter-IMS scenario. The diagram shows two IMS CN subsystems, Network A and Network B, connected via an II-NNI interface. Network A includes P-CSCF, S-CSCF, I-CSCF, BGCF, IBCF, and TrGW. Network B includes P-CSCF, S-CSCF, I-CSCF, BGCF, IBCF, and TrGW. The II-NNI interface is highlighted with a red oval and contains reference points Ici and Izi. Signalling is represented by dashed lines and Bearer by solid lines. Reference points Mx, Ix, and Iz are also shown.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +Legend: ----- Signalling, — Bearer + +Q.3640(18)\_F12-2 + +Figure 12-2: Interconnection for inter-IMS scenario. The diagram shows two IMS CN subsystems, Network A and Network B, connected via an II-NNI interface. Network A includes P-CSCF, S-CSCF, I-CSCF, BGCF, IBCF, and TrGW. Network B includes P-CSCF, S-CSCF, I-CSCF, BGCF, IBCF, and TrGW. The II-NNI interface is highlighted with a red oval and contains reference points Ici and Izi. Signalling is represented by dashed lines and Bearer by solid lines. Reference points Mx, Ix, and Iz are also shown. + +**Figure 12-2 – Interconnection for inter-IMS scenario [b-ETSI TS 123.228]** + +![Figure 12-3: IM CN subsystem to CS network logical interworking reference model. The diagram shows the interconnection between an IM CN subsystem and a CS network. The IM CN subsystem includes BGCF, CSCF, TrGW, and (Note 1). The CS network includes MGCF, IM-MGW, and SIP-I. Reference points Mj, Mg, Nc, Mn, Mb, and Nb are shown. User plane is represented by solid lines and Control plane by dashed lines.](26d664119ad25250780f554633444e54_img.jpg) + +Legend: — User plane, ----- Control plane + +Q.3640(18)\_F12-3 + +Figure 12-3: IM CN subsystem to CS network logical interworking reference model. The diagram shows the interconnection between an IM CN subsystem and a CS network. The IM CN subsystem includes BGCF, CSCF, TrGW, and (Note 1). The CS network includes MGCF, IM-MGW, and SIP-I. Reference points Mj, Mg, Nc, Mn, Mb, and Nb are shown. User plane is represented by solid lines and Control plane by dashed lines. + +**Figure 12-3 – IM CN subsystem to CS network logical interworking reference model [b-ETSI TS 129 235]** + +According to [b-ETSI TS 123.228] there are two reference points Ici and Izi which are used on II-NNI. + +The Ici reference point allows IBCFs to communicate with each other in order to provide the communication and forwarding of SIP signalling messaging between IMS platforms, while the Izi reference point allows TrGWs to forward media streams between IMS-based networks. The reference point Ici is based on SIP signalling which has to be adapted to IMS features. + +Table 12-1 provides a list of signalling protocols and relevant standards used on both interfaces. + +**Table 12-1 – Protocols used on II-NNI interfaces** + +| Interface | Type of protocol | Standard | +|-----------|------------------|--------------------------------------------------------------------------------------------------------------| +| Nc/Ici | SIP, SIP-I | – SIP-I [ITU-T Q.1912.5] (NOTE – ITU-T is trying to update it issuing a revision)
– II-NNI [ITU-T Q.3630] | +| Izi | RTP/RTCP | [b-IETF RFC 3550] | + +## 12.2 Protocol implementation statement (PICS) + +The protocol implementation statement depicted in Table 12-2 describes the scope between network operator A and network operator B. The table shall be filled out with a yes/no. + +**Table 12-2 – Protocol implementation statement** + +| Selection expression | Support | Support | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------| +| | Network A | Network B | +| Network capabilities | | | +| SE 1: The originating network (Network A) sends the P-Charging-Vector header? | | | +| SE 2: The originating network (Network A) sends a subset of parameters in the P-Charging-Vector header? | | | +| SE 3: The P-Early-Media header is supported? | | | +| SE 4: Overlap procedure using multiple INVITE method is supported? | | | +| SE 5: Overlap sending using in-dialog method is supported? | | | +| SE 6: Network A supports the PSTN XML schema? | | | +| SE 7: The resource reservation procedure is supported? | | | +| SE 8: Does the network perform the "Fall back" procedure (PSTN or MGCF)? | | | +| SE 9: The network is untrusted? | | | +| SE 10: The originating network does not have a number portability data base, the number portability look up is done in the interconnected network? | | | +| SE 11: The network supports the REFER method? | | | +| SE 12: The network supports the 3 party call control procedure (REFER interworking)? | | | +| SE 13: Number portability is supported? | | | +| SE 14: Carrier selection is performed? | | | +| SE 15: The network is a long distance carrier? | | | +| SE 16: SIP support of charging is supported? | | | +| SE 17: The interworking ISUP – SIP I is performed in the network? | | | +| Supplementary services | | | +| SE 18: The network supports the originating identification presentation (OIP)? | | | +| SE 19: The network supports the "Special arrangement" procedure for the originating user? | | | +| SE 20: The network supports the originating identification restriction (OIR)? | | | +| SE 21: The network supports the terminating identification presentation (TIP)? | | | +| SE 22: The network supports the "Special arrangement" procedure for the terminating user? | | | +| SE 23: The network supports the terminating identification restriction (TIR)? | | | +| SE 24: The network supports the session HOLD procedure? | | | +| SE 25: The network supports communication forwarding unconditional (CFU)? | | | + +**Table 12-2 – Protocol implementation statement** + +| Selection expression | Support | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------| +| | Network A | Network B | +| SE 26: The network supports communication forwarding busy (CFB)? | | | +| SE 27: The network supports communication forwarding no reply (CFNR)? | | | +| SE 28: The network supports communication forwarding not logged in (CFNL)? | | | +| SE 29: The network supports communication deflection? | | | +| SE 30: The network supports the CDIV notification procedure? | | | +| SE 31: The network supports conference (CONF)? | | | +| SE 32: The network supports the communication barring procedure (CB) – (black list for incoming calls)? | | | +| SE 33: The network supports the anonymous communication rejection (ACR)? | | | +| SE 34: The network supports the closed user group (CUG)? | | | +| SE 35: The network supports the communication waiting (CW) service? | | | +| SE 36: The network supports the T AS-CW timer? | | | +| SE 37: The network supports explicit communication transfer (ECT)? | | | +| SE 38: The network supports malicious communication identification (MCID)? | | | +| SE 39: The network supports message waiting indication (MWI)? | | | +| SE 40: The network supports completion of communications to busy subscriber (CCBS)? | | | +| SE 41: The network supports completion of communications by no reply (CCNR)? | | | +| Terminal capabilities | | | +| SE 42: Void | | | +| SE 43: The end device supports fax transmission via ITU-T G.711 codec? | | | +| SE 44: The end device supports fax transmission via ITU-T V.152 codec? | | | +| SE 45: The end device supports fax transmission via m-line ITU-T T.38 codec? | | | +| SE 46: A SIP end device is used supporting an ISDN user equipment and the PSTN XML schema is used? | | | +| SE 47: End device is located in the PSTN or PLMN? | | | +| SE 48: The terminating UE supports the from-change tag procedure and sends a second user identity in an UPDATE request after the dialogue is confirmed? | | | +| SE 49: The end device performs ECT using the 'Blind/assured transfer'? | | | +| SE 50: The end device performs ECT using the 'Consultative transfer'? | | | +| SE 51: The end device supports the Resource reservation procedure? | | | + +**Table 12-2 – Protocol implementation statement** + +| Selection expression | Support | Support | +|--------------------------------------------------------------------------------------------------------------|-----------|-----------| +| | Network A | Network B | +| PSTN/PLMN supplementary services | | | +| SE 52: CLIP/CLIR is supported in the PSTN/PLMN part of the network? | | | +| SE 53: COLP/COLR is supported in the PSTN/PLMN part of the network? | | | +| SE 54: HOLD is supported in the PSTN/PLMN part of the network? | | | +| SE 55: CDIV is supported in the PSTN/PLMN part of the network? | | | +| SE 56: CONF/3PTY is supported in the PSTN/PLMN part of the network? | | | +| SE 57: ACR is supported in the PSTN/PLMN part of the network? | | | +| SE 58: CUG is supported in the PSTN/PLMN part of the network? | | | +| SE 59: CW is supported in the PSTN/PLMN part of the network? | | | +| SE 60: ECT is supported in the PSTN/PLMN part of the network? | | | +| SE 61: MCID is supported in the PSTN/PLMN part of the network? | | | +| SE 61A: Call completion is supported in the PSTN/PLMN part of the network? | | | +| SE 62: SUB is supported in the PSTN/PLMN part of the network? | | | +| SE 63: UUS is supported in the PSTN/PLMN part of the network? | | | +| SE 64: TP is supported in the PSTN/PLMN part of the network? | | | +| DTMF transmission | | | +| SE 65: The network supports DTMF transmission in the RTP stream? | | | +| SE 65: The network supports DTMF transmission indicating in the SDP offer in the RTP stream? | | | +| SE 67: The network supports DTMF transmission by the SIP INFO/NOTIFY method for DTMF tone generation? | | | + +# Appendix I + +## The current standards, guidelines and other documents related to VoLTE interconnection + +(This appendix does not form an integral part of this Recommendation.) + +Currently, the interconnection issue of VoLTE-based networks is an issue of interconnection/interworking of IMS platforms used for service sessions control. This topic is under study in different standardization organizations and alliances of operators. Among others there are the following key organizations involved to this activity: 3GPP, ETSI, ITU and GSMA. + +For the time being there are some documents and standards which might be considered for understanding the current state of this issue. + +## I.1 GSMA + +Nowadays GSMA as an alliance of mobile operators, which aims to provide recommendations on how to build in IMS interconnection, and is developing some guidelines and temporary documents. + +One such document is [b-GSMA PRD IR.92] which defines a profile that identifies a minimum mandatory set of features which are defined in 3GPP specifications that a wireless device (the user equipment (UE)) and network are required to implement in order to guarantee an interoperable, high quality IMS-based telephony service and IMS-based and SGs-based short message service (SMS) over long-term evolution (LTE) radio access. + +NOTE 1 – [b-GSMA PRD IR.92] defines a minimum set of basic call and supplementary services. It refers to relevant 3GPP standards and sometimes provides additional text selecting a given option in the 3GPP documents. + +[b-GSMA PRD IR.65] gives common guidelines for IMS (IP multimedia subsystem as specified by 3GPP) inter-operator connections in order to prevent non-interoperable and/or inefficient IMS services and networks. Areas covered are IMS specific issues in roaming and interworking, addressing of users and network elements, routing of traffic, inter-operator related security issues, IP version usage and requirements for inter-PLMN backbone caused by IMS, and the document concentrates on the network level issues. + +NOTE 2 – The common role of this document is to provide guideline for operators on how to establish inter-service provider connections using IMS platforms. It focuses on the requirements for the inter-service provider IP backbone network in terms of IMS interconnection. Also, it is mentioned that higher level issues like service interconnection, network (PSTN) as well as layer 3 (IP) connections between IMS network elements and terminals/applications are not within the scope of this document. + +[b-GSMA PRD IR.88] aims to provide a standardized view on how long-term evolution (LTE) and evolved packet core (EPC) networks can interwork in order to provide "Next Generation Mobile Network" capabilities when users roam onto a network different from their HPMN. The document describes the interface S8 between the HPMN and VPMN. It is mentioned that the PMIP protocol will not be maintained for the S8 roaming interface, only the GTP protocol is used for this interface. + +NOTE 3 – In general this document focuses on establishing scenarios for LTE and EPC roaming over 3GPP access. Roaming from non-3GPP access is not supported in this version of the document. + +Also, GSMA started working on developing a dedicated IP exchange network (IPX) with its main objective to create a basic IP-based core network for establishing interconnection among IMS-based networks used for providing VoLTE/ViLTE services. + +In this regard, GSMA is developing guidelines on the implementation of IPX and a relevant numbering system (ENUM) used for providing such VoLTE/ViLTE services. [b-GSMA PRD IR.67] describes a structure and delegation model of Carrier ENUM on the GRX/IPX network. + +NOTE 4 – There are no agreements among operators on how to implement the ENUM infrastructure for VoLTE/ViLTE-based networks. + +Another GSMA guideline, [b-GSMA PRD IR.34] focuses on the requirements for an IPX network which can be used for IMS interworking, according to [b-GSMA PRD IR.65] mentioned above. + +NOTE 5 – There are no requirements for signalling protocols and interfaces used for roaming scenarios. + +## **I.2 ITU** + +ITU-T has started working on SIP-IMS standardization due to the fact that IMS is also widely used on fixed networks. It was considered that the direct "IP-IP" interconnection of fixed network operators using the IP multimedia subsystem (IMS) through Inter-IMS network to network interface (NNI) is a complex issue due to differences in IMS implementations. + +Addressing this challenge, fixed network operators have initiated a session initiation protocol – IMS (SIP-IMS) standardization plan in ITU-T Study Group 11 (Protocols and test specifications). The plan includes a set of ITU-T Recommendations and related test specifications to provide a unified international reference for the implementation of SIP-IMS on fixed networks. + +More details about this activity is available on the relevant ITU [web page](#). + +NOTE – These services may also be used on VoLTE/ViLTE-based networks. + +# Bibliography + +- [b-GSMA PRD IR.34] GSMA PRD IR.34, *Guidelines for IPX Provider networks.* +- [b-GSMA PRD IR.65] GSMA PRD IR.65, *IMS Roaming and Interworking Guidelines.* +- [b-GSMA PRD IR.67] GSMA PRD IR.67, *DNS and ENUM guidelines for service providers and GRX and IPX providers.* +- [b-GSMA PRD IR.88] GSMA PRD IR.88, *LTE and EPC Roaming Guidelines.* +- [b-GSMA PRD IR.92] GSMA PRD IR.92, *IMS Profile for Voice and SMS.* +- [b-GSMA PRD IR.94] GSMA PRD IR.94, *IMS Profile for Conversational Video Service.* +- [b-GSMA PRD NG.105] GSMA PRD NG.105, *ENUM Guidelines for Service Providers and IPX Providers.* +- [b-RFC 3550] RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications.* +- [b-RFC 3761] RFC 3761 (2004), *The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM).* +- [b-ETSI TS 123 002] ETSI TS 123 002 V12.7.0 (07/2015), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunication System (UMTS); LTE; Network architecture (3GPP TS 23.0.002 version 12.7.0 Release 12).* +- [b-ETSI TS 123.228] ETSI TS 123.228 V10.9.0 (07/2015), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 10.9.0 Release 10).* +- [b-ETSI TS 129.235] ETSI TS 129 235 V10.3.0 (2013-09), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between SIP-I based circuit-switched core network and other networks (3GPP TS 29.235 version 10.3.0 Release 10).* + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3648-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.3648-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/Q/T-REC-Q.3648-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/Q/T-REC-Q.3648-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.3648-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c748ac88edd588a7056eb84dc2d09b6097be95cf --- /dev/null +++ b/marked/Q/T-REC-Q.3648-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b8d9145afab158a6bd16ebfa7296791ddb36b67c7850d4ab7a12e4a7e957838 +size 69233 diff --git a/marked/Q/T-REC-Q.3648-202406-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Q/T-REC-Q.3648-202406-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eb2573b31e84032128738b2cdd01861a0f1136d --- /dev/null +++ b/marked/Q/T-REC-Q.3648-202406-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c48e8fe549aaaebab0e9a563a4138ec22ed53063989acc7001b9f9b36996bb14 +size 47793 diff --git a/marked/Q/T-REC-Q.3712-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3712-201608-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4ee2decd80feebc89e184fda689fb5750c061bd5 --- /dev/null +++ b/marked/Q/T-REC-Q.3712-201608-I_PDF-E/raw.md @@ -0,0 +1,421 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3712** + +(08/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for SDN – Resource control protocols + +--- + +**Scenarios and signalling requirements of +unified intelligent programmable interface for +IPv6** + +Recommendation ITU-T Q.3712 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| Resource control protocols | Q.3710-Q.3739 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.3712 + +# Scenarios and signalling requirements of unified intelligent programmable interface for IPv6 + +## Summary + +Recommendation ITU-T Q.3712 describes the scenarios and signalling requirements of unified intelligent programmable interface for IPv6 service deployment. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3712 | 2016-08-29 | 11 | 11.1002/1000/12990 | + +## Keywords + +IPv6, SDN, transition. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 The deployment scenario and use cases ..... | 2 | +| 6.1 Evolve from one IPv6 transition scenario to another ..... | 2 | +| 6.2 Multiple transition mechanisms co-exist..... | 2 | +| 7 The signalling architecture ..... | 4 | +| 8 Signalling requirements ..... | 4 | +| 8.1 Component functions..... | 4 | +| 8.2 Interface requirements ..... | 4 | +| 9 The signalling protocol procedures ..... | 6 | +| 9.1 Information model ..... | 7 | +| 9.2 Operations..... | 7 | +| Appendix I – Protocol profiles for this Recommendation ..... | 8 | +| Bibliography..... | 9 | + + + +## Recommendation ITU-T Q.3712 + +## Scenarios and signalling requirements of unified intelligent programmable interface for IPv6 + +# 1 Scope + +This Recommendation describes the scenarios and signalling requirements of unified intelligent programmable interface for IPv6 service deployment. The example signalling protocol procedures at this interface will also be described in this Recommendation to support protocol unaware flow forwarding in the data plane. The IPv6 technologies supported in this Recommendation will include, but not be limited to, the following: dual-stack lite (DS-Lite), IPv6 only, IPv6 rapid deployment (6rd), IPv4 residual deployment (4rd), mapping of address and port - encapsulation mode (MAP-E), mapping of address and port - translation mode (MAP-T), lightweight 4over6 (lw4over6) and 464XLAT. + +# 2 References + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 software-defined networking** [b-ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|--------------------------------| +| ALG | Application Level Gateway | +| App | Application | +| DS-Lite | Dual-Stack Lite | +| lw4over6 | Lightweight 4over6 | +| NAT64 | Network Address Translation 64 | +| NETCONF | Network configuration protocol | +| RG | Residential Gateway | +| SDN | Software-Defined Networking | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| 4rd | IPv4 Residual Deployment | +| 6rd | IPv4 Rapid Deployment | + +# 5 Conventions + +None. + +# 6 The deployment scenario and use cases + +## 6.1 Evolve from one IPv6 transition scenario to another + +During the IPv6 transition period, the network has three types: IPv4-only, dual-stack and IPv6-only. The networks should support both IPv4 services and IPv6 services at each stage. There are multiple IPv6 transition technologies for different network scenarios (e.g., IPv4 network for IPv4/IPv6 user access, IPv6 network for IPv4/IPv6 user access, IPv4 servers for IPv6 visitors). Different network scenarios will co-exist during IPv6 transition which means the IPv6 transition device should support multiple IPv6 transition technologies. The following are six possible scenarios of IPv6 transition: + +- 1) IPv6 host visits IPv6 servers via IPv4 access network; +- 2) IPv4 host visits IPv4 servers via IPv4 NAT dual-stack network; +- 3) IPv6 host visit IPv6 servers via IPv6 network; +- 4) IPv4 host visits IPv4 servers via IPv6 access network; +- 5) IPv6 host visits IPv6 servers via IPv4 access network; +- 6) IPv4 host and IPv6 host interaction. + +It is not necessary that every operator goes through each scenario one by one. For example, some operators may start from scenario 1), and some may start directly from scenario 2) or scenario 4). However, since the final stage (target) is an IPv6-only access network, one still needs to go through multiple scenarios from a long-term perspective. + +In such a case, the operator should either upgrade existing devices to support new features, or replace them with new ones. In particular, when the operator's network consists of devices from different vendors, it is hard to guarantee that all legacy devices can be upgraded at the same time. This is costly and complicated. + +## 6.2 Multiple transition mechanisms co-exist + +Currently, there are multiple transition mechanisms in the industry, e.g., DS-Lite, lw4over6, mapping of address and port (MAP)/4rd, network address translation 64 (NAT64). In the transition from one scenario to another, different mechanisms may have different impacts on user experience. For example, DS-Lite would have some impact due to address sharing as compared with 6rd mechanisms, and NAT64 would have an additional impact due to application level gateway (ALG) issues. Operators need to offer a fallback mechanism to guarantee the same level of user experience when there are complaints from subscribers. Therefore, it is required to support multiple transition mechanisms in the same area (even in the same device). + +Another use case is that multiple scenarios may exist in the same stage. For example, if both IPv6-only devices and IPv4-only hosts are in the same area with limited public IPv4 address, then NAT64 and NAT44 (or DS-Lite) are both required to achieve IPv4 service connectivity. + +![Figure 6-1: Scenario and use case of this Recommendation. The diagram illustrates a network architecture with three layers: APP layer, Control layer, and Data plane. The APP layer contains an IPv6 application. The Control layer contains multiple SDN controllers. The Data plane shows a network path from a CPE (Customer Premises Equipment) through an Access node, a Metro cloud, an Edge cloud (containing BNG, BR, and PE routers), and a CORE cloud (containing PE routers) to the Internet. The path is labeled with network segments: LAST MILE, ACCESS, METRO, Edge, CORE, and Internet. The Internet side shows both IPv4 and IPv6 connections. The diagram is labeled Q.3712(16)_F6-1.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram shows a three-layer network architecture. At the top is the **APP layer** containing an **IPv6** application. Below it is the **Control layer** with multiple **SDN controllers**. The bottom is the **Data plane**, which consists of a **CPE** connected to an **Access node** (labeled **SDN-enabled**). This is followed by a **Metro** cloud, an **Edge** cloud containing **BNG**, **BR**, and **PE** routers (all labeled **SDN-enabled**), and a **CORE** cloud with **PE** routers. The path ends at the **Internet**, which supports both **IPv4** and **IPv6**. The segments are labeled at the bottom: **LAST MILE**, **ACCESS**, **METRO**, **Edge**, **CORE**, and **Internet**. The diagram is identified by the code **Q.3712(16)\_F6-1**. + +Figure 6-1: Scenario and use case of this Recommendation. The diagram illustrates a network architecture with three layers: APP layer, Control layer, and Data plane. The APP layer contains an IPv6 application. The Control layer contains multiple SDN controllers. The Data plane shows a network path from a CPE (Customer Premises Equipment) through an Access node, a Metro cloud, an Edge cloud (containing BNG, BR, and PE routers), and a CORE cloud (containing PE routers) to the Internet. The path is labeled with network segments: LAST MILE, ACCESS, METRO, Edge, CORE, and Internet. The Internet side shows both IPv4 and IPv6 connections. The diagram is labeled Q.3712(16)\_F6-1. + +**Figure 6-1 – Scenario and use case of this Recommendation** + +The unified intelligent IPv6 deployment scenario offers end-to-end service deployment and management. The residential gateway (RG), the IP edge and the service edge are flow-forwarding enabled. The hardware can be unified for different IPv6 transition technologies via flow-forwarding. IPv6 transition technologies can be plugged into the controllers. The flow-forwarding enabled devices do not need to change during the various stages of IPv6 transition. + +The northbound interface is essential to support the eco-system of software-defined networking (SDN) by allowing various SDN-related applications to be plugged in various vendor controllers. The goal is to make the controller controlled infrastructure to be an open platform for more innovations by allowing applications to be developed with the best network support. + +Several OpenFlow switches are deployed and located at the edge of network, as shown in Figure 6-1. The OpenFlow protocol may be extended mainly to support an IP tunnelling approach for transition purposes. The OpenFlow switches process the incoming packets based on the flow tables delivered by the SDN controller upon the request of an IPv6-transition application (App). + +The controller in the control layer provides an interface to the IPv6 transition App, enabling it to modify traffic processing using OpenFlow. Specifically, the controller provides an OpenFlow driver that enables the IPv6 transition App to instruct all SDN-enabled device how to treat traffic, thus making it possible to flexibly choose the particular transition mechanism to be applied, and to select the parameters governing it. The OpenFlow driver includes OpenFlow protocol specific tasks: listens for OpenFlow connections, creates the channel, keeps alive, proxy between the OpenFlow wire format and the solution internal information representation (e.g., rules, events). It is a basic function of the SDN controller. + +The process shown for this case is generic. A flow can be identified by part of the layer 2 (L2) to layer 4 (L4) packet header information. For example, all packets to a particular subscriber can be treated as belonging to the same flow in an SDN-enabled network. + +SDN provides a programmable platform for service deployment which can reduce new issues arising in the IPv6 transition. + +# 7 The signalling architecture + +![Diagram of the signalling architecture showing three layers: App layer, Control layer, and Data plane. The App layer is connected to the Control layer via the Sn interface. The Control layer contains an IPv6 application/transition support function. The Control layer is connected to the Data plane via the Sn interface.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +``` +graph TD; App[App layer] <-->|Sn| Control[Control layer]; subgraph Control; IPv6[IPv6 application/transition support function]; end; Control <-->|Sn| Data[Data plane]; +``` + +Q.3712(16)\_F7-1 + +Diagram of the signalling architecture showing three layers: App layer, Control layer, and Data plane. The App layer is connected to the Control layer via the Sn interface. The Control layer contains an IPv6 application/transition support function. The Control layer is connected to the Data plane via the Sn interface. + +**Figure 7-1 – Signalling interface** + +IPv6 transition technologies are presented as software Apps and are loaded into the control layer which is responsible for IPv6 application/transition support function via plug-in method. An IPv6 application/transition support function interface (Sn), which may use network configuration protocol (NETCONF)/YANG, describes IPv6 application/transition support function needed, which is independent of IPv6 application/transition technologies. The App layer generates the operation request based on the IPv6 application/transition support function data model configured, and sends the request to the IPv6 application/transition support function in the control layer. The IPv6 application/transition support function enables the Apps to manipulate the traffic via the Sn interface. + +# 8 Signalling requirements + +### 8.1 Component functions + +#### 8.1.1 App layer + +The application modules in the App layer provide the abstracted application program interfaces (APIs) and/or user functions. It receives the packet about the IPv6 transition technologies APP of new IPv6 flows from the control layer after the control layer receives the events from the network devices in the data plane. Then it sends appropriate instructions to the SDN-enabled device via the control layer and the Sn interface. + +#### 8.1.2 Control layer + +The control layer provides a northbound interface (Sn) that enables the IPv6 transition technologies App to modify the traffic using OpenFlow. It receives the events from the network devices and sends it to the App layer if necessary. After receiving the instructions from the App layer, the control layer translates the commands of the IPv6 transition technologies APP to a command that can be executed by the SDN-enabled device. + +### 8.2 Interface requirements + +The control layer provides a northbound interface (Sn) that enables the IPv6-transition App to modify traffic at the data plane using OpenFlow. Specifically, the control layer provides an OpenFlow driver that enables the IPv6-transition App to decide how the SDN-enabled packet-forwarding devices treat traffic using the Sn interface. This interface is used to provide an IPv6 application/transition support function interface to any IPv6-transition application. It mainly provides the following functions: + +- Registration and removal function for applications; +- IPv6 application/transition support function data model for packets and flow tables interaction between controller and applications; + +- Adapting packet-in events into neutral events in the interface; +- Supporting the installation function for applications in the interface. The control layer enables the application to program the data plane. The App layer determines the technology to be used and sets the parameters for it; +- The Sn interface should distribute the up-called events to the appropriate App functions based on the registered features of the App functions; +- Providing the management functions for the App functions to configure and manage the installed modules in the controller. + +The control layer provides a mechanism for new services/applications creation and existing services/applications removal via the Sn interface. A specified transmission control protocol (TCP) port number is provided for application registration, removal and coordination. When a new application is needed in the unified IPv6 system, this new application will initiate a registration request to the control layer using the specified TCP port number. Then the application and the control layer will coordinate an App ID and a dedicated channel for this App. Then the new App will register its features (e.g., the appropriate packet type(s) handled by the App) and/or install some function(s) to the control layer via the dedicated channel of the App. Removal function is also achieved via the specified TCP port number. + +#### 8.2.1 Flow description + +In this Recommendation, two parts of the flow table for IPv6 transition technology will be defined: Match fields and Actions. + +##### Match Fields + +##### Actions + +The procedure to create the flow table is separated into two steps: + +1. The Match field is defined as below: + +| | | +|---------------------|--| +| Field Offset | | +| Field length | | + +2. The possible Actions of the Protocol-Unaware flow table are defined as: Action Type, e.g., set-field, add-field and del-field. + +Taking the set-field and add-field as examples: + +| Action Type | Set-field | +|--------------------|------------------| +| Set-field offset | | +| Set-field length | | + +| Action Type | Add-field | +|------------------|-----------| +| Add-field offset | | +| Add-field length | | + +#### 8.2.2 IPv6 transition parameters in the flow table + +The Sn interface enables the IPv6/IPv6 transition technology applications to manipulate traffic. The parameters appearing in the flow table may be transmitted at this interface, which contains the following information: + +- tunnel\_sip\_v6: The source ipv6 address of tunnel (if any); +- tunnel\_dip\_v6: The destination ipv6 address of tunnel (if any); +- tunnel\_sip\_v4: The source ipv4 address of tunnel (if any); +- tunnel\_dip\_v4: The destination ipv4 address of tunnel (if any); +- sip\_v6: The source ipv6 address of a packet or inner source ipv6 address when packet type is IP-in-IP tunnel; +- dip\_v6: The destination ipv6 address of a packet or inner destination ipv6 address when packet type is IP-in-IP tunnel; +- sip\_v4: The source ipv4 address of a packet or inner source ipv4 address when packet type is IP-in-IP tunnel; +- dip\_v4: The destination ipv4 address of a packet or inner destination ipv4 address when packet type is IP-in-IP tunnel; +- sip\_v6\_port: Source IPv6 TCP/user datagram protocol (UDP) port number of the source ipv6 packet (or inner source ipv6 packet when packet type is IP-in-IP tunnel); +- dip\_v6\_port: Destination IPv6 TCP/UDP port number of the destination ipv6 packet (or inner destination ipv6 packet when packet type is IP-in-IP tunnel); +- src-port: source TCP/UDP port number of a packet; +- dst-port: Destination TCP/UDP port number of a packet; +- set\_ip/port: Modify the IP or/and port number in the header of the packet. + +# 9 The signalling protocol procedures + +The flow in this use case is generic. A flow can be identified by part of the L2-to-L4 packet header information (e.g., all packets to a subscriber can be considered to belong to the same flow in the SDN-enabled device, which will greatly reduce the number of flows). The signalling procedures, as illustrated in Figure 9-1, are as follows: + +![Sequence diagram showing signalling procedures between App layer, Control layer, and SDN-enabled device. The sequence is: 1. Receive first-packet (external to SDN-enabled device), 2. First-packet (SDN-enabled device to Control layer), 3. First-packet via Sn interface (e.g., Netconf) (Control layer to App layer), 4. Configuration parameters of the flow (e.g., Netconf) (App layer to Control layer), 5. Configuration parameters, routing parameters and action of the flow (Control layer to SDN-enabled device).](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +sequenceDiagram + participant App layer + participant Control layer + participant SDN-enabled device + Note right of SDN-enabled device: 1. Receive first-packet + SDN-enabled device->>Control layer: 2. First-packet + Control layer->>App layer: 3. First-packet via Sn interface (e.g., Netconf) + App layer->>Control layer: 4. Configuration parameters of the flow (e.g., Netconf) + Control layer->>SDN-enabled device: 5. Configuration parameters, routing parameters and action of the flow + +``` + +Sequence diagram showing signalling procedures between App layer, Control layer, and SDN-enabled device. The sequence is: 1. Receive first-packet (external to SDN-enabled device), 2. First-packet (SDN-enabled device to Control layer), 3. First-packet via Sn interface (e.g., Netconf) (Control layer to App layer), 4. Configuration parameters of the flow (e.g., Netconf) (App layer to Control layer), 5. Configuration parameters, routing parameters and action of the flow (Control layer to SDN-enabled device). + +Q.3712(16)\_F9-1 + +**Figure 9-1 – Signalling procedures of this Recommendation** + +1. Receiving a first-packet of a flow at the SDN-enabled device; +2. The first-packet is sent to the control layer from the SDN-enabled device, and the open flow protocol may be used at this interface; +3. The first-packet is sent to the APP layer via the Sn interface, and NETCONF may be used; +4. The configuration parameters (e.g., flow table) of the flow are sent out from the App layer to the control layer via the Sn interface. The parameters transmitted are shown in clause 8.2.2; +5. The configuration parameters, routing parameters and corresponding actions of the flow are sent out from the control layer to SDN-enabled device. The SDN-enabled device will add the new flow to the flow table. + +The subsequent packets of the flow received by the SDN-enabled device will then be processed based on the flow table, causing the SDN-enabled device to forward tunnelled IPv6 packets to their proper destination. Some method can be achieved to improve the SDN efficiency. Permanent (rather than per-flow) or even pre-configured flows could be achieved as well. + +## 9.1 Information model + +Information model matches the OpenFlow protocol specification and is slightly extended to support IP-in-IP tunnels. It can accommodate multiple switches (using the datapath id to identify switches or using the IP address of the datapath). + +The data structure is specified as + +- tunnel\_sip\_v6: The src-ipv6 address of tunnel (if any); +- tunnel\_dip\_v6: The dst-ipv6 address of tunnel (if any); +- tunnel\_sip\_v4: The src-ipv4 address of tunnel (if any); +- tunnel\_dip\_v4: The dst-ipv4 address of tunnel (if any); +- sip\_v6: The src-ipv6 address of a packet or inner src-ipv6 address when packet type is IP-in-IP tunnel; +- dip\_v6: The dst-ipv6 address of a packet or inner dst-ipv6 address when packet type is IP-in-IP tunnel; +- sip\_v4: The src-ipv4 address of a packet or inner src-ipv4 address when packet type is IP-in-IP tunnel; +- dip\_v4: The dst-ipv4 address of a packet or inner dst-ipv4 address when packet type is IP-in-IP tunnel; +- sip\_v6\_port: Source IPv6 TCP/UDP port number of the src-ipv6 packet (or inner src-ipv6 packet when packet type is IP-in-IP tunnel); + +- dip\_v6\_port: Destination IPv6 TCP/UDP port number of the dst-ipv6 packet (or inner dst-ipv6 packet when packet type is IP-in-IP tunnel); +- src-port: Source TCP/UDP port number of a packet; +- dst-port: Destination TCP/UDP port number of a packet. + +## 9.2 Operations + +The supported operations match the OpenFlow operations (packet out, flow mod, and all the others) are extended with IP-in-IP support, as follows: + +- push\_ipv4\_header: Encapsulate the packet into an IP-in-IP tunnel, tunnel type is IPv4; +- pop\_ipv4\_header: De-capsulate the packet from IP-in-IP tunnel, tunnel type is IPv4; +- push\_ipv6\_header: Encapsulate the packet into an IP-in-IP tunnel, tunnel type is IPv6; +- pop\_ipv6\_header: De-capsulate the packet from IP-in-IP tunnel, tunnel type is IPv6. + +## Appendix I + +### Protocol profiles for this Recommendation + +(This appendix does not form an integral part of this Recommendation.) + +The NETCONF [b-IETF RFC 6241] is a candidate configuration protocol for the interface between the App layer and the control layer to facilitate the description of the IPv6 application/transition support function and the generation of the operation request (e.g., set, add and delete), further to enable the Apps to manipulate the traffic via the Sn interface. + +This Recommendation requires that the NETCONF "Capabilities Exchange" capability be supported. The following protocol operations should also be supported: + +- +- +- +- +- + +## Bibliography + +- [b-ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. +- [b-IETF RFC 6241] IETF RFC 6241 (2011), *Network Configuration Protocol (NETCONF)*. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c341026a89d694a222bd1766d161cbbf2215d132 --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b14a5ad8964ba16ba8c768d581c776ad0d602df9e8aef528bdc107d7c895ff8 +size 45243 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fc99361ef78c0bd807e99d1c26a58325bb024d4 --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af115d2aae3376415c26bd932fd52b864087862119c11e62865d0e2eff6fc31e +size 52043 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9099e1e6836f5a2e26b9f9604ec713a4f76fe47b --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ea93fb2fbe69149d10132040999a2c63385c0efbd2bce6107e5e1fc7459eadc +size 37020 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c9a83aacd8686e76922af63a16f520c02bff23c --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d451ac5ff0eca3a677e0c189de96ca7b54f9d06b5f3136da429285f499bd9b6c +size 38934 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e72a05fbecea9bff3affde55271db1f725f9918d --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8012da6280fb9e87b5d5e5bde741ae6116cc71af6f82bec1ebc54a2b6ec150c +size 25405 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cc462264e536be9b653ce58abe832b561ab8638 --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:102c5cee1c08bc02bf566c2b3cb806094515aad2c5a605ce3a832c0d281a8b6f +size 52691 diff --git a/marked/Q/T-REC-Q.3720-202009-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34c40b2f18278a137be4dcf1532a98f870ed9f63 --- /dev/null +++ b/marked/Q/T-REC-Q.3720-202009-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:070d1182ca80c7df126ef358b433375ec6fa6fc1d332381530ad199243051c2a +size 40159 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..413af9678d1a05c7b9b44ac717e1df134c430199 --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16fd7ca125adc784b869a2b99a7f9e985dd8e7195f2213acdfcd3e0a88bf7fe9 +size 7122 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe7005e9f8c4081b1d49b67275ff4e7dc6b10fd1 --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97b5baf6681c42d89887512e8d79c1f59acb74d9c1b1d6d0b17de48aa4a8e7af +size 78774 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4c4e1746fff202410ef2378d1e53217dce5df05 --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b944a9b4d9143543ad6f045ea83316c2e2548edf3f24d51e37c5fe1cac712d96 +size 32403 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d84632588cd376bb8d05e8aa5a170d1c21def03 --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb5b591a8fac07dc7bae53e121b5c0b0ed251c9f44406d17c25abda428b0d7ff +size 31134 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29919fa77745149c8c338120097c444ad2df069f --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78a0ee272808945111362ee86328f97ce4b0e24ac02a5ebeda7630a5ff91f8de +size 32398 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad8cd6ab9d6ab283202ddde00648d15134365d5b --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b263cb225bdb4850e7becf53519dbbedd9a4b1c2b8ebf33edb9ea82d195ea5bc +size 14749 diff --git a/marked/Q/T-REC-Q.3742-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ab664c5b33acd9ee4755e386e1fc58022e0b9244 --- /dev/null +++ b/marked/Q/T-REC-Q.3742-202406-I_PDF-E/raw.md @@ -0,0 +1,608 @@ + + +# Recommendation**ITU-T Q.3742 (06/2024)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for SDN – Network signalling and signalling requirements for services + +--- + +# **Signalling requirements and data models for SD-DCI service** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| Resource control protocols | Q.3710-Q.3739 | +| Network signalling and signalling requirements for services | Q.3740-Q.3779 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.3742 + +# Signalling requirements and data models for SD-DCI service + +## Summary + +As enterprises use more and more geographically distributed cloud services, the demand for interconnection among different data centres is increasing. Network operators develop software-defined data centre interconnection (SD-DCI) services to meet customized demands for interconnection among multiple data centres. Recommendation ITU-T Q.3742 specifies the signalling requirements and data models for SD-DCI service. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.3742 | 2024-06-29 | 11 | 11.1002/1000/15957 | + +## Keywords + +Data centre interconnection, software-defined network. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | General description for SD-DCI service..... | 2 | +| 7 | Functional architecture of SD-DCI service ..... | 3 | +| 7.1 | Functional components..... | 3 | +| 7.2 | Interfaces ..... | 5 | +| 8 | Data model for SD-DCI service deployment..... | 5 | +| 8.1 | Customer..... | 5 | +| 8.2 | Virtual private network..... | 5 | +| 8.3 | Node ..... | 5 | +| 9 | Signalling procedures for SD-DCI service deployment..... | 6 | +| 9.1 | Signalling procedure for SD-DCI service creation ..... | 6 | +| 9.2 | Signalling procedure for SD-DCI service deletion ..... | 7 | +| 9.3 | Signalling procedure for service alternation..... | 7 | +| 10 | Signalling requirements for SD-DCI service deployment..... | 8 | +| 10.1 | Overview ..... | 8 | +| 10.2 | Signalling requirement for service creation ..... | 8 | +| 10.3 | Signalling requirement for service deletion ..... | 9 | +| 10.4 | Signalling requirement for service alternation ..... | 10 | +| | Bibliography..... | 12 | + + + +# Recommendation ITU-T Q.3742 + +# Signalling requirements and data models for SD-DCI service + +## 1 Scope + +This Recommendation provides the signalling requirements for software-defined data centre interconnection (SD-DCI) service in one single network operator. The signalling is to support the dynamical setup and management of the multiple data centres' interconnections. This Recommendation focuses on the signalling requirements among the SD-DCI controller, orchestrator and application. + +The scope of this Recommendation includes: + +- a general description of SD-DCI service; +- the functional architecture for SD-DCI service; +- data models for SD-DCI service deployment; +- signalling procedures for SD-DCI service deployment; +- signalling requirements for SD-DCI service deployment. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 software-defined networking** [ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------------| +| API | Application Programming Interface | +| APP | Application | +| BGP | Border Gateway Protocol | + +| | | +|----------|--------------------------------------------------------| +| CE | Customer Edge | +| CLI | Command Line Interface | +| CSP | Cloud Service Provider | +| DC | Data Centre | +| DCI | Data Centre Interconnection | +| GUI | Graphical User Interface | +| ID | Identity Document | +| IP | Internet Protocol | +| MPLS | Multiprotocol Label Switching | +| NETCONF | Network Configuration protocol | +| P router | Provider router | +| PCE | Path Computation Element | +| PE | Provider Edge | +| QoS | Quality of Service | +| RESTconf | Representational State Transfer Configuration protocol | +| SCTP | Stream Control Transmission Protocol | +| SD-DCI | Software-Defined Data Centre Interconnection | +| SDN | Software-Defined Networking | +| SLA | Service Level Agreement | +| TCP | Transmission Control Protocol | +| TE | Traffic Engineering | +| TLS | Transport Layer Security | +| UDP | User Datagram Protocol | +| VLAN | Virtual Local Area Network | +| VPN | Virtual Private Network | +| VRF | Virtual Routing and Forwarding | +| XML | Extensible Markup Language | + +# 5 Conventions + +The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. + +In the body of this document and its appendices, the words shall, shall not, should, and may sometimes appear, in which case they are to be interpreted, respectively, as is required to, is prohibited from, is recommended, and can optionally. The appearance of such phrases or keywords in an appendix or in material explicitly marked as informative are to be interpreted as having no normative intent. + +# 6 General description for SD-DCI service + +The construction of data centres for various organizations and enterprises is becoming increasingly common. There is a need for multiple data centres to be interconnected, since a single data centre + +may not be always suitable for digital business needs. Some of the issues needing to be addressed are listed below: + +- extended response time for remote data centre interconnection network configuration; +- difficulty in meeting a large number of services with varying demands; +- inefficient utilization of network resources. + +SD-DCI service should satisfy the following key capabilities with software-defined networking (SDN) technologies: + +- automatic establishment and flexible configuration of services; +- smart traffic engineering and quality of service (QoS) differentiation; +- instant service alternation. + +# 7 Functional architecture of SD-DCI service + +## 7.1 Functional components + +As shown in Figure 7-1, the functional architecture for SD-DCI service includes the self-service application for customers, the service orchestrator, the SD-DCI controller and the routers, where the routers consist of customer edge (CE), provider edge (PE) and provider (P) routers. The CE routers in data centres are connected with the PE routers of the Internet Protocol (IP) network. The SD-DCI controller is required to control all the appropriate routers of the dedicated carrier network, which realizes the automatic establishment and flexible configuration of services, and provides the functions of smart traffic engineering and QoS differentiation. Based on the service parameters from the service orchestrator, the data centre (DC) controller is used to manage the configuration of the data centre network in order to achieve the interconnectivity and interoperability of the services. + +![Functional architecture diagram for SD-DCI service showing layers from APP down to CE routers, with a central SD-DCI controller and Service orchestrator.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates the functional architecture for SD-DCI service. At the top is an **APP** block. Below it, a red oval labeled **Sao** connects to the **Service orchestrator**. Below the Service orchestrator, another red oval labeled **Soc** connects to the **SD-DCI controller**. The Service orchestrator also connects to two **DC controller** blocks (one on the left, one on the right), each containing a **Service configuration management** sub-block. The SD-DCI controller connects to a central oval containing three routers: **PE router**, **P router**, and **PE router**. This central router oval is connected to five cloud blocks, each containing a **CE router**: **Public cloud A1** (top left), **Public cloud B** (bottom left), **Public cloud A2** (bottom center), **Private cloud A** (bottom right), and **Private cloud B** (top right). The text **Q.3742(24)** is in the bottom right corner. + +Functional architecture diagram for SD-DCI service showing layers from APP down to CE routers, with a central SD-DCI controller and Service orchestrator. + +**Figure 7-1 – The functional architecture for SD-DCI** + +#### (1) The application (APP) functional component + +The APP functional component provides the graphical user interface (GUI) for customers. Through the APP functional component, a user requests one new DC interconnection (DCI) service or modifies the existing DCI service, by inputting the service parameters based on their demands, which include, but are not limited to, the targeted DC, bandwidth, delay and QoS. After confirming and approving the customer's request, the APP functional component transmits the request information to the service orchestrator functional component. + +In addition, the APP functional component informs customers if the service configuration has been deployed successfully, and shows customers the established connections and topology of the deployed service. + +#### (2) The service orchestrator functional component + +The service orchestrator functional component analyzes the received service request information from customers and converts the analysis results into the service configuration based on the unified data model. + +The service orchestrator functional component sends the service configuration information to the SD-DCI controller functional component to realize the automatic service deployment in the IP network. The communication between the service orchestration functional component and the SDN controller functional component may be based on the standard RESTful interface. + +The service orchestration functional component can also coordinate with the DC controller, which can realize the automatic service deployment within the data centre to satisfy the service level agreement (SLA) requirements for customers. However, the interaction process is out of the scope of this Recommendation. + +#### (3) The SD-DCI controller functional component + +The SD-DCI controller functional component manages the relevant resources of the carrier network including, but not limited to, routers, topology and links. It treats the underlying carrier network as one virtualized network resource pool. The network resource can be allocated flexibly and virtually according to the service requirements of different customers and the network conditions. + +The SD-DCI controller functional component communicates with the service orchestrator functional component through its northbound application programming interface (API). It processes the service request and provides specific functions including, but not limited to, L3 virtual private network (VPN) for DCI, traffic engineering (TE) tunnel for traffic engineering or low latency based on DCI service requirement, and path computation element (PCE) server, and translates or adapts the service configuration into the detailed configuration. The SD-DCI controller communicates with the underlying network routers through the southbound API which realizes the issue of network control instructions and feedback of network status. + +When the SD-DCI controller functional component receives the service configuration from the orchestrator functional component, it will map the service configuration to the command-line-based configuration for the corresponding routers. After that, the command-line-based configuration will be sent, for instance, to the corresponding routers, based on Network Configuration protocol (NETCONF) or command line interface (CLI). + +#### (4) The routers' functional component + +The routers' functional component provides the data-forwarding function. The PE routers need to support SDN function, which means the PE routers can be controlled by the SD-DCI controller functional component. The P routers need to support the VPN tunnels between the PE routers. + +#### (5) The CE devices of data centres + +The CE devices of data centres are connected with the PE routers of the IP network. The connection can be based on IP access network, L2 transport network, or direct fibre connection. The DC + +controller can manage the CE devices of the data centres, and the SD-DCI controller functional component can configure the interfaces of the PE routers connected to the CE devices. + +## 7.2 Interfaces + +The interfaces among SD-DCI controller, orchestrator and application need to support information exchange and authentication. They need to support representational state transfer configuration (RESTconf) protocol, and the authentication is based on the token mode. + +#### 7.2.1 Sao interface + +This interface permits the interaction between the APP functional component and the service orchestrator functional components. The service orchestrator functional component receives the service creation/deletion/alternation request from the APP functional component and allocates the basic network resources for the service request including, but not limited to, the PE device loopback, the interface identity document (ID), and the virtual local area network (VLAN) ID. + +#### 7.2.2 Soc interface + +This interface permits the interaction between the service orchestrator functional component and the SD-DCI controller functional component. The SD-DCI controller functional component receives the service creation/deletion/alternation request from the service orchestrator functional component and maps the service configuration to the command-line-based configuration for the corresponding routers. + +# 8 Data model for SD-DCI service deployment + +## 8.1 Customer + +The data model description for a customer is specified in Table 8-1. + +**Table 8-1 – Data model of a customer** + +| Element | Description | +|----------------|-----------------------------------------| +| CustID | CustID uniquely specifies the customer. | +| EnterpriseName | The enterprise name | + +## 8.2 Virtual private network + +The data model description for a VPN is specified in Table 8-2. + +**Table 8-2 – Data model of a VPN** + +| Element | Description | +|-------------|---------------------------------------------------------------------------------------| +| VPNID | VPN ID uniquely specifies a multiprotocol label switching (MPLS) VPN of one customer. | +| VRFID | The customer's virtual routing and forwarding (VRF) ID | +| Topology | The structural relationship of the nodes in the VPN | +| QoSStrategy | The customer's QoS policy | + +## 8.3 Node + +The data model description for the node is specified in Table 8-3. + +**Table 8-3 – Data model of a node** + +| Element | Description | +|-------------|------------------------------------------------------------------------------------| +| NodeID | NodeID uniquely specifies a node of one MPLS VPN. | +| PELoopback | PE loopback uniquely specifies the PE router. | +| InterfaceID | The ID of the PE router port | +| VLANID | The identification of the customer's VLAN | +| RouteType | The type of the customer's network, e.g., border gateway protocol (BGP) and static | +| RD | The customer's route distinguisher | +| BRT | The customer's route target | +| Bandwidth | The maximum bandwidth of this node available to the customer | + +# 9 Signalling procedures for SD-DCI service deployment + +The deployment SD-DCI service consists of three procedures: + +- 1) service creation +- 2) service deletion +- 3) service alternation. + +## 9.1 Signalling procedure for SD-DCI service creation + +Figure 9-1 describes the creation procedure for SD-DCI service. The information exchange for service creation is based on push mode. + +![Sequence diagram showing the service creation procedure between APP, Service orchestrator, and SD-DCI controller. Step 1: APP sends Service creation message to Service orchestrator. Step 2: Service orchestrator sends Service creation message to SD-DCI controller. Step 3: SD-DCI controller sends Service creation response message to Service orchestrator. Step 4: Service orchestrator sends Service creation response message to APP. Q.3742(24) is noted at the bottom right.](853f59c89931a666c07903b31d098277_img.jpg) + +``` +sequenceDiagram + participant APP + participant SO as Service orchestrator + participant SD-DCI as SD-DCI controller + Note left of APP: Step 1 + APP->>SO: Service creation message + Note left of SO: Step 2 + SO->>SD-DCI: Service creation message + Note left of SD-DCI: Step 3 + SD-DCI->>SO: Service creation response message + Note left of SO: Step 4 + SO->>APP: Service creation response message +``` + +Q.3742(24) + +Sequence diagram showing the service creation procedure between APP, Service orchestrator, and SD-DCI controller. Step 1: APP sends Service creation message to Service orchestrator. Step 2: Service orchestrator sends Service creation message to SD-DCI controller. Step 3: SD-DCI controller sends Service creation response message to Service orchestrator. Step 4: Service orchestrator sends Service creation response message to APP. Q.3742(24) is noted at the bottom right. + +**Figure 9-1 – Service creation procedure** + +Step 1: The APP functional component transfers the service parameters filled in by customers into attribute values, and then sends them to the service orchestrator functional component by the service creation message through the Sao interface. + +Step 2: The service orchestrator functional component allocates network resources for the customer's service, then sends the service creation message through the Soc interface to the SD-DCI controller functional component to create the customer's service. + +Step 3: The SD-DCI controller functional component responds to the service orchestrator functional component with the result of the customer's service creation through the Soc interface. + +Step 4: The service orchestrator functional component responds to the APP functional component with the result of the customer's service creation through the Sao interface. + +## 9.2 Signalling procedure for SD-DCI service deletion + +Figure 9-2 describes the deletion procedure for the SD-DCI service. The information exchange for the service deletion request is based on push mode. + +![Sequence diagram for service deletion procedure](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +A sequence diagram illustrating the service deletion procedure. It features three vertical lifelines: APP, Service orchestrator, and SD-DCI controller. The interaction consists of four steps: Step 1 shows a 'Service deletion message' from APP to Service orchestrator; Step 2 shows a 'Service deletion message' from Service orchestrator to SD-DCI controller; Step 3 shows a 'Service deletion response message' from SD-DCI controller to Service orchestrator; and Step 4 shows a 'Service deletion response message' from Service orchestrator to APP. The diagram is labeled 'Q.3742(24)' at the bottom right. + +Sequence diagram for service deletion procedure + +Figure 9-2 – Service deletion procedure + +Step 1: The APP functional component sends the service deletion message to the service orchestrator functional component through the Sao interface. + +Step 2: The service orchestrator functional component sends the service deletion message to the SD-DCI controller functional component through the Soc interface. + +Step 3: The SD-DCI controller functional component responds through the Soc interface to the service orchestrator functional component with the result of the customer's service deletion, and the service orchestrator then releases the related network resources of the customer's network service. + +Step 4: The service orchestrator functional component responds through the Sao interface to the APP functional component with the result of the customer's service deletion, and the APP functional component then releases the service data of the customer's service. + +## 9.3 Signalling procedure for service alternation + +Figure 9-3 describes the alternation procedure for SD-DCI service. The information exchange for the service alternation request is based on push mode. + +![Sequence diagram for service alternation procedure](2e399449b7f62d40167a65ca88888917_img.jpg) + +A sequence diagram illustrating the service alternation procedure. It features three vertical lifelines: APP, Service orchestrator, and SD-DCI controller. The interaction consists of four steps: Step 1 shows a 'Service alternation message' from APP to Service orchestrator; Step 2 shows a 'Service alternation message' from Service orchestrator to SD-DCI controller; Step 3 shows a 'Service alternation response message' from SD-DCI controller to Service orchestrator; and Step 4 shows a 'Service alternation response message' from Service orchestrator to APP. The diagram is labeled 'Q.3742(24)' at the bottom right. + +Sequence diagram for service alternation procedure + +Figure 9-3 – Service alternation procedure + +Step 1: The APP functional component converts the alternation parameters into attribute values and sends the service alternation message to the service orchestrator functional component through the Sao interface. + +Sao interface. The parameters that can be alternated include, but are not limited to, bandwidth, QoS, and interconnection IP addresses. + +Step 2: The service orchestrator functional component allocates or records the related network resources of the alternation request before sending the attribute alternation message to the SD-DCI controller functional component. + +Step 3: The SD-DCI controller functional component responds through the Soc interface to the service orchestrator functional component with the result of the customer's service alternation, and the service orchestrator functional component then updates the usage of related network resources, such as the interface bandwidth. + +Step 4: The service orchestrator functional component responds through the Sao interface to the APP functional component with the result of the customer's service alternation, and the APP functional component then updates the service parameters including, but not limited to, the bandwidth, QoS ratio and interconnection IP addresses. + +# 10 Signalling requirements for SD-DCI service deployment + +## 10.1 Overview + +The message interactions are based on request and response mode. The request messages are used for service creation/deletion/alternation and to query the result, while the response message contains the handling results of the corresponding requests. + +NOTE – No transport protocol or message content format for the signalling messages is specified here. The signalling messages may be extensible markup language (XML)-based messages over (or carried by) transmission control protocol (TCP) [b-IETF RFC 793]; user datagram protocol (UDP) [b-IETF RFC 768]; stream control transmission protocol (SCTP) [b-IETF RFC 2960]; transport layer security (TLS) [b-IETF RFC 5246]; QUIC [b-IETF RFC 9000], etc. All of the messages consist of the message header and the message body. The message format is described in Figure 10-1. + +![Diagram of message composition showing a table with four columns: Message type, Message length, Transaction ID, and Message body. A bracket below the first three columns is labeled 'Message header'. The text 'Q.3742(24)' is to the right of the bracket.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +| | | | | +|--------------|----------------|----------------|--------------| +| Message type | Message length | Transaction ID | Message body | +|--------------|----------------|----------------|--------------| + +Message header Q.3742(24) + +Diagram of message composition showing a table with four columns: Message type, Message length, Transaction ID, and Message body. A bracket below the first three columns is labeled 'Message header'. The text 'Q.3742(24)' is to the right of the bracket. + +**Figure 10-1 – Message composition** + +The message header field contains the following information: + +- Message type: uniquely specifies the type of message, including service creation, service creation response; service deletion, service deletion response; service alternation and service alternation response +- Message length: specifies the length of the message body +- Message transaction ID: generated by the sender of the message + +If there is a response message for the request message, the transaction IDs of the request and response messages are the same. + +The message body field contains the message contents. + +## 10.2 Signalling requirement for service creation + +The service creation message is defined as a ServiceCreation message. + +The ServiceCreation message, indicated by the message type in the message header field, is sent by the APP functional component to the SD-DCI controller functional component through the service orchestrator functional component. + +Message format: + +``` +< ServiceCreation-Message > ::= < Message Header > + {CUST-ID} + {VPN-ID} + {Node-List} +``` + +Meanings and explanations: + +The detailed information is as follows: + +- (1) CUST-ID uniquely specifies the customer, which is specified based on the data model described in clause 8.1. +- (2) VPN-ID uniquely specifies the specific SD-DCI service that is related to the specific customer, which is specified based on the data model described in clause 8.2, and is allocated by the APP functional component. +- (3) Node-List uniquely specifies the node information of the VPN service of the customer, which is specified based on the data model described in clause 8.3. + +The service creation response message is defined as a ServiceCreation-R message. + +The ServiceCreation-R message, indicated by the message type in the message header field, is sent by the SD-DCI controller functional component to the APP functional component through the SD-DCI orchestrator functional component. + +Message format: + +``` +< ServiceCreation-R-Message > ::= < Message Header > + {Configuration-result} + {Node-List} +``` + +The detailed information is as follows: + +- (1) Configuration-result specifies the result of the network configuration distribution. If the network configuration distribution is successful, Configuration-result is TRUE; if not, Configuration-result is FALSE. +- (2) Node-List uniquely specifies the node information of the VPN service of the customer, which is specified based on the data model described in clause 8.3. + +## 10.3 Signalling requirement for service deletion + +The service deletion message is defined as a ServiceDeletion message. + +The ServiceDeletion message, indicated by the message type in the message header field, is sent by the APP to the SD-DCI controller through the service orchestrator. + +Message format: + +``` +< ServiceDeletion-Message > ::= < Message Header > + {CUST-ID} + {VPN-ID} + {Node-ID} +``` + +Meanings and explanations: + +The detailed information is as follows: + +- (1) CUST-ID uniquely specifies the customer, which is specified based on the data model described in clause 8.1. +- (2) VPN-ID uniquely specifies the specific SD-DCI service, which is related to the specific customer, which is specified based on the data model described in clause 8.2. +- (3) Node-ID uniquely specifies the node to be deleted, which is specified based on the data model described in clause 8.3. + +The network service deletion response message is defined as a ServiceDeletion-R message. + +The ServiceDeletion-R message, indicated by the message type in the message header field, is sent by the SD-DCI controller functional component to the APP functional component through the service orchestrator functional component. + +Message format: + +``` +< ServiceDeletion-R-Message > ::= < Message Header > + {Deletion-result} +``` + +The detailed information is as follows: + +- (1) Deletion-result specifies the result of the network deletion. If the network deletion is successful, Deletion-result is TRUE; if not, Deletion-result is FALSE. + +## 10.4 Signalling requirement for service alternation + +The service alternation message is defined as a ServiceAlternation message. + +The ServiceAlternation message, indicated by the message type in the message header field, is sent by the APP functional component to the SD-DCI controller functional component through the service orchestrator functional component. + +Message format: + +``` +< ServiceAlternation-Message > ::= < Message Header > + {CUST-ID} + {VPN-ID} + {Node-List} +``` + +Meanings and explanations: + +The detailed information is as follows: + +- (1) CUST-ID uniquely specifies the customer, which is specified based on the data model described in clause 8.1. +- (2) VPN-ID uniquely specifies the specific SD-DCI service which is related to the specific customer, which is specified based on the data model described in clause 8.2. +- (3) Node-List uniquely specifies the node information of the VPN service of the customer, which is specified based on the data model described in clause 8.3. + +The service alternation response message is defined as a ServiceAlternation-R message. + +The ServiceAlternation-R message, indicated by the message type in the message header field, is sent by the SD-DCI controller functional component to the APP functional component through the service orchestrator functional component. + +Message format: + +``` +< ServiceAlternation-R-Message > ::=< Message Header > + {Configuration-result} + {Node-List} +``` + +The detailed information is as follows: + +- (1) Configuration-result specifies the result of the service alternation configuration. If the service alternation configuration is successful, Configuration-result is TRUE; if not, Configuration-result is FALSE. +- (2) Node-List uniquely specifies the altered node information of the VPN service of the customer, which is specified based on the data model described in clause 8.3. + +## Bibliography + +- [b-IETF RFC 768] IETF RFC 768 (1980), *User Datagram Protocol*. + +- [b-IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol*. + +- [b-IETF RFC 2960] IETF RFC 2960 (2000), *Stream Control Transmission Protocol*. + +- [b-IETF RFC 5246] IETF RFC 5246 (2008), *The Transport Layer Security (TLS) Protocol Version 1.2*. + +- [b-IETF RFC 9000] IETF RFC 9000 (2021), *QUIC: A UDP-Based Multiplexed and Secure Transport*. + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/08e28b34a19ebd5402953188378292ec_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/08e28b34a19ebd5402953188378292ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dec9d1370e23df028ac0dc4e114a6b9f8c7fc512 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/08e28b34a19ebd5402953188378292ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:297ec1ec4305f1dfa9019288a8bab0a46aab31d81e1f9bb95935d836ce17f1c2 +size 38499 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4813249a4869908f22c9d74c99b52b556081f92 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0f74dc92ddc289eb03293df43ab40c147ce18cbc2e2ed76ae7f8a79367adf94 +size 54775 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbd79f7e7420f861067978b1ebd25cd77b64e752 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edfe6f39c954fcf8903672486b60f73ecb1d67b6f77da0f570c4275dc969a054 +size 28243 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f1d96ee827ad2bdcdab54b7de1cc38d54623027 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79354b3dda9fde478d4e0e26baaabfebe013670a2b3aa05abb326838e248138a +size 89306 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64ef6b3bacd92a3e8bac1b50622a2ec465b34c60 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ada3e24c35363a46aaf949b8e2b4e560b036886d3328cea55d1368ee0cc2f85e +size 85179 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aea62984fa7e39f4f76f096027ea780b4b070237 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86319f8390e25e0985ee78dcd0014de1957609a578023b502b20d6aef46484b8 +size 58476 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8348b54fc4e2fcc12681ff50f4af77630e8d332 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e11d2080eec3541138acfb1db5a8610e687c5a400a2105ff0b7ce62e0a2c081a +size 69510 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c3c5b39260239ac6135f435b50095b3c9fcaa0c --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24f4f1e639fb3b5e8a61efaea1783ac0d528baa4db52e79831811f322efab38a +size 68652 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39d45b524cfb7389cef0e6cef289abd25ac797cf --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd41f48193ddffef8523d40f782fb5cc5278733b609615e48e7e3e64830fd490 +size 69688 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd3ed4d67b52b8d8a3f2f610d60cc4e178553276 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1ea790bc71db22b2a81e02b80dd791bf49f13f810c00b008a972eae8d2490e4 +size 89590 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/654cedceef37338716baa54407d488c8_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/654cedceef37338716baa54407d488c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39e9b41aed5e65f01346d8fd3001d9ba73afec60 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/654cedceef37338716baa54407d488c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84bcbe9816b3594bc6bc36601ee541730338e6cfa4b6706247a7b6bc3c1eb27c +size 16245 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..290df232d4dcb218067e0d470448ed258fd5a209 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7af39561b9a4002dcc820f4e8be06e01d7bb50616189958e8c339cdbfe1cda2f +size 47891 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/83397befc16475b196b532d975898715_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/83397befc16475b196b532d975898715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..001fd4f5d65afe2fa29c748125e897816ddaae1b --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/83397befc16475b196b532d975898715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26d8d3f82b689f9c8aaf3ea7728f25b361002d127d1cc8550787c16c60c6ea41 +size 34552 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/8b0c76c2c4aa368163995731c966d7f2_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/8b0c76c2c4aa368163995731c966d7f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25b2bfe01a6ed57613d735cfd8b29d38ab209739 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/8b0c76c2c4aa368163995731c966d7f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f55d9d0820de740d593b11102b264bf38ef9aa7979aa8d64ab00a2285be93eef +size 25644 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b78c7624e0f224c6401292a0d3717d4147e83c6 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8be7afe97625ae53d7e006647019dea05fc3bf416b3775f1411aa3dbcf4aaa9d +size 52959 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/99b769aeac0b78472f4cb81be7836f3b_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/99b769aeac0b78472f4cb81be7836f3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c774cfa6c7cd47cea69bad1a252772bd59d7abd --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/99b769aeac0b78472f4cb81be7836f3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8bb2a872e3ef659733b5abe14de0e62b90cfd6ee6a562a9d9f1143b5a2dc483 +size 15870 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bcac069f296e4b4687343988072de8360b866cd --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac5e5990751bc07ef61f62527d8fcdd270ca418bb3e7ca5a89dedc682527168f +size 24363 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..201366d545ba88a7466eaf82c3e760317edc2be2 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6612594cc3c5b3f7b4ec4d351adf394ff06168b979f2613c90a3156ab49460f +size 146841 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f5df5b7316bd39c5e2541431df013009fe13c2 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70f347c7ab13a8447a5886ad69e647e5831cbb7808f298ea86ae78e57bbd88d4 +size 139297 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64f5de2a7ea74c5f6240d172d01db8de375d8ebf --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75ccec65851f64270b1e10a7934802b2a9a48655d3b93d88626b9ca9f0a00a53 +size 61270 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39c3d1c976185835c27086c00b5ce801272eee4f --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a10f53ac231b347946901cb393ac745c39e4da72e0a3dc148f936ed0f75b1629 +size 174834 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6aa49ec13f26c87eb92c81d6e03891da4d28b88 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d54719e94339302484fac712064562a16342194f5a3c802b0e3b527a6c689bb6 +size 131999 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f41cdbfc010d9e90c18bcb23838b04d158c1594 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4a9fa3343e3a4636121de1e69acf242b07b9c64b8be165a45b8331db143e389 +size 46258 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..484512616acba5e16795012a0610819260970f87 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2657602fcef6d2db7366b84c48eb3caae23c2bc2c306ef95c1020cfebb4a44b +size 128716 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e981a9a3f43c18178f93fccb24c78254a35bda3 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84f8440644a4e61518bf6303e1ae6aa064e968adbd76bd719dd2a4206d485e91 +size 144114 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b05f664dc467a49f25fab2fa1b9b24ddca97ce4 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faafc7ac40a7b93731f817c50f8b34691b0e73e5e4650f3d7f0923694bf735f4 +size 15768 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e29302c6c5a4225a9ec7075b8c31210e6fb44e0 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e232821c73b1611b8a40de9e15fc12888d3453c6b5d828e64dbea1ee872e6c9 +size 23445 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceec80c04850ceae48c02ca0163698fb5352900c --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18879a5eb7d0b9e5469a6191d131ce1a511a0fbf9b32e713d9c2ff81219efb08 +size 46243 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..736da2284c114af0b326eda1ce33e0c4c5a57795 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe3443129ba1263fe583dcc4da57d2282992776e784370eca9041f623de99c9 +size 53079 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43737ddd69cb7ec77f78074840cc3682fdf22603 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bec1916545f49cffa3448d4b6983f39aaa7fd654520aaa6300dd8a5fa4a7feb +size 33077 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c63b15ceb1703282b7a30e63606b215fa78d4b0f --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27f3d985794ed370c09481654261bb5af90b7278b593d388e6aed47b79037b83 +size 23247 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecf4f09d1cf488ef276d98aa94a304430db1baa6 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8cd5373917dff47d626737b7f3905e149c80211a773c1e94bb8cdd275604144 +size 69750 diff --git a/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9b9f96bc629eeb2498e2e5b1d3e8eaf56788a4c0 --- /dev/null +++ b/marked/Q/T-REC-Q.3932.2-201506-I_PDF-E/raw.md @@ -0,0 +1,3406 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3932.2** + +(06/2015) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for next generation networks + +--- + +**IMS/NGN performance benchmark – Part 2: +Subsystem configurations and benchmarks** + +Recommendation ITU-T Q.3932.2 + +ITU-T + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union' + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| Testing specifications for next generation networks | Q.3900–Q.3999 | +| Testing specifications for SIP-IMS | Q.4000–Q.4039 | +| Testing specifications for Cloud computing | Q.4040–Q.4059 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T Q.3932.2 + +# IMS/NGN performance benchmark – Part 2: Subsystem configurations and benchmarks + +## Summary + +Recommendation ITU-T Q.3932.2 provides the second part of a multi-part deliverable covering the IP multimedia subsystem (IMS)/next generation networks (NGN) performance benchmark, as identified below: + +Part 1: Core concepts; + +**Part 2: Subsystem configurations and benchmarks;** + +Part 3: Traffic sets and traffic profiles; + +Part 4: Reference load network quality parameters. + +This Recommendation contains the specific benchmarking use cases and scenarios, along with scenario-specific metrics and design objectives (DOs). It also defines the system under test (SUT) configuration parameters. The present document also contains any required extensions to the overall descriptions present in the present document, if necessary for the specific scenario. + +Part 3 defines an initial benchmark test through the specification of a traffic set, traffic-time profile and benchmark test procedure. + +Part 4 defines reference load network quality parameters for the use cases defined in Recommendation ITU-T Q.3932.2. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3932.2 | 2015-06-13 | 11 | 11.1002/1000/12497 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# Table of Contents + +###### Page + +| | | | +|-------|---------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms: ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | System under test (SUT) subsystems ..... | 4 | +| 6.1 | IMS/multimedia telephony (MMTel) ..... | 4 | +| 6.2 | IMS/IMS-based PSTN/ISDN emulation sub-system (PES)..... | 7 | +| 6.3 | IMS to IMS/PES..... | 7 | +| 6.4 | IMS/LTE basic configuration..... | 7 | +| 6.5 | VoLTE ..... | 8 | +| 7 | Use cases..... | 9 | +| 7.1 | IMS ..... | 9 | +| 8 | Session set-up/tear-down scenarios ..... | 12 | +| 8.1 | MMTel fixed access to MMTel fixed access ..... | 13 | +| 8.2 | IMS/PES to IMS/PES..... | 19 | +| 8.3 | MMTel fixed access – IMS/PES ..... | 19 | +| 8.4 | VoLTE to IMS/PES..... | 45 | +| 8.5 | VoLTE to VoLTE use case 12 ..... | 60 | +| 8.6 | MMTel fixed access – VoLTE ..... | 64 | +| 9 | Metrics and design objectives (DOs)..... | 72 | +| 9.1 | Delay probability ..... | 72 | +| 9.2 | Speech quality analysis..... | 86 | +| 9.3 | Call profiler traffic patterns ..... | 86 | +| | Appendix I – Call flows ..... | 89 | +| | Appendix II – Load profiles examples..... | 97 | +| | Appendix III – Examples for test reports..... | 98 | +| III.1 | Example of a call detail report..... | 98 | +| III.2 | Example of a call summary report..... | 98 | +| III.3 | Example of a voice summary report..... | 98 | +| III.4 | Example of a voice quality detail report..... | 99 | + + + +## Recommendation ITU-T Q.3932.2 + +# IMS/NGN performance benchmark – Part 2: Subsystem configurations and benchmarks + +# 1 Scope + +This Recommendation provides the second part of a multi-part deliverable covering the IMS/NGN performance benchmark, as identified below: + +Part 1: Core concepts; + +**Part 2: Subsystem configurations and benchmarks;** + +Part 3: Traffic sets and traffic profiles; + +Part 4: Reference load network quality parameters. + +This Recommendation contains the specific benchmarking use cases and scenarios, along with scenario-specific metrics and (DOs). It also defines the SUT configuration parameters. The present document also contains any required extensions to the overall descriptions present in the present document, if necessary for the specific scenario. + +Part 3 defines an initial benchmark test through the specification of a traffic set, traffic-time profile and benchmark test procedure. + +Part 4 defines reference load network quality parameters for the use cases defined in ITU-T Q.3932.2. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T P.862.1] Recommendation ITU-T P.862.1 (2003), *Mapping function for transforming P.862 raw result scores to MOS-LQO*. +- [ITU-T P.863] Recommendation ITU-T P.863 (2014), *Perceptual objective listening quality assessment*. +- [ITU-T Q.543] Recommendation ITU-T Q.543 (1993), *Digital exchange performance design objectives*. +- [ITU-T Q.3930] Recommendation ITU-T Q.3930 (2012), *Performance testing of distributed systems – Concepts and terminology*. +- [ITU-T Q.3931.2] Recommendation ITU-T Q.3931.2 (2011), *Performance benchmark for the PSTN/ISDN emulation subsystem of an IP multimedia system – Part 2: Subsystem configurations and benchmarks*. +- [ITU-T Q.3932.3] Recommendation ITU-T Q.3932.3 (2015), *IMS/NGN performance benchmark – Part 3: Traffic sets and traffic profiles*. +- [ITU-T T.38] Recommendation ITU-T T.38 (1998), *Procedures for real-time Group 3 facsimile communication over IP networks*. + +- [ITU-T V.34] Recommendation ITU-T V.34 (1998), *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.* +- [ITU-T V.152] Recommendation ITU-T V.152 (2010), *Procedures for supporting voice-band data over IP networks.* +- [ETSI TR 121 905] ETSI TR 121 905 V10.3.0 (2011), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905).* +- [ETSI TS 123 002] ETSI TS 123 002 V11.6.0 (2013), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.6.0 Release 11).* +- [ETSI TS 124 229] ETSI TS 124 229 (2009), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 8.7.0 Release 8).* +- [ETSI TS 183 036] ETSI TS 183 036 V2.1.1 (2009), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification.* +- [ETSI TS 183 043] ETSI TS 183 043 V1.1.1 (2006), *Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); IMS-based PSTN/ISDN Emulation Stage 3 specification.* +- [IETF RFC 3840] IETF RFC 3840 (2004), *Indicating User Agent Capabilities in the Session Initiation Protocol (SIP).* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +The IMS benchmarking definitions are described in [ITU-T Q.3930]. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms: + +For the purposes of this Recommendation, the abbreviations and acronyms for LTE given in [ETSI TR 121 905] and the following apply: + +| | | +|------|-----------------------------------| +| AKA | Authentication and Key Agreement | +| BGCF | Border Gateway Control Function | +| CSCF | Call Session Control Function | +| DTLS | Datagram Transport Layer Security | +| DO | Design Objective | +| GW | Gateway | +| HSS | Home Subscriber Server | +| FM | Fault Management | + +| | | +|--------|--------------------------------------------| +| IBCF | Interconnection Border Control Function | +| I-CSCF | Interrogating-CSCF | +| IM | IP Multimedia | +| IMS | IP Multimedia Subsystem | +| ISDN | Integrated Services Digital Network | +| IP | Internet Protocol | +| IPsec | Internet Protocol Security | +| ISC | IP multimedia Service Control | +| LCS | Location Services | +| LRF | Location Retrieval Function | +| MCS | Modulation and Coding Scheme | +| MGC | Media Gateway Controller | +| MME | Mobile Management Entity | +| MMTel | Multimedia Telephony | +| MRB | Media Resource Broker | +| MRF | Media Resource Function | +| MRFC | Media Resource Function Controller | +| NGN | Next Generation Networks | +| P-CSCF | Proxy-CSCF | +| PES | IMS-based PSTN/ISDN Emulation Sub-system | +| PSTN | Public Switched Telecommunications Network | +| QoS | Quality of Service | +| RTP | Real-Time Protocol | +| SA | Security Association | +| SBC | Session Border Control | +| SCS | Session Control Subsystem | +| S-CSCF | Serving CSCF | +| SLF | Subscriber Location Function | +| SUT | System Under Test | +| TLS | Transport Layer Security | +| TS | Test System | +| UDUB | User Determined User Busy | +| UE | User Equipment | + +# 5 Conventions + +None. + +# 6 System under test (SUT) subsystems + +## 6.1 IMS/multimedia telephony (MMtel) + +An IMS/NGN benchmark is required to allow not only a complete IMS network but also subsystems of a network corresponding to discrete products that may be available from a supplier. To address this requirement in this multi-part deliverable, a series of subsystems are defined, which will serve as a SUT for a benchmark test. IMS/NGN elements that do not appear in a subsystem are regarded as part of the test environment, which is present for a subsystem to function, but which is not itself subject to benchmarking. + +Figure 1 depicts the IMS reference architecture. The components of the architecture are the primary building blocks, which are either defined by the IMS standard, or defined by external standards and referenced by IMS. The links between the primary building blocks represent reference points over which the building blocks communicate with each other. + +The reference architecture is a logical architecture; no mapping of functional elements to hardware or software component is mandated. + +![Figure 1 – Overview of IMS functional entities [ETSI TS 123 002]. This diagram illustrates the IMS reference architecture, showing various functional entities and their interconnections. The entities are grouped into three main areas: IP multimedia networks (top), CS network (left), and Legacy mobile signalling networks (right). Key components include IMS-MGW, MRFP, MGCF, BGCF, I-CSCF, S-CSCF, HSS, SLF, MRB, E-CSCF, P-CSCF, IBCF, UE, TrGW, AS, LRF, and EATF. Interfaces are categorized into user traffic (solid lines) and signalling (dashed lines), with specific reference points labeled such as Mb, Cs, Mg, Mk, Mj, Mn, Mp, Rx, Ici, Mm, Ma, Cx, Gc, Gr, Sh, Dh, ISC, RC, Cr, Mw, Mi, Mx, Ix, Iz, and Ut.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Legend: + — Interfaces supporting user traffic + - - - Interfaces supporting signalling + +Q.3932.2(15)\_F01 + +Figure 1 – Overview of IMS functional entities [ETSI TS 123 002]. This diagram illustrates the IMS reference architecture, showing various functional entities and their interconnections. The entities are grouped into three main areas: IP multimedia networks (top), CS network (left), and Legacy mobile signalling networks (right). Key components include IMS-MGW, MRFP, MGCF, BGCF, I-CSCF, S-CSCF, HSS, SLF, MRB, E-CSCF, P-CSCF, IBCF, UE, TrGW, AS, LRF, and EATF. Interfaces are categorized into user traffic (solid lines) and signalling (dashed lines), with specific reference points labeled such as Mb, Cs, Mg, Mk, Mj, Mn, Mp, Rx, Ici, Mm, Ma, Cx, Gc, Gr, Sh, Dh, ISC, RC, Cr, Mw, Mi, Mx, Ix, Iz, and Ut. + +**Figure 1 – Overview of IMS functional entities [ETSI TS 123 002]** + +For the purposes of benchmarking, however, certain rules concerning subsystem configurations are required. These rules that benchmark measurements taken from equivalent subsystems of different vendors are comparable with one another. + +The general guidelines for defining a SUT configuration are: + +- All of the functional elements of the subsystem shall be present in the SUT configuration; +- All hardware elements used in the implementation of the SUT configuration shall be completely enumerated; + +- All the quality of service (QoS) spec measurements defined at the interfaces to the SUT shall be collected as specified in the benchmark test. +- All hardware-specific measurements (e.g., CPU utilization, memory utilization, fabric bandwidth) specified in the benchmark test should be collected for all hardware elements used in the implementation of the SUT configuration; +- SUT interface characteristics shall be specified so that they can be emulated by the test system (TS), including: + - Security (e.g., Internet protocol security (IPsec), transport layer security (TLS), datagram transport layer security (DTLS), etc.); + - Interface network characteristics (e.g., up and down bandwidth, up and down latency). + +#### 6.1.1 Session control subsystem (SCS) + +The SCS consists of the proxy-CSCF (P-CSCF), interrogating-CSCF (I-CSCF) and serving-CSCF (S-CSCF), and home subscriber server (HSS) components, as depicted in Figure 2. + +A valid SCS configuration consists of the set of x-CSCF building blocks, as well as the database functions HSS and subscriber location function (SLF) that support their functionality. + +The reference points for the SCS are the $G_m$ reference point between the user equipment (UE) traffic generator and the home and visited P-CSCFs, the $M_r$ reference point between the S-CSCF and the Simulated MRFC, the $M_j$ reference point between the S-CSCF and the Simulated BGCF, and the TS management interface to the HSS and SLF databases. + +A SUT for this subsystem may consist of either one or two SCS configurations to allow benchmark tests to use a combination of local and roaming simulated subscribers. + +![Figure 2 – SUT topology for SCS. The diagram shows a 'Test system' (TS) connected to three 'P-CSCF' units. These P-CSCFs are connected to two 'I-CSCF' units, which are in turn connected to three 'S-CSCF' units. The S-CSCFs are connected to a 'DNS' unit, an 'HSS/UPSF' unit, and an 'SLF' unit. The S-CSCFs are also connected to a 'Test environment' containing 'MRFC' and 'BGCF' units. The diagram is labeled 'System under test' and includes a legend for reference points: Gm (red solid line), Mw (blue solid line), Cx (red dashed line), Dx (red dash-dot line), DNS-Q (yellow dashed line), Mr (green solid line), and Mi (green dashed line).](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram illustrates the SUT topology for the SCS. On the left, a 'Test system' (TS) is connected to three 'P-CSCF' units via red solid lines (Gm reference point). These P-CSCFs are connected to two 'I-CSCF' units via blue solid lines (Mw reference point). The I-CSCFs are connected to three 'S-CSCF' units via blue solid lines (Mw reference point). The S-CSCFs are connected to a 'DNS' unit via yellow dashed lines (DNS-Q reference point). The S-CSCFs are also connected to an 'HSS/UPSF' unit via red dashed lines (Cx reference point) and red dash-dot lines (Dx reference point). The S-CSCFs are connected to an 'SLF' unit via red dash-dot lines (Dx reference point). The S-CSCFs are also connected to a 'Test environment' containing 'MRFC' and 'BGCF' units via green solid lines (Mr reference point) and green dashed lines (Mi reference point). The entire setup is labeled 'System under test'. + +Legend: + +- ← Gm (red solid line) +- ← Mw (blue solid line) +- ← Cx (red dashed line) +- ← Dx (red dash-dot line) +- ← DNS-Q (yellow dashed line) +- ← Mr (green solid line) +- ← Mi (green dashed line) + +Q.3932.2(15)\_F02 + +Figure 2 – SUT topology for SCS. The diagram shows a 'Test system' (TS) connected to three 'P-CSCF' units. These P-CSCFs are connected to two 'I-CSCF' units, which are in turn connected to three 'S-CSCF' units. The S-CSCFs are connected to a 'DNS' unit, an 'HSS/UPSF' unit, and an 'SLF' unit. The S-CSCFs are also connected to a 'Test environment' containing 'MRFC' and 'BGCF' units. The diagram is labeled 'System under test' and includes a legend for reference points: Gm (red solid line), Mw (blue solid line), Cx (red dashed line), Dx (red dash-dot line), DNS-Q (yellow dashed line), Mr (green solid line), and Mi (green dashed line). + +Figure 2 – SUT topology for SCS + +#### 6.1.2 HSS subsystem + +This subsystem refers to the HSS. + +#### 6.1.3 P-CSCF subsystem + +The P-CSCF consists of the P-CSCF component, as depicted in Figure 3. + +A valid P-CSCF configuration consists of the set of P-CSCF building blocks. The reference points for the subsystem are the $G_m$ reference point between the UE traffic generator and the home and visited P-CSCFs, and the $M_w$ reference points to the other simulated components (which are part of the TS in this configuration). + +![Diagram of the P-CSCF subsystem showing the Test system, System under test, and Test environment.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the P-CSCF subsystem configuration. It consists of three main components: a 'Test system' box containing a 'TS' (Traffic Generator) block, a 'System under test' box containing a 'P-CSCF' block, and a 'Test environment' box containing 'DNS', 'I-CSCF', and 'S-CSCF' blocks. The 'Test system' is connected to the 'System under test' via a red double-headed arrow labeled $G_m$ . The 'System under test' is connected to the 'Test environment' via three blue double-headed arrows labeled $M_w$ , pointing to the 'DNS', 'I-CSCF', and 'S-CSCF' blocks respectively. A dashed green double-headed arrow labeled 'DNS-Q' connects the 'P-CSCF' block to the 'DNS' block. The reference points are defined in a legend at the bottom: a red double-headed arrow for $G_m$ , a blue double-headed arrow for $M_w$ , and a dashed green double-headed arrow for 'DNS-Q'. The text 'Q.3932.2(15)\_F03' is located at the bottom right of the diagram. + +Diagram of the P-CSCF subsystem showing the Test system, System under test, and Test environment. + +Figure 3 – P-CSCF subsystem + +#### 6.1.4 S/I-CSCF subsystem + +The S/I-CSCF subsystem consists of the S-CSCF, I-CSCF, HSS and SLF components, as depicted in Figure 4. + +A valid S/I-CSCF configuration consists of the set of S-CSCF and I-CSCF building blocks, as well as the database functions HSS and SLF that support their functionality. The reference points for the subsystem are the $M_w$ reference point between the simulated P-CSCF and the S/I-CSCFs. + +![Figure 4: S/I-CSCF subsystem diagram. It shows a 'Test system' (TS) connected to an 'I-CSCF'. The 'I-CSCF' is part of the 'System under test' which includes 'S-CSCF', 'SLF', and 'HSS/UPSF'. The 'S-CSCF' is connected to 'DNS', 'P-CSCF', and 'SIP AS' within a 'Test environment'. The 'Test environment' also contains 'BGCF', 'MGCF', 'MRFC', and 'CCF'. Various interfaces are shown with colored arrows: Gm (red solid), ISC (blue dashed), Mg (yellow solid), DNS-Q (yellow dashed), Mi (green solid), Mr (green dashed), Rf (green dashed), Cx (red dashed), and Dx (red dashed).](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 4: S/I-CSCF subsystem diagram. It shows a 'Test system' (TS) connected to an 'I-CSCF'. The 'I-CSCF' is part of the 'System under test' which includes 'S-CSCF', 'SLF', and 'HSS/UPSF'. The 'S-CSCF' is connected to 'DNS', 'P-CSCF', and 'SIP AS' within a 'Test environment'. The 'Test environment' also contains 'BGCF', 'MGCF', 'MRFC', and 'CCF'. Various interfaces are shown with colored arrows: Gm (red solid), ISC (blue dashed), Mg (yellow solid), DNS-Q (yellow dashed), Mi (green solid), Mr (green dashed), Rf (green dashed), Cx (red dashed), and Dx (red dashed). + +Figure 4 – S/I-CSCF subsystem + +## 6.2 IMS/IMS-based PSTN/ISDN emulation sub-system (PES) + +The SUT subsystems for IMS/PES are described in this Recommendation. + +## 6.3 IMS to IMS/PES + +The IMS and IMS/PES configurations are depicted in Figure 5. + +![Figure 5: MMtel and IMS/PES configuration diagram. It shows two User Equipment (UE) devices connected to a P-CSCF, which is connected to an S-CSCF. The S-CSCF is connected to an AS (Application Server). The P-CSCF is also connected to a VGW (PDN Gateway) containing MGC, FM, and SIP UA. The VGW is connected to an RTP cloud, which is connected to another MGF (Media Gateway Function) and a UE. The RTP cloud is also connected to an AGCF (Access Gateway Control Function) containing SIP UA, FM, and MGC. The AGCF is connected to another UE. The diagram is labeled Q.3932.2(15)_F05.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 5: MMtel and IMS/PES configuration diagram. It shows two User Equipment (UE) devices connected to a P-CSCF, which is connected to an S-CSCF. The S-CSCF is connected to an AS (Application Server). The P-CSCF is also connected to a VGW (PDN Gateway) containing MGC, FM, and SIP UA. The VGW is connected to an RTP cloud, which is connected to another MGF (Media Gateway Function) and a UE. The RTP cloud is also connected to an AGCF (Access Gateway Control Function) containing SIP UA, FM, and MGC. The AGCF is connected to another UE. The diagram is labeled Q.3932.2(15)\_F05. + +Figure 5 – MMtel and IMS/PES configuration + +## 6.4 IMS/LTE basic configuration + +The IMS/LTE basic configuration is depicted in Figure 6. + +![Figure 6 – IMS/LTE basic configuration diagram showing UE, eNodeB, MME, S-GW, P-GW, IMS core (HSS, P-CSCF, IMS-ALG, IMS-AGW, MMTel AS, IS-CSCF) and various interfaces like S1-MME, S1-U, S11, S5, S6a, S9, Gm, Mb, Ut, Sh, Cx, ISC, Mw, Rx, Gx, SGi.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +This diagram illustrates the basic configuration for IMS/LTE. On the left, a UE with an IMS UA connects to an eNodeB via an LTE-Uu interface. The eNodeB connects to an MME via S1-MME and to an S-GW via S1-U. The MME connects to the S-GW via S11 and to the HSS via S6a. The S-GW connects to the P-GW via S5. The P-GW connects to the IMS core via SGi and to the PCRF via Gx. The PCRF connects to the P-CSCF via Rx. The IMS core contains the HSS, P-CSCF/IMS-ALG/IMS-AGW, MMTel AS, and IS-CSCF. Interfaces include Ut (UE to MMTel AS), Gm (UE to P-CSCF), Mb (UE to IS-CSCF), Sh (HSS to P-CSCF), Cx (P-CSCF to IS-CSCF), ISC (MMTel AS to IS-CSCF), and Mw (P-CSCF to IS-CSCF). A reference label Q.3932.2(15)\_F06 is present in the bottom right. + +Figure 6 – IMS/LTE basic configuration diagram showing UE, eNodeB, MME, S-GW, P-GW, IMS core (HSS, P-CSCF, IMS-ALG, IMS-AGW, MMTel AS, IS-CSCF) and various interfaces like S1-MME, S1-U, S11, S5, S6a, S9, Gm, Mb, Ut, Sh, Cx, ISC, Mw, Rx, Gx, SGi. + +Figure 6 – IMS/LTE basic configuration + +## 6.5 VoLTE + +The VoLTE components are depicted in Figure 7. + +![Figure 7 – VoLTE basic configuration diagram showing HPLMN and VPLMN components. It includes UE, eNodeB, Sec-GW, MME, S-GW, P-GW, IMS core (HSS, P-CSCF, IMS-ALG, IMS-AGW, MMTel/RCS Application servers, MRFP, MRG, I/S-CSCF, IBCF/TrGw), Diameter agent, ENUM server, and IPX. Interfaces include S1-MME, S1-U, S11, S5, S6a, S9, Gx, SGi, Diameter App ID=0, ENUM, and Ici/Izi.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +This diagram shows the VoLTE basic configuration across HPLMN and VPLMN boundaries. In the HPLMN (top), a UE with IMS UA connects to an eNodeB via LTE-Uu, which connects to a Sec-GW. The Sec-GW connects to an MME via S1-MME and to an S-GW via S1-U. The MME connects to the S-GW via S11 and to a Diameter agent via S6a. The Diameter agent connects to the HSS via S9 and to the P-CSCF/IMS-ALG/IMS-AGW via Rx. The P-CSCF/IMS-ALG/IMS-AGW connects to the IMS core (MMTel/RCS Application servers, MRFP, MRG, I/S-CSCF, IBCF/TrGw) via Mw, Cx, and ISC. The IMS core also connects to the HSS via Sh. The Diameter agent connects to an ENUM server via Diameter App ID=0. The ENUM server connects to an IPX via ENUM. The IPX connects to the IBCF/TrGw via Ici/Izi. In the VPLMN (bottom), the UE connects to an eNodeB via LTE-Uu, which connects to a Sec-GW. The Sec-GW connects to an MME via S1-MME and to an S-GW via S1-U. The MME connects to the S-GW via S11 and to a Diameter agent via S6a. The Diameter agent connects to the HSS via S9 and to the P-CSCF/IMS-ALG/IMS-AGW via Rx. The P-CSCF/IMS-ALG/IMS-AGW connects to the IBCF/TRGW via Mx. The IBCF/TRGW connects to the IPX via Ici/Izi. A reference label Q.3932.2(15)\_F07 is present in the bottom right. + +Figure 7 – VoLTE basic configuration diagram showing HPLMN and VPLMN components. It includes UE, eNodeB, Sec-GW, MME, S-GW, P-GW, IMS core (HSS, P-CSCF, IMS-ALG, IMS-AGW, MMTel/RCS Application servers, MRFP, MRG, I/S-CSCF, IBCF/TrGw), Diameter agent, ENUM server, and IPX. Interfaces include S1-MME, S1-U, S11, S5, S6a, S9, Gx, SGi, Diameter App ID=0, ENUM, and Ici/Izi. + +Figure 7 – VoLTE basic configuration + +# **7 Use cases** + +The following use cases and corresponding tests are currently defined. This clause attempts to define a set of basic use-cases and further ones can be defined similarly. These newly defined use cases, or modifications to the ones presented here, will have to be described in a similar manner in the test report. + +## **7.1 IMS** + +#### **7.1.1 Registration/de-registration use case 1** + +Registration is the first use- case that is employed when using an IMS network. During this operation, the UE announces its contact location to the home domain registrar in order for the home network to route terminating messages towards it. It is performed by the UE when it is turned on. De-registration is the last operation that the UE performs before it is turned off and it is used to invalidate the registered contact information. + +Because of security concerns, this operation has to be authenticated and the assigned S-CSCF challenges the UE using authentication vectors obtained from the HSS. + +During the initial registration, the P-CSCF also negotiates a set of security associations (SAs) with the UE. Future registration/deregistration operations performed over these secure channels do not need to further be authenticated as the integrity of the messages is protected. + +The registration has an attached expiration timer. Depending on the type of the network (fixed or mobile) and the usage patterns, this timer can vary from a few minutes up to one week, and it is negotiated between the UE and the home network. Before this timer expires, or when roaming to a new visited network, the UE has to start re-registration scenarios. + +As part of this use case, after registering, the UE will subscribe to its own registration status at the assigned S-CSCF. This subscription will need to be refreshed periodically, similarly to the registration. It is not required to unsubscribe, as the S-CSCF will automatically terminate it on de-registration. To avoid congestion, the notification timing is not strictly coupled to the events that triggered them, and can have a delay in the order of seconds. The first one is sent shortly after subscription, and as a rule, the UE should be ready to respond to notification at any moment during the subscription period. See Figure 8. + +![Figure 8 – Registration/de-registration state machine diagram. The diagram shows the state transitions of a User Equipment (UE) for registration and de-registration. The main states are Off, Discovery, Unsecured, Secured, Secured and registered, and Secured, registered and subscribed. Transitions include 'Turn on', 'Turn off', 'Attachment', 'Detachment', 'Authentication', 'De-registration', 'Save location', 'Subscription', 'Unsubscribe', 'Re-authentication', and 'Update'. The diagram is divided into two main sections: 'IP connectivity' and 'Security communication'. The 'IP connectivity' section includes the states Off, Discovery, and Unsecured. The 'Security communication' section includes the states Secured, Secured and registered, and Secured, registered and subscribed. The 'IMS ready' state is also shown within the 'Security communication' section.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Off + Off --> Discovery : Turn on + Discovery --> Off : Turn off + Discovery --> Unsecured : Attachment + Unsecured --> Discovery : Detachment + Unsecured --> Secured : Authentication + Secured --> Unsecured : De-registration + Secured --> Secured_and_registered : Save location + Secured_and_registered --> Secured : De-registration + Secured_and_registered --> Secured_and_registered_and_subscribed : Subscription + Secured_and_registered_and_subscribed --> Secured_and_registered : Unsubscribe + Secured_and_registered_and_subscribed --> Secured : Update + Secured_and_registered_and_subscribed --> Secured : Re-authentication + +``` + +Figure 8 – Registration/de-registration state machine diagram. The diagram shows the state transitions of a User Equipment (UE) for registration and de-registration. The main states are Off, Discovery, Unsecured, Secured, Secured and registered, and Secured, registered and subscribed. Transitions include 'Turn on', 'Turn off', 'Attachment', 'Detachment', 'Authentication', 'De-registration', 'Save location', 'Subscription', 'Unsubscribe', 'Re-authentication', and 'Update'. The diagram is divided into two main sections: 'IP connectivity' and 'Security communication'. The 'IP connectivity' section includes the states Off, Discovery, and Unsecured. The 'Security communication' section includes the states Secured, Secured and registered, and Secured, registered and subscribed. The 'IMS ready' state is also shown within the 'Security communication' section. + +**Figure 8 – Registration/de-registration state machine** + +- a) Off – In this state the UE does not have any interaction with the environment. +- b) Discovery – The UE is acquiring an internet protocol (IP) address and finds the address of the outbound proxy-CSCF. +- c) Unsecured – In this state the UE is completely attached to the IP layer and can fully act at the signalling level. This state is mainly used to send initial registration intentions. No traffic is to be trusted by the network until the UE is authenticated. The UE should not trust incoming signalling until it attaches to a correctly authenticated network. +- d) Secured – The UE begins authentication by requesting an authentication challenge. The UE can verify the authenticity of this challenge and it creates a SA with the proxy-CSCF. +- e) Secured and registered – The UE sends the authentication challenge response to the network, indicating the location information that it wishes to save. While in this state, as communication is secured, updates can be performed without re-authentication. +- f) Secured, registered and subscribed – To react to network initiated events regarding the registration status, the UE subscribes to its own registration event package. The UE will then receive notifications on changes and it can act accordingly. + +For simplification, it is considered that the initial state is unsecured: The UE simulated by the TS already has IP connectivity and the proxy-CSCF addresses are considered as input configuration for the TS. + +##### 7.1.1.1 Definition + +The registration/de-registration is the process by which a UE announces, updates, or deletes its location information to the home domain's registrar. This operation is authenticated and a secure communication channel for subsequent signalling is set up between the UE and the network. + +##### **7.1.1.2 Scenarios** + +While the scenarios describe actions on the part of the UE, the portion of the signalling path between the UE and the complete IMS system outside the SUT configuration are simulated by the test environment with TS characteristics fixed with stated values. + +###### **7.1.1.2.1 Use case 1 – Scenario 1 – Successful initial registration with unprotected REGISTER requests on the SIP default port values as specified in [IETF RFC 326]** + +The P-CSCF shall be prepared to receive the unprotected REGISTER requests on the SIP default port values as specified in [IETF RFC 3261]. The P-CSCF shall also be prepared to receive the unprotected REGISTER requests on the port advertised to the UE during the P-CSCF discovery procedure. + +##### **7.1.1.2.2 Use case 1 – Scenario 2 – Successful initial registration with IMS authentication and key agreement (AKA) as a security mechanism** + +The P-CSCF supports the registration with IMS AKA as a security mechanism described in clause 5.2.2.2 of [ETSI TS 124 229]. + +###### **7.1.1.2.3 Use case 1- Scenario 3 – Successful initial registration with SIP digest without TLS as a security mechanism** + +The P-CSCF supports the registration with SIP digest without TLS as a security mechanism described in clause 5.2.2.3 of [ETSI TS 124 229]. + +###### **7.1.1.2.4 Use case 1 – Scenario 4 – Successful initial registration with SIP digest with TLS as a security mechanism** + +The P-CSCF supports the registration with SIP digest with TLS as a security mechanism described in clause 5.2.2.4 of [ETSI TS 124 229]. + +##### **7.1.1.2.5 Use case 1- Scenario 5 – Successful initial registration with NASS-IMS bundled authentication as a security mechanism** + +The P-CSCF supports the registration with NASS-IMS bundled authentication as a security mechanism described in clause 5.2.2.5 of [ETSI TS 124 229]. + +##### **7.1.1.2.6 Use case 1 – Scenario 6 – Successful initial registration with GPRS-IMS bundled authentication as a security mechanism** + +The P-CSCF supports the registration with GPRS-IMS bundled authentication as a security mechanism described in clause 5.2.2.6 of [ETSI TS 124 229]. + +###### **7.1.1.2.7 Use case 1 – Scenario 7 – Re-registration – User currently registered** + +To refresh the registration timer, the UE sends a re-registration request before the expiration time expires. This should be sent either 600 seconds before the expiration time if the registration time was greater than 1 200 seconds, or when half the registration time has passed when the registration time was under, equal to, or less than 1 200 seconds. This scenario can also be employed at any time during the registration period when the UE intends to update its capabilities according to [IETF RFC 3840]. + +If a secure channel has been set up and it is used during this procedure, the S-CSCF does not need to authenticate the user. The signalling is presented in Figure 9. If the request is not sent through the secure channel then the signalling flow is similar to that of the initial registration scenario. + +![Sequence diagram for Figure 9: Re-registration – user currently registered signalling flow. Lifelines: UE, P-CSCF, DNS, I-CSCF, S-CSCF, HSS/UPSF. The sequence starts with UE sending a REGISTER to P-CSCF. P-CSCF sends a DNS: DNS-Q to DNS. P-CSCF then sends a REGISTER to I-CSCF. I-CSCF sends a Cx: user registration status query to HSS/UPSF. HSS/UPSF sends a REGISTER to S-CSCF. S-CSCF updates the registration timer. S-CSCF sends a 200 OK to I-CSCF. I-CSCF sends a 200 OK to P-CSCF. P-CSCF sends a 200 OK to UE.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant P-CSCF + participant DNS + participant I-CSCF + participant S-CSCF + participant HSS/UPSF + + UE->>P-CSCF: 1. REGISTER + P-CSCF->>DNS: 2. DNS: DNS-Q + P-CSCF->>I-CSCF: 3. REGISTER + I-CSCF->>HSS/UPSF: 4. Cx: user registration status query + I-CSCF->>S-CSCF: 5. REGISTER + S-CSCF->>S-CSCF: 6. Update registration timer + S-CSCF->>I-CSCF: 7. 200 OK + I-CSCF->>P-CSCF: 8. 200 OK + P-CSCF->>UE: 9. 200 OK + +``` + +Q.3932.2(15)\_F09 + +Sequence diagram for Figure 9: Re-registration – user currently registered signalling flow. Lifelines: UE, P-CSCF, DNS, I-CSCF, S-CSCF, HSS/UPSF. The sequence starts with UE sending a REGISTER to P-CSCF. P-CSCF sends a DNS: DNS-Q to DNS. P-CSCF then sends a REGISTER to I-CSCF. I-CSCF sends a Cx: user registration status query to HSS/UPSF. HSS/UPSF sends a REGISTER to S-CSCF. S-CSCF updates the registration timer. S-CSCF sends a 200 OK to I-CSCF. I-CSCF sends a 200 OK to P-CSCF. P-CSCF sends a 200 OK to UE. + +**Figure 9 – Re-registration – user currently registered signalling flow** + +###### 7.1.1.2.8 Use case 1 – Scenario 8 – Re-subscription – user currently registered + +As the subscription might have a different expiration timer than the registration, re-subscription is not necessarily linked to re-registration. The process is detailed in Figure 10. + +![Sequence diagram for Figure 10: Re-subscription – user currently registered signalling flow. Lifelines: UE, P-CSCF, DNS, I-CSCF, S-CSCF, HSS/UPSF. The sequence starts with UE sending a SUBSCRIBE to P-CSCF. P-CSCF sends a SUBSCRIBE to S-CSCF. S-CSCF sends a 200 OK to P-CSCF. P-CSCF sends a 200 OK to UE.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` + +sequenceDiagram + participant UE + participant P-CSCF + participant DNS + participant I-CSCF + participant S-CSCF + participant HSS/UPSF + + UE->>P-CSCF: 1. SUBSCRIBE + P-CSCF->>S-CSCF: 2. SUBSCRIBE + S-CSCF->>P-CSCF: 3. 200 OK + P-CSCF->>UE: 4. 200 OK + +``` + +Q.3932.2(15)\_F10 + +Sequence diagram for Figure 10: Re-subscription – user currently registered signalling flow. Lifelines: UE, P-CSCF, DNS, I-CSCF, S-CSCF, HSS/UPSF. The sequence starts with UE sending a SUBSCRIBE to P-CSCF. P-CSCF sends a SUBSCRIBE to S-CSCF. S-CSCF sends a 200 OK to P-CSCF. P-CSCF sends a 200 OK to UE. + +**Figure 10 – Re-subscription – user currently registered signalling flow** + +##### 7.1.1.2.9 Use case 1 – Scenario 9 – Re-registration – user roaming + +When the UE is roaming to another visited network, the procedures are similar to those of initial registration. As there is no SA set up with the new P-CSCF, the initial REGISTER request will be authenticated. The network will internally take care of the old registration, without any UE interaction. + +###### 7.1.1.2.10 Use case 1 – Scenario 10 – UE initiated de-registration + +When the UE requires terminating the registration immediately, it can do so by issuing a REGISTER request with an expiration timer set to "0". + +# 8 Session set-up/tear-down scenarios + +This use case corresponds to a normal 2-party call. The "session set-up" part refers to the establishment of the call and the "session tear-down" to its termination. Before this scenario is performed, the respective user endpoints which belong to the particular SUT domain and are involved in the communication have to be successfully registered/re-registered. The registration period should not be performed during execution of this use case (it is acceptable to do a re-registration refreshment during a call scenario). + +This version of the document covers several call scenarios that are encountered the most in a real life deployment. + +Several situations for the user endpoints can be considered, based on the IP-CAN resource reservation status on the two participating sides. For example the originating and/or terminating party might require resource reservation, or they could already have the resources pre-allocated, before the start of the scenario. + +In case the access network is not part of the SUT, the IP-CAN reservation steps should be simulated by fixed delays in the TS and the test report shall contain these values. + +In all successful call scenarios defined in the next clauses, the signalling flow of the tear-down part is depicted as initiated on the terminating side of the call. When generating traffic, the TS should also simulate the symmetric case when the originating user initiates the tear-down and the TS should maintain a 1:1 ratio between the two cases. + +During these scenarios there are several waiting times during which the TS should pause, like the ringing time or the call hold time. Distribution of these delays can follow a constant or a Poisson distribution. + +## 8.1 MMTel fixed access to MMTel fixed access + +| MMTel fixed access to MMTel fixed access use case 2 | | | +|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 1 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow a) Successful call – resource reservation on both sides | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 100 Trying | | +| ← | 183 Session Progress | | +| | PRACK → | | +| ← | 200 OK PRACK | | +| | UPDATE → | | +| ← | 200 OK UPDATE | | +| ← | 180 Ringing | | +| ← | 200 OK | | +| | ACK → | | +| | BYE → | | +| ← | 200 OK BYE | | +| Apply post-test routine | | | +| Message flow: b), c) | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK → | | +| | BYE → | | +| ← | 200 OK BYE | | +| Apply post-test routine | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow a) Successful call – Resource reservation on both sides | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 100 Trying | | +| ← | 183 Session Progress | | +| | PRACK → | | +| ← | 200 OK PRACK | | +| | UPDATE → | | +| ← | 200 OK UPDATE | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK → | | +| ← | BYE | | +| | 200 OK BYE → | | +| Apply post-test routine | | | +| Message flow: b), c) | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK → | | +| ← | BYE | | +| | 200 OK BYE → | | +| Apply post-test routine | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | +|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call with fax with 33,6 kbit/s (super G3 fax)
This scenario represents the case when in the active call state the fax transfer on the media is performed correctly and the echo cancellers in the gateway (GW) are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP

m=audio RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio RTP/AVP 8 | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK → | | +| | Communication | | +| | BYE → | | +| ← | 200 OK BYE | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------|--|---|------------|--|---|-------------|--|---|---------------|--|--|-------|--|--|---------------|--|--|-------|--|---|------------|--| +| Scenario 4 | Basic call with fax with 14,4 kbit/s
This scenario represents the case when in the active call state the fax transfer on the media is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) a resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP

m=audio RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE →
← 100 Trying
← 180 Ringing
← 200 OK INVITE
ACK →
Communication
BYE →
← 200 OK BYE
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE → | | ← | 100 Trying | | ← | 180 Ringing | | ← | 200 OK INVITE | | | ACK → | | | Communication | | | BYE → | | ← | 200 OK BYE | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | BYE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 5 | Basic call – fax with 14,4 kbit/s with ITU-T V.152
This scenario represents the case when in the active call state the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP

m=audio RTP/AVP 8
a=rtpmap PCMA/8000
a=gpmd; vbd=yes

180/200 OK INVITE: SDP

m=audio RTP/AVP
a=rtpmap PCMA/8000
a=gpmd; vbd=yes | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--------------------------------|--|--| +| Scenario 6 | Basic call – fax with 14,4 kbit/s using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
m=image udptl t38
180/200 OK INVITE: SDP
m=image udptl t38 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------|--|---|---------------|--|--|-------|--| +| Scenario 7 | Called user is user busy
This scenario represents the case, when the called user is user determined user busy (UDUB), the network initiate call clearing to the calling user | | | | | | | | | | | | | +| Options | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE →
← 486 Busy Here
ACK →
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE → | | ← | 486 Busy Here | | | ACK → | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | +| | INVITE → | | | | | | | | | | | | | +| ← | 486 Busy Here | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------------|--|--|-------------------------|--|---|---------------------|--|--|----------------------------|--|---|--------------------------|--|--|------------------------------|--|---|------------------|--|--|------------------------------|--|--|------------------|--|----------------------|--|--|--------------------------------|--|--| +| Scenario 8 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
CFU is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A) →
ACK(Call-ID A-B)
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) → | | | CFU is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) → | | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) → | | ← | ACK(Call-ID B-C) | | | 200 OK INVITE(Call-ID B-A) → | | | ACK(Call-ID A-B) | | Communication | | | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFU is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID B-A) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 9 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters)
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFB is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFB is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFB is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|---|--------------------------|--|--|--------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 10 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | ← | 180 Ringing(Call-ID B-A) | | | CFNR is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------------------------------------------|--|---|--------|--|--|---------------|---|--|--------|---|---|-------------|--|---|--------|--|--|---------------|---|---|---------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 11 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful.
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS request was already successful
← NOTIFY
200 OK NOTIFY →
INVITE →
← 180 Ringing
← NOTIFY
200 OK NOTIFY →
← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY | → | | INVITE | → | ← | 180 Ringing | | ← | NOTIFY | | | 200 OK NOTIFY | → | ← | 200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to MMTel fixed access use case 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------------------------------------------|--|---|--------|--|--|---------------|---|--|--------|---|---|-------------|--|---|--------|--|--|---------------|---|---|---------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 12 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.
Ensure that the recall from user A to user B is successful.
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCNR request was already successful
← NOTIFY
200 OK NOTIFY →
INVITE →
← 180 Ringing
← NOTIFY
200 OK NOTIFY →
← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCNR request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY | → | | INVITE | → | ← | 180 Ringing | | ← | NOTIFY | | | 200 OK NOTIFY | → | ← | 200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCNR request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +## 8.2 IMS/PES to IMS/PES + +The use cases for IMS/PES are described in [ITU-T Q.3931.2] + +### 8.3 MMTel fixed access – IMS/PES + +#### 8.3.1 Integrated services digital network (ISDN) to MMTel fixed access use case 4 + +| ISDN to MMTel fixed access use case 4 | | +|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 |

Basic call with BC= ITC_value – enblock sending

This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters)

| +| Options |
  • a) resource reservation is on both sides
  • b) no resource reservation on terminating side
  • c) no resource reservation on either side
| +| Message flow | | +| SIP (TS A) |
Core network
SIP (TS B)

INVITE →
← 100 Trying
← 180 Ringing
← 200 OK INVITE
ACK →
Communication
BYE →
← 200 OK BYE

| +| SIP parameter
public switched telecommunications network (PSTN) XML BearerCapability element in the INVITE | 
 INVITE:   Content-Type: application/vnd.etsi.pstn+xml   Content-Disposition: signal;handling=optional  <?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>ITC_value<     BCoctet4       TransferMode>00<       InformationTransferRate>10000<     BCoctet5       Layer1Identification>01<       UserInfoLayer1Protocol>00011<
| + +| ISDN to MMTel fixed access use case 4 | | | +|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Basic call with BC= ITC_value – enblock sending
This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| | ← 100 Trying | | +| | ← 180 Ringing | | +| | ← 200 OK INVITE | | +| | ACK → | | +| | Communication | | +| | ← BYE | | +| | 200 OK BYE → | | +| SIP parameter
PSTN XML BearerCapability
element in the INVITE | INVITE:
Content-Type: application/vnd.etsi.pstn+xml
Content-Disposition: signal;handling=optional


PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>ITC_value<
<          BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011< | | + +**Table 1 – PSTN XML BearerCapability** + +| ITC_value | BC information transfer capability | XML InformationTransferCapability | +|-----------|------------------------------------|-----------------------------------| +| ITC_VA_1 | Speech | '00000' | +| ITC_VA_2 | 3.1 kHz audio | '10000' | +| ITC_VA_3 | unrestricted digital information | '01000' | + +| ISDN to MMTel fixed access use case 4 | | | +|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – overlap sending with BC= speech
This scenario represents the case when the call establishment is using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow multiple INVITE method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) | → | +| | INVITE(CSq 2) | → | +| ← | 484 Address Incomplete(CSq 1) | → | +| | ACK | → | +| | INVITE(CSq 3) | → | +| ← | 484 Address Incomplete(CSq 2) | → | +| | ACK | → | +| | ..... | | +| | INVITE(CSq 4) | → | +| ← | 484 Address Incomplete(CSq 3) | → | +| | ACK | → | +| ← | 180 Ringing(CSq 4) | | +| Apply post-test routine | | | +| Message flow overlap sending, the in-dialogue method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) 1 | → | +| ← | 484 Address Incomplete(CSq 1) | → | +| | ACK | → | +| | INVITE(CSq 2) 2 | → | +| ← | 183 Session Progress(CSq 2) | → | +| | PRACK | → | +| ← | 200 OK PRACK | | +| | INFO | → | +| ← | 200 OK INFO | | +| | ..... | | +| | INFO | → | +| ← | 200 OK INFO | | +| ← | 180 Ringing(CSq 2) | | +| Apply post-test routine | | | + +| ISDN to MMTel fixed access use case 4 | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------|------------------------|--------------------------|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--------------------------------|--|--| +| Scenario 4 | Basic call with BC= 3,1 KHz audio – fax with 33,6 kbit/s
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter |
INVITE: SDP m=audio <Port> RTP/AVP 8/0
180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8
| INVITE: SDP | m=audio RTP/AVP 8/0 | 180/200 OK INVITE: SDP | m=audio RTP/AVP 8 | | | | | | | | | | | | | | | +| INVITE: SDP | m=audio RTP/AVP 8/0 | | | | | | | | | | | | | | | | | | | +| 180/200 OK INVITE: SDP | m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP TS A Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP TS A | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | Apply post-test routine | | | +| SIP TS A | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | + +| ISDN to MMTel fixed access use case 4 | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------|------------------------|--------------------------|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--------------------------------|--|--| +| Scenario 5 | Basic call with BC= 3,1 KHz audio – fax with 14,4 kbit/s
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter |
INVITE: SDP m=audio <Port> RTP/AVP 8/0
180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8
| INVITE: SDP | m=audio RTP/AVP 8/0 | 180/200 OK INVITE: SDP | m=audio RTP/AVP 8 | | | | | | | | | | | | | | | +| INVITE: SDP | m=audio RTP/AVP 8/0 | | | | | | | | | | | | | | | | | | | +| 180/200 OK INVITE: SDP | m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | + +| ISDN to MMTel fixed access use case 4 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 6 | Basic call with BC= 3,1 KHz audio – fax with 14,4 kbit/s with ITU-T V.152
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8
a=rtpmap PCMA/8000
a=gpmd; vbd=yes

180/200 OK INVITE: SDP
m=audio RTP/AVP
a=rtpmap PCMA/8000
a=gpmd; vbd=yes | +| Message flow
SIP (TS A)
Core network
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
SIP (TS B)
| | + +| ISDN to MMTel fixed access use case 4 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 7 | Basic call with BC= 3,1 KHz audio – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=image udptl t38

180/200 OK INVITE: SDP
m=image udptl t38 | +| Message flow
SIP (TS A)
Core network
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
SIP (TS B)
| | + +| ISDN to MMTel fixed access use case 4 | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------|---|---|-------------|--|---|----------------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 8 | Basic call with BC= 3,1 kHz – Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP

m=audio RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) | → | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) | → | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| ISDN to MMTel fixed access use case 4 | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------|---|---|-------------|--|---|----------------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 9 | Basic call with BC= 3,1 kHz – Modem ITU-T V.34 (up to 33,6 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly. The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP

m=audio RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) | → | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) | → | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| ISDN to MMTel fixed access use case 4 | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|--------|---|---|---------------|--|--|-----|---| +| Scenario 10 | Called user is UDUB
This scenario represents the case, when the called user is UDUB. the network initiates call clearing to the calling user | | | | | | | | | | | | | +| Options | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE →
← 486 Busy Here
ACK →
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE | → | ← | 486 Busy Here | | | ACK | → | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | +| ← | 486 Busy Here | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | + +| ISDN to MMTel fixed access use case 4 | | | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 11 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(Call-ID A-B) | → | +| | CFU is performed | | +| | ← INVITE(Call-ID B-C) | | +| | 180 Ringing(Call-ID C-B) | → | +| | ← 180 Ringing(Call-ID B-A) | | +| | 200 OK INVITE(Call-ID C-B) | → | +| | ← ACK(Call-ID B-C) | | +| | ← 200 OK INVITE(Call-ID B-A) | | +| | ACK(Call-ID A-B) | → | +| | Communication | | +| | Apply post-test routine | | + +| ISDN to MMTel fixed access use case 4 | | | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 12 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(Call-ID A-B) | → | +| | CFB is performed | | +| | ← INVITE(Call-ID B-C) | | +| | 180 Ringing(Call-ID C-B) | → | +| | ← 180 Ringing(Call-ID B-A) | | +| | 200 OK INVITE(Call-ID C-B) | → | +| | ← ACK(Call-ID B-C) | | +| | ← 200 OK INVITE(Call-ID B-A) | | +| | ACK(Call-ID A-B) | → | +| | Communication | | +| | Apply post-test routine | | + +| ISDN to MMTel fixed access use case 4 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 13 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow | | +| SIP (TS A) Core network SIP (TS B) | | +|

→ INVITE(Call-ID A-B)

← 180 Ringing(Call-ID B-A)

CFNR is performed

← INVITE(Call-ID B-C)

→ 180 Ringing(Call-ID C-B)

← 180 Ringing(Call-ID B-A)

→ 200 OK INVITE(Call-ID C-B)

← ACK(Call-ID B-C)

← 200 OK INVITE(Call-ID B-A)

→ ACK(Call-ID A-B)

Communication

Apply post-test routine

| | +| ISDN to MMTel fixed access use case 4 | | +| Scenario 14 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.
Ensure that the recall from user A to user B is successful. The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow | | +| SIP (TS A) Core network SIP (TS B) | | +|

A CCBS request was already successful

← NOTIFY

→ 200 OK NOTIFY

→ INVITE

← 180 Ringing

← NOTIFY

→ 200 OK NOTIFY

← 200 OK INVITE

→ ACK

Apply post-test routine

| | + +| ISDN to MMTel fixed access use case 4 | | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 15 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful.
The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| A CCNR request was already successful | | | +| | ← NOTIFY | | +| | 200 OK NOTIFY | → | +| | INVITE | → | +| | ← 180 Ringing | | +| | ← NOTIFY | | +| | 200 OK NOTIFY | → | +| | ← 200 OK INVITE | | +| | ACK | → | +| Apply post-test routine | | | + +#### 8.3.2 MMTel fixed access to ISDN use case 5 + +| MMTel fixed access to ISDN use case 5 | | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 1 | Basic call. The call is released from the calling user
This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE | → | +| | ← 100 Trying | | +| | ← 180 Ringing | | +| | ← 200 OK INVITE | | +| | ACK | → | +| | Communication | | +| | BYE | → | +| | ← 200 OK BYE | | + +| MMTel fixed access to ISDN use case 5 | | | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Basic call The call is released from the called user
This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK → | | +| | Communication | | +| | BYE ← | | +| → | 200 OK BYE | | + +| MMTel fixed access to ISDN use case 5 | | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call with BC= 3,1 KHz audio – fax with 33,6 kbit/s
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8/0
180/200 OK INVITE: SDP
m=audio RTP/AVP 8 | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE (SDP2) | | +| | ACK → | | +| | Apply post-test routine | | + +| MMTel fixed access to ISDN use case 5 | | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | Basic call with BC= 3,1 KHz audio – fax with 14,4 kbit/s
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8/0
180/200 OK INVITE: SDP
m=audio RTP/AVP 8 | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE (SDP2) | | +| | ACK → | | +| | Apply post-test routine | | + +| MMTel fixed access to ISDN use case 5 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 5 | Basic call with BC= 3,1 KHz audio – fax with 14,4 kbit/s with ITU-T V.152
This scenario represents the case when in the active call state (N10) the fax transfer is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8
a=rtpmap PCMA/8000
a=gpmd; vbd=yes

180/200 OK INVITE: SDP
m=audio RTP/AVP
a=rtpmap PCMA/8000
a=gpmd; vbd=yes | +| Message flow
SIP (TS A)
Core network
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
SIP (TS B)
| | + +| MMTel fixed access to ISDN use case 5 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 6 | Basic call with BC= 3,1 KHz audio – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=image udptl t38

180/200 OK INVITE: SDP
m=image udptl t38 | +| Message flow
SIP (TS A)
Core network
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
SIP (TS B)
| | + +| MMTel fixed access to ISDN use case 5 | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 7 | Basic call with BC= 3,1 kHz – Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s, 14,4 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly the call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8/0

180/200 OK INVITE: SDP
m=audio RTP/AVP 8 | + +| Message flow | | | +|--------------------------------|----------------------|-------------------| +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) | → | +| ← | 180 Ringing | | +| ← | 200 OK INVITE (SDP2) | | +| | ACK | → | +| Apply post-test routine | | | + +| MMTel fixed access to ISDN use case 5 | | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 8 | Basic call with BC= 3,1 kHz – Modem ITU-T V.34 (up to 33,6 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly. The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP

m=audio RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio RTP/AVP 8 | +| Message flow | | +| SIP (TS A) | Core network | +| | INVITE (SDP1) | +| ← | 180 Ringing | +| ← | 200 OK INVITE (SDP2) | +| | ACK | +| Apply post-test routine | | + +| MMTel fixed access to ISDN use case 5 | | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 9 | Called user is UDUB
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | +| Options | | +| Message flow | | +| SIP (TS A) | Core network | +| | INVITE | +| ← | 486 Busy Here | +| | ACK | + +| MMTel fixed access to ISDN use case 5 | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 10 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow | | +| SIP (TS A) | Core network | +| | INVITE(Call-ID A-B) | +| | CFU is performed | +| ← | INVITE(Call-ID B-C) | +| ← | 180 Ringing(Call-ID C-B) | +| ← | 180 Ringing(Call-ID B-A) | +| ← | 200 OK INVITE(Call-ID C-B) | +| ← | ACK(Call-ID B-C) | +| ← | 200 OK INVITE(Call-ID B-A) | +| | ACK(Call-ID A-B) | +| Communication | | +| Apply post-test routine | | + +| MMTel fixed access to ISDN use case 5 | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--|---|--|--|---|--|--|---|--|--|---|--|--|---| +| Scenario 11 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network
INVITE(Call-ID A-B)
CFB is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine 		SIP (TS B)
→
→
→
→
→
| | SIP (TS A) | Core network
INVITE(Call-ID A-B)
CFB is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | → | | | → | | | → | | | → | | | → | +| SIP (TS A) | Core network
INVITE(Call-ID A-B)
CFB is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to ISDN use case 5 | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--|---|--|--|---|--|--|---|--|--|---|--|--|---| +| Scenario 12 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network
INVITE(Call-ID A-B)
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine 		SIP (TS B)
→
→
→
→
→
| | SIP (TS A) | Core network
INVITE(Call-ID A-B)
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | → | | | → | | | → | | | → | | | → | +| SIP (TS A) | Core network
INVITE(Call-ID A-B)
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | +| | | → | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to ISDN use case 5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|------------------------------------------------------|--|---|--------|--|--|---------------|---|--|------------|---|---|-------------|--|---|------------|--|--|---------------|---|---|-------------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 13 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS or CCNR request was already successful
← NOTIFY
200 OK NOTIFY →

INVITE		 →
← 180 Ringing
←
NOTIFY
200 OK NOTIFY →
←
200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS or CCNR request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY | → | |
INVITE | → | ← | 180 Ringing | | ← |
NOTIFY | | | 200 OK NOTIFY | → | ← |
200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS or CCNR request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |
INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← |
NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← |
200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to ISDN use case 5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|------------------------------------------------------|--|---|--------|--|--|---------------|---|--|------------|---|---|-------------|--|---|------------|--|--|---------------|---|---|-------------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 14 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.
Ensure that the recall from user A to user B is successful.
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS or CCNR request was already successful
← NOTIFY
200 OK NOTIFY →

INVITE		 →
← 180 Ringing
←
NOTIFY
200 OK NOTIFY →
←
200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS or CCNR request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY | → | |
INVITE | → | ← | 180 Ringing | | ← |
NOTIFY | | | 200 OK NOTIFY | → | ← |
200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS or CCNR request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |
INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← |
NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← |
200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 8.3.3 MMTel fixed access to PSTN use case 6 + +| MMTel fixed access to PSTN use case 6 | | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 1 | Basic call. The call is released from the called user
This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| | ← 100 Trying | | +| | ← 180 Ringing | | +| | ← 200 OK INVITE | | +| | ACK → | | +| | Communication | | +| | ← BYE | | +| | 200 OK BYE → | | + +| MMTel fixed access to PSTN use case 6 | | | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Basic call. The call is released from the calling user
This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| | ← 100 Trying | | +| | ← 180 Ringing | | +| | ← 200 OK INVITE | | +| | ACK → | | +| | Communication | | +| | ← BYE | | +| | 200 OK BYE → | | + +| MMTel fixed access to PSTN use case 6 | | | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call with fax with 33,6 kBit/s (Super G3 fax)
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are deactivated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP

m=audio <Port> RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio <Port> RTP/AVP 8

| | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| | ← 180 Ringing | | +| | ← 200 OK INVITE (SDP2) | | +| | ACK → | | +| | Apply post-test routine | | + +| MMTel fixed access to PSTN use case 6 | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--------------------------------|--|--| +| Scenario 4 | Basic call with fax with 14,4 kBit/s
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly. The echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8/0
180/200 OK INVITE: SDP
m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to PSTN use case 6 | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--------------------------------|--|--| +| Scenario 5 | Basic call – fax with 14,4 kbit/s with ITU-T V.152
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8
a=rtpmap PCMA/8000
a=gpmd; vbd=yes
180/200 OK INVITE: SDP
m=audio RTP/AVP
a=rtpmap PCMA/8000
a=gpmd; vbd=yes | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to PSTN use case 6 | | +|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 6 | Basic call with BC= 3,1 kHz – Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8/0
180/200 OK INVITE: SDP
m=audio RTP/AVP 8 | + +| Message flow | | | +|--------------------------------|----------------------|-------------------| +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) | → | +| ← | 180 Ringing | | +| ← | 200 OK INVITE (SDP2) | | +| | ACK | → | +| Apply post-test routine | | | + +| MMTel fixed access to PSTN use case 6 | | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 7 | Basic call with BC= 3,1 kHz – Modem ITU-T V.34 (up to 33,6 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly the call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8/0
180/200 OK INVITE: SDP
m=audio RTP/AVP 8 | +| Message flow | | +| SIP (TS A) | Core network | +| | INVITE (SDP1) | +| ← | 180 Ringing | +| ← | 200 OK INVITE (SDP2) | +| | ACK | +| Apply post-test routine | | + +| MMTel fixed access to PSTN use case 6 | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 8 | Basic call – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state (N10) the fax transfer is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| SIP parameter | INVITE: SDP
m=image udptl t38
180/200 OK INVITE: SDP
m=image udptl t38 | +| Message flow | | +| SIP (TS A) | Core network | +| | INVITE (SDP1) | +| ← | 180 Ringing | +| ← | 200 OK INVITE (SDP2) | +| | ACK | +| Apply post-test routine | | + +| MMTel fixed access to PSTN use case 6 | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 9 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | +| Options | | +| Message flow | | +| SIP (TS A) | Core network | +| | INVITE | +| ← | 486 Busy Here | +| | ACK | + +| MMTel fixed access to PSTN use case 6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 10 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
CFU is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | → | | CFU is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | → | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | → | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | → | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFU is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to PSTN use case 6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 11 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
CFB is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | → | | CFB is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | → | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | → | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | → | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFB is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to PSTN use case 6 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 12 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
core network
SIP (TS B)

Image: Sequence diagram for Scenario 12 (CFNR). SIP (TS A) sends INVITE(Call-ID A-B) to core network. core network sends 180 Ringing(Call-ID B-A) to SIP (TS A). core network performs CFNR and sends INVITE(Call-ID B-C) to core network. core network sends 180 Ringing(Call-ID C-B) to core network. core network sends 180 Ringing(Call-ID B-A) to SIP (TS A). core network sends 200 OK INVITE(Call-ID C-B) to core network. core network sends ACK(Call-ID B-C) to core network. core network sends 200 OK INVITE(Call-ID B-A) to SIP (TS A). SIP (TS B) receives ACK(Call-ID A-B). Communication starts. Apply post-test routine.

 sequenceDiagram     participant SIP_A as SIP (TS A)     participant CN as core network     participant SIP_B as SIP (TS B)     Note right of CN: CFNR is performed     SIP_A->>CN: INVITE(Call-ID A-B)     CN-->>SIP_A: 180 Ringing(Call-ID B-A)     CN->>CN: INVITE(Call-ID B-C)     CN-->>CN: 180 Ringing(Call-ID C-B)     CN-->>SIP_A: 180 Ringing(Call-ID B-A)     CN->>CN: 200 OK INVITE(Call-ID C-B)     CN-->>CN: ACK(Call-ID B-C)     CN-->>SIP_A: 200 OK INVITE(Call-ID B-A)     SIP_B->>SIP_A: ACK(Call-ID A-B)     Note right of CN: Communication     Note right of CN: Apply post-test routine
| | + +| MMTel fixed access to PSTN use case 6 | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 13 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.
Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)

Image: Sequence diagram for Scenario 13 (CCBS). A CCBS request was already successful. SIP (TS A) receives NOTIFY from core network. core network sends 200 OK NOTIFY to SIP (TS A). core network sends INVITE to core network. core network sends 180 Ringing to SIP (TS A). core network sends NOTIFY to core network. core network sends 200 OK NOTIFY to core network. core network sends 200 OK INVITE to core network. core network sends ACK to core network. Apply post-test routine.

 sequenceDiagram     participant SIP_A as SIP (TS A)     participant CN as Core network     participant SIP_B as SIP (TS B)     Note right of CN: A CCBS request was already successful     CN-->>SIP_A: NOTIFY     SIP_A->>CN: 200 OK NOTIFY     CN->>CN: INVITE     CN-->>SIP_A: 180 Ringing     CN->>CN: NOTIFY     CN-->>CN: 200 OK NOTIFY     CN->>CN: 200 OK INVITE     CN-->>CN: ACK     Note right of CN: Apply post-test routine
| | + +| MMTel fixed access to PSTN use case 6 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 14 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.
Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
A CCNR request was already successful

Image: Sequence diagram for MMTel fixed access to PSTN use case 6. The diagram shows the message flow between SIP (TS A) and SIP (TS B) via a Core network. The sequence starts with a NOTIFY from Core network to SIP (TS A), followed by a 200 OK NOTIFY from SIP (TS B) to Core network. Then an INVITE from SIP (TS B) to Core network, a 180 Ringing from Core network to SIP (TS A), a NOTIFY from Core network to SIP (TS A), a 200 OK NOTIFY from SIP (TS B) to Core network, a 200 OK INVITE from SIP (TS B) to Core network, and an ACK from Core network to SIP (TS B). The sequence ends with 'Apply post-test routine'.

 sequenceDiagram     participant SIP_A as SIP (TS A)     participant CN as Core network     participant SIP_B as SIP (TS B)     Note right of CN: A CCNR request was already successful     CN->>SIP_A: NOTIFY     SIP_B->>CN: 200 OK NOTIFY     SIP_B->>CN: INVITE     CN->>SIP_A: 180 Ringing     CN->>SIP_A: NOTIFY     SIP_B->>CN: 200 OK NOTIFY     SIP_B->>CN: 200 OK INVITE     CN->>SIP_B: ACK     Note right of CN: Apply post-test routine
| | + +#### 8.3.4 PSTN to MMTel fixed access use case 7 + +| PSTN to MMTel fixed access use case 7 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Basic call. The call is released from the calling user
This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)

Image: Sequence diagram for PSTN to MMTel fixed access use case 7. The diagram shows the message flow between SIP (TS A) and SIP (TS B) via a Core network. The sequence starts with an INVITE from SIP (TS B) to Core network, followed by a 100 Trying from Core network to SIP (TS A), a 180 Ringing from Core network to SIP (TS A), a 200 OK INVITE from Core network to SIP (TS A), an ACK from SIP (TS A) to Core network, a Communication from Core network to SIP (TS B), a BYE from Core network to SIP (TS B), and a 200 OK BYE from SIP (TS B) to Core network.

 sequenceDiagram     participant SIP_A as SIP (TS A)     participant CN as Core network     participant SIP_B as SIP (TS B)     SIP_B->>CN: INVITE     CN->>SIP_A: 100 Trying     CN->>SIP_A: 180 Ringing     CN->>SIP_A: 200 OK INVITE     SIP_A->>CN: ACK     CN->>SIP_B: Communication     CN->>SIP_B: BYE     SIP_B->>CN: 200 OK BYE
| | + +| PSTN to MMTel fixed access – use case 7 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 2 | Basic call The call is released from the called user.
This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)

Image: Sequence diagram for PSTN to MMTel fixed access – use case 7. The diagram shows the message flow between SIP (TS A) and SIP (TS B) via a Core network. The sequence starts with an INVITE from SIP (TS B) to Core network, followed by a 100 Trying from Core network to SIP (TS A), a 180 Ringing from Core network to SIP (TS A), a 200 OK INVITE from Core network to SIP (TS A), an ACK from SIP (TS A) to Core network, a Communication from Core network to SIP (TS B), a BYE from SIP (TS B) to Core network, and a 200 OK BYE from Core network to SIP (TS B).

 sequenceDiagram     participant SIP_A as SIP (TS A)     participant CN as Core network     participant SIP_B as SIP (TS B)     SIP_B->>CN: INVITE     CN->>SIP_A: 100 Trying     CN->>SIP_A: 180 Ringing     CN->>SIP_A: 200 OK INVITE     SIP_A->>CN: ACK     CN->>SIP_B: Communication     SIP_B->>CN: BYE     CN->>SIP_B: 200 OK BYE
| | + +| PSTN to MMTel fixed access use case 7 | | | +|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – overlap sending
This scenario represents the case when the call establishment is using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow multiple INVITE method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) | → | +| | INVITE(CSq 2) | → | +| ← | 484 Address Incomplete(CSq 1) | → | +| | ACK | → | +| | INVITE(CSq 3) | → | +| ← | 484 Address Incomplete(CSq 2) | → | +| | ACK | → | +| | ..... | | +| | INVITE(CSq 4) | → | +| ← | 484 Address Incomplete(CSq 3) | → | +| | ACK | → | +| ← | 180 Ringing(CSq 4) | | +| Apply post-test routine | | | +| Message flow Overlap sending, the in-dialogue method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) 1 | → | +| ← | 484 Address Incomplete(CSq 1) | → | +| | ACK | → | +| | INVITE(CSq 2) 2 | → | +| ← | 183 Session Progress(CSq 2) | → | +| | PRACK | → | +| ← | 200 OK PRACK | | +| | INFO | → | +| ← | 200 OK INFO | | +| | ..... | | +| | INFO | → | +| ← | 200 OK INFO | | +| ← | 180 Ringing(CSq 2) | | +| Apply post-test routine | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 4 | Basic call with fax with 33,6 kBit/s (Super G3 fax)
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are deactivated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
180/200 OK INVITE: SDP
m=audio RTP/AVP 8/0
m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 5 | Basic call with fax with 14,4 kBit/s
This scenario represents the case when in the active call state (N10) the fax transfer is performed correctly. The echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
180/200 OK INVITE: SDP
m=audio RTP/AVP 8/0
m=audio RTP/AVP 8 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 6 | Basic call – fax with 14,4 kbit/s with ITU-T V.152 codec
This scenario represents the case when in the active call state (N10) the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
m=audio RTP/AVP 8
a=rtpmap PCMA/8000
a=gpmd; vbd=yes

180/200 OK INVITE: SDP
m=audio RTP/AVP
a=rtpmap PCMA/8000
a=gpmd; vbd=yes | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 7 | Basic call – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state the fax transfer is performed correctly
The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP
m=image udptl t38

180/200 OK INVITE: SDP
m=image udptl t38 | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 8 | Basic call with BC= 3,1 kHz – Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP

m=audio <Port> RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio <Port> RTP/AVP 8

| | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------|--|---|-------------|--|---|----------------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 9 | Basic call with BC= 3,1 kHz – Modem ITU-T V.34 (up to 33,6 kbit/s)
This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly. The call is released from the calling user | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | +| SIP parameter | INVITE: SDP

m=audio <Port> RTP/AVP 8/0

180/200 OK INVITE: SDP

m=audio <Port> RTP/AVP 8

| | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE (SDP1) →
← 180 Ringing
← 200 OK INVITE (SDP2)
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE (SDP1) → | | ← | 180 Ringing | | ← | 200 OK INVITE (SDP2) | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | +| | INVITE (SDP1) → | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE (SDP2) | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access – use case 7 | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------|--|---|---------------|--|--|-------|--| +| Scenario 10 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | | | | | | | | | | | | | +| Options | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE →
← 486 Busy Here
ACK →
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE → | | ← | 486 Busy Here | | | ACK → | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | +| | INVITE → | | | | | | | | | | | | | +| ← | 486 Busy Here | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|--|-----------------------|--|--|--------------------------|---|--|----------------------------|--|--|----------------------------|---|--|--------------------|--|--|------------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 11 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters).
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFU is performed
⬅ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
⬅ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
⬅ ACK(Call-ID B-C)
⬅ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFU is performed | | | ⬅ INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | | ⬅ 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | | ⬅ ACK(Call-ID B-C) | | | ⬅ 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFU is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|--|-----------------------|--|--|--------------------------|---|--|----------------------------|--|--|----------------------------|---|--|--------------------|--|--|------------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 12 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFB is performed
⬅ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
⬅ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
⬅ ACK(Call-ID B-C)
⬅ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFB is performed | | | ⬅ INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | | ⬅ 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | | ⬅ ACK(Call-ID B-C) | | | ⬅ 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFB is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|----------------------------|--|--|--------------------------|--|--|-----------------------|--|--|--------------------------|---|--|----------------------------|--|--|----------------------------|---|--|--------------------|--|--|------------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 13 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | → | | ← 180 Ringing(Call-ID B-A) | | | CFNR is performed | | | ← INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | → | | ← 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | → | | ← ACK(Call-ID B-C) | | | ← 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | → | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|----------------------------------------------|--|--|--|----------|--|--|---------------|---|--|--------|---|--|---------------|--|--|----------|--|--|---------------|---|--|-----------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 14 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.
Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS request was already successful
← NOTIFY
200 OK NOTIFY →
INVITE →
← 180 Ringing
← NOTIFY
200 OK NOTIFY →
← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | A CCBS request was already successful | | | | ← NOTIFY | | | 200 OK NOTIFY | → | | INVITE | → | | ← 180 Ringing | | | ← NOTIFY | | | 200 OK NOTIFY | → | | ← 200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| A CCBS request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 7 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 15 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
A CCNR request was already successful
Core network
SIP (TS B) 
       ← NOTIFY       200 OK NOTIFY       →       ← INVITE       180 Ringing       →       ← NOTIFY       200 OK NOTIFY       →       ← 200 OK INVITE       ACK       →       Apply post-test routine
| | + +### 8.4 VoLTE to IMS/PES + +#### 8.4.1 ISDN to VoLTE use case 8 + +| ISDN to VoLTE use case 8 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Basic call with BC= ITC_value – enblock sending
This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B) 
       INVITE       →       ← 100 Trying       ← 180 Ringing       ← 200 OK INVITE       ACK       →       Communication       BYE       →       ← 200 OK BYE
| | +| SIP parameter
PSTN XML BearerCapability
element in the INVITE | 
 INVITE:   Content-Type: application/vnd.etsi.pstn+xml   Content-Disposition: signal;handling=optional  <?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>ITC_value<     BCoctet4       TransferMode>00<       InformationTransferRate>10000<     BCoctet5       Layer1Identification>01<       UserInfoLayer1Protocol>00011<
| + +| ISDN to VoLTE use case 8 | | | +|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Basic call with BC= ITC_value – enblock sending
This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| | ← 100 Trying | | +| | ← 180 Ringing | | +| | ← 200 OK INVITE | | +| | ACK → | | +| | Communication | | +| | ← BYE | | +| | 200 OK BYE → | | +| SIP parameter
PSTN XML BearerCapability
element in the INVITE | INVITE:
Content-Type: application/vnd.etsi.pstn+xml
Content-Disposition: signal;handling=optional


PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>ITC_value<
<        BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011< | | + +**Table 2 – PSTN XML BearerCapability** + +| ITC_value | BC Information transfer capability | XML InformationTransferCapability | +|-----------|------------------------------------|-----------------------------------| +| ITC_VA_1 | Speech | '00000' | +| ITC_VA_2 | 3.1 kHz audio | '10000' | +| ITC_VA_3 | unrestricted digital information | '01000' | + +| ISDN to VoLTE use case 8 | | | +|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – overlap sending with BC= speech
This scenario represents the case when the call establishment is using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow multiple INVITE method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) | → | +| | INVITE(CSq 2) | → | +| ← | 484 Address Incomplete(CSq 1) | → | +| | ACK | → | +| | INVITE(CSq 3) | → | +| ← | 484 Address Incomplete(CSq 2) | → | +| | ACK | → | +| | ..... | | +| | INVITE(CSq 4) | → | +| ← | 484 Address Incomplete(CSq 3) | → | +| | ACK | → | +| ← | 180 Ringing(CSq 4) | | +| Apply post-test routine | | | +| Message flow Overlap sending, the in-Dialogue method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) 1 | → | +| ← | 484 Address Incomplete(CSq 1) | → | +| | ACK | → | +| | INVITE(CSq 2) 2 | → | +| ← | 183 Session Progress(CSq 2) | → | +| | PRACK | → | +| ← | 200 OK PRACK | | +| | INFO | → | +| ← | 200 OK INFO | | +| | ..... | | +| | INFO | → | +| ← | 200 OK INFO | | +| ← | 180 Ringing(CSq 2) | | +| Apply post-test routine | | | + +| ISDN to VoLTE use case 8 | | | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | Called user is UDUB
This scenario represents the case, when the called user is UDUB. The network initiates call clearing to the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE | → | +| ← | 486 Busy Here | → | +| | ACK | → | + +| ISDN to VoLTE use case 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 11 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFU is performed
⬅ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
⬅ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
⬅ ACK(Call-ID B-C)
⬅ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFU is performed | | ⬅ | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ⬅ | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ⬅ | ACK(Call-ID B-C) | | ⬅ | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFU is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| ISDN to VoLTE use case 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 5 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFB is performed
⬅ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
⬅ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
⬅ ACK(Call-ID B-C)
⬅ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFB is performed | | ⬅ | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ⬅ | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ⬅ | ACK(Call-ID B-C) | | ⬅ | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFB is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| ISDN to VoLTE use case 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|---------------------|----------------------------|--|---------------------|---|---|--------------------------|--|--|--------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|----------------------|--|--|--------------------------------|--|--| +| Scenario 6 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (Test system B)
INVITE(Call-ID A-B) →
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (Test system B) | | INVITE(Call-ID A-B) | → | ← | 180 Ringing(Call-ID B-A) | | | CFNR is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | → | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | → | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | → | Communication | | | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (Test system B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| ISDN to VoLTE use case 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|----------------------------------------------|--|--|---|--------|--|--|---------------|---|--|------|--|--|--------|---|---|-------------|--|--|------|--|---|--------|--|--|---------------|---|--|------|--|---|---------------|--|--|-----|---|--------------------------------|--|--| +| Scenario 7 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.
Ensure that the recall from user A to user B is successful. The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS request was already successful
← NOTIFY
200 OK NOTIFY →

INVITE →
← 180 Ringing

← NOTIFY
200 OK NOTIFY →

← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | A CCBS request was already successful | | | ← | NOTIFY | | | 200 OK NOTIFY | → | |
| | | INVITE | → | ← | 180 Ringing | | |
| | ← | NOTIFY | | | 200 OK NOTIFY | → | |
| | ← | 200 OK INVITE | | | ACK | → | Apply post-test routine | | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| A CCBS request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| ISDN to VoLTE use case 8 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 8 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.
Ensure that the recall from user A to user B is successful.
The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
A CCNR request was already successful 
       ← NOTIFY       200 OK NOTIFY →       INVITE →       ← 180 Ringing       NOTIFY →       200 OK NOTIFY →       ← 200 OK INVITE       ACK →       Apply post-test routine
| | + +#### 8.4.2 VoLTE to ISDN use case 9 + +| VoLTE to ISDN use case 9 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Basic call. The call is released from the calling user
This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B) 
       INVITE →       ← 100 Trying       ← 180 Ringing       ← 200 OK INVITE       ACK →       Communication       BYE →       ← 200 OK BYE
| | + +| VoLTE to ISDN use case 9 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 2 | Basic call. The call is released from the called user
This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B) 
       INVITE →       ← 100 Trying       ← 180 Ringing       ← 200 OK INVITE       ACK →       Communication       BYE ←       → 200 OK BYE
| | + +| VoLTE to ISDN use case 8 | | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Called user is UDUB
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| | ← 486 Busy Here | | +| | ACK → | | + +| VoLTE to ISDN use case 9 | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(Call-ID A-B) → | | +| | CFU is performed | | +| | ← INVITE(Call-ID B-C) | | +| | 180 Ringing(Call-ID C-B) → | | +| | ← 180 Ringing(Call-ID B-A) | | +| | 200 OK INVITE(Call-ID C-B) → | | +| | ← ACK(Call-ID B-C) | | +| | 200 OK INVITE(Call-ID B-A) → | | +| | ← ACK(Call-ID A-B) | | +| | Communication | | +| | Apply post-test routine | | + +| VoLTE to ISDN use case 9 | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 5 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(Call-ID A-B) → | | +| | CFB is performed | | +| | ← INVITE(Call-ID B-C) | | +| | 180 Ringing(Call-ID C-B) → | | +| | ← 180 Ringing(Call-ID B-A) | | +| | 200 OK INVITE(Call-ID C-B) → | | +| | ← ACK(Call-ID B-C) | | +| | 200 OK INVITE(Call-ID B-A) → | | +| | ← ACK(Call-ID A-B) | | +| | Communication | | +| | Apply post-test routine | | + +| VoLTE to ISDN use case 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-------------------------|--|--|------------------------------|--|--|--------------------------|--|--|-------------------------|--|--|------------------------------|--|--|------------------------------|--|--|--------------------------------|--|--|----------------------|--|--|--------------------------------|--|--|----------------------|--|--|----------------------|--|--|--------------------------------|--| +| Scenario 6 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
← INVITE(Call-ID A-B) →
← 180 Ringing(Call-ID B-A) →
CFNR is performed
← INVITE(Call-ID B-C) →
← 180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A) →
← 200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C) →
← 200 OK INVITE(Call-ID B-A) →
← ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | ← INVITE(Call-ID A-B) → | | | ← 180 Ringing(Call-ID B-A) → | | | CFNR is performed | | | ← INVITE(Call-ID B-C) → | | | ← 180 Ringing(Call-ID C-B) → | | | ← 180 Ringing(Call-ID B-A) → | | | ← 200 OK INVITE(Call-ID C-B) → | | | ← ACK(Call-ID B-C) → | | | ← 200 OK INVITE(Call-ID B-A) → | | | ← ACK(Call-ID A-B) → | | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← INVITE(Call-ID A-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID B-A) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← INVITE(Call-ID B-C) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID C-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID B-A) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE(Call-ID C-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← ACK(Call-ID B-C) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE(Call-ID B-A) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← ACK(Call-ID A-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| VoLTE to ISDN use case 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------------------------------------------|--|--|------------|--|--|-------------------|--|--|------------|--|--|-----------------|--|--|------------|--|--|-------------------|--|--|-------------------|--|--|---------|--|--|--------------------------------|--| +| Scenario 7 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.
Ensure that the recall from user A to user B is successful. The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS request was already successful
← NOTIFY →
← 200 OK NOTIFY →
← INVITE →
← 180 Ringing →
← NOTIFY →
← 200 OK NOTIFY →
← 200 OK INVITE →
← ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS request was already successful | | | ← NOTIFY → | | | ← 200 OK NOTIFY → | | | ← INVITE → | | | ← 180 Ringing → | | | ← NOTIFY → | | | ← 200 OK NOTIFY → | | | ← 200 OK INVITE → | | | ← ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← NOTIFY → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK NOTIFY → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← INVITE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← NOTIFY → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK NOTIFY → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← ACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| VoLTE to ISDN use case 9 | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 8 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful.
The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
A CCNR request was already successful
←
NOTIFY
200 OK NOTIFY
→

INVITE
→
←
180 Ringing

←
NOTIFY
200 OK NOTIFY
→

←
200 OK INVITE
ACK
→
Apply post-test routine
| | + +#### 8.4.3 VoLTE to PSTN use case 10 + +| VoLTE to PSTN use case 10 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Basic call. The call is released from the called user.
This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
INVITE
→
←
100 Trying
←
180 Ringing
←
200 OK INVITE
ACK
→
Communication
←
BYE
200 OK BYE
→
| | + +| VoLTE to PSTN use case 10 | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 2 | Basic call. The call is released from the calling user
This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
INVITE
→
←
100 Trying
←
180 Ringing
←
200 OK INVITE
ACK
→
Communication
BYE
→
←
200 OK BYE
| | + +Rec. ITU-T Q.3932.2 (06/2015) + +53 + +| VoLTE to PSTN use case 10 | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE → | | +| | ← 486 Busy Here | | +| | ACK → | | + +| VoLTE to PSTN use case 10 | | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | core network | SIP (TS B) | +| | INVITE(Call-ID A-B) → | | +| | CFU is performed | | +| | ← INVITE(Call-ID B-C) | | +| | 180 Ringing(Call-ID C-B) → | | +| | ← 180 Ringing(Call-ID B-A) | | +| | 200 OK INVITE(Call-ID C-B) → | | +| | ← ACK(Call-ID B-C) | | +| | ← 200 OK INVITE(Call-ID B-A) | | +| | ACK(Call-ID A-B) → | | +| | Communication | | +| | Apply post-test routine | | + +| VoLTE to PSTN use case 10 | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 5 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(Call-ID A-B) → | | +| | CFB is performed | | +| | ← INVITE(Call-ID B-C) | | +| | 180 Ringing(Call-ID C-B) → | | +| | ← 180 Ringing(Call-ID B-A) | | +| | 200 OK INVITE(Call-ID C-B) → | | +| | ← ACK(Call-ID B-C) | | +| | ← 200 OK INVITE(Call-ID B-A) | | +| | ACK(Call-ID A-B) → | | +| | Communication | | +| | Apply post-test routine | | + +| VoLTE to PSTN use case 10 | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| Scenario 6 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | +| Message flow
SIP (TS A) Core network
INVITE(Call-ID A-B)
180 Ringing(Call-ID B-A)
CFNR is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine 		SIP (TS B)
→ ← ← → ← → ← ← →
| | SIP (TS A) | Core network
INVITE(Call-ID A-B)
180 Ringing(Call-ID B-A)
CFNR is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) |
→ ← ← → ← → ← ← →
| | | +| SIP (TS A) | Core network
INVITE(Call-ID A-B)
180 Ringing(Call-ID B-A)
CFNR is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | | | | +|
→ ← ← → ← → ← ← →
| | | | | | | | + +| VoLTE to PSTN use case 10 | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| Scenario 7 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.
Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | +| Message flow
SIP (TS A) Core network
A CCBS request was already successful
NOTIFY
200 OK NOTIFY

INVITE
180 Ringing

NOTIFY
200 OK NOTIFY

200 OK INVITE
ACK
Apply post-test routine 		SIP (TS B)
← → → ← ← → ← →
| | SIP (TS A) | Core network
A CCBS request was already successful
NOTIFY
200 OK NOTIFY

INVITE
180 Ringing

NOTIFY
200 OK NOTIFY

200 OK INVITE
ACK
Apply post-test routine | SIP (TS B) |
← → → ← ← → ← →
| | | +| SIP (TS A) | Core network
A CCBS request was already successful
NOTIFY
200 OK NOTIFY

INVITE
180 Ringing

NOTIFY
200 OK NOTIFY

200 OK INVITE
ACK
Apply post-test routine | SIP (TS B) | | | | | | +|
← → → ← ← → ← →
| | | | | | | | + +| VoLTE to PSTN use case 10 | | | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 8 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.
Ensure that the recall from user A to user B is successful. The call is released from the calling user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | A CCNR request was already successful | | +| ← | NOTIFY | | +| | 200 OK NOTIFY | → | +| ← | INVITE | | +| | 180 Ringing | → | +| ← | NOTIFY | | +| | 200 OK NOTIFY | → | +| ← | 200 OK INVITE | | +| | ACK | → | +| Apply post-test routine | | | + +#### 8.4.4 PSTN to VoLTE use case 11 + +| PSTN to VoLTE use case 11 | | | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 1 | Basic call. The call is released from the calling user
This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE | → | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK | → | +| | Communication | | +| | BYE | → | +| ← | 200 OK BYE | | + +| PSTN to VoLTE use case 11 | | | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Basic call. The call is released from the called user.
This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE | → | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK | → | +| | Communication | | +| ← | BYE | | +| | 200 OK BYE | → | + +| PSTN to VoLTE use case 11 | | | +|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – overlap sending
This scenario represents the case when the call establishment is using overlap sending. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow Multiple INVITE method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) | → | +| | INVITE(CSq 2) | → | +| ← | 484 Address Incomplete(CSq 1) | | +| | ACK | → | +| | INVITE(CSq 3) | → | +| ← | 484 Address Incomplete(CSq 2) | | +| | ACK | → | +| | ..... | | +| | INVITE(CSq 4) | → | +| ← | 484 Address Incomplete(CSq 3) | | +| | ACK | → | +| ← | 180 Ringing(CSq 4) | | +| Apply post-test routine | | | +| Message flow Overlap sending, the in-dialogue method is used | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE(CSq 1) 1 | → | +| ← | 484 Address Incomplete(CSq 1) | | +| | ACK | → | +| | INVITE(CSq 2) 2 | → | +| ← | 183 Session Progress(CSq 2) | | +| | PRACK | → | +| ← | 200 OK PRACK | | +| | INFO | → | +| ← | 200 OK INFO | | +| | ..... | | +| | INFO | → | +| ← | 200 OK INFO | | +| ← | 180 Ringing(CSq 2) | | +| Apply post-test routine | | | + +| PSTN to VoLTE use case 11 | | | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE | → | +| ← | 486 Busy Here | | +| | ACK | → | + +| PSTN to VoLTE use case 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 5 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters).
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFU is performed
➔ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
➔ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
➔ ACK(Call-ID B-C)
➔ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFU is performed | | ➔ | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ➔ | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ➔ | ACK(Call-ID B-C) | | ➔ | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFU is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to VoLTE use case 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|--|-------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 6 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
CFB is performed
➔ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
➔ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
➔ ACK(Call-ID B-C)
➔ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | | CFB is performed | | ➔ | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ➔ | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ➔ | ACK(Call-ID B-C) | | ➔ | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFB is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ➔ | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to VoLTE use case 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|---|--------------------------|--|--|--------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 7 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | → | ← | 180 Ringing(Call-ID B-A) | | | CFNR is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | → | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | → | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | → | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to MMTel fixed access use case 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------------------------------------------|--|---|--------|--|--|---------------|---|--|--------|---|---|-------------|--|--|--------|---|---|---------------|--|---|---------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 8 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request
Ensure that the recall from user A to user B is successful. The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS request was already successful
← NOTIFY
200 OK NOTIFY →
INVITE →
← 180 Ringing
NOTIFY →
← 200 OK NOTIFY
← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY | → | | INVITE | → | ← | 180 Ringing | | | NOTIFY | → | ← | 200 OK NOTIFY | | ← | 200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| PSTN to VoLTE use case 11 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 9 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCNR request was already successful 
 sequenceDiagram     participant TSA as SIP (TS A)     participant CN as Core network     participant TSB as SIP (TS B)     Note over TSA, TSB: A CCNR request was already successful     CN->>TSA: NOTIFY     TSB->>CN: 200 OK NOTIFY     CN->>TSB: INVITE     TSA->>CN: 180 Ringing     CN->>TSA: NOTIFY     TSB->>CN: 200 OK NOTIFY     CN->>TSA: 200 OK INVITE     TSA->>CN: ACK     Note over TSA, TSB: Apply post-test routine
Apply post-test routine
| | + +### 8.5 VoLTE to VoLTE use case 12 + +| VoLTE to VoLTE use case 12 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow a) Successful call – resource reservation on both sides
SIP (TS A) Core network SIP (TS B) 
 sequenceDiagram     participant TSA as SIP (TS A)     participant CN as Core network     participant TSB as SIP (TS B)     TSA->>CN: INVITE (SDP1)     CN->>TSB: INVITE (SDP1)     CN->>TSA: 100 Trying     CN->>TSA: 183 Session Progress     TSA->>CN: PRACK     CN->>TSB: PRACK     CN->>TSA: 200 OK PRACK     TSA->>CN: UPDATE     CN->>TSB: UPDATE     CN->>TSA: 200 OK UPDATE     CN->>TSA: 180 Ringing     CN->>TSA: 200 OK     TSA->>CN: ACK     CN->>TSB: ACK     TSA->>CN: BYE     CN->>TSB: BYE     CN->>TSA: 200 OK BYE
Apply post-test routine
| | +| Message flow: b), c)
SIP (TS A) Core network SIP (TS B) 
 sequenceDiagram     participant TSA as SIP (TS A)     participant CN as Core network     participant TSB as SIP (TS B)     TSA->>CN: INVITE (SDP1)     CN->>TSB: INVITE (SDP1)     CN->>TSA: 100 Trying     CN->>TSA: 180 Ringing     CN->>TSA: 200 OK INVITE     TSA->>CN: ACK     CN->>TSB: ACK     TSA->>CN: BYE     CN->>TSB: BYE     CN->>TSA: 200 OK BYE
Apply post-test routine
| | + +| VoLTE to VoLTE use case 12 | | | +|-----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Successful call – This scenario represents the case when the call establishment is performed correctly Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow a) Successful call – resource reservation on both sides | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE (SDP1) → | | +| | ← 100 Trying → | | +| | ← 183 Session Progress → | | +| | ← PRACK → | | +| | ← 200 OK PRACK → | | +| | ← UPDATE → | | +| | ← 200 OK UPDATE → | | +| | ← 180 Ringing → | | +| | ← 200 OK → | | +| | ← ACK → | | +| | ← BYE → | | +| | ← 200 OK BYE → | | +| | Apply post-test routine | | +| Message flow: b), c) | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE (SDP1) → | | +| | ← 100 Trying → | | +| | ← 180 Ringing → | | +| | ← 200 OK INVITE → | | +| | ← ACK → | | +| | ← BYE → | | +| | ← 200 OK BYE → | | +| | Apply post-test routine | | + +| VoLTE to VoLTE use case 12 | | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP
m=image udptl t38

180/200 OK INVITE: SDP
m=image udptl t38 | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE (SDP1) → | | +| | ← 180 Ringing → | | +| | ← 200 OK INVITE (SDP2) → | | +| | ← ACK → | | +| | Apply post-test routine | | + +| VoLTE to VoLTE use case 12 | | | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiate call clearing to the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE → | | +| | ← 486 Busy Here → | | +| | ← ACK → | | + +| VoLTE to VoLTE use case 12 | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| Scenario 5 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | +| Message flow
SIP (TS A) Core network
INVITE(Call-ID A-B)
CFU is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine 		SIP (TS B)
➔
←
➔
←
➔
←
←
➔
| | SIP (TS A) | Core network
INVITE(Call-ID A-B)
CFU is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) |
➔
←
➔
←
➔
←
←
➔
| | | +| SIP (TS A) | Core network
INVITE(Call-ID A-B)
CFU is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | | | | +|
➔
←
➔
←
➔
←
←
➔
| | | | | | | | + +| VoLTE to VoLTE use case 12 | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| Scenario 6 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | +| Message flow
SIP (TS A) Core network
INVITE(Call-ID A-B)
CFB is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine 		SIP (TS B)
➔
←
➔
←
➔
←
←
➔
| | SIP (TS A) | Core network
INVITE(Call-ID A-B)
CFB is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) |
➔
←
➔
←
➔
←
←
➔
| | | +| SIP (TS A) | Core network
INVITE(Call-ID A-B)
CFB is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine | SIP (TS B) | | | | | | +|
➔
←
➔
←
➔
←
←
➔
| | | | | | | | + +| VoLTE to VoLTE use case 12 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|---|--------------------------|--|--|--------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 7 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) ➔
⬅ 180 Ringing(Call-ID B-A)
CFNR is performed
⬅ INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) ➔
⬅ 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) ➔
⬅ ACK(Call-ID B-C)
⬅ 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) ➔
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | ➔ | ⬅ | 180 Ringing(Call-ID B-A) | | | CFNR is performed | | ⬅ | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | ➔ | ⬅ | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | ➔ | ⬅ | ACK(Call-ID B-C) | | ⬅ | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | ➔ | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| VoLTE to VoLTE use case 12 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|------------------------------------------------------|--|---|--------|--|--|---------------|---|--|--------|---|---|-------------|--|---|--------|--|--|---------------|---|---|---------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 8 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request
Ensure that the recall from user A to user B is successful
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS or CCNR request was already successful
⬅ NOTIFY
200 OK NOTIFY ➔
INVITE ➔
⬅ 180 Ringing
⬅ NOTIFY
200 OK NOTIFY ➔
⬅ 200 OK INVITE
ACK ➔
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS or CCNR request was already successful | | ⬅ | NOTIFY | | | 200 OK NOTIFY | ➔ | | INVITE | ➔ | ⬅ | 180 Ringing | | ⬅ | NOTIFY | | | 200 OK NOTIFY | ➔ | ⬅ | 200 OK INVITE | | | ACK | ➔ | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS or CCNR request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| VoLTE to VoLTE use case 12 | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 9 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.
Ensure that the recall from user A to user B is successful.
The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)

A CCBS or CCNR request was already successful

← NOTIFY

200 OK NOTIFY →

← INVITE

180 Ringing →

← NOTIFY

200 OK NOTIFY →

← 200 OK INVITE

ACK →

Apply post-test routine

| | + +### 8.6 MMTel fixed access – VoLTE + +#### 8.6.1 VoLTE to MMTel fixed access use case 13 + +| VoLTE to MMTel fixed access use case 13 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow a) Successful call – resource reservation on both sides
SIP (TS A) Core network SIP (TS B)

← INVITE (SDP1) →

← 100 Trying

← 183 Session Progress

PRACK →

← 200 OK PRACK

UPDATE →

← 200 OK UPDATE

← 180 Ringing

← 200 OK

ACK →

BYE →

← 200 OK BYE

Apply post-test routine

| | +| Message flow: b), c)
SIP (TS A) Core network SIP (TS B)

← INVITE (SDP1) →

← 100 Trying

← 180 Ringing

← 200 OK INVITE

ACK →

BYE →

← 200 OK BYE

Apply post-test routine

| | + +| VoLTE to MMTel fixed access use case 13 | | | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow a) Successful call – resource reservation on both sides | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 100 Trying | | +| ← | 183 Session Progress | | +| | PRACK → | | +| ← | 200 OK PRACK | | +| | UPDATE → | | +| ← | 200 OK UPDATE | | +| ← | 180 Ringing | | +| ← | 200 OK | | +| | ACK → | | +| ← | BYE | | +| | 200 OK BYE → | | +| Apply post-test routine | | | +| Message flow: b), c) | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 100 Trying | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE | | +| | ACK → | | +| ← | BYE | | +| | 200 OK BYE → | | +| Apply post-test routine | | | + +| VoLTE to MMTel fixed access use case 13 | | | +|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP
m=image udptl t38

180/200 OK INVITE: SDP
m=image udptl t38 | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | INVITE (SDP1) → | | +| ← | 180 Ringing | | +| ← | 200 OK INVITE (SDP2) | | +| | ACK → | | +| Apply post-test routine | | | + +| VoLTE to MMTel fixed access use case 13 | | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 4 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiates call clearing to the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow | | +| SIP (TS A) | Core network SIP (TS B)
→ INVITE
← 486 Busy Here
→ ACK | + +| VoLTE to MMTel fixed access use case 13 | | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 5 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow | | +| SIP (TS A) | Core network SIP (TS B)
→ INVITE(Call-ID A-B)
CFU is performed
← INVITE(Call-ID B-C)
→ 180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
→ 200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
→ ACK(Call-ID A-B)
Communication
Apply post-test routine | + +| VoLTE to MMTel fixed access use case 13 | | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 6 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters).
The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow | | +| SIP (TS A) | Core network SIP (TS B)
→ INVITE(Call-ID A-B)
CFB is performed
← INVITE(Call-ID B-C)
→ 180 Ringing(Call-ID C-B)
← 180 Ringing(Call-ID B-A)
→ 200 OK INVITE(Call-ID C-B)
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
→ ACK(Call-ID A-B)
Communication
Apply post-test routine | + +| VoLTE to MMTel fixed access use case 13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|-----------------------|--|--|----------------------------|--|--|--------------------------|--|--|-----------------------|--|--|----------------------------|--|--|----------------------------|--|--|------------------------------|--|---|------------------|--|---|----------------------------|--|--|--------------------|--|--|----------------------|--|--|--------------------------------|--| +| Scenario 7 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) → | | | ← 180 Ringing(Call-ID B-A) | | | CFNR is performed | | | ← INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) → | | | ← 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) → | | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) → | | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| VoLTE to MMTel fixed access use case 13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------------------------------------------|--|---|--------|--|--|-----------------|--|--|----------|--|---|-------------|--|---|--------|--|--|-----------------|--|---|---------------|--|--|-------|--|--|--------------------------------|--| +| Scenario 8 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCNR request was already successful
← NOTIFY
200 OK NOTIFY →
INVITE →
← 180 Ringing
← NOTIFY
200 OK NOTIFY →
← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCNR request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY → | | | INVITE → | | ← | 180 Ringing | | ← | NOTIFY | | | 200 OK NOTIFY → | | ← | 200 OK INVITE | | | ACK → | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCNR request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| VoLTE to MMTel fixed access use case 13 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 9 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful
The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCNR request was already successful 
 sequenceDiagram     participant TS_A as SIP (TS A)     participant CN as Core network     participant TS_B as SIP (TS B)     Note over CN: A CCNR request was already successful     CN->>TS_A: NOTIFY     TS_A->>CN: 200 OK NOTIFY     CN->>TS_B:      CN->>TS_B: INVITE     TS_A<<-CN: 180 Ringing     CN->>TS_A: NOTIFY     TS_A->>CN: 200 OK NOTIFY     CN->>TS_B:      CN->>TS_A: 200 OK INVITE     TS_A->>CN: ACK     CN->>TS_B:      Note over CN: Apply post-test routine
| | + +#### 8.6.2 MMTel fixed access to VoLTE use case 14 + +| MMTel fixed access to VoLTE use case 13 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 1 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow a) Successful call – resource reservation on both sides
SIP (TS A) Core network SIP (TS B) 
 sequenceDiagram     participant TS_A as SIP (TS A)     participant CN as Core network     participant TS_B as SIP (TS B)     TS_A->>CN: INVITE (SDP1)     CN->>TS_B:      CN-->>TS_A: 100 Trying     CN-->>TS_A: 183 Session Progress     TS_A->>CN: PRACK     CN->>TS_B:      CN-->>TS_A: 200 OK PRACK     CN->>TS_B: UPDATE     TS_A<<--CN: 200 OK UPDATE     CN-->>TS_A: 180 Ringing     CN-->>TS_A: 200 OK     TS_A->>CN: ACK     CN->>TS_B:      TS_A->>CN: BYE     CN->>TS_B:      CN-->>TS_A: 200 OK BYE     Note over CN: Apply post-test routine
| | + + + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Message flow: b), c)
SIP (TS A) Core network SIP (TS B) 
 sequenceDiagram     participant TS_A as SIP (TS A)     participant CN as Core network     participant TS_B as SIP (TS B)     TS_A->>CN: INVITE (SDP1)     CN->>TS_B:      CN-->>TS_A: 100 Trying     CN-->>TS_A: 180 Ringing     CN-->>TS_A: 200 OK INVITE     TS_A->>CN: ACK     CN->>TS_B:      TS_A->>CN: BYE     CN->>TS_B:      CN-->>TS_A: 200 OK BYE     Note over CN: Apply post-test routine
| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| MMTel fixed access to VoLTE use case 14 | | | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 2 | Successful call – This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| Message flow a) Successful call – resource reservation on both sides | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE (SDP1) → | | +| | ← 100 Trying → | | +| | ← 183 Session Progress → | | +| | ← PRACK → | | +| | ← 200 OK PRACK → | | +| | ← UPDATE → | | +| | ← 200 OK UPDATE → | | +| | ← 180 Ringing → | | +| | ← 200 OK → | | +| | ← ACK → | | +| | ← BYE → | | +| | ← 200 OK BYE → | | +| | Apply post-test routine | | +| Message flow: b), c) | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE (SDP1) → | | +| | ← 100 Trying → | | +| | ← 180 Ringing → | | +| | ← 200 OK INVITE → | | +| | ← ACK → | | +| | ← BYE → | | +| | ← 200 OK BYE → | | +| | Apply post-test routine | | + +| MMTel fixed access to VoLTE use case 14 | | | +|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 3 | Basic call – fax with 14,4 kbit/s with using the ITU-T T.38 in an audio m-line codec
This scenario represents the case when in the active call state the fax transfer on the media and b-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters) | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | +| SIP parameter | INVITE: SDP
m=image udptl t38

180/200 OK INVITE: SDP
m=image udptl t38 | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE (SDP1) → | | +| | ← 180 Ringing → | | +| | ← 200 OK INVITE (SDP2) → | | +| | ← ACK → | | +| | Apply post-test routine | | + +| MMTel fixed access to VoLTE use case 14 | | | +|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Scenario 4 | Called user is user busy
This scenario represents the case, when the called user is UDUB the network initiates call clearing to the calling user | | +| Options | | | +| Message flow | | | +| SIP (TS A) | Core network | SIP (TS B) | +| | ← INVITE → | | +| | ← 486 Busy Here → | | +| | ← ACK → | | + +| MMTel fixed access to VoLTE use case 14 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 5 | CFU
Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
←
INVITE(Call-ID A-B)
CFU is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine
→
| | + +| MMTel fixed access to VoLTE use case 14 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 6 | CFB
Ensure that when user A calls user B which is UDUB, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
←
INVITE(Call-ID A-B)
CFB is performed
INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B)
180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B)
ACK(Call-ID B-C)
200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B)
Communication
Apply post-test routine
→
| | + +| MMTel fixed access to VoLTE use case 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|---------------------|---|---|--------------------------|--|--|--------------------------|--|---|---------------------|--|--|--------------------------|---|---|--------------------------|--|--|----------------------------|---|---|------------------|--|---|----------------------------|--|--|------------------|---|--|----------------------|--|--|--------------------------------|--| +| Scenario 7 | CFNR
Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
INVITE(Call-ID A-B) →
← 180 Ringing(Call-ID B-A)
CFNR is performed
← INVITE(Call-ID B-C)
180 Ringing(Call-ID C-B) →
← 180 Ringing(Call-ID B-A)
200 OK INVITE(Call-ID C-B) →
← ACK(Call-ID B-C)
← 200 OK INVITE(Call-ID B-A)
ACK(Call-ID A-B) →
Communication
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | INVITE(Call-ID A-B) | → | ← | 180 Ringing(Call-ID B-A) | | | CFNR is performed | | ← | INVITE(Call-ID B-C) | | | 180 Ringing(Call-ID C-B) | → | ← | 180 Ringing(Call-ID B-A) | | | 200 OK INVITE(Call-ID C-B) | → | ← | ACK(Call-ID B-C) | | ← | 200 OK INVITE(Call-ID B-A) | | | ACK(Call-ID A-B) | → | | Communication | | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CFNR is performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | INVITE(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE(Call-ID C-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | ACK(Call-ID B-C) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE(Call-ID B-A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK(Call-ID A-B) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to VoLTE use case 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|-------------------|--|----------------------------------------------|--|---|--------|--|--|---------------|---|--|--------|---|---|-------------|--|---|--------|--|--|---------------|---|---|---------------|--|--|-----|---|--|--------------------------------|--| +| Scenario 8 | CCBS
User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful.
The call is released from the calling user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
SIP (TS A) Core network SIP (TS B)
A CCBS request was already successful
← NOTIFY
200 OK NOTIFY →
INVITE →
← 180 Ringing
← NOTIFY
200 OK NOTIFY →
← 200 OK INVITE
ACK →
Apply post-test routine
| | SIP (TS A) | Core network | SIP (TS B) | | A CCBS request was already successful | | ← | NOTIFY | | | 200 OK NOTIFY | → | | INVITE | → | ← | 180 Ringing | | ← | NOTIFY | | | 200 OK NOTIFY | → | ← | 200 OK INVITE | | | ACK | → | | Apply post-test routine | | +| SIP (TS A) | Core network | SIP (TS B) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A CCBS request was already successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post-test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| MMTel fixed access to VoLTE use case 14 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario 9 | CCNR
User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful.
The call is released from the calling user | +| Options | a) resource reservation is on both sides
b) no resource reservation on terminating side
c) no resource reservation on either side | +| Message flow
SIP (TS A)
Core network
SIP (TS B)
A CCNR request was already successful

Image: Sequence diagram showing message flow between SIP (TS A), Core network, and SIP (TS B). The sequence starts with NOTIFY, 200 OK NOTIFY, INVITE, 180 Ringing, NOTIFY, 200 OK NOTIFY, 200 OK INVITE, and ACK. Arrows indicate the direction of messages between the entities.

 sequenceDiagram     participant TS_A as SIP (TS A)     participant CN as Core network     participant TS_B as SIP (TS B)     Note right of CN: A CCNR request was already successful     CN->>TS_B: NOTIFY     TS_B-->>CN: 200 OK NOTIFY     CN->>TS_B: INVITE     TS_B-->>CN: 180 Ringing     CN->>TS_B: NOTIFY     TS_B-->>CN: 200 OK NOTIFY     CN->>TS_A: 200 OK INVITE     TS_A-->>CN: ACK

Apply post-test routine

| | + +# 9 Metrics and design objectives (DOs) + +### 9.1 Delay probability + +This clause defines the delay parameters, the corresponding values are defined in Part 4 of this IMS/NGN performance benchmark series. + +IMS systems shall comply with the requirements given in the following tables. + +**Table 3** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Local exchange call request delay – Originating outgoing and internal traffic connections | | | +| ANALOGUE SUBSCRIBER LINES
Local exchange call request delay – originating outgoing and internal traffic connections | Clause 2.3.2.1 of [ITU-T Q.543],
For ANALOGUE SUBSCRIBER LINES, call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the exchange until the exchange begins to apply dial tone to the line. The call request delay interval is assumed to correspond to the period at the beginning of a call attempt during which the exchange is unable to receive any call address information from the subscriber | PES [ETSI TS 183 043]
For ANALOGUE SUBSCRIBER LINES connected to the AGCF/MSAN
Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the AGCF/MSAN until the AGCF/MSAN begins to apply dial tone to the line | + +**Table 3** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|---------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| ANALOGUE SUBSCRIBER with IAD (VGW)
Local exchange call request delay – originating outgoing and internal traffic connections | | PES [ETSI TS 183 043]
For ANALOGUE SUBSCRIBER LINES connected to the VGW.
Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the VGW until the VGW begins to apply dial tone to the line | + +![Timing diagram for local exchange analogue subscriber call request delay. It shows two scenarios: ITU-T Q.543 and IMS. In the ITU-T Q.543 scenario, an OLE (Office Line Equipment) receives an 'Off hook' signal from an 'Analogue line' and then sends a 'Dial tone' (represented by a sine wave). In the IMS scenario, an AGCF (Access Gateway Control Function) receives an 'Off hook' signal from an 'Analogue line' and then sends a 'Dial tone'. Both diagrams show the time interval between the off-hook signal and the start of the dial tone. A reference label 'Q.3932.2(15)_F11' is present at the bottom right.](d31b402b650e68c7d6b55d3cf8fda086_img.jpg) + +Timing diagram for local exchange analogue subscriber call request delay. It shows two scenarios: ITU-T Q.543 and IMS. In the ITU-T Q.543 scenario, an OLE (Office Line Equipment) receives an 'Off hook' signal from an 'Analogue line' and then sends a 'Dial tone' (represented by a sine wave). In the IMS scenario, an AGCF (Access Gateway Control Function) receives an 'Off hook' signal from an 'Analogue line' and then sends a 'Dial tone'. Both diagrams show the time interval between the off-hook signal and the start of the dial tone. A reference label 'Q.3932.2(15)\_F11' is present at the bottom right. + +**Figure 11 – Local exchange analogue subscriber call request delay: Overlap sending** + +**Table 4** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Local exchange ISDN subscriber call request delay: Overlap sending | | | +| ISDN SUBSCRIBER LINES
Local exchange call request delay – Overlap sending | Clause 2.3.2.2 of [ITU-T Q.543]
Local exchange call request delay.
Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system | ISDN ETSI [TS 183 036]
Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system | +| IMS SUBSCRIBER
Local exchange call request delay | | IMS [ETSI TS 124 229]
Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the session border control SBC/P-CSCF is passed back to the subscriber | + +![Sequence diagrams for ITU-T Q.543 and IMS showing call request delay. The ITU-T Q.543 diagram shows an ISDN line with SETUP and SETUP ACK messages between a subscriber and an OLE. The IMS diagram shows an ISDN line with SETUP and SETUP ACK between a subscriber and an AGCF/VGW, and a SIP line with INVITE and 100 trying between an SBC/P-CSCF and the subscriber. Blue vertical lines indicate the start and end points for the call request delay measurement.](f78d2e126f00fcc5d8d9797ca410cc09_img.jpg) + +Q.3932.2(15)\_F12 + +Sequence diagrams for ITU-T Q.543 and IMS showing call request delay. The ITU-T Q.543 diagram shows an ISDN line with SETUP and SETUP ACK messages between a subscriber and an OLE. The IMS diagram shows an ISDN line with SETUP and SETUP ACK between a subscriber and an AGCF/VGW, and a SIP line with INVITE and 100 trying between an SBC/P-CSCF and the subscriber. Blue vertical lines indicate the start and end points for the call request delay measurement. + +**Figure 12 – Local exchange ISDN subscriber call request delay: Overlap sending** + +**Table 5** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Local exchange ISDN subscriber call request delay: en-block sending | | | +| ISDN SUBSCRIBER LINES
Local exchange call request delay en-block sending | Clause 2.3.2.3 of [ITU-T Q.543]
For DIGITAL SUBSCRIBER LINES using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the call proceeding message is passed back to the subscriber signalling system | ISDN ETSI [TS 183 036]
For ISDN using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the CALL PROCEEDING message is passed back to the subscriber signalling system | + +![Sequence diagrams for ITU-T Q.543 and IMS showing call request delay with en-block sending. The ITU-T Q.543 diagram shows an ISDN line with SETUP and CALL PROCEEDING messages between a subscriber and an OLE. The IMS diagram shows an ISDN line with SETUP and CALL PROCEEDING between a subscriber and an AGCF/VGW. Blue vertical lines indicate the start and end points for the call request delay measurement.](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +Q.3932.2(15)\_F13 + +Sequence diagrams for ITU-T Q.543 and IMS showing call request delay with en-block sending. The ITU-T Q.543 diagram shows an ISDN line with SETUP and CALL PROCEEDING messages between a subscriber and an OLE. The IMS diagram shows an ISDN line with SETUP and CALL PROCEEDING between a subscriber and an AGCF/VGW. Blue vertical lines indicate the start and end points for the call request delay measurement. + +**Figure 13 – Local exchange ISDN subscriber call request delay: en-block sending** + +**Table 6** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Alerting sending delay for terminating traffic (the users are in different locations, controlled by different S-CSCF/P-CSCF) | | | +| ANALOGUE
SUBSCRIBER
LINES
Alerting sending
delay for terminating
traffic | Clause 2.3.6.1.1 of [ITU-T Q.543]
For calls terminating on ANALOGUE
SUBSCRIBER LINES, alerting
sending delay is defined as the interval
from the instant when the last digit is
available for processing in the
exchange until the ringing tone is sent
backwards toward the calling user | PES [ETSI TS 183 043]
For calls terminating on ANALOGUE
SUBSCRIBER LINES, alerting sending
delay is defined as the interval from the
instant when the last digit is available for
processing in the AGCF/MSAN until the
ringing tone is sent toward the calling
user | +| ISDN
SUBSCRIBER
LINES
Alerting sending
delay for terminating
traffic | Clause 2.3.6.1.2 of [ITU-T Q.543]
For calls terminating on DIGITAL
SUBSCRIBER LINES, the alerting
sending delay is defined as the interval
from the instant that an ALERTING
message is received from the digital
subscriber line signalling system to the
instant at which an ADDRESS
COMPLETE message is passed to the
interexchange signalling system or
ringing tone is sent backward toward
the calling user | ISDN [ETSI TS 183 036]
For calls terminating on ISDN, the
alerting sending delay is defined as the
interval from the instant that an
ALERTING message is received from
the digital subscriber line signalling to
the instant at which an AGCF/MSAN
sends the 180 Ringing backward toward
the calling user | + +![Timing diagrams for ITU-T Q.543 and IMS showing alerting sending delays for analogue and ISDN lines. The ITU-T Q.543 section shows a DLE on an analogue line receiving a 'Latest address digit' and then sending a 'Ringing tone', and on an ISDN line receiving an 'ALERTING' message and sending an 'ACM' message. The IMS section shows an AGCF/VGW on an analogue line receiving a 'Latest address digit' and sending a 'Ringing tone', and on an ISDN line receiving an 'ALERTING' message and sending a '180 ringing' message. A third diagram shows an SBC/P-CSCF on a SIP line receiving a '180 ringing' message and sending another '180 ringing' message. Blue arrows indicate the timing intervals for alerting sending delays. Reference Q.3932.2(15)_F14 is noted at the bottom right.](24ba47df8be44ae91945d88ce2232df5_img.jpg) + +Timing diagrams for ITU-T Q.543 and IMS showing alerting sending delays for analogue and ISDN lines. The ITU-T Q.543 section shows a DLE on an analogue line receiving a 'Latest address digit' and then sending a 'Ringing tone', and on an ISDN line receiving an 'ALERTING' message and sending an 'ACM' message. The IMS section shows an AGCF/VGW on an analogue line receiving a 'Latest address digit' and sending a 'Ringing tone', and on an ISDN line receiving an 'ALERTING' message and sending a '180 ringing' message. A third diagram shows an SBC/P-CSCF on a SIP line receiving a '180 ringing' message and sending another '180 ringing' message. Blue arrows indicate the timing intervals for alerting sending delays. Reference Q.3932.2(15)\_F14 is noted at the bottom right. + +**Figure 14 – Local exchange alerting sending delay for terminating traffic (in different locations)** + +**Table 7** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Alerting sending delay for internal traffic (the users are in same locations, controlled by same AGCF/VGW or P-CSCF) | | | +| ANALOGUE SUBSCRIBER LINES
Alerting sending delay for internal traffic | Clause 2.3.6.2.1 of [ITU-T Q.543]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the exchange until ringing tone is applied to an ANALOGUE calling subscriber line or an ALERTING message is sent to a DIGITAL calling subscriber line signalling system. | PES [ETSI TS 183 043]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the AGCF/MSAN until ringing tone is sent towards the calling subscriber. | + +**Table 7** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| ANALOGUE
SUBSCRIBER
LINES
VGW
Alerting sending
delay for internal
traffic | | PES [ETSI TS 183 043]
For calls terminating on ANALOGUE
SUBSCRIBER LINES, alerting sending
delay is defined as the interval from the
instant that the signalling information is
available for processing in the VGW
until ringing tone is sent towards the
calling subscriber | +| ISDN
SUBSCRIBER
LINES
Alerting sending
delay for internal
traffic | Clause 2.3.6.2.2 of [ITU-T Q.543]
For internal calls terminating on
DIGITAL SUBSCRIBER LINES
originating from DIGITAL
SUBSCRIBER LINES, alerting
sending delay is defined as the interval
from the instant that an ALERTING
message is received from the signalling
system of the called subscriber's line
until the ALERTING message is
applied to the calling subscriber line | ISDN [ETSI TS 183 036]
For calls terminating on ISDN, alerting
sending delay is defined as the interval
from the instant that an ALERTING
message is received and ALERTING is
sent towards the calling subscriber | +| IMS SUBSCRIBER
LINES
180 sending
delay for internal
traffic | | IMS [ETSI TS 124 229]
For calls terminating sending delay is
defined as the interval from the instant
that an 180 message at the Gm interface
has received and 180 is sent on the Gm
towards the calling subscriber | +| LTE SUBSCRIBER
LINES
180 sending
delay for Internal
traffic | | LTE
For calls terminating sending delay is
defined as the interval from the instant
that an 180 message at the LTE UE
interface has received and 180 is sent on
the LTE UE towards the calling
subscriber | + +![Sequence diagrams comparing alerting sending delays for ITU-T Q.543 and IMS. The ITU-T Q.543 section shows alerting on analogue and ISDN lines via OLE/DLE. The IMS section shows alerting on analogue, ISDN, and SIP lines via AGCF/VGW and Gm interface. Blue arrows indicate the delay between call setup and alerting signal generation.](5e05915b2a93a3b404422e0966a7c924_img.jpg) + +The diagram is divided into two main sections: ITU-T Q.543 and IMS. + +- ITU-T Q.543:** + - Analogue line:** Shows a 'Latest address digit' and 'Ringing tone' being sent from the 'Calling' side to the 'Called' side through an 'OLE/DLE' unit. A blue arrow indicates the alerting sending delay. + - ISDN line:** Shows an 'ALERTING' message being sent from the 'Called' side to the 'Calling' side through an 'OLE/DLE' unit. A blue arrow indicates the alerting sending delay. +- IMS:** + - Analogue line:** Shows a 'Latest address digit' and 'Ringing tone' being sent from the 'Calling' side to the 'Called' side through an 'AGCF/VGW' unit. A blue arrow indicates the alerting sending delay. + - ISDN line:** Shows an 'ALERTING' message being sent from the 'Called' side to the 'Calling' side through an 'AGCF/VGW' unit. A blue arrow indicates the alerting sending delay. + - SIP line:** Shows a '180 ringing' message being sent from the 'Called' side to the 'Calling' side through a 'Gm interface' unit. A blue arrow indicates the alerting sending delay. + +Q.3932.2(15)\_F15 + +Sequence diagrams comparing alerting sending delays for ITU-T Q.543 and IMS. The ITU-T Q.543 section shows alerting on analogue and ISDN lines via OLE/DLE. The IMS section shows alerting on analogue, ISDN, and SIP lines via AGCF/VGW and Gm interface. Blue arrows indicate the delay between call setup and alerting signal generation. + +**Figure 15 – Alerting sending delay for internal traffic +(the user are in same locations, controlled by same AGCF/VGW or P-CSCF)** + +**Table 8** + +| Meaning of timers | Parameter Q.543 | IMS/PES equivalent | +|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Call set-up delay | | | +| ISDN
SUBSCRIBER
LINES
Call set-up delay
using overlap
signalling |

Clause 2.4.3 of [ITU-T Q.543]

Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system.

Exchange call set-up delay for originating outgoing traffic connections, digital subscriber lines.

The time interval starts when the INFORMATION message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the corresponding signalling information is passed to the outgoing signalling system

|

ISDN [ETSI TS 183 036]

Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on the Ic interface has been sent

| +| | |

ISDN [ETSI TS 183 036]

Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on terminating Gm interface has been sent

| +| | |

IMS [ETSI TS 124 229]

Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user

| +| | |

IMS [ETSI TS 124 229]

Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user (without preconditions)

| + +![Sequence diagrams illustrating call set-up delay for ITU-T Q.543 and IMS. The ITU-T Q.543 diagram shows an OLE sending SETUP, INFO, and INFO (SC) messages over an ISDN line, followed by an IAM message. The IMS diagram shows two cases: one where an AGCF/VGW sends SETUP, INFO, and INFO (SC) over an ISDN line, followed by an INVITE message to an IBCF/terminating Gm; and another where an originating Gm sends INVITE, INFO/INVITE, and INFO/INVITE messages over an SID line, followed by an INVITE message to an IBCF/terminating Gm. Blue arrows indicate the start and end points for call set-up delay measurement.](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +The diagram illustrates call set-up delay for two scenarios: ITU-T Q.543 and IMS. + +**ITU-T Q.543:** An OLE (Office Line Equipment) sends three messages over an ISDN line: SETUP, INFO, and INFO (SC). A blue arrow indicates the start of the call set-up delay. After these messages, an IAM (Initial Address Message) is sent. A blue arrow indicates the end of the call set-up delay. + +**IMS:** There are two cases shown. + +**Case 1:** An AGCF/VGW (Access Gateway Control Function/Visited Gateway) sends three messages over an ISDN line: SETUP, INFO, and INFO (SC). A blue arrow indicates the start of the call set-up delay. After these messages, an INVITE message is sent to an IBCF/terminating Gm (Interconnection Border Control Function/terminating Gateway). A blue arrow indicates the end of the call set-up delay. The labels "Calling" and "Called" are shown below the AGCF/VGW and IBCF/terminating Gm respectively. + +**Case 2:** An originating Gm (Gateway) sends three messages over an SID line: INVITE, INFO/INVITE, and INFO/INVITE. A blue arrow indicates the start of the call set-up delay. After these messages, an INVITE message is sent to an IBCF/terminating Gm. A blue arrow indicates the end of the call set-up delay. The labels "Calling" and "Called" are shown below the originating Gm and IBCF/terminating Gm respectively. + +Q.3932.2(15)\_F16 + +Sequence diagrams illustrating call set-up delay for ITU-T Q.543 and IMS. The ITU-T Q.543 diagram shows an OLE sending SETUP, INFO, and INFO (SC) messages over an ISDN line, followed by an IAM message. The IMS diagram shows two cases: one where an AGCF/VGW sends SETUP, INFO, and INFO (SC) over an ISDN line, followed by an INVITE message to an IBCF/terminating Gm; and another where an originating Gm sends INVITE, INFO/INVITE, and INFO/INVITE messages over an SID line, followed by an INVITE message to an IBCF/terminating Gm. Blue arrows indicate the start and end points for call set-up delay measurement. + +Figure 16 – Call set-up delay: Overlap sending is used + +Table 9 + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Call set-up delay: en-block sending is used | | | +| ISDN
SUBSCRIBER
LINES
Call set-up delay
using en-block
signalling | Clause 2.4.3.1 of [ITU-T Q.543]
Exchange call set-up delay for originating outgoing traffic connections.
For call attempts using en-bloc sending call set-up delay is defined as the interval from the instant when the signalling information required for | ISDN [ETSI TS 183 036]
Call set-up delay is defined as the interval from the instant when the signalling information including sending complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the Ic interface | + +**Table 9** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| |

routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system.

The time interval starts when the SETUP message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the call set-up is sent on the outgoing signalling system

|

ISDN [ETSI TS 183 036]

Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the terminating Gm interface

ISDN [ETSI TS 183 036]

Call set-up delay for internal traffic is defined as the interval from the instant when the SETUP including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding SETUP signalling information is passed to the called line signalling system (see note)

| +|

IMS SUBSCRIBER

Call set-up delay using for internal traffic

| |

IMS [ETSI TS 124 229]

Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user

| +| | |

IMS [ETSI TS 124 229]

Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user (without preconditions)

| +| | |

IMS [ETSI TS 124 229]

Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user (with preconditions)

| + +**Table 9** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|-------------------------------------------------------------------------------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| LTE | | LTE [3GPP TS 36.300]
Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating LTE_UE (ECM Connected) interface until the instant when the corresponding INVITE signalling information is passed on the terminating LTE_UE (ECM Connected ) interface to the called user with QCI 5
(see Note) | +| | | LTE [3GPP TS 36.300]
Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating LTE_UE (ECM Connected) interface until the instant when the corresponding INVITE signalling information is passed on the terminating LTE_UE (ECM Connected ) interface to the called user with QCI 1 | +| NOTE –If SC (#) is not included the set-up delay may increase up to the digit collection timer (15 s) | | | + +![Sequence diagrams illustrating call set-up delay for ITU-T Q.543 and IMS. The first diagram shows an ISDN line connected to an OLE, where a SETUP message is received and an IAM message is sent. The second diagram shows an IMS architecture with AGCF/VGW and IBCF/terminating Gm components, where a SETUP message is received and an INVITE message is sent. The third diagram shows two AGCF/VGW components connected by an ISDN line, where a SETUP message is received and another SETUP message is sent. The fourth diagram shows two Gm interfaces connected by a SIP line, where an INVITE message is received and another INVITE message is sent. A small note 'Q.3932.2(15)_F17' is present at the bottom right.](ec96d99a16edb981eb7defe41a79b57f_img.jpg) + +Sequence diagrams illustrating call set-up delay for ITU-T Q.543 and IMS. The first diagram shows an ISDN line connected to an OLE, where a SETUP message is received and an IAM message is sent. The second diagram shows an IMS architecture with AGCF/VGW and IBCF/terminating Gm components, where a SETUP message is received and an INVITE message is sent. The third diagram shows two AGCF/VGW components connected by an ISDN line, where a SETUP message is received and another SETUP message is sent. The fourth diagram shows two Gm interfaces connected by a SIP line, where an INVITE message is received and another INVITE message is sent. A small note 'Q.3932.2(15)\_F17' is present at the bottom right. + +Figure 17 – Call set-up delay: en-block sending is used + +Table 10 + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Through-connection delay | | | +| ISDN SUBSCRIBER LINES
Through-connection delay | Clause 2.3.4 of [ITU-T Q.543]
Through-connection delay.
The through-connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through-connection is established and available for carrying traffic and the ANSWER and CONNECT ACKNOWLEDGEMENT messages have been passed to the appropriate signalling systems | ISDN [ETSI TS 183 036]
The through-connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through-connection is established and available for carrying traffic and the CONNECT message has been sent to the calling user signalling system (see Note) | +| IMS
Through-connection delay
Delay for Internal traffic | | IMS [ETSI TS 124 229]
The through-connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm | + +**Table 10** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|-------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| | | interface until the through-connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface | +| LTE | | LTE [3GPP TS 36.300]
The through-connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating LTE_UE interface until the through-connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating LTE_UE interface | + +![Sequence diagrams illustrating through-connection delay for ITU-T Q.543 and IMS. The ITU-T Q.543 diagram shows a DLE connected to an ISDN line with ANM, Connect, and Connect ACK messages. The IMS diagram shows originating and terminating AGCF/VGW and Gm interfaces connected via ISDN and SIP lines, with Connect and 200 OK INVITE messages. Blue vertical lines indicate the start and end points for the delay measurement.](bd0283b61b6a59829e9370b29076c79a_img.jpg) + +The diagram illustrates the through-connection delay for two different network architectures. On the left, for ITU-T Q.543, a DLE (Data Link End) is connected to an ISDN line. The sequence of messages shown is ANM (Answer), Connect, and Connect ACK. A blue vertical line marks the start of the delay at the ANM message and another at the Connect ACK message. On the right, for IMS, there are two parts. The top part shows the ISDN line connection between an originating AGCF/VGW and a terminating AGCF/VGW, with a Connect message. A blue vertical line marks the start of the delay at the originating side. The bottom part shows the SIP line connection between an originating Gm interface and a terminating Gm interface, with a 200 OK INVITE message. A blue vertical line marks the end of the delay at the terminating side. + +Sequence diagrams illustrating through-connection delay for ITU-T Q.543 and IMS. The ITU-T Q.543 diagram shows a DLE connected to an ISDN line with ANM, Connect, and Connect ACK messages. The IMS diagram shows originating and terminating AGCF/VGW and Gm interfaces connected via ISDN and SIP lines, with Connect and 200 OK INVITE messages. Blue vertical lines indicate the start and end points for the delay measurement. + +Q.3932.2(15)\_F18 + +**Figure 18 – Through-connection delay** + +**Table 11** + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Connection release delay | | | +| ISDN SUBSCRIBER LINES | Clause 2.4.6 of [ITU-T Q.543]
Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message | ISDN [ETSI TS 183 036]
Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message | + +Table 11 + +| Meaning of timers | Parameter ITU-T Q.543 | IMS/PES equivalent | +|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Detailed description | | +| Connection call release delay | is received from a signalling system until the instant when the connection is no longer available for use on the call (and is available for use on another call) and a corresponding RELEASE or DISCONNECT message is passed to the other signalling system involved in the connection | is received from a signalling system until the instant when RELEASE COMPLETE is sent and a corresponding RELEASE or DISCONNECT message is sent, or vice versa | +| IMS SUBSCRIBER
Connection call release delay
Delay for internal traffic | | IMS [ETSI TS 124 229]
Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating Gm interface until the instant when 200 OK is sent and a corresponding BYE message is sent at the terminating or originating Gm interface respectively | +| LTE – IMS SUBSCRIBER
Connection call release delay
Delay for internal traffic | | LTE [3GPP TS 36.300]
Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating LTE UE interface until the instant when 200 OK is sent and a corresponding BYE message is sent at the terminating or originating LTE UE interface respectively | + +![Sequence diagrams illustrating connection call release delay for ITU-T Q.543 and IMS.](90183a52275501da5a0fd5c63d837009_img.jpg) + +The diagram illustrates the connection call release delay for two signaling protocols: ITU-T Q.543 and IMS. + +**ITU-T Q.543:** Shows the interaction between an OLE (Originating Line Equipment) and a DLE (Destination Line Equipment) over an ISDN line. The OLE sends a DISCONNECT/RELEASE message to the DLE. A vertical blue line indicates the release delay interval, ending when the DLE sends its own DISCONNECT/RELEASE message back to the OLE. + +**IMS:** Shows two scenarios. The first scenario involves an originating AGCF/VGW and a terminating AGCF/VGW over an ISDN line. The originating side sends a DISCONNECT/RELEASE message, and a vertical blue line indicates the release delay until the terminating side sends its DISCONNECT/RELEASE message. The second scenario involves an originating Gm interface and a terminating Gm interface over a SIP line. The originating side sends a BYE message, and a vertical blue line indicates the release delay until the terminating side sends its BYE message. + +Q.3932.2(15)\_F19 + +Sequence diagrams illustrating connection call release delay for ITU-T Q.543 and IMS. + +Figure 19 – Connection call release delay + +### 9.2 Speech quality analysis + +This clause defines a set of parameters which enables the speech quality analysis of the system under test. They are divided into three parts: Speech quality, speech level and PESQ offset. + +Table 12 shows the speech quality parameters based on PESQ/POLQA. + +Table 13 shows the speech level parameters. + +Table 14 shows the PESQ/POLQA offset parameters. + +**Table 12 – Speech quality parameters based on PESQ/POLQA** + +| Speech quality summary | | +|-------------------------------|------------------------------------| +| | ITU-T P.862.1 / ITU-T P.863 | +| Min | | +| Max | | +| Mean | | +| Std-Dev | | + +**Table 13 – Speech level parameters** + +| Speech level summary (Optional) | | | | | +|----------------------------------------|---------------------|-------------|--------------|---------------------------------| +| | Active level | Peak | Noise | Signal to interval noise | +| Min | | | | | +| Max | | | | | +| Mean | | | | | +| Std-Dev | | | | | + +**Table 14 – PESQ/POLQA offset parameters** + +| Delay summary – Delay (PESQ/POLQA time offset) | | +|-------------------------------------------------------|--| +| Min | | +| Max | | +| Mean | | +| Std-Dev | | +| Range | | + +### 9.3 Call profiler traffic patterns + +This clause defines call profiles which are nowadays implemented in benchmark TS. + +#### 9.3.1 Saw Tooth + +The Saw Tooth ramps up to a peak number of calls and then ramps down from peak. + +![Figure 20: Example of Saw Tooth call profile. A line graph showing the number of calls over time. The y-axis is labeled 'Number of calls' with a tick at 5. The x-axis is labeled 'Time (s)' with ticks at 0, 5, 20, 40, 60, 80, 100, and 130. The graph shows a sawtooth pattern where the number of calls increases linearly from 0 to 4 over the first 20 seconds, then decreases linearly back to 0 over the next 20 seconds. This pattern repeats three times. The label 'Q.3932.2(15)_F20' is at the bottom right.](d155a1511db57a83e3f7f7c6172e1939_img.jpg) + +Figure 20: Example of Saw Tooth call profile. A line graph showing the number of calls over time. The y-axis is labeled 'Number of calls' with a tick at 5. The x-axis is labeled 'Time (s)' with ticks at 0, 5, 20, 40, 60, 80, 100, and 130. The graph shows a sawtooth pattern where the number of calls increases linearly from 0 to 4 over the first 20 seconds, then decreases linearly back to 0 over the next 20 seconds. This pattern repeats three times. The label 'Q.3932.2(15)\_F20' is at the bottom right. + +**Figure 20 – Example of Saw Tooth call profile** + +#### 9.3.2 Blast + +Blast – All calls go off-hook simultaneously, are connected for a specified time, and then disconnected. + +![Figure 21: Example of blast call profile. A line graph showing the number of calls over time. The y-axis is labeled 'Number of calls' and the x-axis is labeled 'Time (s)' with ticks at 0, 5, 20, 40, 60, 80, 100, and 130. The graph shows a square wave pattern where the number of calls jumps to a constant value at 0 seconds, remains constant until 20 seconds, drops to 0 at 20 seconds, jumps back to the constant value at 40 seconds, remains constant until 60 seconds, drops to 0 at 60 seconds, jumps back to the constant value at 80 seconds, remains constant until 100 seconds, drops to 0 at 100 seconds, and jumps back to the constant value at 120 seconds. The label 'Q.3932.2(15)_F21' is at the bottom right.](99b769aeac0b78472f4cb81be7836f3b_img.jpg) + +Figure 21: Example of blast call profile. A line graph showing the number of calls over time. The y-axis is labeled 'Number of calls' and the x-axis is labeled 'Time (s)' with ticks at 0, 5, 20, 40, 60, 80, 100, and 130. The graph shows a square wave pattern where the number of calls jumps to a constant value at 0 seconds, remains constant until 20 seconds, drops to 0 at 20 seconds, jumps back to the constant value at 40 seconds, remains constant until 60 seconds, drops to 0 at 60 seconds, jumps back to the constant value at 80 seconds, remains constant until 100 seconds, drops to 0 at 100 seconds, and jumps back to the constant value at 120 seconds. The label 'Q.3932.2(15)\_F21' is at the bottom right. + +**Figure 21 – Example of blast call profile** + +#### 9.3.3 Rolling Blast + +Rolling Blast – A defined set of channels go off-hook at once, and the pattern is repeated for all assigned channels. + +#### 9.3.4 Ramp + +Ramp – Gradually increases connected calls to a specified number and then maintains that number of calls. + +![Figure 22: Example of Ramp call profile. A line graph showing the number of calls over time. The y-axis is labeled 'Number of calls' and the x-axis is labeled 'Time (s)' with ticks at 0, 5, 20, 40, 60, 80, 100, and 130. The graph shows a trapezoidal pattern where the number of calls increases linearly from 0 at 0 seconds to a constant value at 20 seconds, remains constant until 60 seconds, decreases linearly to 0 at 100 seconds, and then increases linearly back to the constant value at 120 seconds. The label 'Q.3932.2(15)_F22' is at the bottom right.](654cedceef37338716baa54407d488c8_img.jpg) + +Figure 22: Example of Ramp call profile. A line graph showing the number of calls over time. The y-axis is labeled 'Number of calls' and the x-axis is labeled 'Time (s)' with ticks at 0, 5, 20, 40, 60, 80, 100, and 130. The graph shows a trapezoidal pattern where the number of calls increases linearly from 0 at 0 seconds to a constant value at 20 seconds, remains constant until 60 seconds, decreases linearly to 0 at 100 seconds, and then increases linearly back to the constant value at 120 seconds. The label 'Q.3932.2(15)\_F22' is at the bottom right. + +**Figure 22 – Example of Ramp call profile** + +#### 9.3.5 Steady Call Rate + +Steady Call Rate – Delivers a fixed, regulated call rate into the SUT. + +#### 9.3.6 Poisson distribution + +Poisson distribution – Defines call arrival rate by a statistical distribution. + +![A line graph showing a Poisson distribution. The x-axis represents the number of arrivals, ranging from 1 to 201 with major ticks every 8 units (1, 9, 17, 25, 33, 41, 49, 57, 65, 73, 81, 89, 97, 105, 113, 121, 129, 137, 145, 153, 161, 169, 177, 185, 193, 201). The y-axis represents the frequency or probability, ranging from 0 to 450 with major ticks every 50 units (0, 50, 100, 150, 200, 250, 300, 350, 400, 450). The distribution is a bell-shaped curve centered at approximately 105 arrivals, with a peak value of about 400. The curve is plotted with blue dots connected by a line.](08e28b34a19ebd5402953188378292ec_img.jpg) + +A line graph showing a Poisson distribution. The x-axis represents the number of arrivals, ranging from 1 to 201 with major ticks every 8 units (1, 9, 17, 25, 33, 41, 49, 57, 65, 73, 81, 89, 97, 105, 113, 121, 129, 137, 145, 153, 161, 169, 177, 185, 193, 201). The y-axis represents the frequency or probability, ranging from 0 to 450 with major ticks every 50 units (0, 50, 100, 150, 200, 250, 300, 350, 400, 450). The distribution is a bell-shaped curve centered at approximately 105 arrivals, with a peak value of about 400. The curve is plotted with blue dots connected by a line. + +**Figure 23 – Example of Poisson distribution** + +# **Appendix I** + +## **Call flows** + +(This appendix does not form an integral part of this Recommendation.) + +This appendix defines the call flows which should be implemented to simulate ISDN – non-ISDN environment. + +Figure I.1 presents the call flow for the – IMS/PES environment calling side. + +Figure I.2 presents the call flow for the – IMS/PES environment called side. + +Figure I.3 presents the call flow for the ISDN environment for voice calls calling side – overlap. + +Figure I.4 presents the call flow for the ISDN environment for voice calls calling side – en-block. + +Figure I.5 presents the call flow for the ISDN environment for voice calls called side. + +Figure I.6 presents the call flow for the ISDN environment for data calls calling side. + +Figure I.7 presents the call flow for the ISDN environment for data calls called side. + +![Flowchart for Figure I.1 showing call processing logic for a calling party. It includes states like 'On hook', 'OFF hook', and various timers (T1, T2, T3, T4) and decision points for tone availability, connection establishment, and quality (PESQ).](ca86f53f9735fe98b6c6003d1b759f64_img.jpg) + +``` + +graph TD + subgraph Calling_party + OnHook([On hook]) --> T1[Timer T1] + T1 --> OFFHook([OFF hook]) + OFFHook --> TLE[Start timer local exchange call request delay] + TLE --> DT{Dialing tone available} + DT -- No --> TLX[Timer local exchange call request delay timeout] + TLX -- No --> TLE + TLX -- Yes --> 1((1)) + DT -- Yes --> STCD[STOP timer call request delay] + STCD --> SD[Send digits] + SD --> T2_Wait[Start timer T2 waiting for ringing tone] + T2_Wait --> RTA{Ringing tone available} + RTA -- No --> T2_ALERT[Timer T2 waiting for ALERTING timeout] + RTA -- Yes --> STOP_T2[STOP timer T2] + T2_ALERT -- No --> STOP_T2 + T2_ALERT -- Yes --> STOP_T2 + STOP_T2 --> 1 + STOP_T2 --> T3_Wait[Start timer T3 waiting for answer] + T3_Wait --> CE{Connection established} + CE -- Yes --> STOP_T3[Stop timer T3] + CE -- No --> T3_TO{T3 time out} + T3_TO -- No --> STOP_T3 + T3_TO -- Yes --> 1 + STOP_T3 --> T4_Wait[Time T4 connection holding time] + T4_Wait --> DTMF{DTMF} + DTMF -- No --> STOP_T4 + DTMF -- Yes --> SID[Send inband digits] + SID --> RID[Receive inband digits] + RID --> ISE{Inband synch established} + ISE -- No --> STOP_T4 + ISE -- Yes --> SVS[Send voice samples] + SVS --> RVS[Receive voice samples] + RVS --> PESQ{PESQ > limit} + PESQ -- Yes --> STOP_T4 + PESQ -- No --> T4_TO{T4 time out} + T4_TO -- Yes --> 2((2)) + T4_TO -- No --> T4_Wait + STOP_T4 --> 1 + end + TestFail{{Test fail}} --> 1 + TestPass{{Test pass}} --> 2 + StopT1[Stop T1] --> TestFail + StopT1 --> TestPass + TestFail --> OnHook + TestPass --> OnHook + +``` + +Flowchart for Figure I.1 showing call processing logic for a calling party. It includes states like 'On hook', 'OFF hook', and various timers (T1, T2, T3, T4) and decision points for tone availability, connection establishment, and quality (PESQ). + +Q.3932.2(15)\_FI.1 + +Figure I.1 + +![Flowchart for Figure I.2 showing two call flow sequences. The left sequence is for 'Calling party' and includes steps: On hook, Alerting available, Number of alerting repetitions < limit, Delay time 1000 ms, OFF hook, Test pass, and Test fail. The right sequence includes steps: Time T5 connection holding time, DTMF, Receive inband digits, Send inband digits, Inband synch established, Receive voice samples, Send voice samples, PESQ > limit, T5 time out, and Stop T5. Connectors 1 and 2 are used between the two flows.](2dd10dd89365981b6b6154de6390a602_img.jpg) + +``` + +graph TD + subgraph Calling_party [Calling party] + OnHook([On hook]) --> AlertingAvail{Alerting available} + AlertingAvail -- No --> TestFail[Test fail] + AlertingAvail -- Yes --> NumAlerting{Number of alerting repetitions < limit} + NumAlerting -- No --> DelayTime[Delay time 1000 ms] + DelayTime --> OffHook([OFF hook]) + OffHook --> TimeT5[Time T5 connection holding time] + TestFail --> C1((1)) + C1 --> DTMF{DTMF} + end + OnHook --> TestPass[Test pass] + TestPass --> C2((2)) + C2 --> TimeT5 + TimeT5 --> DTMF + DTMF -- No --> StopT5_1[Stop T5] + StopT5_1 --> C1 + DTMF -- Yes --> RecInband[Receive inband digits] + RecInband --> SendInband[Send inband digits] + SendInband --> InbandSynch{Inband synch established} + InbandSynch -- No --> StopT5_2[Stop T5] + StopT5_2 --> C1 + InbandSynch -- Yes --> RecVoice[Receive voice samples] + RecVoice --> SendVoice[Send voice samples] + SendVoice --> PESQ{PESQ > limit} + PESQ -- No --> StopT5_3[Stop T5] + StopT5_3 --> C1 + PESQ -- Yes --> T5TimeOut{T5 time out} + T5TimeOut -- Yes --> C2 + T5TimeOut -- No --> TimeT5 + +``` + +Flowchart for Figure I.2 showing two call flow sequences. The left sequence is for 'Calling party' and includes steps: On hook, Alerting available, Number of alerting repetitions < limit, Delay time 1000 ms, OFF hook, Test pass, and Test fail. The right sequence includes steps: Time T5 connection holding time, DTMF, Receive inband digits, Send inband digits, Inband synch established, Receive voice samples, Send voice samples, PESQ > limit, T5 time out, and Stop T5. Connectors 1 and 2 are used between the two flows. + +Q.3932.2(15)\_FI.2 + +Figure I.2 + +![Flowchart for call setup process (Figure I.3). The process starts with 'Calling party' -> 'On hook' -> 'Timer T1' -> 'OFF hook send SETUP'. It then branches into 'Test fail' (leading to 'STOP timer T1') and 'Test pass' (leading to 'Start timer exchange call request delay timer'). The main flow continues through 'SETUP ACK available', 'Exchange call request delay timer timeout', 'STOP timer call request delay', 'Start exchange call request delay timer for dial tone', 'Dial tone available', and 'Exchange call request delay timer timeout' again. From the second 'Exchange call request delay timer timeout', it goes to 'STOP timer call request delay for dial tone' and then to 'Overlap sending'. 'Overlap sending' branches to 'Send digits enblock' (leading to 'Send digits overlap' and 'Timer T3 waiting for ALERTING') and 'Send digits overlap' (leading to 'Timer T3 waiting for ALERTING'). 'Timer T3 waiting for ALERTING' leads to 'Timer T3 ALERTING and ringing tone'. If 'Yes', it goes to 'STOP timer T3 waiting for ALERTING' and then 'Timer T4 waiting for answer'. If 'No', it goes to 'Timer T3 waiting for ALERTING timeout', which leads to 'STOP timer T3 waiting for ALERTING' and then 'Timer T4 waiting for answer'. 'Timer T4 waiting for answer' leads to 'CONNECT Recived'. If 'Yes', it goes to 'STOP timer waiting for CONNECT' and then 'T3 time out'. If 'No', it goes to 'T3 time out'. 'T3 time out' leads to 'Time T5 connection holding time'. 'Time T5 connection holding time' leads to 'DTMF'. If 'Yes', it goes to 'Send inband digits' and then 'Receive inband digits'. If 'No', it goes to 'Stop T5' and then '1'. 'Receive inband digits' leads to 'Inband synch established'. If 'Yes', it goes to 'Send voice samples' and then 'Receive voice samples'. If 'No', it goes to 'Stop T5' and then '1'. 'Receive voice samples' leads to 'PESQ > limit'. If 'Yes', it goes to 'T5 time out'. If 'No', it goes to 'Stop T5' and then '1'. 'T5 time out' leads to '2' and back to 'Time T5 connection holding time'.](b3335932702b8668e62791e9fd12c9ff_img.jpg) + +``` + +graph TD + subgraph Calling_party [Calling party] + OnHook([On hook]) --> T1[Timer T1] + T1 --> OffHook([OFF hook send SETUP]) + OffHook --> TestFail{Test fail} + OffHook --> TestPass{Test pass} + TestFail --> StopT1[STOP timer T1] + TestPass --> StartT1[Start timer exchange call request delay timer] + end + StartT1 --> SetupAck{SETUP ACK available} + SetupAck -- No --> ExchangeTimeout1{Exchange call request delay timer timeout} + ExchangeTimeout1 -- No --> StopDelay1[STOP timer call request delay] + StopDelay1 --> StartDelay2[Start exchange call request delay timer for dial tone] + StartDelay2 --> DialTone{Dial tone available} + DialTone -- No --> ExchangeTimeout2{Exchange call request delay timer timeout} + ExchangeTimeout2 -- No --> StopDelay2[STOP timer call request delay for dial tone] + StopDelay2 --> OverlapSending{Overlap sending} + OverlapSending -- Yes --> Enblock{{Send digits enblock}} + Enblock --> Overlap{{Send digits overlap}} + Overlap --> T3Waiting[Timer T3 waiting for ALERTING] + OverlapSending -- No --> Overlap + Overlap --> T3Waiting + T3Waiting --> T3Alerting{Timer T3 ALERTING and ringing tone} + T3Alerting -- Yes --> StopT3[STOP timer T3 waiting for ALERTING] + T3Alerting -- No --> T3Timeout{Timer T3 waiting for ALERTING timeout} + T3Timeout -- Yes --> StopT3 + T3Timeout -- No --> T3Timeout + StopT3 --> T4Waiting[Timer T4 waiting for answer] + T4Waiting --> ConnectRecived{CONNECT Recived} + ConnectRecived -- Yes --> StopConnect[STOP timer waiting for CONNECT] + StopConnect --> T3TimeOut{T3 time out} + ConnectRecived -- No --> T3TimeOut + T3TimeOut -- Yes --> T5Time[Time T5 connection holding time] + T3TimeOut -- No --> T5Time + T5Time --> DTMF{DTMF} + DTMF -- Yes --> InbandDigits{{Send inband digits}} + InbandDigits --> ReceiveInband{{Receive inband digits}} + DTMF -- No --> StopT5_1[Stop T5] + StopT5_1 --> 1_1((1)) + ReceiveInband --> InbandSynch{Inband synch established} + InbandSynch -- Yes --> VoiceSamples1{{Send voice samples}} + VoiceSamples1 --> ReceiveVoice{{Receive voice samples}} + InbandSynch -- No --> StopT5_2[Stop T5] + StopT5_2 --> 1_2((1)) + ReceiveVoice --> PESQLimit{PESQ > limit} + PESQLimit -- Yes --> T5TimeOut{T5 time out} + PESQLimit -- No --> StopT5_3[Stop T5] + StopT5_3 --> 1_3((1)) + T5TimeOut -- Yes --> 2((2)) + 2 --> T5Time + T5TimeOut -- No --> T5Time + +``` + +Flowchart for call setup process (Figure I.3). The process starts with 'Calling party' -> 'On hook' -> 'Timer T1' -> 'OFF hook send SETUP'. It then branches into 'Test fail' (leading to 'STOP timer T1') and 'Test pass' (leading to 'Start timer exchange call request delay timer'). The main flow continues through 'SETUP ACK available', 'Exchange call request delay timer timeout', 'STOP timer call request delay', 'Start exchange call request delay timer for dial tone', 'Dial tone available', and 'Exchange call request delay timer timeout' again. From the second 'Exchange call request delay timer timeout', it goes to 'STOP timer call request delay for dial tone' and then to 'Overlap sending'. 'Overlap sending' branches to 'Send digits enblock' (leading to 'Send digits overlap' and 'Timer T3 waiting for ALERTING') and 'Send digits overlap' (leading to 'Timer T3 waiting for ALERTING'). 'Timer T3 waiting for ALERTING' leads to 'Timer T3 ALERTING and ringing tone'. If 'Yes', it goes to 'STOP timer T3 waiting for ALERTING' and then 'Timer T4 waiting for answer'. If 'No', it goes to 'Timer T3 waiting for ALERTING timeout', which leads to 'STOP timer T3 waiting for ALERTING' and then 'Timer T4 waiting for answer'. 'Timer T4 waiting for answer' leads to 'CONNECT Recived'. If 'Yes', it goes to 'STOP timer waiting for CONNECT' and then 'T3 time out'. If 'No', it goes to 'T3 time out'. 'T3 time out' leads to 'Time T5 connection holding time'. 'Time T5 connection holding time' leads to 'DTMF'. If 'Yes', it goes to 'Send inband digits' and then 'Receive inband digits'. If 'No', it goes to 'Stop T5' and then '1'. 'Receive inband digits' leads to 'Inband synch established'. If 'Yes', it goes to 'Send voice samples' and then 'Receive voice samples'. If 'No', it goes to 'Stop T5' and then '1'. 'Receive voice samples' leads to 'PESQ > limit'. If 'Yes', it goes to 'T5 time out'. If 'No', it goes to 'Stop T5' and then '1'. 'T5 time out' leads to '2' and back to 'Time T5 connection holding time'. + +Q.3932.2(15)\_FI.3 + +Figure I.3 + +![Flowchart for Figure I.4 showing call processing logic. The left side handles the initial call setup from 'On hook' through 'Timer T1', 'Send digits enblock SETUP', 'CALL PROCEEDING received?', 'Timer T3 waiting for ALERTING', 'Receiving ALERTING and ringing tone', 'Timer T3 waiting for ALERTING timeout', 'STOP timer T3 waiting for ALERTING', 'Timer T4 waiting for answer', 'CONNECT Received', 'STOP timer waiting for CONNECT', and 'T4 time out'. The right side handles the connection holding logic starting with 'Time T5 connection holding time', 'DTMF', 'Send inband digits', 'Receive inband digits', 'Inband synch established', 'Send voice samples', 'Receive voice samples', 'PESQ > limit', and 'T5 time out'. Various connectors (1, 2) and decision points (Test fail, Test pass) are included.](a37adbbe12ec735a20ead2466363d07a_img.jpg) + +``` + +graph TD + subgraph LeftFlow [ ] + OnHook([On hook]) --> T1[Timer T1] + T1 --> SendDigits{{Send digits enblock +SETUP +(sending complete)}} + SendDigits --> CallProceeding{CALL PROCEEDING +received?} + CallProceeding -- No --> C1((1)) + CallProceeding -- Yes --> T3_1[Timer T3 +waiting for +ALERTING] + T3_1 --> ReceivingAlerting{Receiving +ALERTING +and ringing +tone} + ReceivingAlerting -- No --> T3_2{Timer T3 +waiting for +ALERTING +timeout} + ReceivingAlerting -- Yes --> StopT3[STOP +timer T3 +waiting for +ALERTING] + T3_2 -- No --> StopT3 + T3_2 -- Yes --> C1 + StopT3 --> T4[Timer T4 +waiting for +answer] + T4 --> ConnectReceived{CONNECT +Received} + ConnectReceived -- No --> StopT4[STOP timer +waiting for +CONNECT] + ConnectReceived -- Yes --> StopT4 + StopT4 --> T4Timeout{T4 time out} + T4Timeout -- No --> T4 + T4Timeout -- Yes --> C1 + end + + subgraph RightFlow [ ] + T5[Time T5 +connection +holding time] --> DTMF{DTMF} + DTMF -- No --> StopT5_1[Stop T5] + DTMF -- Yes --> SendInband{{Send inband +digits}} + SendInband --> ReceiveInband[/Receive +inband +digits/] + ReceiveInband --> InbandSynch{Inband +synch +established} + InbandSynch -- No --> StopT5_1 + InbandSynch -- Yes --> SendVoice{{Send voice +samples}} + SendVoice --> ReceiveVoice[/Receive +voice +samples/] + ReceiveVoice --> PESQ{PESQ +> limit} + PESQ -- No --> StopT5_2[Stop T5] + PESQ -- Yes --> T5Timeout{T5 time out} + T5Timeout -- Yes --> C2((2)) + T5Timeout -- No --> T5 + end + + StopT3 --> RightFlow + StopT5_1 --> C1 + StopT5_2 --> C1 + C2 --> RightFlow + TestFail{{Test fail}} --> StopT1[STOP +timer T1] + TestPass{{Test pass}} --> StopT1 + StopT1 --> OnHook + TestFail --> C1 + TestPass --> C2 + +``` + +Flowchart for Figure I.4 showing call processing logic. The left side handles the initial call setup from 'On hook' through 'Timer T1', 'Send digits enblock SETUP', 'CALL PROCEEDING received?', 'Timer T3 waiting for ALERTING', 'Receiving ALERTING and ringing tone', 'Timer T3 waiting for ALERTING timeout', 'STOP timer T3 waiting for ALERTING', 'Timer T4 waiting for answer', 'CONNECT Received', 'STOP timer waiting for CONNECT', and 'T4 time out'. The right side handles the connection holding logic starting with 'Time T5 connection holding time', 'DTMF', 'Send inband digits', 'Receive inband digits', 'Inband synch established', 'Send voice samples', 'Receive voice samples', 'PESQ > limit', and 'T5 time out'. Various connectors (1, 2) and decision points (Test fail, Test pass) are included. + +Q.3932.2(15)\_FI.4 + +Figure I.4 + +![Flowchart for Figure I.5 showing call processing logic. The process starts with 'Called party' -> 'On hook' -> 'SETUP available'. If 'No', it goes to 'STOP connection holding timer T5'. If 'Yes', it goes to 'Send ALERTING' -> 'Delay time 1000 ms' -> 'Send CONNECT'. From 'Send CONNECT', it goes to 'Time T5 connection holding time'. From 'Time T5 connection holding time', it goes to 'DTMF'. If 'No', it goes to 'Inband synch established'. If 'Yes', it goes to 'Receive inband digits' -> 'Send inband digits' -> 'Inband synch established'. From 'Inband synch established', if 'Yes', it goes to 'Receive voice samples' -> 'Send voice samples' -> 'PESQ > limit'. If 'No', it goes to connector '1'. From 'PESQ > limit', if 'Yes', it goes to 'T5 time out'. If 'No', it goes to connector '1'. From 'T5 time out', if 'Yes', it goes to connector '2'. If 'No', it goes to connector '1'. Connectors '1' and '2' lead back to 'Test fail' and 'Test pass' respectively, which then lead to 'STOP connection holding timer T5'.](3481cde1adf61b0452dd6489dada6d6a_img.jpg) + +``` + +graph TD + subgraph Called_party [Called party] + On_hook([On hook]) --> SETUP_available{SETUP available} + end + SETUP_available -- No --> STOP_T5[STOP connection holding timer T5] + SETUP_available -- Yes --> Send_ALERTING{{Send ALERTING}} + Send_ALERTING --> Delay_1000_ms[Delay time 1000 ms] + Delay_1000_ms --> Send_CONNECT{{Send CONNECT}} + Send_CONNECT --> Time_T5[Time T5 connection holding time] + Time_T5 --> DTMF{DTMF} + DTMF -- No --> Inband_synch{Inband synch established} + DTMF -- Yes --> Receive_inband[Receive inband digits] + Receive_inband --> Send_inband{{Send inband digits}} + Send_inband --> Inband_synch + Inband_synch -- No --> C1((1)) + Inband_synch -- Yes --> Receive_voice[Receive voice samples] + Receive_voice --> Send_voice{{Send voice samples}} + Send_voice --> PESQ_limit{PESQ > limit} + PESQ_limit -- No --> C1 + PESQ_limit -- Yes --> T5_time_out{T5 time out} + T5_time_out -- Yes --> C2((2)) + T5_time_out -- No --> C1 + C1 --> Test_fail{{Test fail}} + C2 --> Test_pass{{Test pass}} + Test_fail --> STOP_T5 + Test_pass --> STOP_T5 + STOP_T5 --> On_hook + +``` + +Q.3932.2(15)\_FI.5 + +Flowchart for Figure I.5 showing call processing logic. The process starts with 'Called party' -> 'On hook' -> 'SETUP available'. If 'No', it goes to 'STOP connection holding timer T5'. If 'Yes', it goes to 'Send ALERTING' -> 'Delay time 1000 ms' -> 'Send CONNECT'. From 'Send CONNECT', it goes to 'Time T5 connection holding time'. From 'Time T5 connection holding time', it goes to 'DTMF'. If 'No', it goes to 'Inband synch established'. If 'Yes', it goes to 'Receive inband digits' -> 'Send inband digits' -> 'Inband synch established'. From 'Inband synch established', if 'Yes', it goes to 'Receive voice samples' -> 'Send voice samples' -> 'PESQ > limit'. If 'No', it goes to connector '1'. From 'PESQ > limit', if 'Yes', it goes to 'T5 time out'. If 'No', it goes to connector '1'. From 'T5 time out', if 'Yes', it goes to connector '2'. If 'No', it goes to connector '1'. Connectors '1' and '2' lead back to 'Test fail' and 'Test pass' respectively, which then lead to 'STOP connection holding timer T5'. + +Figure I.5 + +![Flowchart for Figure I.6 showing call processing logic for a calling party. It includes states like 'On hook', 'OFF hook send SETUP', and 'CONNECT Received', with various timers (T1, T3, T4, T5) and decision points (e.g., 'SETUP ACK available', 'Receiving ALERTING').](9faa3512b2ff7973283e76192e91bf65_img.jpg) + +``` + +graph TD + subgraph Calling_party [Calling party] + OnHook([On hook]) --> T1[Timer T1] + T1 --> OFFHook([OFF hook send SETUP]) + OFFHook --> StartDelay[Start exchange call request delay timer] + StartDelay --> SetupAck{SETUP ACK available} + SetupAck -- Yes --> StopDelay[STOP timer call request delay] + SetupAck -- No --> DelayTimeout{Exchange call request delay timer timeout} + DelayTimeout -- Yes --> 1((1)) + DelayTimeout -- No --> StopDelay + StopDelay --> StartDelayTone[Start exchange call request delay timer for dial tone] + StartDelayTone --> OverlapSend{Overlap sending} + end + + OverlapSend -- Yes --> SendEnblock{{Send digits enblock}} + OverlapSend -- No --> SendOverlap{{Send digits overlap}} + SendEnblock --> SendOverlap + SendOverlap --> T3Wait[Timer T3 waiting for ALERTING] + T3Wait --> ReceivingAlerting{Receiving ALERTING} + ReceivingAlerting -- Yes --> StopT3Wait[STOP timer T3 waiting for ALERTING] + ReceivingAlerting -- No --> T3Timeout{Timer T3 waiting for ALERTING timeout} + T3Timeout -- Yes --> StopT3Wait + T3Timeout -- No --> StopT3Wait + StopT3Wait --> T4Wait[Timer T4 waiting for answer] + T4Wait --> ConnectReceived{CONNECT Received} + ConnectReceived -- Yes --> StopT4Wait[STOP timer waiting for CONNECT] + ConnectReceived -- No --> T4Timeout{T4 time out} + StopT4Wait --> T4Timeout + T4Timeout -- Yes --> 1 + T4Timeout -- No --> OverlapSend + + StartDelay --> TestFail{{Test fail}} + StartDelay --> TestPass{{Test pass}} + TestFail --> 1 + TestPass --> 2((2)) + + StopT3Wait --> 1 + StopT3Wait --> 2 + StopT3Wait --> T5Time[Time T5 connection holding time] + + T5Time --> SendBERT{{Send BERT sequence}} + SendBERT --> ReceiveBERT{{Receive BERT sequence}} + ReceiveBERT --> BERTLimit{BERT > limit} + BERTLimit -- Yes --> T5Timeout{T5 time out} + BERTLimit -- No --> StopT5[Stop T5] + StopT5 --> 1 + T5Timeout -- Yes --> 2 + T5Timeout -- No --> SendBERT + +``` + +Flowchart for Figure I.6 showing call processing logic for a calling party. It includes states like 'On hook', 'OFF hook send SETUP', and 'CONNECT Received', with various timers (T1, T3, T4, T5) and decision points (e.g., 'SETUP ACK available', 'Receiving ALERTING'). + +Q.3932.2(15)\_FI.6 + +Figure I.6 + +![Flowchart for Figure I.7 showing a call handling process. It starts with 'On hook' (Calling party), followed by 'SETUP available' (No/Yes), 'Send ALERTING', 'Delay time 1000 ms', 'Send CONNECT', 'Time T5 connection holding time', 'Receive BERT sequence', 'Send BERT sequence', 'BERT > limit' (No/Yes), and 'T5 time out' (Yes/No). It includes connectors 1 and 2, and test fail/pass points.](3a006a7c9c9934695f0fc731344eff8a_img.jpg) + +``` + +graph TD + OnHook([On hook]) --> SETUP{SETUP available} + SETUP -- No --> STOP[STOP connection holding timer T5] + STOP --> OnHook + SETUP -- Yes --> ALERTING{{Send ALERTING}} + ALERTING --> DELAY[Delay time 1000 ms] + DELAY --> CONNECT{{Send CONNECT}} + CONNECT --> T5[Time T5 connection holding time] + T5 --> RECEIVE[Receive BERT sequence] + RECEIVE --> SEND[Send BERT sequence] + SEND --> BERT{BERT > limit} + BERT -- No --> 1((1)) + BERT -- Yes --> T5TO{T5 time out} + T5TO -- Yes --> 2((2)) + T5TO -- No --> RECEIVE + 1 --> FAIL{{Test fail}} + 2 --> PASS{{Test pass}} + FAIL --> STOP + PASS --> OnHook + +``` + +Q.3932.2(15)\_FI.7 + +Flowchart for Figure I.7 showing a call handling process. It starts with 'On hook' (Calling party), followed by 'SETUP available' (No/Yes), 'Send ALERTING', 'Delay time 1000 ms', 'Send CONNECT', 'Time T5 connection holding time', 'Receive BERT sequence', 'Send BERT sequence', 'BERT > limit' (No/Yes), and 'T5 time out' (Yes/No). It includes connectors 1 and 2, and test fail/pass points. + +Figure I.7 + +# Appendix II + +## Load profiles examples + +(This appendix does not form an integral part of this Recommendation.) + +This appendix defines the load profiles to simulate ISDN – non-ISDN environments. + +Figure II.1: The load simulates 2.0 CAPS, call duration 100 s, number of simulated users 200. The number of calls increases each 500 ms. After the call duration of 100 s the calls will be released. The call set-up phase is marked orange, the call release phase blue. + +Figure II.2: The load simulates 2.66 CAPS, call duration 15 s, number of simulated users 30. The number of calls increases each 500 ms. After a call duration of 15 s the calls will be released. In the time interval of 5 s are tested simultaneous ISDN call set-ups using five channels. In order to simulate a load of 2.0 CAPS, the increase of number of calls is changed to 1.5 per second. + +![Figure II.1: A line graph titled '2.0 CAPS' showing the number of users over time. The y-axis is labeled 'User' and ranges from 0 to 250. The x-axis is labeled 'Seconds' and ranges from 0 to 200. The graph shows a linear increase from 0 users at 0 seconds to 200 users at 100 seconds, followed by a linear decrease back to 0 users at 200 seconds. The text 'Q.3932.2(15)_FII.1' is in the bottom right corner.](8b0c76c2c4aa368163995731c966d7f2_img.jpg) + +Figure II.1 is a line graph titled "2.0 CAPS". The y-axis is labeled "User" and ranges from 0 to 250. The x-axis is labeled "Seconds" and ranges from 0 to 200. The graph shows a linear increase from 0 users at 0 seconds to 200 users at 100 seconds, followed by a linear decrease back to 0 users at 200 seconds. The text "Q.3932.2(15)\_FII.1" is in the bottom right corner. + +| Seconds | User | +|---------|------| +| 0 | 0 | +| 100 | 200 | +| 200 | 0 | + +Figure II.1: A line graph titled '2.0 CAPS' showing the number of users over time. The y-axis is labeled 'User' and ranges from 0 to 250. The x-axis is labeled 'Seconds' and ranges from 0 to 200. The graph shows a linear increase from 0 users at 0 seconds to 200 users at 100 seconds, followed by a linear decrease back to 0 users at 200 seconds. The text 'Q.3932.2(15)\_FII.1' is in the bottom right corner. + +Figure II.1 + +![Figure II.2: A line graph titled '2.6666.. CAPS' showing the number of users over time. The y-axis is labeled 'User' and ranges from 0 to 45. The x-axis is labeled 'Seconds' and ranges from 0 to 30. The graph shows a piecewise linear increase from 0 users at 0 seconds to 20 users at 5 seconds, then to 40 users at 15 seconds, then a decrease to 30 users at 20 seconds, and finally a decrease to 0 users at 30 seconds. The text 'Q.3932.2(15)_FII.2' is in the bottom right corner.](83397befc16475b196b532d975898715_img.jpg) + +Figure II.2 is a line graph titled "2.6666.. CAPS". The y-axis is labeled "User" and ranges from 0 to 45. The x-axis is labeled "Seconds" and ranges from 0 to 30. The graph shows a piecewise linear increase from 0 users at 0 seconds to 20 users at 5 seconds, then to 40 users at 15 seconds, then a decrease to 30 users at 20 seconds, and finally a decrease to 0 users at 30 seconds. The text "Q.3932.2(15)\_FII.2" is in the bottom right corner. + +| Seconds | User | +|---------|------| +| 0 | 0 | +| 5 | 20 | +| 15 | 40 | +| 20 | 30 | +| 30 | 0 | + +Figure II.2: A line graph titled '2.6666.. CAPS' showing the number of users over time. The y-axis is labeled 'User' and ranges from 0 to 45. The x-axis is labeled 'Seconds' and ranges from 0 to 30. The graph shows a piecewise linear increase from 0 users at 0 seconds to 20 users at 5 seconds, then to 40 users at 15 seconds, then a decrease to 30 users at 20 seconds, and finally a decrease to 0 users at 30 seconds. The text 'Q.3932.2(15)\_FII.2' is in the bottom right corner. + +Figure II.2 + +# Appendix III + +## Examples for test reports + +(This appendix does not form an integral part of this Recommendation.) + +### III.1 Example of a call detail report + +#### CALL DETAIL REPORT + +Test Name: Basic call + +Start time: + +Stop time: + +| Date | Time | Call ID | Server | Chan | Status | Called number | Len | Lat ms | T1 | T2 | T3 | T4 | +|------|------|---------|--------|------|--------|---------------|-----|--------|----|----|----|----| +| | | | | | | | | | | | | | +| | | | | | | | | | | | | | + +| AVERAGE | | | | | | | | | | +|---------|------|------------------|---------------|-------------|------------|----|----|----|----| +| Date | Time | Calls successful | Calls failed: | Call length | Latency ms | T1 | T2 | T3 | T4 | +| | | | | | | | | | | + +### III.2 Example of a call summary report + +#### CALL SUMMARY REPORT + +Test name: Basic call + +Start time: + +Stop time: + +| Server | Channel | Attempts | Successful | Failure | Call length (s) | Connect latency (ms) | +|--------|---------|----------|------------|---------|-----------------|----------------------| +| | | | | | | | + +### III.3 Example of a voice summary report + +Test name: VQ TEST + +Start time: + +Stop time: + +#### SPEECH LATENCY REPORT + +| Server | Channel | Number of tests | Average speech latency | +|--------|---------|-----------------|------------------------| +| | | | | +| | | | | +| | | | | + +Total number of tests: + +Total average speech latency: + +#### DTMF REPORT + +| Server | Channel | Number of failures | +|--------|---------|--------------------| +| | | | +| | | | +| | | | + +**Total number of tests:** + +#### **PESQ/POLQA REPORT** + +| Server | Channel | Number of tests | Average PESQ/POLQA score | Average offset | +|------------------------|----------------|------------------------|---------------------------------|-----------------------| +| | | | | | +| | | | | | +| | | | | | +| Total Averages: | | | | | + +### **III.4 Example of a voice quality detail report** + +Test name: VQ TEST + +Packetsphere test: + +Start time: + +Stop time: + +#### **SPEECH LATENCY REPORT** + +| TimeStamp | Call ID | Server | Channel | Speech lat | +|------------------|----------------|---------------|----------------|-------------------| +| | | | | | +| | | | | | + +**Number of speech latency tests:** + +**Average: (ms)** + +**Minimum: (ms)** + +**Maximum: (ms)** + +#### **DTMF REPORT** + +| TimeStamp | Call ID | Server | Channel | Expected digits | Received digits | +|------------------|----------------|---------------|----------------|------------------------|------------------------| +| | | | | | | + +**Number of DTMF test failures:** + +#### **PESQ REPORT** + +| TimeStamp | Call ID | Server | Channel | PESQ/POLQA value | Offset time | Prompt name | +|------------------|----------------|---------------|----------------|-------------------------|--------------------|--------------------| +| | | | | | | | +| | | | | | | | + +| | Value | Offset time | +|----------------|--------------|--------------------| +| Total Average: | | | +| Minimum | | | +| Maximum | | | + +**Number of PESQ/POLQA tests:** + +**PESQ/POLQA score above threshold:** + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3940-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f92b75df78ccc43448cad781ca430a0609d30aa --- /dev/null +++ b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3379c0fa2819bf6ced3fa0871d6b10defebebd1319fbded3e79b3c47bae2b93b +size 4115 diff --git a/marked/Q/T-REC-Q.3940-201801-I_PDF-E/19582bb3a35dfc4bcab8f239c83c229a_img.jpg b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/19582bb3a35dfc4bcab8f239c83c229a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cc6a2db97e744499d3f82a7153f13e8bc770d19 --- /dev/null +++ b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/19582bb3a35dfc4bcab8f239c83c229a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b374e3d1d69f3b2926f5247d16283d719a7426c5bd7769997d17d6c013df3a8e +size 79560 diff --git a/marked/Q/T-REC-Q.3940-201801-I_PDF-E/3d1ae2a6b8a50db31e4930b5da97fc95_img.jpg b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/3d1ae2a6b8a50db31e4930b5da97fc95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b5b1005ee5712a24453d15cf5c02c06edd46ae9 --- /dev/null +++ b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/3d1ae2a6b8a50db31e4930b5da97fc95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5c001a0ed896c9de41b523f900502cb1f2992d7ec151be175ba8926f3b7f718 +size 51252 diff --git a/marked/Q/T-REC-Q.3940-201801-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c30cf27ab037531e3d38bd8d0690acd109234f1 --- /dev/null +++ b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d5606e37f33a0153cec4b06a11ca38e5e4c1f781062c300140c08244ebe763d +size 108387 diff --git a/marked/Q/T-REC-Q.3940-201801-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..539f30e969c7fa0be965028413b040159fa4cce9 --- /dev/null +++ b/marked/Q/T-REC-Q.3940-201801-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eeb17d33bdc1081ae0103cf75f4abc6dc3c28e904cccac25c7316f4b98e3646e +size 80115 diff --git a/marked/Q/T-REC-Q.3941.3-201106-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3941.3-201106-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e0769a3e88767571f1d6d3b379af299894d8717a --- /dev/null +++ b/marked/Q/T-REC-Q.3941.3-201106-I_PDF-E/raw.md @@ -0,0 +1,177 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3941.3** + +(06/2011) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Testing for NGN networks + +--- + +**Network integration testing between SIP and +ISDN/PSTN network signalling protocols – +Part 3: Test suite structure and test purposes +for SIP-SIP** + +Recommendation ITU-T Q.3941.3 + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3649 | +| NGN applications | Q.3700–Q.3849 | +| Testing for NGN networks | Q.3900–Q.3999 | + +For further details, please refer to the list of ITU-T Recommendations. + +### **Recommendation ITU-T Q.3941.3** + +# **Network integration testing between SIP and ISDN/PSTN network signalling protocols – Part 3: Test suite structure and test purposes for SIP-SIP** + +## **Summary** + +Recommendation ITU-T Q.3941.3 specifies the test suite structure and test purposes (TSS&TP) for network integration testing (NIT) to verify the overall compatibility of IMS networks. For IMS, SIP and SDP specific terminology, reference shall be made to ETSI TS 124 229 and RFC 3261, respectively. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3941.3 | 2011-06-29 | 11 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2011 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +### Recommendation ITU-T Q.3941.3 + +## Network integration testing between SIP and ISDN/PSTN network signalling protocols – Part 3: Test suite structure and test purposes for SIP-SIP + +## 1 Scope + +This Recommendation specifies the test suite structure and test purposes (TSS&TP) for network integration testing (NIT) to verify the overall compatibility of IMS networks. For IMS, SIP and SDP specific terminology, reference shall be made to [ETSI TS 124 229] and RFC 3261, respectively. + +This Recommendation is part 3 of a multi-part deliverable covering network integration testing between SIP and ISDN/PSTN network signalling protocols: + +- Part 1: Test suite structure and test purposes for SIP-ISDN. +- Part 2: Abstract test suite and partial protocol implementation extra information for testing proforma specification for SIP-ISDN. +- Part 3: Test suite structure and test purposes for SIP-SIP. +- Part 4: Abstract test suite and partial protocol implementation extra information for testing proforma specification for SIP-SIP. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ETSI TS 124 229] ETSI TS 124 229 (2011), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 9)*. +- [ETSI TS 186 001-3] ETSI TS 186 001-3 (2010), *IMS Network Testing (INT); Network Integration Testing; Part 3: Test Suite Structure and Test Purposes (TSS&TP) for SIP-SIP*. + +## 3 Endorsement + +The text of [ETSI TS 186 001-3] was approved by ITU-T as the basis for Recommendation ITU-T Q.3941.3 as modified below. + +## **4        Modifications** + +### **Page 5, Intellectual Property Rights** + +Delete the whole section. + +### **Page 5, Foreword** + +Delete the whole section. + +### **Page 6, Scope** + +Replace the whole clause with the following: + +"1 Scope, See clause 1, Scope, of Recommendation ITU-T Q.3941.3" + +### **Page 142, History** + +Delete the whole section. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3941.4-201106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3941.4-201106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..647c80548c08886c4187332e3c71529c97e7a092 --- /dev/null +++ b/marked/Q/T-REC-Q.3941.4-201106-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a714270e2101b36cfb0bc037b45130e7e395251ac65b06a62efb2a46b71474c +size 4002 diff --git a/marked/Q/T-REC-Q.3962-202312-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60acec7bec83d2800115012ee723a2a5f09ada80 --- /dev/null +++ b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52b95ea1aa61b8f88a6564fa79e9b6ad0415f3fc516c6acfa9232a61e5ec3cc1 +size 24068 diff --git a/marked/Q/T-REC-Q.3962-202312-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbd5d1c6813cf5a62fc776ff7cd10e990acd806c --- /dev/null +++ b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11233a9e8cf1cb4338abff84243d8b4dd804312c3b17781bae3b0864008bd610 +size 40864 diff --git a/marked/Q/T-REC-Q.3962-202312-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc5d9a726d23ef6b09cf0b173357673bc4d4c3b4 --- /dev/null +++ b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb612d8f5175aa22a098572d70c1e5cd454f9f7334052ffbb605453f3a6c48ca +size 127982 diff --git a/marked/Q/T-REC-Q.3962-202312-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25f8fbfaef317942ed3102c74b40a7d42f80608b --- /dev/null +++ b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cab7dcabfe939b223d97242d8523e461968d21f7c5432693c30a64f2d95521 +size 7050 diff --git a/marked/Q/T-REC-Q.3962-202312-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac6a15741d64a1844d7e7acae9618652a41529b2 --- /dev/null +++ b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaad63a2371be2ba62ef8882507fca5859a9f778e34d8fa20f379851b2612f5f +size 130832 diff --git a/marked/Q/T-REC-Q.3962-202312-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a646ed42d602e8add65837c3138889191819f00a --- /dev/null +++ b/marked/Q/T-REC-Q.3962-202312-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:553a3e230069cdb22ded65acaa6b36b2988dcd35343b05c694b662cdac88167a +size 129911 diff --git a/marked/Q/T-REC-Q.4001.3-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4001.3-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0d7f14aca40a542ae4e49201d2ae14e29e2694c8 --- /dev/null +++ b/marked/Q/T-REC-Q.4001.3-201602-I_PDF-E/raw.md @@ -0,0 +1,180 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4001.3** + +(02/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**IMS specific use of session initiation protocol +and session description protocol; Conformance +testing – Part 3: Network side; Abstract test +suite and protocol implementation extra +information for testing** + +Recommendation ITU-T Q.4001.3 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| Testing specifications for next generation networks | Q.3900–Q.3999 | +| Testing specifications for SIP-IMS | Q.4000–Q.4039 | +| Testing specifications for Cloud computing | Q.4040–Q.4059 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.4001.3 + +## IMS specific use of session initiation protocol and session description protocol; Conformance testing – Part 3: Network side; Abstract test suite and protocol implementation extra information for testing + +## Summary + +Recommendation ITU-T Q.4001.3 v.1 (2016) specifies Part 3 of the abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma specification on the network side for testing compliance to Recommendation ITU-T Q.3403 v.1. + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4001.3, and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +This Recommendation endorses ETSI TS 102 790-3 V3.1.1 (2014-07) "Core Network and Interoperability Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; (3GPP Release 10); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification”. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4001.3 v.1 | 2016-02-13 | 11 | 11.1002/1000/12729 | + +## Keywords + +Abstract test suite, ATS, IP multimedia subsystem, IMS, network side, PIXIT, session description protocol, SDP, session initiation protocol, SIP, testing, user side. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Recommendation ITU-T Q.4001.3 + +## IMS specific use of session initiation protocol and session description protocol; Conformance testing – Part 3: Network side; Abstract text suite and protocol implementation extra information for testing + +## 1 Scope + +This Recommendation is part 3 of the testing specifications for basic call on IMS basis. It specifies the abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma specification which can be used for testing on network side against [ITU-T Q.3403 v.1]. + +The Recommendation endorses ETSI TS 102 790-3 V3.1.1 (2014-07), "Core Network and Interoperability Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; (3GPP Release 10); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification". + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.3403 v.1] Recommendation ITU-T Q.3403 v.1 (2016), *IP multimedia call control protocol based on the session initiation protocol and the session description protocol – Basic call: Requirements for the user side and the network side.* +- [ETSI TS 102 790-3 V3.1.1] ETSI TS 102 790-3 V3.1.1 (2014-07), *Core Network and Interoperability Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; (3GPP Release 10); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification.* + +## 3 Definitions + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +- ATS Abstract Test Suite +IMS IP Multimedia Subsystem +IP Internet protocol + +PIXIT Protocol Implementation extra Information for Testing + +SDP Session Description Protocol + +SIP Session Initiation Protocol + +## **5 Conventions** + +None. + +## **6 Endorsement** + +[ETSI TS 102 790-3 V3.1.1]. + + + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4004.1-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4004.1-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6c175999d5e193ebc11d7a928fac841cbc55afae --- /dev/null +++ b/marked/Q/T-REC-Q.4004.1-201602-I_PDF-E/raw.md @@ -0,0 +1,425 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4004.1** + +(02/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Communication diversion using IP multimedia +core network subsystem; Conformance testing +– Part 1: Network side and user side, Protocol +implementation conformance statement** + +Recommendation ITU-T Q.4004.1 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| Testing specifications for next generation networks | Q.3900–Q.3999 | +| Testing specifications for SIP-IMS | Q.4000–Q.4039 | +| Testing specifications for Cloud computing | Q.4040–Q.4059 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.4004.1 + +## Communication diversion using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement + +## Summary + +Recommendation ITU-T 4004.1 v.1 (2016) is part 1 of a multi-part deliverable covering communication diversion (CDIV). The Recommendation specifies the protocol implementation conformance statement (PICS) for communications diversion (CDIV) services described in Recommendation ITU-T Q.3620 v.1. + +The communications diversion (CDIV) services enables diverting user, to divert the communications addressed to them to another destination. + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4004.1 and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4004.1 v.1 | 2016-02-13 | 11 | 11.1002/1000/12736 | + +## Keywords + +Communication diversion, CDIV, IP multimedia subsystem, IMS, network side contents, session description protocol, SDP, session initiation protocol, SIP, testing, test purposes, TP, test suite structure, TSS, user side. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Protocol implementation conformance statement proforma..... | 3 | +| 5.1 Instructions for completing the PICS proforma ..... | 3 | +| 5.2 Identification of the implementation ..... | 4 | +| 5.3 PICS proforma tables ..... | 5 | + + + +## Recommendation ITU-T Q.4004.1 + +## Communication diversion using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement + +# 1 Scope + +The present Recommendation specifies the protocol implementation conformance statement (PICS) for communications diversion (CDIV) services, [ITU-T Q.3620 v1]. + +The communications diversion (CDIV) services enables diverting user, to divert the communications addressed to them to another destination. + +The present Recommendation is part 1 of a multi-part deliverable covering communication diversion (CDIV), as identified below: + +**Part 1: "Protocol implementation conformance statement (PICS)";** + +Part 2: "Test suite structure and test purposes; Network side (TSS&TP)"; + +Part 3: "Test suite structure and test purposes; User side (TSS&TP)"; + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.3617 v.1] Recommendation ITU-T Q.3617 v.1 (2015), *Terminating identification presentation and terminating identification restriction using IP multimedia core network subsystem. Protocol specification.* +- [ITU-T Q.3618 v.1] Recommendation ITU-T Q.3618 v.1 (2015), *Originating identification presentation and originating identification restriction using IP multimedia core network subsystem—Protocol specification.* +- [ITU-T Q.3620 v.1] Recommendation ITU-T Q.3620 v.1 (2016), *Communication diversion (CDIV) using IP multimedia core network subsystem— Protocol specification.* +- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts.* +- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements.* +- [ETSI TS 124 611] ETSI TS 124 611 (2012): *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.611 version 10.2.0 Release 10).* + +[ETSI TS 124 629] ETSI TS 124 629 (2013): *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 version 10.2.0 Release 10).* + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------| +| ATS | Abstract Test Suite | +| CDIV | Communication Diversion | +| CDIVN | Communication Diversion Notification | +| CFB | Communication Forwarding Busy | +| CFNL | Communication Forwarding on No Logged-in | +| CFNR | Communication Forwarding No Reply | +| CFU | Communication Forwarding Unconditional | +| ICB | Incoming Communications Barring | +| ICS | Implementation Conformance Statement | +| IP | Internet Protocol | +| IUT | Implementation Under Test | +| OCB | Outgoing Communication Barring | +| OIP | Originating Identification Presentation | +| OIR | Originating Identification Restriction | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SIP | Session Initiation Protocol | +| SUT | System Under Test | +| TIP | Terminating Identification Presentation | +| TIR | Terminating Identification Restriction | +| TP | Test Purpose | +| UE | User Equipment | +| URI | Universal Resource Identifier | + +# **5 Protocol implementation conformance statement proforma** + +## **5.1 Instructions for completing the PICS proforma** + +### **5.1.1 More detailed instructions are given at the beginning of the different clauses of the PICS proforma** + +The supplier of the implementation shall complete the protocol implementation conformance statement (PICS) proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5. + +The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in specifications [ITU-T Q.3620 v.1], [ETSI TS 124 611] and [ETSI TS 124 629] may provide information about the implementation in a standardized manner. + +The PICS proforma is subdivided into clauses for the following categories of information: + +- instructions for completing the PICS proforma; +- identification of the implementation; +- product supplier; +- client; +- PICS contact person; +- PICS proforma tables (containing the global statement of conformance). + +### **5.1.2 Abbreviations and conventions** + +The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in [ITU-T X.296]. + +#### **Item column** + +- It contains a number that identifies the item in the table. + +#### **Item description column** + +- It describes each respective item (e.g. parameters, timers, etc.). + +#### **Reference column** + +- It gives reference to the communication diversion (CDIV) specification [ITU-T Q.3620 v.1], except where explicitly stated otherwise. + +#### **Status column** + +- The following notations, defined in [ITU-T X.296], are used for the status column: +m mandatory – the capability is required to be supported. +n/a not applicable – in the given context, it is impossible to use the capability. No answer is required in the support column. +o optional – the capability may be supported or not. +o.i qualified optional – for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. +ci conditional – the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. + +#### Support column + +- The support column shall be filled in by the supplier of the implementation. The following common notations, defined in [ITU-T X.296], are used for the support column: + +Y or y supported by the implementation. + +N or n not supported by the implementation. + +N/A or n/a no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status). + +## 5.2 Identification of the implementation + +### 5.2.0 General introduction + +Identification of the implementation under test (IUT) and the system in which it resides – the system under test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. + +The product supplier information and client information should both be filled in if they are different. + +A person who can answer queries regarding information supplied in the ICS should be named as the contact person. + +### 5.2.1 Date of the statement + +| | | +|------------------------|--| +| Date of the statement: | | +|------------------------|--| + +### 5.2.2 Implementation under test (IUT) identification + +| | | +|--------------|--| +| IUT name: | | +| IUT version: | | + +### 5.2.3 System under test (SUT) identification + +| | | +|-------------------------|--| +| SUT name: | | +| Hardware configuration: | | +| Operating system: | | + +### 5.2.4 Product supplier + +| | | +|-------------------|--| +| Name: | | +| Address: | | +| Telephone number: | | + +| | | +|-------------------------|--| +| Facsimile number: | | +| Additional information: | | + +### 5.2.5 Client + +| | | +|-------------------------|--| +| Name: | | +| Address: | | +| Telephone number: | | +| Facsimile number: | | +| Additional information: | | + +### 5.2.6 PICS contact person + +| | | +|-------------------------|--| +| Name: | | +| Telephone number: | | +| Facsimile number: | | +| Additional information: | | + +## 5.3 PICS proforma tables + +### 5.3.1 Global statement of conformance + +| | | +|---------------------------------------------|-----------------| +| | (Yes/No) | +| Are all mandatory capabilities implemented? | | + +### 5.3.2 Service capabilities + +**Table 1 – Communication diversion services** + +| Item | Item description | Reference | Status | Support | +|----------|------------------------------------------------------------|------------------------------------|--------|---------| +| 1 | Communication Forwarding Unconditional (CFU) is supported? | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | +| 2 | Communication Forwarding on Busy user (CFB) is supported? | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | +| 3 | Communication Forwarding on No Reply (CFNR) is supported? | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | + +**Table 1 – Communication diversion services** + +| Item | Item description | Reference | Status | Support | +|------|-----------------------------------------------------------------|------------------------------------|--------|---------| +| 4 | Communication Deflection immediate response (CDi) is supported? | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | +| 5 | Communication Deflection during alerting (CDa) is supported? | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | +| 6 | Communication Forwarding on Not Logged-in (CFNL) is supported? | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | +| 7 | Communication Forwarding on Subscriber Not Reachable (CFNRc) | Clause 4.2.1 of [ITU-T Q.3620 v.1] | o | | + +**Table 2 – Network capabilities** + +| Item | Item description | Reference | Status | Support | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|--------|---------| +| 1 | Is the served user notified by sending a MESSAGE request after a period of time according to the timer value $T_{CDIV\_IND}$ as defined in clause 4.8.3 that can be provided by the user? | Clause 4.5.2.6.5 of [ITU-T Q.3620 v.1] | o | | +| 2 | The AS initiates an announcement to be included towards the originating user in order to inform about the diversion? | Clause 4.5.2.6.4 of [ITU-T Q.3620 v.1] | o | | +| 3 | The Communication Diversion Notification (CDIVN) procedure of the served user is supported? | Clause 4.5.2.6.5.1 of [ITU-T Q.3620 v.1] | o | | +| 4 | Is a diverting user informed periodically with a MESSAGE request the information where the call is diverted to? | Clause 4.5.2.6.5 of [ITU-T Q.3620 v.1] | o | | +| 5 | [1/3] Is the served user in case of CFNR furthermore alerted if the alerting indication is received from the diverted-to user ( ringing continues )? | Clause 4.5.2.6.3 of [ITU-T Q.3620 v.1] | o | | +| 6 | Served user communication retention on invocation of diversion (CFNR). Retain call to the served user until alerting begins at the diverted-to user? | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | o | | +| 7 | Served user communication retention on invocation of diversion (CFNR). Clear call to the served user on invocation of call diversion | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | o | | +| 8 | Served user communication retention when forwarding is rejected at forwarded-to user. Continue to alert the forwarding user | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | o | | +| 9 | Served user communication retention when forwarding is rejected at forwarded-to user. No action at the forwarding user | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | o | | +| 10 | Served user communication retention on invocation of diversion (CFNR). Clear call to the served user when the diverted-to-user has accepted the communication request | Clause 4.5.2.6.3 of [ITU-T Q.3620 v.1] | o | | + +**Table 3 – Subscription options** + +| Item | Item description | Reference | Status | Support | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------|---------| +| 1 | Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user)? | Table 4.3.1.1 of [ITU-T Q.3620 v.1] | o | | +| 2 | Served user receives reminder notification on outgoing communication that CDIV is currently activated? | Table 4.3.1.1 of [ITU-T Q.3620 v.1] | o | | +| 3 | Originating user receives notification that his communication has been diverted (forwarded or deflected)? | Table 4.3.1.1 of [ITU-T Q.3620 v.1] | o | | +| 4 | Served user allows the presentation of diverted to URI to originating user in diversion notification? | Table 4.3.1.1 of [ITU-T Q.3620 v.1] | o | | +| 5 | Served user allows the presentation of his/her URI to originating user in diversion notification? | Table 4.3.1.1 of [ITU-T Q.3620 v.1] | o | | +| 6 | Served user allows the presentation of his/her URI to diverted-to user ? | Table 4.3.1.1 of [ITU-T Q.3620 v.1] | o | | + +**Table 4 – Simulation services** + +| Item | Item description | Reference | Status | Support | +|------|-----------------------------------------------------------------------------------|---------------------------------------|--------|---------| +| 1 | Does the served user subscribe to the OIR service in permanent mode? | Clause 4.5.2.4 of [ITU-T Q.3618 v.1] | o | | +| 2 | Does the terminating user subscribe to the override category for the OIR service? | Clause 4.5.2.9 of [ITU-T Q.3618 v.1] | o | | +| 3 | Does the served user subscribe to the TIR service? | Clause 4.5.2.9 of [ITU-T Q.3617 v.1] | o | | +| 4 | Does the originating user subscribe to the override category for the TIR service? | Clause 4.5.2.4 of [ITU-T Q.3617 v.1] | o | | +| 5 | The Outgoing Communications Barring (OCB) service is supported? | Clause 4.5.2.4.1 of [ETSI TS 124 611] | o | | +| 6 | The Incoming Communications Barring (ICB) service is supported? | Clause 4.5.2.6.1 of [ETSI TS 124 611] | o | | +| 7 | The Explicit Communication Transfer simulation service is supported? | Clause 4.2.1 of [ETSI TS 124 629] | o | | + +**Table 5 – User Equipment capabilities** + +| Item | Item description | Reference | Status | Support | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|--------|---------| +| 1 | Is the UE able to receive a 181 Call is being Forwarded response, and able to display the information of the History-Info header if included? | Clause 4.5.2.1 of [ITU-T Q.3620 v.1] | o | | +| 2 | Is the UE able to receive a 180 Ringing response and able to display the information of the History-Info header if included? | Clause 4.5.2.7 of [ITU-T Q.3620 v.1] | o | | +| 3 | Is the UE able to receive a 200 OK INVITE final response and able to display the information of the History-Info header if included? | Clause 4.5.2.7 of [ITU-T Q.3620 v.1] | o | | +| 4 | Is the User Equipment able to receive a History-Info header in an INVITE request and able to display the information of the History-Info header? | Clauses 4.5.2.15, 4.5.2.6.2 of [ITU-T Q.3620 v.1] | o | | +| 5 | Is the User Equipment able to send the previously stored History-Info header in a 180 Ringing provisional response? | Clause 4.5.2.7 of [ITU-T Q.3620 v.1] | o | | +| 6 | Is the User Equipment able to send the previously stored History-Info header in a 200 OK INVITE final response? | Clause 4.5.2.7 of [ITU-T Q.3620 v.1] | o | | +| 7 | Is the User Equipment able to receive communication diversion notification information for the served user in a MESSAGE request and able to display the notification information? | Clause 4.5.2.6.4 of [ITU-T Q.3620 v.1] | o | | +| 8 | Is the User Equipment able to subscribe the receive communication diversion notification information for the served user in a MESSAGE request and able to display the notification information? | Clause 4.5.2.6.5 of [ITU-T Q.3620 v.1] | o | | + +**Table 6 – Values** + +| Item | Item description | Reference | Status | Support | Values | | +|------|-------------------------------------------------------------------------------------------------------------|-------------------------------------|--------|---------|-------------------------|-----------| +| | | | | | allowed | supported | +| 1 | CFNR timer | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | c2 | | service provider option | [sec] | +| 2 | CDIVN Buffer Timer; Timer Value for AS to store CDIVN, if it cannot be delivered as per CDIVN Configuration | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | c1 | | service provider option | [sec] | +| 3 | Maximum number of diverted connections | Table 4.3.1.2 of [ITU-T Q.3620 v.1] | m | | service provider option | [number] | + +NOTE: c1: IF 2/10 THEN m ELSE n/a. +c2: IF 1/3 THEN m ELSE n/a. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4005.2-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4005.2-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7ef1dac27580977bae8b12335e53f494240c8a18 --- /dev/null +++ b/marked/Q/T-REC-Q.4005.2-201602-I_PDF-E/raw.md @@ -0,0 +1,903 @@ + + +# **ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **Q.4005.2** + +(02/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Conference service using IP multimedia core +network subsystem; Conformance testing – +Part 2: Network side; Test suite structure and +test purposes** + +Recommendation ITU-T Q.4005.2 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| Testing specifications for next generation networks | Q.3900–Q.3999 | +| Testing specifications for SIP-IMS | Q.4000–Q.4039 | +| Testing specifications for Cloud computing | Q.4040–Q.4059 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T Q.4005.2** + +## **Conference service using IP multimedia core network subsystem; Conformance testing – Part 2: Network side; Test suite structure and test purposes** + +## **Summary** + +Recommendation ITU-T Q 4005-2 v.1 (2016) is a part 2 of the testing specifications for conference service (CONF) implemented on IP multimedia subsystem (IMS) basis on the network side. The standard specifies the test suite structure and test purposes (TSS&TP) which can be used for testing against the draft Recommendation ITU-T Q.3621 v.1. + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4005.2 and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +## **History** + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4005.2 v.1 | 2016-02-13 | 11 | 11.1002/1000/12739 | + +## **Keywords** + +Conference service, CONF, IP multimedia subsystem, IMS, network side, session description protocol, SDP, session initiation protocol, SIP, testing, test purposes, TP, test suite structure, TSS, user side. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Test suite structure (TSS) ..... | 2 | +| 5.1 Configuration..... | 2 | +| 6 Test purposes (TP)..... | 3 | +| 6.1 Introduction ..... | 3 | +| 6.2 Signalling requirements..... | 4 | +| 6.2 Interaction with other supplementary services ..... | 18 | + + + +## Recommendation ITU-T Q.4005.2 + +## Conference service using IP multimedia core network subsystem; Conformance testing – Part 2: Network side; Test suite structure and test purposes + +# 1 Scope + +This Recommendation specifies the test suite structure and test purposes (TSS&TP) for CONF service [ITU-T Q.3621 v.1] for the network side. + +This Recommendation is part 2 of a multi-part deliverable covering CONF service, as identified below: + +- Part 1: "Protocol implementation conformance statement (PICS)"; +- **Part 2: "Test suite structure and test purposes; Network side (TSS&TP)";** +- Part 3: "Test suite structure and test purposes; User Side (TSS&TP)". + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.3621 v.1] Recommendation ITU-T Q.3621 v.1 (2016), *CONF using IP multimedia core network subsystem – Protocol specification*. +- [ITU-T Q.4005.1 v.1] Recommendation ITU-T Q.4005.1 v.1 (2016), *Conference service using IP multimedia core network subsystem; Conformance testing – Part 1: Network side; User side, protocol implementation conformance statement*. +- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [ETSI TS 124 147] ETSI TS 124 147 V10.5.0 (2015), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 version 10.5.0 Release 10)*. + +# 3 Definitions + +This Recommendation uses the following terms defined elsewhere: + +For the purposes of this Recommendation, the terms and definitions given in [ITU-T X.290] and [ITU-T X.296] apply: + +- 3.1 implementation under test (IUT):** Refer to [ITU-T X.290]. +- 3.2 PICS proforma:** Refer to [ITU-T X.290]. +- 3.3 point of control and observation:** Refer to [ITU-T X.290]. +- 3.4 protocol implementation conformance statement (PICS):** Refer to [ITU-T X.290]. + +**3.5 system under test (SUT):** Refer to [ITU-T X.290]. + +**3.6 test purpose (TP):** Refer to [ITU-T X.290]. + +NOTE – This may contain additional information. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +CONF Conference calling + +IUT Implementation Under Test + +SUT System Under Test + +UE User Equipment + +# 5 Test suite structure (TSS) + +**Table 1 – Test suite structure** + +| | | | +|-----------------|----------------|--------------| +| ConferenceFocus | CreateConf | CONF_N01_xxx | +| | JoinConf | CONF_N02_xxx | +| | InviteToConf | CONF_N03_xxx | +| | LeaveConf | CONF_N04_xxx | +| | RemoveFromConf | CONF_N05_xxx | +| | TerminateConf | CONF_N06_xxx | +| | | | +| Interaction | TIR | CONF_N08_xxx | +| | OIR | CONF_N09_xxx | +| | ACR-CB | CONF_N10_xxx | +| | | | + +## 5.1 Configuration + +The scope of this Recommendation is to test the signalling and procedural aspects of the stage 3 requirements as described in [ITU-T Q.3621 v.1]. The stage 3 description respects the requirements to several networks. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. + +### 5.1.1 Testing of the AS + +The AS entity is responsible for performing and managing services. The IP multimedia subsystem service control (ISC) interface is the appropriate access point for testing (see Figure 5.1.1-1). + +![Diagram showing the applicable interface to test AS functionalities. A central green box labeled 'Application server' and 'Implementation under test' is connected via ISC interfaces to two cyan boxes labeled 'Test system' on either side.](6078636a87fbe0e699aab4a6fddd15d7_img.jpg) + +``` +graph LR; + TS1[Test system] --- ISC1[ISC] --- AS[Application server +Implementation under test]; + AS --- ISC2[ISC] --- TS2[Test system]; +``` + +Diagram showing the applicable interface to test AS functionalities. A central green box labeled 'Application server' and 'Implementation under test' is connected via ISC interfaces to two cyan boxes labeled 'Test system' on either side. + +Q.4005.2v1(16)\_F5.1.1-1 + +**Figure 5.1.1-1 – Applicable interface to test AS functionalities** + +If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (see Figure 5.1.1-2). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. + +![Diagram showing a central green box labeled 'CSCF (and/or AS) Implementation under test' connected to two cyan boxes labeled 'Test system'. The connections are labeled 'Mw, Mg, Mx'.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +``` + +graph LR + TS1[Test system] ---|Mw, Mg, Mx| CSCF[CSCF (and/or AS) +Implementation under test] + CSCF ---|Mw, Mg, Mx| TS2[Test system] + +``` + +Diagram showing a central green box labeled 'CSCF (and/or AS) Implementation under test' connected to two cyan boxes labeled 'Test system'. The connections are labeled 'Mw, Mg, Mx'. + +Q.4005.2v1(16)\_F5.1.1-2 + +**Figure 5.1.1-2 – Applicable interfaces for tests using a (generic) NNI interface** + +# 6 Test purposes (TP) + +## 6.1 Introduction + +The reference column makes reference to [ITU-T Q.3621 v.1], except where explicitly stated otherwise. + +### 6.1.1 TP naming convention + +Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the test suite structure (TSS). Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Table 2). + +**Table 2 – TP identifier naming convention scheme** + +| Identifier: __ | | | +|-------------------------------------|--------------------------|-------------------------------------------------------------------| +| | = supplementary service: | e.g. "CONF" | +| | = type of IUT: | U            User
N            Network
yyy          service | +| | = group | 2 digit field representing group reference according to TSS | +| | = sequential number | (001-999) | + +### 6.1.2 Test strategy + +As the base standard [ITU-T Q.3621 v.1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the protocol implementation conformance statement (PICS) specification [ITU-T Q.4005.1 v.1]. + +## 6.2 Signalling requirements + +### 6.2.1 Conference focus + +#### 6.2.1.1 Conference creation + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------------------------|-------------------------------------------|--------------|--------------|--|--------|---|--|---------------------|-------|--|-----|---|--|---------------|-------|--|--------------------|---|--|--------|---|--|---------------|---|--| +| TSS
ConferenceFocus/CreateConf | TP
CONF_N01_001 | Reference
5.3.2.3.1, 5.3.3 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference creation with a conference factory URI. Conference event package subscribed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). In addition the conference participant subscribes to the conference event package and receives a NOTIFY request describing the conference status. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE: Request URI indicating the conference factory URI
200 OK: conference URI and "isfocus" feature parameter included in Contact header field
SUBSCRIBE: Request URI indicating the conference URI
Event header contains "conference"
NOTIFY: Event contains conference ; Subscription-State contains active ; expires=xxxx | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus
INVITE →

200 OK (INVITE)
←
ACK →

SUBSCRIBE
→
200 OK (SUBSCRIBE) ←
NOTIFY ←
200 OK NOTIFY →
Apply post test routine
| | | | ISC#1 | Focus | | INVITE | → | |
200 OK (INVITE) |
← | | ACK | → | |
SUBSCRIBE |
→ | | 200 OK (SUBSCRIBE) | ← | | NOTIFY | ← | | 200 OK NOTIFY | → | | +| ISC#1 | Focus | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
← | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
SUBSCRIBE |
→ | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (SUBSCRIBE) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------|-------------------------------------------|--------------|--------------|--|--------|---|--|---------------------|-------|--|-----|---|--| +| TSS
ConferenceFocus/CreateConf | TP
CONF_N01_002 | Reference
5.3.2.3.1of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | +| Test purpose
Conference creation with a conference factory URI. Conference event package not subscribed. | | | | | | | | | | | | | | | | +| Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant does not subscribe to the conference event package. | | | | | | | | | | | | | | | | +| SIP header values:
INVITE: Request URI indicating the conference factory URI
200 OK: conference URI and "isfocus" feature parameter included in Contact header field | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus
INVITE →

200 OK (INVITE)
←
ACK →
Apply post test routine
| | | | ISC#1 | Focus | | INVITE | → | |
200 OK (INVITE) |
← | | ACK | → | | +| ISC#1 | Focus | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| TSS
ConferenceFocus/CreateConf | TP
CONF_N01_003 | Reference
5.3.2.3.2, 5.3.3 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------------------------|-------------------------------------------| +| Test purpose
Conference creation with a conference URI. Conference event package subscribed. | | | | +| Ensure that a conference can be created by a UE using the conference URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). In addition the conference participant subscribes to the conference event package and receives a NOTIFY request describing the conference status. | | | | +| SIP header values:
INVITE: Request URI indicating the conference URI
200 OK: "isfocus" feature parameter included in Contact header field
conference URI contained in the Contact header field
SUBSCRIBE: Request URI indicating the conference URI
Event header contains "conference"
NOTIFY: Event contains conference ; Subscription-State contains active; expires=xxxx | | | | +| Comments:
ISC#1 Focus | | | | +| INVITE | ➔ | | | +| | | | | +| 200 OK (INVITE) | ← | | | +| ACK | ➔ | | | +| | | | | +| SUBSCRIBE | ➔ | | | +| 200 OK (SUBSCRIBE) | ← | | | +| NOTIFY | ← | | | +| 200 OK NOTIFY | ➔ | | | +| Apply post test routine | | | | + +| TSS
ConferenceFocus/CreateConf | TP
CONF_N01_004 | Reference
5.3.2.3.2of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------|-------------------------------------------| +| Test purpose
Conference creation with a conference URI. Conference event package not subscribed. | | | | +| Ensure that a conference can be created by a UE using the conference URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant does not subscribe to the conference event package. | | | | +| SIP header values:
INVITE: Request URI indicating the conference URI
200 OK: "isfocus" feature parameter indicated in Contact header field
conference URI contained in the Contact header field | | | | +| Comments:
ISC#1 Focus | | | | +| INVITE | ➔ | | | +| | | | | +| 200 OK (INVITE) | ← | | | +| ACK | ➔ | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------|-------------------------------------------------------------|--|--------------|--|--------|---|--|----------------------|---|--|-------|---|--|--------------|---|--|--------|---|--|---------------|---|--|-----------------|---|--|-----|---|--| +| TSS
ConferenceFocus/CreateConf | TP
CONF_N01_005 | Reference
5.3.2.3.1 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2
AND PICS 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference creation with a conference factory URI. Preconditions indicated a conference URI is sent in the first provisional response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that a conference can be created by a UE using the conference factory URI. Preconditions are requested by the originating UE. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:            Request URI indicating the conference factory URI
SDP    a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv

183                conference URI contained in the Contact header field
SDP    a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=conf:qos remote sendrecv

UPDATE:
SDP    a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv

200 OK UPDATE
SDP    a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv

200 OK:            "isfocus" feature parameter included in Contact header field
conference URI contained in the Contact header field | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1
Focus
INVITE →
183 Session Progress ←
PRACK →
200 OK PRACK ←
UPDATE →
200 OK UPDATE ←
200 OK (INVITE) ←
ACK →

Apply post test routine

| | | | | Focus | | INVITE | → | | 183 Session Progress | ← | | PRACK | → | | 200 OK PRACK | ← | | UPDATE | → | | 200 OK UPDATE | ← | | 200 OK (INVITE) | ← | | ACK | → | | +| | Focus | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK PRACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UPDATE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------|-------------------------------------------|--|--------------|--|--------|---|--|-------------------------|---|--|-----|---|--| +| TSS
ConferenceFocus/CreateConf | TP
CONF_N01_006 | Reference
5.3.2.3.1of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | +| Test purpose
Conference creation with a conference factory URI not allocated in the focus, unsuccessful. | | | | | | | | | | | | | | | | +| Ensure that a conference cannot be created by a UE using a conference factory URI not allocated in the focus. The request is rejected by the focus with a 488 Not Acceptable Here final response. | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:            Request URI indicating a conference factory URI not allocated in the focus | | | | | | | | | | | | | | | | +| Comments:
ISC#1
Focus
INVITE →
488 Not Acceptable Here ←
ACK →
| | | | | Focus | | INVITE | → | | 488 Not Acceptable Here | ← | | ACK | → | | +| | Focus | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 488 Not Acceptable Here | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +#### 6.2.1.2 Joining a conference + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------------|-------------------------------------------|--------------|--------------|--------------|--|----------------------------|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|--|---------------------------------------|--|--|------------|----------|--|---------|-----|--|-------------------|---------------|--|---------|-----|--|--------------------------------|--| +| TSS
ConferenceFocus/JoinConf | TP
CONF_N02_001 | Reference
5.3.2.4.1 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Participant dial-in the conference, the conference URI is used. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1 (via ISC#1) established a conference. UE2 (via ISC#2) joins in that conference by sending an INVITE request to the conferencing AS (the conference URI is known at the UE2). The request is successful. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE 2: Request URI indicating the conference URI
18x "isfocus" feature parameter included in Contact header field
200 OK: "isfocus" feature parameter included in Contact header field
conference URI contained in the Contact header field | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
UE#2 joining in the conference
INVITE   ← INVITE 2
18x   → 18x
200 OK INVITE   → 200 OK INVITE
ACK   ← ACK
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | | Conference creation | | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | | UE#2 joining in the conference | | | INVITE   ← | INVITE 2 | | 18x   → | 18x | | 200 OK INVITE   → | 200 OK INVITE | | ACK   ← | ACK | | Apply post test routine | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE#2 joining in the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE   ← | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 18x   → | 18x | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE   → | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK   ← | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------------|-------------------------------------------|--------------|--------------|--------------|--|---------------------------------------|--|--|------------|----------|--|---------|-----|--|---------|-----| +| TSS
ConferenceFocus/JoinConf | TP
CONF_N02_002 | Reference
5.3.2.4.1 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | +| Test purpose
Participant dial-in the conference, the conference URI is not allocated, the request is rejected. | | | | | | | | | | | | | | | | | | | +| UE2 (via ISC#2) tries to join in a conference but the conference URI in the INVITE request is not allocated at the focus. The request is rejected with the final response 4xx. | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE: Request URI contained the conference URI not allocated in the focus (PIXIT) | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
UE#2 joining in the conference
INVITE   ← INVITE 2
4xx   → 4xx
ACK   ← ACK
| | | | ISC#1 | Focus | ISC#2 | | UE#2 joining in the conference | | | INVITE   ← | INVITE 2 | | 4xx   → | 4xx | | ACK   ← | ACK | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | +| | UE#2 joining in the conference | | | | | | | | | | | | | | | | | | +| | INVITE   ← | INVITE 2 | | | | | | | | | | | | | | | | | +| | 4xx   → | 4xx | | | | | | | | | | | | | | | | | +| | ACK   ← | ACK | | | | | | | | | | | | | | | | | + +#### 6.2.1.3 Inviting other users to a conference + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------|--------------|--------------|--------------|--|----------------------------|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|--|--------------------------------------------|--|-------|---------|--|--------------|----------------|--|--|---------------------------------------|--|--|------------|--------|--------|------------|--|---------------|-----------------|--|--|---------------|-------------|--|-----------------|---------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|--|--------------------------------|--| +| TSS
ConferenceFocus/InviteToConf | TP
CONF_N03_001 | Reference
5.3.2.5.2, 5.3.2.5.4 of [ETSI TS 124 147] | Selection expression
PICS 5.1/2
AND NOT PICS 5.3/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Inviting participant by sending REFER to the focus. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1 (via ISC#1) established a conference and invites UE2 (connected via ISC#2) to join into the conference. UE1 sends a REFER to the focus; the focus sends an INVITE request to UE2 to invite it to the conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER: Request URI indicating the conference URI
Refer-To contains the URI of UE2 , method=INVITE
Referred-By contains SIP URI of UE1
INVITE 2: Request URI indicating the address of UE2
The P-Asserted-Identity contains the conference URI.
conference URI and "isfocus" feature parameter indicated in Contact header field
Referred-By contains SIP or tel URI of UE1
NOTIFY 1 Event contains refer ; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying
NOTIFY 2 Event contains refer ; Subscription-State contains terminated
message/sipfrag contains SIP/2.0 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
UE#1 invites UE#2 to the conference
REFER → REFER
202 Accepted ← 202 Accepted
Focus dials out to invite UE#2
INVITE 2 → INVITE
NOTIFY ← NOTIFY 1
200 OK NOTIFY → 200 OK NOTIFY
← 180 Ringing 180 Ringing
← 200 OK INVITE 200 OK INVITE
→ ACK ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY → 200 OK NOTIFY
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | | Conference creation | | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | | UE#1 invites UE#2 to the conference | | REFER | → REFER | | 202 Accepted | ← 202 Accepted | | | Focus dials out to invite UE#2 | | | INVITE 2 → | INVITE | NOTIFY | ← NOTIFY 1 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | ← 180 Ringing | 180 Ringing | | ← 200 OK INVITE | 200 OK INVITE | | → ACK | ACK | NOTIFY | ← NOTIFY 2 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | Apply post test routine | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE#1 invites UE#2 to the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE 2 → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 180 Ringing | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------|--------------|--------------|--------------|--|----------------------------|--|----------|----------|--|-----------------|-------------------|--|-----|-------|--|--|---------------------------------------|--|--|--------------|--------|--|-------------------|---------------|--|---------|-----|--|--------------------------------|--| +| TSS
ConferenceFocus/InviteToConf | TP
CONF_N03_002 | Reference
5.3.2.5.3, 5.3.2.5.4 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2
AND PICS 5.3/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Inviting participant by sending a participant list to the focus. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1 (via ISC#1) established a conference. A participant list is contained in the INVITE to create the conference. The AS establishes a communication to the UE2 (via ISC#2) indicated in the participant list. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE 1:   Request URI=Focus


INVITE 2:   Request URI = UE#2
The P-Asserted-Identity contains the conference URI.
conference URI and "isfocus" feature parameter indicated in Contact header field | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE 1 ➔ INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK ➔ ACK
Focus dials out to invite UE#2
INVITE 2   ➔ INVITE
200 OK INVITE   ← 200 OK INVITE
ACK   ➔ ACK
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | | Conference creation | | INVITE 1 | ➔ INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | ➔ ACK | | | Focus dials out to invite UE#2 | | | INVITE 2   ➔ | INVITE | | 200 OK INVITE   ← | 200 OK INVITE | | ACK   ➔ | ACK | | Apply post test routine | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE 1 | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE 2   ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE   ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK   ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------|----------------------------------|--------------|--------------|--------------|--------------|--|-----------------------------|--|--|--|---------------------------|--|--|--|-----------------------------|--|--|--|---------------------------|--|--|--|-----------------------------------------|--|--|-------------|----------|--|--|-----------------|-------------------|--|--|-----|-------|--|--|----------------|-------|-------------|--|--------------|---|----------------|--|------------------|-------|--------------------|--|-----------------|---|-------------------|--|--|----------|-------------|--|--|-------------------|-----------------|--|--|-------|-----|--|--------------|---|----------------|--|-----------------|---|-------------------|--|----------|---|------------|--|--------------|---|----------------|--|----------------|-------|--|-------------|--------------|---|--|----------------|------------------|-------|--|--------------------|-----------------|---|--|-------------------|--|----------|--|---------------|--|-------------------|--|-------------------|--|-------|--|-------|--------------|---|--|----------------|-----------------|---|--|-------------------|----------|---|--|------------|--------------|---|--|----------------| +| ConferenceFocus/InviteToConf | CONF_N03_004 | 5.3.1.3.3, 5.3.1.5.2 of
[ETSI TS 124 147] | PICS 5.1/2
AND NOT PICS 5.3/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Three-way session creation. REFER is sent to the participants.

Ensure that it is possible that two active sessions S1 and S2 towards UE2 (via ISC#2) and UE3 (via ISC#3) are joined in a three way session by UE1 and that the existing sessions S1 and S2 can be released by the served user UE1. The remote users receive a REFER request with the Refer-To header containing the address of the Focus directly from UE1. The remote users use the URI of the Refer-To header as the Request URI of the INVITE request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER (S1): Request line=UE#2
Refer-To=Focus; method=INVITE
Referred-By=UE#1
REFER (S2): Request line=UE#3
Refer-To=Focus; method=INVITE
Referred-By=UE#1
INVITE (S4): Request URI=Focus
Referred-By=UE#1
INVITE (S5): Request URI=Focus
Referred-By=UE#1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2 ISC#3
Establish session #1
Session #1 on hold
Establish session #2
Session #2 on hold
Conference creation (session #3)
INVITE (S3) → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK

REFER (S1)
→
→ REFER
202 Accepted ← ← 202 Accepted

NOTIFY (100)
←
← NOTIFY (100)
200 OK (NOTIFY) → → 200 OK (NOTIFY)
INVITE ← INVITE (S4)
200 OK (INVITE) → 200 OK (INVITE)
ACK ← ACK
NOTIFY (200) ← ← NOTIFY (200)
200 OK (NOTIFY) → → 200 OK (NOTIFY)
BYE (S1) → → BYE (S1)
200 OK (BYE) ← ← 200 OK (BYE)

REFER (S2)
→
→ REFER
202 Accepted ← ← 202 Accepted

NOTIFY (100)
←
← NOTIFY (100)
200 OK (NOTIFY) → → 200 OK (NOTIFY)
INVITE ← ← INVITE (S5)
200 OK (INVITE) → → 200 OK (INVITE)
ACK ← ← ACK
NOTIFY (200) ← ← NOTIFY (200)
200 OK (NOTIFY) → → 200 OK (NOTIFY)
BYE (S1) → → BYE (S2)
200 OK (BYE) ← ← 200 OK (BYE)
| | | | ISC#1 | Focus | ISC#2 | ISC#3 | | Establish session #1 | | | | Session #1 on hold | | | | Establish session #2 | | | | Session #2 on hold | | | | Conference creation (session #3) | | | INVITE (S3) | → INVITE | | | 200 OK (INVITE) | ← 200 OK (INVITE) | | | ACK | → ACK | | |
REFER (S1) |
→ |
→ REFER | | 202 Accepted | ← | ← 202 Accepted | |
NOTIFY (100) |
← |
← NOTIFY (100) | | 200 OK (NOTIFY) | → | → 200 OK (NOTIFY) | | | INVITE ← | INVITE (S4) | | | 200 OK (INVITE) → | 200 OK (INVITE) | | | ACK ← | ACK | | NOTIFY (200) | ← | ← NOTIFY (200) | | 200 OK (NOTIFY) | → | → 200 OK (NOTIFY) | | BYE (S1) | → | → BYE (S1) | | 200 OK (BYE) | ← | ← 200 OK (BYE) | |
REFER (S2) |
→ | |
→ REFER | 202 Accepted | ← | | ← 202 Accepted |
NOTIFY (100) |
← | |
← NOTIFY (100) | 200 OK (NOTIFY) | → | | → 200 OK (NOTIFY) | | INVITE ← | | ← INVITE (S5) | | 200 OK (INVITE) → | | → 200 OK (INVITE) | | ACK ← | | ← ACK | NOTIFY (200) | ← | | ← NOTIFY (200) | 200 OK (NOTIFY) | → | | → 200 OK (NOTIFY) | BYE (S1) | → | | → BYE (S2) | 200 OK (BYE) | ← | | ← 200 OK (BYE) | +| ISC#1 | Focus | ISC#2 | ISC#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish session #1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Session #1 on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish session #2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Session #2 on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation (session #3) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (S3) | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
REFER (S1) |
→ |
→ REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
NOTIFY (100) |
← |
← NOTIFY (100) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | → 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE ← | INVITE (S4) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK (INVITE) → | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK ← | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY (200) | ← | ← NOTIFY (200) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | → 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (S1) | → | → BYE (S1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | ← | ← 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
REFER (S2) |
→ | |
→ REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
NOTIFY (100) |
← | |
← NOTIFY (100) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | | → 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE ← | | ← INVITE (S5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK (INVITE) → | | → 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK ← | | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY (200) | ← | | ← NOTIFY (200) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | | → 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (S1) | → | | → BYE (S2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | ← | | ← 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------|--------------|--------------|--------------|--------------|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|-------------|---|--------|--|-----------------|---|-----------------|--|-----|---|-----|--|------------|---|-------|--|--------------|---|--------------|--|--------------|---|--------------|--|-----------------|---|-----------------|--|--|--|-------------|---|--|--|-----------------|---|--|--|-----|---|--------------|---|--------------|--|-----------------|---|-----------------|--|----------|---|--|---|--------------|---|--|---|------------|---|-------|--|--------------|---|--------------|--|--------------|---|--------------|--|-----------------|---|-----------------|--|--|--|-------------|---|--|--|-----------------|---|--|--|-----|---|--------------|---|--------------|--|-----------------|---|-----------------|--|----------|---|--|---|--------------|---|--|---|--|--------------------------------|--|--| +| TSS
ConferenceFocus/InviteToConf | TP
CONF_N03_005 | Reference
5.3.1.3.3, 5.3.1.5.3,
5.3.2.5.2 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Three-way session creation. REFER is sent to the Focus. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that it is possible that two active sessions S1 and S2 towards UE2 (via ISC#2) and UE3 (via ISC#3) are joined in a three way session by UE1 and that the existing sessions S1 and S2 can be released by the served user UE1. UE1 sends two REFER requests to the conference focus which then sends INVITE requests to UE2 and UE3 containing the Referred-By header indicating UE1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER (S1): Request line=Focus
Refer-To=UE#2; method=INVITE
Referred-By=UE#1
REFER (S1): Request line=Focus
Refer-To=UE#3; method=INVITE
Referred-By=UE#1
INVITE (S4): Request URI=UE#2
Referred-By=UE#1
INVITE (S5): Request URI=UE#3
Referred-By=UE#1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2 ISC#3
Establish session #1
Session #1 on hold
Establish session #2
Session #2 on hold
Conference creation (session #3)
INVITE (S3) → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
REFER (S1) → REFER
202 Accepted ← 202 Accepted
NOTIFY (100) ← NOTIFY (100)
200 OK (NOTIFY) → 200 OK (NOTIFY)
INVITE (S4) →
200 OK (INVITE) ←
ACK →
NOTIFY (200) ← NOTIFY (200)
200 OK (NOTIFY) → 200 OK (NOTIFY)
BYE (S1) → →
200 OK (BYE) ← ←
REFER (S2) → REFER
202 Accepted ← 202 Accepted
NOTIFY (100) ← NOTIFY (100)
200 OK (NOTIFY) → 200 OK (NOTIFY)
INVITE (S5) →
200 OK (INVITE) ←
ACK →
NOTIFY (200) ← NOTIFY (200)
200 OK (NOTIFY) → 200 OK (NOTIFY)
BYE (S1) → →
200 OK (BYE) ← ←
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | ISC#3 | | Establish session #1
Session #1 on hold
Establish session #2
Session #2 on hold
Conference creation (session #3) | | | INVITE (S3) | → | INVITE | | 200 OK (INVITE) | ← | 200 OK (INVITE) | | ACK | → | ACK | | REFER (S1) | → | REFER | | 202 Accepted | ← | 202 Accepted | | NOTIFY (100) | ← | NOTIFY (100) | | 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | | | INVITE (S4) | → | | | 200 OK (INVITE) | ← | | | ACK | → | NOTIFY (200) | ← | NOTIFY (200) | | 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | BYE (S1) | → | | → | 200 OK (BYE) | ← | | ← | REFER (S2) | → | REFER | | 202 Accepted | ← | 202 Accepted | | NOTIFY (100) | ← | NOTIFY (100) | | 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | | | INVITE (S5) | → | | | 200 OK (INVITE) | ← | | | ACK | → | NOTIFY (200) | ← | NOTIFY (200) | | 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | BYE (S1) | → | | → | 200 OK (BYE) | ← | | ← | | Apply post test routine | | | +| ISC#1 | Focus | ISC#2 | ISC#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish session #1
Session #1 on hold
Establish session #2
Session #2 on hold
Conference creation (session #3) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (S3) | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER (S1) | → | REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY (100) | ← | NOTIFY (100) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE (S4) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK (INVITE) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY (200) | ← | NOTIFY (200) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (S1) | → | | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | ← | | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER (S2) | → | REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY (100) | ← | NOTIFY (100) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE (S5) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK (INVITE) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY (200) | ← | NOTIFY (200) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (S1) | → | | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | ← | | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------| +| TSS
ConferenceFocus/InviteToConf | TP
CONF_N03_006 | Reference
5.3.1.3.3, 5.3.1.5.3,
5.3.2.5.2 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | +| Test purpose
Three-way session creation. REFER is sent to the Focus. Replaces header included in the REFER. | | | | +| Ensure that it is possible that two active sessions S1 and S2 towards UE2 (via ISC#2) and UE3 (via ISC#3) are joined in a three way session by UE1 and that the existing sessions S1 and S2 can be released by the remote users UE2 and UE3. UE1 sends two REFER requests including Replaces headers to the conference focus which then sends INVITE requests to UE2 and UE3 containing the Referred-By header indicating UE1 and containing the Replaces header indicating the original dialog sessions. | | | | +| SIP header values:
REFER (S1): Request line=Focus
Refer-To=UE#2; method=INVITE?Replaces=S1;to-tag=S1;from-tag=S1
Referred-By=UE#1
REFER (S1): Request line=Focus
Refer-To=UE#3; method=INVITE?Replaces=S2;to-tag=S2;from-tag=S2
Referred-By=UE#1
INVITE (S4): Request URI=UE#2
Referred-By=UE#1
Replaces=S1;to-tag=S1;from-tag=S1
INVITE (S5): Request URI=UE#3
Referred-By=UE#1
Replaces=S2;to-tag=S2;from-tag=S2 | | | | +| Comments: | | | | +| ISC#1 | Focus | ISC#2 | ISC#3 | +| | Establish session #1
Session #1 on hold
Establish session #2
Session #2 on hold
Conference creation (session #3) | | | +| INVITE (S3) | → | INVITE | | +| 200 OK (INVITE) | ← | 200 OK (INVITE) | | +| ACK | → | ACK | | +| REFER (S1) | → | REFER | | +| 202 Accepted | ← | 202 Accepted | | +| NOTIFY (100) | ← | NOTIFY (100) | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | +| | | INVITE (S4) | → | +| | | 200 OK (INVITE) | ← | +| | | ACK | → | +| NOTIFY (200) | ← | NOTIFY (200) | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | +| BYE (S1) | ← | ← | BYE (S1) | +| 200 OK (BYE) | → | → | 200 OK (BYE) | +| REFER (S2) | → | REFER | | +| 202 Accepted | ← | 202 Accepted | | +| NOTIFY (100) | ← | NOTIFY (100) | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | +| | | INVITE (S5) | → | +| | | 200 OK (INVITE) | ← | +| | | ACK | → | +| NOTIFY (200) | ← | NOTIFY (200) | | +| 200 OK (NOTIFY) | → | 200 OK (NOTIFY) | | +| BYE (S1) | ← | | ← | +| 200 OK (BYE) | → | | → | +| Apply post test routine | | | | + +| TSS | TP | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|--------------------------------------------|----------------------|--------------|--------------------------------------------|--------------|--------|----------|--|-----------------|-------------------|--|-----|-------|--|--|--------------------------------------------|--|---------|---------|--|--------------|----------------|--|--|---------------------------------------|--|--|------------|--------|--------|------------|--|---------------|-----------------|--|--|-----------------|---------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|--|--------------------------------|--| +| ConferenceFocus/InviteToConf | CONF_N03_007 | Clause 4.5.2.2.1 of
[ITU-T Q.3621 v.1]] | PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Referred-By value does not contain a valid identity of the requesting user.

Ensure that the invalid identity in the Referred-By header received in the REFER request from UE1 is replaced with the valid value matching the REFER request's P-Asserted-Identity when sending the INVITE request to UE2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER 1: Request line=Focus
Refer-To=UE#2; method=INVITE
Referred-By=any value not indicating UE#1(PIXIT)
P-Asserted-Identity=UE#1
INVITE 1: Request URI=UE#2
Referred-By=UE#1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus
Conference creation		 ISC#2
INVITE ➔ INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK ➔ ACK
UE#1 invites UE#2 to the conference
REFER 1 ➔ REFER
202 Accepted ← 202 Accepted
Focus dials out to invite UE#2
INVITE 1 ➔ INVITE
NOTIFY ← NOTIFY 1
200 OK NOTIFY ➔ 200 OK NOTIFY
200 OK INVITE ← 200 OK INVITE
ACK ➔ ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY ➔ 200 OK NOTIFY
Apply post test routine
| | | | ISC#1 | Focus
Conference creation | ISC#2 | INVITE | ➔ INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | ➔ ACK | | | UE#1 invites UE#2 to the conference | | REFER 1 | ➔ REFER | | 202 Accepted | ← 202 Accepted | | | Focus dials out to invite UE#2 | | | INVITE 1 ➔ | INVITE | NOTIFY | ← NOTIFY 1 | | 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | 200 OK INVITE ← | 200 OK INVITE | | ACK ➔ | ACK | NOTIFY | ← NOTIFY 2 | | 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | Apply post test routine | | +| ISC#1 | Focus
Conference creation | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE#1 invites UE#2 to the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 1 | ➔ REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE 1 ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|---------------------------------------------------------------|-------------------------------------------|--|--------------|--|--------------|--|----------------------------|--|--|----------|----------|--|--|-----------------|-------------------|--|--|-----|-------|--|--|--|--------------------------------------------|--|--|---------|---------|--|--|--------------|----------------|--|--|--|---------------------------------------|--|--|--|----------|---|--------|--------|------------|--|--|---------------|-----------------|--|--|--|-------------|---|-------------|--|---------------|---|---------------|--|-----|---|-----|--------|------------|--|--|---------------|-----------------|--|--|--|--------------------------------|--|--| +| TSS
ConferenceFocus/InviteToConf | TP
CONF_N03_008 | Reference
Clause 4.5.2.2.1 of
[ITU-T Q.3621 v.1] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Referred-By header not present. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the missing Referred-By header in the received REFER request from UE1 is inserted with the valid value matching the REFER request's P-Asserted-Identity when sending the INVITE request to UE2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER 1: Request line=Focus
Refer-To=UE#2; method=INVITE
P-Asserted-Identity=UE#1
INVITE 1: Request URI=UE#2
Referred-By=UE#1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1
Focus ISC#2
Conference creation
INVITE 1 → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
UE#1 invites UE#2 to the conference
REFER 1 → REFER
202 Accepted ← 202 Accepted
Focus dials out to invite UE#2
INVITE 1 → INVITE
NOTIFY ← NOTIFY 1
200 OK NOTIFY → 200 OK NOTIFY
180 Ringing ← 180 Ringing
200 OK INVITE ← 200 OK INVITE
ACK → ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY → 200 OK NOTIFY
Apply post test routine
| | | | | Focus | | ISC#2 | | Conference creation | | | INVITE 1 | → INVITE | | | 200 OK (INVITE) | ← 200 OK (INVITE) | | | ACK | → ACK | | | | UE#1 invites UE#2 to the conference | | | REFER 1 | → REFER | | | 202 Accepted | ← 202 Accepted | | | | Focus dials out to invite UE#2 | | | | INVITE 1 | → | INVITE | NOTIFY | ← NOTIFY 1 | | | 200 OK NOTIFY | → 200 OK NOTIFY | | | | 180 Ringing | ← | 180 Ringing | | 200 OK INVITE | ← | 200 OK INVITE | | ACK | → | ACK | NOTIFY | ← NOTIFY 2 | | | 200 OK NOTIFY | → 200 OK NOTIFY | | | | Apply post test routine | | | +| | Focus | | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE 1 | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE#1 invites UE#2 to the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 1 | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE 1 | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 6.2.1.4 Leaving a conference + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------------|-------------------------------------------|--|--------------|--|--------------|--|----------------------------|--|--|--------|----------|--|--|-----------------|-------------------|--|--|-----|-------|--|--|-------|---------|--|--|--------------|----------------|--|--|--|---------------------------------------|--|--|--|--------|---|----------|--|-------------|---|-------------|--|---------------|---|---------------|--|-----|---|-----|--|---------------------------------|--|--|--|-----------------------------------|--|--|--|--|---|-----|--|--|---|------------|--|--------------------------------|--|--| +| TSS
ConferenceFocus/LeaveConf | TP
CONF_N04_001 | Reference
5.3.2.6.1 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
A participant leaves the conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE#2 wishes to leave the conference by sending a BYE request to the focus in accordance to the basic call procedures. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1
Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
REFER → REFER
202 Accepted ← 202 Accepted
Focus dials out to invite UE#2
INVITE → INVITE 2
180 Ringing ← 180 Ringing
200 OK INVITE ← 200 OK INVITE
ACK → ACK
Conference communication
UE#2 leaves the conference
← BYE
→ 200 OK BYE
Apply post test routine
| | | | | Focus | | ISC#2 | | Conference creation | | | INVITE | → INVITE | | | 200 OK (INVITE) | ← 200 OK (INVITE) | | | ACK | → ACK | | | REFER | → REFER | | | 202 Accepted | ← 202 Accepted | | | | Focus dials out to invite UE#2 | | | | INVITE | → | INVITE 2 | | 180 Ringing | ← | 180 Ringing | | 200 OK INVITE | ← | 200 OK INVITE | | ACK | → | ACK | | Conference communication | | | | UE#2 leaves the conference | | | | | ← | BYE | | | → | 200 OK BYE | | Apply post test routine | | | +| | Focus | | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE | → | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 180 Ringing | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE#2 leaves the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 6.2.1.5 Removing a conference participant from a conference + +| TSS
ConferenceFocus/RemoveFromConf | TP
CONF_N05_001 | Reference
5.3.2.6.2.2,
5.3.2.6.2.3 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------------------------|-------------------------------------------|-------|-------|-------|----------------------------|--|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|---------|---|--|--------------|---|--|---------------------------------------|--|--|--------|------------|--|---------------|-----------------|--|--|----------|----------|--|-----------------|---------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|---------------------------------|--|--|-------------------------------------------------------|--|--|---------|---------|--|--------------|----------------|--|-----------------------------------------------|--|--|--|-------|--|--|--------------|--|--------|------------|--|------------|--------------|--|--------------------------------|--|--| +| Test purpose
The conference owner asks the focus to remove a participant from the conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1 (via ISC#1) sends a REFER request to removes UE2 from the conference. The focus sends a BYE request to UE2 (via ISC#2). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER 1: Request URI contained the URI of conference URI
Refer-To contains the UE#2 URI , method=BYE
Referred-By contains the URI of UE#1 URI
NOTIFY 2: Event contains conference ;
Subscription-State contains active
message/sipfrag contains SIP/2.0 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
REFER 1 →
202 Accepted ←
UE#2 joining in the conference
NOTIFY ← NOTIFY 1
200 OK NOTIFY → 200 OK NOTIFY
INVITE → INVITE 2
200 OK INVITE ← 200 OK INVITE
ACK → ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY → 200 OK NOTIFY
Conference communication
UE#1 wishes to remove UE#2 from the conference
REFER 2 → REFER
202 Accepted ← 202 Accepted
Focus removes UE#2 from the conference
→ BYE
← 200 OK BYE
NOTIFY ← NOTIFY 3
200 NOTIFY → 200 NOTIFY
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | Conference creation | | | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | REFER 1 | → | | 202 Accepted | ← | | UE#2 joining in the conference | | | NOTIFY | ← NOTIFY 1 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | INVITE → | INVITE 2 | | 200 OK INVITE ← | 200 OK INVITE | | ACK → | ACK | NOTIFY | ← NOTIFY 2 | | 200 OK NOTIFY | → 200 OK NOTIFY | | Conference communication | | | UE#1 wishes to remove UE#2 from the conference | | | REFER 2 | → REFER | | 202 Accepted | ← 202 Accepted | | Focus removes UE#2 from the conference | | | | → BYE | | | ← 200 OK BYE | | NOTIFY | ← NOTIFY 3 | | 200 NOTIFY | → 200 NOTIFY | | Apply post test routine | | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE#2 joining in the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE → | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Conference communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE#1 wishes to remove UE#2 from the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 2 | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Focus removes UE#2 from the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 NOTIFY | → 200 NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------------------|-------------------------------------------|---------------|--|--------------|--|--------------|--|--|----------------------------|--|--|--------|---|--------|--|--|-----------------|---|-----------------|--|--|-----|---|-----|--|--|---------|---|--|--|--|--------------|---|--|--|--|--|--|---------------------------------------|--|--|--|--|--------|---|----------|--|--|---------------|---|---------------|--|--|-----|---|-----|--|--|---------------------------------|--|--|--|--|------------------------------------------------------------------|--|--|---------|---|-------|--|--|-----|---|-----|--|--|--|--|--------------------------------|--|--| +| TSS
ConferenceFocus/RemoveFromConf | TP
CONF_N05_002 | Reference
5.3.2.6.2.2 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The conference owner asks the focus to remove a user that is not participant from the conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1 (via ISC#1) sends a REFER request to removes a user that is not participant in the conference from the conference. The focus rejects the request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER 2: Request URI contained the URI of conference URI
Refer-To contains the URI of a user that is not conference participant, method=BYE
Referred-By contains the URI of UE#1 URI | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
REFER 1 →
202 Accepted ←
UE#2 joining in the conference
INVITE → INVITE 2
200 OK INVITE ← 200 OK INVITE
ACK → ACK
Conference communication
UE#1 wishes to remove non-participant from the conference
REFER 2 → REFER
4xx ← 4xx
Apply post test routine
| | | | ISC#1 | | Focus | | ISC#2 | | | Conference creation | | | INVITE | → | INVITE | | | 200 OK (INVITE) | ← | 200 OK (INVITE) | | | ACK | → | ACK | | | REFER 1 | → | | | | 202 Accepted | ← | | | | | | UE#2 joining in the conference | | | | | INVITE | → | INVITE 2 | | | 200 OK INVITE | ← | 200 OK INVITE | | | ACK | → | ACK | | | Conference communication | | | | | UE#1 wishes to remove non-participant from the conference | | | REFER 2 | → | REFER | | | 4xx | ← | 4xx | | | | | Apply post test routine | | | +| ISC#1 | | Focus | | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | UE#2 joining in the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE | → | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK INVITE | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | UE#1 wishes to remove non-participant from the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 2 | → | REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4xx | ← | 4xx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 6.2.1.6 Conference termination + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------|-------------------------------------------|---------------|--|--------------|--|--------------|--|--|----------------------------|--|--|--------|---|--------|--|--|-----------------|---|-----------------|--|--|-----|---|-----|--|--|-------|---|--|--|--|--------------|---|--|--|--|--|--|---------------------------------------|--|--|--|--|--------|---|----------|--|--|-------------|---|-------------|--|--|---------------|---|---------------|--|--|-----|---|-----|--|--|---------------------------------|--|--|--|--|----------------------------------------------------|--|--|-------|---|-----|--|--|------------|---|------------|--|--|--|--|-----------------------------------------------|--|--|--|--|-----|---|-----|--|--|------------|---|------------|--|--|--------------------------------|--|--| +| TSS
ConferenceFocus/TerminateConf | TP
CONF_N06_001 | Reference
5.3.2.7 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The conference owner releases the entire conference by sending a BYE to the focus. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1 (via ISCP#1), the conference owner, sends a BYE request to the focus. The entire conference is released. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
BYE 1:
Request URI = conference URI | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
REFER →
202 Accepted ←
Focus dials out to invite UE#2
INVITE → INVITE 2
180 Ringing ← 180 Ringing
200 OK INVITE ← 200 OK INVITE
ACK → ACK
Conference communication
UE#1 wishes to finish the entire conference
BYE 1 → BYE
200 OK BYE ← 200 OK BYE
Focus removes UE#2 from the conference
BYE → BYE
200 OK BYE ← 200 OK BYE
Apply post test routine
| | | | ISC#1 | | Focus | | ISC#2 | | | Conference creation | | | INVITE | → | INVITE | | | 200 OK (INVITE) | ← | 200 OK (INVITE) | | | ACK | → | ACK | | | REFER | → | | | | 202 Accepted | ← | | | | | | Focus dials out to invite UE#2 | | | | | INVITE | → | INVITE 2 | | | 180 Ringing | ← | 180 Ringing | | | 200 OK INVITE | ← | 200 OK INVITE | | | ACK | → | ACK | | | Conference communication | | | | | UE#1 wishes to finish the entire conference | | | BYE 1 | → | BYE | | | 200 OK BYE | ← | 200 OK BYE | | | | | Focus removes UE#2 from the conference | | | | | BYE | → | BYE | | | 200 OK BYE | ← | 200 OK BYE | | | Apply post test routine | | | +| ISC#1 | | Focus | | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE | → | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 180 Ringing | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK INVITE | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | UE#1 wishes to finish the entire conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE 1 | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Focus removes UE#2 from the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BYE | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK BYE | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------|-------------------------------------------------------------|---------------|--|--------------|--|--------------|--|--|----------------------------|--|--|-------------|---|--------|--|--|----------------------|---|-----------------|--|--|-----|---|-----|--|--|-------|---|--|--|--|--------------|---|--|--|--|--|--|---------------------------------------|--|--|--|--|-------------|---|----------|--|--|---------------|---|---------------|--|--|-----|---|-----|--|--|---------------------------------|--|--|--|--|-------------------------------------------------|--|--|----------|---|----------|--|--|------------|---|------------|--|--|--|--|----------|---|-----|--|--|------------|---|------------| +| TSS
ConferenceFocus/TerminateConf | TP
CONF_N06_002 | Reference
5.3.2.7 of
[ETSI TS 124 147] | Selection expression
PICS 5.1/2 AND
PICS 5.3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference termination when the conference creator has left the conference.

Ensure that the conference is terminated when the conference creator which has created the conference using the conference factory has left the conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE S1: Request URI indicating the conference factory URI
200 OK S1: conference URI and "isfocus" feature parameter included in Contact header field | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE (S1) → INVITE
200 OK (INVITE) (S1) ← 200 OK (INVITE)
ACK → ACK
REFER →
202 Accepted ←
Focus dials out to invite UE#2
INVITE (S2) → INVITE 2
200 OK INVITE ← 200 OK INVITE
ACK → ACK
Conference communication
Conference creator leaves the conference
BYE (S1) → BYE (S1)
200 OK BYE ← 200 OK BYE
BYE (S2) → BYE
200 OK BYE ← 200 OK BYE
| | | | ISC#1 | | Focus | | ISC#2 | | | Conference creation | | | INVITE (S1) | → | INVITE | | | 200 OK (INVITE) (S1) | ← | 200 OK (INVITE) | | | ACK | → | ACK | | | REFER | → | | | | 202 Accepted | ← | | | | | | Focus dials out to invite UE#2 | | | | | INVITE (S2) | → | INVITE 2 | | | 200 OK INVITE | ← | 200 OK INVITE | | | ACK | → | ACK | | | Conference communication | | | | | Conference creator leaves the conference | | | BYE (S1) | → | BYE (S1) | | | 200 OK BYE | ← | 200 OK BYE | | | | | BYE (S2) | → | BYE | | | 200 OK BYE | ← | 200 OK BYE | +| ISC#1 | | Focus | | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (S1) | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) (S1) | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE (S2) | → | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK INVITE | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Conference creator leaves the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (S1) | → | BYE (S1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BYE (S2) | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK BYE | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +## 6.3 Interaction with other supplementary services + +### 6.3.1 Terminating identification restriction (TIR) + +| TSS | TP | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------------|------------------------------------------|--------------|--------------|--------------|--|----------------------------|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|-----------|-------------|--|--------------------|----------------------|--|--|----------------------------------------------------|--|-------|---|--|----------------|---|--|--|---------------------------------------------|--|--------|------------|--|---------------|-----------------|--|--|----------|----------|--|-----------------|-----------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|--|--------------------------------|--| +| Interaction/TIR | CONF_N08_001 | Clause 4.6.3 of [ITU-T Q.3621 v.1] | PICS 5.1/2 AND PICS 5.3/3 AND PICS 5.3/6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Remote user requests TIR, no identity information in the conference notification info send in the NOTIFY request to the conference creator.

Ensure the no identity is sent to the conference creator if a Privacy header was received and the privacy value was set to "id" in the 200 OK to the INVITE from the conference focus to invite the participant to the conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
200 OK INVITE 2: Privacy: id
NOTIFY 2: Event contains conference ; Subscription-State contains active
application/conference-info+xml:
<conference-info>   entity=conference URI, state="full", version="x"   <conference-state>     <user-count>2</user-count> if present     <active>true</active> if present   </conference-state>   <users>     <user entity=ISC#1 URI state="full">       <endpoint entity=endpoint ISC#1 URI>         <status>connected</status>         <joining-method>dialed-in</joining-method>         <media id="1">           <status>sendrecv</status>         </media>       </endpoint>     </user>   </users> </conference-info>

[No identity information of UE#2 or Element is not present]

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
SUBSCRIBE → SUBSCRIBE
200 OK (SUBSCRIBE) ← 200 OK (SUBSCRIBE)
UE1#1 invites UE#2 via the conference focus
REFER →
200 OK (REFER) ←
Focus invites UE#2 to the conference
NOTIFY ← NOTIFY 1
200 OK NOTIFY → 200 OK NOTIFY
INVITE → INVITE 2
200 OK INVITE ← 200 OK INVITE 2
ACK → ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY → 200 OK NOTIFY
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | | Conference creation | | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | SUBSCRIBE | → SUBSCRIBE | | 200 OK (SUBSCRIBE) | ← 200 OK (SUBSCRIBE) | | | UE1#1 invites UE#2 via the conference focus | | REFER | → | | 200 OK (REFER) | ← | | | Focus invites UE#2 to the conference | | NOTIFY | ← NOTIFY 1 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | INVITE → | INVITE 2 | | 200 OK INVITE ← | 200 OK INVITE 2 | | ACK → | ACK | NOTIFY | ← NOTIFY 2 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | Apply post test routine | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBSCRIBE | → SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (SUBSCRIBE) | ← 200 OK (SUBSCRIBE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE1#1 invites UE#2 via the conference focus | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (REFER) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus invites UE#2 to the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE → | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE ← | 200 OK INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### 6.3.2 Originating Identification Restriction (OIR) + +| TSS
Interaction/OIR | TP
CONF_N09_001 | Reference
Clause 4.6.5 of
[ITU-T Q.3621 v.1] | Selection expression
PICS 5.1/2
PICS 5.3/1 AND
PICS 5.3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------------|---------------------------------------------------------------------------|-------|-------|-------|----------------------------|--|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|----------------------------------------------------|--|--|-------|---|--|----------------|---|--|---------------------------------------------|--|--|--------|------------|--|---------------|-----------------|--|--|----------|----------|--|-----------------|---------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|--|--|-------------|--|--|----------------------|--|------------|--------|--|-----------------|---------------|--------------------------------|--|--| +| Test purpose
Conference creator subscribes to OIR in permanent mode. There is no identity information of the creator included in the conference notification sent to the conference participants. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the conference notification sent in the NOTIFY request to the participant after it has joined the conference if the conference creator has subscribed to the OIR service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
SUBSCRIBE: Request URI contained the conference URI, Event contains "conference"
Event header contains "conference"
NOTIFY 3: Event contains conference ; Subscription-State contains active; expires=xxxx
application/conference-info+xml:

entity=conference URI state="full" version="x"

2 if present
true if present

[No identity information of UE#1 or Element is not present]


connected
dialed-in

sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISC#1 Focus ISC#2
Conference creation
INVITE ➔ INVITE
200 OK (INVITE) ⬅ 200 OK (INVITE)
ACK ➔ ACK
UE1#1 invites UE#2 via the conference focus
REFER ➔
200 OK (REFER) ⬅
Focus invites UE#2 to the conference
NOTIFY ⬅ NOTIFY 1
200 OK NOTIFY ➔ 200 OK NOTIFY
INVITE ➔ INVITE 2
200 OK INVITE ⬅ 200 OK INVITE
ACK ➔ ACK
NOTIFY ⬅ NOTIFY 2
200 OK NOTIFY ➔ 200 OK NOTIFY
⬅ SUBSCRIBE
➔ 200 OK (SUBSCRIBE)
NOTIFY 3 ➔ NOTIFY
200 OK NOTIFY ⬅ 200 OK NOTIFY
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | Conference creation | | | INVITE | ➔ INVITE | | 200 OK (INVITE) | ⬅ 200 OK (INVITE) | | ACK | ➔ ACK | | UE1#1 invites UE#2 via the conference focus | | | REFER | ➔ | | 200 OK (REFER) | ⬅ | | Focus invites UE#2 to the conference | | | NOTIFY | ⬅ NOTIFY 1 | | 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | INVITE ➔ | INVITE 2 | | 200 OK INVITE ⬅ | 200 OK INVITE | | ACK ➔ | ACK | NOTIFY | ⬅ NOTIFY 2 | | 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | | ⬅ SUBSCRIBE | | | ➔ 200 OK (SUBSCRIBE) | | NOTIFY 3 ➔ | NOTIFY | | 200 OK NOTIFY ⬅ | 200 OK NOTIFY | Apply post test routine | | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE1#1 invites UE#2 via the conference focus | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (REFER) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Focus invites UE#2 to the conference | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ⬅ NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE ➔ | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ⬅ NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | ➔ 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ 200 OK (SUBSCRIBE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | NOTIFY 3 ➔ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK NOTIFY ⬅ | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + + + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------|----------------------------------------------------------|--------------|--------------------------------------|--------------|--------|----------|--|-----------------|-------------------|--|-----|-------|--|---------------------------------------------------|--|--|---------|---------|--|--------------|----------------|--|--|---------------------------------------|--|--|------------|--------|--------|------------|--|---------------|-----------------|--|--|-----------------|---------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|--------------------------------|--|--| +| TSS
Interaction/OIR | TP
CONF_N09_003 | Reference
Clause 4.6.5 of [ITU-T Q.3621 v.1] | Selection expression
PICS 5.1/2 AND PICS 5.3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference creator subscribes to OIR in temporary mode. Referred-By is not inserted into the INVITE request if Privacy value "user" was received in the REFER.

Ensure that if the Referred-By header is not received in the REFER request to the conference focus, it is not inserted into the INVITE request sent to the participant to be invited to the conference if the REFER request contained a Privacy header set to "user". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER 1: no Referred-By present
Privacy: user
INVITE 1: Request
no Referred-By inserted URI=UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus
Conference creation		 ISC#2
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
UE#1 invites UE#2 via the conference focus
REFER 1 → REFER
202 Accepted ← 202 Accepted
Focus dials out to invite UE#2
INVITE 1 → INVITE
NOTIFY ← NOTIFY 1
200 OK NOTIFY → 200 OK NOTIFY
← 200 OK INVITE 200 OK INVITE
ACK → ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY → 200 OK NOTIFY
Apply post test routine
| | | | ISC#1 | Focus
Conference creation | ISC#2 | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | UE#1 invites UE#2 via the conference focus | | | REFER 1 | → REFER | | 202 Accepted | ← 202 Accepted | | | Focus dials out to invite UE#2 | | | INVITE 1 → | INVITE | NOTIFY | ← NOTIFY 1 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | ← 200 OK INVITE | 200 OK INVITE | | ACK → | ACK | NOTIFY | ← NOTIFY 2 | | 200 OK NOTIFY | → 200 OK NOTIFY | | Apply post test routine | | | +| ISC#1 | Focus
Conference creation | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UE#1 invites UE#2 via the conference focus | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 1 | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE 1 → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Rec. ITU-T Q.4005.2 (02/2016)** +21 + +| TSS | TP | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|---------------------------------------|------------------------------|--------------|--------------|--------------|--|----------------------------|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|--|----------------------------------------------------|--|---------|---------|--|--------------|----------------|--|--|---------------------------------------|--|--|------------|--------|--------|------------|--|---------------|-----------------|--|--|-----------------|---------------|--|-------|-----|--------|------------|--|---------------|-----------------|--|--|--------------------------------|--| +| Interaction/OIR | CONF_N09_004 | Clause 4.6.5 of
[ITU-T Q.3621 v.1] | PICS 5.1/2 AND
PICS 5.3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference creator subscribes to OIR in temporary mode. Referred-By is not inserted into the INVITE request if Privacy value "header" was received in the REFER. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that if the Referred-By header is not received in the REFER request to the conference focus, it is not inserted into the INVITE request sent to the participant to be invited to the conference if the REFER request contained a Privacy header set to "header". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER 1: no Referred-By present
Privacy: header
INVITE 1: Request URI=UE#2
no Referred-By inserted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
UE1#1 invites UE#2 via the conference focus
REFER 1 → REFER
202 Accepted ← 202 Accepted
Focus dials out to invite UE#2
INVITE 1 → INVITE
NOTIFY ← NOTIFY 1
200 OK NOTIFY → 200 OK NOTIFY
200 OK INVITE ← 200 OK INVITE
ACK → ACK
NOTIFY ← NOTIFY 2
200 OK NOTIFY → 200 OK NOTIFY
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | | Conference creation | | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | | UE1#1 invites UE#2 via the conference focus | | REFER 1 | → REFER | | 202 Accepted | ← 202 Accepted | | | Focus dials out to invite UE#2 | | | INVITE 1 → | INVITE | NOTIFY | ← NOTIFY 1 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | 200 OK INVITE ← | 200 OK INVITE | | ACK → | ACK | NOTIFY | ← NOTIFY 2 | | 200 OK NOTIFY | → 200 OK NOTIFY | | | Apply post test routine | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE1#1 invites UE#2 via the conference focus | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER 1 | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ← 202 Accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Focus dials out to invite UE#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | INVITE 1 → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 200 OK INVITE ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ACK → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ← NOTIFY 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK NOTIFY | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### 6.3.3 Anonymous communication rejection and communication barring (ACR/CB) + +| TSS | TP | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|--------------------------------|------------------------------|--------------|--------------|--------------|--|----------------------------|--|--------|----------|--|-----------------|-------------------|--|-----|-------|--|--|-------------------------------------------------------------------------|--|-------|---------|--|-----|-------|--|--|--------------------------------|--| +| Interaction/ACR-CB | CONF_N10_001 | 4.6.9 of
[ITU-T Q.3621 v.1] | PICS 5.1/2 AND
PICS 5.3/7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference creator subscribes to ACR/CB and has Outgoing Call Barring activated for UE2. Conference invitation for UE2 via REFER is rejected. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the conference AS rejects the REFER request targeted at a participant (UE2) that is barred by the conference creator's Outgoing Communication Barring rules. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
REFER: Request URI contained the conference URI
Refer-To contains the URI of UE#2 , method=invite
Referred-By contains SIP URI of UE#1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
UE1#1 invites outgoing call barred UE#2 via the conference focus
REFER → REFER
4xx ← 4xx
Apply post test routine
| | | | ISC#1 | Focus | ISC#2 | | Conference creation | | INVITE | → INVITE | | 200 OK (INVITE) | ← 200 OK (INVITE) | | ACK | → ACK | | | UE1#1 invites outgoing call barred UE#2 via the conference focus | | REFER | → REFER | | 4xx | ← 4xx | | | Apply post test routine | | +| ISC#1 | Focus | ISC#2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Conference creation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UE1#1 invites outgoing call barred UE#2 via the conference focus | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4xx | ← 4xx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------|------------------------------------------------|--------------|--------------|--------------|--------------|-------------|----------|--|--|-----------------|-------------------|--|--|-----|-------|--|--|--|--|-------------|----------|--|--|-----------------|-------------------|--|--|-----|-------| +| Interaction/ACR-CB | CONF_N10_002 | 4.6.9 of
[ITU-T Q.3621 v.1] | PICS 5.1/2 AND
PICS 5.3/3 AND
PICS 5.3/7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
Conference creator subscribes to ACR/CB and has Outgoing Call Barring activated for UE2. Conference invitation for UE2 via the URI-list is rejected.

Ensure that the focus AS removes the URI of UE2 that is barred by the conference creator's Outgoing Communication Barring rules from the list of URIs in the "recipient-list" body of INVITE request. UE2 is not invited to the conference.

SIP header values:
INVITE (S1) Request URI indicating Conference Factory
Content-Type: application/resource-lists+xml
Content-Disposition: recipient-list

<?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:cp="urn:ietf:params:xml:ns:copyControl">   <list>     <entry uri="UE#2" cp:copyControl="to"/>     <entry uri="UE#3" cp:copyControl="to"/>   </list> </resource-lists>

Comments:

ISC#1 Focus ISC#2 ISC#3
INVITE (S1) → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK
INVITE (S2) → INVITE
200 OK (INVITE) ← 200 OK (INVITE)
ACK → ACK

Apply post test routine

| | | | ISC#1 | Focus | ISC#2 | ISC#3 | INVITE (S1) | → INVITE | | | 200 OK (INVITE) | ← 200 OK (INVITE) | | | ACK | → ACK | | | | | INVITE (S2) | → INVITE | | | 200 OK (INVITE) | ← 200 OK (INVITE) | | | ACK | → ACK | +| ISC#1 | Focus | ISC#2 | ISC#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (S1) | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE (S2) | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK (INVITE) | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f10dc31989c7646e569332575ae07165432f75a5 --- /dev/null +++ b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:970106fea50584ef01fb9f9753ac8c7deba22182e2d0fd0bf2e562eab2c4f87b +size 22491 diff --git a/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b11013777ea4eb815bd94104f23c299fc6de075 --- /dev/null +++ b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:508375f9f173497d1af2d41f34990839e21a70e308afa27eba438759ab04e8e7 +size 15675 diff --git a/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8b59a9fbae5fd87e5b2fbc9c3b51dc6568fe2721 --- /dev/null +++ b/marked/Q/T-REC-Q.4010.2-201608-I_PDF-E/raw.md @@ -0,0 +1,421 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4010.2** + +(08/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Message waiting indication using IP multimedia +core network subsystem – Part 2: Test suite +structure and test purposes; Network side** + +Recommendation ITU-T Q.4010.2 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +International +Telecommunication +Union + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| Testing specifications for next generation networks | Q.3900-Q.3999 | +| Testing specifications for SIP-IMS | Q.4000-Q.4039 | +| Testing specifications for Cloud computing | Q.4040-Q.4059 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.4010.2 + +# Message waiting indication using IP multimedia core network subsystem – Part 2: Test suite structure and test purposes; Network side + +## Summary + +Recommendation ITU-T Q.4010.2 v.1 (2016) provides the testing requirements "Message waiting indication (MWI) using IP multimedia (IM) core network (CN) subsystem – Part 2: Test suite structure and test purposes (TSS&TP); Network side" (based on Recommendation ITU-T Q.3626 v.1). + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4010.2, and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4010.2 v.1 | 2016-08-29 | 11 | 11.1002/1000/13002 | + +## Keywords + +IMS, IP multimedia subsystem, message waiting indication, MWI, testing, test suite structure and test purposes, TSS&TP. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2017 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|-------------------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | Test suite structure..... | 2 | +| 6.1 | Configuration..... | 2 | +| 7 | Test purposes ..... | 3 | +| 7.1 | Introduction ..... | 3 | +| 7.2 | Invocation and operation ..... | 4 | + + + +## Recommendation ITU-T Q.4010.2 + +# Message waiting indication using IP multimedia core network subsystem – Part 2: Test suite structure and test purposes; Network side + +# 1 Scope + +This Recommendation is Part 2 of a multi-part deliverable covering "Message waiting indication (MWI) using IP multimedia (IM) core network (CN) subsystem – Part 2: Test suite structure and test purposes (TSS&TP); network side", as identified below: + +Part 1: "Protocol implementation conformance statement (PICS)"; + +**Part 2: "Test suite structure and test purposes (TSS&TP); Network side";** + +Part 3: "Test suite structure and test purposes (TSS&TP); User side". + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.3626 v.1] Recommendation ITU-T Q.3626 v.1 (2016), *Message waiting indication – Protocol specification*. +- [ITU-T Q.4012.1] Recommendation ITU-T Q.4012.1 v.1 (2016), *Anonymous communication rejection and communication barring using IP multimedia core network subsystem; Conformance testing specification – Part 1: Protocol implementation conformance statement*. +- [ITU-T X.290] Recommendation ITU-T X. 290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [IETF RFC 3265] IETF RFC 3265 (2002), *Session Initiation Protocol (SIP) – Specific Event Notification*. +- [IETF RFC 3842] IETF RFC 3842 (2004), *A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +For the purposes of this Recommendation, the terms and definitions given in [ITU-T Q.3626 v.1], [ITU-T X. 290], [ITU-T X.296] and the following apply: + +**3.1.1 PICS proforma:** Document, in the form of a questionnaire, which when completed for an implementation or system becomes a PICS. + +**3.1.2 Protocol ICS (PICS):** ICS for an implementation or system claimed to conform to a given protocol specification. + +NOTE – This may contain additional information. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------------| +| AS | Application Server | +| ICS | Implementation Conformance Statement | +| IUT | Implementation Under Test | +| MA | Message Account | +| MIME | Multipurpose Internet Mail Extensions | +| MWI | Message Waiting Indication | +| PICS | Protocol Implementation Conformance Statement | +| SUT | System Under Test | +| TP | Test Purpose | +| TSS | Test Suite Structure | + +# **5 Conventions** + +None. + +# **6 Test suite structure** + +| | | | +|---------|---------------|-------------| +| Network | | | +| | AS_ServedUser | OIP_N01_xxx | + +## **6.1 Configuration** + +The scope of this Recommendation is to test the signalling and procedural aspects of the stage 3 requirements as described in [ITU-T Q.3626 v.1]. The stage 3 description respects the requirements to several network entities and end devices. Consequently, several interfaces (reference points) are addressed to satisfy the test of the different entities. + +In order to test the appropriate entities the configurations below are applicable: + +**Testing of the application server (AS):** This entity performs the service. Hence the ISC interface is the appropriate access point as shown in Figure 6.1-1. + +![Diagram showing a Test system connected to an Application server via an ISC interface. The Application server contains an Implementation under test. Reference: Q.4010.2v1(16)_F6.1-1](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Diagram showing a Test system connected to an Application server via an ISC interface. The Application server contains an Implementation under test. Reference: Q.4010.2v1(16)\_F6.1-1 + +**Figure 6.1-1 – Applicable interface to test AS functionalities** + +If the ISC interface is not accessible, it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) (consider Figure 6.1-2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. + +![Diagram showing a Test system connected to a CSCF (and/or AS) Implementation under test via Mw, Mg, Mx interfaces. The CSCF is also connected to another Test system via Mw, Mg, Mx interfaces. Reference: Q.4010.2v1(16)_F6.1-2](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Diagram showing a Test system connected to a CSCF (and/or AS) Implementation under test via Mw, Mg, Mx interfaces. The CSCF is also connected to another Test system via Mw, Mg, Mx interfaces. Reference: Q.4010.2v1(16)\_F6.1-2 + +**Figure 6.1-2 – Applicable interfaces to test using the (generic) NNI** + +Figure 6.1-2 illustrates the usage of any NNI. + +# 7 Test purposes + +## 7.1 Introduction + +For each requirement in [ITU-T Q.3626 v.1] a test purpose (TP) is defined. + +### 7.1.1 TP naming convention + +Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the test suite structure (TSS). Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Table 7.1-1). + +**Table 7.1-1 – TP identifier naming convention scheme** + +| | | | | | | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------|---|------------------|---|---------| +| Identifier: __ | | | | | | +| = supplementary service: | e.g. "MWI" | | | | | +| = type of IUT: |
UUser - equipment
NNetwork
| U | User - equipment | N | Network | +| U | User - equipment | | | | | +| N | Network | | | | | +| = group | 2 digit field representing group reference according to TSS | | | | | +| = 3 digit sequential number | (001-999) | | | | | + +### 7.1.2 Test strategy + +As the base standard [ITU-T Q.3626 v.1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the protocol implementation conformance statement (PICS) specification [ITU-T Q.4012.1] The criteria applied include the following: + +- Whether or not a test case can be built from the TP is not considered. + +#### 7.1.3 Reference column "MWI reference" + +The column "MWI reference" makes reference to [ITU-T Q.3626 v.1], except where explicitly stated otherwise. + +## 7.2 Invocation and operation + +### 7.2.1 Actions at the application server + +| TSS | TP | MWI reference | Selection expression | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------|-----------------------------| +| Network/AS_ServedUser | MWI_N01_001 | Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clause 3.4 of [RFC 3842]
Clauses 3.1.4.1, 3.1.6.2 of [RFC 3265] | | +| Test purpose:
Subscription to the message waiting service, all relevant headers present | | | | +| Verify that the SUBSCRIBE request will be accepted with following Subscribe-specific headers: Event, Expires and Accept. The 200 OK (SUBSCRIBE) contains the Expires header indicating the subscription duration for the MWI service. A NOTIFY is sent immediately the actual state of a message account (MA). The From header tag and the Call-ID in the NOTIFY are equal to the values in the SUBSCRIBE. | | | | +| SIP header: SUBSCRIBE
Event: message-summary
Expires: 7200
Accept: application/simple-message-summary
NOTIFY | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | +| Comments:
ISC | | | | +| SUBSCRIBE | → | | SUT | +| CASE A | | | | +| 200 OK (SUBSCRIBE) | ← | | | +| CASE B | | | | +| 202 Accepted | ← | | | +| NOTIFY | ← | | | +| 200 OK (NOTIFY) | → | | | + +| TSS | TP | MWI reference | Selection expression | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------|-----------------------------| +| Network/AS_ServedUser | MWI_N01_002 | Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clause 3.1.4.3 of [RFC 3265] | | +| Test purpose:
The user is able to unsubscribe the service | | | | +| Verify that the SUBSCRIBE request will be accepted with Expires header with value zero; Check that the 2xx response to the unsubscribe contains also an Expires header with value zero. A NOTIFY is sent. | | | | +| SIP header: SUBSCRIBE
Event: message-summary
Expires: 0
Accept: application/simple-message-summary
200 OK (SUBSCRIBE)
Expires: 0
NOTIFY
Event: message-summary
Subscription-State: terminated(; reason=timeout) | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | +| Comments: | | | | +| ISC | | | SUT | +| SUBSCRIBE | → | | | +| 200 OK (SUBSCRIBE) | ← | | | +| NOTIFY | ← | | | +| 200 OK (NOTIFY) | → | | | + +| TSS | TP | MWI reference | Selection expression | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------|-----------------------------| +| Network/AS_ServedUser | MWI_N01_003 | Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clause 3.1.6.2 of [RFC 3265] | | +| Test purpose:
Refresh of current subscription. | | | | +| Verify that a SUBSCRIBE request will be accepted at any time before the original subscription expires when From header tag and the Call-ID in the subsequent SUBSCRIBE are equal to the values in the original SUBSCRIBE request. A NOTIFY is sent. | | | | +| SIP header: SUBSCRIBE 1
To-header with tag=tag_value1
CallId=callId_value1
SUBSCRIBE 2
To-header with tag=tag_value1
CallId=_callId_value1 | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | +| Comments: | | | | +| ISC | | | SUT | +| SUBSCRIBE 1 | → | | | +| CASE A | | | | +| 200 OK (SUBSCRIBE) | ← | | | +| CASE B | | | | +| 202 Accepted | ← | | | +| NOTIFY | ← | | | +| 200 OK (NOTIFY) | → | | | +| Refreshing of Subscription | | | | +| SUBSCRIBE 2 | → | | | +| CASE A | | | | +| 200 OK (SUBSCRIBE) | ← | | | +| CASE B | | | | +| 202 Accepted | ← | | | +| NOTIFY | ← | | | +| 200 OK (NOTIFY) | → | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------------------------------------------------------|-----------------------------|------------|--|------------|-------------|---|--|---------------|--|--|--------------------|---|--|---------------|--|--|--------------|---|--|--------|---|--|-----------------|---|--|--|----------------------------------|--|-------------|---|--|-------------------------------------|---|--| +| TSS
Network/AS_ServedUser | TP
MWI_N01_004 | MWI reference
Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clause 3.1.4.2 of [RFC 3265] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose:
Unsuccessful refresh of subscription | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Verify that a SUBSCRIBE request will be rejected with a "481 Call/Transaction Does Not Exist" response after expiry of the subscription when the subsequent SUBSCRIBE request uses the same dialog (From tag, CallId) as the actual expired subscription. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header: SUBSCRIBE 1
To-header with tag=tag_value1
CallId=_callId_value1
SUBSCRIBE 2
To-header with tag=tag_value1
CallId=callId_value1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
ISC SUT
SUBSCRIBE 1 ➔
CASE A
200 OK (SUBSCRIBE) ⬅
CASE B
202 Accepted ⬅
NOTIFY ⬅
200 OK (NOTIFY) ➔
Subscription time expired
SUBSCRIBE 2 ➔
481 Call/Transaction Does Not Exist ⬅
| | | | ISC | | SUT | SUBSCRIBE 1 | ➔ | | CASE A | | | 200 OK (SUBSCRIBE) | ⬅ | | CASE B | | | 202 Accepted | ⬅ | | NOTIFY | ⬅ | | 200 OK (NOTIFY) | ➔ | | | Subscription time expired | | SUBSCRIBE 2 | ➔ | | 481 Call/Transaction Does Not Exist | ⬅ | | +| ISC | | SUT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBSCRIBE 1 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (SUBSCRIBE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Subscription time expired | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBSCRIBE 2 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/Transaction Does Not Exist | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------------------------------------|-----------------------------| +| TSS
Network/AS_ServedUser | TP
MWI_N01_005 | MWI reference
Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clause 3.2.2 of [RFC 3265] | Selection expression | +| Test purpose:
NOTIFY request after initial subscription

Verify that after a successful subscription to a NOTIFY request is sent containing a "Subscription-State" header with the value "active" and an "expires" parameter which indicates the time remaining on the subscription. The From header tag and the Call-ID in the NOTIFY are equal to the values in the SUBSCRIBE.

The NOTIFY includes:
  • • Event header set to message-summary
  • • Subscription-State header set to active (optional) expires parameter set to the time remaining on the subscription
  • • Content-Type header set to application/simple-message-summary
MIME body:
  • • Messages-Waiting: yes
  • • Message-Account: identifying the served user (optional)
  • • msg-summary-line(s) (optional)
| | | | +| SIP header: SUBSCRIBE
Event: message-summary
Expires: 7200
Accept: application/simple-message-summary
NOTIFY
Event: message-summary
Subscription-State: active; expires=
Content-Type: application/simple-message-summary
Messages-Waiting: yes
| | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes
Comments:
ISC SUT
SUBSCRIBE →
CASE A
200 OK (SUBSCRIBE) ←
CASE B
202 Accepted ←

NOTIFY ←
200 OK (NOTIFY) → | | | | + + + + + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------------------------------------|-----------------------------| +| TSS
Network/AS_ServedUser | TP
MWI_N01_010 | MWI reference
Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clauses 3.5, 5.2 of [RFC 3842] | Selection expression | +| Test purpose:
NOTIFY indicates state change due to a message after successful subscription | | | | +| Verify that after a successful subscription a NOTIFY message is sent immediately. Afterwards verify that an additional NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes" when a change in the subscribed state occurs, e.g. a new message has been received at the message account. The From header tag and the Call-ID in the two NOTIFY requests are equal. | | | | +| SIP header: SUBSCRIBE
Event: message-summary
Expires: 7200
Accept: application/simple-message-summary
NOTIFY 1
Event: message-summary
Subscription-State: active; expires=
Content-Type: application/simple-message-summary
NOTIFY 2
Event: message-summary
Subscription-State: active; expires=
Content-Type: application/simple-message-summary
Messages-Waiting: yes | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | +| Comments:
ISC SUT
SUBSCRIBE →
CASE A
200 OK (SUBSCRIBE) ←
CASE B
202 Accepted ←

NOTIFY 1 ←
200 OK (NOTIFY) →
Action causes in a message summary state change
NOTIFY 2 ←
200 OK (NOTIFY) → | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------------------------------------|-----------------------------------------|------------|------------|-----------|---|---------------|--|--------------------|---|---------------|--|--------------|---|--------------|-------|-----------------|---|--------------------------------------------------------|--|----------|---|-----------------|---| +| TSS
Network/AS_ServedUser | TP
MWI_N01_011 | MWI reference
Clause 4.7.2.5 of [ITU-T Q.3626 v.1]
Clauses 3.5, 5.2 of [RFC 3842] | Selection expression
PICS 3/3 | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose:
NOTIFY indicates state change due to a message after successful subscription, opt-msg-headers are present

Verify that after a successful subscription a NOTIFY message is sent immediately. Afterwards verify that an additional NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes" and containing opt-msg-headers that describe newly added message(s) when a change in the subscribed state occurs, e.g. a new message has been received at the message account. The From header tag and the Call-ID in the two NOTIFY requests are equal. | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header: SUBSCRIBE
Event: message-summary
Expires: 7200
Accept: application/simple-message-summary
NOTIFY 1
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Messages-Waiting: yes
NOTIFY 2
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Messages-Waiting: yes

To:
From:
Message-ID: >
Message-Context: voice-message | | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments: Any set of opt-msg-headers is acceptable for this test, the above code serves only as an example
ISC SUT
SUBSCRIBE ➔
CASE A
200 OK (SUBSCRIBE) ⬅
CASE B
202 Accepted ⬅

NOTIFY 1
⬅
200 OK (NOTIFY) ➔
Action causes in a message summary state change
NOTIFY 2 ⬅
200 OK (NOTIFY) ➔
| | | | ISC | SUT | SUBSCRIBE | ➔ | CASE A | | 200 OK (SUBSCRIBE) | ⬅ | CASE B | | 202 Accepted | ⬅ |
NOTIFY 1 |
⬅ | 200 OK (NOTIFY) | ➔ | Action causes in a message summary state change | | NOTIFY 2 | ⬅ | 200 OK (NOTIFY) | ➔ | +| ISC | SUT | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBSCRIBE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (SUBSCRIBE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | +|
NOTIFY 1 |
⬅ | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | +| Action causes in a message summary state change | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY 2 | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (NOTIFY) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Network/AS_ServedUser | TP
MWI_N03_012 | MWI reference
Clause 4.7.2.5 of
[ITU-T Q.3626 v.1]
Clause 3.1.4.2 of
[RFC 3265] | Selection expression | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------------------------------------|----------------------| +| Test purpose: | | | | +| Refresh of subscription in a new dialogue | | | | +| Verify that at any time before a subscription expires the subscription will be successfully refreshed by sending of a SUBSCRIBE request on a different dialog (different Call-Id and From-Tag) as the existing subscription. The From header tag and the Call-ID in the SUBSCRIBE 1 are unequal to the values in the SUBSCRIBE 2. | | | | +| SIP header: SUBSCRIBE 1
Event: message-summary
Expires: 7200
Accept: application/simple-message-summary
SUBSCRIBE 2
Event: message-summary
Expires: 7200
Accept: application/simple-message-summary | | | | +| Preconditions: An arrangement exists with the service provider to deliver state changes | | | | +| Comments:
ISC SUT
SUBSCRIBE 1 →
CASE A
200 OK (SUBSCRIBE) ←
CASE B
202 Accepted ←

NOTIFY ←
200 OK (NOTIFY) →

Refreshing of Subscription
SUBSCRIBE 2 →
CASE A
200 OK (SUBSCRIBE) ←
CASE B
202 Accepted ←

NOTIFY ←
200 OK (NOTIFY) → | | | | + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4010.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4010.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..072f073b6d42cbfa77c827c76c611f286177034a --- /dev/null +++ b/marked/Q/T-REC-Q.4010.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee72ddf991b7b1d543b2694b1687804845ecb97da77cc35e98e4c7dbf5ac163d +size 4142 diff --git a/marked/Q/T-REC-Q.4010.3-201608-I_PDF-E/740442c999390734911677f01af0316d_img.jpg b/marked/Q/T-REC-Q.4010.3-201608-I_PDF-E/740442c999390734911677f01af0316d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50a287be9188a3895d792d04191acf60a05721a1 --- /dev/null +++ b/marked/Q/T-REC-Q.4010.3-201608-I_PDF-E/740442c999390734911677f01af0316d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5647f539e98cc88bf80f53e092c34c662157f6596f2f927a2401735966cc501 +size 14524 diff --git a/marked/Q/T-REC-Q.4011.1-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4011.1-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/Q/T-REC-Q.4011.1-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/Q/T-REC-Q.4014.1-201904-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.4014.1-201904-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/Q/T-REC-Q.4014.1-201904-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583 +size 3787 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aca069f376b8d207dd1d70427dc2e2e51a25c8a --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c8f3e305ca09abc24c5c5ba7636655320044573d619f08c943e52b174806b4a +size 16438 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..feb2de2950e3e079a0dd52f2c6aeebb1ce07d851 --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c00fb2c1638165465f5a80b514781ceb33a75a7c053d4473d0963c65bc26560 +size 48451 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09d9e9cfe163f049eecb7f1e1cc4371385bf774c --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db09f3a1b2ba8a541dfc71b766ee0fd48dc4e25c81890241eb558563ee5deba4 +size 116306 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..569e5c450c9771f512fe17d92dae26276f8d6de1 --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48ed7406b7b0c2468e0f8a0bea6cc16e44876f93fe200b22ff47b6d52b8d2393 +size 19406 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c437c735dcab44254959cad86d023e646d63425 --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e453695f9992296186a63f5585a54299a5e24371ac9324314c6dec7aa599ffd5 +size 15492 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba4a8a0aaeacd7f892b089d06742db876cce8a6 --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91896083b3dc3bcc138997c3043351ea287b13496105ad7e6c9ed8cfa40c5ae5 +size 71946 diff --git a/marked/Q/T-REC-Q.4016-201801-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79dc1b1d4733d4dc17ebe63d856f795d601c72c8 --- /dev/null +++ b/marked/Q/T-REC-Q.4016-201801-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b84ffa966a05054a64d89af0cb5fbb0a134224d3b570ce3f01573dfbba5b5eb +size 211573 diff --git a/marked/Q/T-REC-Q.4045-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846 --- /dev/null +++ b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75efa8e3513a799767c04a0bb7bcd87a550f2378f5880629068581808c1c9f7f +size 7353 diff --git a/marked/Q/T-REC-Q.4045-202312-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d30e9628cb0c9c6c5aef886660164c1d4978787b --- /dev/null +++ b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2d976f0883b3a0507ef87fe3bca6ddbde52a1ff42c62af4b7ee2d547995558b +size 31347 diff --git a/marked/Q/T-REC-Q.4045-202312-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d5737e7d76b2bbedb1dc66cd9a5fea0a7b052e1 --- /dev/null +++ b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dffcabf56c72a587a4289f2b3c5796e13b1f32342dd7d54fc17f91ee38d376a +size 29169 diff --git a/marked/Q/T-REC-Q.4045-202312-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5aeb2a3182c7b8e2ed723b64f529bd35af03ae3 --- /dev/null +++ b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8026b1cebef89ae9576f18325177a6e32d83f635df6cc9923267a81feaf22dd1 +size 46219 diff --git a/marked/Q/T-REC-Q.4045-202312-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f976bd89768a978e0b6886bf1865f0fb7c09997a --- /dev/null +++ b/marked/Q/T-REC-Q.4045-202312-I_PDF-E/raw.md @@ -0,0 +1,805 @@ + + +# Recommendation**ITU-T Q.4045 (12/2023)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Testing specifications – Testing specifications for Cloud computing + +--- + +# **Framework of network function virtualization automated testing** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| Testing specifications for next generation networks | Q.3900-Q.3999 | +| Testing specifications for SIP-IMS | Q.4000-Q.4039 | +| Testing specifications for Cloud computing | Q.4040-Q.4059 | +| Testing specifications for IMT-2020 and IoT | Q.4060-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.4045 + +# Framework of network function virtualization automated testing + +## Summary + +Recommendation ITU-T Q.4045 provides an overview and framework requirements of network function virtualization (NFV) automated testing. This Recommendation introduces the NFV automated testing framework, and provides an overview of NFV automated testing and design considerations. In addition, the framework and requirements for NFV automated testing are derived based on the use cases presented Appendix I. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4045 | 2023-12-14 | 11 | 11.1002/1000/15721 | + +## Keywords + +Automated testing, framework, NFV. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Overview of NFV automated testing..... | 3 | +| 6.1 NFV and NFV architecture ..... | 3 | +| 6.2 NFV automated testing..... | 4 | +| 7 Design consideration of NFV automated testing..... | 6 | +| 7.1 Role consideration for NFV automated testing..... | 6 | +| 7.2 Support of single component test and scenario test..... | 7 | +| 7.3 Support of reusability and flexibility..... | 7 | +| 7.4 Support of test result reliability ..... | 7 | +| 8 NFV automated testing framework ..... | 7 | +| 8.1 Resource data model..... | 7 | +| 8.2 NFV automated testing stages ..... | 8 | +| 9 Framework requirements of NFV automated testing ..... | 9 | +| 9.1 Requirements of NFVAT for test template support ..... | 9 | +| 9.2 Requirements of NFVAT for test task instantiation..... | 10 | +| 9.3 Requirements of NFVAT for test task orchestration and execution ..... | 10 | +| 9.4 Requirements of NFVAT for test report generation..... | 11 | +| 9.5 Requirements of NFVAT for test tool management ..... | 11 | +| 9.6 Requirements of NFVAT for test object management..... | 11 | +| 9.7 Requirements of NFVAT from system level..... | 12 | +| Appendix I – Use cases of automated testing of NFV ..... | 13 | +| I.1 Use case template ..... | 13 | +| I.2 Use case of NFV automated testing in cloud service continues
integration/continues delivery ..... | 13 | +| I.3 Use case of test case template ..... | 14 | +| I.4 Use case of NFV automated testing orchestration ..... | 16 | +| I.5 Use case of test reliability..... | 17 | +| I.6 Use case of NFV automated testing report..... | 19 | +| Bibliography..... | 20 | + + + +# Recommendation ITU-T Q.4045 + +## Framework of network function virtualization automated testing + +# 1 Scope + +This Recommendation provides the framework of network function virtualization (NFV) automated testing. It addresses the following subjects: + +- Overview of NFV automated testing; +- Design considerations of NFV automated testing; +- NFV automated testing framework; +- Framework requirements of NFV automated testing; +- Typical use cases to derive framework requirements. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T H.644.2] Recommendation ITU-T H.644.2 (2019), *Virtual content delivery network – Network virtualization*. +- [ITU-T Q.3719] Recommendation ITU-T Q.3719 (2019), *Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG)*. +- [ITU-T Q.4043] Recommendation ITU-T Q.4043 (2019), *Interoperability testing requirements of a virtual switch*. +- [ITU-T Y.2320] Recommendation ITU-T Y.2320 (2015), *Requirements for virtualization of control network entities in next generation network evolution*. +- [ITU-T Y.3150] Recommendation ITU-T Y.3150 (2020), *High-level technical characteristics of network softwarization for IMT-2020*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 network functions virtualization (NFV)** [b-ETSI GS NFV 003]: Principle of separating network functions from the hardware they run on by using virtual hardware abstraction. + +**3.1.2 test case** [b-ITU-T Y.4500.15]: Specification of the actions required to achieve a specific test purpose, starting in a stable testing state, ending in a stable testing state and defined in either natural language for manual operation or in a machine-readable language (such as testing and test control notation version 3 (TTCN-3)) for automatic execution. + +**3.1.3 test object** [b-ITU-T X.745]: A managed object that exists only for a controlled test invocation and which has attributes, operations and notifications that pertain to that instance of test. + +**3.1.4 test script** [b-ITU-T M.3710]: A service-specific software unit that can perform the test operations of a particular service automatically. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 test case template:** A structured description of a test case that organizes the unstructured data of the test case into a standardized data structure to simplify the conversion from test case to test script. + +**3.2.2 test entity:** An object in the test script that represents the software or hardware related to a test. + +**3.2.3 test orchestration:** A process that sorts the execution order of a set of test cases and interactions with the test tools for carrying out certain test cases in an automated manner. + +**3.2.4 test scheme template:** A combination of test cases and relevant test parameters for designing the testing activities required to accomplish specific testing objectives from a technical perspective. + +**3.2.5 test task:** The instantiation of a test scheme template, created by the tester, which is used to perform specific test activities. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-----------------------------------------------------------| +| 5GC | 5G Core | +| API | Application Programming Interface | +| BRAS | Broadband Remote Access Server | +| CD | Continues Delivery | +| CI | Continues Integration | +| CSC | Cloud Service Customer | +| CSP | Cloud Service Provider | +| CLI | Command Line Interface | +| E-CORD | Enterprise- Central Office Re-Architected as a Datacentre | +| ID | Identification | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| IT | Information Technology | +| LCM | Lifecycle Management | +| MANO | Management and Orchestration | +| MTU | Maximum Transmission Unit | +| NFV | Network Function Virtualization | +| NFVAT | NFV Automated Testing | +| NF | Network Function | +| NFVI | Network Function Virtualization Infrastructure | + +| | | +|--------|-----------------------------------------------| +| NFVO | Network Function Virtualization Orchestration | +| NGNe | Next Generation Network Evolution | +| NS | Network Service | +| NSD | Network Services Descriptor | +| ONAP | Open Network Automation Platform | +| OSM | Open Source MANO | +| SD-WAN | Software-Defined Wide Area Network | +| vCDN | Virtual Content Delivery Network | +| vCPE | Virtualized Customer Premises Equipment | +| vEPC | Virtual Evolved Packet Core | +| VIM | Virtual Infrastructure Management | +| VNF | Virtualization Network Function | +| VNFD | Virtualized Network Function Descriptor | +| VNFM | Virtualization Network Function Management | +| VOLTE | Voice Over LTE | +| XOS | X-Operating System | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +# 6 Overview of NFV automated testing + +## 6.1 NFV and NFV architecture + +Network function virtualization (NFV) is a technology which uses software to install, control and operate the network functions running on general hardware. The goal of NFV is to replace the private, specialized and closed network functions in the telecommunication network, and to realize a unified and universal software open architecture. + +Future networks are evolving with NFV for better flexibility and scalability. A lot of this work has been done in the International Telecommunication Union (ITU): + +- [ITU-T Y.2320] provides the requirements for virtualization of control network entities in next generation network evolution (NGNe), including the requirements of virtual infrastructures, virtualized network entities, and management systems. +- [ITU-T Y.3150] introduces NFV as a key component for network softwarization in IMT-2020. +- [ITU-T H.644.2] specifies the functional architecture, related functions and functional blocks, and high-level reference points which implement content delivery network virtualization by utilizing networking virtualization technologies. + +- [ITU-T Q.3719] describes a virtualized broadband network gateway with separated control plane and user plane, which is used to either augment or replace the existing traditional broadband remote access server (BRAS). +- [ITU-T Q.4043] introduces the virtual switch and its interoperability requirements. + +The underlying technology logic of NFV depends on virtualization technology. Virtualization technology can decompose general computing, storage, network and other hardware devices into a variety of virtual resources. This facilitates hardware decoupling and allows for the dynamic and flexible deployment of network functions in accordance with specific needs. + +Figure 6-1 shows the NFV high-level architecture, including network function virtualization infrastructure (NFVI), management and orchestration (MANO) and virtualization network function (VNF). + +![Figure 6-1 – High-level NFV architecture diagram. The diagram shows four stacked layers on the left and a vertical MANO block on the right. The layers from top to bottom are: 1. Virtualized network functions (VNFs) containing five VNF boxes. 2. NFV infrastructure (NFVI) containing three boxes: Virtual compute, Virtual storage, and Virtual network. 3. Virtualization layer. 4. Hardware resources containing three boxes: Compute, Storage, and Network. The MANO block on the right is labeled 'NFV management and orchestration' and spans the height of the NFVI and VNF layers.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 6-1 – High-level NFV architecture diagram. The diagram shows four stacked layers on the left and a vertical MANO block on the right. The layers from top to bottom are: 1. Virtualized network functions (VNFs) containing five VNF boxes. 2. NFV infrastructure (NFVI) containing three boxes: Virtual compute, Virtual storage, and Virtual network. 3. Virtualization layer. 4. Hardware resources containing three boxes: Compute, Storage, and Network. The MANO block on the right is labeled 'NFV management and orchestration' and spans the height of the NFVI and VNF layers. + +Q.4045(23) + +**Figure 6-1 – High-level NFV architecture** + +Sourced from [b-ETSI GS NFV 002] + +NFVI includes the virtualization layer and hardware resources, which can be deployed across several physical locations. All virtual resources should be in a unified shared resource pool. VNFs run on top of NFVI, which provides some kinds of network services deployed in virtual machines, containers or bare-metal servers by using the infrastructure provided by NFVI. MANO provides the overall management and orchestration of NFV, which is composed of network function virtualization orchestration (NFVO), virtualization network function management (VNFM) and virtual infrastructure management (VIM). They manage, respectively the network service (NS) life-cycle, the VNF life-cycle and the NFVI. + +## 6.2 NFV automated testing + +### 6.2.1 Challenges in NFV testing + +The three main working layers of NFV are identified as the VNF layer, the NFVI layer, and the NFV MANO layer. Each layer is composed of multi-components provided by different vendors. Each component depends on and calls on each other. Because many implementations of components are private commercial solutions instead of open sourced, the compatibility and interoperability between them is poor, and the system integration complexity is high. In order to promote the application and implementation of NFV architecture, a lot of repetitive testing work needs to be carried out. Compared with traditional IT testing, NFV testing has the following challenges: + +- With more components involved, the testing environment is more complicated. Upgrades in each component may lead to changes in the testing environment, requiring re-testing. At the + +same time, the iteration cycle of NFV network elements is shorter, which then needs a higher testing frequency. + +- Adoption of NFV has cloud-based elastic resource management issues, orchestration issues, operation and maintenance issues, as well as interoperability issues caused by layer decoupling. Consequently, the test content and test scope are larger. + +Testing carried out manually is inefficient and unreliable. There is a need to develop NFV automated testing tools to improve the efficiency and reliability of NFV testing. Test cases in automated testing are usually developed before test execution in the format of scripts which can be executed repeatedly to reduce testing costs. It is also easy to fix the script flaws after they are discovered and modify the script based on different test scenarios. Additionally, automated testing can take advantage of a lot of existing testing tools and executes test tasks in parallel. + +### **6.2.2 Test dimensions in NFV automated testing** + +NFV automated testing should support the following test dimensions for baseline, security and assurance so that basic goals of solution validation, interoperability, verification of service layer agreement (SLA)/assurance, and deployment readiness can be validated. + +Test dimensions for VNF: + +- Basic validation – verification of core services, lifecycle management (LCM) operations, and onboarding. +- Functionality – verification of basic functionality, after reboot, behaviour with virtual infrastructure management (VIM) network fault, behaviour when VIM controller is restarted, VIM network restarted, and support for IPv6-Only (test by turning off IPv4 on the interfaces). +- Performance – verification based on different resource configurations, max throughput, instance creation/deletion time, forwarding performance benchmarking using different traffic types, packet/frame size, and load tests. +- Scale – verification of multiple instances of VNF, max number of VNF, and scale-out/in. +- VNFM interactions – verification of integrity of VNFD/NSD, instantiation, placement, destruction, resilience/recovery, monitoring, backup/restore, updates/roll-back, LCM after rebooting the VNF, and VNF config injection/reconfig time. +- NFVO interactions – verification of VNF deployment using available network services descriptors (NSDs), live migration, and fault management and logging. +- Service chain. + +Test dimensions for NFVI: + +- NFVI stack installation. +- Fault management and log collection. +- MTU changes. +- Platform awareness. +- NFVI under loaded conditions. +- Support for IPv6-only (test by turning off IPv4 on the interfaces). +- Support for service chain. + +Test dimensions for MANO: + +- VNF types. +- Lifecycle management – verification of VNFD/VNF image onboarding, deployment using supported flavour, and instantiation/destruction/resilience/recovery/monitoring/updates/rollbacks. + +- Various VIM infrastructure. +- VNF placement/scaling. +- NFVO fault management and log collection. +- Different types of NFVO (component testing of VNFM). +- End-to-end service orchestration. +- Different types of VNFM (component testing of NFVO). +- Different types of VIM (component testing of NFVO). +- Network service instantiation. + +Broad test dimensions to cover interoperability, compatibility, assurance, service orchestration, and deployment readiness: + +- VNF onboarding. +- VNF config upgrades. +- Data plane performance. +- Fault and healing. +- Functionality. +- Service instantiation. +- NFV service configuration. +- Control plane scaling. +- Placement constraints. +- Use-case specific test cases. + +# 7 Design consideration of NFV automated testing + +## 7.1 Role consideration for NFV automated testing + +There are three roles involved in NFV automated testing, test designer, script developer and tester: + +- NFV test designer: the person who is responsible for the design of NFV test plan. Based on the test purpose, the role involves identifying what test cases need to be conducted with which test tools during the test, determining the execution order of test cases, and determining what parameters need to be configured. The NFV test designer in NFV automated testing is usually someone with professional NFV background and rich test experience. +- Script developer: the person who is responsible for developing of test scripts based on the test cases designed by test designers. The script developer is usually a programmer with a background in computer or software development. There is no need for the script developer to have NFV related experience. +- NFV tester: the person who is responsible for conducting of NFV test, which involves choosing an appropriate test plan, setting up the test environment, executing test cases automatically and analysing testing results. The NFV tester is someone who is familiar with the NFV automated testing tool. + +## 7.2 Support of single component test and scenario test + +Three main working layers are identified in the NFV architecture: VNF, NFVI and NFV MANO. Each layer is composed of multiple components. It is necessary for a single component test to make sure it can function correctly. NFV automated testing needs to support single component tests. + +Applications and implementations of NFV architecture usually include multiple components provided by various vendors from the three working layers. These components collaborate to enable different scenarios. Examples of NFV scenarios are: 5GC, VIMs, voice Over LTE (VOLTE), enterprise software-defined wide area network (SD-WAN), enterprise-central office re-architected as a datacentre (E-CORD), access vCPE, service provider virtual evolved packet core (vEPC), virtual content delivery network (vCDN), etc. It is essential for a specific scenario test to confirm whether these components are compatible with each other and whether they provide corresponding functions together. NFV automated testing needs to support scenario tests. + +## **7.3 Support of reusability and flexibility** + +In order to promote the applications and implementations of NFV architecture in different locations, especially for telecommunication providers and manufacturers, many repetitive testing needs to be carried out. NFV automated testing needs to support test reusability to minimize redundant work, which can be achieved by using a template. Templating includes the templating of test schemes and the templating of test cases, which can be used directly or be customized based on different requirements. They are both concepts of the test design stage. + +In addition, applications and implementations of NFV architecture may vary across different locations due to special local conditions. NFV automated testing should offer flexible scalability, enabling NFV testers to adjust test schemes, test cases and relevant test parameters in order to adapt to different conditions. + +## **7.4 Support of test result reliability** + +Automated testing minimizes manual involvement, but ensuring the reliability of test results is crucial. However, the NFV system is complex, a test task will contain multiple complete test cases, and each test case contains multiple steps, each of which performs multiple operations on multiple test objects. Retaining the intermediate operating state becomes challenging, making it difficult to reproduce the exact state after the test, and compromising the reliability of the test results. To address this challenge a real-time test log during test execution, a test task stoppage to check the status, and a detailed test report after the test is completed, are needed. + +# **8 NFV automated testing framework** + +## **8.1 Resource data model** + +The core elements of resource data models in NFV automated testing include the test scheme template, test case template, test task, test case, test tool, test parameter, test object and test report. The relationship among these elements is shown in Figure 8-1. + +![Figure 8-1: Resource data model in NFV automated testing. This is a class diagram showing relationships between Test scheme template, Test case template, Test report, Test task, Test case, Test tool, Test parameter, and Test object. Test scheme template (1) has 'n' Test case templates and 'n' Test tasks. Test case template (1) has 'n' Test cases. Test task (1) has 'n' Test cases, 'n' Test parameters, and 'n' Test objects. Test case (1) has 'n' Test parameters and is associated with '1' Test tool. Test report (n) is associated with '1' Test task. Test parameter (n) is associated with '1' Test object.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +classDiagram + TestSchemeTemplate[Test scheme template] "1" -- "n" TestCaseTemplate[Test case template] + TestSchemeTemplate "1" -- "n" TestTask[Test task] + TestCaseTemplate "1" -- "n" TestCase[Test case] + TestTask "1" -- "n" TestCase + TestTask "1" -- "n" TestParameter[Test parameter] + TestTask "1" -- "1" TestObject[Test object] + TestCase "1" -- "n" TestParameter + TestCase "1" -- "1" TestTool[Test tool] + TestReport[Test report] "n" -- "1" TestTask + TestParameter "n" -- "1" TestObject + +``` + +Figure 8-1: Resource data model in NFV automated testing. This is a class diagram showing relationships between Test scheme template, Test case template, Test report, Test task, Test case, Test tool, Test parameter, and Test object. Test scheme template (1) has 'n' Test case templates and 'n' Test tasks. Test case template (1) has 'n' Test cases. Test task (1) has 'n' Test cases, 'n' Test parameters, and 'n' Test objects. Test case (1) has 'n' Test parameters and is associated with '1' Test tool. Test report (n) is associated with '1' Test task. Test parameter (n) is associated with '1' Test object. + +Q.4045(23) + +**Figure 8-1 – Resource data model in NFV automated testing** + +A test scheme template refers to a template for designing the testing activities required to accomplish specific testing objectives from a technical perspective. A test scheme template combines test cases templates and relevant test parameters, which can be used directly or be customized based on different test objectives. A test case template serves as a structured description of a test case, organizing the unstructured data of the test case into a standardized data structure to simplify the conversion from test case to test script. A test task is the instantiation of a test scheme template while a test case is the instantiation of a test case template, both by filling in the parameters. A test object represents a managed object which has attributes, operations and notifications to the test task. A test tool is the hardware or software used to carry out or assist in carrying out the test case required. A test report is a document produced at the end of the test giving an overall summary of the test carried out. + +## 8.2 NFV automated testing stages + +![Figure 8-2: NFV automated testing stages. This diagram shows two rows of stages. The top row has three large chevron-shaped stages: Design (grey), Develop (green), and Execution (orange). The bottom row has seven smaller chevron-shaped stages: Plan (light blue), Design (light blue), Code (yellow), Verify (red), Initiation (green), Orchestration and execution (orange), and Check and end (dark orange).](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +``` + +graph LR + subgraph TopRow [ ] + direction LR + D1[Design] --> D2[Develop] --> E[Execution] + end + subgraph BottomRow [ ] + direction LR + P[Plan] --> Des1[Design] --> C[Code] --> V[Verify] --> I[Initiation] --> OE[Orchestration and execution] --> CE[Check and end] + end + style TopRow fill:none,stroke:none + style BottomRow fill:none,stroke:none + +``` + +Figure 8-2: NFV automated testing stages. This diagram shows two rows of stages. The top row has three large chevron-shaped stages: Design (grey), Develop (green), and Execution (orange). The bottom row has seven smaller chevron-shaped stages: Plan (light blue), Design (light blue), Code (yellow), Verify (red), Initiation (green), Orchestration and execution (orange), and Check and end (dark orange). + +Q.4045(23) + +**Figure 8-2 – NFV automated testing stages** + +The lifecycle of NFV automated testing includes 7 stages, where each stage is iterative. Each stage defined in Figure 8-2 is described as follows: + +### 1) Plan + +At this stage, the NFV test designer defines a test plan based on the test requirements provided by NFV tester. The test plan can be presented by test task description documents and test case description documents. + +### 2) Design + +At this stage, the NFV test designer designs what test cases need to be executed to complete the test scheme, what input should be set for each test case template, and the execution order of the test + +cases based on the test plan. Templates are generated after the design is completed, and these templates follow the design considerations presented in clause 7. + +### **3) Code** + +At this stage, the test developer develops the test script according to the test case template designed by the NFV test designer and the test parameters required by the test case. + +### **4) Verify** + +At this stage, the test developer tests the usability of the test script and resolves any bugs found. + +### **5) Initiation** + +At this stage, the NFV tester selects the required test scheme template and instantiates the test task to perform automated testing on the test objects. + +### **6) Orchestration and execution** + +At this stage, the execution order of test cases is generated for the tester to adjust according to specific needs. Then the test tools will carry out those test cases in an automated manner. + +### **7) Check and end** + +At this stage, the tester will get a test report produced by the system. The tester measures and analyses the report and then conducts acceptance of the test objects. If the acceptance conclusion is failed, new demands will be provided to the product development team. + +# **9 Framework requirements of NFV automated testing** + +## **9.1 Requirements of NFVAT for test template support** + +It is required that NFV automated testing (NFVAT) provides test scheme templates and test case templates for NFV testers. + +NOTE 1 – Test scheme template and test case template are the concepts of the test design state. Test scheme templates can be divided into component test scheme templates and scenario test scheme templates. + +NOTE 2 – A component test scheme template of NFV aims at the testing of a single component which only belongs to one working layer in NFV architecture. + +NOTE 3 – A scenario test scheme template of NFV aims at the testing of a specific scenario to confirm whether the functional components are compatible with each other and whether they have the ability to provide corresponding capabilities together in a specific scenario. An NFV scenario consists of multiple components from different NFV architecture layers. + +It is required that NFVAT provides a test scheme template repository and a test case template repository to upload, store, update, and delete templates for NFV testers. + +It is required that NFVAT generates test case templates according to the test information input by NFV testers. + +NOTE 4 – Test case templates include test case description, inputs, preconditions, test steps, and expected results. + +NOTE 5 – Test information input by NFV testers is the description of test steps and expected results. + +NOTE 6 – Test case description includes test case ID, test case type, test object, and test case provider. + +NOTE 7 – Inputs include the information required for script execution and the serialized byte sequence of the test entity. + +NOTE 8 – Preconditions include test cases that this test case depends on, conditions that the test environment needs to meet, and scripts required to verify the conditions. + +NOTE 9 – A test step includes step description, preconditions, step identifiers, and step details. The preconditions are used to identify whether the step can be executed. The step details are used to define the specific actions of each step. + +NOTE 10 – Step details define the interaction type, entities involved in the test, interaction content, and output information. The type is command line interface (CLI) or application programming interface (API). The output information includes the log and the entity generated by the test step, and the result of the test step. + +NOTE 11 – Expected results describe the final results that the test should obtain. + +It is recommended that NFVAT generates test scripts based on the test case template. + +## 9.2 Requirements of NFVAT for test task instantiation + +It is required that NFVAT manages the life cycle of test tasks, including the creation, start, update, pause and deletion of test tasks. + +It is required that NFVAT manages test parameters, which contains the parameters of test cases, and the parameters of test component/scenario. + +NOTE 1 – Examples of test case parameters are the type of test case to indicate whether it is a functional test case or a performance test case, test tool which will carry out the test case, and test category parameter closed/semi-closed to identify whether this test case will pass data to other test cases. + +NOTE 2 – Examples of test component/scenario parameters are the test object/objects of the test component/scenario, the execution order and number of all test cases, input and output data of all test cases. + +It is required that NFVAT provides a user interface for NFV testers to create test tasks, search test task status and view test task results. + +## 9.3 Requirements of NFVAT for test task orchestration and execution + +It is required that NFVAT provides an orchestration engine to analysis test cases and form a process file recording the execution order of each test case in the test template. + +It is required that NFVAT carries out test cases in the test scheme template according to the execution order in the process file. + +It is recommended that NFVAT provides test detection points and supports troubleshooting during test task execution. + +NOTE 1 – The test case script developer sets test detection points and develops test cases according to test requirements during the development of test case scripts. + +NOTE 2 – Before testing, the NFV tester selects several expected pause positions from the test detection points. + +NOTE 3 – During the execution of the test task, when it is executed to the detection point of the test case script, check whether the position of the detection point matches the expected pause position; If it matches, generate a test pause instruction and pause the test task. The tester shall inspect the intermediate state of the test. If it does not match, generate the test continue instruction and continue to execute the test task. + +It is recommended that NFVAT supports the storing and viewing of the intermediate status of the test task execution. + +It is required that NFVAT generates independent log files for the main script log, VIM log, NFVO log, VNFM log, VNF log for each test case, as applicable. + +It is required that NFVAT monitors the test task execution metrics to reflect test status. + +NOTE 4 – The metrics of NFV automated testing task are used by both NFV tester and operator to know whether a test task works properly. It usually includes resource-level metrics and test-level metrics. + +NOTE 5 – Resource-level metrics are metrics of resources used during NFVAT, including compute/network/storage hardware metrics, virtualization layer metrics, virtual compute/network/storage + +resource metrics, VNF metrics, etc. Each of the resource-level metrics can be divided into resource utilization rate, resource operation status, resource quantity, etc. + +NOTE 6 – Test-level metrics are defined by the NFVAT designer, and vary from test task to test task. Taking the 5GC network function testing task as an example, metrics include session number, traffic throughput, etc. + +It is required that NFVAT stores the history of test task failures during task execution. + +It is recommended that NFVAT adaptively integrates with different testing tools and facilitates the transfer of test parameters across these tools. + +It is recommended that NFVAT converts the test case data into test input data that conforms to the data specification of a specific testing tool. + +It is recommended that NFVAT determines the specific testing tool that matches the test case based on the characteristics of the test case from multiple testing tools and invoke the specific testing tool to execute the test case using the testing tool's data specifications for the test input data. + +NOTE 7 – The characteristics of the test case is extracted by analysing test cases. + +NOTE 8 – The test cases and their associated data are retrieved from the orchestration engine. + +It is required that NFVAT restores the initial state of the test environment until the NFV tester deletes the test task. + +## **9.4 Requirements of NFVAT for test report generation** + +It is required that NFVAT generates a test report of each test task automatically for the NFV tester to download. + +It is required that NFVAT provides information about the test task in the report. + +NOTE 1 – Information includes stakeholders involved in the test, information about the test environment, all parameters set during the task, records of the execution process, problems found and, etc. + +It is required NFVAT provides test result to indicate whether the test is passed, partially passed or failed. + +It is recommended NFVAT scores the test based on test results. + +It is recommended that NFVAT provides a setting on the storage time length of the test report, beyond which test reports would be automatically deleted. + +It is recommended that NFVAT provides the ability to analyse the execution results of multiple test tasks from various dimensions and generates reports with statistical information. + +NOTE 2 – The dimensions include a specific test object, a specific test case, a specific time period, etc. + +## **9.5 Requirements of NFVAT for test tool management** + +It is recommended that NFVAT supports registry of the test tool to the test tool catalogue. + +It is required that NFVAT provides an instantiation ability of the test tool according to corresponding test cases and calls of test tools to execute test cases. + +It is recommended that NFVAT provides version control for test tools. + +It is recommended that NFVAT supports pushing test tools from a repository to a remote NFV test bed. + +It is recommended that NFVAT maintains the dependencies of the testing tool's libraries. + +It is recommended that NFVAT verifies the network connectivity of test tools. + +## **9.6 Requirements of NFVAT for test object management** + +It is required that NFVAT supports registry of test object to the test object catalogue. + +It is recommended that NFVAT verifies the network connectivity of test objects. + +It is recommended that NFVAT provides version control for test objects. + +## **9.7 Requirements of NFVAT from system level** + +It is required that NFVAT could be customizable to accommodate different types of MANO platforms and include at least one open-source MANO platform. + +NOTE 1 – Examples of open-source MANO platforms are OSM, ONAP, Tacker, XOS, etc. + +It is recommended NFVAT includes pre-built dynamically configurable NFVI templates. + +It is required that NFVAT could be deployed in containers or VMs based on open-source infrastructure platforms. + +NOTE 2 – Examples of open-source infrastructure platforms are OpenStack and Kubernetes. + +It is required that NFVAT provides extensible interfaces for external hardware traffic generators and network devices. + +It is required that NFVAT supports being customizable for product vendor and end user needs. + +# Appendix I + +## Use cases of automated testing of NFV + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Use case template + +The use cases developed in this appendix should adopt the following unified format for consistent readability and convenient material organization. + +**Table I.1 – Use case template** + +| | | +|----------------------------|--------------------------------------------------------------------------------------------------------------| +| Title | Title of the use case | +| Description | Scenario description of the use case | +| Roles | Roles involved in the use case | +| Figure (optional) | Figure to explain the use case, but is not mandatory | +| Pre-conditions (optional) | The necessary pre-conditions that should be achieved before starting the use case. | +| Post-conditions (optional) | The post-condition that will be carried out after the termination of current use case. | +| Derived requirements | Requirements derived from the use cases, whose detailed descriptions are presented in the dedicated clauses. | + +## I.2 Use case of NFV automated testing in cloud service continues integration/continues delivery + +| | | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of NFV automated testing in cloud service continues integration / continues delivery | +| Description |

A VNF can be provided based on cloud computing, and the continuous integration and delivery of cloud services can be used to accelerate the online process of network functions. The continuous integration and delivery process of a cloud computing-based VNF can be summarized as follows:

  • – Cloud service partner (CSN): network service developers analyse the cloud service customer (CSC): network service customer's network requirements and define specific tasks.
  • – Based on this, the CSN: network service developers provide a development plan. The plan and corresponding tasks are created on the development platform.
  • – Then, a series of CI based development practices are used to ensure that VNF code or functional entities can be integrated, tested and deployed.
  • – Strict automated tests are conducted to verify whether the requirements of VNF are met. Only the code or functional entity that has passed the automated test can be deployed to the real environment through the deployment pipeline defined in the CD.
  • – After the code is delivered to the production environment, cloud service provider (CSP): network service provider automatically monitors its status to receive quality assurance feedback. According to the service level agreement (SLA) between CSP: network service provider and CSC: network service customer, CSP: network service provider is responsible for the continuity of network functions in the cloud.
  • – Finally, CSP: network service provider provides VNF services to CSC: network service customer.
  • – VNF automated testing is an important part of continuous integration and
| + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | continuous delivery, which determines whether the service can meet user needs before deployment. | +| Roles |
  • – CSN: network service developers
  • – CSC: network service provider
  • – CSP: network service customer
| +| Figure (optional) |

Image: Diagram of NFV automated testing in cloud service continuous integration/continuous delivery. It shows two main actors: Cloud service partner: Network service developer (CSN) and Cloud service provider (CSP). CSN's activities include Design, create and maintain service components, Compose services, and Test services. CSP's activities include Deploy and provision services and Performance service level management. Below these, a horizontal flow shows the stages: Plan, Design, Code, Build, TEST, Release, Deploy, Operate. A 'Continuous integration' bar spans from Design to Release. A 'Continuous delivery' bar spans from Code to Operate. A 'Feedback' loop connects Operate back to Design. A 'Measurement' bar is at the bottom, connected to Continuous delivery and Feedback. The diagram is labeled Q.4045(23).

Figure I.1 – NFV automated testing in cloud service continues integration/continues delivery

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Derived requirements |
  • – 9.1 Requirements of NFVAT for test template support
  • – 9.2 Requirements of NFVAT for test task instantiation
  • – 9.3 Requirements of NFVAT for test task orchestration and execution
  • – 9.4 Requirements of NFVAT for test report generation
  • – 9.5 Requirements of NFVAT for test tool management
  • – 9.6 Requirements of NFVAT for test object management
  • – 9.7 Requirements of NFVAT from system level
| + +## I.3 Use case of test case template + +| | | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of test case template | +| Description |

In the process of NFV testing, the NFV tester often needs to create a virtual machine for test tools to call. As a basic operation, a test case template can be created for it, which is convenient for repeated use in the future. A test case template is designed by the NFV test designer.

This test case template should contain the following information:

  • – test case ID;
  • – test case type: this test case is a functional test case;
  • – precondition: the jump host where the test tool is located needs to communicate with the network where the virtual machine will be created. The network
| + +connection can be verified by the ping command; + +- input information: the name of the virtual machine, the flavour of the virtual machine, the network of the virtual machine, etc.; +- test steps: call the API of the virtual infrastructure management platform, request to create a virtual machine; +- expected results: virtual machine1 is successfully created, the operating system of virtual machine1 is working well, and virtual machine1 is in flavour1. + +The test case template can be structured as below. + +--- + +ID: 002 + +Test\_case\_type: functional + +Object: OpenStack + +Inputs: + +- name: flavor\_1 +- type: openstack\_flavor +- name: network\_1 +- type: openstack\_network + +pre\_conditions: + +- dependency: 001 #None +- condition: jump host connects to network\_1 + +pre\_steps: + +- step\_id: server\_ping\_server +- description: jump host connects to network\_1 +- step\_detail: +- entity: \$jump host\$network\_1 +- type: CLI +- content: ping \$network\_1.gateway +- // the gateway of network\_1 +- output: +- log: \$log1 +- result: \$status1 + +steps: + +- step\_id: create\_server +- description: call openstack create virtual machine API +- pre\_condition: \$status1 +- step\_detail: +- entity: \$openstack +- type: API +- content: #API request body +- output: +- log: \$log2 +- result: \$status2 + +| | | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

entity: \$virtual machine1

Expected results:

  • - virtual machine1 is successfully created
  • - the operating system of virtual machine1 is working well
  • - virtual machine1 is in flavour1

Based on the test case template, the test case can be easily transformed into test scripts by test script developer.

| +| Roles |
  • – NFV test designer
  • – Script developer
  • – NFV tester
| +| Figure (optional) |

Image: Diagram illustrating the usage of a test template. An 'NFV tester' provides 'Test information' to a 'Test case template'. The template contains sections for 'Input', 'Precondition' (with 'Steps' and 'Results'), and two 'Test step' blocks (each with 'Preconditions', 'Entity', 'Type', 'Steps', and 'Outputs'). The template generates 'Expected results' and 'Scripts'. Reference Q.4045(23) is shown in the bottom right.

Figure I.2 – Usage of test template

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Derived requirements |
  • – 9.1 Requirements of NFVAT for test template support
| + +## I.4 Use case of NFV automated testing orchestration + +| | | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of NFV automated testing orchestration | +| Description |

The purpose of NFV test orchestration is to create multiple automated test jobs and execute them one by one as planned. It is the most critical step in NFV automated testing. Figure I.3 shows an implementation example of test orchestration. It usually includes the following modules:

  • – Workflow manager: receives requests from the website, generates workflow description files, deploys specific workflows to the workflow engine, instantiates workflows, etc.
  • – Workflow engine: receives the workflow issued by the workflow manager, and generates the job to be processed according to the parameters input by the NFV tester.
| + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
  • – Worker: provides the job workers of various types of jobs to process jobs. The workflow engine can call the job workers to execute jobs or put the jobs in the queue for the job workers to obtain.
  • – Query manager: NFV tester queries the execution status and results of workflow instances by query manager.
| +| Roles | – NFV tester | +| Figure (optional) |

Image: Diagram of NFV automated testing orchestration process. On the left, the NFV tester components are shown: Workflow manager (BPMN files, Workflow deployment, Workflow initiation), Worker (Yardstick jobworker, Functest jobworker), and Query manager (State, Result). On the right, the Workflow engine components are shown: Broker, Gateway, Broker, Elasticsearch, and Data/audit log. A gRPC connection links the Workflow manager to the Gateway. A REST connection links the Query manager to the Elasticsearch. A label 'Q.4045(23)' is at the bottom right of the diagram.

Q.4045(23)

| +| | Figure I.3 – NFV automated testing orchestration process | +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Derived requirements |
  • – 9.3 Requirements of NFVAT for test task orchestration and execution
  • – 9.5 Requirements of NFVAT for test tool management
  • – 9.6 Requirements of NFVAT for test object management
| + +## I.5 Use case of test reliability + +| | | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of test reliability | +| Description |

Automated testing requires less manual participation. The state of the system usually returns to the initial state after the test is completed. If the automatic testing is executed in a black box, it is difficult to reproduce and check the intermediate state of the test after the test is completed. This reduces the credibility of the final test results. At the same time, if the test is terminated due to problems encountered during the test, these problems may be a problem of VNF service, a problem of network configuration, a problem of environment setting, a problem of resource quota, etc. It is difficult to locate faults.

If a test pause point is provided during the test process for testers to pause the execution of the test during NFV automatic testing and check the intermediate state of the test, such as checking the network connection of virtual machine and verifying the configuration of VNF, the reliability of test results can be improved. At the same time, it can provide a guarantee for the troubleshooting of environmental problems, the recurrence of faults and the confirmation of the state of test objects.

The interaction is as follows:

| + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
  • – NFV test designer designs pause points for each test case.
  • – Script developers develop test case scripts, set check points at key positions of test cases, and write relevant codes.
  • – NFV testers create test task, select test cases in NFV automatic testing platform according to test requirements. For each test case, NFV tester select the pause points that meet the test requirements from the check points in the test case script. A list of test task pause points is formed.
  • – The NFV automatic testing platform selects the corresponding test tool, and gradually performs the test on the test object according to the step information of the test case.
  • – When the test case script executes to the check point, query whether the current check point is in the test task pause point list. If the check point is in the test task pause point list, the automatic test platform sends the test pause instruction to the test tool to pause the current test task.
  • – After the test task is suspended, the tester logs in the management module or GUI of the test object and the test environment to check the intermediate state, such as the network connection of the virtual machine and the port group setting of the virtualization platform, and analyses whether the current state is consistent with expectation.
  • – If the situation is inconsistent with the expectation, troubleshoot the problem. If the current state is consistent with the expectation, requests to continue the test.
  • – The automated test platform receives the request to continue the test and continues to execute the test case until the test task is completed.
| +| Roles |
  • – NFV test designer
  • – Script developer
  • – NFV tester
| +| Figure (optional) |

Image: Interaction diagram between NFV testers and NFV automatic testing system for test reliability. The diagram shows the flow of control and data between the NFV tester, NFV automated testing system, Testing tool (Yardstick, Functest), Test object (Hypervisor, VNF), Test case script, and Test task pause point list. The process involves creating a test task, selecting a tool, executing the script, pausing at designated points, checking status, and continuing the task.

The diagram illustrates the interaction between the NFV tester and the NFV automated testing system. The NFV tester initiates the process by sending a 'Create test task' (②-1) and 'Test task continue instruction' (⑤-2) to the NFV automated testing system. The system then selects a testing tool (③-1) and sends a 'Pause test task' (④-2) and 'Continue test task' (⑥) instruction to the testing tool (Yardstick, Functest, etc.). The testing tool executes the test task (③-2) on the test object (Hypervisor, VNF, etc.) according to the test case script. The test case script contains steps (Step A, Step B) with pause points (Pause point A1, Pause point B1). The NFV tester checks the status (⑤-1) and selects pause points (②-2) from the test case script. The NFV automated testing system matches the pause points (④-1) and updates the test task pause point list. The script developer develops the test case script and adds pause points (①). The test task ends (⑥).

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | + +**Figure I.4 – Interaction between NFV testers and NFV automatic testing system for test reliability** + +Q.4045(23) + +| | | | +|----------------------|-----|-----------------------------------------------------------------| +| Derived requirements | 9.1 | Requirements of NFVAT for test template support | +| | 9.2 | Requirements of NFVAT for test task instantiation | +| | 9.3 | Requirements of NFVAT for test task orchestration and execution | + +## I.6 Use case of NFV automated testing report + +| | | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of NFV automated testing report | +| Description |

The test report of NFV automated testing comprises the documents which can present the process and results of the test, present the problems and defects found during the test, provide a basis for correcting the problems in the NFV system, and lay a foundation for NFV acceptance and delivery.

Test report should contain the following information:

  • – Information of the NFV tester.
  • – Test object information, including product name, version and product provider.
  • – Test environment information, including deployment location, surrounding systems and equipment, and equipment connection, etc.
  • – Test task information, including task name, test template used.
  • – Test case information, including the total amount of test cases, the detailed information of each test case, the start time and end time of each test case, the test conclusion of each test case (including pass, fail, partial pass), etc.
  • – The execution process of the test, including the resources used, the parameters configured, the intermediate execution status, the execution results obtained, the verification of the results, etc.
  • – Test score and test result.

An example of the test report is shown as below.

Tester: Davide
Test object: hypervisor
Product type: computing virtualization
Product version: v0.05
Provider: Hua Wei
Environment name: Washington Data Center
Environment description: None
Test case amount: 3
Amount of test cases that do not pass: 0
Amount of test cases that pass: 3
Test score: 100
Test result: PASS

| +| Roles | – NFV tester | +| Figure (optional) | | +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Derived requirements | – 9.4 Requirements of NFVAT for test report generation | + +# Bibliography + +- [b-ITU-T M.3710] Recommendation ITU-T M.3710 (2013), *Overview of an automated service test to support cost-efficient telecom service assurance.* +- [b-ITU-T X.745] Recommendation ITU-T X.745 (1993), *Information technology – Open Systems Interconnection – Systems Management: Test management function.* +- [b-ITU-T Y.4500.15] Recommendation ITU-T Y.4500.15/Q.3955 (2018), *oneM2M – Testing framework.* +- [b-ETSI GS NFV 002] ETSI GS NFV 002 V1.2.1 (2014), *Network functions virtualisation (NFV); Architectural Framework.* +- [b-ETSI GS NFV 003] ETSI GS NFV 003 V1.5.1 (2020), *Network functions virtualisation (NFV); Terminology for main concepts in NFV.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c22aa9df6e0bbedfedc67f3cda0fce78a81b50f --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28613cdae517bd58169e452b715590d579d626a8a71808711e714415616f819e +size 49651 diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c1c9741e3a065a4e9478db83bc43c2473e397a1 --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f3d1856418e77aa2239aaadb27581c9ae53c1cf1ceaa3d936a184a93da04a07 +size 24396 diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..108bdee4df34e3020b189364788be2c472224b32 --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f76a1a636287da5a1d8b96eb315efd7405b66ee1ef307c8ea5283e2c06ecf8d +size 51081 diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6477b79245dfb0bd34bbcf9812174dfad5d8f5f --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4831f6de98d9de4a97bdb1086bdf2d1750642a402a0cce9e91a379946323a92 +size 57450 diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9500ce66ae48a5fbd801e3b3707dc47e4e32e717 --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2a3d1fd3423143555977117a6655563b13675b3f8651345d34c6e17b0ee0943 +size 52405 diff --git a/marked/Q/T-REC-Q.4066-202009-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a95f4bbff509c812b45a1b8f2fa123fca0e6547b --- /dev/null +++ b/marked/Q/T-REC-Q.4066-202009-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aee2af01db85043589e48d6447c4624bcacf9328beacd1c414e298ec61eb2efd +size 51450 diff --git a/marked/Q/T-REC-Q.4075-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..985ce4f109b67d2faa0bfb4095195a8c8daeb31f --- /dev/null +++ b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df1fd24c75458ea11a4825ba5d66828f9be3dd9f00ac276be6c1bcb17fce8e9f +size 7269 diff --git a/marked/Q/T-REC-Q.4075-202406-I_PDF-E/35a7554182eb055209552843f341a1ae_img.jpg b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/35a7554182eb055209552843f341a1ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e18c398b225a5fac0087f698885cb24604916dd --- /dev/null +++ b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/35a7554182eb055209552843f341a1ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf7820a7a1b8103f702ccba5fdcb8f11fa171ecb24f6ef4582e0f2d5d16222b6 +size 56660 diff --git a/marked/Q/T-REC-Q.4075-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..513585b27adbb6fd2a1444c06dcbb3ef43181150 --- /dev/null +++ b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c733760521903f7778769322f056ccb7a7e0d7a1a4554e555f5422031c29f34 +size 150595 diff --git a/marked/Q/T-REC-Q.4075-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ecc129175f17f2e2b886c8bbdfbba477bd6a2ef6 --- /dev/null +++ b/marked/Q/T-REC-Q.4075-202406-I_PDF-E/raw.md @@ -0,0 +1,483 @@ + + +# Recommendation**ITU-T Q.4075 (06/2024)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Testing specifications – Testing specifications for IMT-2020 and IoT + +--- + +## **Test specifications for remote testing of Internet of things using probes** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circular emblem with a globe and signal waves. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +## Switching and signalling, and associated measurements and tests + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| Testing specifications for next generation networks | Q.3900-Q.3999 | +| Testing specifications for SIP-IMS | Q.4000-Q.4039 | +| Testing specifications for Cloud computing | Q.4040-Q.4059 | +| Testing specifications for IMT-2020 and IoT | Q.4060-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T Q.4075 + +## Test specifications for remote testing of Internet of things using probes + +## Summary + +The Internet of things (IoT), defined in Recommendation ITU-T Y.2060, currently plays an important role for telecommunication and information technologies. It is one of the global infrastructures for the information society, delivering advanced services by interconnecting things based on existing and evolving interoperable information and communication technologies. + +Currently, methods of remote testing of network equipment are actively used. During testing, special attention is paid to the quality of service parameters (delays, losses, jitter, bandwidth etc.); however, in relation to the specifics of the IoT devices, it is most appropriate to control the parameters for the optimum functioning of end devices. IoT devices, as an example, have battery power and monitoring of their operation parameters will allow timely adjustments to the algorithms of their functioning in order to extend the battery life. + +The use of probes will allow the addressing of important parameters of the IoT devices and conducting remote testing of various parameters of the IoT devices, such as: power consumption, memory and processor operation and open interfaces. The description of the test specifications for remote testing using probes will allow the development of a unified approach for conducting appropriate testing of IoT devices. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4075 | 2024-06-29 | 11 | 11.1002/1000/15962 | + +## Keywords + +Internet of things, probe, remote testing, test specification. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Architecture of system for remote testing of IoT devices using probes..... | 2 | +| 6.1 IoT test server ..... | 3 | +| 7 Remote testing of IoT device using probes ..... | 5 | +| 7.1 Probes for IoT device detection and classification..... | 5 | +| 7.2 Methodology for polling IoT devices using probes ..... | 6 | +| 8 Collected data analysis module ..... | 8 | +| 8.1 Static characteristics and dynamic characteristics..... | 8 | +| 8.2 Set of parameters for monitoring Internet of things devices collected by probes ..... | 9 | + + + +# Recommendation ITU-T Q.4075 + +## Test specifications for remote testing of Internet of things using probes + +# 1 Scope + +This Recommendation describes test specifications for remote testing of Internet of things (IoT) devices using the probes. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T Q.3913] Recommendation ITU-T Q.3913 (2104), *Set of parameters for monitoring Internet of things devices*. + +[ITU-T Y.4000] Recommendation ITU-T Y.4000 (2012), *Overview of Internet of things*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 device** [ITU-T Y.4000]: With regard to the Internet of things, this is a piece of equipment with the mandatory capabilities of communication and the optional capabilities of sensing, actuation, data capture, data storage and data processing. + +**3.1.2 Internet of things (IoT)** [ITU-T Y.4000]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies. + +NOTE 1 – Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled. + +NOTE 2 – From a broader perspective, the IoT can be perceived as a vision with technological and societal implications. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +AMQP Advanced Message Queuing Protocol + +API Application Programming Interface + +CoAP Constrained Application Protocol + +DBMS Database Management System + +| | | +|------|--------------------------------------------| +| DDS | Data Distribution Service | +| HTTP | Hypertext Transfer Protocol | +| IANA | Internet Assigned Numbers Authority | +| IMEI | International Mobile Equipment Identity | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| MAC | Media Access Control | +| MQTT | Message Queue Telemetry Transport | +| OS | Operating System | +| QoS | Quality of Service | +| RAM | Random Access Memory | +| RTOS | Real Time Operating System | +| TCP | Transmission Control Protocol | +| XMPP | extensible Messaging and Presence Protocol | + +## 5 Conventions + +None. + +# 6 Architecture of system for remote testing of IoT devices using probes + +![Figure 1 – Architecture of a system for remote testing of IoT devices using probes. The diagram shows two types of IoT devices (Without OS and With OS) connected to an IoT gateway. The 'Without OS' devices use protocols like Wi-fi, BLE, LoRa, etc. The 'With OS' devices use MQTT, COAP, HTTP, AMQP and are connected to a Probe. The IoT gateway connects to the Internet. The Internet connects to an IoT cloud server and an IoT test server. The IoT test server is connected to a Probe and a Web interface. The Web interface is connected to a User.](35a7554182eb055209552843f341a1ae_img.jpg) + +``` + +graph LR + subgraph IoT_Devices + direction TB + D1[IoT devices under test +(Without OS)] + D2[IoT devices under test +(With OS)] + P1[Probe] + D2 <--> P1 + end + D1 -- "Wi-fi, BLE, LoRa, Sigfox, LTE, +6Low PAN, ZWave, ZigBee" --> IG[IoT gateway] + D2 -- "MQTT, COAP, HTTP, AMQP" --> IG + IG --> I((Internet)) + I --> ICS((IoT cloud server)) + I --> ITS[IoT test server] + subgraph ITS_Container [ ] + direction TB + ITS[IoT test server] + P2[Probe] + ITS <--> P2 + end + ITS_Container --> WI[Web interface] + WI --> U((User)) + style ITS_Container fill:none,stroke:none + +``` + +Figure 1 – Architecture of a system for remote testing of IoT devices using probes. The diagram shows two types of IoT devices (Without OS and With OS) connected to an IoT gateway. The 'Without OS' devices use protocols like Wi-fi, BLE, LoRa, etc. The 'With OS' devices use MQTT, COAP, HTTP, AMQP and are connected to a Probe. The IoT gateway connects to the Internet. The Internet connects to an IoT cloud server and an IoT test server. The IoT test server is connected to a Probe and a Web interface. The Web interface is connected to a User. + +**Figure 1 – Architecture of a system for remote testing of IoT devices using probes** + +Depending on the particular features of the network construction and the tasks, all the elements and subsystems indicated in this clause may be used jointly or separately in different combinations, including in a single hardware system. + +A system for the remote testing of IoT devices has user client-cloud server architecture and comprises the following elements: + +**Probe** – A test tool which uses probing packets to collect measurements of various parameters of the IoT device under test. It can either be a hardware and/or software. + +## 6.1 IoT test server + +The block diagram of the service core is shown in Figure 2 and includes a cloud server and a database management system. + +Information transmitted via MQTT, CoAP, XMPP, DDS, AMQP, HTTP data transfer protocols can be in any format (platform independent). As a client of the software platform, it is assumed to use a PC or a smartphone with a browser (Chrome, Internet Explorer, Firefox). + +The key functions of the software platform service core are: + +- Registration, modification and removal of user devices in the system. +- Ensuring interaction with user devices through data transfer protocols MQTT, CoAP, XMPP, DDS, AMQP and HTTP. +- Automated collection and processing of data coming from user devices with various protocols and interfaces. +- Providing system users with a template for generating recommended signatures for the data transfer protocols message queue telemetry transport (MQTT), constrained application protocol (CoAP), extensible messaging and presence protocol (XMPP), data distribution service (DDS), advanced message queuing protocol (AMQP) and hypertext transfer protocol (HTTP). +- Creation, storage and modification of user signatures and use cases. + +![Structural diagram of an IoT test server showing the architecture of the service core of the software platform. The diagram is divided into three main sections: IoT devices, the Internet, and the Cloud platform. IoT devices (DDS, HTTP, XMPP, MQTT, AMQP) connect to the Internet. The Internet connects to the Cloud platform. The Cloud platform contains the Software platform service core, which includes helpers for each device type, system services, a PostgreSQL database, and an internal information system. An API interface is also shown within the cloud platform.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the structural architecture of an IoT test server. At the top, five IoT devices (XMPP device, MQTT device, HTTP device, DDS device, and AMQP device) are shown. The XMPP device connects to an XMPP server, which in turn connects to the Internet. The MQTT device connects to an MQTT broker, which connects to the Internet. The HTTP device connects directly to the Internet. The DDS device connects directly to the Internet. The AMQP device connects to an AMQP broker, which connects to the Internet. The Internet is represented by a central dashed circle. Below the Internet, the Cloud platform is shown as a large dashed rectangle. Inside the Cloud platform, the Software platform service core is a dashed rectangle containing five helpers (DDS helper, XMPP helper, AMQP helper, HTTP helper, and MQTT helper) and a System services block. The System services block contains five horizontal boxes: Service for registering and modifying IoT devices, Automatic device data saving service, Service for generating (autocomplete) system signature templates, Service for sending custom signatures, and Service for creating, modifying, and storing use cases. Below the System services block is a PostgreSQL box, which is connected to an Internal information system box. An API interface box is also present within the Software platform service core, connected to the System services block. The entire Cloud platform section is labeled 'Cloud platform' at the bottom. A small text 'Q.4075(24)' is located at the bottom right of the diagram. + +Structural diagram of an IoT test server showing the architecture of the service core of the software platform. The diagram is divided into three main sections: IoT devices, the Internet, and the Cloud platform. IoT devices (DDS, HTTP, XMPP, MQTT, AMQP) connect to the Internet. The Internet connects to the Cloud platform. The Cloud platform contains the Software platform service core, which includes helpers for each device type, system services, a PostgreSQL database, and an internal information system. An API interface is also shown within the cloud platform. + +**Figure 2 – Structural diagram of an IoT test server** + +The block diagram reflects the architecture of the service core of the software platform, consisting of: + +- IoT test server. +- Database management systems – a cluster of an object-relational database management system to improve the fault tolerance of the platform. +- Software platform service cores: + +- DDS helper – implements the publisher-subscriber pattern of the DDS machine-to-machine communication protocol, the helper can simultaneously act as a subscriber and publisher. Also provides customization of user-selected QoS policy. +- XMPP helper – authorizes in a third-party XMPP server selected by the user, creates and/or joins private chats and group rooms, sends invitations to initiate chats to other users and IoT devices. +- AMQP helper – performs queuing and dequeuing, message sending and receiving, and connection and authorization, through standard authentication or X.509 certificate peer verification, in a third-party or custom AMQP broker. +- HTTP helper – listens on the standard HTTP (80) and HTTPS (443) application-layer protocol ports. Implements the identification of users' IoT devices through tokens and basic authorization. If there are no authentication fields, it is required to transfer data by device identifier number (if this method is specified as allowed). +- MQTT helper – Performs connection and authorization in a third party or custom MQTT broker. Implements a mechanism for creating modifications and deleting subscriptions. It also allows the software platform and the user to act as a publisher. +- System Services – is a layer that provides interaction between the external interfaces of the software platform and the database management system (DBMS) cluster. + +# 7 Remote testing of IoT device using probes + +## 7.1 Probes for IoT device detection and classification + +IoT device detection is one of the most important preliminary stages. Scanning open network ports can be used for the detection of IoT devices. + +For the purpose of detection and classification of IoT devices, probes are generally categorized as in clauses 7.1.1–7.1.3. + +### 7.1.1 Port scanning probe + +It finds active IoT devices in the network by scanning ports on specified IP addresses. The port scanning probes scan common ports using TCP connect scan and detects open network ports on devices which respond to port scan query. The probe results different combination of open ports for each device. + +### 7.1.2 Classifier probe + +After the port scanning probe, the classifier probe may be initiated. It classifies the IoT device based on open network ports number and the application data transfer protocol used on this network port. A hierarchical approach with optimal probing may be used, by which devices may be classified correctly. + +Most of the IoT devices are manufactured for specific (and limited) tasks and they expose different sets of protocols operating on port numbers specific to the device. For example, CoAP, MQTT, HTTP, etc. The non-profit organization Internet Assigned Numbers Authority (hereinafter IANA) determines the fixed port numbers which are used for certain purposes and establishes a correspondence between them, and the application-layer protocols applied. By comparing the list of detected network ports on the scanned device and the IANA database, the application data transfer protocol used on this network port can be determined. + +Other ports not listed in the IANA database that use TCP protocol for data transfer typically send a response to any request. The response received from the device allows determining of which application-layer protocol the port is using. + +### 7.1.3 Identification probe + +Depending on the classification of IoT device, the identification probe may be initiated. It determines the type of IoT devices by analysing the information contained in the data field of the received packets. The identification probe will also gather additional information about the device, like the applications running it, and additional attributes, such as memory, network cards and drivers. + +## 7.2 Methodology for polling IoT devices using probes + +### 7.2.1 IoT devices with OS + +After the previous stage IoT device detection and classification, the list of IoT devices and their parameters is fixed in the system: information about the device and a set of protocols used. + +Based on the set of protocols used, a request queue is formed to periodically poll the probe of the IoT device. An association is formed between the request and the value received. + +Values are passed as a byte string. The use of byte strings is due to a decrease in the load on both the IoT device and the communication network. + +Table 7-1 describes the server request from the probe. + +**Table 7-1 – Example of structure for the server request from the probe** + +| Start sequence | Length | Device ID | +|----------------|-----------|--------------| +| 4 bytes | 2 bytes | 8 bytes | +| Message ID | Timestamp | Message type | +| 1 byte | 8 bytes | 1 byte | +| Payload | | End sequence | +| [***] | | 4 bytes | + +*Start and end sequence* – a fixed set of bytes indicating the beginning and end of the message. + +*Length* – the number of bytes occupied by all fields, except for the payload length, start and end sequence fields. + +*Device ID* – a unique value assigned by the information collection platform for this device. + +*Message ID* – message number. Changes cyclically from 0 to 255, to avoid re-counting messages and skipping replies. + +*Timestamp* – the time of relevance of the transmitted data. + +*Message type* is a value associated in the system with event types to understand the level of importance of the message. + +*Payload* – data directly transmitted from the device. + +Probes are polled from the server at certain time intervals. If there is no response from the probe, a record is generated and a new attempt to establish a connection is placed in the request queue. + +The system has a single query execution queue between the server and the probe to prevent simultaneous polling of all probes and creating a heavy load on the communication network. + +Reference parameters for comparison are a set of primary data obtained from the probe or values set for a specific type of IoT device. + +After collection, the data is recorded in a single event format, which records the type of event, source, time and transmitted data. + +Depending on the type of message, it either immediately generates an alert for the administrator, or waits in line to write to the database. + +Thus, all parameters of IoT devices in the communication network are constantly monitored. However, each IoT device with a probe can report a sudden state change. + +The division of all records into events allows you to analyse both changes in a specific IoT device and changes in the entire communication network both in time and in any other parameters. + +For example, if processor utilization increases or open software ports appear. + +To monitor the status of IoT devices using a microprocessor, it is possible to implement two types: by polling or automatic sending, as well as a combined option, when the IoT device sends the basic set of parameters on its own, and the extended set is issued only upon request. + +### **7.2.2 IoT devices without OS (only firmware)** + +#### **IoT devices working with server directly** + +To track the status of IoT devices using a microprocessor, it is possible to implement either the ability of the IoT device to respond to requests with the transfer of the necessary parameters, or to send data independently at a certain time interval. The choice of implementation depends on the functions of the IoT device (either it is constantly connected to the network, or it is in sleep mode and wakes up only during the measurement and data transfer). + +It is assumed that only devices using the operating system for microcontrollers (for example, RTOS) will be able to use the tracking functionality, in other cases, the implementation of support falls entirely on the shoulders of hardware software developers. + +#### **IoT devices working with server via broker** + +IoT devices can use protocols such as MQTT and AMQP to communicate to the network a through broker server which is based on the publish/subscribe messaging method. The broker is responsible for receiving network connections from the client IoT devices and handling the client's requests of subscribe/unsubscribe and publish to the topic, as well as forwarding the messages published by the publisher client IoT device on a topic to other subscribers IoT devices of that topic. + +To track the status of IoT devices, a parent topic, i.e., Testprobe may be created to broker from remote test/user client by publishing to topic, and other IoT devices connected can subscribe to the parent topic. The parent topic may contain the message for subscriber IoT devices to transfer the necessary parameters for subscriber IoT devices. The subscriber IoT device of the parent topic may also publish another topic i.e., Testprobe/IoT-1 to which the test/user client may subscribe. + +For obtaining parameters from IoT devices, a test/user client sends message/command for publishing the topic, i.e., Testprobe, to the broker through the network which sends message/command to subscriber IoT devices. In response, IoT devices will be publishing parameters data to the broker for the topic, i.e., Testprobe/IoT-1, and the broker sends the parameters data to test/user client. The data may be recorded in the server for analysis. For IoT devices with resource constraints (low power, low CPU/memory), only critical data may be requested by remote test/user clients via the broker. As such devices may also operate in a wake-on-request mode; this critical data may be piggybacked with the response message to the wake-on-request message. If the IoT device loses its connection with the broker, the "last seen" status of the IoT device, as recorded by the broker may be sent to the remote test/user client upon request. + +### 7.2.3 Proprietary IoT devices + +To track the state of IoT devices, the hardware, software of which cannot be changed, a support module is created in the core of the software platform. Such modules for interacting with the IoT device implement API calls available for the IoT device, provided by the manufacturer, or it is possible to parse the configuration web page, and format the data in the required format to write to the service database. + +# 8 Collected data analysis module + +## 8.1 Static characteristics and dynamic characteristics + +All data transmitted from devices can be divided into two categories: static characteristics and dynamic characteristics. + +For ESP8266 and ESP32 devices, the following categories can be obtained. + +The static characteristics include: + +- MAC address of the device; +- Device IP address; +- Software version; +- Device name. + +Dynamic characteristics include: + +- Used RAM; +- Temperature. + +In the case of devices with the Linux operating system (for example, devices of the Raspberry Pi family), a greater number of device characteristics, both static and dynamic, can be obtained. + +The static characteristic include: + +- MAC address of the device. +- Device IP address. +- Software version. +- Device name. +- Number of processor cores. +- The amount of disk space for each logical partition. In connection with the virtual fragmentation of the disk into parts, which are called partitions. +- Network interfaces, etc. + +Dynamic characteristics include: + +- Used RAM. +- Graphics card temperature. +- The number of transmitted network packets. +- Number of network packets received. +- The amount of disk space for each logical partition. In connection with the virtual fragmentation of the disk into parts, which are called partitions. +- The amount of used disk space for each logical partition. +- Load per processor core, etc. + +Static data-processing does not require additional software implementation. Working with such data involves tracking changes in their state and transferring information about changes in static characteristics to an administrator or user. These changes can be an important indicator in case of emergency situations with the device, up to access to the device by third parties and detection of the fact of an attack on the device. + +Processing dynamic data requires additional software implementation. Working with such data involves tracking changes in these indicators over time. As a result of the analysis, tables with processed data are formed. Based on this data, graphs are subsequently dynamically drawn, which clearly demonstrate changes in parameters over time. In addition, some parameters are subjected to additional mathematical processing in order to calculate the resulting value of the parameter. For example, the percentage of successfully sent and received network packets. Thus, the data analysis module allows you to sort and process the data received in the monitoring module into special tables, each of which is responsible for a specific characteristic (parameter). + +Also, the collected data analysis module allows you to assess the state of IoT devices by analysing the frequency of changes in transmitted information. If the response from the device was not received within the expected period of time, actions are taken similar to those in case of a change in the static characteristics of devices. + +## 8.2 Set of parameters for monitoring Internet of things devices collected by probes + +The set of parameters for monitoring IoT devices can be different and depends on the characteristics of the IoT device itself. IoT devices can be classified with and without an operating system, with a microprocessor and a microcontroller, etc. + +To systematize, the set of parameters for monitoring of IoT devices is present at [ITU-T Q.3913]. + +Below are the main set of parameters for monitoring IoT devices collected by probes. + +- 1) *Traffic parameters*: Traffic measurement can be applied in usage-based accounting, traffic profiling, traffic engineering, attack/intrusion detection and QoS monitoring. For example, flow-based traffic measurement can be used to help determine device performance or behaviour through the analysis of the measurement parameter values. + - General; + - Flow-based IP traffic measurements. +- 2) *Anomalous behaviour and events parameters*: Monitoring anomalous behaviour or events is an important aspect of security threat detection. A baseline of normal behaviour must be identified over a period of time. Once certain parameters have been defined as normal, any departure from one or more of these parameters is flagged as anomalous. Many anomaly detection algorithms have been proposed that differ in the information used for analysis and in the techniques that are employed to detect deviations from normal behaviour. Examples of anomaly detection methods include statistical methods, rule based methods, profiling methods and model-based approaches. + - Abnormal service activity; + - Mismatch between IMEI/MEID and IMSI; + - Loss of connectivity; + - Change of location; + - Unusual log-on activities. +- 3) *Performance parameters* + - Delay; + - Packet loss rate; + +- Throughput; +- Link utilization; +- Availability. + +4) *Battery parameters.* A device may use a battery as a power supply when the device is mobile, in open country or when the mains power supply is out of service. Some battery parameters should be monitored to indicate the battery state, longevity and capacity so that the operator is informed of the current or future state of the device. + +- Temperature; +- Voltage; +- Discharge current; +- Charging current; +- Remaining capacity of the battery. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71052002c24106985b322c85a7ee855364aa3e64 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7cf598097aae03d433cd597c9cc123e95c65d28c7d162cca06146d1253a2594 +size 62005 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/3376375fe7236a570fd0ee9448d9c4ee_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/3376375fe7236a570fd0ee9448d9c4ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bfbd4567e6d1137e025bc62a39986498b37aee1 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/3376375fe7236a570fd0ee9448d9c4ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5538f50b1209dcc1bd830526ef865caa412df794c6ba54f1faa207db787a7229 +size 48141 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73a5505c3095a1c0785b5be2c18844c63e3003a6 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df3cd41321ed7f1aa9d6dac125788123afa2d84f4d2a6977637f6e9f134fd361 +size 4057 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa586465937646a3a54567c83c85aea0dd872eff --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b3b297e0eca5a45e74f90e2a67fb2a674a76233c1b5a22c700aa52fac27afb1 +size 104399 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0048c3adb1f18831814d1c6678490431cb4aca6a --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:142b3fa1d87798e7402fc8fe450789c8f14f74f572613139ad14bb18b4ad2865 +size 69420 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12c2eacd130abbc00c299c0c7fe062a761c09fdb --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a990abf51db3827bbbf2bed2f37f2c67e350818b753bb414f781078e49bafd41 +size 60748 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3437a70d2b2e4b7b15cacaf1e4660f44d43a686 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17c2c011359c3ac545322966480485c85f50c2b5aa4c4fb683547bf5028a1768 +size 70498 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58bec3d9642db840bf6ddc9735c6d14a1b937a07 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8c5c9ef6493c4f886f983fdaddbb30fc8f2c990fc993476a8ad78f73e20dd89 +size 58986 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b738d8245d547996f00d014ec69725453bf0541f --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5691948497639219976abf03b85094f207033ef66e5263ad72758b9c65247898 +size 3989 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d82fc41645ef552e457425d5508e9a60a86a929a --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82066e79cf43cf3add6b4d74e4237a44f7cc14eb30693d7546fa15565e10ed63 +size 99996 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f99f8972bf7dfb021ab11d11f4641aae3b8bb9 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2216dfe236cacae5a4b5872266a442a93ebdf81ad1bcd391169577048dcc4b09 +size 54124 diff --git a/marked/Q/T-REC-Q.4100-202009-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fb8ebbaf8e517a21a4012abb7822a6b2ca75fb2 --- /dev/null +++ b/marked/Q/T-REC-Q.4100-202009-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f98b460e0f47412b676f5960c5de31fe9d0d8d97a99bd15cc2ee4c33bf4d0582 +size 85710 diff --git a/marked/Q/T-REC-Q.4141-202312-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4141-202312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..851a17f144006bded0c1afc06f9eb9d112a1dac5 --- /dev/null +++ b/marked/Q/T-REC-Q.4141-202312-I_PDF-E/raw.md @@ -0,0 +1,713 @@ + + +# Recommendation**ITU-T Q.4141 (12/2023)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Protocols and signalling for computing power networks + +--- + +### **Requirements and signalling of intelligence control for the border network gateway in computing power networks** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +### **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.4141 + +# Requirements and signalling of intelligence control for the border network gateway in computing power networks + +## Summary + +Recommendation ITU-T Q.4141 provides a network solution to dynamically and flexibly schedule computing tasks at the border network gateway (BNG) based on real-time computing resource performance, network performance, cost and other multi-dimensional factors related to business needs, thereby improving resource utilization, network utilization efficiency, and business user experience. + +This Recommendation aims to study the requirements and signalling of intelligence control for the border network gateway in a computing power network (CPN). + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4141 | 2023-12-14 | 11 | 11.1002/1000/15724 | + +## Keywords + +Computing power network, CPN gateway, intelligence control. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Requirements ..... | 2 | +| 6.1 Overview ..... | 2 | +| 6.2 General requirements..... | 3 | +| 6.3 Specific requirements for the CPN gateway ..... | 3 | +| 7 Architecture of intelligence control for the CPN gateway ..... | 5 | +| 7.1 CPN gateway control plane ..... | 6 | +| 7.2 CPN gateway user plane..... | 6 | +| 7.3 CPN orchestration and management ..... | 7 | +| 7.4 CPN service layer ..... | 7 | +| 8 Signalling procedures of intelligence control for the CPN gateway ..... | 7 | +| 8.1 Information interaction for intelligence control for the CPN gateway..... | 7 | +| 8.2 Signalling procedures for intelligence control for the CPN gateway ..... | 9 | +| 9 Security considerations ..... | 13 | +| Appendix I – Use case descriptions ..... | 15 | +| I.1 Edge computing interconnect scenario ..... | 15 | +| I.2 Data centre interconnect scenario ..... | 16 | +| Appendix II – Deployment of the CPN gateway ..... | 18 | +| II.1 CPN gateway hybrid networking ..... | 18 | +| II.2 CPN gateway distributed networking..... | 18 | + + + +# Recommendation ITU-T Q.4141 + +# Requirements and signalling of intelligence control for the border network gateway in computing power networks + +# 1 Scope + +This Recommendation focus on the requirements architecture and signalling procedure of intelligence control for the border network gateway (BNG) devices in a computing power network (CPN). This Recommendation provides a network solution to dynamically and flexibly schedule computing tasks at the border network gateway based on real-time computing resource performance, network performance, cost and other multi-dimensional factors related to business needs, thereby improving resource utilization, network utilization efficiency, and user experience. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.3719] Recommendation ITU-T Q.3719 (2019), *Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG)*. +- [ITU-T Q.4140] Recommendation ITU-T Q.4140 (2023), *Signalling requirements for service deployment in computing power networks*. +- [ITU-T Y.2501] Recommendation ITU-T Y.2501 (2021), *Computing power network – Framework and architecture*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 computing power network (CPN) gateway:** A border gateway with the functions of service perception, computing power perception, and computing power routing, etc., that can dynamically select forwarding paths and service nodes based on the calculation of service requirements, computing power information and network information, to realize the global optimization of computing power and network resources. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------| +| AI | Artificial Intelligence | +| ASIC | Application Specific Integrated Circuit | + +| | | +|-----------|-----------------------------------------------| +| BGP | Border Gateway Protocol | +| BNG | Border Network Gateway | +| CPN | Computing Power Network | +| CPN-GW | Computing Power Network Gateway | +| CPN-GW-CP | Computing Power Network Gateway Control Plane | +| CPN-GW-UP | Computing Power Network Gateway User Plane | +| CPU | Central Processing Unit | +| DC | Data Centre | +| EVPN | Ethernet Virtual Private Network | +| GPU | Graphics Processing Unit | +| IGP | Interior Gateway Protocol | +| IoT | Internet of Things | +| IP | Internet Protocol | +| MPLS | Multiple Protocol Label Switch | +| NP | Network Process | +| NPU | Neural network Processing Unit | +| OAM | Operation Administration and Maintenance | +| PE | Provider Edge | +| RESTful | Representational State Transfer | +| SDN | Software-Defined Networking | +| SR | Segment Routing | +| SRv6 | Segment Routing Internet Protocol Version 6 | +| SSL | Secure Socket Layer | +| VPN | Virtual Private Network | +| VR/AR | Virtual Reality/Augmented Reality | +| VxLAN | Virtual extensible Local Area Network | +| WAN | Wide Area Network | + +# 5 Conventions + +None. + +# 6 Requirements + +## 6.1 Overview + +In a computing power network (CPN), the computing power network gateway (CPN-GW) is able to collect network resource and status information and computing power information, and so conduct the scheduling policy of computing power intelligently. The CPN gateway perceives computing resource information and network resource information, notifies the current computing resource status as routing information to the network, and routes computing tasks to appropriate computing + +nodes to achieve optimal overall system and user experience. Computing power awareness and computing power routing are the two core capabilities of the CPN gateway. + +CPN gateway awareness is a comprehensive perception of the performance of computing resources, real-time load, network status, and business requirements. It mainly needs to know how many computing resources are in the network and what kinds of computing power are required by users. Computing power awareness includes computing resource perception, network resource perception, and business demand perception. Computing power routing is the process of integrating and distributing network and computing resource information, and achieving resource information announcement and information sharing across the entire network. + +In a CPN, the intelligence control functions for computing power scheduling are deployed in the network control plane. As described in [ITU-T Q.3719], the architecture of the BNG is separated into a control plane and a data plane. It is therefore compatible to extend the scope of functions in the BNG control plane for intelligence control of computing power scheduling in CPN. + +However, in spite of the advantages and compatibility of the BNG for scheduling computing power it remains a challenge to schedule computing power at the CPN gateway in a dynamical and flexible way considering both computing resources and network performances. + +This clause focuses on the general requirements and specific requirements for the CPN gateway. + +## **6.2 General requirements** + +### **6.2.1 Bandwidth requirement** + +It is required to support reserving the bandwidth resources in advance to transmit massive data when scheduling the computing power for those kinds of services which require a lot of bandwidth resources, such as virtual reality/augmented reality (VR/AR). + +### **6.2.2 Latency requirement** + +It is required to support lower and deterministic end-to-end latency when scheduling the computing power for services which are sensitive to latency, such as tactile Internet. + +### **6.2.3 Jitter requirement** + +It is required to support the lower and deterministic jitter of network latency when scheduling the computing power for those kinds of services which are sensitive to the jitter of network latency, such as telemedicine so that the jitter of network latency should be restricted within a certain range. + +### **6.2.4 Packet loss rate requirement** + +It is required to support lower packet loss rate when scheduling the computing power for those kinds of services, such as smart factory, which are sensitive to packet loss rate. + +### **6.2.5 Reliability requirement** + +It is required to support the reliability of communication when scheduling the computing powers for that kinds of services which require high reliability of communication, such as self-driving vehicles. + +### **6.2.6 Security requirement** + +It is required to support higher security when scheduling the computing powers for that kinds of services which have particular requirements for security, such as smart home which requires the user's data to be processed locally. + +## **6.3 Specific requirements for the CPN gateway** + +Besides the general functions of a traditional border gateway, a CPN gateway also needs to perceive computing resource information and network resource information, distribute the current computing + +resource status and network resource status to the network along with routing information, and route computing tasks to the appropriate computing nodes to achieve overall system optimization and user experience optimization. To this end, the CPN gateway needs to implement specific functions, such as computing resource awareness, network resource status awareness, service requirements awareness, computing power routing capability, computing power resource information distribution, and computing power routing table generation, etc. + +### **6.3.1 Computing resource awareness** + +Computing resource awareness is the perception of computing resources of the computing power resource pools, including their performance, real-time load and other related information, which usually includes the IP address, storage capacity, etc. For example, cloud resource pools are usually centrally managed by the cloud management platforms. The CPN gateway can interact with the cloud management platform through interfaces such as representational state transfer (RESTful) APIs to obtain relevant computing power resource information about the cloud resource pools. + +### **6.3.2 Network resource status awareness** + +The perception of network resource status information usually includes bandwidth, delay, jitter, packet loss rate, etc. Taking network delay as an example, since computing power resource pools are in geographically distributed locations, the network path from the user to the computing power resource pool will also change according to the network congestion status. Therefore, it is necessary to detect the network delay information between the user and each computing power resource pool. + +### **6.3.3 Service requirements awareness** + +The CPN gateway at the user entrance receives service requests and perceives service requirements, including network requirements (such as delay, jitter, etc.) and computing power resource requirements (such as computing power type, computing power demand parameters, etc.), based on computing power measurement standards and matches the available computing power to a specific algorithm. It not only accurately matches the service requirements of specific applications, but also dynamically and real-time schedules the computing power network to optimize the computing resources and the network resources. + +### **6.3.4 Computing power routing capability** + +Computing power routing introduces computing power resource information into the routing domain, and dynamically selects the "forwarding path + destination service node" that meets the service requirements by perceiving the user's service requirements, computing power resources, and network resources status, and then schedules the service along the designated path to service nodes to achieve global optimization of computing power resources and network resources. + +### **6.3.5 Computing power resource information distribution** + +The CPN gateway will advertise computing power resource information to the adjacent CPN gateways, computing power routing nodes or the controller. The information notified includes computing power resource information such as processor's type, overload and memories, as well as network-related indicators in the computing power resource pools such as delay and jitter, etc. + +### **6.3.6 Computing resource routing table generation** + +After obtaining the distribution status of computing power resource nodes, the CPN gateway will generate a computing power routing table within the domain. In addition to the network parameters (such as cost) maintained in the IP routing table, the computing power routing table also contains computing power resource information, thereby building a "network + computing" global routing table. + +# 7 Architecture of intelligence control for the CPN gateway + +For the purpose of intelligence control for the CPN gateway, the architecture is designed to meet these requirements: + +- The CPN gateway should collect the information of computing power resources and network resources in the central cloud and the edge cloud. The computing power resources information consists of central processing unit (CPU utilization), memory utilization, storage utilization, etc. and the network resources information consists of bandwidth utilization, latency, etc. +- The design of architecture should consider supporting computing power cross-domain route information. The CPN inter-domain route information should be constructed on all intra-domain route information maintained by the control plane of the CPN gateway. Additionally, the inter-domain and intra-domain computing task scheduling policies should be made based on the corresponding resources information and route information. +- The CPN gateway should interact with components contained in the CPN service layer to accept the service demands and to report the computing power resources information and network resources information. +- The CPN gateway should be able to allocate the resources and schedule the network connection between the consumers and the providers. + +The architecture of the CPN gateway is shown in Figure 7-1. + +![Figure 7-1: Architecture of intelligence control for the CPN gateway. The diagram shows a vertical stack of layers. On the left is a vertical box labeled 'CPN orchestration and management'. To its right is a large box containing three stacked layers. The top layer is 'CPN service layer'. The middle layer is 'CPN-GW control plane', which contains a 2x4 grid of functions: 'Resource information awareness and collection', 'Computing and network connection scheduling', 'Resource allocation', 'UP management function', 'Traffic engineering', and 'QoS control function'. The bottom layer is 'CPN-GW user plane', which contains three boxes labeled 'X86', 'Asic', and 'NP'. Double-headed arrows connect the 'CPN orchestration and management' box to each of the three layers. Vertical double-headed arrows also connect the 'CPN service layer' to the 'CPN-GW control plane', and the 'CPN-GW control plane' to the 'CPN-GW user plane'. A small label 'Q.4141(23)' is at the bottom right of the diagram.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Q.4141(23) + +Figure 7-1: Architecture of intelligence control for the CPN gateway. The diagram shows a vertical stack of layers. On the left is a vertical box labeled 'CPN orchestration and management'. To its right is a large box containing three stacked layers. The top layer is 'CPN service layer'. The middle layer is 'CPN-GW control plane', which contains a 2x4 grid of functions: 'Resource information awareness and collection', 'Computing and network connection scheduling', 'Resource allocation', 'UP management function', 'Traffic engineering', and 'QoS control function'. The bottom layer is 'CPN-GW user plane', which contains three boxes labeled 'X86', 'Asic', and 'NP'. Double-headed arrows connect the 'CPN orchestration and management' box to each of the three layers. Vertical double-headed arrows also connect the 'CPN service layer' to the 'CPN-GW control plane', and the 'CPN-GW control plane' to the 'CPN-GW user plane'. A small label 'Q.4141(23)' is at the bottom right of the diagram. + +**Figure 7-1 – Architecture of intelligence control for the CPN gateway** + +The CPN gateway should include the CPN gateway control plane and user plane, as well as interact with the CPN orchestration and management, and the components of the CPN service layer to realize the intelligent control for the CPN gateway. The intelligent control of the CPN gateway mainly realizes the routing and scheduling of computing power resources, while combining with the orchestration and management of the CPN gateway to achieve controllable, manageable, and schedulable computing power resources and services in the network. Specifically, the CPN orchestration and management mainly provides a unified management system for the CPN and computing power, including computing power measurement and modelling, computing power registration, and computing power operation administration and maintenance (OAM), etc. The CPN gateway control plane is mainly based on perception of network resource and computing power + +resource information for integrated scheduling of the CPN, also including functions such as computing power perception and notification, and computing power routing control, etc. The CPN gateway user plane is mainly based on the computing power routing table to transmit users' data. It further includes functions such as computing power application perception and computing power monitoring, etc. + +## **7.1 CPN gateway control plane** + +The CPN gateway control plane introduces computing power information into the routing domain for computing power perceiving, routing control and scheduling, which mainly includes the computing power perception and the business scheduling functions. The computing power perception further includes computing power discovery and computing power notification functions, mainly used to collect computing power resource and network resource information. The business scheduling is mainly based on computing power and network status information to select appropriate service nodes to process user services. + +Resource information awareness and collection is a function that gathers the computing resources and network resources in the connected computing power resource pool. The resource information table is maintained by this function. Moreover, the resource information table will be exchanged among the adjacent CPN gateways to assist the computing power scheduling. Also the resource information table will be sent in advance to the CPN service layer and CPN orchestration and management component for scheduling the policy of computing task offloading. + +Resource allocation is a function that schedules the computing resources in the computing power resource pool. The function receives computing power transaction information from the CPN service layer and by looking up the resource information table, the resources scheduling policy will be made by this function. Additionally, when the user requests for the edge computing services with low latency requirements, the functions residing in the adjacent CPN gateways will cooperate to allocate the resources. + +Computing and network connection scheduling is a function that builds up the connection between the computing power consumer and the computing power provider. The CPN service layer sends the network performance parameters such as bandwidth, latency, jitter, etc. to the function entity, and using the resource allocation policy, this function schedules the network connection to meet the various computing service demands. + +## **7.2 CPN gateway user plane** + +The CPN gateway user plane mainly provides user packets transmission under the instruction of the CPN gateway control plane. The CPN gateway user plane can be implemented in different types of forwarding hardware, including network process (NP)-based dedicated equipment, application specific integrated circuit (ASIC)-based dedicated equipment, or X86-based commercial equipment, etc. Multiple routing and forwarding schemes have been proposed based on mainstream IPv6/SRV6 protocol extensions, including edge update, software-defined networking (SDN) control, and hop by hop update. The CPN gateway user plane should support multiple methods of traditional IP addressing and IP/service ID hybrid addressing, forming a new data plane for computing power routing. + +The CPN gateway user plane should have the following capabilities: + +- 1) Support forwarding packets according to the computing power forwarding table items. +- 2) Support scheduling of available computing resources of computing resource pool and associated network resources. +- 3) Support reporting network status information such as node capabilities, neighbour relationships, and IP prefixes to the CPN gateway control plane, and executing instructions issued by the CPN gateway control plane and forwarding packets. + +- 4) Support forwarding packets according to the different forwarding policies. +- 5) Support actively establishing network connections between designated users and computing power resource pools according to the service network connection demands issued by the CPN gateway control plane. The connection can be created using various technologies, such as virtual extensible local area network (VxLAN), SR/SRV6, secure socket layer (SSL) virtual private network (VPN), IPsec VPN, etc. + +## **7.3 CPN orchestration and management** + +CPN orchestration and management supports the unified orchestrations of computing resources, network resources, and computing services by managing them. The orchestration function includes unified orchestration of computing power resources and network resources, service intention perception analysis, digital twins of computing networks, and intelligent computing power resource and network resource orchestration. + +The main function of the CPN orchestration and management is to orchestrate computing and network resources, quickly allocate resources based on transaction contracts, such as virtual machine/container allocation, virtual private cloud (VPC) construction, network connection establishment, etc., and quickly recover resources and update resource information after completion. In addition, it supports computing power modelling according to various services and operation administration and maintenance (OAM) functions for the CPN [ITU-T Y.2501]. + +## **7.4 CPN service layer** + +The CPN service layer is responsible for the information exchange between the computing network and user services. User services, such as VR/AR, V2X, AI, etc. support submitting their own computing power and network access requests to the computing power network, as well as understanding real-time status information of the computing power resources and network resources, to achieve on-demand provision and flexible scheduling of computing power resources and network resources. Specifically, the service requests of the business or application are mapped to service application information and user business requests, including parameters such as computing power requests, and sent to the computing power routing node. The CPN service layer can also realize the functions of the computing power transaction, it supports resource information processing, billing and transaction process execution [ITU-T Q.4140]. + +# **8 Signalling procedures of intelligence control for the CPN gateway** + +## **8.1 Information interaction for intelligence control for the CPN gateway** + +In CPN, the CPN gateways exchange computing power resource information and network resource information with each other and with the forwarding equipment of the bearer network through control signalling, and then report them to the CPN gateway control component. The CPN gateway control component generates forwarding routes according to the computing resource information, network topology information and network status information, combined with forwarding strategies, and then selects appropriate computing nodes to deliver tasks. To this end, further discussion is needed on the relevant content of information exchanged, as well as the technical implementation requirements. The architecture is shown in Figure 8-1. + +![Diagram illustrating information exchange in the CPN. A central cloud represents the network, containing PE1, P1, PE2, P2, P3, and PE3. Three CPN gateways (UP1, UP2, UP3) are connected to the cloud, each associated with a cloud resource pool (1, 2, and 3 respectively). A CPN gateway-CP is shown at the top left, connected to the cloud. A WAN controller is shown at the top right, connected to the cloud. Dashed lines represent information exchange paths between the CPN gateways and the cloud network elements.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram illustrating information exchange in the CPN. A central cloud represents the network, containing PE1, P1, PE2, P2, P3, and PE3. Three CPN gateways (UP1, UP2, UP3) are connected to the cloud, each associated with a cloud resource pool (1, 2, and 3 respectively). A CPN gateway-CP is shown at the top left, connected to the cloud. A WAN controller is shown at the top right, connected to the cloud. Dashed lines represent information exchange paths between the CPN gateways and the cloud network elements. + +Q.4141(23) + +**Figure 8-1 – Information exchange in the CPN** + +### 1) Contents of information interaction + +The two-way transmission of information to each other is realized through information collection and information distribution. The interactive information includes network information and computing power resources information. + +Network information: + +- Topology information of the network. +- Link bandwidth, delay, jitter, packet loss rate and other related information. + +Computing power resources information: + +- CPU, graphics processing unit (GPU), neural network processing unit (NPU) and other processor information. +- Memory information. +- Store information. + +### 2) Technical requirements for information interaction + +- Information exchange between computing power network gateway user plane (CPN-GW-UP) and provider edge (PE) equipment: + - The CPN gateway supports the proactive notification of the latest status of the internal information of the cloud resource pool to the bearer network PE equipment on a regular basis. + - Provider edge (PE) equipment supports actively requesting the CPN gateway for internal information of the cloud resource pool. + - The CPN gateway supports the ability to adjust the frequency of advertising information to PE equipment. +- Information exchange between bearer network PE equipment: + - Support information automatic discovery and information exchange such as based on interior gateway protocol (IGP), border gateway protocol (BGP), and BGP+ Ethernet virtual private network (EVPN). + - Supports the ability to adjust the frequency of information announcements. +- Information exchange between bearer network equipment and the computing power network gateway control plane (CPN-GW-CP)/PE controller: + +- The bearer network equipment supports reporting information to the CPN-GW-CP/PE controller. +- The ability of the CPN-GW-CP/PE controller to support routing decisions and path policy issuance. +- The CPN-GW-CP/PE controller supports information exchange with bearer network equipment, and realizes the ability to make path decisions and deliver results. + +## 8.2 Signalling procedures for intelligence control for the CPN gateway + +### 8.2.1 Computing power resource information perception process + +The perception of computing power resource information usually includes the IP address, computing power, storage capacity, and other contents of the computing power resource pool. The cloud resource pools are generally centrally managed by the cloud management platforms. The CPN gateway can interact with the cloud management platform through interfaces (such as RESTful APIs) to obtain the IP address, computing power, storage capacity, etc. of the computing resource pool, and ultimately report the perceived computing power information to the CPN-GW-CP. The procedures are shown in Figure 8-2. + +![Sequence diagram of the computing power information perception process. Lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, Cloud 2. The process involves four steps: 1. Cloud 1 advertises info to CPN-GW-UP1; 2. CPN-GW-UP1 reports info to CPN-GW-CP; 3. Cloud 2 advertises info to CPN-GW-UP2; 4. CPN-GW-UP2 reports info to CPN-GW-CP.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +sequenceDiagram + participant Cloud 1 + participant CPN-GW-CP + participant CPN-GW-UP1 + participant PE1 + participant P1 + participant P2 + participant P3 + participant PE2 + participant CPN-GW-UP2 + participant Cloud 2 + + Note right of Cloud 1: 1. Advertising the computing power resource information to CPN-GW-UP1 + Cloud 1->>CPN-GW-UP1: + Note left of CPN-GW-UP1: 2. Reporting the cloud resource information to CPN-GW-CP + CPN-GW-UP1->>CPN-GW-CP: + Note right of Cloud 2: 3. Advertising the computing power resource information to CPN-GW-UP2 + Cloud 2->>CPN-GW-UP2: + Note left of CPN-GW-UP2: 4. Reporting the cloud resource information to CPN-GW-CP + CPN-GW-UP2->>CPN-GW-CP: + +``` + +Q.4141(23) + +Sequence diagram of the computing power information perception process. Lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, Cloud 2. The process involves four steps: 1. Cloud 1 advertises info to CPN-GW-UP1; 2. CPN-GW-UP1 reports info to CPN-GW-CP; 3. Cloud 2 advertises info to CPN-GW-UP2; 4. CPN-GW-UP2 reports info to CPN-GW-CP. + +**Figure 8-2 – Computing power information perception process** + +Step 1: Cloud resource pools 1 advertises the computing power resource information to CPN-GW-UP1. + +Step 2: CPN-GW-UP1 reports the cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. + +Step 3: Cloud resource pools 2 advertises the computing power resource information to CPN-GW-UP2. + +Step 4: CPN-GW-UP2 reports cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. + +### 8.2.2 Network information perception process + +The perception of network information usually includes content such as latency, bandwidth, packet loss rate, jitter, etc. Taking network latency as an example, due to the distribution of computing power resource pools in different locations, the network path from users to resource pools will also change based on network congestion status. Therefore, it is necessary to detect the latency information between users and various computing power resources pools. The delay detection of the CPN gateway is divided into two parts: one is the delay detection between the computing power resource pool and the CPN gateway. The other is the delay detection between the CPN gateways. The procedures are shown in Figure 8-3. + +![Sequence diagram illustrating the network information perception process. The diagram shows interactions between Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, and Cloud 2. The process involves five steps: 1. Delay detection between Cloud 1 and CPN-GW-UP1; 2. Delay detection between CPN-GW-UP1 and CPN-GW-UP2 via PE1, P1, P2, P3, and PE2; 3. Delay detection between CPN-GW-UP2 and Cloud 2; 4. Reporting network information from CPN-GW-UP1 to CPN-GW-CP; 5. Reporting network information from CPN-GW-UP2 to CPN-GW-CP.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant Cloud 1 + participant CPN-GW-CP + participant CPN-GW-UP1 + participant PE1 + participant P1 + participant P2 + participant P3 + participant PE2 + participant CPN-GW-UP2 + participant Cloud 2 + + Note left of CPN-GW-UP1: 1. Delay detection between the computing power resource pool 1 and the CPN-GW-UP1 + CPN-GW-CP->>CPN-GW-UP1: + Note left of CPN-GW-UP2: 2. Delay detection between the CPN-GW-UP1 and the CPN-GW-UP2 + CPN-GW-UP1->>PE1: + PE1->>P1: + P1->>P2: + P2->>P3: + P3->>PE2: + PE2->>CPN-GW-UP2: + Note left of Cloud 2: 3. Delay detection between the computing power resource pool 2 and the CPN-GW-UP2 + CPN-GW-UP2->>Cloud 2: + Note left of CPN-GW-CP: 4. Reporting the network information to CPN-GW-CP + CPN-GW-UP1->>CPN-GW-CP: + Note left of CPN-GW-CP: 5. Reporting the network information to CPN-GW-CP + CPN-GW-UP2->>CPN-GW-CP: + +``` + +Q.4141(23) + +Sequence diagram illustrating the network information perception process. The diagram shows interactions between Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, and Cloud 2. The process involves five steps: 1. Delay detection between Cloud 1 and CPN-GW-UP1; 2. Delay detection between CPN-GW-UP1 and CPN-GW-UP2 via PE1, P1, P2, P3, and PE2; 3. Delay detection between CPN-GW-UP2 and Cloud 2; 4. Reporting network information from CPN-GW-UP1 to CPN-GW-CP; 5. Reporting network information from CPN-GW-UP2 to CPN-GW-CP. + +**Figure 8-3 – Network information perception process** + +- Step 1: Delay detection between the computing power resource pool 1 and the CPN gateway CPN-GW-UP1. +- Step 2: Delay detection between the CPN gateway CPN-GW-UP1 and the CPN gateway CPN-GW-UP2. +- Step 3: Delay detection between the computing power resource pool 2 and the CPN gateway CPN-GW-UP2. +- Step 4: CPN-GW-UP1 reports the network information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 5: CPN-GW-UP2 reports the network information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. + +### 8.2.3 Computing power routing strategy + +The CPN-GW-CP collects computing power resource and network resource information through the CPN-GW-UP, and determines the optimal computing resource node and network path, and then issues computing resource allocation instructions and routing strategies to the CPN-GW-UP separately. The CPN-GW-UP transmits user packets under the instructions of the CPN-GW-CP. + +The procedures are shown in Figure 8-4. + +![Sequence diagram illustrating the computing power routing strategy. Lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, Cloud 2. The sequence involves resource information exchange and network detection between UP1 and UP2, followed by reporting to CP and subsequent route allocation by CP to both UP1 and UP2.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant Cloud 1 + participant CPN-GW-CP + participant CPN-GW-UP1 + participant PE1 + participant P1 + participant P2 + participant P3 + participant PE2 + participant CPN-GW-UP2 + participant Cloud 2 + + Note left of CPN-GW-UP1: 1. Obtaining the computing power resource and network resource information + CPN-GW-UP1->>CPN-GW-UP2: 2. Network information detection between the CPN-GW-UP1 and the CPN-GW-UP2 + Note right of CPN-GW-UP2: 3. Obtaining the computing power resource and network resource information + CPN-GW-UP1->>CPN-GW-CP: 4. Reporting the network information and cloud resource information to CPN-GW-CP + CPN-GW-UP2->>CPN-GW-CP: 5. Reporting the network information and cloud resource information to CPN-GW-CP + CPN-GW-CP->>CPN-GW-UP1: 6. Allocating computing power nodes and issues route strategies to CPN-GW-UP1 + CPN-GW-CP->>CPN-GW-UP2: 7. Allocating computing power nodes and issues route strategies to CPN-GW-UP2 + +``` + +Sequence diagram illustrating the computing power routing strategy. Lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, Cloud 2. The sequence involves resource information exchange and network detection between UP1 and UP2, followed by reporting to CP and subsequent route allocation by CP to both UP1 and UP2. + +Q.4141(23) + +**Figure 8-4 – Computing power routing strategy** + +- Step 1: CPN-GW-UP1 obtains the computing power resource and network resource information. +- Step 2: Network information detection between the CPN-GW-UP1 and CPN-GW-UP2. +- Step 3: CPN-GW-UP2 obtains the computing power resource and network resource information. +- Step 4: CPN-GW-UP1 reports the network information and cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 5: CPN-GW-UP2 reports the network information and cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 6: CPN-GW-CP allocates computing power nodes and issues route strategies to CPN-GW-UP1 according to service requirements. +- Step 7: CPN-GW-CP allocates computing power nodes and issues route strategies to CPN-GW-UP2 according to service requirements. + +### 8.2.4 Route selection procedure + +The CPN gateway can support the path selection function based on IP route forwarding, multiple protocol label switch (MPLS) label forwarding and the segment routing (SR) source route, and can control the order in which traffic enters the processing unit according to service requirements. The procedures are shown in Figure 8-5. + +![Sequence diagram illustrating the route selection procedure between Cloud 1 and Cloud 2 through various network nodes.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +The diagram is a sequence diagram showing the interaction between ten lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, and Cloud 2. The sequence of messages is as follows: + +- CPN-GW-UP1 sends a message to CPN-GW-CP: "1. Reporting the network information and cloud resource information to CPN-GW-CP". +- CPN-GW-CP sends a message to CPN-GW-UP1: "2. Allocating computing power nodes and issues route strategies to CPN-GW-UP1". +- CPN-GW-UP2 sends a message to CPN-GW-CP: "3. Reporting the network information and cloud resource information to CPN-GW-CP". +- CPN-GW-CP sends a message to CPN-GW-UP2: "4. Allocating computing power nodes and issues route strategies to CPN-GW-UP2". +- CPN-GW-CP sends a message to Cloud 1: "5. Selecting route path for the service according to the route policies issued by CPN-GW-CP". This message is followed by a series of arrows indicating the selected path: CPN-GW-UP1 → PE1 → P1 → P2 → P3 → PE2 → CPN-GW-UP2 → Cloud 2. + +Q.4141(23) + +Sequence diagram illustrating the route selection procedure between Cloud 1 and Cloud 2 through various network nodes. + +**Figure 8-5 – Route selection procedure** + +- Step 1: CPN-GW-UP1 reports the network information and cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 2: CPN-GW-CP allocates computing power nodes and issues route strategies to CPN-GW-UP1 according to the service requirements. +- Step 3: CPN-GW-UP2 reports the network information and cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 4: CPN-GW-CP allocates computing power nodes and issues route strategies to CPN-GW-UP2 according to the service requirements. +- Step 5: CPN-GW-UP1 selects cloud1 → CPN-GW-UP1 → PE1 → P2 → P 3 → PE2 → CPN-GW-UP2 → cloud2 path for forwarding packets according to the route policies issued by CPN-GW-CP. + +### 8.2.5 Load balancing process + +The CPN gateway can support multi-egress functions based on IP route forwarding, MPLS label forwarding and SR source route, and can balance traffic among multiple processing units according to the service requirements. The procedures are shown in Figure 8-6. + +![Sequence diagram illustrating the load balancing procedure. Lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, Cloud 2. The process involves reporting network information, allocating nodes, and then forwarding data packets via multiple paths (Path 1 and Path 2) to balance traffic load.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram is a sequence diagram with the following lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, and Cloud 2. The sequence of messages is as follows: + +- CPN-GW-UP1 reports network and cloud resource information to CPN-GW-CP. +- CPN-GW-CP allocates computing power nodes and route strategies to CPN-GW-UP1. +- CPN-GW-UP2 reports network and cloud resource information to CPN-GW-CP. +- CPN-GW-CP allocates computing power nodes and route strategies to CPN-GW-UP2. +- Cloud 1 sends a data packet to CPN-GW-UP1. +- CPN-GW-UP1 selects multiple paths for forwarding packets to balance traffic load according to the route policies issued by CPN-GW-CP. +- Path 1: CPN-GW-UP1 → PE1 → P2 → P3 → PE2 → CPN-GW-UP2 → Cloud 2. +- Path 2: CPN-GW-UP1 → PE1 → P3 → PE2 → CPN-GW-UP2 → Cloud 2. + +Q.4141(23) + +Sequence diagram illustrating the load balancing procedure. Lifelines: Cloud 1, CPN-GW-CP, CPN-GW-UP1, PE1, P1, P2, P3, PE2, CPN-GW-UP2, Cloud 2. The process involves reporting network information, allocating nodes, and then forwarding data packets via multiple paths (Path 1 and Path 2) to balance traffic load. + +**Figure 8-6 – Load balancing procedure** + +- Step 1: CPN-GW-UP1 reports the network information and cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 2: CPN-GW-CP allocates computing power nodes and issues route strategies to CPN-GW-UP1 according to the service requirements. +- Step 3: CPN-GW-UP2 reports the network information and cloud resource information to CPN-GW-CP, CPN-GW-CP maintains the resource information table. +- Step 4: CPN-GW-CP allocates computing power nodes and issues route strategies to CPN-GW-UP2 according to the service requirements. +- Step 5-7: When the data packet is forwarded from cloud1 to CPN-GW-UP1, CPN-GW-UP1 selects multiple paths for forwarding packets to balance traffic loads according to the route policies issued by CPN-GW-CP. For example: +- Path 1: CPN-GW-UP1 → PE1 → P2 → P3 → PE2 → CPN-GW-UP2 → cloud2, and + - Path 2: CPN-GW-UP1 → PE1 → P3 → PE3 → PE2 → CPN-GW-UP2 → cloud2. + +# 9 Security considerations + +The new architecture, technologies, and services of computing power networks may pose new security risks that need to be addressed, and new security mechanisms that are compatible with CPNs are needed to ensure their security. There are potential complex network risks and computing power node security risks in the infrastructure layer. The orchestration and management layer are involved in the security risks of orchestration and the issue of uncontrolled use of computing power. The CPN service layer faces issues such as accessing malicious nodes, untrustworthy transactions, and insecure applications. In addition, there may be data security risks in the computing power network, such as unreliable calculation results and uncontrollable data flow. It is necessary to strengthen security through an integrated full process trust mechanism. + +The computing network architecture puts forward new requirements for security. Intelligence control for the CPN gateway needs to build end-to-end multi network elements and multi-level cooperative security protection capabilities. Information security, functional security, privacy + +security, trusted security and demand characteristics need to be considered as a whole to provide different security characteristics at different levels. The specific requirements are as follows: + +- The security function shall support intelligent and active adaptation architecture of intelligence control for the CPN gateway, and be able to deploy and expand flexibly. +- Security functions and service support are dynamically deployed to the CPN gateway with applications. +- The CPN gateway supports the isolation of the network domain, controls the scope of security attacks and risks, and avoids attacks from point to surface. +- The CPN gateway supports continuous security detection and response. + +# Appendix I + +## Use case descriptions + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Edge computing interconnect scenario + +A use case of an edge computing interconnect scenario is shown in Figure I.1. The consumers could be Internet of things (IoT) devices, mobile device users, auto-driving vehicles, etc. The computing task requiring low communication latency will be distributed to the nearest edge cloud by the CPN transaction platform in advance. The platform will also allocate other edge clouds to the computing task for the candidate computing node. When the edge cloud lacks computing power, the CPN gateways connected to the computing node should schedule inter-domain computing power in a distributed way. As shown in Figure I.1, the edge cloud1 is short of computing power. The scheduling procedure is described below. + +Procedure 0 – Information on the computing resources and network performances in the edge cloud is reported to the control plane of the CPN gateway and an intra-domain resources information table is maintained by the resource information collection function. The table will be exchanged by the neighbouring CPN-GW-CP1 and CPN-GW-CP2 to maintain the inter-domain resource information table. + +Procedures 1 and 2 – The consumers submit a computing task to the edge cloud1. However, the computing power is not enough. An inter-domain computing power scheduling request will be sent to the connected CPN-GW-CP1. + +Procedure 3 – According to the inter-domain resource information table, the edge cloud1 chooses edge cloud2 to conduct computing offloading and sends the computing task. + +Procedure 4 – The CPN-GW-CP2 consults the intra-domain resource information table and allocates the computing power for the task. The network connection will then be constructed to satisfy the network requirements of the task. + +Procedure 5 – The consumers will be notified that the computing node is changed and send data to the servers deployed in the edge cloud2. The results will then be processed and returned to the consumers. + +![Figure I.1: Use case in an edge computing interconnect scenario. The diagram shows a network architecture with four main components: CPN-GW-CP1, CPN-GW-CP2, CPN-GW-UP1, and CPN-GW-UP2. CPN-GW-CP1 and CPN-GW-CP2 are connected to a central WAN (Wide Area Network) node. CPN-GW-UP1 and CPN-GW-UP2 are connected to an AN (Access Network) node. The AN node is connected to a Consumer (represented by a person, a camera, and a car). The Consumer is connected to two Edge clouds: Edge cloud1 and Edge cloud2. The diagram is numbered 0 to 5, indicating the flow of data or requests. A small text 'Q.4141(23)' is visible in the bottom right corner.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Figure I.1: Use case in an edge computing interconnect scenario. The diagram shows a network architecture with four main components: CPN-GW-CP1, CPN-GW-CP2, CPN-GW-UP1, and CPN-GW-UP2. CPN-GW-CP1 and CPN-GW-CP2 are connected to a central WAN (Wide Area Network) node. CPN-GW-UP1 and CPN-GW-UP2 are connected to an AN (Access Network) node. The AN node is connected to a Consumer (represented by a person, a camera, and a car). The Consumer is connected to two Edge clouds: Edge cloud1 and Edge cloud2. The diagram is numbered 0 to 5, indicating the flow of data or requests. A small text 'Q.4141(23)' is visible in the bottom right corner. + +**Figure I.1 – Use case in an edge computing interconnect scenario** + +## I.2 Data centre interconnect scenario + +As shown in Figure I.2, a use case in a data centre interconnect scenario is described. Unlike in the edge computing interconnect scenario, the network control plane is divided into two parts. The inter-domain part is the wide area network (WAN) inter-domain controller, which manages the inter-domain traffic. The intra-domain part is the intra-domain control plane of the CPN gateways, which manages the intra-domain traffic. Thus, in this scenario, the inter-domain computing power is scheduled in a centralized way and the procedure is described below. + +Procedure 0 – The intra-domain information of computing resources and network performances will be collected by the intra-domain control plane of the CPN gateway and the intra-domain resource information table is maintained in the CPN gateway control plane. + +Procedure 1 – The intra-domain resource information table is sent to the WAN inter-domain controller. The controller maintains the inter-domain resource information table, which contains the inter-domain information of computing resources and network performances. + +Procedure 2 – The inter-domain resource information table is sent to the CPN transaction platform and the platform integrates the resource information and makes a resource quotation. + +Procedures 3 and 4 – When a user terminal requests resources for a computing task, the request will be sent to the platform. The platform then generates a resource view for the user. The users choose the most suitable resources and make a transaction contract with providers. + +Procedure 5 – The platform sends the transaction information to the WAN inter-domain controller. The controller consults the inter-domain resources information table and allocates the inter-domain resources for the transaction. The inter-domain network connection between the user and the chosen data centre will be constructed and maintained by the inter-domain controller. The transaction will then be delivered to the intra-domain CPN gateway controller. + +Procedure 6 – The transaction will be delivered to the intra-domain CPN gateway controller. + +Procedure 7 – By consulting the intra-domain resource information table, resources will be allocated locally by the intra-domain CPN gateway controller and the network connection between the resources and the consumers will be constructed and maintained. + +Procedures 8 and 9 – The user terminal sends the computing task to the server. The server accomplishes the computing task and returns the results to the user terminal. + +![Diagram of a data centre interconnect scenario showing a user terminal, platform, WAN interdomain controller, central cloud, WAN-core, CPN-GW-UP, and Intradomain CPN-GW-CP with numbered arrows indicating data flow.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +The diagram illustrates a network architecture for data centre interconnect. At the top left is a 'User terminal' (represented by a computer icon). At the top center is a 'Platform' (represented by a cloud of nodes). At the top right is a 'WAN interdomain controller' (represented by a server icon). At the bottom left is a 'Central cloud' (represented by a stack of server icons). In the center is a 'WAN-core' (represented by a circle containing four switches). At the bottom center is a 'CPN-GW-UP' (represented by a circle containing two switches). At the bottom right is an 'Intradomain CPN-GW-CP' (represented by a server icon). Numbered arrows (0-9) show the flow of data: 0 from Central cloud to CPN-GW-UP; 1 from CPN-GW-UP to Intradomain CPN-GW-CP; 2 from Intradomain CPN-GW-CP to WAN interdomain controller; 3 from WAN interdomain controller to Platform; 4 from Platform to WAN-core; 5 from WAN-core to Platform; 6 from WAN interdomain controller to CPN-GW-UP; 7 from Intradomain CPN-GW-CP to CPN-GW-UP; 8 from CPN-GW-UP to User terminal; 9 from CPN-GW-UP to Central cloud. A small text 'Q.4141(23)' is located below the Intradomain CPN-GW-CP label. + +Diagram of a data centre interconnect scenario showing a user terminal, platform, WAN interdomain controller, central cloud, WAN-core, CPN-GW-UP, and Intradomain CPN-GW-CP with numbered arrows indicating data flow. + +**Figure I.2 – Use case in a data centre interconnect scenario** + +# Appendix II + +## Deployment of the CPN gateway + +(This appendix does not form an integral part of this Recommendation.) + +In the application deployment of CPN gateways, two networking solutions, hybrid and distributed, are mainly considered. + +## II.1 CPN gateway hybrid networking + +In the hybrid networking solution, the computing network orchestration system [ITU-T Y.2501] relies on the cloud/computing management and control module to collect computing resource information from each computing power resource pool through the CPN gateway, and collects network topology information through the network management and control module. The computing network orchestration system determines the optimal computing resource nodes and network forwarding paths. The cloud/computing management and control module, and the network management and control module issue computing resource allocation instructions and routing strategies respectively. + +![Diagram of CPN gateway hybrid networking architecture showing the flow of information between a central orchestration system and multiple CPN gateways.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +The diagram illustrates the hybrid networking architecture. At the top, a box labeled 'Computing and networking orchestration system' contains two sub-modules: 'Network management and control module' and 'Cloud/computing management and control module', connected by a dashed double-headed arrow. Below this, a large yellow cloud represents the network area, containing six 'The CPN gateway' nodes, each represented by a blue router icon. To the left of the cloud is a building icon representing a user or application. Four numbered arrows indicate the flow of information: 1. 'Report computing power information' from the CPN gateways to the Cloud/computing management module. 2. 'Computing power information synchronization' from the Cloud/computing management module to the CPN gateways. 3. 'Computing power, path calculation, and routing policy generation' from the Network management module to the CPN gateways. 4. 'Deliver routing policy' from the Network management module to the CPN gateways. The caption below the diagram is 'The CPN gateway hybrid networking' and the reference code is 'Q.4141(23)'. + +Diagram of CPN gateway hybrid networking architecture showing the flow of information between a central orchestration system and multiple CPN gateways. + +**Figure II.1 – The CPN gateway hybrid networking** + +Under this architecture, the main functions of the CPN gateway should include obtaining computing resource information and link information of computing power nodes, and receiving path policy information issued by the network management and control module, etc. + +## II.2 CPN gateway distributed networking + +In the distributed solution, the CPN gateway needs to implement functions such as computing power resource awareness, computing power resource information distribution, computing resource routing table generation, and policy customization, as shown in Figure II.2. In addition to supporting the release and notification of computing resource information, the distributed solution also needs to generate routing policies through computing power and path calculations and bind the + +routing policies based on user and application perception, thereby achieving information synchronization of computing resources and network resources, and unified scheduling. + +![Diagram of CPN gateway distributed networking showing a hybrid network cloud with five CPN gateways. A building on the left is connected to one gateway. Above the cloud is a 'Computing and networking orchestration system' with two modules: 'Network management and control module' and 'Cloud/computing management and control module'. Arrows show information flow between the modules and the cloud. Numbered steps 1-5 describe the process: 1. Deliver computing power information; 2. Network-wide announcement of computing power information; 3. Computing power, path calculation, and routing policy generation; 4. User and application awareness, binding routing policy; 5. Network and computing power information synchronization. The diagram is labeled 'The CPN gateway hybrid networking' and 'Q.4141(23)'.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +The diagram illustrates the CPN gateway distributed networking architecture. At the top, a 'Computing and networking orchestration system' contains two modules: 'Network management and control module' and 'Cloud/computing management and control module', which are interconnected by dashed arrows. Below this, a large yellow cloud represents the network, containing five 'The CPN gateway' units, each represented by a cloud icon with a router symbol. On the left, a building icon represents a user or application, connected to one of the CPN gateways. The diagram is annotated with five numbered steps: 1. Deliver computing power information; 2. Network-wide announcement of computing power information; 3. Computing power, path calculation, and routing policy generation; 4. User and application awareness, binding routing policy; 5. Network and computing power information synchronization. The bottom of the diagram is labeled 'The CPN gateway hybrid networking' and 'Q.4141(23)'. + +Diagram of CPN gateway distributed networking showing a hybrid network cloud with five CPN gateways. A building on the left is connected to one gateway. Above the cloud is a 'Computing and networking orchestration system' with two modules: 'Network management and control module' and 'Cloud/computing management and control module'. Arrows show information flow between the modules and the cloud. Numbered steps 1-5 describe the process: 1. Deliver computing power information; 2. Network-wide announcement of computing power information; 3. Computing power, path calculation, and routing policy generation; 4. User and application awareness, binding routing policy; 5. Network and computing power information synchronization. The diagram is labeled 'The CPN gateway hybrid networking' and 'Q.4141(23)'. + +**Figure II.2 – CPN gateway distributed networking** + +The CPN gateway can sense the computing power resource pool information, and sense network information such as delay and packet loss through telemetry and other technologies, and so form a network delay circle for users to choose the appropriate computing power resource pool. The information is transmitted, using for example border gateway protocol (BGP) or internal gateway protocol (IGP) extension, to each computing power routing node device and computing power gateway in the computing power domain, to form a computing power IP routing table and build a resource view. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25f8fbfaef317942ed3102c74b40a7d42f80608b --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cab7dcabfe939b223d97242d8523e461968d21f7c5432693c30a64f2d95521 +size 7050 diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..197497394e802ad58cd05ba932b9dce013fb7bee --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7869e6b0a2daa86fcdab65c7dc57d60a611aa9bcd72227c71a25beb10c831635 +size 17183 diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4686e27bef3688baf3bd4e9bebdfdeb3046b4004 --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d76899d252a62ec79c4c86259337f123ceeac7dcc9d4c6835d2be5d1ea64dff +size 16753 diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dfa7677dae49517e5cd1ef07e47ca979de0edc7 --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b808cf71f2f25509484f78b68325cec0264dfb33877a8b2d3cb6cb061c84760b +size 16429 diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47cd248d167e40456e72cb9a98e061e02bc1370d --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52615cf03c4f4e0ff7eaeb98afe2360efbaeff1bb1bb5191c1ef83c1954268cf +size 16628 diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b0dc06d393dee308f83851147ad26c837ba45eb --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ef621a699bb0082a0aad9cfca5ba88fd60f47fac3d0f2ac279ae841d28c05d +size 17346 diff --git a/marked/Q/T-REC-Q.4164-202504-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b7233115fb6e499da00d9fc24123aa8e96d1599 --- /dev/null +++ b/marked/Q/T-REC-Q.4164-202504-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43b5766b397c1ea5780b2fa65978cf06d4a1a585c81c8fd0c156fd015ec75c99 +size 19132 diff --git a/marked/Q/T-REC-Q.44-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.44-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.44-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.44-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg b/marked/Q/T-REC-Q.44-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c881d3c54484756933b498f2b1a6fa1fe8af79db --- /dev/null +++ b/marked/Q/T-REC-Q.44-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b840424aa907ae14c0d06543ff1868ab660fe14a0579fc8d5f6a4f79d07be954 +size 55153 diff --git a/marked/Q/T-REC-Q.44-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.44-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..748ced43810923ef65f2d4c429425a8919194368 --- /dev/null +++ b/marked/Q/T-REC-Q.44-198811-I_PDF-E/raw.md @@ -0,0 +1,75 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.44** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**ATTENUATION DISTORTION** + +**ITU-T Recommendation Q.44** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.44 was published in Fascicle VI.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **ATTENUATION DISTORTION** + +## **1 Attenuation distortion** + +### **1.1 *All-analogue conditions*** + +The design objectives recommended for carrier terminal equipment by the Recommendation cited in [3] are such that for a chain of six circuits, each equipped with a single pair of channel translating equipments in accordance with that Recommendation, the network performance objective for the attenuation distortion given by Figure 1/G.132 [2] will in most cases be met. The distortion contributed by the seven international centres is thereby included. + +*Note* - To assess the attenuation distortion of the international chain, the limits indicated for international circuits in Recommendation G.151, § 1 [4] must not be added to the limits for international centres mentioned in Recommendation Q.45. In fact, on the one hand, some exchange equipment would be counted twice if this addition were made; on the other, the specification limits of Recommendation Q.45 apply to the worst possible connection through an international exchange, while the maintenance limits of Recommendation G.151, § 1 apply to the poorest international circuit. The specifications of the various equipments are such that the mean performance will be appreciably better than could be estimated by the above-mentioned addition. + +### **1.2 *Mixed analogue/digital conditions*** + +In the mixed analogue/digital period, it is expected that the attenuation/frequency characteristics of the analogue carrier terminal equipment that is to be used in international telephone connections will continue to be governed by existing Recommendations that are relevant to this type of circuit. + +Where unintegrated PCM digital processes are to be included in international telephone connections, it is recommended that the attenuation/frequency characteristic of the bandpass filters associated with such processes should comply with the more stringent version of Figure 1/G.712 [5]. The latter Recommendation applies specifically to cases where integrated PCM digital processes are associated with trunk junctions (toll connecting trunks), trunk circuits (intertoll trunks), and international circuits. + +With regard to the incorporation of unintegrated PCM digital processes in local telephone networks, the required attenuation/frequency characteristics of the bandpass filters involved are still under study. + +**2** The network performance objectives for the variation with frequency of transmission loss in terminal condition of a worldwide 4-wire chain of 12 circuits (international plus national extensions), each one routed over a single group link, are shown in Figure 1/Q.44 which assumes that no use is made of high-frequency radio circuits or 3-kHz channel equipment. + +![Graph showing permissible attenuation variation (dB) versus frequency (Hz) for a 4-wire chain. The y-axis ranges from -2.2 to 9 dB, with major ticks at 0, 2.2, 4.3, 8.7, and -2.2. The x-axis ranges from 300 to 3400 Hz, with major ticks at 300, 400, 500, 800, 2400, 3000, and 3400 Hz. The graph shows a series of steps and shaded regions representing the permissible variation. The steps are: 8.7 dB from 300 to 400 Hz, 4.3 dB from 400 to 500 Hz, 2.2 dB from 500 to 2400 Hz, 4.3 dB from 2400 to 3000 Hz, and 8.7 dB from 3000 to 3400 Hz. Shaded regions are shown above the 8.7 dB steps and below the -2.2 dB line. The label 'CCITT-44981' is at the bottom right.](5d92d5c9cc01a262b0389d138caa9aea_img.jpg) + +Graph showing permissible attenuation variation (dB) versus frequency (Hz) for a 4-wire chain. The y-axis ranges from -2.2 to 9 dB, with major ticks at 0, 2.2, 4.3, 8.7, and -2.2. The x-axis ranges from 300 to 3400 Hz, with major ticks at 300, 400, 500, 800, 2400, 3000, and 3400 Hz. The graph shows a series of steps and shaded regions representing the permissible variation. The steps are: 8.7 dB from 300 to 400 Hz, 4.3 dB from 400 to 500 Hz, 2.2 dB from 500 to 2400 Hz, 4.3 dB from 2400 to 3000 Hz, and 8.7 dB from 3000 to 3400 Hz. Shaded regions are shown above the 8.7 dB steps and below the -2.2 dB line. The label 'CCITT-44981' is at the bottom right. + +FIGURE I/Q.44 + Permissible attenuation variation with respect to its value measured at 800 Hz + (objective for worldwide 4-wire chain of 12 circuits in terminal service) + +# References + +- [1] CCITT Recommendation *Transmission losses, relative levels and attenuation distortion*, Vol. III, Rec. G.141. +- [2] CCITT Recommendation *Attenuation distortion*, Vol. III, Rec. G.132. +- [3] CCITT Recommendation *12-channel terminal equipments*, Vol. III, Rec. G.232, § 1. +- [4] CCITT Recommendation *General performance objectives applicable to all modern international circuits and national extension circuits*, Vol. III, Rec. G.151, § 1. +- [5] CCITT Recommendation *Performance characteristics of the PCM multiplex at audio frequencies*, Vol. III, Rec. G.712. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b65f1bcef568cb9f103fcdb9a3fc4a9e23a73a --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78c782303f90f191a7844f009556f9872048cc35ffb8089c0451efd4b1bea550 +size 83014 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8002433dd55274f130d81bc704421f35c2044960 --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5241ea6728da8499acd33bfae57f950a14a4f964dafb8ec93ed45c6ad6fea7b +size 58599 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..279893486816f830f34f27d53709d2309ccc4916 --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d5d11513ca480e7294b76ea81614f2f826f2a1c7f56b8897c45383e2b49af4b +size 118727 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d847b716c297ffd8232583a36ec8accd108b8aa9 --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27d0b592cec55e2c126824aec392563e17a399d0926719ffdcccbb89da75ce85 +size 15120 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9260c351a5bc78331d0c81d83b99863cb6e7a960 --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7ce196dbc7e86612b26d15b331ed9dff38f0c17b0ca7a588a3ebc78a1a7a11b +size 39518 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8fa13d1ede6caa347e198ce5a535d256fcedc65 --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c3fc37a05b96753aff384b717395e8e0c3febbe9e6bb862186b732a416776b1 +size 59679 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f939592bc63fdfc3a01b6ae8a49cd3f31c0b531 --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e12c236a88f3b341cf57de82153dbb7dbe347d6f50d39dc29da23ccb8d28e2e8 +size 15728 diff --git a/marked/Q/T-REC-Q.5006-202307-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f3f92a3ad65024d53cf0d4054c5123528d635fc --- /dev/null +++ b/marked/Q/T-REC-Q.5006-202307-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38daccab0fd408c8fc5132f6876ce9b9d4f50b0830ea1b6e3afc2fcac8c2f252 +size 11874 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c +size 4070 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9af847170a82589f238aa3f400ff4a3d736d6ce4 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bd1ca8273766cedd2fd739c4be728a3b8ac182216992040b4feffadaa2dda33 +size 59351 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af5636ae8c425cb882e0b594c6da8c46dda591e3 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feb8306ad5b28389ac43ecfe91a0dc7f157e7020fa86f0d1262c4d43f8412654 +size 76396 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef00b8b65b47211771f834a66b315ec8a0f162be --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2cc863009ef463aa0f9e690a4805e9e799d3cee93bd62b4543a3b408a229341 +size 81944 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3354e5b09adaedfe65309a370a91cc2cb4e3124d --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb81b393ea2b0fdc732f61e9fe7b66860249e8a6174253b21d5e01d535733f7f +size 63636 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45e2d6146717a9f2e55c8a69f47c775324b7d8f2 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a02217eaa49d9c912429e9d001ddedc0daea8e2d616f040ffe15e2b97bd1665e +size 75972 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b7cf8a6799aca92c59f7363cb6160df7eb66a98 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b53e758ade254232618921ee57a8ad3aed4d0ee89be31e31d4b9d19f2426171 +size 109305 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1f8ae497ea0ef51e874da9fbc736fa563511f70 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5c2aad6dd521a925e98ded5b9540b57e880a3de21749628ea6fc543f8ed2142 +size 39829 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21eed166006e456acf7e4378ec6a789b1d74c0aa --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4780db09007017b3b9d5f09e8eea246019d99094ba4f875600cee330086054f3 +size 114113 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65403b98ad002b926896ab651acd476c4ce11c2f --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b760c8e471b11bae40b11ab2133710040efb84dbead6b0d6b6634d40b253f6d +size 48292 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85832e1519af6e4de1910a3f8d118b3eb9e635b3 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58c7cda49a41e5547f10001a9a769571123a4e1e19835ed506796c3ab3bd0958 +size 31474 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd141d24d7a6e65b5796f85a68cb1d0d2ff22b37 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92bf10bda80ce970b94ba6eab0e5f4fa1e189ff7b28b05a86b231ad35bb73926 +size 113901 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7977d9c88b3dc83af90f471bd37d8370192a9cbc --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:519cfb01e2f1b564a49f1da5afc066268922d202b513fe4742f8dce9479e5946 +size 79500 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3090b61b90dc07f1873832352d61287b8de343f2 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77270d752a0fdf9fbec8b89a0c4ac76a9e72945ae9cdb532205b9214989313d6 +size 16033 diff --git a/marked/Q/T-REC-Q.5022-202004-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c9e370b53f35adb2effd6aebb7c64da57e7a900 --- /dev/null +++ b/marked/Q/T-REC-Q.5022-202004-I_PDF-E/raw.md @@ -0,0 +1,534 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.5022** + +(04/2020) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for IMT-2020 – +Protocols for IMT-2020 + +--- + +**Signalling procedure of energy efficient device-to-device communication for IMT-2020 networks** + +Recommendation ITU-T Q.5022 + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| Signalling requirements and architecture of IMT-2020 | Q.5000–Q.5019 | +| Protocols for IMT-2020 | Q.5020–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.5022 + +# Signalling procedure of energy efficient device-to-device communication for IMT-2020 networks + +## Summary + +According to different surveys, the number of wireless devices may reach trillions by 2020. The massive increase of wireless devices will lead to different interconnection and communication challenges. In this regard, most wireless devices would need to use device-to-device (D2D) communication. + +In general, D2D communication may bring additional benefits to new wireless devices such as higher throughput, better cell coverage, spectrum efficiency and other valuable features of the cellular networks. + +However, there is still a need to specify a procedure which may switch between two algorithms used for D2D communication according to the cell status, as follows: + +- communication algorithm which is used in a stable condition of the cell, +- communication algorithm which is used in the situation when the serving base station (BS) becomes unavailable at certain periods of time. + +This procedure should be based on an energy efficient intra-cell clustering and the procedure should be able to reuse frequency between clusters. The key advantage of the procedure is the reducing of the signalling overhead. + +Recommendation ITU-T Q.5022 describes a D2D communication procedure to be used as a part of the IMT-2020 control plane. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.5022 | 2020-04-29 | 11 | 11.1002/1000/14246 | + +## Keywords + +Clustering, device-to-device communication, procedure, signalling, IMT 2020. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Overview ..... | 2 | +| 7 Features of energy efficient D2D communication procedure..... | 3 | +| 7.1 Architecture and methodology ..... | 3 | +| 7.2 Cluster formation in normal mode ..... | 4 | +| 7.3 Signalling and connection set up in normal mode..... | 5 | +| 7.4 Discovery phase..... | 5 | +| 7.5 Cluster formation in failure mode ..... | 9 | +| Appendix I – Use cases of D2D communications in IMT-2020 networks..... | 13 | +| Appendix II – Gap analysis about D2D communications in related SDOs..... | 14 | +| Bibliography..... | 15 | + + + +## Recommendation ITU-T Q.5022 + +## Signalling procedure of energy efficient device-to-device communication for IMT-2020 networks + +# 1 Scope + +This Recommendation describes the procedure for device-to-device (D2D) communication based on energy efficient intra-cell clustering and the ability to reuse frequencies between intra-cell clusters. The aim of this procedure is to enable D2D communication in different conditions (normal mode and failure mode) in IMT-2020 network, including clustering in cell, switching between different modes, signalling for node discovery, and communication with neighbour cells. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 software-defined networking** [b-ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner. + +**3.1.2 network virtualization** [b-ITU-T Y.3011]: A technology that enables the creation of logically isolated network partitions over shared physical networks so that heterogeneous collections of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggregation of multiple resources in a provider and appearing as a single resource. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------| +| B-CH | Boundary Cluster Head | +| BS | Base Station | +| CH | Cluster Head | +| CM | Cluster Members | +| CSMA | Carrier Sense Multiple Access | +| D2D | Device to Device | + +| | | +|------|------------------------------------------| +| IMSI | International Mobile Subscriber Identity | +| MEC | Mobile Edge Computing | +| MLHC | Multilevel Hierarchical Clustering | +| NFC | Near Field Communication | +| NFV | Network Function Virtualization | +| QoS | Quality of Service | +| SDN | Software Defined Networking | +| TDMA | Time Division Multiple Access | +| TMSI | Temporary Mobile Subscribe Identity | +| UE | User Equipment | +| UWB | Ultra Wide Bandwidth | + +# 5 Conventions + +None. + +# 6 Overview + +Benefits of D2D – IMT-2020: + +The proposed procedure can be employed in the bottom layers of the IMT-2020 (data plane network function and resources). Besides, D2D – IMT-2020 provides the best way for integrating wireless sensors and other wireless devices into the cellular network, it also adds several benefits to the IMT-2020 system performance. + +1 – Spectrum efficiency (resources efficiency): + +Employing device to device (D2D) communication with frequency reuse and proper interference management increases the spectrum efficiency of IMT-2020 system. + +2 – Power efficiency: + +The proposed procedure stack increases the power efficiency of the IMT-2020 system by applying energy efficient clustering scheme. + +3 – Data rate: + +D2D – IMT-2020 achieves the high data rate required from the IMT-2020 by improving radio resources utilization. + +4 – Traffic congestion: + +D2D – IMT-2020 provides a way for offloading cellular traffic by introducing direct paths and thus reduces the traffic congestion anticipated from IMT-2020. + +5 – System coverage: + +D2D – IMT-2020 achieves higher availability and reliability of the system and thus increases the system coverage to a higher level. + +In this Recommendation: + +Normal operation mode is the network operation mode in which the base station (BS) works well and leads all the communication processes in the cellular cell. In this mode, the BS controls and monitors both types of communication (cellular and D2D) run inside the cellular cell. + +Failure operation mode is the network operation mode in which the inter-cell communication is maintained using D2D communication. If the BS goes into failure, the communication inside the cell takes place using D2D communication and multi-level clustering. + +Mode selection is the process of selecting the transmission mode if it will be a D2D or a cellular. + +Clustering of wireless devices is the way in which wireless nodes are organized into groups or clusters according to specific properties of nodes and network requirements. The leader of each group of nodes or cluster is known as the cluster head (CH) and the other non-CH nodes are known as member nodes. Each CH acts as the local coordinator of transmissions within its cluster (i.e., intra-cluster communication) and also communicates with other cluster heads or with the base station (i.e., inter-cluster communication). + +# 7 Features of energy efficient D2D communication procedure + +## 7.1 Architecture and methodology + +This procedure switches between two modes based on the network status. The first mode is the normal mode, which works as long as the network operation is in the normal situation, therefore the cell employs the normal mode when the BS works well. For the failure situations, the second mode is employed and thus it is defined as the failure mode. If the BS goes into failure due to a technical problem or a catastrophic situation the cell employs the failure mode. The network employs an intelligent core network based on software defined networking (SDN), network function virtualization (NFV) and mobile edge computing (MEC). Figures 7-1 and 7-2 illustrate the network topology in both modes while the mechanisms of clustering in the two modes are totally different. + +![Diagram of network topology in normal mode showing a central eNB connected to multiple clusters of devices.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram illustrates a network topology within a hexagonal cell. At the center is an 'eNB' (evolved NodeB) icon. Surrounding it are 12 clusters, each enclosed in a red circle. Each cluster contains one 'Cluster head' (represented by a blue smartphone icon) and one or more 'Cluster members' (represented by black smartphone icons). The cluster heads are connected to the central eNB, and the members are connected to their respective cluster heads. A legend at the bottom identifies the icons: a blue smartphone for 'Cluster head' and a black smartphone for 'Cluster member'. The text 'Q.5022(20)\_F7-1' is in the bottom right corner. + +Diagram of network topology in normal mode showing a central eNB connected to multiple clusters of devices. + +Figure 7-1 – Network topology in normal mode + +![Diagram of network topology in failure mode showing 15 clusters within a hexagonal cell. Each cluster is enclosed in a red circle and contains one 'Cluster head' (blue smartphone icon) and one or more 'Cluster members' (black smartphone icons). A legend at the bottom identifies the icons: a blue smartphone for 'Cluster head' and a black smartphone for 'Cluster member'. The text 'Q.5022(20)_F7-2' is in the bottom right corner.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Diagram of network topology in failure mode showing 15 clusters within a hexagonal cell. Each cluster is enclosed in a red circle and contains one 'Cluster head' (blue smartphone icon) and one or more 'Cluster members' (black smartphone icons). A legend at the bottom identifies the icons: a blue smartphone for 'Cluster head' and a black smartphone for 'Cluster member'. The text 'Q.5022(20)\_F7-2' is in the bottom right corner. + +**Figure 7-2 – Network topology in failure mode** + +## 7.2 Cluster formation in normal mode + +In normal mode, the network employs an in-band underlay D2D communication. In the in-band underlay D2D communication user equipment (UEs) close to each other are able to exchange data through a cellular direct link without transmitting and receiving to the BS. The BS performs an intra-cell clustering and forms many clusters. The BS selects cluster heads and constructs clusters based on the game theory. Each cluster has a cluster head and cluster members (CMs); and the communication between CMs and CH is established via direct link. After cluster formation, the resources are distributed by the BS. A portion of the cell bandwidth is dedicated to the D2D communication inside clusters. This part of the spectrum is shared by the clusters with the employing of frequency reuse. Figure 7-1 illustrates the network structure in this mode and Figure 7-3 shows the employment of frequency reuse mechanism between intra-cell clusters. + +![Diagram of a cell under normal mode. A central eNB (evolved NodeB) is surrounded by various user equipment (UE) labeled F1 through F9. The UEs are arranged in a hexagonal cell. F1 (orange) is at the top right, F3 (yellow) is at the top right, F5 (blue) is at the top left and right, F2 (white) is at the top left, F7 (purple) is at the top center, F8 (red) is at the center right, F4 (white) is at the left, F1 (orange) is at the center left, F6 (white) is at the bottom left, F3 (yellow) is at the bottom center, F1 (orange) is at the bottom right, F9 (white) is at the bottom right, F8 (red) is at the bottom left, F5 (blue) is at the bottom center, and F7 (purple) is at the bottom right. The eNB is in the center, emitting signals. A small text 'Q.5022(20)_F7-3' is visible in the bottom right corner of the diagram.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram of a cell under normal mode. A central eNB (evolved NodeB) is surrounded by various user equipment (UE) labeled F1 through F9. The UEs are arranged in a hexagonal cell. F1 (orange) is at the top right, F3 (yellow) is at the top right, F5 (blue) is at the top left and right, F2 (white) is at the top left, F7 (purple) is at the top center, F8 (red) is at the center right, F4 (white) is at the left, F1 (orange) is at the center left, F6 (white) is at the bottom left, F3 (yellow) is at the bottom center, F1 (orange) is at the bottom right, F9 (white) is at the bottom right, F8 (red) is at the bottom left, F5 (blue) is at the bottom center, and F7 (purple) is at the bottom right. The eNB is in the center, emitting signals. A small text 'Q.5022(20)\_F7-3' is visible in the bottom right corner of the diagram. + +**Figure 7-3 – The cell under normal mode** + +## 7.3 Signalling and connection set up in normal mode + +The proposed structure of clustering with in-band D2D communication reduces the signalling overhead to the information data due to the existence of CHs that lead all the communication processes inside clusters. + +Similar to the existing technologies of short-range wireless transmission (e.g., Wi-Fi direct, Bluetooth, near field communication (NFC) and ultra wide bandwidth (UWB)), the in- band D2D communications achieve a low transmission delay. Moreover, because of the use of licensed spectrum, the in-band D2D communication significantly increases the spectral efficiency, achieves high quality of service (QoS), offloads traffic, as well as achieves better system energy efficiency. The proposed in-band D2D signalling procedure for normal mode consists of two phases: Discovery phase and Communication phase. + +## 7.4 Discovery phase + +The discovery process is generally the main process for any type of D2D communication as the devices should first discover that they are in proximity with each other. The main advantage of involving network in the discovery process is to conserve the energy of the devices, provide higher latency efficiency and make the process more user friendly for the end user. The discovery is the first step to establish a D2D communication process. This process contains all the signalling between BS and UEs to establish a connection and set up clusters. Resource allocations by the BS to CHs are a part of this phase. Two discovery processes are applied in the procedure, one for discovering CHs (major discovery) and the other for discovering CMs (minor discovery). + +Major discovery: + +The major discovery process can be classified into two main categories as indicated in Figure 7-4. The first classification is from the network point of view and it can be classified as: a light BS control and a tight BS control. In the light BS control, the BS periodically broadcasts a set of available resources that can be used by CHs to transmit and receive the discovery beacon. While for the tight BS control, the BS solicits users who want to be CHs to transmit their discovery beacon. + +The second classification is from the user point of view and the discovery process can be seen as: Open discovery or restricted discovery. In the open discovery, all devices are available and can be detected and involved in the D2D communication process. For the other, the restricted discovery allows users to permit or prevent the D2D signalling requests. + +![](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph TD + MD[Major discovery] --> NPV[Network point of view] + MD --> UPV[User point of view] + NPV --> LBS[Light BS control] + NPV --> TBS[Tight BS control] + UPV --> OD[Open discovery] + UPV --> RD[Restricted discovery] + +``` + +Q.5022(20)\_F7-4 + +**Figure 7-4 – Classifications of major discovery process** + +For this mode of operation of the proposed signalling procedure, the light BS control was selected to act as the major discovery mode. Thus, users who want to be CHs send or receive the discovery beacon via the broadcasted resources. Figure 7-5 illustrates the signalling steps for the major discovery process. The main advantage of this discovery approach is the extremely low signalling overhead compared to other discovery methods. BS allocates resources for each CH and plays an important role in transmission format selection for each cluster (e.g., mode selection of multi-antenna transmission, modulation scheme and coding), mode selection, power control and scheduling. + +Minor discovery: + +Here the signalling procedure employs a direct discovery based on the steps indicated in Figures 7-6 and 7-7. CHs broadcast a discovery signal for CMs discovery. CMs respond to the discovery signal and then exchange the identities with the CH. + +![Figure 7-5: Major discovery signalling steps. The diagram shows three sequential steps of a wireless communication process. Step (1) 'Cell searching – CH scheduling' depicts a base station (BS) tower with upward and downward arrows next to it, and a larger red arrow pointing down towards an oval containing red and blue circles (nodes). Step (2) 'CHs announcement – CHs response' shows the BS tower with dashed lines radiating down to specific red nodes within a similar oval of nodes, with small upward and downward arrows. Step (3) 'Resources allocation' shows the BS tower with dashed lines radiating to all nodes in the oval, with a single downward arrow indicating resource distribution. A small code 'Q.5022(20)_F7-5' is at the bottom right.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Step (1) Cell searching – CH scheduling + +Step (2) CHs announcement – CHs response + +Step (3) Resources allocation + +Q.5022(20)\_F7-5 + +Figure 7-5: Major discovery signalling steps. The diagram shows three sequential steps of a wireless communication process. Step (1) 'Cell searching – CH scheduling' depicts a base station (BS) tower with upward and downward arrows next to it, and a larger red arrow pointing down towards an oval containing red and blue circles (nodes). Step (2) 'CHs announcement – CHs response' shows the BS tower with dashed lines radiating down to specific red nodes within a similar oval of nodes, with small upward and downward arrows. Step (3) 'Resources allocation' shows the BS tower with dashed lines radiating to all nodes in the oval, with a single downward arrow indicating resource distribution. A small code 'Q.5022(20)\_F7-5' is at the bottom right. + +**Figure 7-5 – Major discovery signalling steps** + +![Figure 7-6: Minor discovery signalling steps. This diagram illustrates three steps of a discovery process between a cluster head (CH) and member nodes (ME1). Step 1 shows 'Discovery messages - Join request' as red dashed arrows from ME1 nodes to the CH. Step 2 shows 'CM Response' as blue dashed arrows from the CH to ME1 nodes. Step 3 shows 'Resource allocation link quality' as red dashed arrows from the CH to ME1 nodes. The diagram includes icons for mobile devices and signal waves. A label 'Q.5022(20)_F7-6' is in the bottom right.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 7-6: Minor discovery signalling steps. This diagram illustrates three steps of a discovery process between a cluster head (CH) and member nodes (ME1). Step 1 shows 'Discovery messages - Join request' as red dashed arrows from ME1 nodes to the CH. Step 2 shows 'CM Response' as blue dashed arrows from the CH to ME1 nodes. Step 3 shows 'Resource allocation link quality' as red dashed arrows from the CH to ME1 nodes. The diagram includes icons for mobile devices and signal waves. A label 'Q.5022(20)\_F7-6' is in the bottom right. + +Figure 7-6 – Minor discovery signalling steps + +![Figure 7-7: Signalling diagram for minor discovery stage. This is a sequence diagram with two vertical lifelines labeled CH (Cluster Head) and CM (Cluster Member). The sequence of messages is: 1. A red arrow labeled 'D2D request' from CH to CM. 2. A blue arrow labeled 'D2D join response' from CM back to CH. 3. A red arrow labeled 'Connection setting' from CH to CM. A label 'Q.5022(20)_F7-7' is in the bottom right.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +Figure 7-7: Signalling diagram for minor discovery stage. This is a sequence diagram with two vertical lifelines labeled CH (Cluster Head) and CM (Cluster Member). The sequence of messages is: 1. A red arrow labeled 'D2D request' from CH to CM. 2. A blue arrow labeled 'D2D join response' from CM back to CH. 3. A red arrow labeled 'Connection setting' from CH to CM. A label 'Q.5022(20)\_F7-7' is in the bottom right. + +Figure 7-7 – Signalling diagram for minor discovery stage + +Figure 7-8 shows a flow chart that summarizes the multilevel hierarchical clustering (MLHC) operation. + +This stage consists of two phases, set-up phase and steady state phase. + +- Set-up phase: + +In the set-up phase, each node decides whether or not to be a cluster-head based on its residual energy and a globally pre-established percentage of cluster heads. The cluster head election process will be the nodes that elect themselves as a cluster head that broadcast an announcement message announcing themselves as cluster heads. + +The member nodes (non-cluster head nodes) receive the advertisement message from the cluster heads and may possibly receive multiple messages from multiple cluster heads. It selects only one cluster to join based on the signal strength of the received message from the corresponding cluster-head. + +To join a cluster, a member node prepares a join message and sends it to the selected cluster head in accordance with the time division multiple access (TDMA) schedule to know when to send it to the cluster head. The join message is a short message which contains the member node's identification number (ID) and the cluster head ID. Each CH receives messages from other non-CH nodes that are + +decided to join its cluster and thus clusters are formed. After that, each CH creates a TDMA schedule for the nodes in its cluster, allocating each node a time slot to use for sending data. + +The TDMA schedule is used to: + +- Avoid the collisions of data sent by member nodes, +- Put the member nodes in sleep mode (i.e., turn off the radio transmission components of the sensor node) for a long period of time, and in active mode (i.e., the radio transmission component of sensor is on) only during the transmission time. This will reduce the energy dissipation and save the sensor's battery. +- Each CH broadcasts its TDMA schedule and each member node receives the schedule of its CH. At this point the set-up phase is completed, and the next phase begins. All messages in this phase are broadcasted using carrier sense multiple access (CSMA) MAC protocol. + +#### **Three level hierarchy (MLHC)** + +In MLHC, the network operation is divided into rounds; each round consists of three stages with two phases for each stage as shown in Figure 7-8. Each stage corresponds to a clustering level. + +#### **Stage (1): The first level of clustering** + +This stage is the same as the first stage of MLHC. It consists of two phases, set-up phase and steady state phase. Similar to what happens in the first stage of MLHC, the nodes are organized into clusters with one CH for each cluster. The selection of cluster heads is done in the same way as in MLHC and the duration of the set-up phase and the steady state phase are the same as in MLHC. Each CH organizes the communication in its cluster and collects the sensed data from the member nodes. It also aggregates the collected data removing any redundancy in it. + +#### **Stage (2): The second level of clustering** + +In this stage, a second level of clustering is performed in the same manner as that of the second stage of MLHC. This stage consists of two phases, the set-up phase and the steady state phase. + +In the setup phase, the CHs of the first stage are grouped into clusters with a leader of each cluster ( $L_2$ -CH). The $L_2$ -CHs are chosen from the CHs of the first stage in the same manner as in MLHC. Each $L_2$ -CH creates a TDMA schedule for the CH nodes in its cluster to inform them when they can send their data. + +In the steady state phase, the CH nodes send their data to the $L_2$ -CHs based on the broadcasted TDMA schedule. $L_2$ -CHs receive the data and aggregate it to remove any redundancy. + +#### **Stage (3): The third level of clustering** + +In this stage, a third clustering is performed between $L_2$ -CHs of the second stage. $L_2$ -CHs do not send their data directly to the base station but they elect some of them known as the third level cluster heads and denoted as $L_3$ -CHs. $L_2$ -CHs are organized into clusters with a coordinator for each cluster ( $L_3$ -CH). The $L_3$ -CHs are responsible for collecting data from the $L_2$ -CHs and sending it to the base station. + +The third level of clustering achieves energy reduction as the distance to the base station is reduced and the number of nodes sent to the base station is reduced. This stage is like other stages, consisting of two phases, i.e., the set-up phase and steady state phase. + +In the set-up phase, the third level of clusters is constructed, and the $L_3$ -CHs are chosen. The election of $L_3$ -CHs is based on the residual energy of each $L_2$ -CH node, the distance to the base station and the pre-established percentage of the $L_3$ -CHs as will be discussed. In the steady-state phase, each $L_2$ -CH node sends its aggregated data to the corresponding $L_3$ -CH based on the allocated TDMA schedule that each one sends during its allocated time slot. $L_3$ -CHs receive data from $L_2$ -CHs and + +depending on the application of the network, L3-CHs may aggregate the received data if it contains any redundancy to conserve more energy. Finally, L3-CHs send their data directly to the base station. + +![Flow chart of MLHC operation. The process starts with 'Start round' and branches based on whether 'Node i' is a cluster head. It details the message exchanges for cluster formation and data aggregation, leading to 'End round'.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +``` + +graph TD + Start([Start round]) --> NodeCH{Node i cluster head?} + NodeCH -- Yes --> BroadcastAnn1[Broadcast an announcement message] + NodeCH -- No --> WaitAd1[Wait for cluster head advertisement message] + BroadcastAnn1 -.-> WaitAd1 + BroadcastAnn1 --> WaitJoin1[Wait for join request message] + WaitAd1 --> SendJoin1[Send a join request message to the appropriate cluster head] + SendJoin1 -.-> WaitJoin1 + SendJoin1 --> SendData1[Send the sended data to the cluster head] + SendData1 -.-> Aggregate1[Receive data from the member nodes, aggregate and compress it.] + Aggregate1 --> PrimeCH{If cluster head is chosen to be prime cluster head} + PrimeCH -- Yes --> BroadcastAnn2[Broadcast an announcement message] + PrimeCH -- No --> WaitAd2[Wait for prime cluster head advertisement message] + BroadcastAnn2 -.-> WaitAd2 + BroadcastAnn2 --> WaitJoin2[Wait for join request message] + WaitAd2 --> SendJoin2[Send a join request message to the chosen prime cluster head] + SendJoin2 -.-> WaitJoin2 + SendJoin2 --> SendData2[Send the compressed aggregated data to the prime cluster head] + SendData2 -.-> SendBS[Receive data from the cluster head and send it to the base station.] + SendBS --> End([End round]) + SendData2 --> End + +``` + +Flow chart of MLHC operation. The process starts with 'Start round' and branches based on whether 'Node i' is a cluster head. It details the message exchanges for cluster formation and data aggregation, leading to 'End round'. + +Q.5022(20)\_F7-8 + +**Figure 7-8 – Flow chart of MLHC operation** + +## 7.5 Cluster formation in failure mode + +In failure mode, the vision is to maintain the cell operation without the BS. In order to achieve this vision an energy efficient multilevel clustering is employed. The cell is divided into clusters with a CH and CMs for each cluster and this is the first level of clustering. The network topology for this mode is illustrated in Figure 7-2. The communication inside clusters is out-band autonomous D2D type as CMs communicate with their CH using Wi-Fi direct. + +In order to maintain the cell operation, CHs must be able to communicate with the neighbouring cells. Not all CHs can communicate directly with the neighbouring cells because of the distance and thus the second level clustering is performed. + +A cluster is a group of several users with a CH that acts as the leader of the group. As the clusters are formed inside each cell, they are referred to as intra-cell clusters. All intra-cluster communications run over a WLAN in an unlicensed spectrum. In failure mode, cluster formation is achieved by users. The users switch to this mode only if they lose the control of BS due to failure or a catastrophic situation. + +In order to maintain the cell operation, a multi-level clustering is applied in this mode. The main reason for applying clustering multiple-times is to enable all nodes to communicate with the boundary + +nodes. The boundary nodes are nodes that are located at the cell boundary and can communicate directly with nodes in the neighbouring cells. + +The first level of clustering is formed based on the announced Wi-Fi direct specifications. Each Wi-Fi direct group represents a cluster and the group owner is the head of the cluster. Each CH receives the basic information of its CMs. This information contains the temporary mobile subscribe identity (M/S-TMSI), international mobile subscriber identity (IMSI) and the preferred payoff method. As a response, each CH that forms a schedule contains all member nodes in its cluster. The schedule contains the member node identification (CM-ID) allocated by the CH and other received data of the member nodes. CHs share their schedules and the downlink traffic with their CMs through broadcasting message. + +To set up connections with the neighbouring cells, the first level cluster heads should find their way to communicate directly with nodes in the neighbouring cells. Not all CHs can communicate directly with the neighbouring cells because of the distance. CHs go on a discovery stage to discover which ones are able to reach and communicate with the neighbouring cells. All CHs broadcast a message and wait for a response from the neighbouring cells. CHs that are able to reach to the neighbouring cells announce themselves as a boundary CHs (BCHs or CHLN) and those are the CHs of the last clustering stage (N). + +BCHs forms their clusters by broadcasting discovery messages for other first level CHs. CHs of the first level are able to receive the message of B-CHs, respond to the message and announce themselves as cluster heads of the clustering stage N-1 ( $CHL_{N-1}$ ). The procedure of forming clustering levels goes on until all CH can reach to BCHs and thus to the neighbouring cells. Figures 7-9 to 7-13 illustrate the formation of multi-level clustering in failure mode. + +![Diagram of first level cluster heads showing a central hexagonal cell shaded in light red containing 19 node icons. Surrounding this central cell are seven regions labeled C1, C2, C3, C4, C5, C6, and C7, each containing several node icons. The nodes are represented by small square icons with a blue screen. The diagram is bounded by lines radiating from the center to separate the neighboring cell regions.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Q.5022(20)\_F7-9 + +Diagram of first level cluster heads showing a central hexagonal cell shaded in light red containing 19 node icons. Surrounding this central cell are seven regions labeled C1, C2, C3, C4, C5, C6, and C7, each containing several node icons. The nodes are represented by small square icons with a blue screen. The diagram is bounded by lines radiating from the center to separate the neighboring cell regions. + +**Figure 7-9 – First level cluster heads** + +![Diagram of last level cluster heads (CH_LN) showing a central cluster of nodes with yellow cluster heads connected to external nodes.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +This diagram illustrates the last level of cluster heads ( $CH_{LN}$ ). A central light blue hexagonal area contains numerous small blue square nodes. Several of these nodes are highlighted within yellow ovals, representing the last level cluster heads. Arrows point from these yellow ovals to small black square icons located outside the hexagonal boundary. The entire structure is overlaid on a larger hexagonal grid defined by lines labeled $C1$ through $C7$ . A small text label $Q.5022(20)_F7-10$ is located in the bottom right corner. + +Diagram of last level cluster heads (CH\_LN) showing a central cluster of nodes with yellow cluster heads connected to external nodes. + +Figure 7-10 – Last level cluster heads ( $CH_{LN}$ ) + +![Diagram of (N-1) level cluster heads (CH_L(N-1)) showing a hierarchical clustering of nodes with yellow and orange cluster heads.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +This diagram shows the $(N-1)$ level of cluster heads ( $CH_{L(N-1)}$ ). It follows the same hexagonal grid structure as the previous diagram. The central area contains blue square nodes grouped into yellow ovals, which are further grouped into larger orange ovals. Arrows indicate a hierarchical relationship, pointing from the orange ovals to the yellow ovals, and from the yellow ovals to the external black square icons. A small text label $Q.5022(20)_F7-11$ is located in the bottom right corner. + +Diagram of (N-1) level cluster heads (CH\_L(N-1)) showing a hierarchical clustering of nodes with yellow and orange cluster heads. + +Figure 7-11 – $(N-1)$ level cluster heads ( $CH_{L(N-1)}$ ) + +![Diagram of multi-level clusters showing a deep hierarchy of clustering with yellow, orange, and purple cluster heads.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +This diagram depicts multi-level clusters. It uses the same hexagonal grid and node layout. The hierarchy is deeper, with blue square nodes being clustered into yellow ovals, which into orange ovals, and some orange ovals further clustered into purple ovals. Arrows show the flow of connections from the purple ovals down to the orange ovals, then to the yellow ovals, and finally to the external black square icons. A small text label $Q.5022(20)_F7-12$ is located in the bottom right corner. + +Diagram of multi-level clusters showing a deep hierarchy of clustering with yellow, orange, and purple cluster heads. + +Figure 7-12 – Multi-level clusters + +![Diagram of multi-level clusters with cluster head identifications. It shows a central area with nodes labeled CH13-0 through CH13-11 and CH12-0 through CH12-3. These nodes are grouped into seven clusters labeled C1 through C7. Each node is represented by a yellow circle containing a small icon of a device. Arrows indicate connections between nodes and cluster heads. The entire structure is surrounded by a light blue shaded area, and the outer boundary is marked by lines and labels C1 through C7. A small text 'Q.5022(20)_F7-13' is visible in the bottom right corner of the diagram area.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Diagram of multi-level clusters with cluster head identifications. It shows a central area with nodes labeled CH13-0 through CH13-11 and CH12-0 through CH12-3. These nodes are grouped into seven clusters labeled C1 through C7. Each node is represented by a yellow circle containing a small icon of a device. Arrows indicate connections between nodes and cluster heads. The entire structure is surrounded by a light blue shaded area, and the outer boundary is marked by lines and labels C1 through C7. A small text 'Q.5022(20)\_F7-13' is visible in the bottom right corner of the diagram area. + +Figure 7-13 – Multi-level clusters with cluster head identifications + +## Appendix I + +### Use cases of D2D communications in IMT-2020 networks + +(This appendix does not form an integral part of this Recommendation.) + +Device-to-device (D2D) communication enables direct communication between proximate devices without relaying information to the base station (BS). Employing D2D communication in cellular networks achieves lots of benefits, including: + +- 1) D2D communication provides an offloading way for the cellular network, +- 2) Increases spectrum efficiency, +- 3) Achieves higher throughput, +- 4) Reduces the traffic congestion, and +- 5) Achieves better cell coverage. + +The proposed procedure is used to maintain the cell communication in case of the BS failure (due to either a technical problem or a catastrophic situation), thus the vision is to maintain the cell operation without the BS. If the cell users lose the control of the BS, they can switch to the D2D proposed procedure. The procedure employs the short range D2D communication as an alternative method to put the hole cell in communication with the neighbouring cells. Beside D2D communication, the cell nodes should be clustered more than once to enable reaching to the neighbouring cells. The main reason for applying clustering multi-times is to enable all nodes to communicate with the boundary nodes. The boundary nodes are nodes that are located at the cell boundary and can communicate directly with nodes in the neighbouring cells. Thus, in order to maintain the cell operation without BS, the proposed procedure employs multi-level cluster based D2D procedures. The idea behind multi-level clustering is to perform clustering between cluster heads of the first level and select some of them to be a second level cluster heads. Then the second level cluster heads select some of them to be a third level cluster heads and the procedure goes on until the final level cluster head. + +D2D communication achieves many benefits for the cellular system and thus it must be embedded to the existing 4G and the future 5G cellular systems. Behind the benefits, D2D communication can also be used to solve some problems associated with the cellular system; one of them is the BS failure. Employing multi-level clustering with D2D communication is an efficient way to maintain the inter-cell communication without BS. Multi-level clustering gives all nodes inside the cell communication paths to neighbouring cells and thus can perform all required communication processes. + +In case of catastrophic situation, the proposed procedure is an efficient way to preserve the cell communication. The worst case is the failure of the BS and those of all neighbouring cells, in this situation the proposed procedure does not help. The best case for employing the proposed procedure is the BS failure due to a technical problem or a regional catastrophic situation with all BSs of neighbouring cells in operation. + +## Appendix II + +## Gap analysis about D2D communications in related SDOs + +(This appendix does not form an integral part of this Recommendation.) + +| No. | SDOs | Title | Status | Analysis results | +|-----|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | ITU-R M.2083 | Framework and overall objectives of the future development of IMT for 2020 and beyond, Sep. 2015 | Published, in force | This Recommendation states that by 2020, the first commercial release of fifth generation cellular system (5G) will be launched according to the road map of the International Telecommunication Union (ITU) road map for the International Mobile Telecommunications-2020 system (IMT-2020). | +| 2 | ITU-R M.2410-0 | Minimum requirements related to technical performance for IMT-2020 radio interface(s), Nov. 2017 | Published, in force | New features and services that cover the needs of market segments and verticals. Far from the traditional services provided by the current cellular systems, 5G will introduce new types of services and applications with the developed new radio (NR) | +| 3 | 3GPP TS 22.261, | Service requirements for next generation new services and markets; Stage 1, Release 15, August 2016 | Published, in force | The 3rd Generation Partnership Project (3GPP) in this release show the mean services and roadmap for the first 5G release. | +| 4 | 3GPP TS 27.502 | Procedures for the 5G System, 2017 | Published, in force | 3GPP launched the Study on New Services and Markets Technology Enablers project (SMARTER), in 2015, to define and develop high level use cases and services of 5G system that meet the market demands. Moreover, SMARTER is expected to define the main features and requirements for each use case scenario. The work of SMARTER project is included in release 14 and 15. The 3GPP roadmap of 5G systems includes four main releases including release 13, 14, 15 and release 16. Each release contains different phases that are merged at the final stage of each release. Release 14 has been frozen by the end of the last year, while release 15 is going to be frozen by the end of this year completing the first phase of 5G. | +| 5 | ISO/CD 17515-2 | Intelligent transport systems – Communications access for land mobiles (CALM) – Evolved universal terrestrial radio access network (E-UTRAN) – Part 2: Device to device communications (D2D) | Under development | Device to device communications (D2D) | + +## Bibliography + +- [b-ITU-T Y.3011] Recommendation ITU-T Y.3011 (2012), *Framework of network virtualization for future networks.* +- [b-ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking.* + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca8534ea82db909550616c11cce76de5f0f71bb1 --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da2f7572e954b15c35d8d1a8ad7906a5bd50a5e1aafdfb953eb41283f1aa89de +size 21745 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d8deae6031c18707104a329a7eae044811bbb4b --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f418e2fcf77b057e807e60d0a0a741dd98ab9ee337764072def10cd9ce79d647 +size 5986 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d22d6273fe3ae917d37f5b182d2415b171f9a96 --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01f3fdc59f16503b88288fb15387f441ef1f7f07647e4d084a1253ffc8ed1858 +size 21475 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71fca40137b26b5a21a7838462932c071bae9c44 --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26ae279f4a20fedb44e63dee67f7a7a1f5070732b15bafb579d704133d23b612 +size 17153 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3be2421e2c8b4b9c576a620e6da6842a6e02773b --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:add5e6e8c70e02133985e234d54ba0777ab1086702d3676ff18ff02ecdd4305a +size 19220 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c56db65f5f3c0dc47a1d13d203a1d4af69ac2577 --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ada9ab331e325fddb46c0a65f77411b32a6c4cd008431a0c3cc28d28ec8a85d +size 22351 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67434fa034806e6c649b99500b0513f905288f52 --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2d7acf0f62a2487c15ed537f8ecc5c401991dd661c6fc1ca582c93f1216bbe9 +size 18591 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6fe09abc46db3e6c9b7a4789063834784a64f37 --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d80c444e3045d6fb75f7352b611b3fffc02b614859d8bc34dad6c0b0d3fc839d +size 17767 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a08f7b64f68b469e600ca32d9d8e282a94c2a7f --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bba95ebbcf538028f3ed88508c09a93f1895cdf9a4f005647064945b6dcd8bf9 +size 22351 diff --git a/marked/Q/T-REC-Q.5024-202202-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ed65311b415c7ae29521a4bc7b7369f06132fda --- /dev/null +++ b/marked/Q/T-REC-Q.5024-202202-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93e725d92960602ebcaee0b58771f47f24a1613fc4908bf44fa4e034dd03a349 +size 39238 diff --git a/marked/Q/T-REC-Q.5028-202312-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5028-202312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e2d8f0f5c00d6830dcd2f80e0781b520610546c4 --- /dev/null +++ b/marked/Q/T-REC-Q.5028-202312-I_PDF-E/raw.md @@ -0,0 +1,614 @@ + + +# Recommendation**ITU-T Q.5028 (12/2023)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for IMT-2020 – +Protocols for IMT-2020 + +--- + +## **Data management interfaces for intelligent edge computing-based smart agriculture service** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 | +| Protocols for IMT-2020 | Q.5020-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.5028 + +# Data management interfaces for intelligent edge computing-based smart agriculture service + +## Summary + +Recommendation ITU-T Q.5028 provides an overview of the intelligent edge computing-based smart agriculture service and specifies its data management interfaces, including network function interfaces and data processing interfaces. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.5028 | 2023-12-14 | 11 | 11.1002/1000/15731 | + +## Keywords + +Agriculture, data management, edge. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 1 | +| 6 Introduction..... | 2 | +| 7 Data management interfaces for intelligent edge computing-based smart agriculture service..... | 3 | +| 7.1 Interfaces for network functions..... | 3 | +| 7.2 Data resources ..... | 3 | +| 7.3 Interfaces for data processing ..... | 12 | +| Bibliography..... | 17 | + + + +###### Recommendation ITU-T Q.5028 + +## Data management interfaces for intelligent edge computing-based smart agriculture service + +# 1 Scope + +This Recommendation addresses data management interfaces for intelligent edge computing-based smart agriculture service including the following: + +- Overview of the intelligent edge computing-based smart agriculture service; +- Data management interfaces for the intelligent edge computing-based smart agriculture service. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T Q.5001] Recommendation ITU-T Q.5001 (2018), *Signalling requirements and architecture of intelligent edge computing*. + +[IETF RFC 7159] IETF RFC 7159 (2014), *The JavaScript Object Notation (JSON) Data Interchange Format*. + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|------|-----------------------------------| +| AI | Artificial Intelligence | +| API | Application Programming Interface | +| EC | Electrical Conductivity | +| IEC | Intelligent Edge Computing | +| JSON | JavaScript object notation | +| pH | Potential of Hydrogen | + +# 5 Conventions + +Resource elements in clause 7.1 and the fields of the messages in clause 7.2 are encoded in JavaScript object notation (JSON) [IETF RFC 7159]. + +The grammar used in representing objects defined in this Recommendation is as follows: + +- "STRING" and "NUMBER" types are used to indicate string and number, respectively; + +- An array of collective values are enclosed in brackets "[ ]" with values separated by commas " , "; +- Selective options are separated by a vertical bar " | "; +- "MIN" means minimum value, while "MAX" means maximum value. + +# 6 Introduction + +Smart agriculture has improved productivity by controlling the growing environment of crops and analysing data collected during crop growth. Recently, the demand for data-based smart agriculture services has been increasing, as the importance of converged agricultural services (farm autonomous control, pest control, etc.) based on big data is emphasized. Accordingly, the data generated and consumed by Internet of things devices in the smart agriculture have been increasing exponentially. + +With the development of data and artificial intelligence (AI) technologies, it has become clear that smart agriculture could benefit from the edge-cloud platform service, which provides a low-delay service from edge servers, and a powerful computational service from cloud servers. Figure 6-1 shows the concept of edge-based smart agriculture service. + +![Figure 6-1: Concept of edge-based smart agriculture service. The diagram shows a central 'Smart agriculture system' box containing a 'Controller', 'Sensors' (temp, CO2, power, humid., rain, wind), 'Actuators' (fan, heater, window, light, irrigator, valve), and 'Equipment/machinery' (camera, feeder, tractor, drone, milking parlor, milking system, spreader, injector). This system is connected to an 'Edge server', which is in turn connected to a 'Cloud'. Two other 'Edge server' boxes are shown, each connected to a 'Smart agriculture system' box. A legend at the bottom indicates that light grey boxes represent 'Edge server' and dark grey boxes represent 'Terminal entity'. The diagram is labeled Q.5028(23).](35a7554182eb055209552843f341a1ae_img.jpg) + +Figure 6-1: Concept of edge-based smart agriculture service. The diagram shows a central 'Smart agriculture system' box containing a 'Controller', 'Sensors' (temp, CO2, power, humid., rain, wind), 'Actuators' (fan, heater, window, light, irrigator, valve), and 'Equipment/machinery' (camera, feeder, tractor, drone, milking parlor, milking system, spreader, injector). This system is connected to an 'Edge server', which is in turn connected to a 'Cloud'. Two other 'Edge server' boxes are shown, each connected to a 'Smart agriculture system' box. A legend at the bottom indicates that light grey boxes represent 'Edge server' and dark grey boxes represent 'Terminal entity'. The diagram is labeled Q.5028(23). + +Figure 6-1 – Concept of edge-based smart agriculture service + +As the well-defined edge-cloud infrastructure, the intelligent edge computing (IEC) architecture [ITU-T Q.5001] defines signalling architecture and reference points. Figure 6-2 highlights the reference points used in this Recommendation. This Recommendation defines data management application programming interfaces (APIs) for IEC-based smart agriculture. + +![Figure 6-2: Reference points of IEC [ITU-T Q.5001] used in this Recommendation. The diagram shows the architecture of Intelligent Edge Computing (IEC) involving a Terminal entity (TE), an Edge networking entity, an Intelligent computing entity, an Edge gateway entity, Big data analytics in the cloud, and the IEC itself. Reference points are labeled as Dx (data flow), Cx (control flow), and Ux (model update).](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Dx – Identifier for data flow reference points    Cx – Identifier for control flow reference points    Ux – Identifier for model update reference points    Q.5028(23) + +Figure 6-2: Reference points of IEC [ITU-T Q.5001] used in this Recommendation. The diagram shows the architecture of Intelligent Edge Computing (IEC) involving a Terminal entity (TE), an Edge networking entity, an Intelligent computing entity, an Edge gateway entity, Big data analytics in the cloud, and the IEC itself. Reference points are labeled as Dx (data flow), Cx (control flow), and Ux (model update). + +**Figure 6-2 – Reference points of IEC [ITU-T Q.5001] used in this Recommendation** + +# 7 Data management interfaces for intelligent edge computing-based smart agriculture service + +For extensibility, APIs follow representational state transfer (REST) architecture [b-REST] and payloads are encoded in JavaScript object notation (JSON) [IETF RFC 7159]. + +## 7.1 Interfaces for network functions + +The interfaces for network functions conform to [ITU-T Q.5001]. + +## 7.2 Data resources + +### 7.2.1 Temperature + +Temperature is an essential data attribute for growing crops. Table 7-1 shows information describing temperature data. + +**Table 7-1 – Temperature data resource element** + +| Keyword | Type | Description | +|-----------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| temperature-value | NUMBER | temperature-value is a value indicating the temperature. It is measured by the temperature sensor. | +| temperature-units | STRING | temperature-units indicates the unit of the temperature value. The unit may be represented by 'C' indicating Celsius, 'F' indicating Fahrenheit, and 'K' indicating absolute temperature. | +| temperature-range | NUMBER (MIN, MAX) | temperature-range indicates effective range of temperature values. By specifying an effective range of temperature, unnecessary data collection and transmission can be avoided. | +| temperature-precision | NUMBER | temperature-precision indicates precision of the temperature value. It can be used in conjunction with ' temperature-range '. For example, if ' temperature-range ' is (0, 10) and ' temperature-precision ' is 1, valid temperature data can be expressed as an integer. | + +**Table 7-1 – Temperature data resource element** + +| Keyword | Type | Description | +|--------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| temperature-margin | NUMBER | temperature-margin indicates the error range of the temperature value. It can be used in conjunction with ' temperature-range '. For example, if ' temperature-range ' is (0, 10) and ' temperature-margin ' is 2, the range of valid measurements may be (-2, 12). | + +### 7.2.2 Humidity + +As temperature, humidity is an essential data attribute for growing crops. Table 7-2 shows information describing humidity data. + +**Table 7-2 – Humidity data resource element** + +| Keyword | Type | Description | +|--------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| humidity-value | NUMBER | humidity-value is a value indicating the humidity. It is measured by the humidity sensor. | +| humidity-units | STRING | humidity-units indicates the unit of the humidity value. The unit may be represented by '%'. | +| humidity-range | NUMBER (MIN, MAX) | humidity-range indicates effective range of humidity values. By specifying an effective range of humidity, unnecessary data collection and transmission can be avoided. | +| humidity-precision | NUMBER | humidity-precision indicates precision of the humidity value. It can be used in conjunction with ' humidity-range '. For example, if ' humidity-range ' is (0, 10) and ' humidity-precision ' is 1, valid humidity data can be expressed as an integer from 1 to 9. | +| humidity-margin | NUMBER | humidity-margin indicates the error range of the humidity value. It can be used in conjunction with ' humidity-range '. For example, if ' humidity-range ' is (0, 10) and ' humidity-margin ' is 2, the range of valid measurements may be (-2, 12). | + +### 7.2.3 Carbon dioxide + +Carbon dioxide (CO2) is a data attribute highly related to the photosynthesis of crops. Table 7-3 shows information describing carbon dioxide data. + +**Table 7-3 – Carbon dioxide data resource element** + +| Keyword | Type | Description | +|----------------------|--------|--------------------------------------------------------------------------------------------------------------------| +| carbon-dioxide-value | NUMBER | carbon-dioxide-value is a value indicating the carbon dioxide. It is measured by the carbon dioxide sensor. | +| carbon-dioxide-units | STRING | carbon-dioxide-units indicates the unit of the carbon dioxide value. The unit may be represented by 'ppm'. | + +**Table 7-3 – Carbon dioxide data resource element** + +| Keyword | Type | Description | +|--------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carbon-dioxide-range | NUMBER (MIN, MAX) | carbon-dioxide-range indicates effective range of carbon dioxide values. By specifying an effective range of carbon dioxide, unnecessary data collection and transmission can be avoided. | +| carbon-dioxide-precision | NUMBER | carbon-dioxide-precision indicates precision of the carbon dioxide value. It can be used in conjunction with ' carbon-dioxide-range '. For example, if ' carbon-dioxide-range ' is (0, 10) and ' carbon-dioxide-precision ' is 1, valid carbon dioxide data can be expressed as an integer from 1 to 9. | +| carbon-dioxide-margin | NUMBER | carbon-dioxide-margin indicates the error range of the carbon dioxide value. It can be used in conjunction with ' carbon-dioxide-range '. For example, if ' carbon-dioxide-range ' is (0, 10) and ' carbon-dioxide-margin ' is 2, the range of valid measurements may be (-2, 12). | + +### 7.2.4 Insolation + +Insolation can be used to presume the amount of crop's photosynthesis. Table 7-4 shows information describing insolation data. + +**Table 7-4 – Insolation data resource element** + +| Keyword | Type | Description | +|----------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| insolation-value | NUMBER | insolation-value is a value indicating the insolation. It is measured by the insolation sensor. | +| insolation-units | STRING | insolation-units indicates the unit of the insolation value. The unit may be represented by one of the following: 'W/m 2 ', 'kcal/m 2 ', 'cal/cm 2 /min', or 'ly/min'. | +| insolation-range | NUMBER (MIN, MAX) | insolation-range indicates effective range of insolation values. By specifying an effective range of insolation, unnecessary data collection and transmission can be avoided. | +| insolation-precision | NUMBER | insolation-precision indicates precision of the insolation value. It can be used in conjunction with ' insolation-range '. For example, if ' insolation-range ' is (0, 10) and ' insolation-precision ' is 1, valid insolation data can be expressed as an integer from 1 to 9. | +| insolation-margin | NUMBER | insolation-margin indicates the error range of the insolation value. It can be used in conjunction with ' insolation-range '. For example, if ' insolation-range ' is (0, 10) and ' insolation-margin ' is 2, the range of valid measurements may be (-2, 12). | + +### 7.2.5 Wind direction + +Wind direction is the direction in which the air is blowing. Table 7-5 shows information describing wind direction data. + +**Table 7-5 – Wind direction data resource element** + +| Keyword | Type | Description | +|--------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| wind-direction-value | NUMBER | wind-direction-value is a value indicating the wind direction. It is measured by the wind direction sensor. | +| wind-direction-units | STRING | wind-direction-units indicates the unit of the wind direction value. The unit may be represented by 360 degrees clockwise. For example, wind direction may be represented 360 degrees for north, 90 degrees for east, 180 degrees for south, and 270 degrees for west | +| wind-direction-range | NUMBER (MIN, MAX) | wind-direction-range indicates effective range of wind direction values. By specifying an effective range of wind direction, unnecessary data collection and transmission can be avoided. | +| wind-direction-precision | NUMBER | wind-direction-precision indicates precision of the wind direction value. It can be used in conjunction with ' wind-direction-range '. For example, if ' wind-direction-range ' is (0, 10) and ' wind-direction-precision ' is 1, valid wind direction data can be expressed as an integer from 1 to 9. | +| wind-direction-margin | NUMBER | wind-direction-margin indicates the error range of the wind direction value. It can be used in conjunction with ' wind-direction-range '. For example, if ' wind-direction-range ' is (0, 10) and ' wind-direction-margin ' is 2, the range of valid measurements may be (-2, 12). | + +### 7.2.6 Wind speed + +Wind speed is the speed at which the air is blowing. Table 7-6 shows information describing wind speed data. + +**Table 7-6 – Wind speed data resource element** + +| Keyword | Type | Description | +|----------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| wind-speed-value | NUMBER | wind-speed-value is a value indicating the wind speed. It is measured by the wind speed sensor. | +| wind-speed-units | STRING | wind-speed-units indicates the unit of the wind speed value. The unit may be represented by 'm/s' or 'Knot'. | +| wind-speed-range | NUMBER (MIN, MAX) | wind-speed-range indicates effective range of wind speed values. By specifying an effective range of wind speed, unnecessary data collection and transmission can be avoided. | +| wind-speed-precision | NUMBER | wind-speed-precision indicates precision of the wind speed value. It can be used in conjunction | + +**Table 7-6 – Wind speed data resource element** + +| Keyword | Type | Description | +|-------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | with ' wind-speed-range '. For example, if ' wind-speed-range ' is (0, 10) and ' wind-speed-precision ' is 1, valid wind speed data can be expressed as an integer from 1 to 9. | +| wind-speed-margin | NUMBER | wind-speed-margin indicates the error range of the wind speed value. It can be used in conjunction with ' wind-speed-range '. For example, if ' wind-speed-range ' is (0, 10) and ' wind-speed-margin ' is 2, the range of valid measurements may be (-2, 12). | + +### 7.2.7 Rain detection + +Rain detection indicates whether precipitation events such as rainfall or snowfall have taken place. Table 7-7 shows information describing rain detection data. + +**Table 7-7 – Rain detection data resource element** + +| Keyword | Type | Description | +|----------------------|--------|--------------------------------------------------------------------------------------------------------------------------| +| rain-detection-value | NUMBER | rain-detection-value is a value indicating whether rain is detected. It is measured by the rain detection sensor. | + +### 7.2.8 Soil moisture tension + +Soil moisture tension presents the degree of moisture absorption of the soil. Table 7-8 shows information describing soil moisture tension data. + +**Table 7-8 – Soil moisture tension data resource element** + +| Keyword | Type | Description | +|---------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| soil-moisture-tension-value | NUMBER | soil-moisture-tension-value is a value indicating the soil moisture tension. It is measured by the soil moisture tension sensor. | +| soil-moisture-tension-units | STRING | soil-moisture-tension-units indicates the unit of the soil moisture tension value. The unit may be represented by 'kPA' or 'PA'. | +| soil-moisture-tension-range | NUMBER (MIN, MAX) | soil-moisture-tension-range indicates the effective range of soil moisture tension values. By specifying an effective range of soil moisture tension, unnecessary data collection and transmission can be avoided. | +| soil-moisture-tension-precision | NUMBER | soil-moisture-tension-precision indicates precision of the soil moisture tension value. It can be used in conjunction with ' soil-moisture-tension-range '. For example, if ' soil-moisture-tension-range ' is (0, 10) and ' soil-moisture-tension-precision ' is 1, valid soil moisture tension data can be expressed as an integer from 1 to 9. | + +**Table 7-8 – Soil moisture tension data resource element** + +| Keyword | Type | Description | +|------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| soil-moisture-tension-margin | NUMBER | soil-moisture-tension-margin indicates the error range of the soil moisture tension value. It can be used in conjunction with ' soil-moisture-tension-range '. For example, if ' soil-moisture-tension-range ' is (0, 10) and ' soil-moisture-tension-margin ' is 2, the range of valid measurements may be (–2, 12). | + +### 7.2.9 Electrical conductivity + +Electrical conductivity (EC) indicates a measure of a material's ability to carry an electrical current. Table 7-9 shows information describing electrical conductivity data. + +**Table 7-9 – Electrical conductivity data resource element** + +| Keyword | Type | Description | +|-----------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| electrical-conductivity-value | NUMBER | electrical-conductivity-value is a value indicating the electrical conductivity. It is measured by the electrical conductivity sensor. | +| electrical-conductivity-units | STRING | electrical-conductivity-units indicates the unit of the electrical conductivity value. The unit may be represented by 'mS/cm' or 'dS/m'. | +| electrical-conductivity-range | NUMBER (MIN, MAX) | electrical-conductivity-range indicates effective range of electrical conductivity values. By specifying an effective range of electrical conductivity, unnecessary data collection and transmission can be avoided. | +| electrical-conductivity-precision | NUMBER | electrical-conductivity-precision indicates precision of the electrical conductivity value. It can be used in conjunction with ' electrical-conductivity-range '. For example, if ' electrical-conductivity-range ' is (0, 10) and ' electrical-conductivity-precision ' is 1, valid electrical conductivity data can be expressed as an integer from 1 to 9. | +| electrical-conductivity-margin | NUMBER | electrical-conductivity-margin indicates the error range of the electrical conductivity value. It can be used in conjunction with ' electrical-conductivity-range '. For example, if ' electrical-conductivity-range ' is (0, 10) and ' electrical-conductivity-margin ' is 2, the range of valid measurements may be (–2, 12). | + +### 7.2.10 Potential of hydrogen + +Potential of Hydrogen (pH) is a measure of the hydrogen ion concentration in an aqueous solution. Table 7-10 shows information describing potential of hydrogen data. + +**Table 7-10 – Potential of hydrogen data resource element** + +| Keyword | Type | Description | +|---------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| potential-of-hydrogen-value | NUMBER | potential-of-hydrogen-value is a value indicating the potential of hydrogen It is measured by the potential of hydrogen sensor. | +| potential-of-hydrogen-units | STRING | potential-of-hydrogen-units indicates the unit of the potential of hydrogen value. The unit may be represented by 'kPA' or 'PA'. | +| potential-of-hydrogen-range | NUMBER (MIN, MAX) | potential-of-hydrogen-range indicates effective range of potential of hydrogen values. By specifying an effective range of potential of hydrogen, unnecessary data collection and transmission can be avoided. | +| potential-of-hydrogen-precision | NUMBER | potential-of-hydrogen-precision indicates the precision of the potential of hydrogen value. It can be used in conjunction with ' potential-of-hydrogen-range '. For example, if ' potential-of-hydrogen-range ' is (0, 10) and ' potential-of-hydrogen-precision ' is 1, valid potential of hydrogen data can be expressed as an integer from 1 to 9. | +| potential-of-hydrogen-margin | NUMBER | potential-of-hydrogen-margin indicates the error range of the potential of hydrogen value. It can be used in conjunction with ' potential-of-hydrogen-range '. For example, if ' potential-of-hydrogen-range ' is (0, 10) and ' potential-of-hydrogen-margin ' is 2, the range of valid measurements may be (–2, 12). | + +### 7.2.11 Farm + +Farm provides the information of a farm. Table 7-11 shows information describing farm data. + +**Table 7-11 – Farm data resource element** + +| Keyword | Type | Description | +|------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| id-of-farm | STRING | id-of-farm is a value identifying the farm. id-of-farm shall not be modified throughout its lifecycle. | +| name-of-farm | STRING | name-of-farm allows users to intuitively identify the farm. | +| ctime-of-farm | STRING | ctime-of-farm is the time when the farm data is created by registering a farm with smart greenhouse service, and shall not be modified throughout its lifecycle. | +| mtime-of-farm | STRING | mtime-of-farm is the time when the farm data is modified and shall be automatically updated. | +| address-of-farm | STRING | address-of-farm allows users to intuitively identify the farm. | +| location-of-farm | STRING | location-of-farm indicates the geographic location of the farm. The location of a farm is important to identify the farm because geographical location is closely related to the climate conditions affecting | + +**Table 7-11 – Farm data resource element** + +| Keyword | Type | Description | +|--------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | crop growth. location-of-farm can be represented by various types of value such as global navigation satellite system (GNSS) coordinates, and shall include the type of value and unit. | +| area-of-farm | STRING | area-of-farm indicates the area of the farm. area-of-farm can be represented by various types of value such as acre or square meter and shall include value, unit and error range. | + +### 7.2.12 Greenhouse + +Greenhouse provides the information of a smart greenhouse. Table 7-12 shows information describing greenhouse data. + +**Table 7-12 – Greenhouse data resource element** + +| Keyword | Type | Description | +|------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| id-of-greenhouse | STRING | id-of-greenhouse is a value identifying the greenhouse. id-of-greenhouse shall not be modified throughout its lifecycle | +| name-of-greenhouse | STRING | name-of-greenhouse allows users to intuitively identify the greenhouse. | +| ctime-of-greenhouse | STRING | ctime-of-greenhouse is the time when the greenhouse data is created by registering a greenhouse with smart greenhouse service and shall not be modified throughout its lifecycle. | +| mtime-of-greenhouse | STRING | mtime-of-greenhouse is the time when the greenhouse data is modified and shall be automatically updated. | +| location-of-greenhouse | STRING | location-of-greenhouse indicates the geographic location of the greenhouse. location-of-greenhouse can be represented by various types of value such as GNSS coordinates and shall include the type of value and unit. | +| size-of-greenhouse | STRING | size-of-greenhouse indicates the width, height and length of the greenhouse. size-of-greenhouse can be represented by various types of values such as yard (yd) or meter (m) and shall include value, unit and error range. | +| type-of-greenhouse | STRING | type-of-greenhouse indicates human-readable information about shape, medium, irrigation, heating system, crop, description of cropping season and utilization status of the greenhouse. | + +### 7.2.13 Device + +Device provides the information of a device that can be installed in a smart greenhouse. Table 7-13 shows information describing device data. + +**Table 7-13 – Device data resource element** + +| Keyword | Type | Description | +|------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| id-of-device | STRING | id-of-device is a value identifying the device. id-of-device shall not be modified throughout its lifecycle. | +| name-of-device | STRING | name-of-device allows users to intuitively identify the device. | +| ctime-of-device | STRING | ctime-of-device is the time when the device data is created by registering a device with smart greenhouse service and shall not be modified throughout its lifecycle. | +| mtime-of-device | STRING | mtime-of-device is the time when the device data is modified and shall be automatically updated. | +| type-of-device | STRING | type-of-device indicates the usage of the device, and multiple device data can have the same type. | +| model-of-device | STRING | model-of-device indicates the model name of the device. Multiple device data can have the same model name. | +| code-of-device | STRING | code-of-device indicates the compatibility of the device. Multiple device data can have the same code. | +| manufacturer-of-device | STRING | manufacturer-of-device indicates human-readable name for easily identifying the manufacturer of the device and includes name, website Internet address, etc. | + +### 7.2.14 Device installation + +Device installation provides the information about a device installed and operated in a smart greenhouse. A device can be installed at various locations in a smart greenhouse for helping crop growth or collecting environmental status. To control the device or utilize data from the device, it is important to be aware of the information regarding the installation. Table 7-14 shows information describing device installation data. + +**Table 7-14 – Device installation data resource element** + +| Keyword | Type | Description | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| id-of-device-install | STRING | id-of-device-install is a value identifying the installed device. id-of-device-install shall not be modified throughout its lifecycle. | +| name-of-device-install | STRING | name-of-device-install allows users to intuitively identify the installed device. | +| ctime-of-device-install | STRING | ctime-of-device-install is the time when the device installation data is created by registering a device with smart greenhouse service. It shall not be modified throughout its lifecycle. | +| mtime-of-device-install | STRING | mtime-of-device-install is the time when the device installation data is modified. It shall be automatically updated. | + +**Table 7-14 – Device installation data resource element** + +| Keyword | Type | Description | +|----------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| location-of-device-install | STRING | location-of-device-install indicates the location of the installed device represented by various types of values such as GNSS coordinates, or an appropriate exchange format regarding GNSS coordinates. It shall include the type of value and unit. | +| date-of-device-install | STRING | date-of-device-install is a value indicating the date of device installation. | + +### 7.2.15 User + +User provides the information about the user of crop-growth related data. Table 7-15 shows information describing user data. + +**Table 7-15 – User data resource element** + +| Keyword | Type | Description | +|---------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| id-of-user | STRING | id-of-user is a value identifying the user. id-of-user shall not be modified throughout its lifecycle. | +| name-of-user | STRING | name-of-user allows users to intuitively identify the user. | +| ctime-of-user | STRING | ctime-of-user is the time when the user data is created by registering a device with smart greenhouse service and shall not be modified throughout its lifecycle. | +| mtime-of-user | STRING | mtime-of-user is the time when the user data is modified and shall be automatically updated. | +| group-of-user | STRING | group-of-user indicates the group to which the user belongs, and includes group identifier, group authority, etc. | + +## 7.3 Interfaces for data processing + +This clause describes the APIs for data processing including creating, retrieving, updating, and deleting data to be used in the reference point Da specified in [ITU-T Q.5001]. In the body of HTTP request/response message, following notation is used for representing the requirements on the specific parameter. + +- m: mandatory; +- o: optional; +- c: conditional meaning that the use of the parameter depends on the context of the message usages. + +### 7.3.1 DataCreation + +DataCreation is used for posting data at the edge networking entity. Table 7-16 describes the syntax of the request message. + +**Table 7-16 – Request message syntax for DataCreation** + +| | | +|--------------------|--------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | POST | +| HTTP URI | http://[address of edge networking entity]:[port]/[name of smart agriculture service]/[version]/[type of event]/c | +| BODY | "timestamp" : NUMBER,
"device-id" : STRING,
"data-id" : NUMBER,
"data-type" : "STRING",
"data-value": DATA ELEMENT | + +- *timestamp* field indicates the time when the value is measured. The time when the value measured by the device reaches the system is mainly utilized. +- *device-id* field indicates identifiers of the sensor device that measures the value. It is possible to check which sensor the value was measured through the device identifier. That means the location of the value is measured can be estimated. +- *data-id* field indicates identifiers which is identifying each measurement value. +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. +- *data-value* field indicates data element, which is defined in clauses 7.2.1 to 7.2.10, corresponding data-type. + +Table 7-17 describes the syntax of the response for *DataCreation*. + +**Table 7-17 – Response message syntax for DataCreation** + +| | | +|---------------------------|-----------------| +| HTTP Response code | rsp_code | +| BODY | None | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails. + +### 7.3.2 DataRetrieval + +DataRetrieval is used for retrieving data at the edge networking entity. Table 7-18 describes the syntax of the request message for getting entire data resources. + +**Table 7-18 – Request message syntax for DataRetrieval for getting entire data resources** + +| | | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | GET | +| HTTP URI | http://[address of edge networking entity]:[port]/[name of smart agriculture service]/[version]/[type of event]/r/[data-type] | +| PARAMETERS | "data-type" : STRING | + +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. + +Table 7-19 describes the syntax of the response for *DataRetrieval* for getting specific data resource. + +**Table 7-19 – Request message syntax for DataRetrieval for Specific Data Resource** + +| | | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | GET | +| HTTP URI | http://[address of edge networking entity]:[port]/[name of smart agriculture service]/[version]/[type of event]/r/[data-type]/[device-id] | +| PARAMETERS | "device-id" : STRING,
"data-type" : STRING | + +- *device-id* field indicates identifiers of the sensor device that measures the data value. It is possible to check which sensor the data value was measured through the device identifier. That means the location where the data value is measured can be estimated. +- *data-type* field indicates the kinds of data, which are defined in clause 7.2. + +Table 7-20 describes the syntax of the response for *DataRetrieval*. + +**Table 7-20 – Response message syntax for DataRetrieval** + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------| +| HTTP Response code | rsp_code | +| BODY | "timestamp" : NUMBER,
"device-id" : STRING,
"data-id" : NUMBER,
"data-type" : STRING,
"data-value": DATA ELEMENT | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails; +- *timestamp* field indicates the time when the data value is measured. The time when the data value measured by the device reaches the system is mainly utilized. +- *device-id* field indicates identifiers of the sensor device that measures data value. It is possible to check which sensor the data value was measured through the device identifier. That means the location of the data value is measured can be estimated. +- *data-id* field indicates identifiers which is identifying each data value. +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. +- *data-value* field indicates data element, which is defined in clauses 7.2.1 to 7.2.10, corresponding to data-type. + +### 7.3.3 DataUpdate + +DataUpdate is used for updating data at the edge networking entity. Table 7-21 describes the syntax of the request message. + +**Table 7-21 – Request message syntax for DataUpdate** + +| | | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | PUT | +| HTTP URI | http:// [address of edge networking entity]: [port]/ [name of smart agriculture service]/ [version]/ [type of event]/u/ [data-id} | +| PARAMETERS | "data-id" : NUMBER | +| BODY | "timestamp" : NUMBER,
"data-value": DATA ELEMENT | + +- *data-id* field indicates identifiers which is identifying each data value. +- *timestamp* field indicates the time when the data value is measured. The time when the data value measured by the device reaches the system is mainly utilized. +- *data-value* field indicates data element, which is only supported for configuration data and defined in clauses 7.2.11 to 7.2.15, corresponding to data-type. + +Table 7-22 describes the syntax of the response for *DataUpdate*. + +**Table 7-22 – Response message syntax for DataUpdate** + +| | | +|---------------------------|-----------------| +| HTTP Response code | rsp_code | +| BODY | None | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails; + +### 7.3.4 DataDeletion + +DataDeletion is used for deleting data at the edge networking entity. Table 7-23 describes the syntax of the request message. + +**Table 7-23 – Request message syntax for DataDeletion** + +| | | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | POST | +| HTTP URI | http:// [address of edge networking entity]: [port]/ [name of smart agriculture service]/ [version]/ [type of event]/d/ [data-id] | +| BODY | "data-id" : NUMBER | + +- *data-id* field indicates identifiers which is identifying each data value. + +Table 7-24 describes the syntax of the response for *DataDeletion*. + +**Table 7-24 – Response message syntax for DataDeletion** + +| | | +|-------------------------------|-----------------| +| HTTP
Response code | rsp_code | +| BODY | None | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails. + +## Bibliography + +[b-REST] Fielding, R. (2000), *Architectural Styles and the Design of Network-based Software Architectures*, Doctoral Dissertation, University of California, Irvine, September. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99ea68044d79578ff9efeb788caf59b4cf8735cf --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79d0edd65f0543ba532ca33dab47c3bc9954d45b604389a135a97102ead85c59 +size 37723 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a6c1ccb1db0c3582e679992562f92386db9b270 --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29fae0e1a4a0ab18aca6e7c71b15f2420d4888d5d93c06d2e7bec236049b4047 +size 56072 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21d0d80d748813e6f5fd3f8c64e1ef01f1699908 --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f5abddc50e1915af73312cbfa9b5626de614f5ba4afd718a2bb2020732ed054 +size 35861 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ce0b6c89e8ee5a807cebb983755c3d45bf5759a --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c20178be344178a60814164ae68774355938d07a47c572e5ad4e08f104a67a91 +size 58524 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e00c74a1f491b06b609227165a3438641c1c93e --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd443fb3ed6e53271dd0f6323c351a433b9b0dd2f0d92948bf49ad52c18f28af +size 74782 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a5f7796c83ca4a2b5247c83ae17a3b66ac17737 --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d43ae1ddf3807f134b1b097de739ec93b6edc2a5846f1ff240dc4e3c9a4fa705 +size 35868 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/Q/T-REC-Q.522-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1a9e5903c1cd5e93b4410b4011d7882de04a82f --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51ad4a9e12d0f6fae91539a063ab017bdabd40a54bc51ac343617417e5c72e02 +size 9676 diff --git a/marked/Q/T-REC-Q.522-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.522-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..85b3caa37324b7a816053cc8c4bb698e332162aa --- /dev/null +++ b/marked/Q/T-REC-Q.522-198811-I_PDF-E/raw.md @@ -0,0 +1,736 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.522** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**DIGITAL EXCHANGES** + +--- + +**DIGITAL EXCHANGE CONNECTIONS, +SIGNALLING AND ANCILLARY FUNCTIONS** + +**ITU-T Recommendation Q.522** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation Q.522 was published in Fascicle VI.5 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **DIGITAL EXCHANGE CONNECTIONS, SIGNALLING AND ANCILLARY FUNCTIONS** + +## **1 General** + +This Recommendation applies to digital local, combined, transit and international exchanges for telephony in Integrated Digital Networks (IDN) and also to local, combined, transit, and international exchanges in an Integrated Services Digital Network (ISDN). The field of application of this Recommendation is more fully defined in Recommendation Q.500. + +## **2 Connections through an exchange** + +### **2.1 General** + +The characteristics of the connections detailed in this section refer to an established connection when it is made available to the users. + +An exchange must be able to provide originating, terminating and internal exchange connections between input and output interfaces for telephony and other services as required. It may also provide transit connections: + +- A connection (if any) between an incoming and an outgoing circuit at interfaces to other exchanges/networks is called a transit connection. +- A connection between channel(s) of a calling subscriber line at an interface for subscriber access and an outgoing circuit at an interface to other exchange/networks is called an originating connection. +- A connection between an incoming circuit at an interface to other exchange/networks and channel(s) of a called subscriber line at an interface for subscriber access is called a terminating connection. +- A connection between channels of two subscriber lines at interfaces for subscriber access is called an internal connection. + +An exchange must be able to provide bidirectional connections between input and output interfaces for telephony and other services as required. + +Also unidirectional connections may be required. + +### **2.2 Basic exchange connections** + +#### **2.2.1 General** + +The requirements in this section primarily apply to digital local or combined exchanges. Applicability to digital transit or international exchanges requires further study. + +Four types of exchange connection have been identified to show the basic forms of connection and their associated information flows that a digital local or combined exchange may be required to handle in an ISDN. They have been based on originating/terminating connections established via interfaces for subscriber access as described in Recommendation Q.512 to/from locations external to the exchange. Calls may be set up in either direction, i.e., subscriber to network or network to subscriber. + +These diagrams are functional and not intended to represent any particular implementation. They illustrate the options which may be available for handling a given information type or service within a digital local or combined exchange. Although this approach leads to some duplication between the individual diagrams when considered from the connection point of view, the approach is a logical basis for the further consideration of the more detailed issues arising from the impact of the ISDN on a digital local or combined exchange. + +It is not intended to imply that every digital local or combined exchange should necessarily have the capability to handle all these types of connection. + +Other types of connection and variants of these basic exchange connections may be feasible in an ISDN and are the subject of further study. + +The signalling and control aspects of these connections are covered in §§ 3 and 5 of this Recommendation. + +#### 2.2.2 Explanatory information on the exchange connection diagrams + +The functions associated with the groupings shown on the types I-IV exchanges connection diagrams are covered in § 3. + +##### Key + +![](d62e2e2281009c16f4ee61660e716cd9_img.jpg) + +| | | | +|---|-----------|--------------------------------------------| +| { | ————— | information other than separate signalling | +| | - - - - - | separate signalling(s) | + +##### Information flows + +- $p_1$ : packet data information different from customer-originated packetized data; +- $s_1, s_2, s_4, s_5$ : signalling information different from the signalling associated with customer terminals; +- packet switching interworking functions may be provided at other exchanges in an ISDN or at the point of access to a separate packet switched network. + +#### 2.2.3 Type 1 exchange connection (Figure 1/Q.522) + +This connection is used to transport telephony and associated voice services. + +This connection is characterized by (see Table 2/I.340, A 4, A 5, A 7 and A 8): + +- *Information transfer attributes* + - mode: circuit + - rate: 64 kbit/s + - capability: speech – 3.1 kHz audio + - establishment: switched – semi-permanent + - symmetry: bidirectional – symmetric + - configuration: point-to-point uniform + - structure: 8 kHz integrity +- *Access attributes* (Table 1/Q.522) + +TABLE 1/Q.522 + +| Access attributes | User access | Network access | +|-------------------------------|-------------------|------------------------------------------------------------------| +| Access channel and rate | | | +| Information | B/64 | Digital circuit with access to analogue/digital switched network | +| Signalling | D/16—64 | Digital circuit ( $s_1$ ) | +| Access protocol a) | | | +| Layer 1 | For further study | Q.702, others | +| Layer 2 | I.441 | Q.703, others | +| Layer 3 | I.451 | Q.704, Q.714, Q.764, others | + +a) Only for switched services. + +- *Other attributes* +For further study. + +![Diagram of Type I exchange connection showing digital subscriber access (B and D channels) connected to Layer 1 and Layer 2 functions. Layer 1 functions connect to a 64 kbit/s circuit switch, which outputs 'info'. Layer 2 functions connect to signalling handling and exchange control functions, which output '(s)'. Both the 'info' and '(s)' outputs are combined into a 64 kbit/s digital circuit with access to analogue/digital network, labeled (s1). The diagram is labeled CCITT-59641.](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +Diagram of Type I exchange connection showing digital subscriber access (B and D channels) connected to Layer 1 and Layer 2 functions. Layer 1 functions connect to a 64 kbit/s circuit switch, which outputs 'info'. Layer 2 functions connect to signalling handling and exchange control functions, which output '(s)'. Both the 'info' and '(s)' outputs are combined into a 64 kbit/s digital circuit with access to analogue/digital network, labeled (s1). The diagram is labeled CCITT-59641. + +FIGURE 1/Q.522 +**Type I exchange connection** + +#### 2.2.4 *Type II exchange connection* (Figure 2/Q.522) + +This connection is used to transport circuit switched services such as data, telephony, multiple substrate information streams multiplexed into 64 kbit/s by the user, transparent access to a PSPDN (see § 5.2.2). + +This connection is characterized by: + +- *Information transfer attributes* (see Table 2/I.340, A 1 and A 2) + - mode: circuit + - rate: 64 kbit/s + - capability: unrestricted digital information + - establishment: switched – semi-permanent + - symmetry: bidirectional – symmetric + - configuration: point-to-point uniform + - structure: 8 kHz integrity +- *Access attributes* (Table 2/Q.522) + +TABLE 2/Q.522 + +| Access attributes | User access | Network access | +|-------------------------|------------------------------------------------|------------------------------------------------------------------------------| +| Access channel and rate | | | +| Information | B/64 | Digital circuit with access to analogue/digital switched network | +| Signalling | D/16-64 | Digital circuit ( $s_1$ ) | +| Access protocol | See type I (For signalling only) a) | See type I (For signalling access to digital switched network) a) | + +a) Further study is required for information transfer protocol or access to PSPDN. + +##### – *Other attributes* + +For further study. + +![Diagram of Type II exchange connection showing digital subscriber access (B, D, (s)) connected to Layer 1 and Layer 2 functions, which are then connected to a 64 kbit/s circuit switch and signalling handling functions, leading to a 64 kbit/s digital circuit with access to a digital switched network (info, (s1)).](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) + +The diagram illustrates the internal architecture of a Type II exchange connection. On the left, 'Digital subscriber access' is shown with components B, D, and (s). These connect to a central block containing 'Layer 1 functions', 'Layer 2 functions', a '64 kbit/s circuit switch', and 'Signalling handling and exchange control functions'. The Layer 1 and 2 functions are connected to the circuit switch via an 'info' path. Layer 2 functions also connect to the signalling handling functions via a dashed line labeled (s). The circuit switch outputs to the right via an 'info' path, which leads to a '64 kbit/s digital circuit with access to digital switched network'. This output path is also associated with (s1). The entire central block is enclosed in a dashed box, and the label 'CCITT-S9651' is at the bottom right. + +Diagram of Type II exchange connection showing digital subscriber access (B, D, (s)) connected to Layer 1 and Layer 2 functions, which are then connected to a 64 kbit/s circuit switch and signalling handling functions, leading to a 64 kbit/s digital circuit with access to a digital switched network (info, (s1)). + +FIGURE 2/Q.522 +**Type II exchange connection** + +#### 2.2.5 *Type III exchange connection* (Figure 3/Q.522) + +This is a connection used to transport packetized data information between an information channel on a digital subscriber access and a 64 kbit/s digital circuit which has an access to: + +- a) a remote ISDN Packet Handling Functional Grouping; +- b) a remote ISDN Packet Switching Interworking Functional Grouping; +- c) a public packet network (see § 5.2.3). + +This connection is characterized by: + +- *Information transfer attributes* (see Table 3/Q.522) + (see Table 2/I.340, A 10 and A 11) + +TABLE 3/Q.522 + +| Access attributes | Option a) | Options b) and c) | +|-------------------|----------------------------------|----------------------------------| +| Mode | Circuit | Packet | +| Rate | 64 kbit/s (further study) | 64 kbit/s (further study) | +| Capability | Unrestricted digital information | Unrestricted digital information | +| Establishment | Switched – semi-permanent | Switched – semi-permanent | +| Symmetry | Bidirectional symmetric | Bidirectional symmetric | +| Configuration | Point-to-point | Point-to-point | +| Structure | 8 kHz | Service data unit integrity | + +- Access attributes (Table 4/Q.522) + +TABLE 4/Q.522 + +| Access attributes | User access | Network access | +|-------------------------|-------------------|-----------------------------------------| +| Access channel and rate | | | +| Information | | | +| Options a), b), c) | B/Further study | 64 kbit/s digital circuit a) | +| Signalling a), b), c) | D/16-64 | 64 kbit/s digital circuit a) | +| Access protocol | | | +| Options a), b) | For further study | For further study | +| Option c) | For further study | X.75- X.25 | + +a) Information and signalling may be carried by the same circuit (in-band signalling). + +- Other attributes + +For further study. + +![Diagram of Type III exchange connection option a) showing digital subscriber access (B and D channels) connected to Layer 1 and Layer 2 functions, which are then connected to a 64 kbit/s circuit switch and signalling handling functions. The diagram is labeled with (s) and (s1) for signalling paths.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +The diagram illustrates the connection architecture for Type III exchange option a). On the left, 'Digital subscriber access' is shown with two channels: 'B' (solid line) and 'D' (dashed line). Both channels are grouped by a bracket and labeled '(s)'. The 'B' channel connects to a box labeled 'Layer 1 functions', and the 'D' channel connects to a box labeled 'Layer 2 functions'. These two boxes are stacked vertically. A solid line connects 'Layer 1 functions' to a box labeled '64 kbit/s circuit switch'. A dashed line connects 'Layer 2 functions' to a box labeled 'Signalling handling and exchange control functions'. Both of these boxes are contained within a larger dashed-line boundary. From the '64 kbit/s circuit switch', a solid line extends to the right, where it is grouped by a bracket and labeled '(s1)'. This line leads to a text description: '64 kbit/s digital circuit with access to packet handling functional grouping (see Note 1)'. The label 'TI102800-86' is located at the bottom right of the diagram. + +Diagram of Type III exchange connection option a) showing digital subscriber access (B and D channels) connected to Layer 1 and Layer 2 functions, which are then connected to a 64 kbit/s circuit switch and signalling handling functions. The diagram is labeled with (s) and (s1) for signalling paths. + +FIGURE 3a/Q.522 + +Type III exchange connection option a) + +![Diagram of Type III exchange connection option b)](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +This diagram illustrates the internal architecture of a Type III exchange for option b). On the left, 'Digital subscriber access' is shown with two lines labeled 'B' and 'D'. The 'B' line connects to a box labeled 'Layer 1 functions', which in turn connects to a '64 kbit/s circuit switch'. The 'D' line connects to a box labeled 'Layer 2 functions'. A dashed line labeled '(s)' connects 'Layer 2 functions' to a box labeled 'Signalling handling and exchange control functions'. This box is connected to a 'Packet handling functional grouping' box. A line from the 'Packet handling functional grouping' box points to a bracket labeled '(Note 1)' which contains the text: '64 kbit/s digital circuit with access to packet handling and/or interworking functional groupings'. The identifier 'T1102811-87' is located at the bottom right of the diagram. + +Diagram of Type III exchange connection option b) + +FIGURE 3b/Q.522 +**Type III exchange connection option b)** + +![Diagram of Type III exchange connection option c)](990567efebf979be51f56d1150012c9d_img.jpg) + +This diagram illustrates the internal architecture of a Type III exchange for option c). On the left, 'Digital subscriber access' is shown with two lines labeled 'B' and 'D'. The 'B' line connects to a box labeled 'Layer 1 functions', which connects to a '64 kbit/s circuit switch'. The 'D' line connects to a box labeled 'Layer 2 functions'. A dashed line labeled '(s)' connects 'Layer 2 functions' to a box labeled 'Signalling handling and exchange control functions'. This box is connected to a 'Packet handling functional grouping' box. Below this box is a dashed line labeled '(Note 2) (s2)', which connects to a box labeled 'Packet switching interworking functional grouping'. A line from this box points to a bracket labeled '(Note 1)' which contains the text: '64 kbit/s digital circuit with access to public packet network'. The identifier 'T1102820-86' is located at the bottom right of the diagram. + +Diagram of Type III exchange connection option c) + +FIGURE 3c/Q.522 +**Type III exchange connection option c)** + +*Note 1* – These links may pass through the 64 kbit/s circuit switch. This requires further study. + +*Note 2* – $s_2$ , optional. + +#### 2.2.6 *Type IV exchange connection* (Figure 4/Q.522) + +This connection is used to transport message type data, for example packetized data messages or teleaction information messages (see § 5.2.4). + +It consists of a message/packet type connection via a D channel on a digital subscriber access to an access port to either: + +- a) a remote ISDN Interworking Functional Grouping; or +- b) a public packet network. + +This connection is characterized by: + +- *Information transfer attributes* +(see Table 2/I.340). +See type III, options b) and c). +- *Access attributes* (Table 5/Q.522). + +TABLE 5/Q.522 + +| Access attributes | User access | Network access | +|----------------------------|-----------------------------------|-----------------------------------------| +| Access channel and rate | | | +| Information and signalling | | | +| Options a) and b) | D/For further study a) | 64 kbit/s digital circuit b) | +| Access protocol | | | +| Option a) | For further study | For further study | +| Option a) | For further study | X.75 - X.25 | + +a) Signalling in-band or out-band. + +b) Signalling in-band or out-band for option a), or in-band for option b). + +- *Other attributes* +For further study. + +![Diagram of Type IV exchange connection showing functional groupings and two options for network access.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph LR + subgraph "Digital subscriber access" + DSA_P["(p)"] + DSA_S["(s)aa)"] + end + + subgraph "Exchange Connection" + L1[Layer 1 functions] + L2[Layer 2 functions] + PH[Packet handling functions] + CS[64 kbit/s circuit switch] + SH[Signalling handling and exchange control functions] + PS[Packet switching interworking function] + end + + DSA_P --> L1 + L1 --- L2 + L2 --- PH + DSA_S --- L2 + DSA_S --- PH + + L2 -- "(s4)aa)" --- CS + L2 -- "(s3)" --- SH + PH -- "(s2)" --- SH + SH -- "(s5)aa)" --- PS + CS --- PS + PH --- PS + + CS -- "(p)" --- OA + SH -- "(s1)" --- OA + PS -- "(p1)" --- OB + + subgraph "Option a)" + OA["64 kbit/s digital circuit switched network with access to packet handling and/or packet switching interworking functional groupingsb)"] + end + + subgraph "Option b)" + OB["64 kbit/s digital circuit with access to packet networkb)"] + end + +``` + +The diagram illustrates the functional architecture of a Type IV exchange connection. On the left, 'Digital subscriber access' provides interfaces (p) and (s)a. Inside the exchange, Layer 1 and Layer 2 functions handle the initial processing. Signaling paths (s2), (s3), (s4)a, and (s5)a connect various functional blocks including the 64 kbit/s circuit switch, Signalling handling, and Packet switching interworking. Two options for network connection are shown on the right: Option a) for circuit-switched network access and Option b) for packet network access. Reference code T1108870-87 is present. + +Diagram of Type IV exchange connection showing functional groupings and two options for network access. + +- a) *s*, *s*4 and *s*5 are only applicable when all signalling required is not contained in the *p* information. +- b) Signalling in-band or out-band for option a), or in-band for option b). + +FIGURE 4/Q.522 + +##### **Type IV exchange connection** + +### 2.3 *Functions associated with attributes shown in § 2.2* + +The following information is to clarify which functions may be associated with the attributes shown on the types I-IV exchange connection diagrams described in § 2.2. + +#### 2.3.1 *Layer 1 functions* (see Note in § 2.3.4) + +This functional grouping includes: + +- digital line/exchange termination interface functions. + +#### 2.3.2 *Layer 2 functions* (see Note in § 2.3.4) + +This functional grouping includes: + +- layer 2 D-channel protocol handling (LAP D) + +#### 2.3.3 *64 kbit/s circuit switching functions* + +This functional grouping includes: + +- 64 kbit/s switching stage(s). + +#### 2.3.4 *Signalling handling and exchange control functions* + +This functional grouping may include: + +- layer 3 D-channel protocol for signalling (see Note); +- functions related to circuit switched connection control; + +- signalling functions for common channel signalling; +- signalling interfaces with “packet handling function”; +- functions related to packet switched connections; +- signalling interface with “packet switching interworking function”. + +*Note* - The term “layer” refers to Open Systems Interconnection as applied to CCITT signalling systems as defined by Recommendations X.200 and I.112. + +#### 2.3.5 *Packet switching interworking functions* + +This functional grouping may include: + +- signalling interface with “packet handling function” and “signalling handling and exchange control function” allowing call packets to be routed to/from the appropriate subscriber terminals; +- routing functions; +- functions such as compatibility checking; +- protocol conversion; +- numbering interworking; +- control function (see Note in § 2.3.6). + +#### 2.3.6 *Packets handling function* + +This functional grouping may include: + +- layer 3 D-channel protocol for packet calls; +- packet level multiplexing for outgoing calls; +- packet level demultiplexing for incoming calls; +- signalling interface with the “signalling handling function” and subscriber terminals via layer 1 and 2 functional block; +- control functions for packet switched connections (see Note); +- some or all the functions associated with packet switching (e.g., internal packet calls). + +*Note* - Clarification of control function would need further study. + +In the case where the packet switching interworking function is not present in the local exchange, the local exchange contains the minimum functions necessary to enable it to communicate with the packet switching interworking function. The protocols to carry out this minimum function require further study. + +### 2.4 *Bit rate of a connection through an exchange* + +#### 2.4.1 *Basic bit rate for circuit switched connections* + +The exchange should be able to make circuit switched connections between channel timeslots with the basic bit rate of 64 kbit/s. The channel timeslots to be connected are contained in primary or higher order frame structures appearing at the digital interfaces of the exchange or derived from analogue channels appearing at the analogue interfaces, or from individual digital interfaces for subscriber access. + +Switching at rates other than 64 kbit/s is for further study. + +#### 2.4.2 *Basic bit rate for message/packet switched connections Type IV* + +The bit rate of a message/packet connection Type IV will depend on a number of factors including the bit rate of the subscriber terminal equipment, the bit rate of the D channel and the bit rate capacity of the connection to the appropriate network. + +### 2.5 *Services offered at bit rates less than 64 kbit/s* + +Services requiring less than 64 kbit/s for a connection should be switched as 64 kbit/s connections. + +### 2.6 Services offered at bit rates greater than 64 kbit/s + +#### 2.6.1 General + +Services requiring more than 64 kbit/s for a connection are through-connected as a multiple of 64 kbit/s connections. They are called multi-slot connections. + +The exchange may be required to establish the following types of multi-slot connections (see Recommendation I.340): + +- $2 \times 64$ kbit/s connections; +- $6 \times 64$ kbit/s connections to provide a $H_0$ channel; +- $24 \times 64$ kbit/s connections to provide a $H_{11}$ channel; +- $30 \times 64$ kbit/s connections to provide a $H_{12}$ channel. + +It should be noted that an $n \times 64$ kbit/s connection can seriously affect the blocking probability of an exchange and the network, particularly if all $n$ timeslots are routed in a defined order in the same multiplex. The ability to handle multi-slot traffic will be influenced by the traffic loading of the exchange at any instant and the number of circuits available on the required route. + +#### 2.6.2 $2 \times 64$ kbit/s connections + +This connection type is characterized by the following attributes (see Recommendation I.340). + +The attributes are for further study. + +A $2 \times 64$ kbit/s connection is established in response to signalling information received on the subscriber line or on an inter-exchange link. + +The exchange should maintain restricted differential time delay between the two timeslots involved in the connection. The precise definition of "restricted differential time delay" is still to be formulated, but the intention is to ensure that the time delay between the individual slots forming a $2 \times 64$ kbit/s connection is not excessive, for example as could occur if the two channels were routed out of the exchange on diverse physical routings. + +The exchange aspects of meeting this requirement require further study, but will include the need for the exchange to be capable of recognizing the signalling information on incoming inter-exchange circuits/subscriber accesses which indicates that there is an association between two incoming 64 kbit/s channels and to ensure that the two channels are handled by the exchange in a uniform manner. + +#### 2.6.3 Switching of $6 \times 64$ kbit/s connections ( $H_0$ channel) + +The 64 kbit/s timeslots which form an $H_0$ channel are transmitted over the same primary multiplex system within the same frame. This is valid for both the subscriber line and the inter-exchange links. + +The requirement for $6 \times 64$ kbit/s connections can be satisfied by establishing 6 separate 64 kbit/s semi-permanent connections, each of which would be set up to preserve the sequence with the other slots forming the $6 \times 64$ kbit/s connection. + +#### 2.6.4 Switching of 24 or $30 \times 64$ kbit/s connection ( $H_1$ channels) + +This is for further study. + +### 2.7 Mode of establishment + +#### 2.7.1 Circuit switched connections, Type I, Type II and Type III option a) + +Circuit switched connections are set up at any time on demand in response to signalling information received from subscribers, other exchanges or other networks. + +#### 2.7.2 Packet switched connections, Type III options b) and c) + +For further study. + +#### 2.7.3 Message/packet switched connections, Type IV + +These connections are set up on demand subject to any D channel priority/flow control restrictions that may be applicable. + +#### 2.7.4 *Semi-permanent connections* + +The exchange should have the capability of establishing semi-permanent connections which pass through the exchange switching network. + +Other features of semi-permanent connections, e.g. grade of service, the need for an out-slot signalling channel associated with the connection, etc. are for further study. + +### 2.8 *Bit sequence independence* + +See Recommendation Q.554. + +### 2.9 *Bit integrity* + +See Recommendation Q.554. + +### 2.10 *Octet sequence integrity* + +See Recommendation Q.9. + +### 2.11 *8 kHz (structure) integrity* + +See Recommendation I.140. + +### 2.12 *Bit patterns generated by the exchange in idle channel timeslots* + +At interfaces A and B, the following patterns are recommended for the idle condition, where the left-most digit is the polarity digit. + +01111111 for 1544 kbit/s systems + +01010100 for 2048 and 8448 kbit/s systems. + +At other interfaces the bit pattern generated in idle channel timeslots is for further study. + +The patterns should not be used as an indication of the idle or barred conditions of a channel since this information should be derived from the control or signalling functions. + +*Note* - These patterns are slightly different from the quiet code produced by external test equipment and used as an auxiliary signal for noise and crosstalk measurements on digital exchanges (see Recommendations Q.551, § 1.2.3.1, Q.552, §§ 2, 2.2.3, 3.1.4 and Q.553, §§ 2.1.1.2, 3.1.4). + +### 2.13 *Error performance* + +See Recommendation Q.554. + +### 2.14 *In-call rearrangement* + +In-call rearrangement is the rearrangement by the exchange of the established connections across the switchblock in a more efficient manner. + +When it is provided, it is essential that the requirements for error performance, Quality of Service, etc. be met (see Recommendation Q.543). + +### 2.15 *Transmission performance characteristics* + +See Recommendations Q.551 to Q.554. + +## 3 Signalling and D-channel handling + +### 3.1 General + +The exchange should be capable of interworking with other exchanges using signalling systems indicated in Recommendation Q.7, and for local or combined exchanges with user equipment on digital access lines (e.g., terminals and PABXs) using the signalling procedures in Recommendations I.430, I.431, and Q.920 (I.440), Q.930 (I.450)-Series of Recommendations. + +For a local or combined exchange interworking with user terminals or analogue subscriber access lines should be accomplished using nationally recommended signalling procedures. + +64 kbit/s signalling channels entering the exchange via a multiplex structure may be connected through the exchange as semi-permanent channels. + +### 3.2 Signalling associated with exchange connections Types I-IV + +This section applies to local or combined exchanges only. + +#### 3.2.1 General + +Details of the exchange connections Types I-IV are given in § 5. + +For internal and originating connections, the call set up signalling information will be received from the subscriber. + +For terminating and transit connections, the call set up signalling information will be received from the appropriate network or separate signalling network. + +*Note* - Receipt of call set up signalling information may be affected by the involvement of supplementary services. + +#### 3.2.2 Basic connections including Type I exchange connection + +The exchange should carry out the functions defined in the following signalling systems. + +##### 3.2.2.1 On the subscribers side: + +- analogue line signalling systems as defined nationally; and +- the defined digital subscriber access signalling system(s) if digital subscriber accesses are provided (see Recommendations I.430 and Q.920, Q.930-Series of Recommendations). + +##### 3.2.2.2 On the network side + +One or more of the signalling systems are defined in Recommendation Q.7. + +#### 3.2.3 Type II exchange connection + +The exchange should carry out the functions defined in the following signalling systems. + +##### 3.2.3.1 On the subscriber side + +The defined digital subscriber access signalling system(s) (see Recommendations I.430 and Q.920, Q.930-Series of Recommendations). + +##### 3.2.3.2 On the network side + +One or more of the signalling systems defined in Recommendation Q.7. + +*Note* - Further study is required for information transfer protocol or access to PSPDN. + +#### 3.2.4 Type III exchange connection + +##### 3.2.4.1 On the subscriber side + +For further study. + +##### 3.2.4.2 *On the network side* + +The signalling associated with the messages/packets may be: + +- contained in the individual message/packets; or +- transported separately, in accordance with one or more of the signalling systems defined in Recommendation Q.7. + +A local exchange which supports such services must contain a function that is capable of either interpreting them and routing them appropriately, or of sending them directly to an appropriate interworking function. + +#### 3.2.5 *Type IV exchange connection* + +On the subscriber side: + +The signalling associated with the messages/packets may be: + +- contained in the individual message/packet, or +- transported separately as s-information (see Recommendations I.430 and Q.920, and Q.930-Series of Recommendations). + +On the trunk side: + +The signalling associated with the messages/packets may be: + +- contained in the individual message/packet ( $p_1$ ); or +- transported separately ( $s_1$ information), in accordance with one or more of the signalling systems defined in Recommendation Q.7. + +A local exchange which supports such services must contain a function that is capable of either interpreting them and routing appropriately, or of sending them directly to an appropriate interworking function. + +### 3.3 *Digital subscriber access - D channel and protocol handling layers 1, 2 and 3* + +The following text refers to handling the D-channel protocol on the exchange side of the interfaces U and $V_1$ . + +The functions associated with handling the D-channel protocol are defined in the parts of Recommendations I.430, Q.920 and Q.930-Series of Recommendations relating to call establishment for subscribers connected to the U or $V_1$ interfaces. Exchange functions for D-channel signalling procedures for users connected via a primary rate multiple access are also given in I.431, Q.920 and Q.930-Series of Recommendations. + +### 3.4 *User-to-user signalling* + +The exchange may receive signals from the user (e.g., from a PABX) for transport across the network. It must be capable of receiving this information, verifying its acceptability, and if the service is permitted to the requesting user, send it via the inter-exchange signalling or other network to the distant exchange. Similarly the exchange may receive information from the signalling network for transmission to the subscriber. This capability may not be provided on all types of connection. + +Where user-to-user signalling involves network inter-exchange facilities, it may be necessary for the originating local exchange to process this signalling information before sending it to the network, to ensure that it is compatible with signalling, charging and flow control requirements of the originating exchange and network. + +## 4 **Ancillary functions** + +### 4.1 *Connection of ancillary equipment* + +Ancillary equipment may be connected in the following way: + +- Serially. This may require more than one connection through the exchange. Examples of serially connected equipment include: + - echo control devices, + - encoding law converters, + - manual board access equipment (for operator controlled traffic). + +- ii) As terminal connected equipment usually requiring one connection through the exchange. Examples of such equipment include: +- recorded announcements, + - manual board terminations, + - speech codecs, + - data terminal facilities, + - test equipment (such as a test call sender), + - tone generators, + - signalling receivers. + +The interface between the exchange and the items of equipment listed above may be left to the national designers. However, the use of internationally standardized interfaces is preferred. + +*Note* – In some cases it may be necessary to establish more than one connection to one timeslot at the same time. + +### 4.2 *Digitally generated tones and frequencies* + +When tones and frequencies are digitally generated the following minimum requirements apply on a provisional basis. + +#### 4.2.1 *Service tones* + +Digitally generated tones should meet the recommended limits specified in Recommendation Q.35 when decoded. + +#### 4.2.2 *Signalling frequencies* + +Digitally generated signalling frequencies should be such that they can be detected after decoding by any analogue receivers designed to CCITT Recommendations. + +### 4.3 *Echo control devices* + +The exchange should be able to be equipped with echo control devices (echo suppressors/echo cancellers conforming to Recommendations G.164 and G.165 respectively). When required the exchange should be able to control such devices to meet the requirements of Recommendation Q.115. The means of control by the exchange is for further study. + +(*Note* – It is recognized that there is a need for an internationally agreed method of disabling and enabling echo control devices for the purposes of making end-to-end circuit transmission maintenance measurements, e.g. as recommended in Recommendation V.25.) + +## 5 **Control functions associated with call handling** + +### 5.1 *Basic control functions* + +The requirements for the basic control functions are implicit in the requirements recommended for the other functions of the exchange. However recommendation of a number of new requirements for the control functions associated with the handling of digital subscriber lines and the use of a digital local exchange within an ISDN, may be necessary. + +The exchange should provide the capability to avoid fraudulent use of the connection. Such capabilities may be based on the use of digital pads or an asymmetrical through-connect procedure. + +An originating local exchange should be capable of supporting either symmetric or asymmetric through-connect procedures. The choice of procedure may be determined on the basis of service. + +Terminating and transit exchange need only support symmetric through-connect procedure. + +This subject is for further study. + +### 5.2 *Exchange connections Types I-IV, general control aspects* + +#### 5.2.1 *Type I* + +These connections will be set up between the accesses associated with network addresses specified in response to the signalling information received. Voice-associated facilities, e.g. tones, should be provided where appropriate and telephony supplementary services may be invoked if provided. + +#### 5.2.2 *Type II* + +Such connections will be set up between the accesses associated with network addresses specified in response to the signalling messages received. Compatibility checking may be provided before the connection is completely established (see § 2.3.1). Voice associated facilities (e.g. tones, pads) will be disabled in order to provide a transparent digital path, (the means of doing this is for further study). Data supplementary services may be invoked if provided. + +#### 5.2.3 *Type III* + +Such connections will be set up between the accesses associated with network addresses specified in response to the signalling messages received. Compatibility checking may be provided before the connection is completely established (see § 2.3.1). Voice associated facilities (e.g. tones, pads) will be disabled in order to provide a transparent digital path (the means of doing this is for further study). Data supplementary services may be invoked if provided. + +For option a) in the switched access case, originating calls will be set up over the B channel towards the 64 kbit/s digital circuit using the ISDN signalling procedures prior to starting X.25 layer 2 and layer 3 functions. The corresponding service requested in the Q.931 SET-UP message is ISDN packet mode bearer service. For calls originated by the network, the same consideration applies (see Recommendations X.31 and I.462). + +The distant packet handling must be selected by the called address in the D-channel protocol when the terminal sets up the circuit switched connection. + +Packet data communications, when using a switched B channel, will be established by separating the establishment phase of the B channel (carried out by the exchange) and the control phase of the virtual circuit using the X.25 link layer and packet layer protocol (carried out in the distant packet handling function). + +For options b) and c) the same considerations as above apply except that the control phase of the virtual circuit is performed within the exchange. + +#### 5.2.4 *Type IV* + +These connections will be of the message/packet type (e.g., virtual circuit). The “p-information handling function” and “packet switching interworking function” shown in Figure 4/Q.521 will implement procedures for control of the logical links on the D channel (e.g., flow control, error control) (see also § 3.2.5). Voice associated facilities (e.g., tones, pads) will be disabled in order to provide a transparent digital path. + +The D channel provides a semi-permanent physical connection which enables the user terminal to access a packet handling function by establishing a link layer connection (with a specific SAPI) to that function which can then be used to support packet communications according to X.25 layer 3 procedures. The X.25 packet layer will use the acknowledged information service provided by LAP D (see Recommendation Q.920). X.25 layer 3 procedures are transferred transparently over the D Channel link. + +A single or multiple LAP D link must support the multiplexing of logical channels at layer 3. + +### 5.3 *Control functions associated with calls over a digital subscriber access via Interfaces U and V1* + +#### 5.3.1 *Control of circuit switched calls Types I, II and III* + +In response to s-information carried on the D channel and network signalling messages, the exchange must have the following capabilities. + +##### a) *Setting up a call* + +The exchange must receive address information (overlap sending or en bloc), establish the desired path (digital only or mixed) and send further (e.g., Signalling System No. 7) signalling, if necessary (e.g., address, calling line identity, service indicator) into the network. + +The call set up procedure may include steps to verify compatibility based on the record in the exchange of the services permitted for the subscriber. The degree of compatibility checking provided by the exchange requires further study. + +##### b) *During a call* + +In addition to the basic functions of maintaining a call record, supervising the call, charging for the call, etc., the exchange must be able to handle in-call service/facility requests. These include for example transfer of a call to another terminal or conferencing. + +If it is required that a terminal be moved from one location to another on the same access during a call, the exchange must be able to hold the call while the transfer is made and to re-establish communication on request by the user (including carrying out any compatibility checks). The exchange may limit the time allowed for moving a terminal. In addition, the user must send a signal to the exchange indicating that terminal movement is about to take place. Signalling procedures for terminal movement are given in Recommendation Q.931. + +##### c) *Clearing a call* + +The exchange will need to initiate call clearing on receipt of a clear request signal from the terminal or network. + +##### d) *Without a call path* + +The exchange may be required to handle signalling information without establishment of a call path (subscriber-network transactions). + +#### 5.3.2 *Control of message/packet calls over the D channel, Type IV* + +Any messages carrying p-information on the D channel must be handled by the exchange in accordance with the applicable Recommendation for services (e.g., Recommendation X.25) requested by the user. It is not necessary that every digital local or combined exchange in an ISDN should be able to carry out all the possible functions associated with handling this information. It is possible for example that the exchange may route such traffic to another node which has the appropriate handling facilities. + +## 6 Control functions associated with maintenance and automatic supervision + +See Recommendation Q.542. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da5eed29c3555cd1112aa3e8052b379bc5607de --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ea8cbfe9027ff1527f3a936add437b63fd94e8a499e5c74e0f608786b32f2a4 +size 7270 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d917210d1ab7fcb8ab0a4be4f3b5648cc53655d --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1db2c05770484b0b1d48baed2a2c2a7dd9bfd0eaa33413c4c5571318c77979b2 +size 16992 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c462ee7a8c6cfdeca3be98043d236cd44def2d6 --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce2c977acbeccc33dfc59b484dfc93121639c2aa23b3dbc11d88289e88a1e00c +size 45739 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c6352a47d85a88aa6220fda5938de32966efc17 --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cc8e6d031cba778bcdf49c1a8383b41b5627d4af9d57ee9610787c6282630e1 +size 49121 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78d138ff8f37d92187d431185f7f03a3f8d01e8f --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b81f57a4fca89c8b5df50d50c59587b0210d73fe9317f956f9bd274c979e8efc +size 35874 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff5961be2f041d10b2e9bd075868c745b0df32fc --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae805229c9383f86ffad376639a8ae45b1bf290520c2f6b3e00c67a2fc804d0f +size 55038 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/b6e90f8ae3109449704b9b5c7951f631_img.jpg b/marked/Q/T-REC-Q.605-198811-I_PDF-E/b6e90f8ae3109449704b9b5c7951f631_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35ebc807f061b06d1b9a6672846d9d73e52995d2 --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/b6e90f8ae3109449704b9b5c7951f631_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fd6eb9e09c5471dfc7b503a09af9f73b987ad1cf1fc26a2da026cd982812652 +size 7219 diff --git a/marked/Q/T-REC-Q.605-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.605-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0802cce2e01c934b58823fde1df546a1ab4fee87 --- /dev/null +++ b/marked/Q/T-REC-Q.605-198811-I_PDF-E/raw.md @@ -0,0 +1,186 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.605** + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**INTERWORKING OF SIGNALLING SYSTEMS - +DRAWING CONVENTIONS** + +**ITU-T Recommendation Q.605** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation Q.605 was published in Fascicle VI.6 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# 5 DRAWING CONVENTIONS + +In addition to Recommendations Z.101 to Z.104, the following rules apply to the logic procedures of the interworking specifications. + +## 5.1 *Inputs and outputs* + +In accordance with the basic concepts of SDL, *internal* inputs and outputs are used for logic procedures that do not go beyond the functional block involved. In addition, some SPITEs are used as *internal* inputs to describe the information flow at the interface between the signalling and switching procedures. + +All other inputs and outputs, including FITEs and BITEs as well as signals, which pass from one functional block to another are considered as being *external*. + +The *external* inputs and outputs point in the direction of the data flow between the three functional blocks as shown in Figure 2/Q.602. + +A multiple input (i.e. a group of signals) which leads to one and the same procedure can be represented by one standard symbol including that group of signals, if possible. + +## 5.2 *States* + +State symbols shall contain + +- the state number, and +- the descriptive text of the state. + +Most frequently the state indicates the input being waited for. + +The layout of the state symbol to be used for the interworking specifications is given in Figure 3/Q.605. + +![Diagram of a state symbol. It is a rounded rectangle with a thick border. Inside, at the top left, is a hash symbol '#'. In the center is the text 'Descriptive text of the state'. Below the symbol is the text 'CCITT - 32 710'.](b6e90f8ae3109449704b9b5c7951f631_img.jpg) + +CCITT - 32 710 + +Diagram of a state symbol. It is a rounded rectangle with a thick border. Inside, at the top left, is a hash symbol '#'. In the center is the text 'Descriptive text of the state'. Below the symbol is the text 'CCITT - 32 710'. + +# State number + +FIGURE 3/Q.605 + +**State symbol** + +## 5.3 *Connectors* + +Connectors are represented by a circle. The in-connector labels (within the connector symbol) shall be unique within the same interworking diagram. + +The designations used within the connector symbols are as follows (see Figure 4/Q.605): + +- a) arabic numerals, where the vertical line of flow of the procedure is to be interrupted. Subscripts outside the connector indicate the sheet numbers on which the associated connectors appear; + +- b) capital letters, where the horizontal line of a multiple branching of the process is to be interrupted. Subscripts outside the connectors indicate the sheet numbers, on which the associated connectors appear; +- c) "Pi" to indicate that the procedures are not completed (e.g. a subroutine or another detailed procedure). The connector symbol will then be non-subscripted with sheet numbers but be provided with the comment "to be completed" associated with a reference to the Recommendation concerned, if any. + +The connector reference is always shown in the left-hand column of each sheet of the interworking diagrams. + +![Diagram showing out-connectors. On the left, a vertical line has '7' and 'A'. To the right, connector '7' with subscript '4' has an arrow pointing to it. Below, connector 'A' with subscript '3' is at the end of a horizontal line with four vertical branches. Explanatory text is on the right. Diagram showing in-connectors. On the left, a vertical line has '7' and 'A'. For connector '7', there are two symbols: one with '2, 6, 8' and 'or' below it, and another with an arrow pointing away. For connector 'A', there is a symbol with subscript '5' and a horizontal line with three vertical branches. Explanatory text is on the right.](9e6062272bbe3ddbb7c0606721d64cf0_img.jpg) + +*Out-connectors* + +Out-connector No. 7, the corresponding in-connector is given on sheet 4 + +Out-connector A, the corresponding in-connector is given on sheet 3 + +*In-connectors* + +In-connector No. 7, the corresponding out-connectors are given on sheets 2, 6 and 8 + +In-connector A, the corresponding out-connector is given on sheet 5 + +CCITT - 32720 + +Diagram showing out-connectors. On the left, a vertical line has '7' and 'A'. To the right, connector '7' with subscript '4' has an arrow pointing to it. Below, connector 'A' with subscript '3' is at the end of a horizontal line with four vertical branches. Explanatory text is on the right. Diagram showing in-connectors. On the left, a vertical line has '7' and 'A'. For connector '7', there are two symbols: one with '2, 6, 8' and 'or' below it, and another with an arrow pointing away. For connector 'A', there is a symbol with subscript '5' and a horizontal line with three vertical branches. Explanatory text is on the right. + +FIGURE 4/Q.605 + +Examples of how to use connectors + +## 5.4 *Procedures not presented* + +In general, possible signals which are not shown as inputs in a given state are to be considered as consumed but discarded, i.e. ignored. A special treatment may be required in the following cases: + +- a) electrical conditions not recognized as regular signals (e.g. 1 out of 6 frequencies in the case of MFC signalling); +- b) regular signals, but not relevant to interworking (e.g. blocking, identification); +- c) any other regular signal recognized as an abnormality (e.g. out of sequence). + +In the cases a) and c), the appropriate actions to be taken are not specified in the existing Recommendations. Further study is required. + +The reactions in case of signals out of sequence can be shown by means of a state/signal matrix as auxiliary documentation. The interpretation of the diagrams will then be unambiguous. + +## 5.5 Presentation of time supervision + +The method of time supervision presentation to be used is shown in Figure 5/Q.605. + +If two timers are running in a state such that the longer timer can never mature, the input "time release" should nevertheless be shown for both timers in order that no misunderstanding can result. The meaning of start $t_1$ also includes the possibility of restart $t_1$ , $\bar{t}_1$ means the expiry of $t_1$ , + +![Figure 5/Q.605: Method of time supervision presentation. The diagram shows a sequence of states and transitions. It starts with an oval state, followed by a 'Start t1' transition (a rectangle with a right-pointing arrow) leading to another oval state. From this state, a horizontal line branches to two parallel transitions: a 'Stop t1' transition (rectangle with right-pointing arrow) and a 't1-bar' transition (rectangle with a right-pointing arrow). Both lead to a final 'Stop t1' transition (rectangle with right-pointing arrow). Dashed lines connect the states and transitions vertically. The label 'CCITT - 32730' is at the bottom right.](53f1f7d17b3e7aae62169c41d2a88a77_img.jpg) + +Figure 5/Q.605: Method of time supervision presentation. The diagram shows a sequence of states and transitions. It starts with an oval state, followed by a 'Start t1' transition (a rectangle with a right-pointing arrow) leading to another oval state. From this state, a horizontal line branches to two parallel transitions: a 'Stop t1' transition (rectangle with right-pointing arrow) and a 't1-bar' transition (rectangle with a right-pointing arrow). Both lead to a final 'Stop t1' transition (rectangle with right-pointing arrow). Dashed lines connect the states and transitions vertically. The label 'CCITT - 32730' is at the bottom right. + +FIGURE 5/Q.605 +Method of time supervision presentation + +## 5.6 Storage of inputs + +During the method of register function activation, all inputs are implicitly stored and the sequence of FITEs is also recorded. When the register function is not activated, inputs must explicitly be stored if required in a later state transition. + +## 5.7 Method of changing the order of signals + +In several interworking situations, the order in which signals are received is not necessarily the order of their utilization. Therefore, a rearrangement of the order is necessary. To change the signalling sequence in the interworking diagrams, the method indicated in Figure 6/Q.605 should be applied. Figure 6/Q.605 shows how such a situation can be coped with by SDL. + +## 5.8 Multiple sending of FITEs 1 or digits + +The case of multiple sending of FITEs 1 or digits often occurs in the logic procedures: in the former case in the incoming or interworking procedures, and in the latter case in the outgoing procedures of the en-bloc Signalling Systems No. 5 and R1. The presentation of Figure 7/Q.605 should be used. a) of Figure 7/Q.605 is used for multiple FITEs 1, while b) of Figure 7/Q.605 is used for outgoing Signalling Systems No. 5 or R1. In b) of Figure 7/Q.605 the outgoing logic has already received all the FITEs 1 and has established the "ST condition" prior to the logic sequence shown. + +![Diagram showing the method of changing the order of signals across three columns: Incoming logic procedures of system X, Interworking logic procedures from system X to system Y, and Outgoing logic procedures of system Y. The sequence of signals A, B, and C is shown being reordered from X to Y.](547f726730e589392f239257a833ede3_img.jpg) + +Incoming logic procedures of system X +Interworking logic procedures from system X to system Y +Outgoing logic procedures of system Y + +CCITT-32740 + +Diagram showing the method of changing the order of signals across three columns: Incoming logic procedures of system X, Interworking logic procedures from system X to system Y, and Outgoing logic procedures of system Y. The sequence of signals A, B, and C is shown being reordered from X to Y. + +FIGURE 6/Q.605 +**Method of changing the order of signals** + +![Flowcharts for the presentation method for multiple use of FITE 1. Part (a) shows the normal method with a loop for FITE 1. Part (b) shows the method for outgoing signalling systems R1 and No. 5, including steps like 'Start t1', 'Wait for time release', and 'Digit'.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) + +a) *Normal method* + +b) *Method for outgoing Signalling System R1 and No. 5* + +Only valid for Signalling System No. 5 + +CCITT-32752 + +Flowcharts for the presentation method for multiple use of FITE 1. Part (a) shows the normal method with a loop for FITE 1. Part (b) shows the method for outgoing signalling systems R1 and No. 5, including steps like 'Start t1', 'Wait for time release', and 'Digit'. + +FIGURE 7/Q.605 +**Presentation method for multiple use of FITE 1** + +In interworking cases where the signalling system at the outgoing end uses the overlap signalling mode with acknowledgements (Signalling Systems No. 4 and R2) or where the signalling speed of the system at the outgoing end is lower than that at the incoming end, the presentation method indicated in Figure 8/Q.605 should be used. + +![Flowchart of the presentation method for overlap signalling. The process starts with '03 Wait for FITE 1', followed by 'FITE 1', then 'Digit'. A loop exists between 'Digit' and '04 Wait for acknowledgement' via a 'FITE 1' block. From '04 Wait for acknowledgement', the flow goes to 'Acknowledgement', then to a decision diamond 'Any FITE 1 stored'. If 'Yes', it loops back to the start. If 'No', it proceeds to 'CCITT-32761'.](a738993919a50143787084ee7ce6e2f2_img.jpg) + +``` +graph TD; Start(( )) --> O3(03 Wait for FITE 1); O3 --> FITE1_1[FITE 1]; FITE1_1 --> Digit[Digit]; Digit --> FITE1_2[FITE 1]; FITE1_2 --> O4(04 Wait for acknowledgement); O4 --> Ack[Acknowledgement]; Ack --> Decision{Any FITE 1 stored}; Decision -- Yes --> Start; Decision -- No --> CCITT[CCITT-32761]; +``` + +Flowchart of the presentation method for overlap signalling. The process starts with '03 Wait for FITE 1', followed by 'FITE 1', then 'Digit'. A loop exists between 'Digit' and '04 Wait for acknowledgement' via a 'FITE 1' block. From '04 Wait for acknowledgement', the flow goes to 'Acknowledgement', then to a decision diamond 'Any FITE 1 stored'. If 'Yes', it loops back to the start. If 'No', it proceeds to 'CCITT-32761'. + +FIGURE 8/Q.605 + +**Presentation method for cases where the signalling system at the outgoing end uses the overlap signalling method** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2b0b2d73b247fc8d38494c438665beb0b34dde --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d968315bfd08bea8a3c05b4e9fc37faa6d95aeb204c966b61eaaf1aca7232874 +size 8237 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01854651f630ea26c8f2854c16411c4650c3ab50 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eff1a2f6750ace06afa037a707f016fa8d8979cf9ac729aef1a704ec5088765 +size 100236 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4533bb6fa61e3b1c1a89a068f1805be3e303b91d --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed8e9acbe8875585451f0a5566d06c3e13e3578f74f60dde74464c21e682cf1 +size 129077 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e508e32845f635b17d13c574ec2129b16ad50ebe --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afaefb6d7d364424243fef569f3acbbcee4910871474c7aa1c47daaa47d37391 +size 156619 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4644357e844ba288e26f1c09804662e862634f0e --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:029f6b11ad1c66959179828b97f0fd4c13af7b6e1530154cd2ceee858ccdd927 +size 131699 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..619ed02081d39f4b2ada3d237a409bf5f00e2657 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4570475818549c0c9b00c9c512af88899fdbb3010440a189fccfa36705a0b15 +size 27344 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87ceaca471ec74529f811bbaeade232b762a9d68 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02691419832dced523d7515379f2734580abb153f6584af3da62fc2aeeef9b0d +size 140281 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de808e068ca57eb1875a4f02e32782106e350f01 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5acac116b83e55866899c9721d3ea343c871d2677ce32e1aac8401a80d2d3932 +size 86253 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..631b94a2b57bf4bcfd07e50671f9687a8f3686ba --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4df4101e449268aa777edd0195ccdbcae1eba7ae9c074e12080b01e6dadd2e +size 101406 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2179ce0da4da0e2a80adae1464cc78c2c3f456a9 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bbfecaf665da6d2e3d039f393b46d10b8451aa994d849284f46420616ed5859 +size 120804 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a55b027a58840e347b70ad8264b78000f9bf8fc1 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1541d2909e4ba648307cfa704408933979346abc195d33faedcfa82f291b2e1a +size 37063 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.624-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e29fbdb53c13f3793bddb83a717df4e271fb9e --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc2a0e3eaa1ae8437b50ea37f53ef26bc94315276d53766b30ebd42e011f2acf +size 97340 diff --git a/marked/Q/T-REC-Q.624-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.624-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1ac3c913b02247ea612b17871c46de62e1723134 --- /dev/null +++ b/marked/Q/T-REC-Q.624-199303-I_PDF-E/raw.md @@ -0,0 +1,815 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.624** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +# **INTERWORKING OF SIGNALLING SYSTEMS** --- + +## **INTERWORKING OF SIGNALLING SYSTEMS – LOGIC PROCEDURES FOR OUTGOING SIGNALLING SYSTEM No. 7 (TUP)** + +**ITU-T Recommendation Q.624** + +(Previously "CCITT Recommendation") + +--- + +## FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.624 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +## --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTERWORKING OF SIGNALLING SYSTEMS – LOGIC PROCEDURES FOR OUTGOING SIGNALLING SYSTEM No. 7 (TUP) + +*(Melbourne, 1988; revised Helsinki at 1993)* + +![State overview diagram for outgoing Signalling System No. 7 (TUP)](69edc2887e907309499ac95b47ab6905_img.jpg) + +The diagram shows 10 circular nodes representing states numbered 00 to 09. Transitions are indicated by directed arrows. State 00 is connected to 01. 01 connects to 02 and 03. 02 connects to 04. 03 connects to 04 and 05. 04 connects to 06. 05 connects to 07. 06 connects to 07. 07 connects to 08. 08 connects to 09. 09 connects back to 00. There are also several arrows pointing from various states (01, 02, 03, 05, 07) upwards towards a common horizontal line, and arrows pointing from that line down to state 09. A label 'T1157620-93/d01' is located near state 08. + +State overview diagram for outgoing Signalling System No. 7 (TUP) + +| State number | State description | Sheet reference | Timers running | +|---------------------|-----------------------------------|------------------------|-----------------------| +| 00 | Idle | 1, 10 | | +| 01 | Wait for FITEs of IAM/IAI | 1 | | +| 02 | Wait for continuity check | 3 | $t_1, t_2$ | +| 03 | Wait for continuity indicator | 3 | $t_2$ | +| 04 | Wait for address complete | 7 | $t_2$ | +| 05 | Wait for answer | 7 | | +| 06 | Wait for answer (subscriber free) | 9 | | +| 07 | Answered | 9 | | +| 08 | Clear-back | 9 | | +| 09 | Wait for release-guard | 10 | $t_3, t_4$ | + +FIGURE 1/Q.624 +**State overview diagram for outgoing Signalling System No. 7 (TUP)** + +### **Supervisory timers for outgoing Signalling System No. 7** + +$t_1 = 2$ s              7.4.1/Q.724 + +$t_2 = 20-30$ s      6.4.1/Q.724 + +$t_3 = 4-15$ s        6.2.3/Q.724 + +$t_4 = 1$ min          6.2.3/Q.724 + +### **Procedures not shown** + +The following procedures, not directly relevant to interworking, are not shown in the logic procedures: + +- Dual seizure. +- Blocking and unblocking sequences. +- Reset signals. +- Test call procedures. +- Out of service. + +### **Signal abbreviations used** + +The signal abbreviations used correspond to those of the Signalling System No. 7 Specifications and are listed in Figure 2/Q.614. + +FIGURE 2/Q.624 +**Notes to outgoing Signalling System No. 7 (TUP)** + +![Flowchart for Outgoing Signalling System No. 7 (TUP). The process starts at state '00 Idle', followed by 'Activate outgoing No. 7 (TUP)'. It enters state '01 Wait for FITes of IAM/AI'. A horizontal sequence of FITes (FITE 1, 2, 3, 4, 5, 9, 10, 11) is shown, each with a corresponding action: FITE 1 (Set address digits and field length indicator), FITE 2 (Set NAI = 0), FITE 3 (Set NAI = 1), FITE 4 (Set ESI = 0), FITE 5 (Set ESI = 1), FITE 9 (Set CPCI = 1), FITE 10 (Set CPCI = 2), and FITE 11 (Set CPCI = 3). A decision diamond 'IAM/AI complete?' follows. If 'No', it loops back to state '01'. If 'Yes', it proceeds to 'IAM/AI' message, then 'Start t2' (t2 = 20-30 s). A decision diamond 'CCH' follows, with a '0, 2' path leading to connector '17' and a '1' path leading to connector '3'. Connector '3' also leads to 'SPITE 31 perform continuity check', then 'Start t1' (t1 = 2 s), which leads to connector '3'. Connector reference lines 1, A, B, 17, and 3 are on the left. Connector A is labeled '2' and connector B is labeled '2'. The diagram code 'T1141230-92/d02' is present.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Activate[Activate outgoing No. 7 (TUP)] + Activate --> Wait[01 Wait for FITes of IAM/AI] + state "FITE 1: Set address digits and field length indicator" as FITE1 + state "FITE 2: Set NAI = 0" as FITE2 + state "FITE 3: Set NAI = 1" as FITE3 + state "FITE 4: Set ESI = 0" as FITE4 + state "FITE 5: Set ESI = 1" as FITE5 + state "FITE 9: Set CPCI = 1" as FITE9 + state "FITE 10: Set CPCI = 2" as FITE10 + state "FITE 11: Set CPCI = 3" as FITE11 + Wait --> FITE1 + Wait --> FITE2 + Wait --> FITE3 + Wait --> FITE4 + Wait --> FITE5 + Wait --> FITE9 + Wait --> FITE10 + Wait --> FITE11 + FITE1 --> Complete{IAM/AI complete?} + FITE2 --> Complete + FITE3 --> Complete + FITE4 --> Complete + FITE5 --> Complete + FITE9 --> Complete + FITE10 --> Complete + FITE11 --> Complete + Complete -- No --> Wait + Complete -- Yes --> IAMAI[IAM/AI] + IAMAI --> StartT2[Start t2] + StartT2 --> T2Value["t2 = 20-30 s"] + T2Value --> CCH{CCH} + CCH -- 0, 2 --> Connector17((17)) + CCH -- 1 --> Connector3_1((3)) + Connector3_1 --> SPITE31[SPITE 31 perform continuity check] + SPITE31 --> StartT1[Start t1] + StartT1 --> T1Value["t1 = 2 s"] + T1Value --> Connector3_2((3)) + Connector17 --> Connector17_ref((2)) + Connector3_1 --> Connector3_ref((3)) + Connector3_2 --> Connector3_ref + ConnectorA((A)) --> ConnectorA_ref((2)) + ConnectorB((B)) --> ConnectorB_ref((2)) + FITE1 --> ConnectorA + FITE2 --> ConnectorA + FITE3 --> ConnectorA + FITE4 --> ConnectorA + FITE5 --> ConnectorA + FITE9 --> ConnectorA + FITE10 --> ConnectorA + FITE11 --> ConnectorA + FITE1 --> ConnectorB + FITE2 --> ConnectorB + FITE3 --> ConnectorB + FITE4 --> ConnectorB + FITE5 --> ConnectorB + FITE9 --> ConnectorB + FITE10 --> ConnectorB + FITE11 --> ConnectorB + +``` + +Connector reference + +1 + +A + +B + +17 + +3 + +00 Idle + +Activate outgoing No. 7 (TUP) + +01 Wait for FITes of IAM/AI + +FITE 1 + +FITE 2 + +FITE 3 + +FITE 4 + +FITE 5 + +FITE 9 + +FITE 10 + +FITE 11 + +Set address digits and field length indicator + +Set NAI = 0 + +Set NAI = 1 + +Set ESI = 0 + +Set ESI = 1 + +Set CPCI = 1 + +Set CPCI = 2 + +Set CPCI = 3 + +A + +B + +IAM/AI complete? + +No + +Yes + +IAM/AI + +Start $t_2$ + +$t_2 = 20-30$ s + +CCH + +0, 2 + +1 + +17 + +3 + +SPITE 31 perform continuity check + +Start $t_1$ + +$t_1 = 2$ s + +T1141230-92/d02 + +CCH Continuity check indicator + CPCI Calling party category indicator + ESI Echo suppressor indicator + NAI Nature of address indicator + +Flowchart for Outgoing Signalling System No. 7 (TUP). The process starts at state '00 Idle', followed by 'Activate outgoing No. 7 (TUP)'. It enters state '01 Wait for FITes of IAM/AI'. A horizontal sequence of FITes (FITE 1, 2, 3, 4, 5, 9, 10, 11) is shown, each with a corresponding action: FITE 1 (Set address digits and field length indicator), FITE 2 (Set NAI = 0), FITE 3 (Set NAI = 1), FITE 4 (Set ESI = 0), FITE 5 (Set ESI = 1), FITE 9 (Set CPCI = 1), FITE 10 (Set CPCI = 2), and FITE 11 (Set CPCI = 3). A decision diamond 'IAM/AI complete?' follows. If 'No', it loops back to state '01'. If 'Yes', it proceeds to 'IAM/AI' message, then 'Start t2' (t2 = 20-30 s). A decision diamond 'CCH' follows, with a '0, 2' path leading to connector '17' and a '1' path leading to connector '3'. Connector '3' also leads to 'SPITE 31 perform continuity check', then 'Start t1' (t1 = 2 s), which leads to connector '3'. Connector reference lines 1, A, B, 17, and 3 are on the left. Connector A is labeled '2' and connector B is labeled '2'. The diagram code 'T1141230-92/d02' is present. + +FIGURE 3/Q.624 (sheet 1 of 10) +**Outgoing Signalling System No. 7 (TUP)** + +![Diagram showing two rows of FITE (Forward Interworking Transfer Element) blocks. The top row includes FITE 12, 13, 17, 18, 19, and 20, each with a corresponding 'Set' block (e.g., Set CPCI = 4). The bottom row includes FITE 25, 26, 27, 20, 21, 22, and 24, with blocks for continuity checks, NCI settings, Idle, and a '1' output. Connector references A, J, B, E are on the left, and J, E are on the right.](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +The diagram illustrates two horizontal sequences of Forward Interworking Transfer Elements (FITEs) and their associated control blocks. + +**Top Sequence:** + +- Starts at connector reference **A, J** (1). +- Passes through FITE 12, 13, 17, 18, 19, and 20. +- Each FITE has a corresponding 'Set' block below it: + - Set CPCI = 4 (under FITE 12) + - Set CPCI = 5 (under FITE 13) + - Set CPCI = 10 (under FITE 17) + - Set CPCI = 11 (under FITE 18) + - Set CPCI = 12 (under FITE 19) + - SPITE 43 set IAM fields as defined by "service provided" (under FITE 20) +- Ends at connector reference **J** (2). + +**Bottom Sequence:** + +- Starts at connector reference **J** (2). +- Passes through FITE 25, 26, 27, 20, 21, 22, and 24. +- Each FITE has a corresponding block below it: + - Set continuity check ind. = 0 (under FITE 25) + - Set continuity check ind. = 1 (under FITE 26) + - Set continuity check ind. = 2 (under FITE 27) + - Set NCI = 0 (under FITE 20) + - Set NCI = 1 (under FITE 21) + - Idle (under FITE 22, with a '00' indicator) + - 1 (under FITE 24) +- Ends at connector reference **E** (2). + +Connector reference labels (A, J, B, E) are positioned on the left side of the diagram, with numbers 1 and 2 indicating specific points. Arrows indicate the flow from left to right through the FITEs and their associated blocks. + +Diagram showing two rows of FITE (Forward Interworking Transfer Element) blocks. The top row includes FITE 12, 13, 17, 18, 19, and 20, each with a corresponding 'Set' block (e.g., Set CPCI = 4). The bottom row includes FITE 25, 26, 27, 20, 21, 22, and 24, with blocks for continuity checks, NCI settings, Idle, and a '1' output. Connector references A, J, B, E are on the left, and J, E are on the right. + +NCI Nature of circuit indicator + +T1157630-93/d03 + +FIGURE 3/Q.624 (sheet 2 of 10) +Outgoing Signalling System No. 7 (TUP) + +![Flowchart for Outgoing Signalling System No. 7 (TUP)](547f726730e589392f239257a833ede3_img.jpg) + +Connector reference + +``` + +graph TD + Start((3)) -- "1, 3 (3x) +4 (2x)" --> Wait02[02 Wait for continuity check] + Wait02 --> SPITE33{SPITE 33 continuity check OK} + SPITE33 --> StopT1[Stop t1] + StopT1 --> CrossOffice{Cross office check OK} + CrossOffice -- No --> P2((P2)) + CrossOffice -- Yes --> CCH{CCH} + CCH -- No --> 14((14)) + CCH -- Yes --> FITE24Rec{FITE 24 received?} + FITE24Rec -- No --> 4((4)) + FITE24Rec -- Yes --> Wait03[03 Wait for continuity indicator] + Wait03 --> FITE24_1{FITE 24} + FITE24_1 --> COT{COT} + COT --> 14_3((14)) + COT --> SAMComp{SAM complete?} + SAMComp -- No --> 4_3((4)) + SAMComp -- Yes --> StartT2_1[Start t2] + StartT2_1 --> SAOSAM[SAO/SAM] + SAOSAM --> 4_3((4)) + FITE1_1{FITE 1} --> SAMComp_1{SAM complete?} + SAMComp_1 -- No --> 3((3)) + SAMComp_1 -- Yes --> StartT2_2[Start t2] + StartT2_2 --> SAOSAM_1[SAO, SAM] + SAOSAM_1 --> 3((3)) + FITE22_1{FITE 22} --> StopT1_1[Stop t1] + StopT1_1 --> StopT2_1[Stop t2] + StopT2_1 --> 15_10((15)) + FITE24_2{FITE 24} --> 3((3)) + BITE30{BITE 30} --> 5((5)) + StartT2_2 --> SAOSAM_2[SAO/SAM] + SAOSAM_2 --> 4((4)) + BITE19{BITE 19} --> 15_10((15)) + BITE31GRO1{BITE 31 (GRO)} --> 3((3)) + SPITE44[SPITE 44 Analyse info requested] --> SPITE45{SPITE 45} + SPITE45 -- No --> SPITE46{SPITE 46} + SPITE46 -- Yes --> BITE31GRO2{BITE 31 (GRO)} + BITE31GRO2 --> 3((3)) + SPITE46 -- No --> SPITE48[SPITE 48 Construct GSM message] + SPITE48 --> GSM{GSM} + GSM --> 4((4)) + FITE31GSM{FITE 31 (GSM)} --> 3((3)) + D((D)) --> SPITE44 + Note1[Note] -.-> SAOSAM + Note2[Note] -.-> SAOSAM_2 + +``` + +The flowchart illustrates the logic for Outgoing Signalling System No. 7 (TUP). It begins with a connector reference (1, 3 (3x), 4 (2x)) leading to a 'Wait for continuity check' (02). From there, it branches based on 'SPITE 33 continuity check OK', 'Cross office check OK', and 'CCH' status. If 'CCH' is Yes, it checks if 'FITE 24 received?'. If No, it goes to connector 4. If Yes, it goes to 'Wait for continuity indicator' (03). From 'Wait for continuity indicator', it branches to 'FITE 24', 'COT', 'FITE 1', 'FITE 22', and 't2'. 'COT' leads to connector 14. 'FITE 1' leads to 'SAM complete?'. If No, connector 3. If Yes, 'Start t2' leads to 'SAO/SAM' and then connector 4. 'FITE 22' leads to 'Stop t1', then 'Stop t2', then connector 15. 'FITE 24' leads to connector 3. 't2' leads to 'Stop t2' and 'BITE 19', both leading to connector 15. 'BITE 30' leads to connector 5. 'BITE 19' leads to connector 15. 'BITE 31 (GRO)' leads to connector 3. 'SPITE 44 Analyse info requested' leads to 'SPITE 45'. If No, 'SPITE 46'. If Yes, 'BITE 31 (GRO)' leads to connector 3. If No, 'SPITE 48 Construct GSM message' leads to 'GSM' and then connector 4. 'FITE 31 (GSM)' leads to connector 3. Connector D leads to 'SPITE 44'. Notes indicate that digits should be forwarded as soon as available and multi-digit SAMs only if more than one address digit is waiting. + +Flowchart for Outgoing Signalling System No. 7 (TUP) + +T1157640-93/d04 + +NOTE – Digits should be forwarded to the outgoing link as soon as they are available, multi digit SAMs should only be sent if more than one address digit is awaiting. + +FIGURE 3/Q.624 (sheet 3 of 10) +Outgoing Signalling System No. 7 (TUP) + +![Flowchart for Outgoing Signalling System No. 7 (TUP) showing the process from connector C to connector D, including continuity check, service analysis, and message construction.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Connector reference + +C, D + +P1 + +3 + +3 + +``` + +graph TD + C((C +3)) --> T1[" $\bar{t}_1$ "] + T1 --> P1((P1)) + P1 -.- PC[Procedure for continuity check failure] + T1 --> FITE31[FITE 31 +(GSM)] + FITE31 --> BITE31_GRQ1{BITE 31 +(GRQ)} + BITE31_GRQ1 --> SPITE44[SPITE 44 +Analyse information requested] + SPITE44 --> SPITE45{SPITE 45 +Is service allowed?} + SPITE45 -- No --> SPITE48[SPITE 48 +Construct GSM message] + SPITE45 -- Yes --> SPITE46{SPITE 46 +Is information available?} + SPITE46 -- No --> BITE31_GRQ2{BITE 31 +(GRQ)} + BITE31_GRQ2 --> S3_1((3 +3)) + SPITE46 -- Yes --> SPITE48 + SPITE48 --> GSM[/GSM/] + GSM --> S3_2((3 +3)) + BITE31_GRQ1 --> D((D +5)) + +``` + +The flowchart illustrates the signaling process for Outgoing Signalling System No. 7 (TUP). It begins at connector C (labeled 3) and proceeds through a timer ( $\bar{t}_1$ ) which can lead to a continuity check failure procedure (P1). The main path involves FITE 31 (GSM) and BITE 31 (GRQ) processing. The flow branches to connector D (labeled 5) or into an analysis phase. In the analysis phase (SPITE 44), it checks if service is allowed (SPITE 45). If not, it proceeds to construct a GSM message (SPITE 48). If allowed, it checks if information is available (SPITE 46). If information is not available, it sends a BITE 31 (GRQ) and goes to connector 3. If available, it proceeds to SPITE 48 to construct and send the GSM message, ending at connector 3. + +Flowchart for Outgoing Signalling System No. 7 (TUP) showing the process from connector C to connector D, including continuity check, service analysis, and message construction. + +FIGURE 3/Q.624 (sheet 4 of 10) +**Outgoing Signalling System No. 7 (TUP)** + +![Flowchart for Outgoing Signalling System No. 7 (TUP) showing various signal types (SEC, CGC, NNC, ADI, UNN, SSB, LOS, SST) and their corresponding BITEs (9, 10, 12, 14, 15, 16, 17, 20). The flowchart includes decision points for CCH and Continuity check OK, leading to Stop t2, Stop t1, or connector 15.](2ee59e629035d641140e55f4d215b0d7_img.jpg) + +Connector reference + +``` + +graph TD + D((D +4, 8)) --> SEC[SEC] + SEC --> B9[BITE 9] + B9 --> H((H +6)) + CGC[CGC] --> B10[BITE 10] + B10 --> H + NNC[NNC] --> B12[BITE 12] + B12 --> H + ADI[ADI] --> B14[BITE 14] + B14 --> H + UNN[UNN] --> B15[BITE 15] + B15 --> H + SSB[SSB] --> B16[BITE 16] + B16 --> H + LOS[LOS] --> B17[BITE 17] + B17 --> H + SST[SST] --> B20[BITE 20] + B20 --> H + G((G +6)) --> SEC + H --> StopT2{{Stop t2}} + StopT2 --> CCH{CCH +0, 2} + CCH -- 1 --> ContOK{Continuity check OK} + ContOK -- Yes --> H + ContOK -- No --> StopT1{{Stop t1}} + StopT1 --> 15((15 +10)) + T1157660-93/d06 + +``` + +The diagram illustrates the signal flow and processing for Outgoing Signalling System No. 7 (TUP). At the top, a horizontal line connects connector D (4, 8) to connector G (6). Below this line, eight signal types are shown in a row: SEC, CGC, NNC, ADI, UNN, SSB, LOS, and SST. Each signal type is associated with a specific BITE (Bit Error Test Equipment): BITE 9 for SEC, BITE 10 for CGC, BITE 12 for NNC, BITE 14 for ADI, BITE 15 for UNN, BITE 16 for SSB, BITE 17 for LOS, and BITE 20 for SST. All BITEs lead to a common horizontal line that connects to connector H (6). Below this line, the flow proceeds to a decision point 'Stop t2'. From 'Stop t2', the flow goes to a decision point 'CCH' (0, 2). If the 'CCH' decision is '1', the flow proceeds to 'Continuity check OK'. If 'Continuity check OK' is 'Yes', the flow returns to connector H. If 'Continuity check OK' is 'No', the flow proceeds to 'Stop t1'. From 'Stop t1', the flow proceeds to connector 15 (10). A reference 'T1157660-93/d06' is noted near connector H. A vertical line on the left is labeled 'Connector reference' at the top, 'D, G' near the top, 'H' near the middle, and '15' near the bottom. + +Flowchart for Outgoing Signalling System No. 7 (TUP) showing various signal types (SEC, CGC, NNC, ADI, UNN, SSB, LOS, SST) and their corresponding BITEs (9, 10, 12, 14, 15, 16, 17, 20). The flowchart includes decision points for CCH and Continuity check OK, leading to Stop t2, Stop t1, or connector 15. + +FIGURE 3/Q.624 (sheet 5 of 10) +Outgoing Signalling System No. 7 (TUP) + +![Diagram of Outgoing Signalling System No. 7 (TUP) showing connections between connector references G and H, and functional blocks CFL, ACB, DPN, BITE 19, BITE 35, and BITE 36.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Connector reference + +The diagram illustrates the signal flow for the Outgoing Signalling System No. 7 (TUP). On the left, two connector references are shown: 'G' at the top and 'H' at the bottom, each associated with a circle labeled 'G' and 'H' respectively, and the number '5' next to them. A horizontal line connects the 'G' circle to three chevron-shaped blocks labeled 'CFL', 'ACB', and 'DPN'. Below each of these blocks is a rectangular block labeled 'BITE 19', 'BITE 35', and 'BITE 36' respectively. Arrows point from each of these three 'BITE' blocks down to a common horizontal line. From this line, an arrow points to the 'H' circle. The text 'T1157670-93/d07' is located in the bottom right corner of the diagram area. + +Diagram of Outgoing Signalling System No. 7 (TUP) showing connections between connector references G and H, and functional blocks CFL, ACB, DPN, BITE 19, BITE 35, and BITE 36. + +FIGURE 3/Q.624 (sheet 6 of 10) +**Outgoing Signalling System No. 7 (TUP)** + +![SDL diagram for Outgoing Signalling System No. 7 (TUP).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Connector reference + +5 +3, 8 (4x) + +04 +Wait for address complete + +It was noted that further study is required concerning how additional information in the address complete can be economically represented in this SDL diagram. + +Z + +8 + +ACM (ADC) + +BITE 2 + +ACM (ADC) + +BITE 3 + +ACM (ADX) + +BITE 4 + +ACM (AFC) + +BITE 5 + +ACM (AFX) + +BITE 6 + +ACM (AFN) + +BITE 7 + +Stop $t_2$ + +6 + +7 + +05 +Wait for answer + +Stop $t_2$ + +7 + +9 + +ANC + +BITE 22 + +ANN + +BITE 23 + +CGC + +BITE 10 + +NNC + +BITE 12 + +CFL + +BITE 19 + +FITE 22 + +15 + +10 + +T1157680-93/d08 + +FITE 23 + +FOT + +6 + +7 + +8, 15, 6 + +8 + +9 + +``` + +graph TD + C5((5)) --> S04[04 Wait for address complete] + S04 --> ACM_ADC1[/ACM ADC/] + S04 --> ACM_ADC2[/ACM ADC/] + S04 --> ACM_ADX[/ACM ADX/] + S04 --> ACM_AFC[/ACM AFC/] + S04 --> ACM_AFX[/ACM AFX/] + S04 --> ACM_AFN[/ACM AFN/] + S04 --> CZ((Z)) + CZ --> C8((8)) + + ACM_ADC1 --> BITE2[/BITE 2/] + ACM_ADC2 --> BITE3[/BITE 3/] + ACM_ADX --> BITE4[/BITE 4/] + ACM_AFC --> BITE5[/BITE 5/] + ACM_AFX --> BITE6[/BITE 6/] + ACM_AFN --> BITE7[/BITE 7/] + + BITE2 --> STOP_T2_1[Stop t2] + BITE3 --> STOP_T2_1 + BITE4 --> STOP_T2_1 + BITE5 --> STOP_T2_1 + BITE6 --> STOP_T2_1 + BITE7 --> STOP_T2_1 + + STOP_T2_1 --> C6((6)) + C6 --> S05[05 Wait for answer] + S05 --> ANC[/ANC/] + S05 --> ANN[/ANN/] + S05 --> CGC[/CGC/] + S05 --> NNC[/NNC/] + S05 --> CFL[/CFL/] + S05 --> FITE22[/FITE 22/] + + ANC --> BITE22[/BITE 22/] + ANN --> BITE23[/BITE 23/] + CGC --> BITE10[/BITE 10/] + NNC --> BITE12[/BITE 12/] + CFL --> BITE19[/BITE 19/] + + BITE22 --> C8_2((8)) + BITE23 --> C8_2 + BITE10 --> C15((15)) + BITE12 --> C15 + BITE19 --> C15 + FITE22 --> C15 + + C15 --> C10((10)) + + S05 --> STOP_T2_2[Stop t2] + STOP_T2_2 --> C7((7)) + C7 --> C9((9)) + + C8_2 --> FITE23[/FITE 23/] + FITE23 --> FOT[/FOT/] + FOT --> C6_2((6)) + C6_2 --> C7_2((7)) + +``` + +SDL diagram for Outgoing Signalling System No. 7 (TUP). + +FIGURE 3/Q.624 (sheet 7 of 10) +Outgoing Signalling System No. 7 (TUP) + +![Flowchart for Outgoing Signalling System No. 7 (TUP) logic starting from connector Z and ending at connector D. The flow includes various FITE, BITE, and SPITE processes, decision diamonds for service allowance and info availability, and timers t2.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Connector reference + +Z, D + +5, 15 + +5 + +5 + +5 + +``` + + graph TD + Z((Z)) --> FITE31[FITE 31 GSM] + Z --> BITE31GRQ[BITE 31 GRQ] + Z --> FITE1[FITE 1] + Z --> FITE22[FITE 22] + Z --> T2BAR[ $\bar{t}_2$ ] + + BITE31GRQ --> SPITE44[SPITE 44 Analyse info requested] + SPITE44 --> SPITE45{SPITE 45 In service allowed?} + SPITE45 -- No --> SPITE46{SPITE 46 Is info available?} + SPITE45 -- Yes --> SPITE46 + + SPITE46 -- No --> BITE31GRQ_2[BITE 31 GRQ] + BITE31GRQ_2 --> C5_7((5 7)) + + SPITE46 -- Yes --> SPITE48[SPITE 48 Construct GSM message] + SPITE48 --> GSM_OUT[GSM] + GSM_OUT --> C5_7_2((5 7)) + + FITE1 --> SAM_COMP{SAM complete?} + SAM_COMP -- No --> C5_7_3((5 7)) + SAM_COMP -- Yes --> START_T2[Start $t_2$ ] + START_T2 --> SAO_SAM[SAO/SAM] + SAO_SAM --> C5_7_4((5 7)) + SAO_SAM -.- NOTE_REF[Note] + + FITE22 --> STOP_T2[Stop $t_2$ ] + STOP_T2 --> C15_10((15 10)) + + T2BAR --> BITE19[BITE 19] + BITE19 --> D((D)) + D --> C5((5)) + +``` + +T1157690-93/d09 + +Flowchart for Outgoing Signalling System No. 7 (TUP) logic starting from connector Z and ending at connector D. The flow includes various FITE, BITE, and SPITE processes, decision diamonds for service allowance and info availability, and timers t2. + +NOTE – Digits should be forwarded to the outgoing link as soon as they are available. Multi digits SAMs should only be sent if more than one address digit is waiting. + +FIGURE 3/Q.624 (sheet 8 of 10) +**Outgoing Signalling System No. 7 (TUP)** + +![Flowchart for Outgoing Signalling System No. 7 (TUP) showing call processing steps: Wait for answer (SUB free), Answered, Clear back, and Re-answer. It includes connector references and various signaling elements like ANC, ANN, CFL, FITE 23, FITE 22, BITE 22, BITE 23, BITE 19, FOT, and BITE 25.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph TD + Start((7)) -- "7, 9" --> Wait[06 Wait for answer +(SUB free)] + Wait --> ANC[ANC] + Wait --> ANN[ANN] + Wait --> CFL[CFL] + Wait --> FITE23[FITE 23] + ANC --> BITE22{BITE 22} + ANN --> BITE23{BITE 23} + CFL --> BITE19{BITE 19} + FITE23 --> FOT1{FOT} + FITE23 --> FITE22_1[FITE 22] + BITE19 --> End15_1((15)) + FOT1 --> End7((7)) + FITE22_1 --> End15_2((15)) + BITE22 --> End8((8)) + BITE23 --> End8 + End8 -- "8, 15, 7, 15" --> Answered[07 Answered] + Answered --> ClearBack[Clear back] + Answered --> FITE23_2[FITE 23] + Answered --> FITE22_2[FITE 22] + ClearBack --> BITE25{BITE 25} + FITE23_2 --> FOT2{FOT} + FITE22_2 --> End15_3((15)) + BITE25 --> End9((9)) + FOT2 --> End8_2((8)) + End9 -- "9, 8" --> ClearBack_2[08 Clear back] + ClearBack_2 --> ReAnswer[Re-answer] + ClearBack_2 --> FITE23_3[FITE 23] + ClearBack_2 --> FITE22_3[FITE 22] + ReAnswer --> BITE24{BITE 24} + FITE23_3 --> FOT3{FOT} + FITE22_3 --> End15_4((15)) + BITE24 --> End8_3((8)) + FOT3 --> End9_2((9)) + End8_3 -- "8, 9" --> End9_3((9)) + T1157700-93/d10 + +``` + +Flowchart for Outgoing Signalling System No. 7 (TUP) showing call processing steps: Wait for answer (SUB free), Answered, Clear back, and Re-answer. It includes connector references and various signaling elements like ANC, ANN, CFL, FITE 23, FITE 22, BITE 22, BITE 23, BITE 19, FOT, and BITE 25. + +FIGURE 3/Q.624 (sheet 9 of 10) +**Outgoing Signalling System No. 7 (TUP)** + +![Flowchart for Outgoing Signalling System No. 7 (TUP) state transitions. The diagram shows a sequence of states and transitions starting from connector 15, through 'Clear forward', 'Start t3', 'Start t4', 'Wait for release guard', a 'Release guard' state with sub-transitions for t3 and t4, and finally reaching the 'Idle' state. Connector 10 is used as an intermediate and final connector. Connector 09 is on the 'Wait for release guard' state, and connector 00 is on the 'Idle' state. Connector 15 has associated message types: 3 (2x), 5, 7 (2x), 8, 9 (3x). Timeouts are t3 = 4-15 s and t4 = 1 min. A 'Procedure for timeout to out of service' is linked to connector P4.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Connector reference + +``` + +graph TD + C15((15)) -- "3 (2x), 5, 7 (2x), 8, 9 (3x)" --> CF1[Clear forward] + CF1 --> ST3[Start t3] + ST3 -.-> T3VAL["t3 = 4-15 s"] + ST3 --> ST4[Start t4] + ST4 -.-> T4VAL["t4 = 1 min"] + ST4 --> C10a((10)) + C10a --> S09([09 Wait for release guard]) + S09 --> RG[Release guard] + S09 --> T3TO[t3 timeout] + S09 --> T4TO[t4 timeout] + RG --> STP3[Stop t3] + STP3 --> STP4[Stop t4] + STP4 --> S00([00 Idle]) + T3TO --> ST3a[Start t3] + ST3a --> CF2[Clear forward] + CF2 --> C10b((10)) + T4TO --> CP4((P4)) + CP4 --- PROC[Procedure for timeout to out of service] + S00 --> C10c((10)) + +``` + +15 +3 (2x), +5, 7 (2x), +8, 9 (3x) + +15 + +Clear forward + +Start $t_3$     $[t_3 = 4-15\text{ s}]$ + +Start $t_4$     $[t_4 = 1\text{ min}]$ + +10 + +10 + +09 +Wait for release guard + +Release guard     $\bar{t}_3$     $\bar{t}_4$ + +Stop $t_3$     Start $t_3$     $P_4$ [Procedure for timeout to out of service] + +Stop $t_4$     Clear forward + +00 +Idle     10 + +10 + +T1157710-93/d11 + +Flowchart for Outgoing Signalling System No. 7 (TUP) state transitions. The diagram shows a sequence of states and transitions starting from connector 15, through 'Clear forward', 'Start t3', 'Start t4', 'Wait for release guard', a 'Release guard' state with sub-transitions for t3 and t4, and finally reaching the 'Idle' state. Connector 10 is used as an intermediate and final connector. Connector 09 is on the 'Wait for release guard' state, and connector 00 is on the 'Idle' state. Connector 15 has associated message types: 3 (2x), 5, 7 (2x), 8, 9 (3x). Timeouts are t3 = 4-15 s and t4 = 1 min. A 'Procedure for timeout to out of service' is linked to connector P4. + +FIGURE 3/Q.624 (sheet 10 of 10) +**Outgoing Signalling System No. 7 (TUP)** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.674-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.674-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.674-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.674-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.674-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bae27a994de4a60b5fae1953bce8119fdb35f415 --- /dev/null +++ b/marked/Q/T-REC-Q.674-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26cbd0c1eaffbccc664e67f2185f1163df311bd3b3252eda0c36ce9bbb580ac0 +size 146178 diff --git a/marked/Q/T-REC-Q.674-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.674-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58cff505cd4040abe21fd099eb62ab5b5c876d3d --- /dev/null +++ b/marked/Q/T-REC-Q.674-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a63d20230310f4bb88968452519d605dcc505e1693ca3658ea46692dd2cf2a2 +size 15648 diff --git a/marked/Q/T-REC-Q.674-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.674-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ddf0107e68b93231c5083c40aa22c9551682714 --- /dev/null +++ b/marked/Q/T-REC-Q.674-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bfbd8ce920e4c297a33bd291749212d2648d1fe72e64fa155a6b46e40809d81 +size 51716 diff --git a/marked/Q/T-REC-Q.674-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.674-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c30a3b148331a378b5b2cae0c52975778ae52aca --- /dev/null +++ b/marked/Q/T-REC-Q.674-198811-I_PDF-E/raw.md @@ -0,0 +1,291 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.674** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR +INTERWORKING OF SIGNALLING +SYSTEM R1 TO R2** + +**ITU-T Recommendation Q.674** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation Q.674 was published in Fascicle VI.6 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# LOGIC PROCEDURES FOR INTERWORKING OF SIGNALLING SYSTEM R1 TO R2 + +![State overview diagram for interworking of Signalling System R1 to R2. It shows a sequence of six states: 00, 01, 02, 03, 04, and 05. State 00 is Idle, 01 is Wait for ST-FITE, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear-back. Transitions are shown as arrows: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, and 05 back to 00. A label 'CCITT-48730' is present below the diagram.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 00 + 00 --> 01 + 01 --> 02 + 02 --> 03 + 03 --> 04 + 04 --> 05 + 05 --> 00 + state "00" as 00 + state "01" as 01 + state "02" as 02 + state "03" as 03 + state "04" as 04 + state "05" as 05 + +``` + +CCITT-48730 + +State overview diagram for interworking of Signalling System R1 to R2. It shows a sequence of six states: 00, 01, 02, 03, 04, and 05. State 00 is Idle, 01 is Wait for ST-FITE, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear-back. Transitions are shown as arrows: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, and 05 back to 00. A label 'CCITT-48730' is present below the diagram. + +| State number | State description | Sheet reference | +|---------------------|---------------------------|------------------------| +| 00 | Idle | 1, 2 | +| 01 | Wait for ST-FITE | 1 | +| 02 | Wait for address-complete | 1 | +| 03 | Wait for answer | 2 | +| 04 | Answered | 2 | +| 05 | Clear-back | 2 | + +FIGURE 1/Q.674 +State overview diagram for interworking of Signalling System R1 to R2 + +*Procedures not shown* + +The following procedure not directly relevant to interworking, is not shown in the logic procedures: + +P1 - Procedure for repeat attempt. + +FIGURE 2/Q.674 +Notes to interworking of Signalling System R1 to R2 + +Connector +reference + +![Flowchart for Interworking of Signalling System R1 to R2. The process starts with 'Idle' (00), followed by 'Activate interworking R1/R2' and 'Activate outgoing R2'. It then enters a loop of 'FITE 15' (with a note about alternatives 9-13), 'SPITE 22', 'FITE 2', and 'SPITE 21'. Depending on 'SPITE 21', it goes to 'FITE 4', 'FITE 5', 'FITE 7', or 'FITE 8' (with a note about FITE 6). All lead to connector '1'. Next is '01 Wait for ST-FITE'. From here, 'FITE 1' leads to 'Country code FITE'. If 'Yes', it goes to 'SPITE 22'. If 'No', it goes to 'FITE 1-ST'. 'SPITE 22' Yes leads to connector '1', No leads to connector '1'. 'FITE 1-ST' Yes leads to '02 Wait for address-complete'. '02 Wait for address-complete' leads to a parallel set of options: 'BITE 2' (to connector '5' with note '1(2x)'), 'BITEs 5, 6' (to connector '5'), 'BITEs 12, 13, 15, 16, 17, 20' (to connector '4'), 'BITE 11' (to 'Repeat attempt'), and 'FITE 22' (to connector '2'). 'Repeat attempt' Yes leads to connector 'P1', No leads to connector '4'. 'BITE 27' (from 'BITE 2') leads to connector '3'. 'BITE 28' (from 'SPITE 6') leads to 'Idle' (00). 'SPITE 6 Return appropriate tone' is reached from 'BITEs 12, 15, 20' via connector '4' with note '1(3x)'.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +00 Idle + +Activate interworking R1/R2 + +Activate outgoing R2 + +FITE 15 + +{ One of the FITEs 9-13 could be used to replace FITE 15 if the call was known to originate from an operator position, e.g. by analysis of path of entry, by use of pseudo country code } + +SPITE 22 + +Yes + +No + +FITE 2 + +SPITE 21 + +Yes + +No + +FITE 4 + +FITE 5 + +SPITE 21 + +Yes + +No + +FITE 7 + +FITE 8 + +{ FITE 6 may be used by bilateral agreement } + +1 + +01 Wait for ST-FITE + +FITE 1 + +BITE 2 + +BITEs 12, 15, 20 + +BITE 11 + +FITE 22 + +Country code FITE + +Yes + +No + +SPITE 22 + +No + +Yes + +1 + +FITE 1 + +FITE 1-ST + +No + +Yes + +02 Wait for address-complete + +BITE 2 + +BITEs 5, 6 + +BITEs 12, 13, 15, 16, 17, 20 + +BITE 11 + +FITE 22 + +5 1(2x) + +BITE 27 + +3 + +5 + +4 + +Repeat attempt + +Yes + +No + +P1 + +4 + +2 + +4 1(3x) + +SPITE 6 Return appropriate tone + +BITE 28 + +00 Idle + +Repeat attempt + +Yes + +No + +P1 + +4 + +2 + +1 + +4 + +5, 2 + +4 + +1 + +5 + +5, 4, 2 + +4 + +3 + +Flowchart for Interworking of Signalling System R1 to R2. The process starts with 'Idle' (00), followed by 'Activate interworking R1/R2' and 'Activate outgoing R2'. It then enters a loop of 'FITE 15' (with a note about alternatives 9-13), 'SPITE 22', 'FITE 2', and 'SPITE 21'. Depending on 'SPITE 21', it goes to 'FITE 4', 'FITE 5', 'FITE 7', or 'FITE 8' (with a note about FITE 6). All lead to connector '1'. Next is '01 Wait for ST-FITE'. From here, 'FITE 1' leads to 'Country code FITE'. If 'Yes', it goes to 'SPITE 22'. If 'No', it goes to 'FITE 1-ST'. 'SPITE 22' Yes leads to connector '1', No leads to connector '1'. 'FITE 1-ST' Yes leads to '02 Wait for address-complete'. '02 Wait for address-complete' leads to a parallel set of options: 'BITE 2' (to connector '5' with note '1(2x)'), 'BITEs 5, 6' (to connector '5'), 'BITEs 12, 13, 15, 16, 17, 20' (to connector '4'), 'BITE 11' (to 'Repeat attempt'), and 'FITE 22' (to connector '2'). 'Repeat attempt' Yes leads to connector 'P1', No leads to connector '4'. 'BITE 27' (from 'BITE 2') leads to connector '3'. 'BITE 28' (from 'SPITE 6') leads to 'Idle' (00). 'SPITE 6 Return appropriate tone' is reached from 'BITEs 12, 15, 20' via connector '4' with note '1(3x)'. + +CCITT-50281 + +FIGURE 3/Q.674 (Sheet 1 of 2) + +## Interworking of Signalling System R1 to R2 + +![State transition diagram for Signalling System R1 to R2 interworking. The diagram shows states 03 (Wait for answer), 04 (Answered), 00 (Idle), and 05 (Clear-back). Transitions are labeled with messages like BITE 21, FITE 22, and BITE 25. Connector references 3, 6, 2, and 2,6 are indicated on the left.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 03 : 3 + state "03 : Wait for answer" as 03 + state "04 : Answered" as 04 + state "00 : Idle" as 00 + state "05 : Clear-back" as 05 + + 03 --> BITE21_1 : BITE 21 + BITE21_1 --> 04 : 6 + 04 --> FITE22_1 : FITE 22 + FITE22_1 --> 2 + + 04 --> FITE22_2 : FITE 22 + FITE22_2 --> 00 : 1(2x), 2(2x) + 04 --> BITE25_1 : BITE 25 + BITE25_1 --> 05 + 05 --> FITE22_3 : FITE 22 + 05 --> BITE21_2 : BITE 21 + FITE22_3 --> 2 + BITE21_2 --> 6 + +``` + +Connector reference + +3 + +6 + +2 + +2 + +2, 6 + +State transition diagram for Signalling System R1 to R2 interworking. The diagram shows states 03 (Wait for answer), 04 (Answered), 00 (Idle), and 05 (Clear-back). Transitions are labeled with messages like BITE 21, FITE 22, and BITE 25. Connector references 3, 6, 2, and 2,6 are indicated on the left. + +CCITT-50290 + +FIGURE 3/Q.674 (Sheet 2 of 2) + Interworking of Signalling System R1 to R2 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.683-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.683-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.683-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.683-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.683-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c990b2e2cb640f1bb2eebee56855ec22ee0945a --- /dev/null +++ b/marked/Q/T-REC-Q.683-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e52d396eb5ceca1bc4c64933048446f7f6037d0bc31f30ab60a8119fb9f7534 +size 17737 diff --git a/marked/Q/T-REC-Q.683-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg b/marked/Q/T-REC-Q.683-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86fd94888b376f07fb7b8f2f5bc26c5dd04b82e2 --- /dev/null +++ b/marked/Q/T-REC-Q.683-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cc3779566d057f613c8c2e5cc1970a99499f5675272986daa3776f1c0667772 +size 139431 diff --git a/marked/Q/T-REC-Q.684-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.684-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24242cba917ff8515a309f9b35c3a85fb6759b8c --- /dev/null +++ b/marked/Q/T-REC-Q.684-198811-I_PDF-E/raw.md @@ -0,0 +1,194 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.684** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR +INTERWORKING OF SIGNALLING +SYSTEM R2 TO No. 7 (TUP)** + +**ITU-T Recommendation Q.684** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.684 was published in Fascicle VI.6 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# LOGIC PROCEDURES FOR INTERWORKING OF SIGNALLING SYSTEM R2 TO No. 7 (TUP) + +![State overview diagram showing states 00 through 06 with transitions between them. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for Z-digit, 03 is Wait for address-complete, 04 is Wait for answer, 05 is Answered, and 06 is Clear-back. Transitions are shown as arrows between adjacent states, with feedback loops from 01, 02, 03, 04, and 05 back to 00. A label 'CCITT-48690' is present near state 06.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +``` +graph LR; 00((00)) --> 01((01)); 01 --> 02((02)); 02 --> 03((03)); 03 --> 04((04)); 04 --> 05((05)); 05 --> 06((06)); 06 --> 00; 01 --> 00; 02 --> 00; 03 --> 00; 04 --> 00; 05 --> 00; +``` + +State overview diagram showing states 00 through 06 with transitions between them. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for Z-digit, 03 is Wait for address-complete, 04 is Wait for answer, 05 is Answered, and 06 is Clear-back. Transitions are shown as arrows between adjacent states, with feedback loops from 01, 02, 03, 04, and 05 back to 00. A label 'CCITT-48690' is present near state 06. + +| State number | State description | Sheet reference | +|---------------------|---------------------------|------------------------| +| 00 | Idle | 1, 2, 3 | +| 01 | Wait for CPCI-FITE | 1 | +| 02 | Wait for Z-digit | 1 | +| 03 | Wait for address-complete | 2 | +| 04 | Wait for answer | 2 | +| 05 | Answered | 2 | +| 06 | Clear-back | 3 | + +FIGURE 1/Q.684 + +State overview diagram for interworking of Signalling System R2 to No. 7 (TUP) + +FIGURE 2/Q.684 + +(Reserved for future notes) + +![Flowchart for interworking of Signalling System R2 to No. 7 (TUP).](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +``` + +graph TD + S00([00 Idle]) --> T1[Activate interworking R2/No. 7 TUP] + T1 --> S01([01 Wait for CPCI]) + S01 --- BUS[ ] + BUS --> F14[/FITE 14/] + BUS --> F16[/FITE 16/] + BUS --> F18[/FITE 18/] + BUS --> F19[/FITE 19/] + BUS --> F22[/FITE 22/] + F22 --> S00_2([00 Idle]) + F14 --> S02([02 Wait for Z-digit]) + S02 --> F1[/FITE 1/] + F1 --> S02 + S02 --> F9_15[/FITEs 9, 10, 11, 12, 13, 15/] + S02 --> F22_2[/FITE 22/] + F22_2 --> S00_3([00 Idle]) + F9_15 --> T2[Activate outgoing No. 7 TUP] + T2 --> D36{SPITE 36} + D36 -- No --> F25[/FITE 25/] + D36 -- Yes --> F26[/FITE 26/] + F25 --> F24[/FITE 24/] + F26 --> F24 + F24 --> D22{SPITE 22} + D22 -- No --> F2[/FITE 2/] + D22 -- Yes --> F3[/FITE 3/] + F2 --> D20{SPITE 20} + F3 --> D20 + D20 -- No --> F20[/FITE 20/] + D20 -- Yes --> F21[/FITE 21/] + F20 --> D21{SPITE 21} + F21 --> D21 + D21 -- No --> F4[/FITE 4/] + D21 -- Yes --> F5[/FITE 5/] + F4 --> C1((1)) + F5 --> C1 + +``` + +The flowchart illustrates the interworking process between Signalling System R2 and No. 7 (TUP). It begins with an 'Idle' state (00), followed by 'Activate interworking R2/No. 7 (TUP)' and 'Wait for CPCI' (01). A horizontal bus connects FITE 14, FITE 16, FITE 18, FITE 19, and FITE 22. FITE 22 leads to another 'Idle' state (00). FITE 14 leads to 'Wait for Z-digit' (02), which then connects to FITE 1, FITEs 9, 10, 11, 12, 13, 15, and FITE 22. FITE 22 from this stage leads to 'Idle' (00). The main path continues from FITEs 9-15 to 'Activate outgoing No. 7 (TUP)', which leads to decision SPITE 36. SPITE 36 'Yes' leads to FITE 26, and 'No' leads to FITE 25. Both FITE 25 and FITE 26 lead to FITE 24. FITE 24 leads to decision SPITE 22. SPITE 22 'Yes' leads to FITE 3, and 'No' leads to FITE 2. Both FITE 2 and FITE 3 lead to decision SPITE 20. SPITE 20 'Yes' leads to FITE 21, and 'No' leads to FITE 20. Both FITE 20 and FITE 21 lead to decision SPITE 21. SPITE 21 'Yes' leads to FITE 5, and 'No' leads to FITE 4. Both FITE 4 and FITE 5 lead to connector 1, which is labeled with a subscript 2. + +Flowchart for interworking of Signalling System R2 to No. 7 (TUP). + +CCITT - 60 421 + +12 + +FIGURE 3/Q.684 (Sheet 1 of 3) +**Interworking of Signalling System R2 to No. 7 (TUP)** + +![Flowchart for Interworking of Signalling System R2 to No. 7 (TUP). The diagram shows a sequence of decision diamonds and process blocks. It starts with 'Which 2-digit FITE' (1), leading to 'FITEs 9, 10, 11, 12, 13' (9-13) or 'Which category FITE' (15). The latter leads to 'FITE 17' (14, 16), 'FITE 18' (18), or 'FITE 19' (19). All lead to connector (2). Connector (2) leads to 'Any FITE 1's stored' (7). 'No' leads to connector (3) and 'Wait for address-complete' (03). 'Yes' leads to 'Country code FITE' (3). 'Yes' leads to 'FITE 1' (2) and 'SPITE 22' (2). 'No' leads to 'Omit country code FITE' (2). 'Wait for address-complete' (03) leads to 'FITE 1' (3), 'BITES 2, 4, 44, 46' (3), 'BITES 5, 7' (3), and 'BITES 3, 6' (3). These lead to 'BITE 2' (2), 'BITE 5' (2), and 'BITE 6' (2). 'BITE 2' leads to 'BITE 27' (2). All lead to 'Wait for answer' (04). 'Wait for answer' (04) leads to 'BITES 22, 23' (4) and 'FITE 22' (4). 'BITES 22, 23' leads to 'BITE 21' (6). 'FITE 22' leads to 'FITE 22' (6). Both lead to 'Answered' (05) and 'Idle' (00). 'Answered' leads to 'BITE 25' (4) and 'FITE 22' (4). 'Idle' leads to 'FITE 22' (4). 'BITE 25' leads to 'BITE 25' (5). All lead to connector (5). Connector (A) is also shown at the top right.](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +``` + +graph TD + 1((1)) --> D1{Which 2-digit FITE} + D1 -- "9-13" --> P1[/FITEs 9, 10, 11, 12, 13/] + D1 -- "15" --> D2{Which category FITE} + D2 -- "14, 16" --> P2[/FITE 17/] + D2 -- "18" --> P3[/FITE 18/] + D2 -- "19" --> P4[/FITE 19/] + P1 --> C2((2)) + P2 --> C2 + P3 --> C2 + P4 --> C2 + C2 --> D3{Any FITE 1's stored} + D3 -- No --> C3((3)) + D3 -- Yes --> D4{Country code FITE} + D4 -- Yes --> P5[/FITE 1/] + D4 -- No --> D5{SPITE 22} + D5 -- Yes --> D4 + D5 -- No --> P6[Omit country code FITE] + P5 --> C2 + P6 --> C2 + C3 --> P7([03 Wait for address-complete]) + P7 --> C_A((A)) + P7 --> P8[/FITE 1/] + P7 --> P9[/BITES 2, 4, 44, 46/] + P7 --> P10[/BITES 5, 7/] + P7 --> P11[/BITES 3, 6/] + P8 --> C3 + P9 --> P12[/BITE 2/] + P10 --> P13[/BITE 5/] + P11 --> P14[/BITE 6/] + P12 --> P15[/BITE 27/] + P13 --> P16([04 Wait for answer]) + P14 --> P16 + P15 --> P16 + P16 --> P17[/BITES 22, 23/] + P16 --> P18[/FITE 22/] + P17 --> P19[/BITE 21/] + P18 --> C4((4)) + P18 --> P20[/FITE 22/] + P19 --> C6((6)) + P19 --> P21([05 Answered]) + P20 --> C6 + P20 --> P22([00 Idle]) + P21 --> P23[/BITE 25/] + P21 --> P24[/FITE 22/] + P22 --> P24 + P23 --> P25[/BITE 25/] + P24 --> C4 + P25 --> C5((5)) + C4 --> C5 + C5 --> C3 + +``` + +Flowchart for Interworking of Signalling System R2 to No. 7 (TUP). The diagram shows a sequence of decision diamonds and process blocks. It starts with 'Which 2-digit FITE' (1), leading to 'FITEs 9, 10, 11, 12, 13' (9-13) or 'Which category FITE' (15). The latter leads to 'FITE 17' (14, 16), 'FITE 18' (18), or 'FITE 19' (19). All lead to connector (2). Connector (2) leads to 'Any FITE 1's stored' (7). 'No' leads to connector (3) and 'Wait for address-complete' (03). 'Yes' leads to 'Country code FITE' (3). 'Yes' leads to 'FITE 1' (2) and 'SPITE 22' (2). 'No' leads to 'Omit country code FITE' (2). 'Wait for address-complete' (03) leads to 'FITE 1' (3), 'BITES 2, 4, 44, 46' (3), 'BITES 5, 7' (3), and 'BITES 3, 6' (3). These lead to 'BITE 2' (2), 'BITE 5' (2), and 'BITE 6' (2). 'BITE 2' leads to 'BITE 27' (2). All lead to 'Wait for answer' (04). 'Wait for answer' (04) leads to 'BITES 22, 23' (4) and 'FITE 22' (4). 'BITES 22, 23' leads to 'BITE 21' (6). 'FITE 22' leads to 'FITE 22' (6). Both lead to 'Answered' (05) and 'Idle' (00). 'Answered' leads to 'BITE 25' (4) and 'FITE 22' (4). 'Idle' leads to 'FITE 22' (4). 'BITE 25' leads to 'BITE 25' (5). All lead to connector (5). Connector (A) is also shown at the top right. + +CCITT - 60431 + +FIGURE 3/Q.684 (Sheet 2 of 3) +Interworking of Signalling System R2 to No. 7 (TUP) + +Connector reference + +![Flowchart showing the interworking of Signalling System R2 to No. 7 (TUP). The diagram is divided into two main sections. The top section shows two separate signal paths: one starting from connector 5 (2) through 'Clear-back' (06), 'BITE 24', 'FITE 22', and 'BITE 21' to connector 6 (2); the other starting from connector B (3) through 'BITE 31', 'SPITE 48', and 'FITE 31' to connector 7 (2). The bottom section shows a more complex path starting from connector A (2) to a horizontal bus. From this bus, five branches emerge: 1) 'BITEs 14, 20' -> 'BITE 20' -> 'Idle' (00); 2) 'BITEs 15, 16, 17' -> 'BITEs 15, 16, 17' -> 'Repeat attempt procedure' (P1); 3) 'BITE 12' -> 'BITE 12' -> 'Repeat attempt' (Yes/No); 4) 'BITEs 9, 10, 19' -> 'Which BITE' (9, 10 / 19) -> 'BITE 11' or 'BITE 12' -> 'Idle' (00); 5) 'FITE 22' -> 'FITE 22' -> 'Idle' (00). Connector reference numbers 5, 4, 6, 7 are on the left, and A, B are on the bus.](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +Flowchart showing the interworking of Signalling System R2 to No. 7 (TUP). The diagram is divided into two main sections. The top section shows two separate signal paths: one starting from connector 5 (2) through 'Clear-back' (06), 'BITE 24', 'FITE 22', and 'BITE 21' to connector 6 (2); the other starting from connector B (3) through 'BITE 31', 'SPITE 48', and 'FITE 31' to connector 7 (2). The bottom section shows a more complex path starting from connector A (2) to a horizontal bus. From this bus, five branches emerge: 1) 'BITEs 14, 20' -> 'BITE 20' -> 'Idle' (00); 2) 'BITEs 15, 16, 17' -> 'BITEs 15, 16, 17' -> 'Repeat attempt procedure' (P1); 3) 'BITE 12' -> 'BITE 12' -> 'Repeat attempt' (Yes/No); 4) 'BITEs 9, 10, 19' -> 'Which BITE' (9, 10 / 19) -> 'BITE 11' or 'BITE 12' -> 'Idle' (00); 5) 'FITE 22' -> 'FITE 22' -> 'Idle' (00). Connector reference numbers 5, 4, 6, 7 are on the left, and A, B are on the bus. + +TI108980-87 + +FIGURE 3/Q.684 (Sheet 3 of 3) +**Interworking of Signalling System R2 to No. 7 (TUP)** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/028422d3e6ce272069a2b4f317c88474_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/028422d3e6ce272069a2b4f317c88474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71c7809bd9d494f49b6fbd8b114806e0fff221b0 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/028422d3e6ce272069a2b4f317c88474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c95d79e76569d941ed83271bd501437560a7a8e68d89451f4238eea55597348 +size 51178 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/1bc1746388cb64bf23b356ce2365dfc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45566f2e129c2d797453c825e395d095b1916a42 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/1bc1746388cb64bf23b356ce2365dfc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99ef4e18295eb39e2876f01ac3278608ad5049ae0674711f5bb9ad291bf312a9 +size 54701 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..940c8cc61b3a0b472e122b570fb04e9e9920c78f --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:240b4f1cd798edbf8e2e3865af9d5af100616e9e10129722027ce83f977cecc2 +size 57077 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..087707b48b90c19392763000fe358695c518a860 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:414dc659368330a5d42bc30854826efbe8db55bf7dca018829767f90066cc891 +size 56698 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0660fa30e9d6f1ad534b453f29e2fc622b3bb938 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2e3ca2fcbd91ed5602bb990c4cb2a138b0afa2c969f04ebabfd3ff0c5ab1bf9 +size 8209 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ffbda904c32b3116d1b4e09f957d0807441e362 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78de7dafe7dfc5a6198b802540ce27214d9dab72f3b835afbba815141d7e05ae +size 40055 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/40b80ef077f6151a9fbb593b8ad4864d_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/40b80ef077f6151a9fbb593b8ad4864d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1711afaa874e9d0c7d274474ef8a3a57a2a523e6 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/40b80ef077f6151a9fbb593b8ad4864d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b1461a142b9cd63b67c35b83b94c6ed1e808f38899d39e02e1a95932fa46945 +size 53820 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/50a63fe40eaa16cb8745c689fe8f8264_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/50a63fe40eaa16cb8745c689fe8f8264_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4244b959674565426680a264fcdc832088612c41 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/50a63fe40eaa16cb8745c689fe8f8264_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf50860148ac9cb3743d25f830685af6e429609830cd5491036b1ae64fde080 +size 83220 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1468a56f02737b0791bfea8f5bd75f02fddcc6d3 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/56f125e1bc127f7ac3d210407957413c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccdd8015d43914b67050ae138a04e754957470ef52287ad3402cce978d6c6a11 +size 41284 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff7ef5ef269f52ea933e75c9b111affbf4ae120c --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e685286a210d512758af758d5bf294219efb7d7f576516c4dfcdb4e8be218850 +size 48882 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/684fc3764b7e61b9a9f9e28c2f7ecde9_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/684fc3764b7e61b9a9f9e28c2f7ecde9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b5f769d770b2f95d5eba1244252c307ea7eecb0 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/684fc3764b7e61b9a9f9e28c2f7ecde9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cc709f0ae7d3d7d47f05a4592ac1fc519e648520b871ad7bade23a1cfd30cbd +size 74676 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/8768e42bf1062f1af11f259fc52a92e9_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/8768e42bf1062f1af11f259fc52a92e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eb41116e8a635c1b48c30579402b97bced7d400 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/8768e42bf1062f1af11f259fc52a92e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd619d24bbb75bef5fd86f8137391ced1c269b584c1bda8e3d77a24a35403edc +size 61946 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/88e677d1623f443e57a730fe04a495a5_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/88e677d1623f443e57a730fe04a495a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87f8b04a96ba2fc6893a3fdb9dc5c1f4ce2a259c --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/88e677d1623f443e57a730fe04a495a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b90d1d93076b3f3e8162bb058fc4a2048afa06227ed3e614c9f6a371ca74fa1a +size 59595 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88ea6afc96e4de9a9345c3f7072df49da68d70f6 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d2dd5e5b32a5c8313783b6cedd43ac13986a0305c83c992e668048205ee84d1 +size 51196 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/9874e3ac6f14360133f8e1674f79824f_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/9874e3ac6f14360133f8e1674f79824f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fdfa66f9068d95fc05d7a21870f090733af9742 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/9874e3ac6f14360133f8e1674f79824f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c16d1906e77d99e4c08fd89ba3eb27dc8202564cc199366fdb5345f466df0014 +size 57706 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b5790fea6e023e33991ea19328f289bb938546e --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4773152a25efaef3084e9c4fe4b7ba3fe01d9704859f3a2ef4b760726b3d41c +size 62563 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36416b5698c22a9aa0922cbed63782907821a7d6 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:827a6d6cfd65ffce0404d2fdd3b9cfc1a549317a8eaee2bfb450f0a3839a2236 +size 67383 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/a34a521d4a9ba7071e87adf963f12fa7_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/a34a521d4a9ba7071e87adf963f12fa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25d2e60caf5b7065aa9c9e469816977d8e942a54 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/a34a521d4a9ba7071e87adf963f12fa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:678ba092c14c09b9a9b365987edbf8b2d5885404595415b7fe2d6f761494512c +size 57253 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..483ac948eb85b12c02ebaa64ed041dc4653e68c5 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e5443dd59bd8a9270688ab87803b71156f1dafac94630f2839b267408e0541c +size 55293 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/b13465efdac63129aef9b6f1787d0d00_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9ed347066a63799c99e48714b8a36ad61df9e78 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:673377835ac6d03219de8b4b7c73b91d51d7a9ae5855f2d80d7a3e62b31cc7d5 +size 55267 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0189599691f60493e072343c21c06d14731c8d67 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17fe7484e7d9577d7cbb6595f0028a05c65a396bf9a8e74de1ded80adb0dd60c +size 48999 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/c5424b117a719524c619938e97c4cb1f_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/c5424b117a719524c619938e97c4cb1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51b7a5950647ad4de775c3da0465767872f6f430 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/c5424b117a719524c619938e97c4cb1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9e35ae8802c9b86124d8464e02befaa442b1988de1d0a0866897d5110cd911f +size 50722 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c9d739aa8ecfe10b9c80c87c2756d4b14c74126 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:854a742891e0a415c83691b4cda07cd5131f9e4b379a48db6811a870dd1bba06 +size 49243 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/d1be394c67ec994c0c8529d29ea3e9cc_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/d1be394c67ec994c0c8529d29ea3e9cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84337142c2781d826917bd77a8f5f3a8cf5ac6fd --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/d1be394c67ec994c0c8529d29ea3e9cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:202716f292d9cf1bcba3fa128e6dcbf16760dfb67943df035e7b8d3001ceb80c +size 46204 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70d9b5a851fe22861ae8a02e5cbe383ed1ec6f1f --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40be40ef271f582417177e7024f71227a9b32fde1c0f4a56112e9c5a18891417 +size 75713 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..274e717efaa6e3cebe4f9e30110752afa9645ccd --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e670f00138d7589c5b1d706c5243186bb488b59a4dfaf434be8dbdda8cbafe39 +size 51697 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f853b1788b6033cf16e9d7ee4549cbab137a0b40 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6539bf08167959a15790695b3d186db92069be897bb5a45e13b1db62d23fe88 +size 70780 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/db7a693cf26f527ac6c0d4d41da20858_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/db7a693cf26f527ac6c0d4d41da20858_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38771817df05539f30dc9558ca770bc7b48c9399 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/db7a693cf26f527ac6c0d4d41da20858_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4bb9441b95d71f3b0959305306baf1f99916b17e4c98116b199e67b86388aaf +size 56127 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/ed29f40262b821f88760fe2539d31090_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/ed29f40262b821f88760fe2539d31090_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..114d330ee1b9a80ffc0890e131671ec79b1eb62b --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/ed29f40262b821f88760fe2539d31090_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:007528c3c6d0a6ceecd3efcaa3e6e46e216a02dff406f6d57af53ac110e6305e +size 53431 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e687c2509a1a30fd5f833c25aca95dc3dd492213 --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7563f948ff5eee0716f5196bec9e39cf4f3c57d92fc987867444a7f80c1f27a +size 59380 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efe97a2fed45211616d396d0624b1336721be9ee --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3112f52a977f7d46722815eb2a08c178b419cfcbf0b9172039efca3500eacc6f +size 104628 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/f5698523df298c80a0c6b5d4ca657993_img.jpg b/marked/Q/T-REC-Q.699-199709-I_PDF-E/f5698523df298c80a0c6b5d4ca657993_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9775d8ee3aef31ee710354158b79de47f2bc4cd --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/f5698523df298c80a0c6b5d4ca657993_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3460088c03e4b2a8b4860126350581ac242563920bd5f4aaee0052e2af537d49 +size 58803 diff --git a/marked/Q/T-REC-Q.699-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.699-199709-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..50ead7a70875bec18a903641a4032b539b8147ed --- /dev/null +++ b/marked/Q/T-REC-Q.699-199709-I_PDF-E/raw.md @@ -0,0 +1,4419 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A diagonal line with an arrowhead points from the top-left towards the bottom-right, crossing the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.699** + +(09/97) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Interworking of Signalling Systems – Interworking between +Digital Subscriber Signalling System No. 1 and Signalling +System No. 7 + +--- + +**Interworking between ISDN access and +non-ISDN access over ISDN User Part of +Signalling System No. 7** + +ITU-T Recommendation Q.699 + +(Previously CCITT Recommendation) + +--- + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------------------------------------------------|---------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| General considerations | Q.600–Q.609 | +| Logic procedures | Q.610–Q.697 | +| Interworking of Signalling Systems No. 7 and No. 6 | Q.698 | +| Interworking between Digital Subscriber Signalling System No. 1 and Signalling System No. 7 | Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION Q.699** + +# **INTERWORKING BETWEEN ISDN ACCESS AND NON-ISDN ACCESS OVER ISDN USER PART OF SIGNALLING SYSTEM No. 7** + +## **Summary** + +This Recommendation defines the interworking between different types of access (ISDN and non-ISDN) and the ISDN User Part functions and protocol of Signalling System No. 7. + +## **Source** + +ITU-T Recommendation Q.699 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th September 1997. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------------------------------------------|-------------| +| 1 General..... | 1 | +| 1.1 Scope..... | 1 | +| 1.2 References..... | 1 | +| 1.3 Methodology..... | 3 | +| 1.4 Symbols and abbreviations ..... | 4 | +| 2 Outgoing call..... | 5 | +| 2.1 Interworking from DSS 1 to ISUP ..... | 5 | +| 2.1.1 Basic call..... | 5 | +| 2.1.2 Supplementary Services..... | 23 | +| 2.2 Interworking from non-ISDN access to ISUP..... | 58 | +| 2.2.1 Basic call..... | 58 | +| 2.2.2 Supplementary services ..... | 61 | +| 3 Incoming call ..... | 61 | +| 3.1 Interworking from ISUP to DSS 1 ..... | 61 | +| 3.1.1 Basic call..... | 61 | +| 3.1.2 Supplementary Services..... | 76 | +| 3.2 Interworking from ISUP to non-ISDN access..... | 104 | +| 3.2.1 Basic call..... | 104 | +| 3.2.2 Supplementary services ..... | 106 | +| Annex A – Interworking scenarios between subscriber access types interworking over SS 7
ISUP ..... | 106 | +| A.1 General..... | 106 | +| A.1.1 Scope ..... | 106 | +| A.1.2 Methodology..... | 106 | +| A.1.3 Symbols and abbreviations ..... | 106 | +| A.2 Interworking of ISDN accesses over ISUP ..... | 107 | +| A.2.1 Successful call set-up procedures/call flow diagrams for basic call control . | 108 | +| A.2.2 Unsuccessful call set-up procedures/call flow diagrams for basic call
control..... | 116 | +| A.2.3 Release procedures/call flow diagrams for basic call control..... | 123 | +| A.2.4 Simple segmentation procedures/call flow diagrams for basic call control .. | 124 | +| A.3 Interworking of ISDN access and non-ISDN access over ISUP ..... | 125 | +| A.3.1 Successful call set-up procedures/call flow diagrams ..... | 126 | +| A.3.2 Unsuccessful call set-up procedures/call flow diagrams ..... | 128 | +| A.3.3 Release procedures/call flow diagrams..... | 130 | + +| | Page | +|--------------------------------------------------------------------|-------------| +| A.3.4 Simple segmentation procedures ..... | 132 | +| A.4 Interworking of non-ISDN access over ISUP ..... | 132 | +| A.4.1 Successful call set-up procedures/call flow diagrams ..... | 133 | +| A.4.2 Unsuccessful call set-up procedures/call flow diagrams ..... | 134 | +| A.4.3 Release procedures/call flow diagrams..... | 136 | +| A.4.4 Suspend/resume procedures/call flow diagrams..... | 137 | + +# **INTERWORKING BETWEEN ISDN ACCESS AND NON-ISDN ACCESS OVER ISDN USER PART OF SIGNALLING SYSTEM No. 7** + +*(revised in 1997)* + +# **1 General** + +## **1.1 Scope** + +This Recommendation describes the interworking between different types of access (ISDN and non-ISDN) and the ISDN User Part functions and protocol of Signalling System No. 7 [1], [2], [3], [4]. The non-ISDN access defined in this Recommendation means the analogue line access except the PABX access. + +The interworking between the above signalling protocols occurs in an exchange with ISDN local exchange functionality and is specified in the context of a typical call in a pure ISDN or mixed ISDN/non-ISDN environment. + +## **1.2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation Q.761 (1993), *Functional description of the ISDN User Part of Signalling System No. 7*. +- [2] ITU-T Recommendation Q.762 (1993), *General function of messages and signals of the ISDN User Part of Signalling System No. 7*. +- [3] ITU-T Recommendation Q.763 (1993), *Formats and codes of the ISDN User Part of Signalling System No. 7*. +- [4] ITU-T Recommendation Q.764 (1993), *ISDN User Part signalling procedures*. +- [5] ITU-T Recommendation Q.850 (1993), *Use of cause and location in the digital subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part*. +- [6] ITU-T Recommendation Q.931 (1993), *ISDN user-network interface layer 3 specification for basic call control*. +- [7] ITU-T Recommendation Q.932 (1993), *Generic procedures for the control of ISDN supplementary services*. +- [8] ITU-T Recommendation Q.731 (1993), *Stage 3 description for number identification supplementary services using Signalling System No. 7*: + - Q.731.3, *Calling line identification presentation (CLIP)*. + - Q.731.4, *Calling line identification restriction (CLIR)*. + - Q.731.5, *Connected line identification presentation (COLP)*. + +- Q.731.6, *Connected line identification restriction (COLR)*. +- [9] ITU-T Recommendation Q.732 (1993), *Stage 3 description for the call offering supplementary services using Signalling System No. 7*: +- Q.732.2, *Call forwarding busy*. +- Q.732.3, *Call forwarding no reply*. +- Q.732.4, *Call forwarding unconditional*. +- Q.732.5, *Call deflection*. +- [10] ITU-T Recommendation Q.733 (1993), *Stage 3 description for call completion Supplementary Services using Signalling System No. 7*: +- Q.733.2, *Call Hold (CH)*. +- Q.733.4, *Terminal Portability (TP)*. +- [11] ITU-T Recommendation Q.734, *Stage 3 description for multiparty supplementary services using Signalling System No. 7*: +- Q.734.1 (1993), *Conference calling*. +- Q.734.2 (1996), *Three-party service*. +- [12] ITU-T Recommendation Q.735 (1993), *Stage 3 description for community of interest supplementary services using Signalling System No. 7*: +- Q.735.1, *Closed user group (CUG)*. +- Q.735.2, *Multi-level precedence and preemption*. +- [13] ITU-T Recommendation Q.737 (1993), *Stage 3 description for additional information transfer Supplementary Services using Signalling System No. 7*: +- Q.737.1, *User-to-user signalling (UUS)*. +- [14] ITU-T Recommendation Q.951 (1993), *Stage 3 description for number identification supplementary services using DSS I*: +- Q.951.3, *Calling line identification presentation (CLIP)*. +- Q.951.4, *Calling line identification restriction (CLIR)*. +- Q.951.5, *Connected line identification presentation (COLP)*. +- Q.951.6, *Connected line identification restriction (COLR)*. +- [15] ITU-T Recommendation Q.952 (1993), *Stage 3 description for call offering supplementary services using DSS I – Diversion supplementary services*. +- [16] ITU-T Recommendation Q.953 (1993), *Stage 3 description for call completion supplementary services using DSS I*: +- Q.953.2, *Call hold*.4 +- [17] ITU-T Recommendation Q.954, *Stage 3 description for multiparty supplementary services using DSS I*: +- Q.954.1 (1993), *Conference calling*. +- Q.954.2 (1995), *Three-party service*. + +- [18] ITU-T Recommendation Q.955 (1993), *Stage 3 description for community of interest supplementary services using DSS 1*. +Q.955.3, *Multi-level Precedence and Preemption (MLPP)*. +- [19] ITU-T Recommendation Q.957 (1993), *Stage 3 description for additional information transfer supplementary services using DSS 1*: +Q.957.1, *User-to-User Signalling (UUS)*. + +## 1.3 Methodology + +The procedures and elements of information that are not carried over the international interface (i.e. are defined for national use) are not described in this Recommendation, except for the interworking cases of the calling party number, connected number and redirection number when the national number can be used. + +The elements of information (parameters, information element and messages) that are of local significance only, i.e. are not mapped onto elements of information in the other signalling system, are not mentioned. + +Moreover, only the parameters and indicators being a matter of interworking are described. Hence, no information is given concerning e.g. the satellite indicator, the continuity check indicator, the echo control device indicator, the propagation delay counter parameter. + +In the same way, information to be sent in case of local fallback or local rejection of Supplementary Services are not relevant to interworking and therefore are not mentioned. + +### ISUP segmentation + +Some ISUP messages may indicate that they are followed by a Segmentation Message (SGM). The actions described in this Recommendation on receipt of such messages take place only after the completion of the segmentation procedure specified in 2.1.12/Q.764 [4]. + +When it is said in the text that a parameter is received in an ISUP message, in case of segmentation it could be received in the segmentation message (SGM) as well. + +ISUP messages which can be segmented and ISUP parameters which can be conveyed in a segmentation message (SGM) are described in 2.1.12/Q.764 [4]. + +### DSS 1 segmentation + +When it is said in the text that a specific DSS 1 message is received, in case of segmentation the content of this message is received in SEGMENT messages. + +The actions described in this Recommendation then take place only after the completion of the DSS 1 segmentation procedure specified in Annex H/Q.931 [6]. + +#### Handling of the cause and location fields + +When a cause parameter or information element has to be sent by the exchange, only the cause value is given in the text; the location indication is coded according to [5]. + +When a progress indicator information element has to be sent by the exchange, only the progress description is given in the text; the location indication is coded according to [5]. + +The handling of the diagnostic received in a cause parameter or in a cause information element is described in [5]. + +#### Services interactions + +Impacts of services interactions on interworking are not described. + +## 1.4 Symbols and abbreviations + +The ISUP messages are written in small letters, the DSS 1 messages in capital letters. + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------| +| 3PTY | Three-Party Service | +| ACM | Address Complete Message | +| ANM | Answer Message | +| ATP | Access Transport Parameter | +| BC | Bearer Capability information element | +| CGB | Circuit Group Blocking message | +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| COLP | Connected Line Identification Presentation | +| COLR | Connected Line Identification Restriction | +| CON | Connect message | +| CPG | Call Progress message | +| CUG | Closed User Group | +| CW | Call Waiting | +| DDI | Direct-Dialling-In | +| DSS 1 | Digital Subscriber Signalling System No. 1 | +| FAA | Facility Accepted message | +| FAR | Facility Request message | +| FRJ | Facility Reject message | +| GRS | Circuit Group Reset message | +| HLC | High Layer Compatibility information element | +| HOLD | Call HOLD | +| i.e. | information element | +| IAM | Initial Address Message | +| ind. | indicator | +| ISDN | Integrated Service Digital Network | +| ISUP | ISDN User Part | +| MLPP | Multi-Level Precedence and Preemption | +| MSN | Multiple Subscriber Number | +| p.i. | progress indicator information element | + +| | | +|-----|-------------------------------------------| +| REL | Release message | +| RES | Resume message | +| RSC | Reset Circuit message | +| SAM | Subsequent Address Message | +| SGM | Segmentation Message | +| SUB | Sub-addressing | +| SUS | Suspend message | +| TMR | Transmission Medium Requirement parameter | +| TMU | Transmission Medium Used parameter | +| TP | Terminal Portability | +| USI | User Service Information parameter | +| USR | User-to-user information message | +| UUS | User-to-User signalling | + +# 2 Outgoing call + +## 2.1 Interworking from DSS 1 to ISUP + +### 2.1.1 Basic call + +#### 2.1.1.1 Sending of the Initial Address Message (IAM) + +When the exchange has received from the calling user in a SETUP message (possibly followed by INFORMATION messages) enough information to determine that the call is to be routed to another exchange, it shall select a suitable, free, inter-exchange circuit and send an Initial Address Message (IAM). + +The coding of the Initial Address Message (IAM) according to the SETUP message is described hereafter. + +NOTE – The coding of the Initial Address Message (IAM) sent by a forwarding exchange is described in 2.5.2.5/Q.732 [9]. The parameters used in such a case are not mentioned hereafter. + +##### MANDATORY PARAMETERS + +###### Forward call indicators + +| | | | +|-----|---|----------------------------------------------| +| bit | A | National/international call indicator | +| | 0 | call to be treated as a national call | + +This bit can be set to "1" for international calls. + +| | | | +|-----|---|-------------------------------------------------------------------| +| bit | D | Interworking indicator | +| | 0 | no interworking encountered (No. 7 signalling all the way) | +| bit | F | ISDN User Part indicator | +| | 1 | ISDN User Part used all the way | + +| | | | +|------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------| +| bits | HG | ISDN User Part preference indicator | +| | 1 0 | ISDN User Part required all the way if required by the invoked telematic teleservices or Supplementary Services or by Recommendation E.172 | +| | 0 0 | ISDN User Part preferred all the way otherwise | +| bit | I | ISDN access indicator | +| | 1 | originating access ISDN | + +###### Calling party's category + +Coded according to internal data of the originating exchange. + +###### Transmission medium requirement + +If only one bearer capability information element is present in the SETUP message, the transmission medium requirement parameter is coded as described in Table 1. + +**Table 1/Q.699 – Coding of the transmission medium requirement parameter (TMR) +One BC received** + +| SETUP→ | | IAM→ | +|------------------------------------------------------------------|-----------------------------------|-------------------------------| +| Bearer capability information element | | Transmission medium | +| Information transfer capability | Information transfer rate | requirement parameter | +| Speech | Value non-significant | Speech | +| 3.1 kHz audio | Value non-significant | 3.1 kHz audio | +| Restricted digital information | For further studies | For further studies | +| Unrestricted digital information | 64 kbit/s unrestricted | 64 kbit/s unrestricted | +| | 2 × 64 kbit/s unrestricted | 2 × 64 kbit/s | +| | 384 kbit/s unrestricted | 384 kbit/s | +| | 1536 kbit/s unrestricted | 1536 kbit/s | +| | 1920 kbit/s unrestricted | 1920 kbit/s | +| or | | | +| Unrestricted digital information with tones/announcements | Multirate: 6 × 64 kbit/s | 384 kbit/s | +| | Multirate: 24 × 64 kbit/s | 1536 kbit/s | +| | Multirate: 30 × 64 kbit/s | 1920 kbit/s | +| Video | For further studies | For further studies | + +If two bearer capability information elements are present in the SETUP message, and: + +- if fallback occurs in the originating exchange when there is no circuit available being capable of satisfying the connection type requirements, the transmission medium requirement parameter is coded according to the first BC received (BC 1) as described in Table 1; +- if no fallback occurs in the originating exchange, the transmission medium requirement parameter is coded according to the second BC received (BC 2) as described in Table 2. + +**Table 2/Q.699 – Coding of the transmission medium requirement parameter (TMR) +Two BC received** + +| SETUP→ | IAM→ | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| Content | Transmission medium requirement parameter | +| Two BC received (Note):
BC 1 ( speech or 3.1 kHz audio )
BC 2 ( unrestricted digital information with tones and announcements ) | 64 kbit/s preferred | +| NOTE – BC 1 is the bearer capability information element received in first position in the SETUP message, BC 2 in second position. Bearer capability information elements shall be received in ascending order of priority as described in 5.11.1.1/Q.931 [6]. | | + +###### **Called party number** + +- Nature of address indicator: +According to the type of number field in the called party number information element and internal data of the originating exchange. +- Internal network number indicator: +1           *routing to internal network number not allowed* +- Numbering plan indicator: +001       *ISDN (telephony) numbering plan (Recommendation E.164)* +- Address signal: +According to the called number information received in the SETUP or INFORMATION messages. + +NOTE – The transport of the called party information in the keypad facility information element is network specific and therefore is not described here. + +##### **OPTIONAL PARAMETERS** + +###### **Calling party number** + +See 2.1.2.3 and 2.1.2.4. + +###### **Optional forward call indicators** + +- bits    BA    Closed user group call indicator: +See 2.1.2. +- bit      H      Connected line identity request indicator: +See 2.1.2. + +###### **Closed user group interlock code** + +See 2.1.2. + +###### **Connection request** + +See 2.1.2. + +###### User-to-user information + +See 2.1.2. + +###### Access transport + +**Table 3/Q.699 – Contents of the access transport parameter** + +| SETUP→ | IAM→ | +|---------------------------------|----------------------------| +| Content | Access transport parameter | +| Progress indicator | Progress indicator | +| High layer compatibility (Note) | High layer compatibility | +| Low layer compatibility | Low layer compatibility | + +NOTE – If two high layer compatibility information elements are received, they are transferred in the same order as received in the SETUP message in the access transport parameter of the initial address message. + +It may carry other information elements as well (as the called party subaddress). See 2.1.2. + +###### User service information + +**Table 4/Q.699 – Coding of the user service information parameter (USI)** + +| SETUP→ | IAM→ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Content | User service information parameter | +| One BC received:
BC | BC (Note 2) | +| Two BC received (Note 1):
BC 1 ( speech or 3.1 kHz audio )
BC 2 ( unrestricted digital information with tones and announcements ) | BC 1 (Note 2) | + +NOTE 1 – BC 1 is the bearer capability information element received in first position in the SETUP message, BC 2 in second position. Bearer capability information elements shall be received in ascending order of priority as described in 5.11.1.1/Q.931 [6]. + +NOTE 2 – Octet 1 (information element identifier) and 2 (length) of the bearer capability information element are not included. + +###### User-to-user indicators + +See 2.1.2. + +###### Generic number + +See 2.1.2. + +###### User service information prime + +This parameter is present only if two bearer capability information elements are received and if no fallback occurs in the originating exchange. It is coded as follows: + +**Table 5/Q.699 – Coding of the user service information prime parameter (USI prime)** + +| SETUP→ | IAM→ | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| Content | User service information prime parameter | +| Two BC received (Note 1):
BC 1 ( speech or 3.1 kHz audio )
BC 2 ( unrestricted digital information with tones and announcements ) | BC 2 (Note 2) | +| NOTE 1 – BC 1 is the bearer capability information element received in first position in the SETUP message, BC 2 in second position. Bearer capability information elements shall be received in ascending order of priority as described in 5.11.1.1/Q.931 [6].
NOTE 2 – Octets 1 (information element identifier) and 2 (length) of the bearer capability information element are not included. | | + +###### **User teleservice information** + +**Table 6/Q.699 – Coding of the user teleservice information parameter (UTI)** + +| SETUP→ | IAM→ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Content | User teleservice information parameter | +| One HLC received:
HLC | HLC (Note 2) | +| Two HLC received (Note 1):
HLC 1
HLC 2 | HLC 2 (Note 2) | +| NOTE 1 – HLC 1 Is the high layer compatibility information element received in first position in the SETUP message, HLC 2 in second position. High layer compatibility information elements shall be received in ascending order of priority as described in 5.12.1.1/Q.931 [6].
NOTE 2 – Octets 1 (information element identifier) and 2 (length) of the high layer compatibility information element are not included. | | + +###### **Generic notification** + +See 2.1.2. + +###### **Transmission medium requirement prime** + +This parameter is present only if two bearer capability information elements are received and if no fallback occurs in the originating exchange. It is coded as follows. + +**Table 7/Q.699 – Coding of the transmission medium requirement prime parameter (TMR prime)** + +| SETUP→ | IAM→ | +|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Content | Transmission medium requirement prime parameter | +| Two BC received:
BC 1 ( speech )
BC 2 ( unrestricted digital information with tones and announcements ) | Speech | +| Two BC received:
BC 1 ( 3.1 kHz audio )
BC 2 ( unrestricted digital information with tones and announcements ) | 3.1 kHz audio | + +###### **MLPP precedence** + +See 2.1.2. + +#### **2.1.1.2 Sending of the Subsequent Address Message (SAM)** + +If the initial address message has already been sent, and if the originating exchange has not determined that the called number information received was complete, the receipt of an INFORMATION message containing additional digits causes the sending of a Subsequent Address Message (SAM). + +#### **2.1.1.3 Receipt of the Address Complete Message (ACM)** + +##### **2.1.1.3.1 ACM with a cause parameter** + +**Table 8/Q.699 – Receipt of ACM with a cause parameter** + +| ←DISCONNECT | ←ACM | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Cause information element (Note 1)
Progress indicator No. 8 (Note 2) | Cause parameter
Optional backward call indicators parameter
In-band information ind. In-band info... | +| NOTE 1 – If the cause value received in the Address Complete Message (ACM) is unknown in DSS 1, the unspecified cause value of the class is sent.
NOTE 2 – The progress indicator No. 8 ( in-band information or an appropriate pattern is now available ) is only sent if the BC received in the SETUP message is coded speech , 3.1 kHz audio or unrestricted digital information with tones/announcements . | | + +##### **2.1.1.3.2 ACM without the cause parameter** + +Upon receiving an address complete message, the exchange shall send a message across the user-network interface to the calling user, as described in Table 9. + +**Table 9/Q.699 – Message sent to the DSS 1 upon receipt of ACM** + +| ←Message sent to the DSS 1 | ←ACM | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| | Backward call indicators parameter
Called party's status indicator | +| CALL PROCEEDING when not been sent before (Note 1), otherwise:
  • – PROGRESS if a progress indicator information element is to be sent (Note 2)
  • – No message if no progress indicator information element is to be sent (Note 2)
| 00 No indication | +| ALERTING | 01 Subscriber free | + +NOTE 1 – The receipt from the network of an Address Complete Message (ACM) without the *subscriber free* indication is interpreted by the network as a sending complete indication, in the case where the network couldn't determine it before. + +NOTE 2 – The sending of a progress indicator information element is described below. + +The backward message sent to the calling user (ALERTING, CALL PROCEEDING or PROGRESS message) is coded as follows. + +###### Bearer capability + +If the transmission medium used parameter or the bearer capability information element in the access transport parameter are present in the Address Complete Message (ACM) received, see handling of fallback information at the end of this subclause. + +###### Progress indicator + +Progress indicator information elements possibly present in the access transport parameter of the Address Complete Message (ACM) are transferred into the message sent to the calling user. + +In addition, progress indicator information elements are created by the originating exchange according to the coding of the Address Complete Message (ACM). Table 10 shows the sending criteria of each value. + +In case of fallback, a progress indicator No. 5 (*interworking has occurred and has resulted in a telecommunication service change*) is sent as well. See Tables 11 and 12. + +Every message sent to the access (ALERTING, CALL PROCEEDING or PROGRESS) may contain two progress indicator information elements. When more than two progress indicator information elements are to be sent, the supplementary progress indicator information elements are sent in a PROGRESS message. + +**Table 10/Q.699 – Sending criteria of the progress indicator information elements created by the originating exchange** + +| ←Message sent to the DSS 1
(See Table 9) | ←ACM | +|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Progress indicator information element | Content | +| No. 1
(Call is not end-to-end ISDN: further progress information may be available in-band) | Backward call indicators parameter
ISDN User Part indicator
0 ISDN User Part not used all the way | +| No. 2
(Destination address is non-ISDN) | Backward call indicators parameter
ISDN User Part indicator
1 ISDN User Part used all the way
ISDN access indicator
0 Terminating access non-ISDN | +| No. 8 (Note)
(In-band information or appropriate pattern now available) | Optional backward call indicators parameter
In-band information indicator
1 In-band info... | + +NOTE – The progress indicator No. 8 (*in-band information or an appropriate pattern is now available*) is only sent if the BC received in the SETUP message is coded *speech, 3.1 kHz audio or unrestricted digital information with tones/announcements*. + +###### **High layer compatibility** + +If a high layer compatibility information element is present in the access transport parameter of the Address Complete Message (ACM), see handling of fallback information at the end of this subclause. + +###### **Notification indicator** + +See 2.1.2. + +###### **Redirecting number** + +See 2.1.2. + +###### **Redirection number** + +See 2.1.2. + +###### **Facility** + +See 2.1.2. + +###### **User-user** + +This information element cannot be included in the CALL PROCEEDING message. + +See 2.1.2. + +###### Handling of fallback information + +If the Transmission Medium Used parameter (TMU) is present in the Address Complete Message (ACM), and if no progress indicator No. 1 (*call is not end-to-end ISDN*) or No. 2 (*destination address is non-ISDN*) has to be sent, the Table 11 is applicable. + +**Table 11/Q.699 – Sending of BC fallback information** + +| ←Message sent to DSS 1 | ←ACM | +|----------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| BC = Speech
p.i. No. 5 | TMU Speech
ATP No BC | +| BC = 3.1 kHz audio
p.i. No. 5 | TMU 3.1 kHz audio
ATP No BC | +| BC received in the ATP
( speech or 3.1 kHz audio )
p.i. No. 5 | TMU Speech or 3.1 kHz audio
ATP BC
( speech or 3.1 kHz audio ) | + +If a high layer compatibility information element is present in the access transport parameter of the Address Complete Message (ACM), and if no progress indicator No. 1 (*call is not end-to-end ISDN*) or No. 2 (*destination address is non-ISDN*) has to be sent, Table 12 is applicable. + +**Table 12/Q.699 – Sending of HLC fallback information** + +| ←Message sent to DSS 1 | ←ACM | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Content | Access transport parameter | +| HLC
Progress indicator No. 5 | HLC
Progress indicator No. 5 | +| NOTE – If procedures of BC fallback and HLC fallback both require the sending of the progress indicator No. 5, only one progress indicator No. 5 is sent. | | + +#### 2.1.1.4 Receipt of the Call Progress message (CPG) + +##### 2.1.1.4.1 CPG with a cause parameter + +**Table 13/Q.699 – Receipt of CPG with a cause parameter** + +| ←DISCONNECT | ←CPG | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cause information element
(Note 1) | Cause parameter | +| Progress indicator No. 8
(Note 2) | Event information parameter
Event indicator In-band info...
or
Optional backward call indicators parameter
In-band information ind. In-band info... | + +NOTE 1 – If the cause value received in the Call Progress Message (CPG) is unknown in DSS 1, the unspecified cause value of the class is sent. +NOTE 2 – The progress indicator No. 8 (*in-band information or an appropriate pattern is now available*) is only sent if the BC received in the SETUP message is coded *speech, 3.1 kHz audio or unrestricted digital information with tones/announcements*. + +##### 2.1.1.4.2 CPG without the cause parameter + +Upon receiving a Call Progress message (CPG), the exchange shall send a message across the user-network interface to the calling user, as described in Table 14. + +**Table 14/Q.699 – Message sent to the DSS 1 upon receipt of CPG** + +| ←Message sent to the DSS 1 | ←CPG | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| | Event information parameter
Event indicator | +| ALERTING when not been sent before, otherwise:
– PROGRESS if a progress indicator information element is to be sent (Note)
– No message if no progress indicator information element is to be sent (Note) | 000 0001 ( alerting ) | +| – PROGRESS if a progress indicator information element is to be sent (Note)
– No message if no progress indicator information element is to be sent (Note) | 000 0010 ( progress )
or
000 0011 ( in-band information or an appropriate pattern is now available ) | + +NOTE – The sending of a progress indicator information element is described below. + +The backward message sent to the calling user (ALERTING or PROGRESS message) is coded as follows. + +###### Bearer capability + +If the transmission medium used parameter or the bearer capability information element in the access transport parameter are present in the Call Progress message (CPG) received, see handling of fallback information at the end of this subclause. + +###### Progress indicator + +Progress indicator information elements possibly present in the access transport parameter of the Call Progress Message (CPG) are transferred into the message sent to the calling user. + +In addition, progress indicator information elements are created by the originating exchange according to the coding of the Call Progress Message (CPG). Table 15 shows the sending criteria of each value. + +In case of fallback, a progress indicator No. 5 (*interworking has occurred and has resulted in a telecommunication service change*) is sent as well. See Tables 11 and 12. + +Every message sent to the access (ALERTING or PROGRESS) may contain two progress indicator information elements. When more than two progress indicator information elements are to be sent, the supplementary progress indicator information elements are sent in a PROGRESS message. + +**Table 15/Q.699 – Sending criteria of the progress indicator information elements created by the originating exchange** + +| ←Message sent to the DSS 1
(See Table 9) | ←CPG | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Progress indicator information element | Content
(Note 2) | +| No. 1
(Call is not end-to-end ISDN: further progress information may be available in-band) | Backward call indicators parameter
ISDN User Part indicator
0 ISDN User Part not used all the way | +| No. 2
(Destination address is non-ISDN) | Backward call indicators parameter
ISDN User Part indicator
1 ISDN User Part used all the way
ISDN access indicator
0 Terminating access non-ISDN | +| No. 4
(Call has returned to the ISDN) | Backward call indicators parameter
ISDN User Part indicator
1 ISDN User Part used all the way
ISDN access indicator
1 Terminating access ISDN whereas the last indication received was "0", Terminating access non-ISDN | +| No. 8 (Note 1)
(In-band information or appropriate pattern now available) | Event information parameter
Event indicator
000 0011 In-band info ... | +| No. 8 (Note 1)
(In-band information or appropriate pattern now available) | Optional backward call indicators parameter
In-band information indicator
1 In-band info ... | +| NOTE 1 – The progress indicator No. 8 ( in-band information or an appropriate pattern is now available ) is only sent if the BC received in the SETUP message is coded speech, 3.1 kHz audio or unrestricted digital information with tones and announcements . | | +| NOTE 2 – The mapping of the contents in the CPG message is only relevant if the information received in the message is different compared to earlier received information, e.g. in the ACM message or a CPG message received prior to this message. | | + +###### **High layer compatibility** + +If a high layer compatibility information element is present in the access transport parameter of the Call Progress message (CPG), see handling of fallback information at the end of this subclause. + +###### **Notification indicator** + +See 2.1.2. + +###### **Redirecting number** + +See 2.1.2. + +###### **Redirection number** + +See 2.1.2. + +###### **Facility** + +See 2.1.2. + +###### **User-user** + +See 2.1.2. + +##### **Handling of fallback information** + +See 2.1.1.3.2. + +#### **2.1.1.5 Receipt of the Answer Message (ANM)** + +Upon receipt of an Answer Message (ANM), the exchange shall send a CONNECT message across the user-network interface to the calling user. + +The CONNECT message is coded as follows. + +##### **Bearer capability** + +See handling of fallback information at the end of this subclause. + +##### **Progress indicator** + +Progress indicator information elements possibly present in the access transport parameter of the Answer Message (ANM) are transferred into the CONNECT message sent to the calling user. + +In addition, progress indicator information elements are created by the originating exchange according to the coding of the backward call indicators parameter possibly received in the Answer Message (ANM). Table 16 shows the sending criteria of each value. + +In case of fallback, a progress indicator No. 5 (*interworking has occurred and has resulted in a telecommunication service change*) is sent as well. See Tables 17 and 18. + +The CONNECT message sent to the access may contain two progress indicator information elements. + +When more than two progress indicator information elements are to be sent, the supplementary progress indicator information elements are sent in a PROGRESS message. + +**Table 16/Q.699 – Sending criteria of the progress indicator information elements created by the originating exchange** + +| ←CONNECT | ←ANM | +|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Progress indicator information element | Content | +| No. 1
(Call is not end-to-end ISDN: further progress information may be available in-band) | Backward call indicators parameter
ISDN User Part indicator
0 ISDN User Part not used all the way | +| No. 2
(Destination address is non-ISDN) | Backward call indicators parameter
ISDN User Part indicator
1 ISDN User Part used all the way
ISDN access indicator
0 terminating access non-ISDN | +| No. 4
(Call has returned to the ISDN) | Backward call indicators parameter
ISDN User Part indicator
1 ISDN User Part used all the way
ISDN access indicator
1 terminating access ISDN whereas the last indication received was "0" terminating access non-ISDN | + +##### **High layer compatibility** + +If a high layer compatibility information element is present in the access transport parameter of the call Answer Message (ANM), see handling of fallback information at the end of this subclause. + +##### **Low layer compatibility** + +The low layer compatibility possibly present in the access transport parameter of the Answer Message (ANM) is passed on unchanged. + +##### **Notification indicator** + +See 2.1.2. + +##### **Redirecting number** + +See 2.1.2. + +##### **Redirection number** + +See 2.1.2. + +##### **Facility** + +See 2.1.2. + +##### **User-user** + +See 2.1.2. + +##### Connected number + +See 2.1.2. + +##### Connected subaddress + +See 2.1.2. + +##### Handling of fallback information + +If the Transmission Medium Used parameter (TMU) is present in the Answer Message (ANM), or if a bearer capability information element is present in the access transport parameter of the Answer Message, and if no progress indicator No. 1 (*call is not end-to-end ISDN*) or No. 2 (*destination address is non-ISDN*) has to be sent, Table 17 is applicable. + +**Table 17/Q.699 – Sending of BC fallback information** + +| ←CONNECT | ←ANM | | +|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--| +| BC
( Unrestricted digital information with tones and announcements ) | No TMU
ATP BC
( unrestricted digital information with tones and announcements ) | | +| BC = Speech
p.i. No. 5 | TMU Speech
ATP No BC | | +| BC = 3.1 kHz audio
p.i. No. 5 | TMU 3.1 kHz audio
ATP No BC | | +| BC received in the ATP
( speech or 3.1 kHz audio ) | TMU Speech or 3.1 kHz audio
ATP BC
( speech or 3.1 kHz audio ) | | +| BC received in the ATP
( speech or 3.1 kHz audio )
p.i. No. 5 | TMU Speech or 3.1 kHz audio
ATP BC
( speech or 3.1 kHz audio )
p.i. No. 5 | | + +If a high layer compatibility information element is present in the access transport parameter of the Answer Message (ANM), and if no progress indicator No. 1 (*call is not end-to-end ISDN*) or No. 2 (*destination address is non-ISDN*) has to be sent, Table 18 is applicable. + +**Table 18/Q.699 – Sending of HLC fallback information** + +| ←CONNECT | ←ANM | +|---------------------------------|---------------------------------| +| Content | Access transport parameter | +| HLC | HLC | +| HLC
Progress indicator No. 5 | HLC
Progress indicator No. 5 | +| no HLC | no HLC | + +NOTE – If procedures of BC fallback and HLC fallback both require the sending of the progress indicator No. 5, only one progress indicator No. 5 is sent. + +#### **2.1.1.6 Receipt of the Connect message (CON)** + +Upon receiving a Connect message (CON), the exchange shall send a CONNECT message across the user-network interface to the calling user. + +The CONNECT message is coded as follows. + +##### **Bearer capability** + +See handling of fallback information at the end of this subclause. + +##### **Progress indicator** + +Progress indicator information elements possibly present in the access transport parameter of the Connect message (CON) are transferred into the CONNECT message sent to the calling user. + +In case of fallback, a progress indicator No. 5 (*interworking has occurred and has resulted in a telecommunication service change*) is sent as well: see Tables 17 and 18. + +The CONNECT message sent to the access may contain two progress indicator information elements. + +##### **High layer compatibility** + +If a high layer compatibility information element is present in the access transport parameter of the call Connect message (CON), see handling of fallback information at the end of this subclause. + +##### **Low layer compatibility** + +The low layer compatibility possibly present in the access transport parameter of the Connect message (CON) is passed on unchanged. + +##### **Notification indicator** + +See 2.1.2. + +##### **Redirecting number** + +See 2.1.2. + +##### **Redirection number** + +See 2.1.2. + +##### **Facility** + +See 2.1.2. + +##### **User-user** + +See 2.1.2. + +##### **Connected number** + +See 2.1.2. + +##### **Connected subaddress** + +See 2.1.2. + +##### **Handling of fallback information** + +See 2.1.1.5. + +#### 2.1.1.7 Receipt of the release message (REL) + +**Table 19/Q.699 – Receipt of the Release message (REL)** + +| ←DISCONNECT | ←REL | +|-----------------------------------|-------------------| +| Cause information element | Cause parameter | +| Cause value No. x (Notes 1 and 2) | Cause value No. x | + +NOTE 1 – If the cause value received in the Release message (REL) is unknown in DSS 1, the unspecified cause value of the class is sent. +NOTE 2 – Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some causes values; see 2.1.2. + +The handling of the other parameters is described in 2.1.2. + +The receipt of the release message (REL) during the user suspend/resume procedure is described in 2.1.2. + +#### 2.1.1.8 Sending of the Release message (REL) + +**Table 20/Q.699 – Call clearing from the user** + +| DISCONNECT,
RELEASE
RELEASE COMPLETE→ | REL→ | +|---------------------------------------------|--------------------------------------| +| Cause information element | Cause parameter | +| Cause value No. x | Cause value No. x
(Notes 1 and 2) | + +NOTE 1 – If the cause value received in the DSS 1 message is unknown in ISUP, the unspecified cause value of the class is sent. +NOTE 2 – Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values; see 2.1.2. + +#### 2.1.1.9 Receipt of Reset Circuit message (RSC), Circuit Group Reset message (GRS) or Circuit Group Blocking message (CGB) with the indication *hardware failure oriented* + +Table 21 shows the message sent to the calling user upon receipt of either a RSC message, GRS message or CGB message with the indication *hardware failure oriented*, when at least one backward message relating to the call has already been received. + +**Table 21/Q.699 – Receipt of RSC, GRS or CGB messages** + +| ←DISCONNECT | ←Message received from ISUP | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cause information element | | +| Cause value No. 31
Normal, unspecified | Reset Circuit message (RSC) | +| Cause value No. 31
Normal, unspecified | Circuit Group Reset message (GRS) | +| Cause value No. 31
Normal, unspecified | Circuit Group Blocking message (CGB)
with the type indicator of the circuit group
supervision message type indicator parameter
coded "01" ( hardware failure oriented ) | + +#### 2.1.1.10 DSS 1 data link reset and data link failure procedures + +The data link reset and data link failure procedures are respectively described in 5.8.8/Q.931 and 5.8.9/Q.931 [6]. + +**Table 22/Q.699 – DSS 1 data link reset and data link failure procedures** + +| ←DISCONNECT | Trigger event | REL→ | +|--------------------------------------------------|----------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Cause information element | | Cause parameter | +| Cause value No. 41
(temporary failure) | Data link reset in overlap sending state | Cause value No. 41
(temporary failure) | +| (Note) | Data link failure in an other state than active state | Cause value No. 27
(destination out of order) | +| (Note) | Failure of the data link reestablishment procedure after a data link failure in active state | Cause value No. 27
(destination out of order) | + +NOTE – The call is cleared internally. No DISCONNECT message is sent on the access. + +#### 2.1.1.11 Receipt of the Suspend message (SUS) network initiated + +The actions taken on the ISUP side upon receipt of the Suspend message (SUS) are described in 2.4.1/Q.764 [4]. + +No action is taken on the DSS 1 side. + +#### 2.1.1.12 Receipt of the Resume message (RES) network initiated + +The actions taken on the ISUP side upon receipt of the Resume message (RES) are described in 2.4.1/Q.764 [4]. + +No action is taken on the DSS 1 side. + +#### 2.1.1.13 Release by the exchange + +**Table 23/Q.699 – Release from the originating exchange** + +| ←DISCONNECT | Trigger event | REL→ | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| Cause information element | | Cause parameter | +| Cause value No. 28
Invalid number format
(address incomplete) | Determination that the called number information received is incomplete, after an IAM message has already been sent | Cause value No. 28
Invalid number format
(address incomplete) | +| Cause value No. 31
normal, unspecified | Failure of the automatic repeat attempt procedure | No action | +| Cause value No. 16
normal call clearing | T6 expiry (Note 1) | Cause value No. 102
recovery on timer expiry | +| Cause value No. 97 or No. 99 | Call release due to the ISUP compatibility procedure | Cause value No. 97 or No. 99 | +| Same cause value as in the REL message (Note 2) | Other cases of failure on the ISUP side | Cause value coded according to [4] | +| Cause value coded according to [6] | Other cases of failure on the DSS 1 side | Same cause value as in the DISCONNECT message (Note 3) | + +NOTE 1 – T6: awaiting resume message (RES) timer. T6 start, stop, and expiry are described in 2.4/Q.764 and Annex A/Q.764 [4]. + +NOTE 2 – If the cause value sent in the REL message is unknown in DSS 1, the unspecified cause value of the class is sent. + +NOTE 3 – If the cause value sent in the DISCONNECT message is unknown in ISUP, the unspecified cause value of the class is sent. + +### 2.1.2 Supplementary Services + +#### 2.1.2.1 Direct-Dialling-In (DDI) + +There is no interworking requirement relating to the direct-dialling-in supplementary service. + +#### 2.1.2.2 Multiple Subscriber Number (MSN) + +There is no interworking requirement relating to the multiple subscriber number supplementary service. + +#### 2.1.2.3 Calling Line Identification Presentation (CLIP) + +The mapping shown in 2.1.2.3.1 forms part of basic call. + +##### 2.1.2.3.1 Special arrangement applies + +**Table 24/Q.699 – CLIP – Special arrangement applies** + +| SETUP→ | | IAM→ | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|------------------------------------------------------------------------------------------|---------------------------------------|---------------------------------------------|----------------------------------------------| +| Calling party number i.e. | | Coding of the calling party number and generic number parameters | | | | +| Type of number | Numbering plan identification | Address signals | Numbering plan indicator | Nature of address indicator | Screening indicator | +| No or invalid (Note 1)
calling party number
information element | | Calling party number parameter | | | | +| | | Default number | 001
ISDN
numbering plan | 000 0011
National
number | 11
Network
provided | +| | | No generic number parameter
indicating additional calling party number is sent | | | | +| National
number | | Calling party number parameter | | | | +| | | Default number | 001
ISDN
numbering plan | 000 0011
National
number | 11
Network
provided | +| | | Generic number parameter (Note 2) | | | | +| | | Number
provided by the
user | 001
ISDN
numbering plan | 000 0011
National
number | 00
User provided,
not verified | +| International
number | | Calling party number parameter | | | | +| | | Default number | 001
ISDN
numbering plan | 000 0011
National
number | 11
Network
provided | +| | | Generic number parameter (Note 2) | | | | +| | | Number
provided by the
user | 001
ISDN
numbering plan | 000 0100
International
number | 00
User provided,
not verified | +| NOTE 1 – Validity conditions of the calling party number information element are defined in 3.5.2.1/Q.951 [14]. | | | | | | +| NOTE 2 – The generic number parameter contains the number qualifier indicator coded "00000110" ( additional calling party number ). | | | | | | + +The address presentation restricted indicator of the calling party number and generic number parameters shall be set according to the CLIR supplementary service. + +The calling party number incomplete indicator of the calling party number and the generic number parameters shall be set to "0" (*complete*). + +###### Calling party subaddress + +If provided, the calling party subaddress is transported transparently in the access transport parameter. + +##### 2.1.2.3.2 Special arrangement does not apply + +**Table 25/Q.699 – CLIP – Special arrangement does not apply** + +| SETUP→ | | | IAM→ | | | | +|-----------------------------------------------------------------------------------------------|-------------------------------|---------------|---------------------------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------------------------|-------------------------------------------------| +| Calling party number information element | | | Coding of the calling party number and generic number parameters | | | | +| Type of number | Numbering plan identification | Number digits | Address signals | Numbering plan indicator | Nature of address indicator | Screening indicator | +| No or invalid (Note) calling party number information element | | | Calling party number parameter | | | | +| | | | Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | +| | | | No generic number parameter indicating additional calling party number is sent | | | | +| Failure of the screening function | | | Calling party number parameter | | | | +| | | | Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | +| | | | No generic number parameter indicating additional calling party number is sent | | | | +| Subscriber number
or
National number
or
International number | | | Calling party number parameter | | | | +| | | | Number provided by the user | 001
ISDN numbering plan | 000 0011
National number , or
000 0100
International Number | 01
User provided, verified and passed | +| | | | No generic number parameter indicating additional calling party number is sent | | | | +| Unknown | | | Calling party number parameter | | | | +| | | | Completion of the number provided by the user | 001
ISDN numbering plan | 000 0011
National number | 01
User provided, verified and passed | +| | | | No generic number parameter indicating additional calling party number is sent | | | | +| ISDN/telephony numbering plan
or
Unknown | | | Correct complete number | | | | +| Unknown | | | Incomplete number | | | | + +NOTE – Validity conditions of the calling party number information element are defined in 3.5.2.1/Q.951 [14]. + +The address presentation restricted indicator of the calling party number parameter shall be set according to the CLIR supplementary service. + +The calling party number incomplete indicator of the calling party number parameters shall be set to "0" (*complete*). + +###### Calling party subaddress + +If provided, the calling party subaddress is transported transparently in the access transport parameter. + +#### 2.1.2.4 Calling Line Identification Restriction (CLIR) + +The address presentation restricted indicator of the calling party number and of the generic number parameters is coded as described in Table 26. + +NOTE – If the calling user has not subscribed the CLIR supplementary service, the address presentation restricted indicator of the calling party number parameter is set to *presentation allowed* (see 4.10/Q.951 [14]). + +**Table 26/Q.699 – Coding of the address presentation restricted indicator of the calling party number and generic number parameters** + +| Internal data | | SETUP→ | IAM→ | +|----------------|--------------------------------|------------------------------------------|-----------------------------------------------| +| Permanent mode | Temporary mode default setting | Calling party number information element | Calling party number/generic number parameter | +| | | Presentation indicator | Address presentation restricted indicator | +| Yes | Value non-significant | Value non-significant | Presentation restricted | +| No | Restricted | Presentation restricted | Presentation restricted | +| | | Absent | Presentation restricted | +| | | Presentation allowed | Presentation allowed | +| | Allowed | Presentation allowed | Presentation allowed | +| | | Absent | Presentation allowed | +| | | Presentation restricted | Presentation restricted | + +#### 2.1.2.5 Connected Line Identification Presentation (COLP) + +If the calling user is provided with the COLP supplementary service, the connected line identity request indicator of the optional forward call indicators parameter in the Initial Address Message (IAM) is coded to *requested*. + +If the calling user is provided with the COLP supplementary service, only one connected number information element is sent in the CONNECT message. + +**Table 27/Q.699 – COLP information sent to the calling user** + +| ←CONNECT | ←ANM/CON | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| COLP information sent to the calling user | Connected number parameter | Generic number parameter with number qualifier set to additional connected number | +| | Address presentation restricted indicator | | +| Connected number i.e.
(see Table 28) | Presentation allowed | Absent | +| Connected number i.e.
(see Table 28) | Presentation allowed | Present | +| Connected number i.e.
Option 1:
Type of number   As received
Numbering plan   As received
Presentation ind. Presentation restricted
Screening ind.   As received
Number digits   No digit

Option 2:
Type of number Unknown
Numbering plan Unknown
Presentation ind. Presentation restricted
Screening ind. Network provided
Number digits   No digit | Presentation restricted
(Note ) | Value non-significant | +| Connected number i.e.
Type of number Unknown
Numbering plan Unknown
Presentation ind. Not available due to interworking
Screening ind. Network provided
Number digits   No digit | Address not available
or
No connected number parameter | Value non-significant | + +NOTE – As a national option, the presentation restriction indication received in the connected number parameter can be overridden for specific calling access' categories. In such a case, the same actions are taken as if *presentation allowed* was received, except for the presentation restriction indication which is passed transparently into the connected number information element. + +**Table 28/Q.699 – Coding of the connected number information element according to the connected number parameter** + +| ←CONNECT | ←ANM/CON | +|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| Connected number i.e. | Connected number parameter | +| Type of number (Note)
National number
International number | Nature of address indicator
National number
International number | +| Numbering plan identification
ISDN/Telephony numbering plan | Numbering plan indicator
ISDN/Telephony numbering plan | +| Presentation indicator
Presentation allowed | Address presentation restricted indicator
Presentation allowed | +| Screening indicator
User provided, verified and passed
Network provided | Screening indicator
User provided, verified and passed
Network provided | +| Number digits | Address signals | + +NOTE – As a network option, the type of number may be coded *unknown* when a prefix is added to the number. + +**Table 29/Q.699 – Coding of the connected number information element according to the generic number parameter** + +| ←CONNECT | ←ANM/CON | +|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| Connected number i.e. | Generic number parameter
with number qualifier set to
additional connected number | +| Type of number (Note)
National number
International number | Nature of address indicator
National number
International number | +| Numbering plan identification
ISDN/Telephony numbering plan | Numbering plan indicator
ISDN/Telephony numbering plan | +| Presentation indicator
Presentation allowed | Address presentation restricted indicator
Presentation allowed | +| Screening indicator
User provided, not verified | Screening indicator
User provided, not verified | +| Number digits | Address signals | + +NOTE – As a network option, the type of number may be coded *unknown* when a prefix is added to the number. + +##### Connected subaddress + +**Table 30/Q.699 – Sending of the connected subaddress** + +| ←CONNECT | ←ANM/CON | | +|---------------------------------------------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Content | Access transport parameter | Address presentation restricted indicator of the connected number parameter | +| Connected subaddress information element | Connected subaddress information element | Presentation allowed | +| No connected subaddress information element | Connected subaddress information element | Presentation restricted (Note)
or
Address not available
or
No connected number parameter | + +NOTE – As a national option, the presentation restriction indication received in the connected number parameter can be overridden for specific calling access' categories. In such a case, the same actions are taken as if *presentation allowed* was received. + +#### 2.1.2.6 Connected line identification restriction (COLR) + +See Table 27. + +#### 2.1.2.7 Sub-addressing (SUB) + +The mapping shown in the subclause below forms part of basic call. + +The called party subaddress information element received from the access in the SETUP message is transferred transparently in the access transport parameter of the IAM. + +#### 2.1.2.8 Call diversion + +Hereafter are only described the handling of notification received from a public or private network at the originating exchange. The actions taken in the forwarding exchange are described in Recommendations Q.732 [9] and Q.952 [15]. + +##### 2.1.2.8.1 Interworking at the calling user's exchange + +###### 2.1.2.8.1.1 Reception of a "call diversion may occur" notification + +According to [9], the Address Complete Message (ACM), or the Call Progress Message (CPG) may be received with the optional backward call indicators parameter including the call diversion may occur indicator set to "call diversion may occur". No specific interworking action is required: see 2.1.1. + +###### 2.1.2.8.1.2 Reception of a "call is diverting" notification + +According to [9], the Address Complete message (ACM) or the Call Progress message (CPG) may be received with: + +- the call diversion information parameter; +- the generic notification indicators parameter coded *call is diverting*; and +- the redirection number parameter. + +At least the call diversion information and generic notification indicators parameters should be available in the Address Complete (ACM) or Call Progress (CPG) message. + +###### First diversion + +The number information contained in the redirection number parameter is stored. + +A notification of diversion is sent to the calling user as shown in Table 31. + +**Table 31/Q.699 – First diversion: notification of diversion sent to the calling user** + +| ←DSS 1 message
(Note) | ←ACM/CPG | | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| | Call diversion information parameter | Generic notification indicator parameter | +| Notification indicator information element | Notification subscription option | | +| Call is diverting | Presentation allowed with redirection number
or
Presentation allowed without redirection number | Call is diverting | +| Not sent | Unknown
or
Presentation not allowed | | + +NOTE – The determination of the DSS 1 message sent upon the Address Complete (ACM) or Call Progress (CPG) message is described in 2.1.1. If no message is to be sent, the notification indicator information element is sent in a NOTIFY message. + +###### Subsequent diversion + +The number information contained in the redirection number parameter is stored (i.e. the latest received diverted-to number replaces the one received previously). + +If it has been previously determined, according to [15], that notification of diversion is not allowed, no specific interworking action is required towards the calling user: see 2.1.1. + +If it has been previously determined, according to [15], that notification of diversion is allowed, Table 32 is applicable. + +**Table 32/Q.699 – Subsequent diversion: notification of diversion sent to the calling user** + +| ←DSS 1 message
(Note 1) | ←CPG | | Generic notification
indicator parameter | +|-----------------------------|-----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| | Call diversion information parameter | | | +| Notification indicator i.e. | Redirecting reason | Notification
subscription option | | +| No notification sent | | Unknown
or
Presentation not
allowed | | +| Call is diverting | Deflection during
alerting
or
No reply | Presentation allowed
with redirection
number
or
Presentation allowed
without redirection
number | Call is diverting | +| No notification sent | Other reason | | | + +NOTE 1 – The determination of the DSS 1 message sent upon Call Progress message (CPG) is described in 2.1.1. If no message is to be sent, the notification indicator information element is sent in a NOTIFY message. + +NOTE 2 – The latest received diverted-to number replaces the one received previously. + +###### 2.1.2.8.1.3 Reception of the redirection number restriction parameter + +If a backward message (ACM, CPG, ANM or CON) is received containing the redirection number restriction parameter: + +- if it has been determined, according to [15], that the notification of diverted-to number is not allowed, no specific interworking action are required: see 2.1.1; +- if it has been determined, according to [15], that the notification of diverted-to number is allowed, a redirection number information element is sent to the calling user as shown in Table 33. + +**Table 33/Q.699 – Notification of the diverted-to number** + +| ←DSS 1 message (Note 1) | Redirection number parameter
stored in the originating exchange | ←ACM, CPG, ANM
or CON | +|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------|---------------------------------------| +| Redirection number
information element | | Presentation restriction
parameter | +| Type of number
According to the nature of
address indicator (Note 2) | Nature of address indicator
National number, or
International number | | +| Numbering plan identification
ISDN (telephony) numbering
plan | Numbering plan indicator
ISDN (telephony) numbering plan | Presentation allowed | +| Presentation indicator
Presentation allowed | Address signal | | +| Number digits
Digits received in the address
signal | | | +| Type of number
Unknown | Nature of address indicator
National number, or
International number | | +| Numbering plan identification
Unknown | Numbering plan indicator
ISDN (telephony) numbering plan | Presentation restricted | +| Presentation indicator
Presentation restricted | Address signal | | +| Number digits
Not included | | | +| Type of number
Unknown | No redirection number stored | Value non-significant | +| Numbering plan identification
Unknown | | | +| Presentation indicator
Number not available due to
interworking | | | +| Number digits
Not included | | | + +NOTE 1 – The determination of the DSS 1 message sent upon the ISUP backward message is described in 2.1.1. If no message is to be sent, the redirection number information element is sent in a NOTIFY message. + +NOTE 2 – As a network option, the type of number may be coded *unknown*. + +##### 2.1.2.8.2 Interworking at the exchange where a diverted call is presented from a private ISDN + +For further study. + +#### 2.1.2.9 Call Waiting (CW) + +**Table 34/Q.699 – Mapping of ACM, CPG for CW procedure in ISDN access** + +| ←ALERTING/PROGRESS/NOTIFY
(Note) | ←ACM, CPG | +|--------------------------------------------|-------------------------------------------| +| Notification indicator information element | Generic notification indicator parameter | +| Notification description | Notification indicator | +| 110 0000
Call is a waiting call | 110 0000
Call is a waiting call | + +NOTE – The criteria of sending of ALERTING or PROGRESS is defined in 2.1.1. If neither ALERTING or PROGRESS has to be sent, a NOTIFY message is sent. + +#### 2.1.2.10 Call Hold (HOLD) + +##### 2.1.2.10.1 Notification received from the network + +**Table 35/Q.699 – Receipt of HOLD notification from the network** + +| ←NOTIFY or FACILITY | ←CPG | +|--------------------------------------------|------------------------------------------| +| Notification indicator information element | Generic notification indicator parameter | +| Notification description | Notification indicator | +| 111 1001
Remote hold | 111 1001
Remote hold | +| 111 1010
Remote retrieval | 111 1010
Remote retrieval | + +##### 2.1.2.10.2 Invocation at coincident S and T reference point + +**Table 36/Q.699 – HOLD invocation** + +| Message received from
the DSS 1 → | CPG→ | | +|--------------------------------------|---------------------------------------------|--------------------------------| +| | Generic notification
indicator parameter | Event information
parameter | +| | Notification indicator | Event indicator | +| HOLD | 111 1001
Remote hold | 000 0010
Progress | +| RETRIEVE | 111 1010
Remote retrieval | 000 0010
Progress | + +##### 2.1.2.10.3 Notification received at T reference point + +A HOLD notification may be received at T reference point in the active phase of the call. + +**Table 37/Q.699 – Receipt of a HOLD notification from a private network** + +| NOTIFY→ | CPG→ | | +|--------------------------------------------|------------------------------------------|-----------------------------| +| Notification indicator information element | Generic notification indicator parameter | Event information parameter | +| Notification description | Notification indicator | Event indicator | +| 111 1001
Remote hold | 111 1001
Remote hold | 000 0010
Progress | +| 111 1010
Remote retrieval | 111 1010
Remote retrieval | 000 0010
Progress | + +#### 2.1.2.11 Terminal Portability (TP) + +##### 2.1.2.11.1 Notification received from the network + +**Table 38/Q.699 – Receipt of TP notification from the network** + +| ←NOTIFY | ← Message received from the ISUP | +|---------------------------------------------------------|-----------------------------------------------------------------------------| +| Notification indicator i.e.
Notification description | | +| 000 0000
User suspended | SUS message
Suspend/resume indicator
ISDN subscriber initiated | +| 000 0001
User resumed | RES message
Suspend/resume indicator
ISDN subscriber initiated | +| 000 0000
User suspended | CPG message
Generic notification indicator
User suspended | +| 000 0001
User resumed | CPG message
Generic notification indicator
User resumed | + +##### 2.1.2.11.2 Invocation at coincident S and T reference point + +**Table 39/Q.699 – TP invocation** + +| Message received from the DSS 1 → | Message sent to the ISUP → | +|-----------------------------------|-----------------------------------------------------------------------------| +| SUSPEND | SUS message
Suspend/resume indicator
ISDN subscriber initiated | +| RESUME | RES message
Suspend/resume indicator
ISDN subscriber initiated | + +The action taken on the access side upon receipt of SUSPEND and RESUME messages are described in 5.6/Q.931 and Figure A.6/Q.931. + +The actions taken on the ISUP side upon sending of the Suspend (SUS) and Resume (RES) messages are described in 4.5.2.1/Q.733 [10]. + +Upon the T2 or T307 expiry (Note), a Release message (REL) is sent with the cause value No. 102, *recovery on timer expiry*. No action is taken on the DSS 1 side. + +NOTE – T2 start, stop, and expiry are described in 4.5.2.1/Q.733 [10] and Annex A/Q.764 [4]. T307 start, stop and expiry are described in 5.6/Q.931. + +##### 2.1.2.11.3 Notification received at T reference point + +A TP notification may be received at T reference point from a point-to-point data link in the active phase of the call. + +**Table 40/Q.699 – Receipt of a TP notification from a private network** + +| NOTIFY→ | CPG→ | | +|--------------------------------------------|------------------------------------------|-----------------------------| +| Notification indicator information element | Generic notification indicator parameter | Event information parameter | +| Notification description | Notification indicator | Event indicator | +| 000 0000
User suspended | 000 0000
User suspended | 000 0010
Progress | +| 000 0001
User resumed | 000 0001
User resumed | 000 0010
Progress | + +#### 2.1.2.12 Conference calling (CONF) + +##### 2.1.2.12.1 Notification received from the network + +**Table 41/Q.699 – Conference calling notification** + +| ←NOTIFY | ←CPG | +|---------------------------------------------|---------------------------------------------| +| Notification indicator information element | Generic notification indicator parameter | +| Notification description | Notification indicator | +| 100 0010
Conference established | 100 0010
Conference established | +| 100 0011
Conference disconnected | 100 0011
Conference disconnected | +| 100 0100
Other party added | 100 0100
Other party added | +| 100 0101
Isolated | 100 0101
Isolated | +| 100 0110
Reattached | 100 0110
Reattached | +| 100 0111
Other party isolated | 100 0111
Other party isolated | +| 100 1000
Other party reattached | 100 1000
Other party reattached | +| 100 1001
Other party split | 100 1001
Other party split | +| 100 1010
Other party disconnected | 100 1010
Other party disconnected | +| 100 1011
Conference floating | 100 1011
Conference floating | + +##### 2.1.2.12.2 Invocation at coincident S and T reference point + +**Table 42/Q.699 – Conference calling** + +| Procedure | Message received from served user
→ | Message sent to B
→ | Message sent to all other remote users
→ | +|--------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| Beginning the conference from an active call (with B) | FACILITY
Facility i.e.
BeginCONF-Inv
Call reference i.e.
Call reference of existing call | CPG
Generic notification indicator parameter
Conference established | Not applicable | +| Adding a remote user (B) | FACILITY
Facility i.e.
AddCONF-Inv
Call reference i.e.
Call reference of call to be added | CPG
Generic notification indicator parameter
Conference established | CPG
Generic notification indicator parameter
Other party added | +| Isolate a remote user (B) | FACILITY
Facility i.e.
IsolateCONF-Inv | CPG
Generic notification indicator parameter
Isolated | CPG
Generic notification indicator parameter
Other party isolated | +| Reattach a remote user (B) | FACILITY
Facility i.e.
ReattachCONF-Inv | CPG
Generic notification indicator parameter
Reattached | CPG
Generic notification indicator parameter
Other party reattached | +| Splitting a remote user (B) | SETUP (Note)
Facility i.e.
SplitCONF-Inv | CPG
Generic notification indicator parameter
Conference disconnected | CPG
Generic notification indicator parameter
Other party split | +| Disconnect a remote user (B) | FACILITY
Facility i.e.
DropCONF-Inv | REL | CPG
Generic notification indicator parameter
Other party disconnected | +| Terminate the conference | FACILITY
Facility i.e.
EndCONF-Inv | REL | | + +**Table 42/Q.699 – Conference calling (concluded)** + +| Procedure | Message received from served user
→ | Message sent to B
→ | Message sent to all other remote users
→ | +|-------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| Disconnect the served user | FACILITY
Facility i.e.
FloatCONF-Inv | CPG
Generic notification indicator parameter
Conference floating | | +| Call clearing by served user | DISCONNECT | If the conditions for floating are met:
CPG
Generic notification indicator parameter
Conference floating
If the conditions for floating are not met:
REL | | + +NOTE – This SETUP message does not contain any called party information but contains a bearer capability information element (see 1.5.2.6.1/Q.954 [17]). + +**Table 43/Q.699 – Conference calling: a remote user clears** + +| Procedure | Message sent to served user
← | Message received from B
← | +|---------------------------|--------------------------------------------|-------------------------------------| +| Remote user clears | FACILITY
Facility i.e.
PartyDisc-Inv | REL | + +##### 2.1.2.12.3 Notification received at T reference point + +**Table 44/Q.699 – Receipt of a conference calling notification from a private network** + +| NOTIFY→ | CPG→ | | +|---------------------------------------------|---------------------------------------------|-----------------------------| +| Notification indicator information element | Generic notification indicator parameter | Event information parameter | +| Notification description | Notification indicator | Event indicator | +| 100 0010
Conference established | 100 0010
Conference established | 000 0010
Progress | +| 100 0011
Conference disconnected | 100 0011
Conference disconnected | 000 0010
Progress | +| 100 0100
Other party added | 100 0100
Other party added | 000 0010
Progress | +| 100 0101
Isolated | 100 0101
Isolated | 000 0010
Progress | +| 100 0110
Reattached | 100 0110
Reattached | 000 0010
Progress | +| 100 0111
Other party isolated | 100 0111
Other party isolated | 000 0010
Progress | +| 100 1000
Other party reattached | 100 1000
Other party reattached | 000 0010
Progress | +| 100 1001
Other party split | 100 1001
Other party split | 000 0010
Progress | +| 100 1010
Other party disconnected | 100 1010
Other party disconnected | 000 0010
Progress | +| 100 1011
Conference floating | 100 1011
Conference floating | 000 0010
Progress | + +#### 2.1.2.13 Three-party (3PTY) + +##### 2.1.2.13.1 Notification received from the network + +**Table 45/Q.699 – 3PTY notification** + +| ←NOTIFY | ←CPG | +|--------------------------------------------|--------------------------------------------| +| Notification indicator information element | Generic notification indicator parameter | +| Notification description | Notification indicator | +| 100 0010
Conference established | 100 0010
Conference established | +| 100 0011
Conference disconnected | 100 0011
Conference disconnected | +| 111 1001
Remote hold | 111 1011
Remote hold | + +If the call progress message (CPG) contains two generic notification indicator parameters, one with the notification indicator coded *conference disconnected*, the other with the notification indicator coded *remote hold*, + +- either a NOTIFY message is sent containing: + - a notification indicator information element with the notification description *conference disconnected*; and + - a notification indicator information element with the notification description *remote hold*; +- or + - a NOTIFY message is sent containing a notification indicator information element with the notification description *conference disconnected*; and + - a subsequent NOTIFY message is sent containing a notification indicator information element with the notification description *remote hold*. + +##### 2.1.2.13.2 Invocation at coincident S and T reference point + +Table 46/Q.699 – Three-party (3PTY) + +| Procedure | Message received from served user
→ | Call A-B: Active-held connection message sent to B
→ | Call A-C: Active-idle connection message sent to C
→ | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| Beginning the 3PTY | FACILITY→
Facility i.e.
Begin3PTY-Inv
Call reference i.e.
Call reference of call A-B | CPG→
Generic notification indicator parameter
Conference established | CPG→
Generic notification indicator parameter
Conference established | +| Creation of a private communication with B | FACILITY→
Facility i.e.
End3PTY-Inv
Call reference i.e.
Call reference of call A-B | CPG→
Generic notification indicator parameter
Remote hold | CPG→
Generic notification indicator parameter
Conference disconnected | +| | HOLD→
Call reference i.e.
Call reference of call A-C | No message sent | CPG→
Generic notification indicator parameter
remote hold | +| | RETRIEVE→
Call reference i.e.
Call reference of call A-B | CPG→
Generic notification indicator parameter
Conference disconnected | No message sent | + +**Table 46/Q.699 – Three-party (3PTY) (concluded)** + +| Procedure | Message received from served user
→ | Call A-B: Active-held connection message sent to B
→ | Call A-C: Active-idle connection message sent to C
→ | +|---------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| Creation of a private communication with C | FACILITY→
Facility i.e.
End3PTY-Inv
Call reference i.e.
Call reference of call A-C | CPG→
Generic notification indicator parameter
Conference disconnected
Generic notification indicator parameter
Remote hold | CPG→
Generic notification indicator parameter
Conference disconnected | +| Disconnect the remote user B | DISCONNECT→
Call reference i.e.
Call reference of call A-B | REL→ | CPG→
Generic notification indicator parameter
Conference disconnected | +| Disconnect the remote user C | DISCONNECT→
Call reference i.e.
Call reference of call A-C | CPG→
Generic notification indicator parameter
Remote hold | REL→ | +| | RETRIEVE→
Call reference i.e.
Call reference of call A-B | CPG→
Generic notification indicator parameter
Conference disconnected | Not applicable | + +Table 47 describes the actions taken when user B or user C disconnects. + +**Table 47/Q.699 – Three-party (3PTY): user B or user C disconnects** + +| Messages sent to or received from served user | Call A-B: Active-held connection messages sent to B or received from B | Call A-C: Active-idle connection message sent to C or received from C | Procedure | +|------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|---------------------------| +| ←DISCONNECT
Call reference i.e.
Call reference of call A-B | ←REL | CPG→
Generic notification indicator parameter
Conference disconnected | User B disconnects | +| ←DISCONNECT
Call reference i.e.
Call reference of call A-C | CPG→
Generic notification indicator parameter
Remote hold | ←REL | User C disconnects | +| RETRIEVE→
Call reference i.e.
Call reference of call A-B | CPG→
Generic notification indicator parameter
Conference disconnected | Not applicable | | + +##### 2.1.2.13.3 Notification received at T reference point + +**Table 48/Q.699 – Receipt of a 3PTY notification from a private network** + +| NOTIFY→ | CPG→ | | +|--------------------------------------------|--------------------------------------------|-----------------------------| +| Notification indicator information element | Generic notification indicator parameter | Event information parameter | +| Notification description | Notification indicator | Event indicator | +| 100 0010
Conference established | 100 0010
Conference established | 000 0010
Progress | +| 100 0011
Conference disconnected | 100 0011
Conference disconnected | 000 0010
Progress | +| 111 1001
Remote hold | 111 1011
Remote hold | 000 0010
Progress | + +#### 2.1.2.14 Closed User Group (CUG) + +CUG checks at the originating exchange and determination of the type of call request in correlation with the CUG information received from the calling user in the SETUP message and the CUG attributes of the calling user are described in Table 1-1/Q.955 [18]. + +The coding of the ISUP CUG parameter (closed user group call indicator of the optional forward call indicators parameter, CUG interlock code parameter) and of the ISDN User Part indicator of the forward call indicators parameter are described in 1.5.2.1.1/Q.735 [12]. + +A rejection indication may be received in a Release message (REL). + +**Table 49/Q.699 – Receipt of a rejection indication** + +| ←DISCONNECT | | ←REL | +|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------------| +| Cause information element | Return error component | Cause parameter | +| Implicit request:
Cause value No. 29
Facility rejected | No return error component | Cause value No. 55
Incoming calls barred within CUG | +| Explicit request:
Cause value No. 29
Facility rejected | Return error value #19
incomingCallsBarredWithinCUG | | +| Implicit request or not CUG request:
Cause value No. 87
User not member of CUG | No return error component | Cause value No. 87
User not member of CUG | +| Explicit request:
Cause value No. 29
Facility rejected | Return error value #20
userNotMemberOfCUG | | +| Implicit request:
Cause value No. 87
User not member of CUG | No return error component | Cause value No. 29
Facility rejected | +| Explicit request:
Cause value No. 29
Facility rejected | Return error value #20
userNotMemberOfCUG | Diagnostic with the name of the closed user group interlock parameter | +| Implicit request:
Normal handling of the cause value
See 2.1.1 | No return error component | | +| Explicit request:
Normal handling of the cause value
See 2.1.1 | Return error value #8
basicServiceNotProvided | Other cause value | + +NOTE – This table provides examples of mapping. + +#### 2.1.2.15 User-to-User Signalling (UUS) + +##### 2.1.2.15.1 Service 1 (UUS1) implicit + +Service 1 may be requested implicitly by the presence of the user-user information element in the SETUP message which is mapped into the user-to-user information parameter of the initial address message. + +**Table 50/Q.699 – Implicit UUS1 transfer** + +| DSS 1 messages | ISUP messages | +|-------------------------------------------------|------------------------------------| +| SETUP
→ | IAM
→ | +| User-user information element | User-to-user information parameter | +| PROGRESS, ALERTING, CONNECT,
DISCONNECT
← | ACM, CPG, ANM, CON, REL, SGM
← | +| User-user information element | User-to-user information parameter | +| DISCONNECT, RELEASE, RELEASE
COMPLETE
→ | REL
→ | +| User-user information element | User-to-user information parameter | + +NOTE 1 – If there is no user-user information element in the SETUP message, the exchange should discard the user-to-user information possibly received afterwards from the access or from the ISUP side. + +NOTE 2 – In case of service 1 rejection, no specific notification is sent to the calling user. + +If a backward message (ACM, CPG, ANM) indicates that interworking has occurred with a called analogue user or a non-ISDN signalling system, a progress indicator information element is sent as described in 2.1.1. + +##### 2.1.2.15.2 Service 1 (UUS1) explicit + +**Table 51/Q.699 – Explicit UUS1 invocation** + +| SETUP→ | IAM→ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Content | Content | +| Facility information element
UserUserService invoke component

Service 1 preferred | User-to-user indicators parameter
Type Request
Service 1 Request, not essential
Service 2 No information (Note 1)
Service 3 No information (Note 1)

Forward call indicators parameter
ISDN User Part preference indicator
ISDN User Part preferred all the way | +| User-user information element (Note 2) | User-to-user information parameter | +| Facility information element
UserUserService invoke component

Service 1 required | User-to-user indicators parameter
Type Request
Service 1 Request, essential
Service 2 No information (Note 1)
Service 3 No information (Note 1)

Forward call indicators parameter
ISDN User Part preference indicator
ISDN User Part required all the way | +| User-user information element (Note 2) | User-to-user information parameter | +| NOTE 1 – These indicators may be coded in a different way if service 2 (respectively service 3) information has to be transported: see Tables 56 and 61. | | +| NOTE 2 – The user-user information element is optional for the invocation. When absent, the user-to-user parameter is not included in the Initial Address Message (IAM). | | + +Service 1 acceptance shall be received in the first backward message containing either an alerting, connecting or disconnecting indication. See Table 52. + +**Table 52/Q.699 – Explicit UUS1 acceptance** + +| ←ALERTING, CONNECT, DISCONNECT | ←ACM, CPG, ANM, CON, REL | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Facility information element
UserUserService return result component | User-to-user indicators parameter
Type Response
Service 1 Provided | + +When acceptance of service 1 has been received, user-user information may be exchanged in all the call control messages. See Table 53. + +**Table 53/Q.699 – Explicit UUS1 transfer** + +| DSS 1 messages | ISUP messages | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| PROGRESS, ALERTING, CONNECT,
DISCONNECT (Note)
← | ACM, CPG, ANM,
CON, REL, SGM
← | +| User-user information element | User-to-user information parameter | +| DISCONNECT, RELEASE, RELEASE
COMPLETE
→ | REL
→ | +| User-user information element | User-to-user information parameter | +| NOTE – The correspondence between ISUP and DSS 1 messages is described in 2.1.1.
In case Tables 9 (ACM) or 14 (CPG) do not indicate any message, the user-user information element is included in a PROGRESS message. | | + +###### **Service 1 rejection** + +Only the cases of rejection determined upon receipt of an ISUP message are described below. Rejection initiated by the originating exchange when it cannot support the service or when the calling user has not subscribed the service is not relevant to the interworking and is described in 1.5.2.1.4.2/Q.957 [19]. + +Table 54 describes the handling of a rejection indication received from the network when the service 1 was requested as required. + +Table 55 describes the handling of a rejection indication received from the network when the service 1 was requested as preferred. + +**Table 54/Q.699 – UUS1 rejection: service requested as "required"** + +| DSS 1 messages | ISUP messages | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| +| ←DISCONNECT | ←REL | +| Cause information element
Value As received | Cause parameter
Value No. 29 ( facility rejected ) | +| Facility information element
UserUserService return error component
rejectedByNetwork | Diagnostic UUI indicators parameter's name | +| ←DISCONNECT | ←REL | +| Cause information element
Value No. 69 ( requested facility not implemented ) | Cause parameter
Value No. 69 ( requested facility not implemented ) | +| Facility information element
UserUserService return error component
rejectedByUser | Diagnostic UUI indicators parameter's name | +| ←DISCONNECT (Note) | ←ANM, CON, or REL prior active phase | +| Cause information element
Value No. 69 ( requested facility not implemented ) | No rejection or acceptance indication is received in the ANM, CON or REL message
and | +| Facility information element
UserUserService return error component
rejectedByUser | No rejection or acceptance indication has already been received in a previous backward message (ACM or CPG) | +| NOTE – In case of receipt of an Answer Message (ANM) or a Connect message (CON), a Release message (REL) with the cause value No. 31 ( normal, unspecified ) is sent to the remote exchange. | | + +**Table 55/Q.699 – UUS1 rejection: service requested as "preferred"** + +| DSS 1 messages | ISUP messages | +|----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CALL PROCEEDING, ALERTING, PROGRESS,
CONNECT, or DISCONNECT (Note 1)
← | ACM, CPG, ANM, CON, or
REL prior active phase
← | +| Facility information element
UserUserService return error component
rejectedByUser (Note 2) | User-to-user indicators parameter
Type Response
Service 1 Not provided | +| ←CONNECT, DISCONNECT (Note 1) | ←ANM, CON, or REL prior active phase | +| Facility information element
UserUserService return error component
rejectedByUser | No rejection or acceptance indication is received
in the ANM, CON or REL message
and
No rejection or acceptance indication has already
been received in a previous backward message
(ACM or CPG) | + +NOTE 1 – The correspondence between the ISUP message received and the DSS 1 message sent to the calling user is described in 2.1.1. + +NOTE 2 – Since it is not possible to know if the rejection is due to the network or to the remote user, the default value *rejectedByUser* is used. + + + +**Table 58/Q.699 – UUS2 transfer** + +| DSS 1 messages | ISUP messages | +|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| USER INFORMATION→ | USR→ | +| User-user information element
More data information element | User-to-user information parameter
Access transport parameter
More data information element | +| ←USER INFORMATION | ←USR | +| User-user information element
More data information element | User-to-user information parameter
Access transport parameter
More data information element | + +###### **Service 2 rejection** + +Only the cases of rejection determined upon receipt of an ISUP message are described below. Rejection initiated by the originating exchange when it cannot support the service or when the calling user has not subscribed to the service is not relevant to the interworking and is described in 1.5.2.2.4.2/Q.957 [19]. + +Table 59 describes the handling of a rejection indication received from the network when the service 2 was requested as required. + +Table 60 describes the handling of a rejection indication received from the network when the service 2 was requested as preferred. + +**Table 59/Q.699 – UUS2 rejection: service requested as "required"** + +| DSS 1 messages | ISUP messages | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←DISCONNECT | ←REL | +| Cause information element
Value As received
Facility information element
UserUserService return error component
rejectedByNetwork | Cause parameter
Value No. 29 ( facility rejected )
Diagnostic UUI indicators parameter's name | +| ←DISCONNECT | ←REL | +| Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByNetwork | Cause parameter
Value No. 88 ( incompatible destination )
Diagnostic UUI indicators parameter's name | +| ←DISCONNECT | ←REL | +| Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | Cause parameter
Value No. 69 ( requested facility not implemented )
Diagnostic UUI indicators parameter's name | +| ←DISCONNECT (Note) | ←ACM, CPG with an alerting indication
or REL prior active phase | +| Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | No rejection or acceptance indication is received in the ACM, CPG or REL message
and
No rejection or acceptance indication has already been received in a previous backward message (ACM or CPG) | + +NOTE – In case of receipt of an Address Complete Message (ACM) or a Call Progress message (CPG), a Release message (REL) with the cause value No. 31 (*normal, unspecified*) is sent to the remote exchange. + +**Table 60/Q.699 – UUS2 rejection: service requested as "preferred"** + +| DSS 1 messages | ISUP messages | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←ALERTING, DISCONNECT (Note 1) | ←ACM, CPG with an alerting indication or REL prior active phase | +| Facility information element
UserUserService return error component
rejectedByUser (Note 2) | User-to-user indicators parameter
Type Response
Service 2 Not provided | +| ←ALERTING or DISCONNECT (Note 1) | ←ACM, CPG with an alerting indication or REL prior active phase | +| Facility information element
UserUserService return error component
rejectedByUser | No rejection or acceptance indication is received in the ACM, CPG or REL message
and
No rejection or acceptance indication has already been received in a previous backward message (ACM or CPG) | +| NOTE 1 – The correspondence between the ISUP message received and the DSS 1 message sent to the calling user is described in 2.1.1. | | +| NOTE 2 – Since it is not possible to know if the rejection is due to the network or to the remote user, the default value rejectedByUser is used. | | + +##### 2.1.2.15.4 Service 3 + +**Table 61/Q.699 – UUS3 invocation** + +| SETUP→ | IAM→ | +|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Content | Content | +| Facility information element
UserUserService invoke component

Service 3 preferred | User-to-user indicators parameter
Type Request
Service 1 No information (Note)
Service 2 No information (Note)
Service 3 Request, essential | +| | Forward call indicators parameter
ISDN user part preference indicator
ISDN User Part preferred all the way | +| Facility information element
UserUserService invoke component

Service 3 required | User-to-user indicators parameter
Type Request
Service 1 No information (Note)
Service 2 No information (Note)
Service 3 Request, essential | +| | Forward call indicators parameter
ISDN user part preference indicator
ISDN user part required all the way | + +NOTE – These indicators may be coded in a different way if service 1 (respectively service 2) information have to be transported: see Tables 51 and 56 + +Service 3 acceptance is indicated in the connecting information received from the remote user. + +**Table 62/Q.699 – UUS3 acceptance** + +| ←CONNECT | ←ANM, CON | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Facility information element
UserUserService return result component | User-to-user indicators parameter
Type Response
Service 3 Provided | + +Service 3 may be activated in the active phase by either the calling user (see Tables 63 and 66) or the called user (see Tables 65 and 66). + +**Table 63/Q.699 – UUS3 activation received from the calling user in active phase** + +| FACILITY → | Facility request message (FAR) → | +|------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Facility information element
UserUserService invoke component
Service 3 preferred | User-to-user indicators parameter
Type Request
Service 3 Request, not essential | + +**Table 64/Q.699 – UUS3 acceptance received from the called user in active phase** + +| ←FACILITY | ←Facility accepted message (FAA) | +|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Facility information element
UserUserService return result component | User-to-user indicators parameter
Type Response
Service 1 No information
Service 2 No information
Service 3 Provided | + +**Table 65/Q.699 – UUS3 activation received from the called user in active phase** + +| ←FACILITY | ←Facility request message (FAR) | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Facility information element
UserUserService invoke component
Service 3 preferred | User-to-user indicators parameter
Type Request
Service 1 No information
Service 2 No information
Service 3 Request, not essential | + +**Table 66/Q.699 – UUS3 acceptance received from the calling user in active phase** + +| FACILITY→ | Facility accepted message (FAA)→ | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Facility information element
UserUserService return result component | User-to-user indicators parameter
Type Response
Service 3 Provided | + +When acceptance of service 3 has been received, user-user information may be exchanged during the active phase of the call: see Table 67. + +**Table 67/Q.699 – UUS3 transfer** + +| DSS 1 messages | ISUP messages | +|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| USER INFORMATION→ | User-to-user information (USR)→ | +| User-user information element
More data information element | User-to-user information parameter
Access transport parameter
More data information element | +| ←USER INFORMATION | ←User-to-user information (USR) | +| User-user information element
More data information element | User-to-user information parameter
Access transport parameter
More data information element | + +###### **Service 3 rejection** + +Only the cases of rejection determined upon receipt of an ISUP message are described below. Rejection initiated by the originating exchange when it cannot support the service or when the calling user has not subscribed the service is not relevant to the interworking and is described in 1.5.2.3.6/Q.957 [19]. + +Rejection of service 3 requested during call establishment. + +Table 68 describes the handling of a rejection indication received from the network when the service 3 was requested as required. + +Table 69 describes the handling of a rejection indication received from the network when the service 3 was requested as preferred. + +**Table 68/Q.699 – UUS3 rejection: service requested as "required" during call establishment** + +| DSS 1 messages | ISUP messages | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←DISCONNECT | ←REL | +| Cause information element
Value As received
Facility information element
UserUserService return error component
rejectedByNetwork | Cause parameter
Value No. 29 ( facility rejected )
Diagnostic UUI indicators parameter's name | +| ←DISCONNECT | ←REL | +| Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | Cause parameter
Value No. 69 ( requested facility not implemented )
Diagnostic UUI indicators parameter's name | +| ←DISCONNECT (Note) | ←ANM or CON, or REL prior active phase | +| Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | No rejection or acceptance indication is received in the ANM, CON or REL message
and
No rejection or acceptance indication has already been received in a previous backward message (ACM or CPG) | + +NOTE – In case of receipt of an Answer Message (ANM) or a connect message (CON), a Release message (REL) with the cause value No. 31 (*normal, unspecified*) is sent to the remote exchange. + +**Table 69/Q.699 – UUS3 rejection: service requested as "preferred" during call establishment** + +| DSS 1 messages | ISUP messages | +|----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←CONNECT, DISCONNECT (Note 1) | ←ANM, CON or REL prior active phase | +| Facility information element
UserUserService return error component
rejectedByUser (Note 2) | User-to-user indicators parameter
Type Response
Service 1 Not provided | +| ←CONNECT, DISCONNECT (Note 1) | ←ANM, CON, or REL prior active phase | +| Facility information element
UserUserService return error component
rejectedByUser | No rejection or acceptance indication is received in the ANM, CON or REL message
and
No rejection or acceptance indication has already been received in a previous backward message (ACM or CPG) | + +NOTE 1 – The correspondence between the ISUP message received and the DSS 1 message sent to the calling user is described in 2.1.1. + +NOTE 2 – Since it is not possible to know if the rejection is due to the network or to the remote user, the default value *rejectedByUser* is used. + +###### **Rejection of service 3 requested after call establishment** + +**Table 70/Q.699 – Rejection of UUS3 requested by the calling user after call establishment** + +| DSS 1 messages | ISUP messages | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| ←FACILITY | ←FRJ (Note 1) | +| Facility information element
UserUserService return error component
rejectedByUser (Note 2) | User-to-user indicators parameter
Type Response
Service 3 Not provided | +| NOTE 1 – FRJ: Facility reject message
NOTE 2 – Since it is not possible to know if the rejection is due to the network or to the remote user, the default value rejectedByUser is used. | | + +**Table 71/Q.699 – Rejection of UUS3 requested by the called user after call establishment** + +| DSS 1 messages | ISUP messages | +|-------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FACILITY→ | FRJ (Note 1)→ | +| Facility information element
UserUserService return error component
rejectedByUser | User-to-user indicators parameter
Type Response
Service 1 No information
Service 2 No information
Service 3 Not provided
Cause parameter
Value No. 69 ( requested facility not implemented ) | +| T1 expiry (Note 2) | FRJ (Note 1)→
User-to-user indicators parameter
Type Response
Service 1 No information
Service 2 No information
Service 3 Not provided
Cause parameter
Value No. 69 ( requested facility not implemented ) | + +NOTE 1 – FRJ: Facility reject message. + +NOTE 2 – T1 start and normal stop are described in 1.5.2.3/Q.957 [19]. + +## 2.2 Interworking from non-ISDN access to ISUP + +### 2.2.1 Basic call + +#### 2.2.1.1 Sending of the Initial Address Message (IAM) + +When the exchange has received enough information from the calling user in the Address signals to determine that the call is to be routed to another exchange after detection of the off-hook condition, it shall select a suitable, free, inter-exchange circuit and send an initial address message. + +The coding of the Initial Address Message (IAM) is described hereafter. + +NOTE – The coding of the initial address message (IAM) sent by a forwarding exchange is described in 2.5.2.5/Q.732 [9]. The parameters used in such a case are not mentioned hereafter. + +##### 2.2.1.1.1 Coding of the Initial Address Message (IAM) + +###### MANDATORY PARAMETERS + +###### Forward call indicators + +bit A National/international call indicator + +0 *call to be treated as a national call* + +This bit can be set to "1" for international calls. + +bit D Interworking indicator + +0 *no interworking encountered (No. 7 signalling all the way)* + +bit F ISDN user part indicator + +1 *ISDN user part used all the way* + +bits HG ISDN user part preference indicator + +1 0 *ISDN user part required all the way* + +0 0 *ISDN user part preferred all the way* if required by the invoked supplementary services or by Recommendation E.172 + +0 1 *ISDN user part not required* otherwise + +bit I ISDN access indicator + +0 *originating access non-ISDN* + +###### Calling party's category + +Coded according to internal data of the originating exchange. + +###### Transmission medium requirement + +This parameter is coded *3.1 kHz audio*. + +###### Called party number + +– Nature of address indicator: + +According to the internal data of the originating exchange. + +– Internal network number indicator: + +1 *routing to internal network number not allowed* + +– Numbering plan indicator: + +001 *ISDN (telephony) numbering plan (Recommendation E.164)* + +#### 2.2.1.2 Receipt of the Address Complete Message (ACM) + +Upon receiving the Address Complete Message (ACM), no mapping is taken on the non-ISDN side. + +In particular, upon receiving the address complete message, in case that certain tone and announcement can be generated from the destination exchange for example for a changed number announcement, the exchange may send an appropriate signal, e.g. Clear-back signal, to the calling user depending on the condition of the access type. + +#### 2.2.1.3 Receipt of the Call Progress message (CPG) + +Upon receiving the Call Progress message (CPG), no mapping is taken on the non-ISDN side. + +#### **2.2.1.4 Receipt of the Answer Message (ANM)** + +Upon receiving the Answer Message (ANM) in the exchange, it may be mapped into an appropriate signal, e.g. Answer signal on the non-ISDN side. + +#### **2.2.1.5 Receipt of the Connect message (CON)** + +Upon receiving the Connect Message (CON) in the exchange, it may be mapped into an appropriate signal, e.g. Answer signal, on the non-ISDN side. + +#### **2.2.1.6 Receipt of the Release message (REL)** + +Upon receiving the Release Message (REL) in the exchange, it may be mapped into an appropriate backward signal, e.g. Clear-backward signal, on the non-ISDN side. + +#### **2.2.1.7 Sending of the Release message (REL)** + +If the exchange detects the on-hook condition or receives an appropriate signal to indicate release procedures, e.g. Clear-forward signal, it shall send a Release message (REL). + +##### **MANDATORY PARAMETERS** + +###### **Cause indicators** + +Coded to No. 16. + +#### **2.2.1.8 Receipt of the Suspend message (SUS) network initiated** + +The actions taken on the ISUP side upon receipt of the Suspend message (SUS) are described in 2.4.1/Q.764 [4]. + +No action taken on the non-ISDN side. + +#### **2.2.1.9 Receipt of the Resume message (RES) network initiated** + +The actions taken on the ISUP side upon receipt of the Resume message (RES) are described in 2.4.1/Q.764 [4]. + +No action is taken on the non-ISDN side. + +#### 2.2.1.10 Release by the exchange + +**Table 72/Q.699 – Release from the originating exchange** + +| Trigger event | REL→ | +|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| | Cause parameter | +| Determination that the called number information received is incomplete, after an IAM message has already been sent | Cause value No. 28
Invalid number format
(address incomplete) | +| Failure of the automatic repeat attempt procedure | No action | +| T6 expiry
(Note) | Cause value No. 102
recovery on timer expiry | +| Call release due to the ISUP compatibility procedure | Cause value No. 97 or No. 99 | +| Other cases of failure on the ISUP side | Cause value coded according to [4] | + +NOTE – T6: awaiting resume message (RES) timer. T6 start, stop, and expiry are described in 2.4/Q.764 and Annex A/Q.764 [4]. + +### 2.2.2 Supplementary services + +For further study. + +# 3 Incoming call + +## 3.1 Interworking from ISUP to DSS 1 + +### 3.1.1 Basic call + +#### 3.1.1.1 Sending of the SETUP message + +The call information are received in the Initial Address Message (IAM), possibly followed by one or several Subsequent Address Messages (SAM) (See 3.1.1.2). + +If the continuity check indicator of the nature of connection indicators is coded 01, *continuity check required on this circuit*, or 10, *continuity check required on a previous circuit*, the setting up of the call must be prevented until the receipt of the result of the continuity check procedure. + +When the exchange has received all the information required to go on with the call, and performed the various checks to determine that the call is allowed, a SETUP message is sent to the called user. + +The information elements carried in the access transport parameter of the Initial Address Message (IAM) are taken into account whatever the order of receipt, except when two high layer compatibility information elements are received: the order of these two information elements is then significant. + +The sending of some information elements (like the calling party number, the calling or called party subaddress) may depend on other checks: see 3.1.2. + +Only the information elements involved in the interworking are described hereafter. + +The information elements used for the supplementary services are described in 3.1.2. + +##### Bearer capability + +**Table 73/Q.699 – Coding of the Bearer Capability information element (BC)** + +| IAM→ | SETUP→ | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Content | Bearer capability information element | +| No USI present
TMR 3.1 kHz audio | Coding standard CCITT standardized coding
Information transfer capability 3.1 kHz audio
Transfer mode Circuit mode
Information transfer rate 64 kbit/s | +| No USI present
TMR 64 kbit/s unrestricted | Coding standard CCITT standardized coding
Information transfer capability Unrestricted digital information
Transfer mode Circuit mode
Information transfer rate 64 kbit/s | +| USI present
No USI prime | BC = USI (Note 1) | +| USI Speech, or
3.1 kHz audio
USI prime Unrestricted digital
information with tones
and announcements | BC 1 = USI (Notes 1 and 2)

BC 2 = USI' (Notes 1 and 2) | +| NOTE 1 – Octet 1 (information element identifier) and octet 2 (length) are recreated. | | +| NOTE 2 – BC 1 is the bearer capability information element sent in first position in the SETUP message, BC 2 in second position. Bearer capability information elements shall be sent in ascending order of priority as described in 5.11.2.1/Q.931 [6]. | | + +##### Facility + +See 3.1.2. + +##### Sending complete + +This information element is included, in case of *en bloc* sending used, to indicate that the SETUP message contains all the information required by the called user to process the call. + +##### Progress indicator + +**Table 74/Q.699 – Coding of the progress indicator information element** + +| IAM→ | | | SETUP→ | +|---------------------------------------------------|-------------------------------------------|----------------------------|----------------------------------------| +| Forward call indicators parameter | | Access transport parameter | Progress indicator information element | +| ISDN User Part indicator | ISDN access indicator | | | +| 0
(ISDN User Part not used all the way) | Value non-significant | Value non-significant | No. 1 | +| 1
(ISDN User Part used all the way) | 0
(originating access non-ISDN) | Value non-significant | No. 3 | +| 1
(ISDN User Part used all the way) | 1
(originating access ISDN) | p.i. No. x | No. x | + +##### Calling party number + +See 3.1.2. + +##### Calling party subaddress + +See 3.1.2. + +##### Called party number + +See 3.1.2.1 and 3.1.2.2. + +###### Called party subaddress + +See 3.1.2. + +##### Low layer compatibility + +If the low layer compatibility information element is present in the access transport parameter of the Initial Address Message (IAM), it is passed on unchanged in the SETUP message. + +##### High layer compatibility + +If the high layer compatibility information element is present in the access transport parameter of the Initial Address Message (IAM), it is passed on unchanged in the SETUP message. + +If two high layer compatibility information elements are received in the access transport parameter of the Initial Address Message (IAM), they are passed on unchanged in the same order in the SETUP message (the meaning of HLC order is described in 5.12.3.2/Q.931 [6]). + +##### User-user + +See 3.1.2. + +#### 3.1.1.2 Receipt of the Subsequent Address Message (SAM) + +If *en bloc* sending is used on the DSS 1 side, the SETUP message shall contain all the information required by the called user to process the call (See 3.1.1.1). + +If overlap sending is used, and if the SETUP message has already be sent and the SETUP ACKNOWLEDGE message received, an INFORMATION message is sent upon receipt of each Subsequent Address Message (SAM). + +#### 3.1.1.3 Sending of the Address Complete Message (ACM) + +The following cases are possible trigger conditions of sending the address complete message (ACM): + +- a) The destination exchange has determined independently of access indications that the complete called party number has been received. +- b) Overlap receiving is used on the DSS 1 side and a CALL PROCEEDING is received. +- c) *En bloc* receiving is used on the DSS 1 side and a Progress indicator information element (except with value No. 8, *in-band information or an appropriate pattern is now available*, No. 3, *originating address is non-ISDN*, or No. 4, *call has returned to the ISDN*) is received in a CALL PROCEEDING message or in a PROGRESS message. +- d) The first ALERTING message is received. +- e) It has been determined, in case of call failure, that a special in-band tone or announcement has to be returned to the calling party from the destination exchange. + +On *speech* or *3.1 kHz* calls, the awaiting answer indication (e.g. ring tone) is sent to the calling party upon receipt of the first ALERTING message. + +NOTE 1 – In all cases, it is assumed that no Address Complete Message (ACM) has already been sent. + +NOTE 2 – The case of the sending of the Address Complete Message (ACM) when the call is forwarded is not described hereafter: see 3.1.2. + +##### MANDATORY PARAMETERS + +##### Backward call indicators + +| | | | +|------|-----|-----------------------------------------------------------------------------------------------| +| bits | DC | Called party's status indicator | +| | 0 1 | subscriber free if the ALERTING message has been received. | +| | 0 0 | no indication otherwise | +| bits | FE | Called party's category indicator | +| | 0 0 | no indication if the user's characteristics (internal data) have not been analysed, or | +| | 0 1 | ordinary subscriber , or | +| | 1 0 | payphone according to the user's characteristics | +| bit | I | Interworking indicator | +| | 0 | no interworking encountered | +| bit | K | ISDN user part indicator | +| | 1 | ISDN user part used all the way | +| bit | M | ISDN access indicator | +| | 1 | terminating access ISDN | + +##### OPTIONAL PARAMETERS + +###### Optional backward call indicators + +bit A In-band information indicator + +1 *in-band information or an appropriate pattern is now available* if it has been determined, in case of call failure, that a special in-band tone or announcement has to be returned to the calling party from the destination exchange., + +0 *no indication* otherwise. + +bit B Call diversion may occur indicator + +See 3.1.2. + +bit D MLPP user indicator + +See 3.1.2. + +###### User-to-user indicators + +See 3.1.2. + +###### User-to-user information + +See 3.1.2. + +###### Access transport + +This parameter carries the progress indicator information element possibly received from the called user (except the value No. 8). + +It may carry other information element as well: see 3.1.2 and Tables 75 and 76. + +###### Generic notification indicator + +See 3.1.2. + +###### Transmission medium used + +See handling of fallback information at the end of this subclause. + +###### Access delivery information + +If a SETUP message has been sent to the called user, this parameter is coded *Set-up message generated*. Otherwise, it is not included in the address complete message. + +###### Redirection number + +See 3.1.2. + +###### Call diversion information + +See 3.1.2. + +###### Redirection number restriction parameter + +See 3.1.2. + +##### Handling of fallback information (only applicable at T reference point) + +When the terminating exchange has knowledge that the fallback capability was requested in the Initial Address Message (IAM), and if no progress indicator No. 1 or No. 2 has been received from the DSS 1 side, Tables 75 and 76 are applicable. + +**Table 75/Q.699 – Handling of BC fallback information** + +| ←ACM | | ←Message received from the access | +|------------------------------------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------| +| Transmission medium used parameter | Access transport parameter | Content | +| Value received in the TMR prime of the IAM message
( speech or 3.1 kHz audio ) | BC low
( speech or 3.1 kHz audio )
p.i. No. 5 | BC low
( speech or 3.1 kHz audio )
p.i. No. 5 | + +**Table 76/Q.699 – Handling of HLC fallback information** + +| ←ACM | ←Message received from the access | +|---------------------------------|-----------------------------------| +| Access transport parameter | Content | +| HLC
Progress indicator No. 5 | HLC
Progress indicator No. 5 | + +#### 3.1.1.4 Sending of the Call Progress message (CPG) + +If the Address Complete Message (ACM) has already been sent, the following cases are possible trigger conditions of sending the Call Progress message (CPG): + +- It has been determined that an in-band tone or announcement has to be returned to the calling party from the destination exchange. +- Receipt of a progress indicator information element in a CALL PROCEEDING message (except with value No. 8, *in-band information or an appropriate pattern is now available*, No. 3, *originating address is non-ISDN*, or No. 4, *call has returned to the ISDN*) or in a PROGRESS message (except with value No. 8, *in-band information or an appropriate pattern is now available* or No. 3 *originating address is non-ISDN*). +- Receipt of the first ALERTING message. + +NOTE – The case of the sending of the Call Progress message (CPG) when the call is forwarded is not described hereafter: see 3.1.2. + +##### MANDATORY PARAMETERS + +###### Event information + +| | | | +|------|---------|---------------------------------------------------------------------------------------------| +| bits | G-A | Event indicator | +| | 0000001 | alerting in case c (see Note); | +| | 0000010 | progress in case b; | +| | 0000011 | in-band information or an appropriate pattern is now available in case a (see Note). | + +##### OPTIONAL PARAMETERS + +###### Other parameters + +The other parameters may have already been sent in a previous backward message. In this case they are not repeated unless new information are now available. + +The coding of these parameters is described in 3.1.1.3. + +NOTE – If cases a and c occur simultaneously, the event indicator of the event information parameter is coded *alerting* and the in-band information indicator of the optional backward call indicators parameter *in-band information or an appropriate pattern is now available* (for further study). + +#### 3.1.1.5 Sending of the Answer Message (ANM) + +Upon receipt of the first CONNECT message, if the address complete message has already been sent, the destination exchange shall: + +- stop the sending of the awaiting indication (if any); +- send the Answer Message (ANM) to the preceding exchange. + +The Answer Message (ANM) is coded as follows: + +##### OPTIONAL PARAMETERS + +###### Connected number + +See 3.1.2. + +###### Generic number + +See 3.1.2. + +###### Access transport + +**Table 77/Q.699 – Contents of the access transport parameter** + +| ←ANM | ←Message received from the access | +|-------------------------|-----------------------------------| +| Access transport | Information elements | +| Progress indicator | Progress indicator | +| Low layer compatibility | Low layer compatibility | + +It may carry other information elements as well: See 3.1.2 and Tables 78, 79, 80 and 81. + +###### Transmission medium used + +This parameter is only present in case where fallback occurs (see the end of this subclause). + +###### Other parameters + +The other parameters may have already been sent in a previous backward message. In this case they are not repeated unless new information are now available. + +The coding of these parameters is described in 3.1.1.3. + +##### Handling of fallback information + +When the terminating exchange has knowledge that the fallback capability was requested in the Initial Address Message (IAM), and if no progress indicator No. 1 or No. 2 has been received from the DSS 1 side, Tables 78 to 81 are applicable. + +###### **Coincident S and T reference point** + +**Table 78/Q.699 – Handling of BC fallback information +Coincident S and T reference point** + +| ←ANM | | ←CONNECT | +|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| Transmission medium used parameter | Access transport parameter | Content | +| No TMU | BC
(unrestricted digital information with tones and announcements) | BC
(unrestricted digital information with tones and announcements) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC received in the USI of the IAM message
(speech or 3.1 kHz audio) | No BC | + +**Table 79/Q.699 – Handling of HLC fallback information +Coincident S and T reference point** + +| ←ANM | ←CONNECT | +|--------------------------------------------------------------|-----------------| +| Access transport parameter | Content | +| HLC | HLC | +| HLC received in first position in the ATP of the IAM message | No HLC | + +###### T reference point + +**Table 80/Q.699 – Handling of BC fallback information +T reference point** + +| ←ANM | | ←CONNECT | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| Transmission medium used parameter | Access transport parameter | Content | +| No TMU | BC
(unrestricted digital information with tones and announcements) | BC
(unrestricted digital information with tones and announcements) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio)
p.i. No. 5 | BC
(speech or 3.1 kHz audio)
p.i. No. 5 | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC received in the USI of the IAM message
(speech or 3.1 kHz audio)
p.i. No. 5 | No BC (Note) | + +NOTE – In this case, the fallback information coded in the transmission medium used and access transport parameters are not repeated if already sent in a previous backward message. + +**Table 81/Q.699 – Handling of HLC fallback information +T reference point** + +| ←ANM | ←CONNECT | +|---------------------------------|---------------------------------| +| Access transport parameter | Content | +| HLC | HLC | +| HLC
Progress indicator No. 5 | HLC
Progress indicator No. 5 | +| No HLC | No HLC | + +#### 3.1.1.6 Sending of the Connect message (CON) + +Upon receipt of the first CONNECT message, if the Address Complete Message (ACM) has not yet been sent, the destination exchange shall send the Connect message (CON) to the preceding exchange. + +The Connect message (CON) is coded as follows. + +##### **MANDATORY PARAMETERS** + +###### **Backward call indicators** + +See 3.1.1.3. + +##### **OPTIONAL PARAMETERS** + +###### **Optional backward call indicators** + +See 3.1.1.3. + +###### **Connected number** + +See 3.1.2. + +###### **Access transport** + +**Table 82/Q.699 – Contents of the access transport parameter** + +| ←CON | ←CONNECT | +|----------------------------|-------------------------| +| Access transport parameter | Information elements | +| Progress indicator | Progress indicator | +| Low layer compatibility | Low layer compatibility | + +It may carry other information elements as well: see 3.1.2 and Tables 83, 84, 85 and 86. + +###### **Access delivery information** + +bit      A    Access delivery indicator +             0    *SETUP message generated* + +###### **Generic number** + +See 3.1.2. + +###### **Generic notification indicator** + +See 3.1.2. + +##### **Transmission medium used** + +This parameter is only present in case where fallback occurs (see the end of this subclause). + +##### **User-to-user indicators** + +See 3.1.2. + +###### **User-to-user information** + +See 3.1.2. + +##### **Handling of fallback information** + +When the terminating exchange has knowledge that the fallback capability was requested in the Initial Address Message (IAM), and if no progress indicator No. 1 or No. 2 has been received from the DSS 1 side, Tables 83 to 86 are applicable. + +##### Coincident S and T reference point + +**Table 83/Q.699 – Handling of BC fallback information +Coincident S and T reference point** + +| ←CON | | ←CONNECT | +|-----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| Transmission medium used parameter | Access transport parameter | Content | +| No TMU | BC
(unrestricted digital information with tones and announcements) | BC
(unrestricted digital information with tones and announcements) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | +| Value received in the TMR prime of the IAM message
(speech, or 3.1 kHz audio) | BC received in the USI of the IAM message
(speech or 3.1 kHz audio) | No BC | + +**Table 84/Q.699 – Handling of HLC fallback information +Coincident S and T reference point** + +| ←CON | ←CONNECT | +|--------------------------------------------------------------|----------| +| Access transport parameter | Content | +| HLC | HLC | +| HLC received in first position in the ATP of the IAM message | No HLC | + +###### **T reference point** + +**Table 85/Q.699 – Handling of BC fallback information +T reference point** + +| ←CON | | ←CONNECT | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| Transmission medium used parameter | Access transport parameter | Content | +| No TMU | BC
(unrestricted digital information with tones and announcements) | BC
(unrestricted digital information with tones and announcements) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio) | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC
(speech or 3.1 kHz audio)
p.i. No. 5 | BC
(speech or 3.1 kHz audio)
p.i. No. 5 | +| Value received in the TMR prime of the IAM message
(speech or 3.1 kHz audio) | BC received in the USI of the IAM message
(speech or 3.1 kHz audio)
p.i. No. 5 | No BC | + +**Table 86/Q.699 – Handling of HLC fallback information +T reference point** + +| ←CON | ←CONNECT | +|----------------------------|--------------------------| +| Access transport parameter | Content | +| HLC | HLC | +| HLC | HLC | +| Progress indicator No. 5 | Progress indicator No. 5 | +| No HLC | No HLC | + +#### 3.1.1.7 Receipt of the Release message (REL) + +**Table 87/Q.699 – Receipt of the Release message (REL)** + +| REL→ | DISCONNECT or RELEASE→
(Note 1) | +|-------------------|-------------------------------------------| +| Cause parameter | Cause information element | +| Cause value No. x | Cause value No. x
(Notes 2 and 3) | + +NOTE 1 – The RELEASE message is sent at coincident S and T reference point if the Release message (REL) is received during the call establishment as described in 5.3.2/Q.931 [6]. +In the other cases, DISCONNECT is sent. +NOTE 2 – If the cause value received in the Release message (REL) is unknown in DSS 1, the unspecified cause value of the class is sent. +NOTE 3 – Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values: see 3.1.2. + +The handling of the other parameters is described in 3.1.2. + +The receipt of the Release message (REL) during the user suspend/resume procedure is described in 3.1.2. + +#### 3.1.1.8 Sending of the Release message (REL) + +**Table 88/Q.699 – Call clearing during call establishment** + +| ←REL | ←DISCONNECT
RELEASE
RELEASE COMPLETE
(Note 1) | +|--------------------------------------|-----------------------------------------------------------------| +| Cause parameter | Cause information element | +| Cause value No. x
(Notes 2 and 3) | Cause value No. x | + +NOTE 1 – In case of coincident S and T reference point, 5.2.5.3/Q.931 describes how these messages are taken into account when they are received during call establishment. +NOTE 2 – If the cause value received in the DSS 1 message is unknown in ISUP, the unspecified cause value of the class is sent. +NOTE 3 – Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values: see 3.1.2. + +The Release message (REL) contains the access delivery information parameter coded to *Set-up message generated* if this information has not been sent before. + +The handling of the other parameters possibly present in the Release message (REL) is described in 3.1.2. + +#### **3.1.1.9 Receipt of the Reset Circuit message (RSC), Circuit Group Reset message (GRS) or Circuit Group Blocking message (CGB) with the indication *hardware failure oriented*** + +**Table 89/Q.699 – Receipt of RSC, GRS or CGB messages** + +| Message received from ISUP→ | DISCONNECT→ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| | Cause information element | +| Reset Circuit message (RSC) | Cause value No. 31
Normal, unspecified | +| Circuit Group Reset message (GRS) | Cause value No. 31
Normal, unspecified | +| Circuit Group Blocking message (CGB)
with the type indicator of the circuit group
supervision message type indicator parameter
coded "01" ( hardware failure oriented ) | Cause value No. 31
Normal, unspecified | + +#### **3.1.1.10 DSS 1 Data link reset and Data link failure procedures** + +The data link reset and data link failure procedures are respectively described in 5.8.8/Q.931 and 5.8.9/Q.931 [6]. + +**Table 90/Q.699 – DSS 1 Data link reset and Data link failure procedures** + +| ←REL | Trigger event | DISCONNECT→ | +|---------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Cause parameter | | Cause information element | +| Cause value No. 41
(temporary failure) | Data link reset
in overlap receiving state | Cause value No. 41
(temporary failure) | +| Cause value No. 27
(destination out of order) | Data link failure
in an other state than active state | (Note) | +| Cause value No. 27
(destination out of order) | Failure of the data link reestablishment
procedure after a data link failure in active
state | (Note) | + +NOTE – The call is cleared internally. No DISCONNECT message is sent on the access. + +#### 3.1.1.11 Release by the exchange + +**Table 91/Q.699 – Release from the destination exchange** + +| ← Message sent to the ISUP | Trigger event | Message sent to the DSS 1 → | | +|-----------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------| +| | | Point-to-point data link | Broadcast data link | +| REL
Cause value No. 18
No user responding | No response to the SETUP message (T303 expiry) | DISCONNECT
Cause value No. 102
Recovery on timer expiry | No action | +| REL
Cause value No. 18
No user responding | No ALERTING, CONNECT or DISCONNECT after CALL PROCEEDING (T310 expiry) | DISCONNECT
Cause value No. 102
Recovery on timer expiry | RELEASE
Cause value No. 102
Recovery on timer expiry | +| REL
Cause value No. 19
No answer from user (user alerted) | No CONNECT or DISCONNECT after ALERTING (T301 expiry) | DISCONNECT
Cause value No. 102
Recovery on timer expiry | RELEASE
Cause value No. 102
Recovery on timer expiry | +| REL
Cause value No. 31
Normal, unspecified | Unsuccessful termination of the B-channel selection procedure | RELEASE
Cause 6
Channel unacceptable | | +| REL
Cause value No. 97 or No. 99 | Call release due to the ISUP compatibility procedure | DISCONNECT
Cause value No. 97 or No. 99 | | +| REL
Cause value coded according to [4] | Other cases of failure on the ISUP side | DISCONNECT
Same cause value as in the REL message (Note 1) | | +| REL
Same cause value as in the DISCONNECT message (Note 2) | other cases of failure on the DSS 1 side | DISCONNECT
Cause value coded according to [6] | | + +NOTE 1 – If the cause value sent in the REL message is unknown in DSS 1, the unspecified cause value of the class is sent. +NOTE 2 – If the cause value sent in the DISCONNECT message is unknown in ISUP, the unspecified cause value of the class is sent. + +If the SETUP message has been sent, the Release message (REL) contains the access delivery information parameter coded to *Set-up message generated* if this information has not been sent before. + +The handling of the other parameters possibly present in the Release message (REL) is described in 3.1.2. + +### **3.1.2 Supplementary Services** + +#### **3.1.2.1 Direct-Dialling-In (DDI)** + +There is no specific interworking requirement relating to the direct-dialling-in supplementary service. + +The coding of the called party number information element is described in Recommendation Q.951.1. + +#### **3.1.2.2 Multiple Subscriber Number (MSN)** + +There is no specific interworking requirement relating to the multiple subscriber number supplementary service. + +The coding of the called party number information element is described in Recommendation Q.951.2. + +#### **3.1.2.3 Calling Line Identification Presentation (CLIP)** + +If the called user has subscribed to the CLIP service, one or two calling party number information elements are sent in the SETUP message. + +**Table 92/Q.699 – CLIP information sent to the called user** + +| IAM→ | | SETUP→ | +|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Calling party number parameter Address presentation restricted indicator | Generic number parameter with number qualifier set to additional calling party number | CLIP information sent to the calling user | +| Presentation allowed | Absent | Calling party number i.e.
(see Table 94) | +| Presentation allowed | Present | Calling party number i.e. (Note 1)
(see Table 94)
Calling party number i.e. (Note 1)
(see Table 93) | +| Presentation restricted
(Note 2) | Value non-significant | Calling party number i.e.
Option 1:
Type of number As received
Numbering plan As received
Presentation ind. Presentation restricted
Screening ind. As received
Number digits No digit
Option 2:
Type of number Unknown
Numbering plan Unknown
Presentation ind. Presentation restricted
Screening ind. Network provided
Number digits No digit | +| Address not available
or
No calling party number parameter | Value non-significant | Calling party number i.e.
Type of number Unknown
Numbering plan Unknown
Presentation ind. Not available due to interworking
Screening ind. Network provided
Number digits No digit | + +NOTE 1 – If the two calling party number delivery option does not apply: +– only one calling party number information element is sent on DSS 1 side. The generic number is used (see Table 94). +If the two calling party number delivery option applies: +– two calling party number information elements are sent on DSS 1 side: one coded according to the generic number parameter (see Table 94), one according to the calling party number parameter (see Table 93). The order in which the calling party number information elements appear in the SETUP message is a network option. + +NOTE 2 – As a national option, the presentation restriction indication received in the calling party number parameter can be overridden for specific calling access' categories. In such a case, the same actions are taken as if *presentation allowed* was received, except for the presentation restriction indication which is passed transparently into the calling party number information element. + +**Table 93/Q.699 – Coding of the calling party number information element according to the calling party number parameter** + +| IAM→ | SETUP→ | +|------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| Calling party number parameter | Calling party number i.e. | +| Nature of address indicator
National number
International number | Type of number (Note)
National number
International number | +| Numbering plan indicator
ISDN/Telephony numbering plan | Numbering plan identification
ISDN/Telephony numbering plan | +| Address presentation restricted indicator
Presentation allowed
Presentation restricted | Presentation indicator
Presentation allowed
Presentation restricted | +| Screening indicator
User provided, verified and passed
Network provided | Screening indicator
User provided, verified and passed
Network provided | +| Address signals | Number digits | +| NOTE – As a network option, the type of number may be coded unknown when a prefix is added to the number. | | + +**Table 94/Q.699 – Coding of the calling party number information element according to the generic number parameter** + +| IAM→ | SETUP→ | +|------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| Generic number parameter
with number qualifier set to
additional calling party number | Calling party number i. e. | +| Nature of address indicator
National number
International number | Type of number (Note)
National number
International number | +| Numbering plan indicator
ISDN/Telephony numbering plan | Numbering plan identification
ISDN/Telephony numbering plan | +| Address presentation restricted indicator
Presentation allowed
Presentation restricted | Presentation indicator
Presentation allowed
Presentation restricted | +| Screening indicator
User provided, not verified | Screening indicator
User provided, not verified | +| Address signals | Number digits | +| NOTE – As a network option, the type of number may be coded unknown when a prefix is added to the number. | | + +##### Calling party sub-address + +**Table 95/Q.699 – Sending of the calling party subaddress** + +| IAM→ | | SETUP→ | +|------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-------------------------------------------------| +| Address presentation restricted indicator of the Calling party number parameter | Access transport parameter | Content | +| Presentation allowed | Calling party subaddress information element | Calling party subaddress information element | +| Presentation restricted (Note)
or
Address not available
or
No calling party number parameter | Calling party subaddress information element | No calling party subaddress information element | + +NOTE – As a national option, the presentation restriction indication received in the calling party number parameter can be overrid for specific calling access' categories. In such a case, the same actions are taken as if *presentation allowed* was received. + +#### 3.1.2.4 Calling Line Identification Restriction (CLIR) + +See Table 92. + +#### 3.1.2.5 Connected Line Identification Presentation (COLP) + +If the connected line identity request indicator of the optional forward call indicators parameter in the Initial Address Message (IAM) is received coded to *requested*, then the connected number and possibly the generic number parameter and the connected sub-address are sent in the answer or connect message as described in Tables 96 and 97. + +##### 3.1.2.5.1 Special arrangement applies + +**Table 96/Q.699 – COLP – Special arrangement applies** + +| ←ANM, CON | | | | ←CONNECT | | | | +|-----------------------------------------------------------------------------------|-----------------------------------|-----------------------------------------|------------------------------------------|--------------------------------------------------------------|-----------------------------|--|--| +| Coding of the connected number and generic number parameters | | | | Connected number i.e. | | | | +| Address signals | Numbering plan indicator | Nature of address indicator | Screening indicator | Numbering plan identification | Type of number | | | +| Connected number parameter | | | | | | | | +| Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | No or invalid (Note 1) connected number information element | | | | +| No generic number parameter indicating additional connected number is sent | | | | ISDN/telephony numbering plan
or
Unknown | National number | | | +| Connected number parameter | | | | | | | | +| Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | | | | | +| Generic number parameter (Note 2) | | | | | | | | +| Number provided by the user | 001
ISDN numbering plan | 000 0011
National number | 00
User provided, not verified | | | | | +| Connected number parameter | | | | ISDN/telephony numbering plan
or
unknown | international number | | | +| Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | | | | | +| Generic number parameter (Note 2) | | | | | | | | +| Number provided by the user | 001
ISDN numbering plan | 000 0100
International number | 00
User provided, not verified | | | | | + +NOTE 1 – Validity conditions of the connected number information element are defined in 5.5.2.3/Q.951 [14]. + +NOTE 2 – The generic number parameter contains the number qualifier indicator coded "0000 0101" (*additional connected number*). + +The address presentation restricted indicator of the connected number and generic number parameters shall be set according to the COLR supplementary service. + +The number incomplete indicator of the generic number parameter shall be set to "0" (*complete*). + +###### Connected subaddress + +If provided, the connected subaddress is transported transparently in the access transport parameter of the answer or connect message. + +##### 3.1.2.5.2 Special arrangement does not apply + +**Table 97/Q.699 – COLP – Special arrangement does not apply** + +| ←ANM, CON | | | | ←CONNECT | | | | | | +|-------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------|--|--|--| +| Coding of the connected number and generic number parameters | | | | Connected number information element | | | | | | +| Address signals | Numbering plan indicator | Nature of address indicator | Screening indicator | Type of number | Numbering plan identification | Number digits | | | | +| Connected number parameter | | | | No or invalid (Note) connected number information element | | | | | | +| Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | | | | | | | +| No generic number parameter indicating additional connected number is sent | | | | | | | | | | +| Connected number parameter | | | | Failure of the screening function | | | | | | +| Default number | 001
ISDN numbering plan | 000 0011
National number | 11
Network provided | | | | | | | +| No generic number parameter indicating additional connected number is sent | | | | | | | | | | +| Connected number parameter | | | | Subscriber number

National number
or
International number | ISDN/telephony numbering plan
or

Unknown | Correct complete number | | | | +| Number provided by the user | 001
ISDN numbering plan | As received | 01
User provided, verified and passed | | | | | | | +| No generic number parameter indicating additional connected number is sent | | | | | | | | | | +| Connected number parameter | | | | Unknown | ISDN/telephony numbering plan
or

Unknown | Incomplete number | | | | +| Completion of the number provided by the user | 001
ISDN numbering plan | 000 0011
National number | 01
User provided, verified and passed | | | | | | | +| No generic number parameter indicating additional connected number is sent | | | | | | | | | | +| NOTE – Validity conditions of the connected number information element are defined in section 5.5.2.3/Q.951 [14]. | | | | | | | | | | + +The address presentation restricted indicator of the connected number parameter shall be set according to the COLR supplementary service. + +###### Connected subaddress + +If provided, the connected subaddress is transported transparently in the access transport parameter of the Answer (ANM) or Connect (CON) message. + +#### 3.1.2.6 Connected Line Identification Restriction (COLR) + +The address presentation restricted indicator of the connected number and of the generic number is coded as described in Table 98. + +NOTE – If the called user has not subscribed to the COLR supplementary service, the address presentation restricted indicator of the connected number parameter is set to *presentation allowed* (see 6.10/Q.951 [14]). + +**Table 98/Q.699 – Coding of the address presentation restricted indicator of the connected number and generic number parameters** + +| ←ANM/CON | ←CONNECT | Internal data | | +|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|--------------------------------|----------------| +| | | Temporary mode default setting | Permanent mode | +| Connected number/
generic number
parameter

Address presentation
restricted indicator | Connected number
information element

Presentation indicator | | | +| Presentation restricted | Value non-significant | Value non-significant | Yes | +| Presentation restricted | Presentation restricted | Restricted | No | +| Presentation restricted | Absent | | | +| Presentation allowed | Presentation allowed | Allowed | | +| Presentation allowed | Presentation allowed | | | +| Presentation allowed | Absent | | | +| Presentation restricted | Presentation restricted | | | + +#### 3.1.2.7 Sub-addressing (SUB) + +The called party subaddress information element received in the access transport parameter of the Initial Address Message (IAM) is transferred transparently in the SETUP message. + +#### 3.1.2.8 Call diversion + +##### 3.1.2.8.1 Interworking at the exchange where a call is diverted within or beyond the private ISDN + +For further study. + +##### 3.1.2.8.2 Interworking at the coincident S and T reference point where a diverted call is presented + +For further study. + +##### 3.1.2.8.3 Interworking at the exchange where a diverted call is presented to a private ISDN + +For further study. + +##### 3.1.2.8.4 Interworking at the exchange where partial rerouting is requested from a private ISDN + +For further study. + +#### 3.1.2.9 Call Waiting (CW) + +##### 3.1.2.9.1 Procedure at coincident S and T reference point + +If the call is presented with indication *no channel* in the information channel selection field of the channel identification information element in the SETUP message, and depending on the subscription options offered by the network, a notification is sent in the network upon receipt of the alerting indication. + +**Table 99/Q.699 – Sending of CW notification** + +| ←ACM, CPG | ←ALERTING | +|-------------------------------------------|-----------| +| Generic notification indicator parameter | | +| Notification indicator | | +| 110 0000
Call is a waiting call | | + +##### 3.1.2.9.2 Notification received at T reference point + +A CW notification may be received at T reference point in the ALERTING message. + +**Table 100/Q.699 – Receipt of a CW notification from a private network** + +| ←ACM, CPG
(Note) | ←ALERTING/PROGRESS/NOTIFY | +|-------------------------------------------|--------------------------------------------| +| Generic notification indicator parameter | Notification indicator information element | +| Notification indicator | Notification description | +| 110 0000
Call is a waiting call | 110 0000
Call is a waiting call | + +NOTE – In case of receipt of ALERTING or PROGRESS, ACM or CPG is sent as described in 3.1.1. In case of receipt of NOTIFY, CPG is sent with the event indicator coded *progress*. + +#### 3.1.2.10 Call Hold (HOLD) + +##### 3.1.2.10.1 Notification received from the network + +**Table 101/Q.699 – HOLD notification** + +| CPG→ | NOTIFY or FACILITY→ | +|------------------------------------------|--------------------------------------------| +| Generic notification indicator parameter | Notification indicator information element | +| Notification indicator | Notification description | +| 111 1001
Remote hold | 111 1001
Remote hold | +| 111 1010
Remote retrieval | 111 1010
Remote retrieval | + +##### 3.1.2.10.2 Invocation at coincident S and T reference point + +**Table 102/Q.699 – HOLD invocation** + +| ←CPG | | Message received from the DSS 1 | +|-----------------------------|------------------------------------------|----------------------------------------| +| Event information parameter | Generic notification indicator parameter | | +| Event indicator | Notification indicator | | +| 000 0010
Progress | 111 1001
Remote hold | HOLD | +| 000 0010
Progress | 111 1010
Remote retrieval | RETRIEVE | + +##### 3.1.2.10.3 Notification received at T reference point + +A HOLD notification may be received at T reference point in the active phase of the call. + +**Table 103/Q.699 – Receipt of a HOLD notification from a private network** + +| ←CPG | | ←NOTIFY | +|-----------------------------|------------------------------------------|--------------------------------------------| +| Event information parameter | Generic notification indicator parameter | Notification indicator information element | +| Event indicator | Notification indicator | Notification description | +| 000 0010
Progress | 111 1001
Remote hold | 111 1001
Remote hold | +| 000 0010
Progress | 111 1010
Remote retrieval | 111 1010
Remote retrieval | + +#### 3.1.2.11 Terminal Portability (TP) + +##### 3.1.2.11.1 Notification received from the network + +**Table 104/Q.699 – TP notification** + +| Message received from the ISUP
→ | NOTIFY→ | +|-----------------------------------------------------------------------------|----------------------------------------------------------| +| | Notification indicator i. e.
Notification description | +| SUS message
Suspend/resume indicator
ISDN subscriber initiated | 000 0000
User suspended | +| RES message
Suspend/resume indicator
ISDN subscriber initiated | 000 0001
User resumed | +| CPG message
Generic notification indicator
User suspended | 000 0000
User suspended | +| CPG message
Generic notification indicator
User resumed | 000 0001
User resumed | + +##### 3.1.2.11.2 Invocation at coincident S and T reference point + +**Table 105/Q.699 – TP invocation** + +| Message sent to the ISUP
← | Message received from the DSS 1
← | +|-----------------------------------------------------------------------------|--------------------------------------| +| SUS message
Suspend/resume indicator
ISDN subscriber initiated | SUSPEND | +| RES message
Suspend/resume indicator
ISDN subscriber initiated | RESUME | + +The actions taken on the access side upon receipt of the SUSPEND and RESUME messages are described in 5.6/Q.931 and Figure A.6/Q.931. + +The actions taken on the ISUP side upon sending of the Suspend (SUS) and Resume (RES) messages are described in 4.5.2.1/Q.733 [10]. + +Upon the T2 expiry (Note), a Release message (REL) is sent with the cause value No. 102, *recovery on timer expiry*. No action is taken on the DSS 1 side. + +NOTE – T2 start, stop, and expiry are described in 4.5.2.1/Q.733 [10] and Annex A/Q.764 [4]. T307 start, stop and expiry are described in 5.6/Q.931. + +##### 3.1.2.11.3 Notification received at T reference point + +A TP notification may be received at T reference point in the active phase of the call. + +**Table 106/Q.699 – Receipt of a TP notification from a private network** + +| ←CPG | | ←NOTIFY | +|-----------------------------|------------------------------------------|--------------------------------------------| +| Event information parameter | Generic notification indicator parameter | Notification indicator information element | +| Event indicator | Notification indicator | Notification description | +| 000 0010
Progress | 000 0000
User suspended | 000 0000
User suspended | +| 000 0010
Progress | 000 0001
User resumed | 000 0001
User resumed | + +#### 3.1.2.12 Conference calling (CONF) + +##### 3.1.2.12.1 Notification received from the network + +**Table 107/Q.699 – Conference calling notification** + +| CPG→ | NOTIFY→ | +|---------------------------------------------|---------------------------------------------| +| Generic notification indicator parameter | Notification indicator information element | +| Notification indicator | Notification description | +| 100 0010
Conference established | 100 0010
Conference established | +| 100 0011
Conference disconnected | 100 0011
Conference disconnected | +| 100 0100
Other party added | 100 0100
Other party added | +| 100 0101
Isolated | 100 0101
Isolated | +| 100 0110
Reattached | 100 0110
Reattached | +| 100 0111
Other party isolated | 100 0111
Other party isolated | +| 100 1000
Other party reattached | 100 1000
Other party reattached | +| 100 1001
Other party split | 100 1001
Other party split | +| 100 1010
Other party disconnected | 100 1010
Other party disconnected | +| 100 1011
Conference floating | 100 1011
Conference floating | + +##### 3.1.2.12.2 Invocation at coincident S and T reference point + +Table 108/Q.699 – Conference calling + +| Message sent to all other remote users
← | Message sent to B
← | Message received from served user
← | Procedure | +|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| Not applicable | CPG
Generic notification indicator parameter
Conference established | FACILITY
Facility i.e.
BeginCONF-Inv
Call reference i.e.
Call reference of existing call | Beginning the conference from an active call (with B) | +| CPG
Generic notification indicator parameter
Other party added | CPG
Generic notification indicator parameter
Conference established | FACILITY
Facility i.e.
AddCONF-Inv
Call reference i.e.
call reference of call to be added | Adding a remote user (B) | +| CPG
Generic notification indicator parameter
Other party isolated | CPG
Generic notification indicator parameter
Isolated | FACILITY
Facility i.e.
IsolateCONF-Inv | Isolate a remote user (B) | +| CPG
Generic notification indicator parameter
Other party reattached | CPG
Generic notification indicator parameter
Reattached | FACILITY
Facility i.e.
ReattachCONF-Inv | Reattach a remote user (B) | +| CPG
Generic notification indicator parameter
Other party split | CPG
Generic notification indicator parameter
Conference disconnected | SETUP (Note)
Facility i.e.
SplitCONF-Inv | Splitting a remote user (B) | +| CPG
Generic notification indicator parameter
Other party disconnected | REL | FACILITY
Facility i.e.
DropCONF-Inv | Disconnect a remote user (B) | + +**Table 108/Q.699 – Conference calling (concluded)** + +| Message sent to all other remote users
← | Message sent to B
← | Message received from served user
← | Procedure | +|--------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------------------------------|-------------------------------------| +| REL | | FACILITY
Facility i.e.
EndCONF-Inv | Terminate the conference | +| CPG
Generic notification indicator parameter
Conference floating | | FACILITY
Facility i.e.
FloatCONF-Inv | Disconnect the served user | +| If the conditions for floating are met:
CPG
Generic notification indicator parameter
Conference floating | | DISCONNECT | Call clearing by served user | +| If the conditions for floating are not met:
REL | | | | + +NOTE – This SETUP message does not contain any called party information but contains a bearer capability information element (see 1.5.2.6.1/Q.954 [17]). + +**Table 109/Q.699 – Conference calling: a remote user clears** + +| Message received from B
→ | Message sent to served user
→ | Procedure | +|------------------------------|--------------------------------------------|--------------------| +| REL | FACILITY
Facility i.e.
PartyDisc-Inv | Remote user clears | + +##### 3.1.2.12.3 Notification received at T reference point + +**Table 110/Q.699 – Receipt of a conference calling notification from a private network** + +| ←CPG | | ←NOTIFY | +|-----------------------------|---------------------------------------------|---------------------------------------------| +| Event information parameter | Generic notification indicator parameter | Notification indicator information element | +| Event indicator | Notification indicator | Notification description | +| 000 0010
Progress | 100 0010
Conference established | 100 0010
Conference established | +| 000 0010
Progress | 100 0011
Conference disconnected | 100 0011
Conference disconnected | +| 000 0010
Progress | 100 0100
Other party added | 100 0100
Other party added | +| 000 0010
Progress | 100 0101
Isolated | 100 0101
Isolated | +| 000 0010
Progress | 100 0110
Reattached | 100 0110
Reattached | +| 000 0010
Progress | 100 0111
Other party isolated | 100 0111
Other party isolated | +| 000 0010
Progress | 100 1000
Other party reattached | 100 1000
Other party reattached | +| 000 0010
Progress | 100 1001
Other party split | 100 1001
Other party split | +| 000 0010
Progress | 100 1010
Other party disconnected | 100 1010
Other party disconnected | +| 000 0010
Progress | 100 1011
Conference floating | 100 1011
Conference floating | + +#### 3.1.2.13 Three-party (3PTY) + +##### 3.1.2.13.1 Notification received from the network + +**Table 111/Q.699 – 3PTY notification** + +| CPG→ | NOTIFY→ | +|--------------------------------------------|--------------------------------------------| +| Generic notification indicator parameter | Notification indicator information element | +| Notification indicator | Notification description | +| 100 0010
Conference established | 100 0010
Conference established | +| 100 0011
Conference disconnected | 100 0011
Conference disconnected | +| 111 1001
Remote hold | 111 1001
Remote hold | + +If the Call Progress Message (CPG) contains two generic notification indicator parameters, one with the notification indicator coded *conference disconnected*, the other with the notification indicator coded *remote hold*, + +- either a NOTIFY message is sent containing: + - a notification indicator information element with the notification description *conference disconnected*; and + - a Notification indicator information element with the notification description *remote hold*; +- or + - a NOTIFY message is sent containing a notification indicator information element with the notification description *conference disconnected*; and + - a subsequent NOTIFY message is sent containing a notification indicator information element with the notification description *remote hold*. + +##### 3.1.2.13.2 Invocation at coincident S and T reference point + +Table 112/Q.699 – Three-Party (3PTY) + +| Call A-B: Active-held connection message sent to B
← | Call A-C: Active-idle connection message sent to C
← | Message received from served user
← | Procedure | +|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------| +| ←CPG
Generic notification indicator parameter
Conference established | ←CPG
Generic notification indicator parameter
Conference established | ←FACILITY
Facility i.e.
Begin3PTY-Inv
Call reference i.e.
Call reference of call A-B | Beginning the 3PTY | +| ←CPG
Generic notification indicator parameter
Remote hold | ←CPG
Generic notification indicator parameter
Conference disconnected | ←FACILITY
Facility i.e.
End3PTY-Inv
Call reference i.e.
Call reference of call A-B | | +| No message sent | ←CPG
Generic notification indicator parameter
Remote hold | ←HOLD
Call reference i.e.
Call reference of call A-C | Creation of a private communication with B | +| ←CPG
Generic notification indicator parameter
Conference disconnected | No message sent | ←RETRIEVE
Call reference i.e.
Call reference of call A-B | | + +**Table 112/Q.699 – Three-Party (3PTY) (concluded)** + +| Call A-B: Active-held connection message sent to B
← | Call A-C: Active-idle connection message sent to C
← | Message received from served user
← | Procedure | +|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|---------------------------------------------------| +| ←CPG
Generic notification indicator parameter
Conference disconnected
Generic notification indicator parameter
Remote hold | ←CPG
Generic notification indicator parameter
Conference disconnected | ←FACILITY
Facility i.e.
End3PTY-Inv
Call reference i.e.
Call reference of call A-C | Creation of a private communication with C | +| ←REL | ←CPG
Generic notification indicator parameter
Conference disconnected | ←DISCONNECT
Call reference i.e.
Call reference of call A-B | Disconnect the remote user B | +| ←CPG
Generic notification indicator parameter
Remote hold | ←REL | ←DISCONNECT
Call reference i.e.
Call reference of call A-C | Disconnect the remote user C | +| ←CPG
Generic notification indicator parameter
Conference disconnected | Not applicable | ←RETRIEVE
Call reference i.e.
Call reference of call A-B | | + +Table 113 describes the actions taken when user B or user C disconnects. + +**Table 113/Q.699 – Three-party (3PTY): user B or user C disconnects** + +| Procedure | Call A-C: Active-idle connection message sent to C or received from C | Call A-B: Active-held connection messages sent to B or received from B | Messages sent to or received from served user | +|---------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------| +| User B disconnects | ←CPG
Generic notification indicator parameter
Conference disconnected | REL→ | DISCONNECT→
Call reference i.e.
Call reference of call A-B | +| User C disconnects | REL→ | ←CPG
Generic notification indicator parameter
Remote hold | DISCONNECT→
Call reference i.e.
Call reference of call A-C | +| | Not applicable | ←CPG
Generic notification indicator parameter
Conference disconnected | ←RETRIEVE
Call reference i.e.
Call reference of call A-B | + +Upon receipt from a remote user of a Release message (REL), that call is released according to normal call release procedure and a Call Progress message (CPG) is sent through the network to the other remote user with the event information parameter coded *progress* and the generic notification indicator coded *conference disconnected*. + +##### 3.1.2.13.3 Notification received at T reference point + +**Table 114/Q.699 – Receipt of a 3PTY notification from a private network** + +| ←CPG | | ←NOTIFY | +|--------------------------------------------|-----------------------------|--------------------------------------------| +| Generic notification indicator parameter | Event information parameter | Notification indicator information element | +| Notification indicator | Event indicator | Notification description | +| 100 0010
Conference established | 000 0010
Progress | 100 0010
Conference established | +| 100 0011
Conference disconnected | 000 0010
Progress | 100 0011
Conference disconnected | +| 111 1001
Remote hold | 000 0010
Progress | 111 1001
Remote hold | + +#### 3.1.2.14 Closed User Group (CUG) + +CUG checks at the destination exchange and determination of the type of call request in correlation with the CUG information received in the Initial Address Message (IAM) message and the CUG attributes of the called user are described in Table 1-4/Q.735 [12]. + +The coding of the facility information element sent in the SETUP message is described in 1.5.2/Q.955 [18]. + +A rejection indication may be received in a DSS 1 call clearing message prior alerting phase. + +**Table 115/Q.699 – Receipt of a rejection indication** + +| ←REL | ←DISCONNECT, RELEASE or
RELEASE COMPLETE | | +|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------|----------------------------| +| Cause parameter | Return error component | Cause information element | +| Cause value No. 87
User not member of CUG | Return error value #20
userNotMemberOfCUG | Any basic call cause value | +| Cause value No. 87
User not member of CUG | Return error value #16
invalidOrUnregisteredCUG Index | Any basic call cause value | +| Cause value No. 87
User not member of CUG | Return error value #17
requestedBasicServiceViolatesCUGConstraints | Any basic call cause value | +| As received from DSS 1 | Return error value #21
inconsistencyInDesignatedFacilityAnd
SubscriberClass | Any basic call cause value | +| Cause value No. 55
Incoming calls barred within
CUG | Return error value #19
incomingCallsBarredWithinCUG | Any basic call cause value | +| As received from DSS 1 | Return error value #8
basicServiceNotProvided | Any basic call cause value | +| As received from DSS 1 | None | Any basic call cause value | + +NOTE – This table provides examples of mapping. + +#### 3.1.2.15 User-to-User Signalling (UUS) + +##### 3.1.2.15.1 Service 1 (UUS1) implicit + +Service 1 may be requested implicitly by the presence of the user-to-user information parameter of the Initial Address Message (IAM) which is mapped into the user-user information element in the SETUP message. + +If service 1 is requested: + +**Table 116/Q.699 – Implicit UUS1 transfer** + +| ISUP messages | DSS 1 messages | +|------------------------------------------------------------------------------------|------------------------------------------------------------------| +| ACM, CPG, ANM,
CON, REL, SGM
(Note)
← | ALERTING, CONNECT, DISCONNECT,
RELEASE, RELEASE COMPLETE
← | +| User-to-user information parameter | User-user information element | +| REL
→ | DISCONNECT
→ | +| User-to-user information parameter | User-user information element | +| NOTE – The correspondences between ISUP and DSS 1 messages are described in 3.1.1. | | + +If there is no user-user information element in the SETUP message, the exchange should discard the user-to-user information possibly received afterwards from the access or from the ISUP side. + +##### 3.1.2.15.2 Service 1 (UUS1) explicit + +**Table 117/Q.699 – Explicit UUS1 invocation** + +| IAM→ | SETUP→ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| Content | Content | +| User-to-user indicators parameter
Type Request
Service 1 Request, not essential | Facility information element
UserUserService invoke component
Service 1 preferred | +| User-to-user information parameter (Note) | User-user information element | +| User-to-user indicators parameter
Type Request
Service 1 Request, essential | Facility information element
UserUserService invoke component
Service 1 required | +| User-to-user information parameter (Note) | User-user information element | +| NOTE – The user-user information element is optional for the invocation. When absent, the user-to-user parameter is not included in the SETUP message. | | + +**Table 118/Q.699 – Explicit UUS1 acceptance** + +| ←Corresponding message
(ACM, CPG, ANM, CON or REL) | ←First backward message
(ALERTING, CONNECT, or release message) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Response
Service 1 Provided
Service 2 No information (Note)
Service 3 No information (Note) | Facility information element

UserUserService return result component | + +NOTE – These indicators may be coded in a different way if service 2 (respectively service 3) information have to be transported: see Tables 122, 124, 126 and 132. + +In case of acceptance of service, user-user information may be exchanged in all the call control messages: see Table 119. + +**Table 119/Q.699 – Explicit UUS1 transfer** + +| ISUP messages | DSS 1 messages | +|------------------------------------------------|------------------------------------------------------------------| +| ACM, CPG, ANM,
CON, REL, SGM
(Note)
← | ALERTING, CONNECT, DISCONNECT,
RELEASE, RELEASE COMPLETE
← | +| User-to-user information parameter | User-user information element | +| REL
→ | DISCONNECT
→ | +| User-to-user information parameter | User-user information element | + +NOTE – The correspondences between ISUP and DSS 1 messages are described in 3.1.1. + +###### Service 1 rejection + +**Table 120/Q.699 – UUS1 rejection** + +| ISUP messages | DSS 1 messages | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←REL | ←DISCONNECT or RELEASE COMPLETE | +| Cause parameter
Value No. 69 ( requested facility not implemented )
Diagnostic UUI indicators parameter's name | Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | +| ←REL | DISCONNECT, RELEASE or RELEASE COMPLETE
Prior active state
← | +| Cause parameter
Value As received
User-to-user indicators parameter
Type Response
Service 1 Not provided
Service 2 No information (Note 1)
Service 3 No information (Note 1) | Cause information element
Value Other than No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | +| ←ACM, CPG, ANM, or CON (Note 2) | ←ALERTING or CONNECT (Note 3) | +| User-to-user indicators parameter
Type Response
Service 1 Not provided
Service 2 No information (Note 1)
Service 3 No information (Note 1) | Facility information element
UserUserService return error component
rejectedByUser | + +NOTE 1 – This field may be coded in a different way if a service 2 (respectively service 3) acceptance or rejection indication have to be carried: see Tables 122, 124, 126 and 132. + +NOTE 2 – The correspondence between the DSS 1 message received from the called user and the DSS 1 message sent is described in 3.1.1 + +NOTE 3 – In case of call contention, only the indication possibly received in the CONNECT message is taken into account. + +##### 3.1.2.15.3 Service 2 + +**Table 121/Q.699 – UUS2 invocation** + +| IAM→ | SETUP→ | +|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| Content | Content | +| User-to-user indicators parameter
Type Request
Service 2 Request, not essential | Facility information element
UserUserService invoke component
Service 2 preferred | +| User-to-user indicators parameter
Type Request
Service 2 Request, essential | Facility information element
UserUserService invoke component
Service 2 required | + +Service 2 acceptance is indicated in the alerting information received from the remote user. + +**Table 122/Q.699 – UUS2 acceptance** + +| ←ACM, CPG | ←ALERTING | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Response
Service 1 No information (Note)
Service 2 Provided
Service 3 No information (Note) | Facility information element

UserUserService return result component | + +NOTE – These indicators may be coded In a different way if service 1 (respectively service 3) information have to be transported: see Tables 118, 120, 126, 132. + +When acceptance of Service 2 has been received, user-user information may be exchanged during the alerting phase of the call: see Table 123. + +**Table 123/Q.699 – UUS2 transfer** + +| ISUP messages | DSS 1 messages | +|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| USR→ | USER INFORMATION→ | +| User-to-user information parameter
Access transport parameter
More data information element | User-user information element
More data information element | +| ←USR | ←USER INFORMATION | +| User-to-user information parameter
Access transport parameter
More data information element | User-user information element
More data information element | + +###### Service 2 rejection + +Table 124/Q.699 – UUS2 rejection + +| ISUP messages | DSS 1 messages | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←REL | ←DISCONNECT or RELEASE COMPLETE | +| Cause parameter
Value No. 69 ( requested facility not implemented )
Diagnostic UUI indicators parameter's name | Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | +| ←REL | DISCONNECT, RELEASE or RELEASE COMPLETE
Prior active state
← | +| Cause parameter
Value As received
User-to-user indicators parameter
Type Response
Service 1 No information (Note 1)
Service 2 Not provided
Service 3 No information (Note 1) | Cause information element
Value Other than No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | +| ←ACM or CPG (Note 2) | ←ALERTING | +| User-to-user indicators parameter
Type Response
Service 1 No information (Note 1)
Service 2 Not provided
Service 3 No information (Note 1) | Facility information element
UserUserService return error component
rejectedByUser | + +**Table 124/Q.699 – UUS2 rejection (concluded)** + +| ISUP messages | DSS 1 messages | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Service 2 required
←REL
Cause parameter
Value No. 88 ( destination incompatible )
Diagnostic UUI indicators parameter's name | Point-to-multipoint arrangement | +| Service 2 preferred
←ACM or CPG (Note 3)
User-to-user indicators parameter
Type Response
Service 1 No information (Note 1)
Service 2 Not provided
Service 3 No information (Note 1) | | +| NOTE 1 – This field may be coded in a different way if a service 1 (respectively service 3) acceptance or rejection indication have to be carried: see Tables 118, 120, 126 and 132.
NOTE 2 – The mapping of an ALERTING message into an Address Complete (ACM) or a Call Progress (CPG) message is described in 3.1.1.
NOTE 3 – Message sent upon receipt of the first ALERTING message from the called user. | | + +##### 3.1.2.15.4 Service 3 + +Service 3 may be invoked during the call establishment. + +**Table 125/Q.699 – UUS3 invocation during the call establishment** + +| IAM→ | SETUP→ | +|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Request
Service 3 Request, not essential | Facility information element
UserUserService invoke component
Service 3 preferred | +| User-to-user indicators parameter
Type Request
Service 3 Request, essential | Facility information element
UserUserService invoke component
Service 3 required | + +Service 3 acceptance is indicated in the connecting information received from the remote user. + +**Table 126/Q.699 – UUS3 acceptance** + +| ←ANM, CON | ←CONNECT | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Response
Service 1 No information (Note)
Service 2 No information (Note)
Service 3 Provided | Facility information element

UserUserService return result component | + +NOTE – These indicators may be coded in a different way if service 1 (respectively service 2) information have to be transported: see Tables 118, 120, 122, 124. + +If not already done before, service 3 may be invoked by either the calling user (see Tables 127 and 128) or the called user (see Tables 129 and 130). + +**Table 127/Q.699 – UUS3 invocation received from the calling user in active phase** + +| Facility request message (FAR)
→ | FACILITY
→ | +|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Request
Service 3 Request, not essential | Facility information element
UserUserService invoke component
Service 3 preferred | + +**Table 128/Q.699 – UUS3 acceptance received from the called user in active phase** + +| Facility accepted message (FAA)
← | FACILITY
← | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Response
Service 1 No information
Service 2 No information
Service 3 Provided | Facility information element

UserUserService return result component | + +**Table 129/Q.699 – UUS3 invocation received from the called user in active phase** + +| Facility request message (FAR)
← | FACILITY
← | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Request
Service 1 No information
Service 2 No information
Service 3 Request, not essential | Facility information element
UserUserService invoke component
Service 3 preferred | + +**Table 130/Q.699 – UUS3 acceptance received from the calling user in active phase** + +| Facility accepted message (FAA)
→ | FACILITY
→ | +|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| User-to-user indicators parameter
Type Response
Service 3 Provided | Facility information element
UserUserService return result component | + +When acceptance of service 3 has been received, user-user information may be exchanged during the active phase of the call: see Table 131. + +**Table 131/Q.699 – UUS3 transfer** + +| ISUP messages | DSS 1 messages | +|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| User-to-User information (USR)→ | USER INFORMATION→ | +| User-to-user information parameter
Access transport parameter
More data information element | User-user information element
More data information element | +| ←User-to-User information (USR) | ←USER INFORMATION | +| User-to-user information parameter
Access transport parameter
More data information element | User-user information element
More data information element | + +###### Service 3 rejection + +Rejection of service 3 requested during call establishment + +**Table 132/Q.699 – Rejection of service 3 requested during call establishment** + +| ISUP messages | DSS 1 messages | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ←REL | ←DISCONNECT or RELEASE COMPLETE | +| Cause parameter
Value No. 69 ( requested facility not implemented )
Diagnostic UUI indicators parameter's name | Cause information element
Value No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | +| ←REL | DISCONNECT, RELEASE or RELEASE COMPLETE
prior active state
← | +| Cause parameter
Value As received
User-to-user indicators parameter
Type Response
Service 1 No information (Note 1)
Service 2 No information (Note 1)
Service 3 Not provided | Cause information element
Value other than No. 69 ( requested facility not implemented )
Facility information element
UserUserService return error component
rejectedByUser | +| ←ANM or CON (Note 2) | ←CONNECT | +| User-To-User Indicators Parameter
Type Response
Service 1 No Information (Note 1)
Service 2 No Information (Note 1)
Service 3 Not Provided | Facility information element
UserUserService return error component
rejectedByUser | + +NOTE 1 – This field may be coded in a different way if a service 1 (respectively service 2) acceptance or rejection indication have to be carried: see Tables 118, 120, 122 and 124. +NOTE 2 – The mapping of a CONNECT message into an Answer (ANM) or a Connect (CON) message is described in 3.1.1. + +Rejection of service 3 requested after call establishment + +**Table 133/Q.699 – Rejection of service 3 requested by the calling user after call establishment** + +| ISUP messages | DSS 1 messages | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| ←FRJ | ←FACILITY | +| User-to-user indicators parameter
Type Response
Service 1 No information
Service 2 No information
Service 3 Not provided
Cause parameter
Value       No. 69 ( requested facility not implemented ) | Facility information element
UserUserService return error component
rejectedByUser | +| ←FRJ | | +| User-to-user indicators parameter
Type Response
Service 1 No information
Service 2 No information
Service 3 Not provided
Cause parameter
Value       No. 69 ( requested facility not implemented ) | T1 expiry (Note) | +| FRJ Facility reject message
NOTE – T1 start and normal stop are described in 1.5.2.3/Q.957 [19]. | | + +**Table 134/Q.699 – Rejection of UUS3 requested by the called user after call establishment** + +| ISUP messages | DSS 1 messages | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| FRJ→ | FACILITY→ | +| User-to-user indicators parameter
Type Response
Service 3 Not provided | Facility information element
UserUserService return error component
rejectedByUser (Note) | +| FRJ Facility reject message
NOTE – Since it is not possible to know if the rejection is due to the network or to the remote user, the default value RejectedByUser is used. | | + +## 3.2 Interworking from ISUP to non-ISDN access + +### 3.2.1 Basic call + +#### 3.2.1.1 Sending of the ringing + +The call information are received in the Initial Address Message (IAM), possibly followed by one or several Subsequent Address Messages (SAM) (See 3.1.1.2). + +If the continuity check indicator of the nature of connection indicators is coded 01, *continuity check required on this circuit*, or 10, *continuity check required on a previous circuit*, the setting up of the call must be prevented until the receipt of the result of the continuity check procedure. + +When the exchange has received all the information required to go on with the call, and performed the various checks to determine that the call is allowed, the call set-up indication, e.g. ringing, is passed to the called user. + +#### 3.2.1.2 Receipt of the Subsequent Address Message (SAM) + +The call set-up indication upon receiving the Subsequent Address Message (SAM) is shown in 3.2.1.1. + +#### 3.2.1.3 Sending of the Address Complete Message (ACM) + +The following cases are possible trigger conditions of sending the Address Complete Message (ACM): + +- The destination exchange has determined independently of line conditions that the complete called party number has been received. +- The destination exchange has determined that the subscriber is free. +- It has been determined, in case of call failure, that a special in-band tone or announcement has to be returned to the calling party from the destination exchange. + +##### MANDATORY PARAMETERS + +##### Backward call indicators + +| | | | +|------|-----|-----------------------------------------------------------------------------------------------| +| bits | DC | Called party's status indicator | +| | 0 1 | subscriber free if the exchange recognizes that the access line condition is free | +| | 0 0 | no indication otherwise | +| bits | FE | Called party's category indicator | +| | 0 0 | no indication if the user's characteristics (internal data) have not been analysed, or | +| | 0 1 | ordinary subscriber , or | +| | 1 0 | payphone according to the user's characteristics | +| bit | I | Interworking indicator | +| | 0 | no interworking encountered | +| bit | K | ISDN user part indicator | +| | 1 | ISDN user part used all the way | +| bit | M | ISDN access indicator | +| | 1 | terminating access non-ISDN | + +##### OPTIONAL PARAMETERS + +###### Optional backward call indicators + +| | | | +|-----|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bit | A | In-band information indicator | +| | 1 | in-band information or an appropriate pattern is now available if it has been determined, in case of call failure, that a special in-band tone or announcement has to be returned to the calling party from the destination exchange | +| | 0 | no indication otherwise | + +#### 3.2.1.4 Sending of the Call progress message (CPG) + +If the Address Complete Message (ACM) has already been sent, the following cases are possible trigger conditions of sending the Call Progress Message (CPG): + +- the destination exchange has determined that the subscriber is free; +- it has been determined that an in-band tone or announcement has to be returned to the calling party from the destination exchange. + +##### MANDATORY PARAMETERS + +###### Event information + +| | | | +|------|---------|----------------------------------------------------------------------------------| +| bits | G-A | Event indicator | +| | 0000001 | alerting | +| | 0000011 | in-band information or an appropriate pattern is now available in case b. | + +##### OPTIONAL PARAMETERS + +###### Other parameters + +The other parameters may have already been sent in a previous backward message. In this case they are not repeated unless new information are now available. + +The coding of these parameters is described in 3.2.1.3. + +#### 3.2.1.5 Sending of the Answer Message (ANM) + +If the exchange detects the off-hook condition on the non-ISDN side, it shall send an Answer Message (ANM). + +#### 3.2.1.6 Receipt of the Release message (REL) + +Upon receiving the Release message (REL) in the exchange, it may be mapped into an appropriate forward signal, e.g. Clear-forward signal, on the non-ISDN side. + +#### 3.2.1.7 Sending of the Suspend message (SUS) network initiated + +The action taken on the ISUP side upon receipt of the on-hook condition are described in 2.4.1/Q.764 [4]. + +#### 3.2.1.8 Sending of the Resume message (RES) network initiated + +The action taken on the ISUP side upon receipt of the off-hook condition are described in 2.4.1/Q.764 [4]. + +#### 3.2.1.9 Release by the exchange + +**Table 135/Q.699 – Release from the destination exchange** + +| Message sent to the ISUP | Trigger event | +|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| ← | | +| REL
Cause value No. 97 or No. 99 | Call release due to the ISUP compatibility procedure | +| REL
Cause value coded according to [4] | Other cases of failure on the ISUP side | +| REL
Cause value coded according to [4]
(Note) | Other cases of failure on the non-ISDN side
(Note) | +| NOTE – The destination exchange has determined line conditions, e.g. subscriber busy, during call set-up. | | + +### 3.2.2 Supplementary services + +For further study. + +# ANNEX A + +## **Interworking scenarios between subscriber access types interworking over SS 7 ISUP** + +## **A.1 General** + +### **A.1.1 Scope** + +This annex defines some typical interworking scenarios between certain subscriber access types interworking over the Signalling System No. 7 ISDN User Part (ISUP). + +### **A.1.2 Methodology** + +Call flow or "arrow" diagrams are provided to show the temporal relationships between signalling messages during execution of a call control procedure. The general format of an arrow diagram is shown in Figure A.1. + +The main part of the Recommendation takes precedence over this annex. + +### **A.1.3 Symbols and abbreviations** + +The vertical boxes represent three exchanges: originating, intermediate and destination. + +The vertical dashed lines represent the access interface. Each access interface supports a single access type: ISDN or non-ISDN. + +Solid horizontal arrows represent signalling messages and indicate their direction of propagation, i.e. to or from the incoming or outgoing exchange. The interaction of messages shown along the vertical represent increasing time in the downward direction. All events on the same vertical line are related, e.g. an incoming message causes voice-path connections and triggers an outgoing message. Events on different vertical lines are not related unless connected by dashed lines. A dashed line indicates that an incoming message may trigger an event at a later time. + +Wavy horizontal arrows ( $\sim\sim>$ ) represent tones or announcements sent in-band (Note). + +Timers are represented as vertical arrows. + +For call control the following symbols are used within the vertical boxes to indicate the relationship between the incoming and outgoing messages and the call control action taken. + +![Diagram of a call flow or 'arrow' diagram showing message flow between Access X, Originating exchange, Intermediate exchange, Destination exchange, and Access Y. It includes symbols for tone generation, through-connections, disconnections, and reservations, with a legend for messages A-E, actions f-h, and access types X-Y.](d3162014eae89d17bf0117dabb0c8796_img.jpg) + +The diagram illustrates a call flow across five entities: Access X, Originating exchange, Intermediate exchange, Destination exchange, and Access Y. + +- Access X and Y are represented by vertical dashed lines labeled X and Y respectively. + +- The three exchanges are represented by vertical rectangular boxes. + +- Arrows represent signalling messages: A (X to Originating), B (Originating to Intermediate), C (Intermediate to Destination), D (Destination to Y), and E (Originating to X). + +- Inside the Originating exchange, message A points to a symbol (circle with top-left quadrant shaded) which then points to call control action 'f'. Action 'f' has a dashed arrow pointing to message E. + +- Inside the Intermediate exchange, message B points to a symbol (circle with top-right quadrant shaded) which then points to call control action 'g'. + +- Inside the Destination exchange, message C points to a symbol (circle with bottom-left quadrant shaded) which then points to call control action 'h'. + +- A legend below the diagram defines the symbols: + +- Circle with top-left quadrant shaded: Tone generation + +- Circle with top-right quadrant shaded: Through-connection of the path in the backward direction + +- Circle with bottom-left quadrant shaded: Through-connection of the path in the forward direction + +- Circle with top and bottom quadrants shaded: Through-connection of the path in both directions + +- Circle with an 'X': Disconnection of path through the exchange + +- Empty circle: Reservation of an incoming/outgoing circuit channel without through-connection + +- A, B, C, D and E: Signalling messages + +- f, g and h: Call control action + +- X and Y: Access types + +- The text 'T1183770-97' is located near the bottom right of the diagram. + +Diagram of a call flow or 'arrow' diagram showing message flow between Access X, Originating exchange, Intermediate exchange, Destination exchange, and Access Y. It includes symbols for tone generation, through-connections, disconnections, and reservations, with a legend for messages A-E, actions f-h, and access types X-Y. + +Message A in access X causes call control action f in the originating exchange, ISUP message B, call control action g in the intermediate exchange, ISUP message C, call control action h in the destination exchange and message D in access Y. Message A may trigger message E in access X. + +NOTE – For simplicity, normal ring-back tones are not shown. + +**Figure A.1/Q.699 – Example of a call flow or "arrow" diagram** + +## A.2 Interworking of ISDN accesses over ISUP + +Subclauses A.2.1 through A.2.4 contain information relevant to ISDN basic call control functions as defined in Recommendations Q.930, Q.931, Q.763 and Q.764. The call flow diagrams are divided into functional subclauses: + +- successful call set-up procedures; +- unsuccessful call set-up procedures; +- release procedures; +- suspend/resume procedures; +- simple message segmentation procedures. + +### A.2.1 Successful call set-up procedures/call flow diagrams for basic call control + +#### A.2.1.1 *En bloc*, non-automatic answering terminal sending of address complete independent of access + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.2 shows the sequence of messages for successful call set-up where *en bloc* address signalling is used, the ACM is sent by the network independent of access indications, and the called party is not an automatic answering terminal. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for call set-up (Figure A.2/Q.699). The diagram shows message flows between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence is: 1. SETUP from ISDN access to Originating exchange. 2. CALL PROC from Originating exchange to ISDN access. 3. IAM from Originating exchange to Intermediate exchange. 4. ACM from Intermediate exchange to Originating exchange. 5. CPG from Intermediate exchange to Originating exchange. 6. ANM from Intermediate exchange to Originating exchange. 7. CONN from Originating exchange to ISDN access. 8. CONN ACK from ISDN access to Originating exchange (Note 2). 9. SETUP from Originating exchange to Destination exchange. 10. CALL PROC from Destination exchange to ISDN access (Note 1). 11. ACM from Destination exchange to Intermediate exchange (Note 3). 12. CPG from Destination exchange to Intermediate exchange. 13. ANM from Destination exchange to Intermediate exchange. 14. CONN from Destination exchange to ISDN access. 15. CONN ACK from ISDN access to Destination exchange. The diagram is labeled T1183780-97 at the bottom right.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) + +Sequence diagram for call set-up (Figure A.2/Q.699). The diagram shows message flows between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence is: 1. SETUP from ISDN access to Originating exchange. 2. CALL PROC from Originating exchange to ISDN access. 3. IAM from Originating exchange to Intermediate exchange. 4. ACM from Intermediate exchange to Originating exchange. 5. CPG from Intermediate exchange to Originating exchange. 6. ANM from Intermediate exchange to Originating exchange. 7. CONN from Originating exchange to ISDN access. 8. CONN ACK from ISDN access to Originating exchange (Note 2). 9. SETUP from Originating exchange to Destination exchange. 10. CALL PROC from Destination exchange to ISDN access (Note 1). 11. ACM from Destination exchange to Intermediate exchange (Note 3). 12. CPG from Destination exchange to Intermediate exchange. 13. ANM from Destination exchange to Intermediate exchange. 14. CONN from Destination exchange to ISDN access. 15. CONN ACK from ISDN access to Destination exchange. The diagram is labeled T1183780-97 at the bottom right. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see /Q.931 5.2.5.1). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 1.8/Q.931). + +NOTE 3 – The method of ACM generation independent of access is termed the *Early ACM*. The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISDN access indicator = ISDN access; ISUP used all the way = yes; interworking encountered = no. + +**Figure A.2/Q.699 – *En bloc*, non-automatic answering terminal, sending of ACM independent of access** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- CPG message – subclauses 2.1.1.4 and 3.1.1.4; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.1.2 *En bloc*, automatic answering terminal sending of address complete independent of access + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.3 shows the sequence of messages for successful call set-up where *en-bloc* address signalling is used, the ACM is sent independent of access indications, and the called party is an automatic answer terminal (fast-connect scenario). If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for ISDN call setup between two ISDN accesses through three exchanges (Originating, Intermediate, Destination). The diagram shows the flow of messages: SETUP, CALL PROC, CONN, CONN ACK, IAM, ACM, and ANM. The Originating and Destination exchanges have symbols (circles with crosses) indicating active components, while the Intermediate exchange has a single circle. The Destination exchange sends an ACM message (Note 3) back to the Intermediate exchange, which then forwards it to the Originating exchange. The Originating exchange then sends CONN and CONN ACK messages (Note 2) to the ISDN access. The Destination exchange also sends a CALL PROC message (Note 1) to the ISDN access.](d7996c295c6d5c251be4bce3dea03f2e_img.jpg) + +``` + +sequenceDiagram + participant ISDN_Access_1 as ISDN access + participant Originating_Exchange as Originating exchange + participant Intermediate_Exchange as Intermediate exchange + participant Destination_Exchange as Destination exchange + participant ISDN_Access_2 as ISDN access + + Note left of Originating_Exchange: (Note 2) + Note right of Destination_Exchange: (Note 1) + Note right of Intermediate_Exchange: (Note 3) + + ISDN_Access_1->>Originating_Exchange: SETUP + Originating_Exchange-->>ISDN_Access_1: CALL PROC + Originating_Exchange->>Intermediate_Exchange: IAM + Intermediate_Exchange->>Originating_Exchange: ACM + Intermediate_Exchange->>Destination_Exchange: IAM + Destination_Exchange-->>Intermediate_Exchange: ACM + Destination_Exchange->>ISDN_Access_2: SETUP + ISDN_Access_2-->>Destination_Exchange: CALL PROC + Destination_Exchange-->>ISDN_Access_2: CONN + ISDN_Access_2-->>Destination_Exchange: CONN ACK + Destination_Exchange->>Intermediate_Exchange: ANM + Intermediate_Exchange->>Originating_Exchange: ANM + Originating_Exchange->>ISDN_Access_1: CONN + ISDN_Access_1-->>Originating_Exchange: CONN ACK + +``` + +Sequence diagram for ISDN call setup between two ISDN accesses through three exchanges (Originating, Intermediate, Destination). The diagram shows the flow of messages: SETUP, CALL PROC, CONN, CONN ACK, IAM, ACM, and ANM. The Originating and Destination exchanges have symbols (circles with crosses) indicating active components, while the Intermediate exchange has a single circle. The Destination exchange sends an ACM message (Note 3) back to the Intermediate exchange, which then forwards it to the Originating exchange. The Originating exchange then sends CONN and CONN ACK messages (Note 2) to the ISDN access. The Destination exchange also sends a CALL PROC message (Note 1) to the ISDN access. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 3 – The ACM is independently generated at the destination exchange with the following parameters: called party status no indication; ISDN access indicator = ISDN access; ISUP used all the way = yes; interworking encountered = no. + +**Figure A.3/Q.699 – En bloc, automatic answering terminal, sending of ACM independent of access** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.1.3 *En bloc*, non-automatic answering terminal + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.4 shows the sequence of messages for successful call set-up where *en bloc* address signalling is used, the ACM is delayed until receipt of alerting information from the access (Note), and the called party is not an automatic answering terminal. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +NOTE – Termed *Late ACM*. + +![Sequence diagram of ISDN call set-up for a non-automatic answering terminal.](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +The diagram illustrates the message sequence for a successful call set-up between two ISDN accesses through three exchanges: Originating, Intermediate, and Destination. The sequence is as follows: + +- ISDN access to Originating exchange:** SETUP +- Originating exchange to ISDN access:** CALL PROC (dashed line), ALERT, CONN +- Originating exchange to Intermediate exchange:** IAM +- Intermediate exchange to Originating exchange:** ACM, ANM +- Intermediate exchange to Destination exchange:** IAM +- Destination exchange to Intermediate exchange:** ACM, ANM +- Destination exchange to ISDN access:** SETUP +- ISDN access to Destination exchange:** CALL PROC (Note 1), ALERT, CONN, CONN ACK (Note 2) + +Icons for the exchanges are: Originating (top circle with X), Intermediate (circle with X), Destination (top circle empty, bottom circle with X). The diagram is labeled T1183800-97. + +Sequence diagram of ISDN call set-up for a non-automatic answering terminal. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +**Figure A.4/Q.699 – *En bloc*, non-automatic answering terminal** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.1.1.3; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.1.4 *En bloc*, automatic answering terminal + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.5 shows successful call set-up with *en bloc* address signalling, and the address complete indication delayed until receipt of connect indication from an automatic answering terminal. In this case the address complete indication and connect indication are combined in the CONNECT message in the network. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram of ISDN call set-up with en bloc signalling.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +The diagram illustrates the message exchange for an *en bloc*, automatic answering terminal call set-up across five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence of messages is as follows: + +- The first ISDN access sends a **SETUP** message to the Originating exchange. +- The Originating exchange responds with **CALL PROC** (Note 2) back to the first ISDN access. +- The Originating exchange sends an **IAM** (Initial Address Message) to the Intermediate exchange. +- The Intermediate exchange forwards the **IAM** to the Destination exchange. +- The Destination exchange sends a **SETUP** message to the second ISDN access. +- The second ISDN access responds with **CALL PROC** (Note 1) back to the Destination exchange. +- The Destination exchange sends a **CONN** (Connect) message back to the Intermediate exchange. +- The Intermediate exchange forwards the **CONN** message back to the Originating exchange. +- The Originating exchange sends a **CONN** message back to the first ISDN access. +- The first ISDN access responds with **CONN ACK** (Note 2) back to the Originating exchange. + +Icons representing the entities are: a circle with an 'X' for ISDN access, a circle with a diagonal line for the Originating exchange, a circle with an 'X' for the Intermediate exchange, a circle with a diagonal line for the Destination exchange, and a circle with an 'X' for the second ISDN access. + +Sequence diagram of ISDN call set-up with en bloc signalling. + +T1183810-97 + +NOTE 1 – This message may be sent by the symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +**Figure A.5/Q.699 – *En bloc*, automatic answering terminal** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- CON message – subclauses 2.1.1.6 and 3.1.1.6. + +#### A.2.1.5 Overlap addressing, originating access only, non-automatic answering terminal + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.6 shows the sequence of messages when overlap addressing is used between the calling party and the originating exchange, and *en bloc* addressing is used within the network with closed numbering plan. An independent ACM and non-automatic answering terminal is assumed in this case. Variations are possible as in Figures 3 to 6. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for Overlap addressing, originating access only, non-automatic answering terminal. The diagram shows message exchanges between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence includes SETUP, SETUP ACK, INFO, CALL PROC, ACM, CPG, ALERT, CONN, CONN ACK, IAM, and ANM messages. The Originating and Destination exchanges have symbols indicating non-automatic answering terminals. The Intermediate exchange has a symbol indicating a continuity check.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +``` + +sequenceDiagram + participant ISDN_Access as ISDN access + participant Originating_Exchange as Originating exchange + participant Intermediate_Exchange as Intermediate exchange + participant Destination_Exchange as Destination exchange + participant ISDN_Access_2 as ISDN access + + Note left of Originating_Exchange: (Note 4) + ISDN_Access->>Originating_Exchange: SETUP + Originating_Exchange-->>ISDN_Access: SETUP ACK + ISDN_Access->>Originating_Exchange: INFO + Originating_Exchange-->>ISDN_Access: CALL PROC + Originating_Exchange->>Intermediate_Exchange: IAM + Intermediate_Exchange->>Originating_Exchange: ACM + Note right of Originating_Exchange: (Note 3) + Intermediate_Exchange->>Destination_Exchange: IAM + Destination_Exchange-->>Intermediate_Exchange: ACM + Destination_Exchange->>ISDN_Access_2: SETUP + ISDN_Access_2-->>Destination_Exchange: CALL PROC + Note right of Destination_Exchange: (Note 1) + Destination_Exchange->>ISDN_Access_2: ALERT + ISDN_Access_2-->>Destination_Exchange: CONN + Destination_Exchange-->>ISDN_Access_2: CONN ACK + Note right of ISDN_Access_2: (Note 2) + Destination_Exchange->>Intermediate_Exchange: ANM + Intermediate_Exchange-->>Originating_Exchange: ANM + Originating_Exchange->>ISDN_Access: CONN + ISDN_Access-->>Originating_Exchange: CONN ACK + Originating_Exchange->>ISDN_Access: ACK + +``` + +Sequence diagram for Overlap addressing, originating access only, non-automatic answering terminal. The diagram shows message exchanges between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence includes SETUP, SETUP ACK, INFO, CALL PROC, ACM, CPG, ALERT, CONN, CONN ACK, IAM, and ANM messages. The Originating and Destination exchanges have symbols indicating non-automatic answering terminals. The Intermediate exchange has a symbol indicating a continuity check. + +T1183820-97 + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 3 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISDN access indicator = ISDN access; ISUP used all the way = yes; interworking encountered = no. + +NOTE 4 – The number of INFORMATION messages shown is for example only. In practice the number may be zero or more: if zero, the IAM and CALL PROCEEDING messages may be originated on expiry of timer T302 (see 5.1.5.2/Q.931). + +**Figure A.6/Q.699 – Overlap addressing, originating access only, non-automatic answering terminal** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- CPG message – subclauses 2.1.1.4 and 3.1.1.4; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.1.6 Overlap addressing, originating access and network, non-automatic answering terminal + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.7 shows the sequence of messages when overlap addressing is used at the originating access and within the network. In this case the ACM through the network informs the originating exchange that enough address information has been received, and the exchange can therefore indicate call proceeding to the calling party. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for Figure A.7/Q.699 showing message flow between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The diagram shows the sequence of messages for overlap addressing, originating access and network, non-automatic answering terminal. The sequence starts with SETUP from ISDN access to Originating exchange, followed by SETUP ACK. Then INFO messages are sent from ISDN access to Originating exchange. The Originating exchange sends IAM to Intermediate exchange, which then sends IAM to Destination exchange. The Destination exchange sends SETUP to ISDN access. The Originating exchange sends SAM to Intermediate exchange, which sends SAM to Destination exchange. The Destination exchange sends CALL PROC (Note 1) to ISDN access. The Originating exchange sends ACM to Intermediate exchange, which sends ACM to Destination exchange. The Destination exchange sends ALERT to ISDN access. The Originating exchange sends CPG to Intermediate exchange, which sends CPG to Destination exchange. The Destination exchange sends CONN to ISDN access. The Originating exchange sends ANM to Intermediate exchange, which sends ANM to Destination exchange. The Destination exchange sends CONN ACK to ISDN access. The Originating exchange sends CONN to ISDN access, which receives CONN ACK (Note 2).](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +T1183830-97 + +Sequence diagram for Figure A.7/Q.699 showing message flow between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The diagram shows the sequence of messages for overlap addressing, originating access and network, non-automatic answering terminal. The sequence starts with SETUP from ISDN access to Originating exchange, followed by SETUP ACK. Then INFO messages are sent from ISDN access to Originating exchange. The Originating exchange sends IAM to Intermediate exchange, which then sends IAM to Destination exchange. The Destination exchange sends SETUP to ISDN access. The Originating exchange sends SAM to Intermediate exchange, which sends SAM to Destination exchange. The Destination exchange sends CALL PROC (Note 1) to ISDN access. The Originating exchange sends ACM to Intermediate exchange, which sends ACM to Destination exchange. The Destination exchange sends ALERT to ISDN access. The Originating exchange sends CPG to Intermediate exchange, which sends CPG to Destination exchange. The Destination exchange sends CONN to ISDN access. The Originating exchange sends ANM to Intermediate exchange, which sends ANM to Destination exchange. The Destination exchange sends CONN ACK to ISDN access. The Originating exchange sends CONN to ISDN access, which receives CONN ACK (Note 2). + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 3 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISDN access indicator = ISDN access; ISUP used all the way = yes; interworking encountered = no. + +NOTE 4 – The number of INFORMATION messages shown is for example only. In practice the number may be zero or more: if zero, the IAM and CALL PROCEEDING messages may be originated on expiry of timer T302 (see 5.1.5.2/Q.931). + +**Figure A.7/Q.699 – Overlap addressing, originating access and in network, non-automatic answering terminal** + +For detailed message and parameter mappings, refer to: + +- CPG message – subclauses 2.1.1.4 and 3.1.1.4; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.1.7 Overlap addressing, both accesses and network address complete cannot be determined by number analysis + +See 2.1/Q.764 and 5.1/Q.931. + +In Figure A.8 overlap addressing is used at both accesses and in the network. An example is a call made to an ISDN PABX, where determination of address complete may only be made as a result of an indication, e.g. alerting, from the called access. In this case, the ALERTING message from the called access allows the sending of an ACM in the network, which, since it carries the "subscriber free" indication, is mapped to ALERTING at the calling access. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for Figure A.8/Q.699 showing overlap addressing. The diagram illustrates the message flow between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. The sequence includes SETUP, INFO, ALERT, CONN, CONN ACK, IAM, SAM, ACM, and ANM messages. The Originating and Destination exchanges are marked with a crossed circle symbol. The Intermediate exchange is marked with a circle symbol. The sequence of messages is: 1. ISDN access sends SETUP to Originating exchange. 2. Originating exchange sends SETUP ACK to ISDN access. 3. ISDN access sends INFO (Note 2) to Originating exchange. 4. Originating exchange sends INFO to Intermediate exchange. 5. Intermediate exchange sends INFO to Destination exchange. 6. Destination exchange sends SETUP to ISDN access. 7. ISDN access sends SETUP ACK to Destination exchange. 8. Destination exchange sends INFO to ISDN access. 9. ISDN access sends ALERT to Destination exchange. 10. Destination exchange sends CONN to ISDN access. 11. ISDN access sends CONN ACK to Destination exchange. 12. Destination exchange sends CONN to Intermediate exchange. 13. Intermediate exchange sends CONN to Originating exchange. 14. Originating exchange sends CONN ACK to ISDN access (Note 1). 15. Originating exchange sends IAM to Intermediate exchange. 16. Intermediate exchange sends IAM to Destination exchange. 17. Destination exchange sends SAM to Intermediate exchange. 18. Intermediate exchange sends SAM to Originating exchange. 19. Originating exchange sends ACM to Intermediate exchange. 20. Intermediate exchange sends ACM to Destination exchange. 21. Destination exchange sends ANM to Intermediate exchange. 22. Intermediate exchange sends ANM to Originating exchange.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +Sequence diagram for Figure A.8/Q.699 showing overlap addressing. The diagram illustrates the message flow between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. The sequence includes SETUP, INFO, ALERT, CONN, CONN ACK, IAM, SAM, ACM, and ANM messages. The Originating and Destination exchanges are marked with a crossed circle symbol. The Intermediate exchange is marked with a circle symbol. The sequence of messages is: 1. ISDN access sends SETUP to Originating exchange. 2. Originating exchange sends SETUP ACK to ISDN access. 3. ISDN access sends INFO (Note 2) to Originating exchange. 4. Originating exchange sends INFO to Intermediate exchange. 5. Intermediate exchange sends INFO to Destination exchange. 6. Destination exchange sends SETUP to ISDN access. 7. ISDN access sends SETUP ACK to Destination exchange. 8. Destination exchange sends INFO to ISDN access. 9. ISDN access sends ALERT to Destination exchange. 10. Destination exchange sends CONN to ISDN access. 11. ISDN access sends CONN ACK to Destination exchange. 12. Destination exchange sends CONN to Intermediate exchange. 13. Intermediate exchange sends CONN to Originating exchange. 14. Originating exchange sends CONN ACK to ISDN access (Note 1). 15. Originating exchange sends IAM to Intermediate exchange. 16. Intermediate exchange sends IAM to Destination exchange. 17. Destination exchange sends SAM to Intermediate exchange. 18. Intermediate exchange sends SAM to Originating exchange. 19. Originating exchange sends ACM to Intermediate exchange. 20. Intermediate exchange sends ACM to Destination exchange. 21. Destination exchange sends ANM to Intermediate exchange. 22. Intermediate exchange sends ANM to Originating exchange. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 2 – The number of INFORMATION messages shown is for example only. In practice the number may be zero or more: if zero, the IAM and CALL PROCEEDING messages may be originated on expiry of timer T302 (see 5.1.5.2/Q.931). + +**Figure A.8/Q.699 – Overlap addressing, both accesses and within network, address complete cannot be determined by number analysis** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.1.1.3; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.1.8 Overlap addressing, both accesses and within network transfer of address complete indication via call proceeding + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.9 shows the case where the indication that complete address information has been received is transferred by the terminating access. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for Figure A.9/Q.699 showing message exchanges between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The diagram illustrates the flow of messages like SETUP, INFO, CALL PROC, ALERT, CONN, and ACK through the network elements.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +The diagram illustrates the message sequence for overlap addressing. It involves five entities: ISDN access (left), Originating exchange, Intermediate exchange, Destination exchange, and ISDN access (right). The sequence of messages is as follows: + +- The left ISDN access sends a **SETUP** message to the Originating exchange. +- The Originating exchange responds with a **SETUP ACK**. +- The left ISDN access sends an **INFO (Note 2)** message to the Originating exchange. +- The Originating exchange forwards an **IAM** message to the Intermediate exchange. +- The Intermediate exchange forwards an **IAM** message to the Destination exchange. +- The Destination exchange sends a **SETUP** message to the right ISDN access. +- The right ISDN access responds with a **SETUP ACK**. +- The right ISDN access sends an **INFO** message to the Destination exchange. +- The Destination exchange sends a **CALL PROC** message to the right ISDN access. +- The right ISDN access sends an **ALERT** message to the Destination exchange. +- The right ISDN access sends a **CONN** message to the Destination exchange. +- The right ISDN access sends a **CONN ACK (Note 1)** message to the Destination exchange. +- The Destination exchange sends an **ANM** message to the Intermediate exchange. +- The Intermediate exchange sends an **ANM** message to the Originating exchange. +- The Originating exchange sends a **CPG** message to the left ISDN access. +- The Originating exchange sends an **ACM** message to the left ISDN access. +- The Originating exchange sends a **CALL PROC** message to the left ISDN access. +- The Originating exchange sends an **ALERT** message to the left ISDN access. +- The Originating exchange sends a **CONN** message to the left ISDN access. +- The left ISDN access sends a **CONN ACK (Note 1)** message to the Originating exchange. +- Additional **INFO** messages are shown being sent from the Originating exchange to the Intermediate exchange and from the Intermediate exchange to the Destination exchange. + +T1183850-97 + +Sequence diagram for Figure A.9/Q.699 showing message exchanges between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The diagram illustrates the flow of messages like SETUP, INFO, CALL PROC, ALERT, CONN, and ACK through the network elements. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 2 – The number of INFORMATION messages shown is for example only. In practice the number may be zero or more: if zero, the IAM and CALL PROCEEDING messages may be originated on expiry of timer T302 (see 5.1.5.2/Q.931). + +**Figure A.9/Q.699 – Overlap addressing, both access and within network, transfer of address complete indication via call proceeding (option a: call proceeding mapped to address complete)** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.1.1.3; +- CPG message – subclauses 2.1.1.4 and 3.1.1.4; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +### A.2.2 Unsuccessful call set-up procedures/call flow diagrams for basic call control + +#### A.2.2.1 Point-to-point data link sending of address complete independent of access + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.10 shows the unsuccessful call set-up procedure where in-band tones/announcements are not provided (e.g. 64 kbit/s unrestricted bearer service). The RELEASE COMPLETE message at the destination exchange is mapped into the REL. At the originating exchange the REL is mapped into the DISCONNECT message. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram of an unsuccessful call set-up procedure across ISDN access, originating, intermediate, and destination exchanges.](c5424b117a719524c619938e97c4cb1f_img.jpg) + +The diagram illustrates the message flow for an unsuccessful call set-up. It involves four main entities: ISDN access (left), Originating exchange, Intermediate exchange, and Destination exchange (right), followed by another ISDN access (far right). The sequence of messages is as follows: 1. SETUP is sent from the left ISDN access to the Originating exchange. 2. CALL PROC is returned from the Originating exchange to the left ISDN access. 3. IAM is sent from the Originating exchange to the Intermediate exchange. 4. ACM is returned from the Intermediate exchange to the Originating exchange. 5. DISC is sent from the Originating exchange to the left ISDN access. 6. REL is sent from the Originating exchange to the Intermediate exchange. 7. RLC is sent from the Originating exchange to the Intermediate exchange. 8. REL is sent from the Intermediate exchange to the Destination exchange. 9. RLC is sent from the Intermediate exchange to the Destination exchange. 10. REL COMP is sent from the Destination exchange to the Intermediate exchange. 11. REL COMP is sent from the Intermediate exchange to the Originating exchange. 12. DISC is sent from the Originating exchange to the left ISDN access. 13. REL is sent from the Originating exchange to the left ISDN access. 14. REL COMP is sent from the Originating exchange to the left ISDN access. 15. SETUP (Note 2) is sent from the Destination exchange to the far right ISDN access. A note (Note 3) is associated with the ACM message between the Intermediate and Destination exchanges. The diagram is labeled T1183860-97 at the bottom right. + +Sequence diagram of an unsuccessful call set-up procedure across ISDN access, originating, intermediate, and destination exchanges. + +NOTE 1 – This procedure is applicable in those cases where in-band tone/announcements are not provided, e.g. 64 kbit/s unrestricted bearer service. + +NOTE 2 – This message is delivered by a point-to-point data link. + +NOTE 3 – If *Early* ACM is used, the ACM is independently generated with the following parameters: called party status = no indication; ISDN access indicator = ISDN access; ISUP used all the way = yes; interworking encountered = no. + +**Figure A.10/Q.699 – Unsuccessful call set-up, point-to-point data link, ACM generated independent of access (Note 1)** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- REL message – subclauses 2.1.1.7 and 3.1.1.8. + +#### A.2.2.2 Point-to-point data link + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.11 shows the unsuccessful call set-up procedure, where in-band tones/announcements are not provided (e.g. 64 kbit/s unrestricted bearer service). The RELEASE COMPLETE message at the destination exchange is mapped into the REL. At the originating exchange the REL is mapped into the DISCONNECT message. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram of an unsuccessful call set-up over a point-to-point data link. The diagram shows five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence of messages is: 1. SETUP from ISDN access to Originating exchange. 2. CALL PROC from Originating exchange to ISDN access. 3. IAM from Originating exchange to Intermediate exchange. 4. IAM from Intermediate exchange to Destination exchange. 5. SETUP (Note 2) from Destination exchange to ISDN access. 6. REL COMP from ISDN access to Destination exchange. 7. REL from Destination exchange to Intermediate exchange. 8. REL from Intermediate exchange to Originating exchange. 9. DISC from Originating exchange to ISDN access. 10. REL from ISDN access to Originating exchange. 11. REL COMP from Originating exchange to ISDN access. The Originating and Intermediate exchanges are shown with two internal symbols: a circle with a cross (top) and a circle with an X (bottom). The Destination exchange is shown with a plain circle symbol. The diagram is labeled T1183870-97 at the bottom right.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +Sequence diagram of an unsuccessful call set-up over a point-to-point data link. The diagram shows five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence of messages is: 1. SETUP from ISDN access to Originating exchange. 2. CALL PROC from Originating exchange to ISDN access. 3. IAM from Originating exchange to Intermediate exchange. 4. IAM from Intermediate exchange to Destination exchange. 5. SETUP (Note 2) from Destination exchange to ISDN access. 6. REL COMP from ISDN access to Destination exchange. 7. REL from Destination exchange to Intermediate exchange. 8. REL from Intermediate exchange to Originating exchange. 9. DISC from Originating exchange to ISDN access. 10. REL from ISDN access to Originating exchange. 11. REL COMP from Originating exchange to ISDN access. The Originating and Intermediate exchanges are shown with two internal symbols: a circle with a cross (top) and a circle with an X (bottom). The Destination exchange is shown with a plain circle symbol. The diagram is labeled T1183870-97 at the bottom right. + +NOTE 1 – This procedure is applicable in those cases where in-band tone/announcements are not provided, e.g. 64 kbit/s unrestricted bearer service. + +NOTE 2 – This message is delivered by a point-to-point data link. + +**Figure A.11/Q.699 – Unsuccessful call set-up, point-to-point data link (Note 1)** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- REL message – subclauses 2.1.1.7 and 3.1.1.8. + +#### A.2.2.3 Broadcast data link + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.12 shows the unsuccessful call set-up procedure, where in-band tones/announcements are not provided (e.g. 64 kbit/s unrestricted bearer service), in the case where the called party is addressed via a broadcast data link. The returning of the RELEASE COMPLETE message via a broadcast data link is optional. In the case shown, on receipt of the RELEASE COMPLETE message at the destination exchange the cause value is retained, and to allow for the possibility of another terminal accepting the call, the REL is not generated until the expiry of timer T303. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +NOTE – Where the network does not receive any response to the initial SETUP message before the expiry of timer T303, the SETUP message is retransmitted and T303 is restarted. If no further response is received by the network on the second expiry of timer T303, the REL message is generated. At the originating exchange the REL is mapped into the DISCONNECT message. + +![Sequence diagram of an unsuccessful call set-up via a broadcast data link. The diagram shows five vertical lifelines: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence starts with a SETUP message from the first ISDN access to the Originating exchange. The Originating exchange sends an IAM message to the Intermediate exchange, which then sends an IAM message (Note 4) to the Destination exchange. The Destination exchange sends a SETUP message (Note 2) to the second ISDN access. The second ISDN access returns a REL COMP message to the Destination exchange. Upon receiving REL COMP, the Destination exchange starts Timer 303. When Timer 303 expires, the Destination exchange sends a REL message (Note 3) back to the Intermediate exchange, which in turn sends a RLC message to the Originating exchange. The Originating exchange then generates a DISC message and a REL message for the first ISDN access, and finally receives a REL COMP message from the first ISDN access. The diagram is labeled T1183880-97 at the bottom right.](028422d3e6ce272069a2b4f317c88474_img.jpg) + +Sequence diagram of an unsuccessful call set-up via a broadcast data link. The diagram shows five vertical lifelines: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence starts with a SETUP message from the first ISDN access to the Originating exchange. The Originating exchange sends an IAM message to the Intermediate exchange, which then sends an IAM message (Note 4) to the Destination exchange. The Destination exchange sends a SETUP message (Note 2) to the second ISDN access. The second ISDN access returns a REL COMP message to the Destination exchange. Upon receiving REL COMP, the Destination exchange starts Timer 303. When Timer 303 expires, the Destination exchange sends a REL message (Note 3) back to the Intermediate exchange, which in turn sends a RLC message to the Originating exchange. The Originating exchange then generates a DISC message and a REL message for the first ISDN access, and finally receives a REL COMP message from the first ISDN access. The diagram is labeled T1183880-97 at the bottom right. + +NOTE 1 – This procedure is applicable in those cases where in-band tone/announcements are not provided, e.g. 64 kbit/s unrestricted bearer service. + +NOTE 2 – This message is delivered by a broadcast data link. + +NOTE 3 – The REL is not mapped from a message from the destination user. It is generated due to a time-out at the destination exchange. However, the REL does cause a message mapping at the originating exchange. + +NOTE 4 – If *Early ACM* is used, an ACM should be sent after the IAM by the destination exchange as shown in Figure A.10 + +**Figure A.12/Q.699 – Unsuccessful call set-up, broadcast data link (Note 1)** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- REL message – subclauses 2.1.1.7 and 3.1.1.13. + +#### A.2.2.4 Tone/announcement applied at the originating exchange + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.13 shows the unsuccessful set-up procedure where tones or announcements are generated in the originating exchange towards the ISDN access as a result of receiving a REL message. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +Timer T306 is started after the appropriate toner announcement is sent. Figure A.13 shows the originating ISDN access releasing before timer T306 expires. + +![Sequence diagram of an unsuccessful call set-up procedure. The diagram shows five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence of messages is: 1. SETUP from the first ISDN access to the Originating exchange. 2. CALL PROC from the Originating exchange to the first ISDN access. 3. DISC (PI = 8) from the Originating exchange to the first ISDN access. 4. REL from the Destination exchange to the Intermediate exchange. 5. RLC from the Intermediate exchange to the Originating exchange. 6. REL from the Originating exchange to the first ISDN access. 7. REL COMP from the first ISDN access to the Originating exchange. Notes: (Note 1) is near the DISC message, (Note 2) is near the REL message, and (Note 3) is near the IAM message from the Intermediate exchange to the Destination exchange. The diagram is labeled T1183890-97 at the bottom right.](9874e3ac6f14360133f8e1674f79824f_img.jpg) + +Sequence diagram of an unsuccessful call set-up procedure. The diagram shows five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence of messages is: 1. SETUP from the first ISDN access to the Originating exchange. 2. CALL PROC from the Originating exchange to the first ISDN access. 3. DISC (PI = 8) from the Originating exchange to the first ISDN access. 4. REL from the Destination exchange to the Intermediate exchange. 5. RLC from the Intermediate exchange to the Originating exchange. 6. REL from the Originating exchange to the first ISDN access. 7. REL COMP from the first ISDN access to the Originating exchange. Notes: (Note 1) is near the DISC message, (Note 2) is near the REL message, and (Note 3) is near the IAM message from the Intermediate exchange to the Destination exchange. The diagram is labeled T1183890-97 at the bottom right. + +NOTE 1 – If tones/announcements are applied, a DISCONNECT message may be sent containing progress indicator No. 8. As an alternative, a PROGRESS message may also be sent containing progress indicator No. 8. + +NOTE 2 – Timer T306 is started after tone is sent in the Q.931 protocol block. + +NOTE 3 – If *Early ACM* is used, an ACM should be sent after the IAM by the destination exchange as shown in Figure A.10. + +**Figure A.13/Q.699 – Unsuccessful call set-up tone/announcement applied at originating exchange** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- REL message – subclauses 2.1.1.7 and 3.1.1.8. + +#### A.2.2.5 Tone applied by destination exchange + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.14 shows an unsuccessful call where certain tones and announcements can only be generated in the destination exchange (or intermediate exchange) during call establishment. This is a typical case for example for a changed number announcement where the changed number information is only available at the destination exchange. Alternatively a specific announcement may be applied at an intermediate exchange to indicate for example that all circuits to a particular destination are busy. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +The originating exchange sends a DISCONNECT message to the calling user with progress indicator No. 8 thus indicating that in-band information is available. Normal release procedures apply after the in-band information has been connected. + +![Sequence diagram showing signaling flow for an unsuccessful call set-up with tone/announcement applied by the destination exchange.](f5698523df298c80a0c6b5d4ca657993_img.jpg) + +The diagram shows four vertical columns representing: ISDN access (left), Originating exchange, Intermediate exchange, Destination exchange, and ISDN access (right). +1. SETUP is sent from left ISDN access to Originating exchange. +2. CALL PROC is sent back to ISDN access. +3. IAM is sent from Originating to Intermediate exchange. +4. IAM is sent from Intermediate to Destination exchange. +5. ACM (Note 1) is sent from Destination to Intermediate exchange. +6. ACM is sent from Intermediate to Originating exchange. +7. PROG/DISC (PI = 8) (Note 2) is sent from Originating exchange to left ISDN access. A timer (Note 3) is indicated at the Originating exchange. +8. A wavy line labeled 'Tone/Annct' originates at the Destination exchange (labeled 'e.g. number changed (Note 4)') and passes through the Intermediate exchange to the Originating exchange. +9. REL is sent from Originating to Intermediate exchange. +10. REL is sent from Intermediate to Destination exchange. +11. RLC is sent from Destination to Intermediate exchange. +12. RLC is sent from Intermediate to Originating exchange. +13. REL is sent from Originating exchange to left ISDN access. +14. REL COMP is sent from left ISDN access to Originating exchange. +Reference code: T1183900-97. + +Sequence diagram showing signaling flow for an unsuccessful call set-up with tone/announcement applied by the destination exchange. + +NOTE 1 – The ACM is not mapped from a message from the destination user. It is generated at the destination exchange. + +NOTE 2 – If tones/announcements are applied, the DISCONNECT message containing progress indicator No. 8 may be mapped from the ACM message with an appropriate cause indicators parameter. As an alternative, a PROGRESS message may also be sent containing progress indicator No. 8 when the cause indicators parameter is not contained in an ACM message. + +NOTE 3 – Timer T306 is started in the Q.931 protocol block. + +NOTE 4 – Customized announcements can only be provided by the destination exchange. + +**Figure A.14/Q.699 – Unsuccessful call set-up tone/announcement applied by destination exchange** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.1.1.3; +- REL message – subclauses 2.1.1.8 and 3.1.1.7. + +#### A.2.2.6 Originating exchange tone/announcement time-out expires + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.15 shows the case of tone time-out expiry at the originating exchange. This is very similar to *tone/announcement applied at the originating exchange* above except that the caller fails to clear the call following the application of the tone. Timer T306 then expires. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for an unsuccessful call setup where the originating exchange tone/announcement time-out expires. The diagram shows five vertical lifelines: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence starts with a SETUP message from the first ISDN access to the Originating exchange. The Originating exchange responds with CALL PROC, DISC (with PI=8), and Tone/Anncnt. The caller then sends a REL message to the Originating exchange, which in turn sends REL to the Intermediate exchange and RLC to the Destination exchange. The Originating exchange then sends REL COMP back to the caller. The Intermediate exchange sends IAM (with Note 3) to the Destination exchange, which then sends SETUP to the second ISDN access. The Destination exchange sends REL COMP back to the Intermediate exchange, which sends REL to the Originating exchange. The diagram is labeled T1183910-97 at the bottom right.](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +``` +sequenceDiagram + participant ISDN_Access_1 as ISDN access + participant Originating_Exchange as Originating exchange + participant Intermediate_Exchange as Intermediate exchange + participant Destination_Exchange as Destination exchange + participant ISDN_Access_2 as ISDN access + + Note left of Originating_Exchange: Note 1: DISC (PI=8), Tone/Anncnt + Note right of Originating_Exchange: Note 2: Timer T306 expires + Note right of Destination_Exchange: Note 3: IAM + + ISDN_Access_1->>Originating_Exchange: SETUP + Originating_Exchange-->>ISDN_Access_1: CALL PROC + Originating_Exchange-->>ISDN_Access_1: DISC (PI=8) + Originating_Exchange-->>ISDN_Access_1: Tone/Anncnt + ISDN_Access_1->>Originating_Exchange: REL + Originating_Exchange-->>Intermediate_Exchange: REL + Originating_Exchange-->>Destination_Exchange: RLC + Originating_Exchange-->>ISDN_Access_1: REL COMP + Intermediate_Exchange->>Destination_Exchange: IAM + Destination_Exchange-->>ISDN_Access_2: SETUP + Destination_Exchange-->>Intermediate_Exchange: REL COMP + Intermediate_Exchange-->>Originating_Exchange: REL +``` + +Sequence diagram for an unsuccessful call setup where the originating exchange tone/announcement time-out expires. The diagram shows five vertical lifelines: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence starts with a SETUP message from the first ISDN access to the Originating exchange. The Originating exchange responds with CALL PROC, DISC (with PI=8), and Tone/Anncnt. The caller then sends a REL message to the Originating exchange, which in turn sends REL to the Intermediate exchange and RLC to the Destination exchange. The Originating exchange then sends REL COMP back to the caller. The Intermediate exchange sends IAM (with Note 3) to the Destination exchange, which then sends SETUP to the second ISDN access. The Destination exchange sends REL COMP back to the Intermediate exchange, which sends REL to the Originating exchange. The diagram is labeled T1183910-97 at the bottom right. + +NOTE 1 – If tone/announcements are applied, a DISCONNECT message may be sent containing progress indicator No. 8. As an alternative, a PROGRESS message may also be sent containing progress indicator No. 8. + +NOTE 2 – Timer T306 is started in the Q.931 protocol block. + +NOTE 3 – If *Early ACM* is used, an ACM should be sent after the IAM by the destination exchange as shown in Figure A.10. + +**Figure A.15/Q.699 – Unsuccessful call set-up originating exchange tone/announcement time-out expires** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- REL message – subclauses 2.1.1.7 and 3.1.1.8. + +#### A.2.2.7 Premature release – Point-to-point data link + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.16 shows a premature release situation where release is received at the destination exchange prior to any terminal response. In this situation a DISCONNECT message is sent to the called user and the normal clearing procedure is initiated. + +![Sequence diagram of premature release in a point-to-point data link.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +The diagram illustrates a sequence of messages between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. The sequence is as follows: + +- SETUP**: From the first ISDN access to the Originating exchange. +- CALL PROC**: From the Originating exchange back to the first ISDN access. +- DISC**: From the Originating exchange to the Intermediate exchange. +- REL**: From the Intermediate exchange to the Originating exchange. +- REL COMP**: From the Originating exchange to the first ISDN access. +- IAM**: From the Originating exchange to the Intermediate exchange. +- IAM**: From the Intermediate exchange to the Destination exchange. +- SETUP (Note 2)**: From the Destination exchange to the second ISDN access. +- DISC (Note 1)**: From the Destination exchange to the second ISDN access. +- REL**: From the second ISDN access to the Destination exchange. +- REL COMP**: From the Destination exchange to the second ISDN access. +- RLC**: From the Destination exchange to the Intermediate exchange. +- RLC**: From the Intermediate exchange to the Originating exchange. + +Exchange symbols: Originating and Intermediate exchanges have a circle with an 'X'; Destination exchange has an empty circle. The diagram is labeled T1183920-97. + +Sequence diagram of premature release in a point-to-point data link. + +NOTE 1 – In the case of point-to-multipoint, the DISCONNECT message is not sent. Terminals are released as they respond. + +NOTE 2 – Where the destination exchange normally sends *Early ACM*. If the premature REL is received before the ACM is sent, there may be no SETUP message sent. + +**Figure A.16/Q.699 – Premature release point-to-point data link** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- REL message – subclauses 2.1.1.8 and 3.1.1.7. + +### A.2.3 Release procedures/call flow diagrams for basic call control + +#### A.2.3.1 Normal call release procedure without tone provision + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.17 shows the normal call release interworking procedure without tone provision. A DISCONNECT message from the originating user is mapped into a REL in the network. At the destination end, a REL message from the network is mapped into a DISCONNECT message sent to the terminating user. + +The tone/announcement option is not applied in the destination exchange. + +![Sequence diagram of the normal call release procedure without tone provision.](3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg) + +The diagram illustrates the call release sequence across five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The Originating, Intermediate, and Destination exchanges are each represented by a box containing a circle with an 'X'. The sequence of messages is as follows: + +- The first ISDN access sends a DISC message to the Originating exchange. +- The Originating exchange maps this to a REL message sent to the Intermediate exchange. +- The Intermediate exchange responds with an RLC message back to the Originating exchange. +- The Originating exchange then sends a REL COMP message back to the first ISDN access. +- Simultaneously, the Intermediate exchange sends a REL message to the Destination exchange. +- The Destination exchange responds with an RLC message back to the Intermediate exchange. +- The Destination exchange then maps the REL to a DISC message (labeled with Note 2) sent to the second ISDN access. +- The second ISDN access responds with a REL message back to the Destination exchange. +- Finally, the Destination exchange sends a REL COMP message to the second ISDN access. + +T1183930-97 + +Sequence diagram of the normal call release procedure without tone provision. + +NOTE 1 – This procedure is applicable to those basic services where in-band tone/announcement is not provided, e.g. 64 kbit/s unrestricted bearer service. + +NOTE 2 – The DISCONNECT message should not include the progress indicator No. 8. + +**Figure A.17/Q.699 – Normal call release procedure without tone provision (Note 1)** + +For detailed message and parameter mappings, refer to: + +- REL message – subclauses 2.1.1.8 and 3.1.1.7. + +### A.2.4 Simple segmentation procedures/call flow diagrams for basic call control + +#### A.2.4.1 Simple segmentation procedures in the forward direction + +See 2.1.12/Q.764 and 5.1/Q.931. + +Figure A.18 indicates the simple segmentation procedures in the forward direction. + +![Sequence diagram showing simple segmentation procedures in the forward direction for basic call control. The diagram illustrates the flow of messages between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. The sequence of messages is: SETUP (from ISDN access to Originating exchange), CALL PROC (from Originating exchange to ISDN access), IAM (from Originating exchange to Intermediate exchange), SGM (from Originating exchange to Intermediate exchange, Note 4), ACM (from Intermediate exchange to Originating exchange, Note 3), CPG (from Intermediate exchange to Originating exchange), ANM (from Intermediate exchange to Originating exchange), ALERT (from Originating exchange to ISDN access), CONN (from Originating exchange to ISDN access), CONN ACK (from ISDN access to Originating exchange, Note 2). The Destination exchange receives IAM and SGM from the Intermediate exchange, and sends SETUP, CALL PROC (Note 1), ALERT, CONN, CONN, and ACK to the final ISDN access. The diagram also shows the flow of messages from the Destination exchange back to the Originating exchange: ACM (Note 3), CPG, and ANM. The diagram is labeled T1183940-97.](8768e42bf1062f1af11f259fc52a92e9_img.jpg) + +The diagram illustrates the call flow for simple segmentation procedures in the forward direction. It shows the sequence of messages between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. The sequence of messages is: SETUP (from ISDN access to Originating exchange), CALL PROC (from Originating exchange to ISDN access), IAM (from Originating exchange to Intermediate exchange), SGM (from Originating exchange to Intermediate exchange, Note 4), ACM (from Intermediate exchange to Originating exchange, Note 3), CPG (from Intermediate exchange to Originating exchange), ANM (from Intermediate exchange to Originating exchange), ALERT (from Originating exchange to ISDN access), CONN (from Originating exchange to ISDN access), CONN ACK (from ISDN access to Originating exchange, Note 2). The Destination exchange receives IAM and SGM from the Intermediate exchange, and sends SETUP, CALL PROC (Note 1), ALERT, CONN, CONN, and ACK to the final ISDN access. The diagram also shows the flow of messages from the Destination exchange back to the Originating exchange: ACM (Note 3), CPG, and ANM. The diagram is labeled T1183940-97. + +Sequence diagram showing simple segmentation procedures in the forward direction for basic call control. The diagram illustrates the flow of messages between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. The sequence of messages is: SETUP (from ISDN access to Originating exchange), CALL PROC (from Originating exchange to ISDN access), IAM (from Originating exchange to Intermediate exchange), SGM (from Originating exchange to Intermediate exchange, Note 4), ACM (from Intermediate exchange to Originating exchange, Note 3), CPG (from Intermediate exchange to Originating exchange), ANM (from Intermediate exchange to Originating exchange), ALERT (from Originating exchange to ISDN access), CONN (from Originating exchange to ISDN access), CONN ACK (from ISDN access to Originating exchange, Note 2). The Destination exchange receives IAM and SGM from the Intermediate exchange, and sends SETUP, CALL PROC (Note 1), ALERT, CONN, CONN, and ACK to the final ISDN access. The diagram also shows the flow of messages from the Destination exchange back to the Originating exchange: ACM (Note 3), CPG, and ANM. The diagram is labeled T1183940-97. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931 ). + +NOTE 3 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISDN access indicator = ISDN access, ISUP used all the way = yes, interworking encountered = no. If *Late ACM* is used, the ACM is delayed until the ALERT is received from the ISDN access. No CPG message is sent. + +NOTE 4 – The SGM is independently generated by the originating exchange when the original IAM could have exceeded 272 octets in length. The SGM contains the parameters removed from the IAM that allowed the IAM message length to under 272 octets. For details see 2.1.12/Q.764. + +**Figure A.18/Q.699 – Simple segmentation in forward direction** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclause 2.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.1.1.3; +- CPG message – subclauses 2.1.1.4 and 3.1.1.4; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +#### A.2.4.2 Simple segmentation procedures in the backward direction + +See 2.1.12/Q.764 and 5.1/Q.931. + +Figure A.19 indicates the simple segmentation procedures in the backward direction. + +![Sequence diagram illustrating simple segmentation procedures in the backward direction for ISDN access. The diagram shows message exchanges between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. Forward messages (left to right) include SETUP, IAM, and SETUP. Backward messages (right to left) include CALL PROC, ACM, SGM, ANM, ALERT, CONN, CONN ACK, and ACK. The diagram uses symbols for exchanges: a circle with an 'X' for the Originating and Intermediate exchanges, and a circle with a dot for the Destination exchange. The ISDN access is represented by dashed vertical lines. The label 'T1183950-97' is at the bottom right.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +The diagram illustrates the message flow for simple segmentation procedures in the backward direction. It involves five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The flow is as follows: +1. SETUP is sent from the first ISDN access to the Originating exchange. +2. CALL PROC is sent from the Originating exchange back to the first ISDN access. +3. SETUP is sent from the Originating exchange to the Intermediate exchange. +4. IAM is sent from the Intermediate exchange to the Destination exchange. +5. SETUP is sent from the Destination exchange to the second ISDN access. +6. ACM is sent from the Destination exchange back to the Intermediate exchange. +7. SGM (Note 2) is sent from the Destination exchange back to the Intermediate exchange. +8. ANM is sent from the Destination exchange back to the Intermediate exchange. +9. ACM is sent from the Intermediate exchange back to the Originating exchange. +10. SGM is sent from the Intermediate exchange back to the Originating exchange. +11. ANM is sent from the Intermediate exchange back to the Originating exchange. +12. ALERT is sent from the Originating exchange back to the first ISDN access. +13. CONN is sent from the Originating exchange back to the first ISDN access. +14. CONN ACK is sent from the first ISDN access back to the Originating exchange (Note 1). +15. ACK is sent from the Originating exchange back to the first ISDN access. + +Sequence diagram illustrating simple segmentation procedures in the backward direction for ISDN access. The diagram shows message exchanges between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another ISDN access. Forward messages (left to right) include SETUP, IAM, and SETUP. Backward messages (right to left) include CALL PROC, ACM, SGM, ANM, ALERT, CONN, CONN ACK, and ACK. The diagram uses symbols for exchanges: a circle with an 'X' for the Originating and Intermediate exchanges, and a circle with a dot for the Destination exchange. The ISDN access is represented by dashed vertical lines. The label 'T1183950-97' is at the bottom right. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 2 – The SGM is independently generated by the destination exchange when the original ACM would have exceeded 272 octets in length. The SGM contains the parameters removed from the ACM that allowed the ACM message length to under 272 octets. + +For details see 2.1.12/Q.764. Segmentation procedure can be repeated + +to any backward message containing the optional backward call indicator parameter. + +If *Late ACM* is used, the ACM is sent with called party status = subscriber free. SGM is sent after ACM. No CPG is sent from the ISDN access. + +**Figure A.19/Q.699 – Simple segmentation in-backward direction** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.1.1.3; +- ANM message – subclauses 2.1.1.5 and 3.1.1.5. + +## A.3 Interworking of ISDN access and non-ISDN access over ISUP + +The call flow diagrams are divided into functional subclauses: + +- successful call set-up procedures; +- unsuccessful call set-up procedures; +- release procedures; and +- suspend/resume procedures. + +### A.3.1 Successful call set-up procedures/call flow diagrams + +#### A.3.1.1 ISDN access to non-ISDN access + +See 2.1/Q.764 and 5.1/Q.764. + +Figure A.20 shows the sequence of messages for a call from an ISDN access to a non-ISDN access. The arrows between the originating exchange and the non-ISDN access indicate signals that may vary with the access protocol. If continuity check occurs in the network, the ringing from the destination exchange is not passed until continuity is verified. + +![Sequence diagram for ISDN access to non-ISDN access call set-up. The diagram shows two cases (Case 1 and Case 2) of message exchanges between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and a Non-ISDN access. Case 1 shows a standard setup with SETUP, CALL PROC, ALERT (PI=2), CONN, and ACK messages. Case 2 shows a setup with SETUP, CALL PROC, PROG (PI=2), CONN, and ACK messages. Both cases involve IAM, ACM, and ANM messages between the exchanges. The Non-ISDN access receives Ringing and Off-hook signals from the Destination exchange.](50a63fe40eaa16cb8745c689fe8f8264_img.jpg) + +The diagram illustrates the message sequence for two cases of call set-up from an ISDN access to a non-ISDN access. The entities involved are: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The Originating and Destination exchanges are shown with symbols for ISDN interfaces (circles with crosses) and non-ISDN interfaces (circles). The Intermediate exchange is shown with a cross symbol. The sequence of messages is as follows: + +- Case 1:** + - ISDN access sends **SETUP** to Originating exchange. + - Originating exchange sends **CALL PROC** to ISDN access. + - Originating exchange sends **ALERT (PI=2)** to ISDN access (Note 1). + - Originating exchange sends **CONN** to ISDN access. + - ISDN access sends **CONN** to Originating exchange. + - ISDN access sends **ACK** to Originating exchange (Note 3). + - Originating exchange sends **IAM** to Intermediate exchange. + - Intermediate exchange sends **IAM** to Destination exchange. + - Destination exchange sends **Ringing** to Non-ISDN access. + - Destination exchange sends **ACM** to Intermediate exchange (Note 2). + - Intermediate exchange sends **ACM** to Originating exchange. + - Destination exchange sends **ANM** to Intermediate exchange. + - Intermediate exchange sends **ANM** to Originating exchange. + - Destination exchange sends **Off-hook** to Non-ISDN access. +- Case 2:** + - ISDN access sends **SETUP** to Originating exchange. + - Originating exchange sends **CALL PROC** to ISDN access. + - Originating exchange sends **PROG (PI=2)** to ISDN access (Note 1). + - Originating exchange sends **CONN** to ISDN access. + - ISDN access sends **CONN** to Originating exchange. + - ISDN access sends **ACK** to Originating exchange (Note 3). + - Originating exchange sends **IAM** to Intermediate exchange. + - Intermediate exchange sends **IAM** to Destination exchange. + - Destination exchange sends **Ringing** to Non-ISDN access. + - Destination exchange sends **ACM** to Intermediate exchange (Note 4). + - Intermediate exchange sends **ACM** to Originating exchange. + - Destination exchange sends **ANM** to Intermediate exchange. + - Intermediate exchange sends **ANM** to Originating exchange. + - Destination exchange sends **Off-hook** to Non-ISDN access. + +Sequence diagram for ISDN access to non-ISDN access call set-up. The diagram shows two cases (Case 1 and Case 2) of message exchanges between an ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and a Non-ISDN access. Case 1 shows a standard setup with SETUP, CALL PROC, ALERT (PI=2), CONN, and ACK messages. Case 2 shows a setup with SETUP, CALL PROC, PROG (PI=2), CONN, and ACK messages. Both cases involve IAM, ACM, and ANM messages between the exchanges. The Non-ISDN access receives Ringing and Off-hook signals from the Destination exchange. + +T1183960-97 + +NOTE 1 – Progress indicator = No. 2. In addition, originating local exchanges may generate progress indicator No. 8 to accomplish attachment of the B-channel if there is the possibility that terminals do not attach the B-channel on receipt of CALL PROCEEDING or SETUP ACKNOWLEDGE message. + +NOTE 2 – The ACM is independently generated at the destination exchange with the following parameters: called party status = subscriber free; ISDN User Part indicator = ISDN User Part used all the way; ISDN access indicator = non-ISDN access. + +NOTE 3 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 4 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISUP used all the way = yes; ISDN access indicator = non-ISDN access. In order to support user-generated in-band information (e.g. from PBX. See 2.1.4.1 1b)/Q.764), the destination exchange may include in the ACM optional backward call indicators = in-band information available and through-connect in the backward direction. + +**Figure A.20/Q.699 – ISDN access to non-ISDN access** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 3.2.1.1; +- ANM message – subclauses 2.1.1.5 and 3.2.1.5. + +#### A.3.1.2 Non-ISDN access to ISDN access + +See 2.1/Q.764 and 5.1/Q.931. + +Figure A.21 shows the sequence of messages for a call from a non-ISDN access to an ISDN access. Again the arrows between the non-ISDN access and originating exchange indicate signals that may vary with the access protocol. Procedures for ACM and ANM may vary as in Figures 3 to 6. Overlap addressing may also be used in this case. Interworking then follows the message flows shown in Figures 8 and 9. If continuity check occurs in the network, the SETUP message in the destination exchange is not passed until continuity is verified. + +![Sequence diagram for Non-ISDN access to ISDN access call flow. The diagram shows message exchanges between Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence starts with Off-hook plus digits from Non-ISDN access to Originating exchange. The Originating exchange sends IAM to Intermediate exchange, which then sends IAM to Destination exchange. The Destination exchange sends SETUP to ISDN access. The ISDN access responds with CALL PROC (Note 1), ALERT, CONN, and CONN ACK. The Destination exchange sends ACM (Note 2) and CPG to Intermediate exchange, which then sends ACM and CPG to Originating exchange. The Originating exchange sends ANM to Intermediate exchange, which sends ANM to Destination exchange. Finally, the Originating exchange sends Answer (Note 3) to Non-ISDN access.](db7a693cf26f527ac6c0d4d41da20858_img.jpg) + +``` + +sequenceDiagram + participant Non-ISDN access + participant Originating exchange + participant Intermediate exchange + participant Destination exchange + participant ISDN access + + Non-ISDN access->>Originating exchange: Off-hook plus digits + Originating exchange->>Intermediate exchange: IAM + Intermediate exchange->>Destination exchange: IAM + Destination exchange->>ISDN access: SETUP + ISDN access-->>Destination exchange: CALL PROC (Note 1) + Destination exchange-->>Intermediate exchange: ACM (Note 2) + Intermediate exchange-->>Originating exchange: ACM + ISDN access-->>Destination exchange: ALERT + Destination exchange-->>Intermediate exchange: CPG + Intermediate exchange-->>Originating exchange: CPG + ISDN access-->>Destination exchange: CONN + Destination exchange-->>Intermediate exchange: ANM + Intermediate exchange-->>Originating exchange: ANM + Originating exchange->>Non-ISDN access: Answer (Note 3) + Destination exchange->>ISDN access: CONN ACK + +``` + +Sequence diagram for Non-ISDN access to ISDN access call flow. The diagram shows message exchanges between Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. The sequence starts with Off-hook plus digits from Non-ISDN access to Originating exchange. The Originating exchange sends IAM to Intermediate exchange, which then sends IAM to Destination exchange. The Destination exchange sends SETUP to ISDN access. The ISDN access responds with CALL PROC (Note 1), ALERT, CONN, and CONN ACK. The Destination exchange sends ACM (Note 2) and CPG to Intermediate exchange, which then sends ACM and CPG to Originating exchange. The Originating exchange sends ANM to Intermediate exchange, which sends ANM to Destination exchange. Finally, the Originating exchange sends Answer (Note 3) to Non-ISDN access. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working or to avoid timer expire response to SETUP (see 5.2.5.1/Q.931). + +NOTE 2 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISDN access indicator = ISDN access, ISUP used all the way = yes; interworking encountered = no. + +NOTE 3 – Conditional on type of access. + +**Figure A.21/Q.699 – Non-ISDN access to ISDN access** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.2.1.1 and 3.1.1.1; +- ANM message – subclauses 2.2.1.4 and 3.1.1.5. + +### A.3.2 Unsuccessful call set-up procedures/call flow diagrams + +#### A.3.2.1 Tone/announcement applied at the originating exchange + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.22 shows the unsuccessful set-up procedure where tones or announcements are generated in the originating exchange towards the ISDN access as a result of receiving a REL. + +Timer T306 is started after the appropriate tones or announcement are sent. Figure A.22 shows the originating ISDN access releasing before timer T306 expires. + +![Sequence diagram of an unsuccessful call set-up procedure. The diagram shows five vertical lifelines: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The sequence starts with a SETUP message from the ISDN access to the Originating exchange. The Originating exchange responds with a CALL PROC message. The Destination exchange sends a REL message (e.g., user busy) to the Intermediate exchange, which in turn sends a REL message to the Originating exchange. The Originating exchange then sends a DISC (PI=8) message to the ISDN access, followed by a (Note) and a REL message. The ISDN access responds with a REL COMP message. The diagram also shows IAM and RLC messages being passed between the exchanges. A note indicates that tones or announcements are generated in the originating exchange towards the ISDN access.](ed29f40262b821f88760fe2539d31090_img.jpg) + +``` +sequenceDiagram + participant ISDN access + participant Originating exchange + participant Intermediate exchange + participant Destination exchange + participant Non-ISDN access + + Note right of Destination exchange: (e.g. user busy) + + ISDN access->>Originating exchange: SETUP + Originating exchange-->>ISDN access: CALL PROC + Destination exchange-->>Intermediate exchange: REL + Intermediate exchange-->>Originating exchange: REL + Originating exchange-->>ISDN access: DISC (PI=8) + Note right of Originating exchange: (Note) + Originating exchange-->>ISDN access: REL + ISDN access-->>Originating exchange: REL COMP + ISDN access->>Originating exchange: IAM + Originating exchange->>Intermediate exchange: IAM + Intermediate exchange->>Destination exchange: IAM + Originating exchange-->>Intermediate exchange: RLC + Intermediate exchange-->>Destination exchange: RLC +``` + +Sequence diagram of an unsuccessful call set-up procedure. The diagram shows five vertical lifelines: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The sequence starts with a SETUP message from the ISDN access to the Originating exchange. The Originating exchange responds with a CALL PROC message. The Destination exchange sends a REL message (e.g., user busy) to the Intermediate exchange, which in turn sends a REL message to the Originating exchange. The Originating exchange then sends a DISC (PI=8) message to the ISDN access, followed by a (Note) and a REL message. The ISDN access responds with a REL COMP message. The diagram also shows IAM and RLC messages being passed between the exchanges. A note indicates that tones or announcements are generated in the originating exchange towards the ISDN access. + +NOTE – If tones/announcements are applied, a DISCONNECT message may be sent containing progress indicator No. 8. As an alternative, a PROGRESS message may also be sent containing progress indicator No. 8. + +**Figure A.22/Q.699 – Unsuccessful call set-up tone/announcement applied at originating exchange** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclause 2.1.1.1; +- REL message – subclauses 2.1.1.7 and 3.2.1.9. + +#### A.3.2.2 Tone or announcement applied by destination exchange + +See 2.2/Q.764 and 5.3/Q.931. + +Figure A.23 shows an unsuccessful call where certain tones or announcements can only be generated in the destination exchange (or intermediate exchange) during call establishment. This is a typical case for example for a changed number announcement where the changed number information is only available at the destination exchange. Alternatively a specific announcement may be applied at an intermediate exchange to indicate for example that all circuits to a particular destination are busy. + +The originating exchange sends a DISCONNECT message to the calling user with progress indicator No. 8 thus indicating that in-band information is available. Normal release procedures apply after the in-band information has been connected. + +![Sequence diagram for an unsuccessful call setup tone/announcement applied by destination exchange. The diagram shows two cases (Case 1 and Case 2) involving ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access.](f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg) + +``` +sequenceDiagram + participant ISDN as ISDN access + participant OE as Originating exchange + participant IE as Intermediate exchange + participant DE as Destination exchange + participant NISDN as Non-ISDN access + + Note over ISDN, NISDN: Case 1 + ISDN->>OE: SETUP + OE->>IE: IAM + IE->>DE: IAM + OE<<--ISDN: CALL PROC + DE-->>IE: ACM (Note 3) + IE-->>OE: ACM + OE-->>ISDN: DISC (PI = 8) (Note 1) + Note right of DE: Tone/Annct (Note 2) + OE->>IE: REL + IE->>DE: REL + DE-->>IE: RLC + IE-->>OE: RLC + OE-->>ISDN: REL COMP + + Note over ISDN, NISDN: Case 2 + ISDN->>OE: SETUP + OE->>IE: IAM + IE->>DE: IAM + OE<<--ISDN: CALL PROC + DE-->>IE: ACM + IE-->>OE: CPG + OE-->>ISDN: DISC (PI = 8) (Note 1) + Note right of DE: Tone/Annct (Note 2) + OE->>IE: REL + IE->>DE: REL + DE-->>IE: RLC + IE-->>OE: RLC + OE-->>ISDN: REL COMP +``` + +T1183990-97 + +Sequence diagram for an unsuccessful call setup tone/announcement applied by destination exchange. The diagram shows two cases (Case 1 and Case 2) involving ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. + +NOTE 1 – A DISCONNECT message may be sent containing progress indicator No. 8. As an alternative, a PROGRESS message may also be sent containing progress indicator No. 8. + +NOTE 2 – Customized announcements can only be provided by this exchange. + +NOTE 3 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISUP used all the way = yes; ISDN access indicator = non-ISDN access. + +**Figure A.23/Q.699 – Unsuccessful call set-up tone/announcement applied by destination exchange** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclause 2.1.1.1; +- ACM message – subclauses 2.1.1.3 and 3.2.1.3; +- CPG message – subclauses 2.1.1.4 and 3.2.1.4. + +### A.3.3 Release procedures/call flow diagrams + +#### A.3.3.1 Normal release for ISDN access to non-ISDN access interworking + +See 2.3/Q.764 and 5.3/Q.931. + +*Case 1: Clear forward.* This part of Figure A.24 shows the normal call release procedure being initiated from the originating ISDN access by means of a DISCONNECT message. + +At the destination exchange, a REL is mapped into an appropriate clear-forward signal to the non-ISDN access. + +*Case 2: Clear backward.* This part of Figure A.24 shows the normal call release procedure being initiated from the terminating non-ISDN access by means of a clear-back signal. + +At the destination exchange, the clear-back signal is mapped into a SUS with suspend/resume indicator (network initiated). + +The originating ISDN exchange starts the timer. Upon expiry of the timer, if the originating exchange has not received a RES message, the originating exchange initiates clearing by a REL to the preceding exchange. + +![Sequence diagram showing normal release procedures for ISDN access to non-ISDN access interworking. The diagram is divided into two cases: Case 1 (Clear forward) and Case 2 (Clear backward). It shows the interaction between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. Case 1 shows release initiated from the ISDN access with DISC, REL, and REL COMP messages. Case 2 shows release initiated from the Non-ISDN access with On-hook, REL, RLC, and SUS messages, leading to a timeout and subsequent REL/RLC/REL COMP messages back to the ISDN access.](684fc3764b7e61b9a9f9e28c2f7ecde9_img.jpg) + +The diagram illustrates two call release scenarios between an ISDN access and a non-ISDN access via a series of exchanges. The components are: ISDN access, Originating exchange (marked with a circle-X), Intermediate exchange (marked with a circle-X), Destination exchange (marked with a circle-X), and Non-ISDN access. + +**Case 1: Clear forward** +The release is initiated at the ISDN access with a DISC message to the Originating exchange. The Originating exchange sends a REL message to the Intermediate exchange, which in turn sends a REL message to the Destination exchange. The Destination exchange sends a 'Clear forward' signal to the Non-ISDN access. A return path of REL and REL COMP messages is shown from the Originating exchange back to the ISDN access. + +**Case 2: Clear backward** +The release is initiated at the Non-ISDN access with an 'On-hook' signal to the Destination exchange. The Destination exchange sends a SUS (network) message to the Intermediate exchange, which sends a REL message to the Originating exchange. The Originating exchange starts a 'Time out' timer. Upon timeout, the Originating exchange sends a REL message to the Intermediate exchange, which sends a RLC message to the Destination exchange. A return path of REL, RLC, and REL COMP messages is shown from the Originating exchange back to the ISDN access. + +Sequence diagram showing normal release procedures for ISDN access to non-ISDN access interworking. The diagram is divided into two cases: Case 1 (Clear forward) and Case 2 (Clear backward). It shows the interaction between ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. Case 1 shows release initiated from the ISDN access with DISC, REL, and REL COMP messages. Case 2 shows release initiated from the Non-ISDN access with On-hook, REL, RLC, and SUS messages, leading to a timeout and subsequent REL/RLC/REL COMP messages back to the ISDN access. + +T1184000-97 + +**Figure A.24/Q.699 – Normal release procedures for ISDN access to non-ISDN access interworking** + +For detailed message and parameter mappings, refer to: + +- REL message – subclauses 2.1.1.8 and 3.2.1.6. + +#### A.3.3.2 Normal release for non-ISDN access to ISDN access interworking + +See 2.3/Q.764 and 5.3/Q.931. + +*Case 1: Clear forward.* This part of Figure A.25 shows the normal call release procedure being initiated from the originating non-ISDN access by means of a clear-forward signal. + +At the originating exchange, the clear-forward signal is mapped into a REL to the ISDN exchange. + +*Case 2: Clear backward.* This part of Figure A.25 shows the normal call release procedure being initiated from the terminating ISDN access by means of a DISCONNECT message. + +At the originating exchange, a REL message is mapped into an appropriate backward signal in non-ISDN access. + +![Sequence diagram of normal release procedure for non-ISDN access to ISDN access interworking. It shows two cases: Case 1 (Clear forward) and Case 2 (Clear backward) involving Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access.](a34a521d4a9ba7071e87adf963f12fa7_img.jpg) + +The diagram illustrates the message flow for call release between a Non-ISDN access and an ISDN access through a series of exchanges. The components are: Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. Each exchange is represented by a box with a circle-X symbol. Case 1 (Clear forward) shows the release initiated from the Non-ISDN access via an 'On-hook' signal, which is then processed through the exchanges using REL and RLC messages, finally reaching the ISDN access with DISC, REL, and REL COMP messages. Case 2 (Clear backward) shows the release initiated from the ISDN access via DISC, REL, and REL COMP messages, which are then processed back through the exchanges using REL and RLC messages, finally reaching the Non-ISDN access with a 'Clear back' signal. The diagram is labeled T1184010-97 at the bottom right. + +Sequence diagram of normal release procedure for non-ISDN access to ISDN access interworking. It shows two cases: Case 1 (Clear forward) and Case 2 (Clear backward) involving Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and ISDN access. + +**Figure A.25/Q.699 – Normal release procedure for non-ISDN access to ISDN access interworking** + +For detailed message and parameter mappings, refer to: + +- REL messages – subclauses 2.2.1.6, 2.2.1.7, 3.1.1.7 and 3.1.1.8. + +### A.3.4 Simple segmentation procedures + +See 2.1.12/Q.764 and 5.1/Q.931. + +Figure A.26 indicates the simple segmentation procedures in the forward direction. The destination exchange should not set up the call to the non-ISDN access until the SGM is received. + +![Sequence diagram of simple segmentation procedures in the forward direction. The diagram shows five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The flow of messages is as follows: 1. SETUP from ISDN access to Originating exchange. 2. CALL PROC from Originating exchange to ISDN access. 3. PROG from Originating exchange to ISDN access. 4. CONN from Originating exchange to ISDN access. 5. CONN ACK from ISDN access to Originating exchange (Note 1). 6. IAM from Originating exchange to Intermediate exchange. 7. SGM (Note 4) from Originating exchange to Intermediate exchange. 8. ACM from Intermediate exchange to Originating exchange. 9. ANM from Intermediate exchange to Originating exchange. 10. IAM from Intermediate exchange to Destination exchange. 11. SGM from Intermediate exchange to Destination exchange. 12. ACM from Destination exchange to Intermediate exchange (Note 3). 13. ANM from Destination exchange to Intermediate exchange. 14. Ringing from Destination exchange to Non-ISDN access. 15. Off-hook from Non-ISDN access to Destination exchange. The diagram is labeled T1184020-97 at the bottom right.](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) + +Sequence diagram of simple segmentation procedures in the forward direction. The diagram shows five entities: ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The flow of messages is as follows: 1. SETUP from ISDN access to Originating exchange. 2. CALL PROC from Originating exchange to ISDN access. 3. PROG from Originating exchange to ISDN access. 4. CONN from Originating exchange to ISDN access. 5. CONN ACK from ISDN access to Originating exchange (Note 1). 6. IAM from Originating exchange to Intermediate exchange. 7. SGM (Note 4) from Originating exchange to Intermediate exchange. 8. ACM from Intermediate exchange to Originating exchange. 9. ANM from Intermediate exchange to Originating exchange. 10. IAM from Intermediate exchange to Destination exchange. 11. SGM from Intermediate exchange to Destination exchange. 12. ACM from Destination exchange to Intermediate exchange (Note 3). 13. ANM from Destination exchange to Intermediate exchange. 14. Ringing from Destination exchange to Non-ISDN access. 15. Off-hook from Non-ISDN access to Destination exchange. The diagram is labeled T1184020-97 at the bottom right. + +NOTE 1 – This message may be sent by the user to achieve symmetrical working (see 5.1.8/Q.931). + +NOTE 2 – Completion of transmission path timing is described in 2.1.9.1/Q.764. + +NOTE 3 – The ACM is independently generated at the destination exchange with the following parameters: called party status = no indication; ISDN access indicator = non-ISDN access; ISUP used all the way = yes; interworking encountered = no. + +NOTE 4 – The SGM is independently generated by the originating exchange when the original IAM would have exceeded 272 octets in length. The SGM contains the parameters removed from the IAM that allowed the IAM message length to under 272 octets. For details see 2.1.12/Q.764. + +**Figure A.26/Q.699 – Simple segmentation** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.1.1.1 and 2.2.1.1; +- ANM message – subclauses 2.1.1.5 and 3.2.1.5. + +## A.4 Interworking of non-ISDN access over ISUP + +The call flow diagrams are divided into functional subclauses: + +- successful call set-up procedures; +- unsuccessful call set-up procedures; +- release procedures; and +- suspend/resume procedures. + +### A.4.1 Successful call set-up procedures/call flow diagrams + +#### A.4.1.1 Non-ISDN access to non-ISDN access over ISUP + +See 2.1/Q.764. + +Figure A.27 shows the sequence of messages for a call from a non-ISDN access to a non-ISDN access. The arrows between the originating exchange and non-ISDN access indicate signals that may vary with the access protocol. If continuity check occurs in the network, the ringing from the destination exchange is not passed until continuity is verified. + +![Sequence diagram for Non-ISDN access to non-ISDN access over ISUP call set-up.](8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg) + +The diagram illustrates the call set-up sequence between a Non-ISDN access, an Originating exchange, an Intermediate exchange, a Destination exchange, and another Non-ISDN access. The sequence of messages is as follows: + +- The Non-ISDN access sends an **Off-hook and digits** signal to the Originating exchange. +- The Originating exchange sends an **IAM** (Initial Address Message) to the Intermediate exchange. +- The Intermediate exchange sends an **IAM** to the Destination exchange. +- The Destination exchange sends a **Ringing** signal to the Non-ISDN access. +- The Destination exchange also sends an **ACM** (Address Complete Message) back to the Intermediate exchange. +- The Intermediate exchange sends an **ACM** back to the Originating exchange. +- The Destination exchange sends an **Off-hook** signal to the Non-ISDN access. +- The Destination exchange sends an **ANM** (Answer Message) back to the Intermediate exchange. This message is labeled **(Note 1)**. +- The Intermediate exchange sends an **ANM** back to the Originating exchange. +- The Originating exchange sends an **Answer** signal back to the Non-ISDN access. This message is labeled **(Note 2)**. + +T1184030-97 + +Sequence diagram for Non-ISDN access to non-ISDN access over ISUP call set-up. + +NOTE 1 – The ACM is independently generated at the destination exchange with the following parameters: called party status = subscriber free; ISUP used all the way = yes; ISDN access indicator = non-ISDN access. + +NOTE 2 – Conditional on type of access. + +**Figure A.27/Q.699 – Non-ISDN access to non-ISDN access** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.2.1.1 and 3.2.1.1; +- ANM message – subclauses 2.2.1.4 and 3.2.1.5. + +### A.4.2 Unsuccessful call set-up procedures/call flow diagrams + +#### A.4.2.1 Tone/announcement applied at the originating exchange + +See 2.2/Q.764. + +Figure A.28 shows the unsuccessful set-up procedure where tones or announcements are generated in the originating exchange towards the non-ISDN access as a result of receiving a REL. The destination exchange sends a REL after detection of the user busy by the non-ISDN access condition. + +Timer T306 is started after the appropriate tone/announcement is sent. Figure A.28 shows the originating non-ISDN line access releasing before timer T306 expires. + +![Sequence diagram of an unsuccessful call set-up procedure. The diagram shows five entities: Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The sequence starts with 'Off-hook and digits' from the first Non-ISDN access to the Originating exchange. The Originating exchange sends an 'IAM' message to the Intermediate exchange, which in turn sends an 'IAM' message to the Destination exchange. The Destination exchange detects a busy condition (e.g., user busy) and sends a 'REL' message back to the Intermediate exchange. The Intermediate exchange then sends a 'REL' message back to the Originating exchange. The Originating exchange generates a 'Clear back (Note)' signal and a 'Clear forward' signal back to the first Non-ISDN access. The Originating exchange also sends an 'RLC' message to the Intermediate exchange, which is then forwarded by the Intermediate exchange to the Destination exchange. The diagram is labeled T1184040-97.](d1be394c67ec994c0c8529d29ea3e9cc_img.jpg) + +``` +sequenceDiagram + participant Non-ISDN access 1 as Non-ISDN access + participant Originating exchange + participant Intermediate exchange + participant Destination exchange + participant Non-ISDN access 2 as Non-ISDN access + + Note right of Destination exchange: (e.g. user busy) + + Non-ISDN access 1->>Originating exchange: Off-hook and digits + Originating exchange->>Intermediate exchange: IAM + Intermediate exchange->>Destination exchange: IAM + Destination exchange-->>Intermediate exchange: REL + Intermediate exchange-->>Originating exchange: REL + Originating exchange-->>Non-ISDN access 1: Clear back (Note) + Originating exchange-->>Non-ISDN access 1: Clear forward + Originating exchange->>Intermediate exchange: RLC + Intermediate exchange->>Destination exchange: RLC +``` + +Sequence diagram of an unsuccessful call set-up procedure. The diagram shows five entities: Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The sequence starts with 'Off-hook and digits' from the first Non-ISDN access to the Originating exchange. The Originating exchange sends an 'IAM' message to the Intermediate exchange, which in turn sends an 'IAM' message to the Destination exchange. The Destination exchange detects a busy condition (e.g., user busy) and sends a 'REL' message back to the Intermediate exchange. The Intermediate exchange then sends a 'REL' message back to the Originating exchange. The Originating exchange generates a 'Clear back (Note)' signal and a 'Clear forward' signal back to the first Non-ISDN access. The Originating exchange also sends an 'RLC' message to the Intermediate exchange, which is then forwarded by the Intermediate exchange to the Destination exchange. The diagram is labeled T1184040-97. + +NOTE – The originating exchange sends a clear-back signal to the calling user depending on the condition of the type of access. + +**Figure A.28/Q.699 – Unsuccessful call set-up tone/announcement applied at originating exchange** + +For detailed message and parameter mappings refer to: + +- IAM message – subclauses 2.2.1.1 and 3.2.1.1; +- REL message – subclauses 2.2.1.7 and 3.2.1.9. + +#### A.4.2.2 Tone applied by destination exchange + +See 2.2/Q.764. + +Figure A.29 shows an unsuccessful call where certain tones and announcements can only be generated in the destination exchange (or intermediate exchange) during call establishment. This is a typical case for example for a changed number announcement where the changed number information is only available at the destination exchange. Alternatively a specific announcement may be applied at an intermediate exchange to indicate for example that all circuits to a particular destination are busy. + +The originating exchange sends a clear backward to the calling user. Normal release procedures apply after the in-band information has been connected. + +![Sequence diagram of an unsuccessful call setup with tone/announcement at the destination exchange.](a83c022a6dac411615bcc38b7cd0d573_img.jpg) + +The diagram illustrates the signaling flow for an unsuccessful call setup across five entities: Non-ISDN access, Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access. The sequence of messages is as follows: + +- Off-hook and digits:** Sent from the left Non-ISDN access to the Originating exchange. +- IAM (Initial Address Message):** Sent from the Originating exchange to the Intermediate exchange, and then from the Intermediate exchange to the Destination exchange. +- ACM (Address Complete Message):** Sent from the Destination exchange back to the Intermediate exchange, and then from the Intermediate exchange back to the Originating exchange. +- Tone/Annct:** Generated at the Destination exchange (e.g., "number changed" as per Note 2) and sent back to the Originating exchange via a wavy line representing in-band information. +- REL (Release Message):** Sent from the Originating exchange to the Intermediate exchange, and then from the Intermediate exchange to the Destination exchange. +- RLC (Release Complete Message):** Sent from the Destination exchange back to the Intermediate exchange, and then from the Intermediate exchange back to the Originating exchange. +- Clear back (Note 1):** Sent from the Originating exchange back to the left Non-ISDN access. +- On-hook:** Sent from the left Non-ISDN access to the Originating exchange. + +Reference code: T1184050-97 + +Sequence diagram of an unsuccessful call setup with tone/announcement at the destination exchange. + +NOTE 1 – The originating exchange sends a clear-back signal to the calling user depending on the condition of the type of access. + +NOTE 2 – Customized announcements can only be provided by this exchange. + +**Figure A.29/Q.699 – Unsuccessful call set-up tone/announcement applied by destination exchange** + +For detailed message and parameter mappings, refer to: + +- IAM message – subclauses 2.2.1.1 and 3.2.1.1; +- REL message – subclauses 2.2.1.7 and 3.2.1.6. + +### A.4.3 Release procedures/call flow diagrams + +#### A.4.3.1 Normal release for non-ISDN access to non-ISDN access interworking + +See 2.3/Q.764. + +*Case 1: Clear forward.* This part of Figure A.30 shows the normal call release procedure being initiated from the originating non-ISDN access by means of a clear-forward signal. + +At the originating exchange, the clear-forward signal is mapped into a REL message to the ISDN exchange. + +*Case 2: Clear backward.* This part of Figure A.30 shows the normal call release procedure being initiated from the terminating non-ISDN access by means of a clear-backward message. + +At the originating exchange, a REL message is mapped into an appropriate backward signal on the non-ISDN access. + +![Sequence diagram showing normal release procedures for non-ISDN access to non-ISDN access interworking. It illustrates two cases: Case 1 (Clear forward) and Case 2 (Clear backward) involving an originating exchange, intermediate exchange, and destination exchange.](88e677d1623f443e57a730fe04a495a5_img.jpg) + +The diagram illustrates two call release scenarios between two non-ISDN accesses through a series of three exchanges: Originating exchange, Intermediate exchange, and Destination exchange. Each exchange is represented by a vertical rectangle containing a circle with an 'X' (representing a switch or node). + +**Case 1: Clear forward** +The release is initiated at the left Non-ISDN access with an 'On-hook' signal. This is mapped to a 'REL' message sent from the Originating exchange to the Intermediate exchange. The Intermediate exchange forwards the 'REL' message to the Destination exchange. The Destination exchange then sends a 'Clear forward' signal to the right Non-ISDN access. Backward signals 'RLC' (Release Link) are sent from the Intermediate exchange back to the Originating exchange, and from the Destination exchange back to the Intermediate exchange. + +**Case 2: Clear backward** +The release is initiated at the right Non-ISDN access with an 'On-hook' signal. This is mapped to a 'Clear forward' signal sent from the Destination exchange to the Intermediate exchange. The Intermediate exchange then sends a 'REL' message to the Originating exchange. The Originating exchange maps this to a 'Clear back' signal sent to the left Non-ISDN access. Backward signals 'RLC' are sent from the Intermediate exchange back to the Originating exchange, and from the Destination exchange back to the Intermediate exchange. Additionally, a 'SUS (network)' (Suspend) message is shown being sent from the Originating exchange to the Intermediate exchange, and a 'Time out' indicator is shown at the Originating exchange. + +T1184060-97 + +Sequence diagram showing normal release procedures for non-ISDN access to non-ISDN access interworking. It illustrates two cases: Case 1 (Clear forward) and Case 2 (Clear backward) involving an originating exchange, intermediate exchange, and destination exchange. + +**Figure A.30/Q.699 – Normal release procedure for non-ISDN access to non-ISDN access interworking** + +For detailed message and parameter mappings refer to: + +- SUS message – subclauses 2.2.1.7 and 3.2.1.7; +- REL message – subclauses 2.2.1.7, 2.2.1.10 and 3.2.1.6. + +### A.4.4 Suspend/resume procedures/call flow diagrams + +#### A.4.4.1 Suspend/resume non-ISDN access/non-ISDN access interworking + +See 2.4/Q.764. + +Figure A.31 illustrates the suspend and resume procedures for non-ISDN access – non-ISDN access interworking. + +![Sequence diagram for non-ISDN access interworking suspend/resume procedures.](56f125e1bc127f7ac3d210407957413c_img.jpg) + +The diagram illustrates the sequence of messages for suspend and resume procedures between two non-ISDN accesses. The components involved are: Non-ISDN access (left), Originating exchange, Intermediate exchange, Destination exchange, and Non-ISDN access (right). The sequence of messages is as follows: + +- Suspend procedure:** + - The Destination exchange sends an **On-hook** message to the right Non-ISDN access. + - The Destination exchange sends a **SUS (network)** message to the Intermediate exchange. + - The Intermediate exchange sends a **SUS (network)** message to the Originating exchange. + - The Originating exchange sends a **Clear back** message to the left Non-ISDN access. +- Resume procedure:** + - The right Non-ISDN access sends an **Off-hook** message to the Destination exchange. + - The Destination exchange sends a **RES (network)** message to the Intermediate exchange. + - The Intermediate exchange sends a **RES (network)** message to the Originating exchange. + - The Originating exchange sends a **Reanswer** message to the left Non-ISDN access. + +T1184070-97 + +Sequence diagram for non-ISDN access interworking suspend/resume procedures. + +NOTE – Supervision control in controlling exchange. + +**Figure A.31/Q.699 – Suspend/resume ISDN access – non-ISDN access interworking** + +For detailed message and parameter mappings, refer to: + +- SUS message – subclauses 2.1.1.8 and 3.2.1.7; +- RES message – subclauses 2.1.1.9 and 3.2.1.8. + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.699.1-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.699.1-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/Q/T-REC-Q.699.1-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/Q/T-REC-Q.7-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.7-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd6d37344e1dcb73e876a09f0e28fcc3cc12e0bf --- /dev/null +++ b/marked/Q/T-REC-Q.7-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:473a66f8b6837745a7f32ac1741f274c5a10ec4eec34cbcf59ae9cab1ea41190 +size 7270 diff --git a/marked/Q/T-REC-Q.7-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.7-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4b548bd791672daee56c346f3f2ddb76b7cfc68a --- /dev/null +++ b/marked/Q/T-REC-Q.7-198811-I_PDF-E/raw.md @@ -0,0 +1,312 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.7** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**SIGNALLING SYSTEMS TO BE USED +FOR INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC TELEPHONE WORKING** + +**ITU-T Recommendation Q.7** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.7 was published in Fascicle VI.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SIGNALLING SYSTEMS TO BE USED FOR INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC TELEPHONE WORKING** + +*(Geneva, 1954 and 1964, Mar del Plata, 1968, +Geneva, 1976 and 1980)* + +The CCITT, + +*considering* + +(a) that standardization of the signalling systems to be used for international automatic and semiautomatic telephone working is necessary to keep to a minimum the number of different types of equipment serving the various routes at any one exchange; + +(b) that the following signalling systems have been standardized and are applicable for *general use* in international automatic and semi-automatic working: + +- Signalling System No. 4, standardized by the CCIF in 1954; +- Signalling System No. 5, standardized by the CCITT in 1964; +- Signalling System No. 6, standardized by the CCITT in 1968; +- Signalling System No. 7, standardized by the CCITT in 1980; + +(c) that the following signalling systems have been standardized and are applicable for *regional use* in international automatic and semi-automatic telephone working: + +- Signalling System R1 (Regional Signalling System No. 1, formerly called the North American System), standardized by the CCITT in 1968; +- Signalling System R2 (Regional Signalling System No. 2, formerly called the MFC Bern System), standardized by the CCITT in 1968; + +(d) that, under the conditions and subject to the reservations stated below, these signalling systems may be expected to give acceptable results for international automatic and semi-automatic telephone working; + +*desiring* + +that the CCITT Recommendation concerning the signalling systems for international automatic and semi-automatic telephone working be generally applied by all Administrations; + +*unanimously recommends* + +that, under the conditions and subject to the reservations stated below, Administrations should use, for international automatic and semi-automatic telephone working, one or more of the standard signalling systems mentioned in (b) and (c) above. + +## **1 Criteria for selecting a signalling system** + +Many factors influence the selection of a given signalling system for a particular application. Factors that should be considered include: + +### 1.1 *Satellite systems* because of long round-trip propagation delays ( $540 \pm 40$ ms) + +The inclusion of one satellite link in a telephone connection requires subscribers to keep more discipline than usual during a conversation. If use is made of two satellite links in tandem, requirements are even more stringent. In addition, there is the question of what transmission objectives are attainable on such a connection. + +According to Recommendation Q.13 the inclusion of two satellite links in a connection should be avoided in all but exceptional cases. To facilitate the observance of this Recommendation, it is advisable to inform the subsequent transit centres by means of signalling that a satellite link is already included in the connection. During the following routing process the transit centre(s) should select a terrestrial link. + +### 1.2 *Echo suppressors* + +Both long terrestrial telephone links and satellite links call for the insertion of echo suppressors. Recommendations G.131 [1] and Q.115 include basic requirements for the insertion of echo suppressors. + +Therefore, signalling systems should be arranged to act in cooperation with switching equipment to achieve the goals covered by Recommendations G.131 [1] and Q.115. This would be facilitated where the signalling system to be used provides the possibility of controlling the inclusion of echo suppressors. + +In the future, the use of echo cancellers may need to be considered (see Recommendation G.165 [2]). + +### 1.3 *Speech interpolation systems (e.g. TASI)* + +In the case of a transmission system with speech interpolation, it must be ensured that the signalling system to be used is compatible with speech interpolation. + +## 2 Further criteria for selecting a signalling system + +Once Administrations decide to establish a route, they will have to specify the general requirements to be met by the signalling system. + +In the following, some questions are drawn up which may serve as a guideline: + +- a) Does the transmission system provide for sufficient bandwidth (e.g. for outband line signalling)? +- b) Is the signal capacity sufficient to allow the setting-up of an ordinary connection? +- c) Is an additional exchange of information required, e.g.: + - for echo suppressor control, + - to increase routing facilities, + - to obtain or to offer detailed information on congestion, + - to obtain or to offer information on the condition of the called subscriber line, + - to obtain or to offer information on the nature of the call: + - i) for identification or + - ii) for management purposes? +- d) What requirements have to be set for the speed of the signalling system? What post-dialling and answering delays are to be tolerated? +- e) Is there any interdependence between the minimum bundle size and signalling (e.g., as in the case of pilot interruption control of Signalling System R2)? +- f) In the case of satellite systems, does the earth station require an extra interface between the terrestrial access circuits and the satellite links? +- g) Is it necessary to introduce a new signalling system? +- h) Is the signalling system suitable for application to the particular exchange type, e.g., electromechanical exchanges? + +## 3 Characteristics of the standard CCITT Signalling Systems for general use + +### 3.1 *Signalling System No. 4* + +Described and specified in Fascicle VI.2. + +Suitable for one-way operation. + +Suitable for terminal and transit working; in the latter case two or three circuits equipped with Signalling System No. 4 may be switched in tandem. + +Signalling System No. 4 is used in Europe and the Mediterranean Basin. + +It makes use of a two-frequency code within the speech band. + +A four-element binary code is employed for interregister signalling. Each of these elements consists of one of the two signal frequencies. + +Each digit is acknowledged. In the case of long propagation times, these acknowledgements have an adverse effect because the propagation time is included twice in one signalling cycle. This disadvantage is more or less compensated for by the overlap mode of operation. + +Signalling System No. 4 has a signal capacity of 16 codes for forward interregister signals and no register signals in the backward direction other than the acknowledgement signals. + +One signal is provided for echo suppressor control on mutual agreement. + +A signal is not provided to indicate whether the connection already includes a satellite link. + +Not suitable for operation on transmission systems with speech interpolation. + +### 3.2 *Signalling System No. 5* + +Described and specified in Fascicle VI.2. + +Suitable for both-way operation. + +Suitable for terminal and transit working; in the latter case two or three circuits equipped with Signalling System No. 5 may be switched in tandem. + +A multifrequency code (MFC: 2 out of 6) within the speech band is used for interregister signalling. The line signals consist of 1 or 2 frequencies within the speech band. + +The entire address information is stored up to the last signal. It is then transmitted en bloc as a rapid sequence of pulsed multifrequency code signals. + +The application of the en bloc mode of operation may result in an increased post-dialling delay, especially if the ST condition is determined by time out. + +Signalling System No. 5 has a signal capacity of 15 codes for forward interregister signals and no backward interregister signals. + +Signals are not provided either for echo suppressor control or for indicating whether the connection already includes a satellite link. + +Suitable for operation on transmission systems with speech interpolation and on satellite links. + +### 3.3 *Signalling System R1* + +Described and specified in Fascicle VI.4. + +Signalling System R1 is mainly used in North America. + +Suitable for both-way operation. + +Specified for terminal working. + +A multifrequency code (MFC: 2 out of 6) within the speech band is used for interregister signalling. + +In the analogue version of the Signalling System R1 line signalling, one frequency within the speech band is used. In the digital version of the Signalling System R1 line signalling, the two resultant signalling channels per speech circuit may be regarded as outband channels. + +The following three modes of operation can be used to transmit the address information: + +- en bloc, +- en bloc/overlap, or +- overlap. + +The mode of operation selected influences: + +- the seizing time of the next link, as well as +- the post-dialling delay. + +The address information is transmitted as pulsed MFC signals. + +Signalling System R1 has a signal capacity of 15 codes for forward interregister signals but no backward interregister signals. + +Signals are not provided either for echo suppressor control or for indicating whether the connection already includes a satellite link. + +Signalling System R1 can be used on satellite links. A variant of Signalling System R1 may be suitable for operation on transmission systems with digital speech interpolation, provided that the systems are designed and engineered to be transparent to pulsed interregister signals. + +### 3.4 *Signalling System R2* + +Described and specified in Fascicle VI.4. + +Used for one-way operation on analogue transmission systems. Both-way operation is possible on digital transmission systems. + +Suitable for terminal and transit working. + +Signalling System R2 is used in both national and international telephone networks in several regions of the world. + +A multifrequency code (MFC: 2 out of 6) within the speech band is used for interregister signalling. Since two different sets of six frequencies in separate bands are defined for forward and backward interregister signals, Signalling System R2 interregister signalling is suitable for use on 2-wire circuits as well as on 4-wire circuits. + +For the analogue version of the Signalling System R2 line signalling, use is made of a low-level tone-on-idle method out of band. In addition, pilot interruption control is used. + +The digital version of the line signalling uses two signalling channels to transmit the signalling information and for circuit supervision. For 2048 kbit/s PCM systems, the signalling information of the 30 speech circuits is transmitted in the Time Slot 16 (see Recommendation G.732 [3]). + +It should be noted that the analogue version of the line signalling can be used on digital links; the signalling states are sent coded on one signalling channel. This use of the analogue version on digital links is not recommended on international circuits. + +When a circuit is composed of both digital and analogue links, a conversion between the two versions of the line signalling can occur at the interface (see Recommendation Q.430). + +Compelled signalling is used to transmit the address information in the overlap mode as multifrequency code signals, i.e., each forward interregister signal is acknowledged by a backward interregister signal. Considering that four times the propagation time is to be included in one signalling cycle, the exchange of signals is rather slow if the propagation time is long. This disadvantage is more or less compensated for by the overlap mode of operation. + +Signalling System R2 has a higher signalling capacity than Signalling Systems No. 4, No. 5 and R1. The interregister signals allow, amongst others: + +- improved routing, +- detailed information on congestion, +- information on: + - i) the nature of call, + - ii) the condition of the called subscriber line, +- no-charge calls, and +- address-complete information. + +Signalling System R2 includes both forward and backward interregister signals for echo suppressor control. + +In Signalling System R2, two signals are specified which indicate whether *or not* the connection already includes a satellite link. + +Signalling System R2 may be suitable for use on satellite circuits, especially when it is already employed in the national or regional telephone networks concerned. + +When Signalling System R2 is to be used on satellite links, the following must be borne in mind: + +- In the case of analogue line signalling, intervals T1 and T2 have to be adapted. +- Pilot interruption control requires bundles comprising a multiple of 12 speech circuits. +- The register at the incoming end of a satellite link using Signalling System R2 shall be operated as an outgoing R2 register. +- The guard time for blocking and recognition of forward signals when pulsed signals are transmitted should be adapted to the propagation time on the satellite link. + +Signalling System R2 may be suitable for operation on transmission systems with digital speech interpolation, provided the systems are designed and engineered to be transparent to pulsed interregister signals. + +With 3 kHz spaced channels, the interregister signalling of Signalling System R2 may be used with the line signalling of Signalling System No. 4. + +### 3.5 *Signalling System No. 6* + +Fully described and specified in Fascicle VI.3. + +Suitable for both-way operation. + +Suitable for terminal and transit working. + +During the period from 1970 to 1972 Signalling System No. 6 was tested internationally. + +Some Administrations have introduced it for international telephone traffic. A variant of Signalling System No. 6 is employed in the national telephone network of the United States. + +A common signalling link is used for signalling. + +May be used in either an associated or quasi-associated mode of operation. Use in a quasi-associated mode may be more economic for small bundles of circuits. + +Signalling is performed by means of signal units. Each unit is 28 bits in length, including 8 check bits. Transmission is at a speed of 2400 bit/s for the analogue version and 4 kbit/s (optionally 56 kbit/s) for the digital version. + +Each signal unit within a block of 11 signal units is acknowledged and retransmitted in case of errors. + +The address information can be transmitted en bloc and in the overlap mode. Because the transmission speed of Signalling System No. 6 is considerably higher than that of channel-associated signalling systems, the influence of the mode of operation on the post-dialling delay is reduced substantially. + +The signal capacity (including the spare codes) of Signalling System No. 6 is much higher than that of Signalling Systems No. 4, No. 5, R1 and R2. + +Signalling System No. 6 contains signals for echo suppressor control as well as signals indicating whether a satellite link is already included in the connection. + +Signalling System No. 6 can be used for all types of telephone circuits including those with speech interpolation. + +Signalling System No. 6 can be used on satellite links. + +### 3.6 *Signalling System No. 7* + +Fully described and specified in Fascicles VI.7, VI.8 and VI.9. + +Suitable for both-way operation. + +Suitable for terminal and transit working. + +A common signalling link is used for signalling. + +Signalling System No. 7 can be used in national and international telecommunication networks. + +Signalling System No. 7 can be used for dedicated networks (e.g. data transmission, telephone) and within an integrated services digital network. It is the preferred signalling system between Integrated Digital Network (IDN) exchanges and within the Integrated Services Digital Network (ISDN). + +Signalling System No. 7 may be used in either an associated or quasi-associated mode of operation. Use in a quasi-associated mode may be more economical for small bundles of circuits. + +Variable length signal units with an integer number of octets are used of which 6 perform message transfer part functions. Signalling System No. 7 is optimized for a digital bearer with transmission speed of 64 kbit/s, but operation at lower speeds (e.g. 4.8 kbit/s) on analogue bearers is possible. + +Two error control methods (basic and preventive cyclic retransmission) are specified, each with its own field of application. In the basic method each signal unit is acknowledged and retransmitted in case of errors while in the preventive cyclic retransmission method no negative acknowledgements occur and error correction is performed by retransmission during idle periods of not yet acknowledged signal units. + +The address information can be transmitted en bloc and in the overlap mode. Because the transmission speed of Signalling System No. 7 is considerably higher than that of channel-associated signalling systems, the influence of the mode of operation on the post-dialling delay is reduced substantially. + +The signal capacity (including the spare codes) of Signalling System No. 7 is much higher than that of Signalling Systems No. 4, No. 5, R1 and R2. + +Signalling System No. 7 contains signals for echo suppressor control as well as signals indicating whether a satellite link is already included in the connection. + +Signalling System No. 7 can be used for all types of telephone circuits including those with speech interpolation. + +Signalling System No. 7 can be used on satellite links. + +## References + +- [1] CCITT Recommendation *Stability and echo*, Vol. III, Rec. G.131. +- [2] CCITT Recommendation *Echo cancellers*, Vol. III, Rec. G.165. +- [3] CCITT Recommendation *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s*, Vol. III, Rec. G.732. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4236be32ef37bed89595690800843c7afe9cee6c --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3e2d4dffd4a96b0e576709e251bffdc4c9a12b8c49e462e19ee4abae464e54 +size 60295 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2410449b2af0b5024579ee9041eee4b182ca3aad --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa5fafc33a0872c7b9201dc24a6003958ed0553a47014cbb97923939cb1bf2f6 +size 37067 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c66ac0185cbc13b48148ad1f0ce40c569b6b1ad4 --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:681b5b905b6b759cc383346c7653eee11434eba8468dc5e5d0147065a9fe3d96 +size 4033 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cc0e07494fadd31801bcb0b128b73174c63a615 --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37c1b3918245d1ae5f9e0535318a18cfda5fb03732a5fa4c2565dc18ab310d73 +size 24821 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/633fb609c4b7e841224c558b9db215bf_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/633fb609c4b7e841224c558b9db215bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8dbbb105d7dfebd862924b7076a6d2e26118e4d --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/633fb609c4b7e841224c558b9db215bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24ddc49e1e369ec3147f86f614134c0b41522b62bbe6de327e7af9901edfb98f +size 4550 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d35b5ae6dbfe8d697855590655e2fb6c7b1cd7bc --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:920285af147b058b21adc55f113083776521fe22de342d712900a4760c3fd301 +size 137636 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2aaa46401e34b1c4967abecabee9f675a70c333 --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc0867580643c02b723a18390ef796147bcc8699a3de088bdec1b6c3269390de +size 99883 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4b2bf17aee1fb3af4ff795d0e50b97af367dd9c --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3395f6ee473b7891162c9de81b6b986bfe51a2681482dc4c6fcaa450c1e8a33 +size 129742 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3dce4ba9cce504b04e14883e649ada40f9d43560 --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d581e6abe242e5cbd8615bba6992d218976665cf3ace1f48711cb64fecf7421 +size 126619 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c2f52e410ca3ff9217759f663b3e29bf12b764b --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad8b62c6ce8b596f65638f1bbe8af07644655a016fb9429063f7e28820c605c2 +size 25339 diff --git a/marked/Q/T-REC-Q.71-199303-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/marked/Q/T-REC-Q.71-199303-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4ad3d7e7fdac03f932e4598e25b5e03f6aff64f --- /dev/null +++ b/marked/Q/T-REC-Q.71-199303-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7366e773b24c5745bf723171d0ee50ce7829c07750a1dfcf376cebf4da464ff2 +size 25921 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a1297307812dee32f84d966450a83dd194847b9 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef0e1513c0ac611589fd22edddddab1c93d8f821a3d22c166324af5ae41c5e00 +size 79964 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff54dca9d187207412dcbc585affc1603a9f7c6 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf109d4c6ad0c35bc96068fb9279d744ac784b4cd75186254bda98f3bfb5c9f1 +size 37160 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc5c653033eae4ad281c327e8af4574f3dd5312 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a10febfd8f1e8bf419855cd4cab5cb51eab7ae2ef9768e19e3c9e2322edad46 +size 8325 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba784bd80afccb471a86c8fa82d9a17cdacd9835 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:834c808e6455c2cd8a0e2050628bea30b995adbe18c1649161b3b8e4759446d4 +size 44011 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9669400140e257d0f523b441dbf93a4406f4d4a --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96f5dd85d416b5e022c7f15e26459f04ab92a0607485155d400a211494bfac79 +size 24519 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46b6ea35ed969cda7e071d294cd460a8a0bb9159 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faff3ed2cc3207c92dc27d65c872694f038e46ed8dd7dc400c73abf64f5ad81d +size 53954 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f225625ebe1aced027abcbe3898abd64b2e09217 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cc7f3e0e18123ec3b1ebb7dd1ddcdcc39f51e840772e6c82d267a3e3e3a6101 +size 81567 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db032cef1c2addc01e5b855dd8631ee197699ce9 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1813b976d07b8c7744f5da45cc75be4cb366f9c9c6919635419da73b6a4cf86c +size 28871 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a727940023d2cca0d2a4ddf515effd142bcc10d --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:344a63bde273bb9a0636fcb6fbe3a20461d18f2c7ece388259cd3100295cecae +size 41812 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3b386a66025853e13ef0d09ff880521821b21ec --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fc13b6e868868e5e083c7a38e47622aaf13b70ea370425d1e099d2035233e18 +size 35627 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7368adcb682f3831df33117ad81e4a26f3e451f6 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95653042d29169eb515215a843528f95f2f04919053f242a57f07e75e792a199 +size 53883 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e78335fba09145e9fa801e942daa00364859d677 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29af08d94551f0ed62ada79793171c25b8a35c3472594457faa2160ad480888e +size 25254 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8a392b3b9c770ccea61879e493216ee5ab535a7 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56b3f6730e87e60bf7e200245166ae4263cecea4b0fd761d2f3382c447cae875 +size 39609 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62616313fdf43d1f0d3ea193f5464f5b7984e4c6 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ee8a17ce883be33c86cdfd5bf9b1f598f6cdf7830498bee1832f52f1b8c0684 +size 24434 diff --git a/marked/Q/T-REC-Q.730-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.730-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f706a6162b4d181201b2b25d000a7434b7d4fe7 --- /dev/null +++ b/marked/Q/T-REC-Q.730-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5c2eab34da683dbde617528b5c80b81077501d50a7297fe48a381048d663673 +size 44525 diff --git a/marked/Q/T-REC-Q.731.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.731.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a16c16debfc5530f59783e0b541498a448580678 --- /dev/null +++ b/marked/Q/T-REC-Q.731.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bc676c4500f11cc4624aff43b5f196e679f5cfaeb34bb963cab097ee62ca660 +size 8267 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77132a9b12752b5704e73ffe58242e4eaafbf797 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2796c8540e7ba32a4aceb37a8c083823c57307d5f5fb5c75fa1d90b5e5158c9 +size 52577 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef217a35c606f996aec24fcc6d998d1acd256f8 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:247ac7e691d9b397de6c25536f4e75ec7745dc147c743ea9971188d8020f638a +size 8239 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c61a9b09333608f78b60b1d176c454fb781f879 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b5dc42dee0653de2485e9f4d606cd637e9f8b9c25d63ed57080ed4d2dfd8943 +size 47281 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b9fcb0dc5cdb814ffb83056e5b076c4616ea22b --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:548daf045f9ad5aaf35efefd6b86168e38bb4f13491c81df847d8c578fa9faea +size 51168 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f12b834de5607c433e8ff8ded1a2d4ab3fcf8f1 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6565df3e3baf63c992c81517abaea8fbbe42a62194946fc9b4dbc423719cbf9e +size 51478 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79cb11d2b049d4b4e4946348d90642ae0392ed3e --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d2db87b48e70856eed7de6b33603de00a0b2c009ea2f3ddd620fbc54222fedb +size 45718 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28a1924476e332fea77ed43de006a1c977d2fb49 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16367d8a0f237e03fdca43757d23cc0cf91e7c0793c1a9a01052b7829e4dba17 +size 54055 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..527ba972b19cb97cc1a38bbe5f498b049d639a53 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a3ed8c3d4c18ce8f9cd4c4e3fd0cde65e63039936658352a429c41e35af370b +size 58081 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a76c2a0e7a98535233c8fb66a5f572681e110d0 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97ab5fde96c9649b90ff48d53401fcfe3a64f6fb59afd86335872ab7bf25432e +size 72680 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6828c2d04370a7e95f805698c6a9b4ee647bb052 --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4d170c11dd914edc765dbcac8d4a24d05c08bb97044ed013a7a17281162d6b6 +size 55150 diff --git a/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a8885d8ae197b6c2b1839bf4f9aa2f8417d21d1f --- /dev/null +++ b/marked/Q/T-REC-Q.734.2-199607-I_PDF-E/raw.md @@ -0,0 +1,729 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.734.2** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/96) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – ISDN +supplementary services + +--- + +**Stage 3 description for multiparty +supplementary services using Signalling +System No. 7: Three-party service** + +ITU-T Recommendation Q.734.2 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATION OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part | Q.701–Q.709 | +| Signalling connection control part | Q.711–Q.719 | +| Telephone user part | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **ITU-T RECOMMENDATION Q.734.2** + +# **STAGE 3 DESCRIPTION FOR MULTIPARTY SUPPLEMENTARY SERVICES USING SIGNALLING SYSTEM NO. 7: THREE-PARTY SERVICE** + +## **Summary** + +This Recommendation defines the essential functions, procedures and messages required for the transportation of information relating to the three-party supplementary service. This Recommendation has been updated due to a need for alignment with the revised specification of this supplementary service within DSS 1. + +### **Source** + +ITU-T Recommendation Q.734.2 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | | Page | +|--------|-----------------------------------------------------------------------|------| +| 2 | Three-Party Service..... | 1 | +| 2.1 | Introduction..... | 1 | +| 2.1.1 | Scope ..... | 1 | +| 2.1.2 | References..... | 1 | +| 2.1.3 | Terms and definitions ..... | 2 | +| 2.1.4 | Abbreviations..... | 2 | +| 2.2 | Description..... | 2 | +| 2.2.1 | General description..... | 2 | +| 2.2.2 | Specific terminology..... | 3 | +| 2.2.3 | Qualification on the applicability to telecommunication services..... | 3 | +| 2.2.4 | State definitions ..... | 3 | +| 2.3 | Operational requirements..... | 3 | +| 2.3.1 | Provision/withdrawal..... | 3 | +| 2.3.2 | Requirements on the originating network side..... | 3 | +| 2.3.3 | Requirements in the network..... | 3 | +| 2.3.4 | Requirements at the destination network side ..... | 3 | +| 2.4 | Coding requirements..... | 3 | +| 2.5 | Signalling requirements ..... | 4 | +| 2.5.1 | Activation/deactivation/registration ..... | 4 | +| 2.5.2 | Invocation and operation ..... | 4 | +| 2.6 | Interactions with other supplementary services..... | 7 | +| 2.6.1 | Call Waiting (CW)..... | 7 | +| 2.6.2 | Explicit Call Transfer (ECT) ..... | 8 | +| 2.6.3 | Connected line identification presentation (COLP) ..... | 8 | +| 2.6.4 | Connected line identification restriction (COLR) ..... | 8 | +| 2.6.5 | Calling Line Identification Presentation (CLIP)..... | 8 | +| 2.6.6 | Calling Line Identification Restriction (CLIR)..... | 8 | +| 2.6.7 | Closed User Group (CUG) ..... | 8 | +| 2.6.8 | Conference calling (CONF)..... | 8 | +| 2.6.9 | Direct-Dialling-In (DDI)..... | 8 | +| 2.6.10 | Diversion services..... | 8 | +| 2.6.11 | Line Hunting (LH)..... | 8 | +| 2.6.12 | Three-Party Service (3PTY)..... | 8 | +| 2.6.13 | User-to-User Signalling (UUS) ..... | 9 | +| 2.6.14 | Multiple Subscriber Number (MSN)..... | 9 | +| 2.6.15 | Call hold (HOLD)..... | 9 | +| 2.6.16 | Advice of Charge (AOC)..... | 9 | + +| | Page | +|-----------------------------------------------------------|-------------| +| 2.6.17 Sub-addressing (SUB) ..... | 9 | +| 2.6.18 Terminal Portability (TP) ..... | 9 | +| 2.6.19 Completion of Calls to Busy Subscriber (CCBS)..... | 9 | +| 2.6.20 Malicious Call Identification (MCID)..... | 9 | +| 2.6.21 Reverse charging (REV)..... | 9 | +| 2.6.22 Multi-Level Precedence and Preemption (MLPP)..... | 9 | +| 2.6.23 Support of Private Numbering Plan (SPNP) ..... | 9 | +| 2.6.24 International telecommunication charge card..... | 9 | +| 2.7 Interactions with other networks..... | 10 | +| 2.8 Signalling flows ..... | 10 | +| 2.9 Parameter values (timers) ..... | 14 | +| 2.10 Dynamic description ..... | 14 | + +# **STAGE 3 DESCRIPTION FOR MULTIPARTY SUPPLEMENTARY SERVICES USING SIGNALLING SYSTEM NO. 7: THREE-PARTY SERVICE** + +*(Geneva, 1996)* + +# **2 Three-Party Service** + +## **2.1 Introduction** + +### **2.1.1 Scope** + +This Recommendation describes the stage 3 of the three-party supplementary service for the Integrated Services Digital Network (ISDN) by means of the Signalling System No. 7 ISDN User Part (ISUP). + +The three-party (3PTY) supplementary service enables a user to establish a three-way conversation, i.e. a simultaneous communication between the served user and two other users. + +The 3PTY supplementary service is applicable to all circuit-switched telecommunication services carrying speech. + +### **2.1.2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation Q.730 (1993), *ISDN supplementary services*. +- [2] ITU-T Recommendation Q.761 (1993), *Functional description of the ISDN user part of Signalling System No. 7*. +- [3] ITU-T Recommendation Q.762 (1993), *General function of messages and signals of the ISDN user part of Signalling System No. 7*. +- [4] ITU-T Recommendation Q.763 (1993), *Formats and codes of the ISDN user part of Signalling System No. 7*. +- [5] ITU-T Recommendation Q.764 (1993), *ISDN user part signalling procedures*. +- [6] CCITT Recommendation I.254.2 (1992), *Three-Party supplementary service*. +- [7] ITU-T Recommendation Q.84.2 (1995), *Stage 2 description for multiparty supplementary services: Three-Party service*. +- [8] ITU-T Recommendation Q.954.2 (1995), *Stage 3 description for multiparty supplementary services using DSS 1: Three-Party service*. +- [9] ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs*. +- [10] ITU-T Recommendation I.210 (1993), *Principles of telecommunication services supported by an ISDN and the means to describe them*. + +### 2.1.3 Terms and definitions + +This Recommendation defines the following terms. + +**2.1.3.1 served user (user A):** The user who has the service under his control during the invocation and the active phase. + +**2.1.3.2 remote users (user B and user C):** The users involved in the two calls that are joined together into a three-way conversation. + +**2.1.3.3 integrated services digital network (ISDN):** See 2.3/I.112 [9], definition 308. + +**2.1.3.4 private communication:** Communication between the served user and one remote user. This excludes communication with the other remote user. + +**2.1.3.5 service; telecommunications service:** See 2.2/I.112 [9], definition 201. + +**2.1.3.6 supplementary service:** See 2.4/I.210 [10]. + +**2.1.3.7 three-way conversation:** Communication between all three users, i.e. the served user and both remote users. + +### 2.1.4 Abbreviations + +This Recommendation uses the following abbreviations. + +| | | +|----------|--------------------------------------------| +| 3PTY | Three-Party Service | +| CPG | Call Progress Message | +| DSS 1 | Digital Subscriber Signalling System No. 1 | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN Signalling User Part | +| SS No. 7 | Signalling System No. 7 | + +## 2.2 Description + +### 2.2.1 General description + +The served user, which has two calls can join the two calls, to form a three-way conversation. + +NOTE – Each call, to be involved in the 3PTY supplementary service, can have been originated by either the served user, or by the appropriate remote user. + +During the three-way conversation, the served user can request that the network: + +- explicitly disconnects one of the remote users, and the connection to that remote user; +- terminates the three-way conversation; +- creates a private communication with one of the remote users; or +- in conjunction with the call hold supplementary service, place its connection to the three-way conversation on hold. + +Either of the remote users (user B or user C) can request that the network disconnects the connection. + +Remote users are notified of these actions. + +The stage 1 ITU-T definitions for the 3PTY supplementary service is given in Recommendation I.254.2 [6]. The stage 2 ITU-T description is given in Recommendation Q.84.2 [7]. The stage 3 DSS 1 ITU-T description is given in Recommendation Q.954.2 [8]. This stage 3 description of the 3PTY supplementary service uses the ISDN User Part protocol as defined in Recommendations Q.761 [2], Q.762 [3], Q.763 [4], Q.764 [5] and Q.730 [1]. + +### 2.2.2 Specific terminology + +See 2.1.3. + +### 2.2.3 Qualification on the applicability to telecommunication services + +See 2.1.1. + +### 2.2.4 State definitions + +No specific states are required. + +## 2.3 Operational requirements + +### 2.3.1 Provision/withdrawal + +See Recommendation I.254.2 [6]. + +### 2.3.2 Requirements on the originating network side + +This subclause is not applicable to SS No. 7. + +### 2.3.3 Requirements in the network + +No specific requirements are needed in the network. + +### 2.3.4 Requirements at the destination network side + +This subclause is not applicable to SS No. 7. + +## 2.4 Coding requirements + +For the 3PTY supplementary service, the call progress message, containing the generic notification indicator parameter, shall be used to send the appropriate notification towards the remote user. + +The generic notification indicator is accompanied by the parameter compatibility information parameter. The procedures for compatibility are defined in 2.9.5/Q.764 [5]. + +The event indicator is set to "Progress". + +The following notification descriptions are used: + +- conference established; +- conference disconnected; +- remote hold. + +The generic notification indicator parameter field shall be coded as shown below See Table 2-1. + +**Table 2-1/Q.734.2 – Coding of the generic notification indicator parameter** + +| Bits | | | | | | | Description | +|------|---|---|---|---|---|---|-------------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 1 | 0 | 0 | 0 | 0 | 1 | 0 | Conference established | +| 1 | 0 | 0 | 0 | 0 | 1 | 1 | Conference disconnected | +| 1 | 1 | 1 | 1 | 0 | 0 | 1 | Remote hold | + +## **2.5 Signalling requirements** + +### **2.5.1 Activation/deactivation/registration** + +This subclause is not applicable to SS No. 7. + +### **2.5.2 Invocation and operation** + +#### **2.5.2.1 Actions at the originating local exchange** + +The originating local exchange is the exchange where the service is controlled. The originating local exchange for this description is not necessarily the originating exchange for the basic call. + +##### **2.5.2.1.1 Normal operation** + +###### **2.5.2.1.1.1 Requirements related to echo control** + +###### **a) *General*** + +When the conference bridge is located in the originating local exchange, this exchange shall have the capability to invoke echo-control procedures. This is necessary in the case the total propagation delay for the two legs of the three-way conversation is above the value for which echo control is necessary. (Reference: 2.6/Q.764 [5].) + +The exchange shall also have the capability of storing propagation delay information received either in a received Initial Address message (for incoming calls) or in an Answer/Connect message (for outgoing calls) until call release. This shall be done for both legs included in the three-way conversation. + +###### **b) *Criteria to initiate echo control procedures*** + +The originating local exchange has to sum up the propagation delay values of the calls A-B and A-C in order to determine the total value of propagation delay of the three-way conversation. + +If echo control is necessary, the exchange shall initiate echo control procedures for each of the legs concerned. (Reference: 2.7/Q.764 [5].) + +###### **2.5.2.1.1.2 Beginning the three-way conversation** + +Prior to the invocation of the 3PTY supplementary service, the served user (user A) shall be involved in two calls, both in the answered state: one call (e.g. with user B) in a held state and the other one (e.g. with user C) in an active state. + +When the 3PTY supplementary service is invoked the originating exchange, to which the served user's equipment is connected, shall: + +- a) join the two calls together into a three-way conversation; +- b) on request of the access protocol (see 2.9.2.1.1/Q.954) send a call progress message to each remote user, containing the generic notification indicator parameter with the notification "conference established". + +NOTE 1 – See Figure 2-1 and also Figure 2-I.1/Q.954. + +NOTE 2 – For an interim period of time, some networks may not support the sending of notifications to the remote users. + +NOTE 3 – Procedure a) does not have any impact on ISUP protocol. + +###### 2.5.2.1.1.3 Managing the three-way conversation + +During the three-way conversation mode, the served user shall be able to: + +- a) Create a private communication with a remote user. + +There are two possible cases which are identified dependent on the local DSS 1 network entity: + +**Case 1** – Creating a private communication with the user who has been in the held state prior to establishment of the three-way conversation (see also Note 3). + +On request of the access protocol [see 2.9.2.4.1 a)/Q.954], the local exchange shall send the following messages to the remote users: + +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Remote Hold". +- A call progress message to the user who has been in the active state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". +- A call progress message to the user who has been in the active state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Remote Hold". +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". + +NOTE 1 – See Figure 2-6 and also Figure 2-I.6/Q.954. + +**Case 2** – Creating a private communication with the user who has been in the active state prior to establishment of the three-way conversation (see also Note 3). + +On request of the access protocol [see 1.9.2.4.1 b)/Q.954], the local exchange shall send the following messages to the remote users: + +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Remote Hold". +- A call progress message to the user who has been in the active state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". + +NOTE 2 – See Figure 2-7 and also Figure 2-I.7/Q.954. + +NOTE 3 – If the three-way conversation is held and retrieved using the call hold supplementary service, then the DSS 1 states which existed for the initiation of the three-way conversation may be different to those that exist at the time of the request for creation of a private communication. The current DSS 1 states specify which case applies. + +- b) Disconnect one remote user and retain the other. + +There are two possible cases which are identified dependent on the local DSS 1 network entity: + +**Case 1** – Disconnection of the user who has been in the held state prior to establishment of the three-way conversation (see also Note 6). + +On request of the access protocol (see 2.9.2.2.1/Q.954), the local exchange shall send the following messages to the remote users: + +- A call progress message to the user who has been in the active state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". + +NOTE 4 – See Figure 2-2 and also Figure 2-I.2/Q.954. + +**Case 2** – Disconnection of the user who has been in the active state prior to establishment of the three-way conversation (see also Note 6). + +On request of the access protocol [see 2.9.2.2.1 b)/Q.954], the local exchange shall send the following messages to the remote users: + +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Remote Hold". +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". + +NOTE 5 – See Figure 2-3 and also Figure 2-I.3/Q.954. + +NOTE 6 – If the three-way conversation is held and retrieved using the call hold supplementary service, then the DSS 1 states which existed for the initiation of the three-way conversation may be different to those that exist at the time of the request for disconnection of one remote party. The current DSS 1 states specify which case applies. + +- c) Disconnect both remote users and terminate the call. + +There are two possible cases which are identified dependent on the local DSS 1 network entity: + +**Case 1** – Disconnection of both remote users, the user who has been in the held state prior to establishment of the three-way conversation released first (see also Note 9). + +On request of the access protocol (see 2.9.2.3.1/Q.954), the local exchange shall send the following messages to the remote users: + +- A call progress message to the user who has been in the active state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Conference Disconnected". + +NOTE 7 – See Figure 2-4 and also Figure 2-I.4/Q.954. + +**Case 2** – Disconnection of both remote users, the user who has been in the active state prior to establishment of the three-way conversation released first (see also Note 9). + +On request of the access protocol (see 2.9.2.3.1/Q.954), the local exchange shall send the following messages to the remote users: + +- A call progress message to the user who has been in the held state prior to establishment of the three-way conversation containing the generic notification indicator parameter with the notification "Remote Hold". + +NOTE 8 – See Figure 2-5 and also Figure 2-I.5/Q.954. + +NOTE 9 – If the three-way conversation is held and retrieved using the call hold supplementary service, then the DSS 1 states which existed for the initiation of the three-way conversation may be different to those that exist at the time of the request for disconnection of one remote party. The current DSS 1 states specify which case applies. + +##### **2.5.2.1.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **2.5.2.2 Actions at the transit exchange** + +##### **2.5.2.2.1 Normal operation** + +The exchange shall transfer transparently the messages related to the notification mechanism. + +See also 2.5.2.1.1.1. + +##### **2.5.2.2.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **2.5.2.3 Actions at the outgoing international gateway exchange** + +##### **2.5.2.3.1 Normal operation** + +The exchange shall transfer transparently the messages related to the notification mechanism. + +See also 2.5.2.1.1.1. + +##### **2.5.2.3.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **2.5.2.4 Actions at the incoming international gateway exchange** + +##### **2.5.2.4.1 Normal operation** + +The exchange shall transfer the messages related to the notification mechanism. + +See also 2.5.2.1.1.1. + +##### **2.5.2.4.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **2.5.2.5 Actions at the destination local exchange** + +The destination local exchange for this description is not necessarily the destination exchange for the basic call. + +##### **2.5.2.5.1 Normal operation** + +The information contained in the call progress message related to the notification mechanism received by the destination local exchange shall be passed along to the access signalling system. + +See also 2.5.2.1.1.1. + +##### **2.5.2.5.2 Exceptional procedures** + +No exceptional procedures are identified. + +## **2.6 Interactions with other supplementary services** + +### **2.6.1 Call Waiting (CW)** + +No impact on ISUP. + +### **2.6.2 Explicit Call Transfer (ECT)** + +No applicable interaction at this time. + +### **2.6.3 Connected line identification presentation (COLP)** + +No impact on ISUP. + +### **2.6.4 Connected line identification restriction (COLR)** + +No impact on ISUP. + +### **2.6.5 Calling Line Identification Presentation (CLIP)** + +No impact on ISUP. + +### **2.6.6 Calling Line Identification Restriction (CLIR)** + +No impact on ISUP. + +### **2.6.7 Closed User Group (CUG)** + +For the successful invocation of the 3PTY supplementary service, any closed user group restrictions normally applied to individual closed user group calls between users A-B, or A-C shall still apply when the 3PTY supplementary service is invoked, i.e. the closed user group check procedure is only performed on each individual leg of the call. + +NOTE – Closed user group restrictions cannot be guaranteed between users B and C. + +### **2.6.8 Conference calling (CONF)** + +No impact on ISUP. + +### **2.6.9 Direct-Dialling-In (DDI)** + +No impact on ISUP. + +### **2.6.10 Diversion services** + +#### **2.6.10.1 Call Forwarding Busy (CFB)** + +No impact on ISUP. + +#### **2.6.10.2 Call Forwarding no Reply (CFNR)** + +No impact on ISUP. + +#### **2.6.10.3 Call Forwarding Unconditional (CFU)** + +No impact on ISUP. + +#### **2.6.10.4 Call Deflection (CD)** + +No impact on ISUP. + +### **2.6.11 Line Hunting (LH)** + +No impact on ISUP. + +### **2.6.12 Three-Party Service (3PTY)** + +Not applicable. + +### **2.6.13 User-to-User Signalling (UUS)** + +#### **2.6.13.1 Service 1** + +No impact on ISUP. + +#### **2.6.13.2 Service 2** + +No impact on ISUP. + +#### **2.6.13.3 Service 3** + +No impact on ISUP. + +### **2.6.14 Multiple Subscriber Number (MSN)** + +No impact on ISUP. + +### **2.6.15 Call hold (HOLD)** + +In case of a hold request sent by a served user during the three-way conversation active phase, no notifications shall be sent toward the remote users. + +### **2.6.16 Advice of Charge (AOC)** + +No impact on ISUP. + +### **2.6.17 Sub-addressing (SUB)** + +No impact on ISUP. + +### **2.6.18 Terminal Portability (TP)** + +No impact on ISUP. + +### **2.6.19 Completion of Calls to Busy Subscriber (CCBS)** + +No applicable interaction at this time. + +### **2.6.20 Malicious Call Identification (MCID)** + +No impact on ISUP. + +### **2.6.21 Reverse charging (REV)** + +No applicable interaction at this time. + +### **2.6.22 Multi-Level Precedence and Preemption (MLPP)** + +No impact on ISUP. + +### **2.6.23 Support of Private Numbering Plan (SPNP)** + +No applicable interaction at this time. + +### **2.6.24 International telecommunication charge card** + +No applicable interaction at this time. + +## 2.7 Interactions with other networks + +In case of interactions with networks which do not provide the notification procedure, the interaction exchange shall discard the call progress message. However, the three-way conversation will be completed according to the proper basic call procedures as described in Recommendation Q.764 [5]. + +## 2.8 Signalling flows + +Information flows for the 3PTY supplementary service are shown in Figures 2-1 through 2-9. + +![Sequence diagram for Figure 2-1/Q.734.2 – Request for a three-way conversation. The diagram shows the interaction between User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The process starts with User A sending a Facility (A-B) message to Originating Exchange (A). Originating Exchange (A) responds with Facility (A-B) and then sends a CPG (Conf. establ.) message to Transit Exchange. Transit Exchange forwards the CPG (Conf. establ.) message to Destination Exchange (B). Destination Exchange (B) sends a Notify message to User B. Finally, Originating Exchange (A) sends a CPG (Conf. establ.) message to Destination Exchange (C), which in turn sends a Notify message to User C. The state 'Calls A-B held and A-C active' is indicated at the top of the diagram. The reference T1175030-95 is shown at the bottom right.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +T1175030-95 + +Sequence diagram for Figure 2-1/Q.734.2 – Request for a three-way conversation. The diagram shows the interaction between User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The process starts with User A sending a Facility (A-B) message to Originating Exchange (A). Originating Exchange (A) responds with Facility (A-B) and then sends a CPG (Conf. establ.) message to Transit Exchange. Transit Exchange forwards the CPG (Conf. establ.) message to Destination Exchange (B). Destination Exchange (B) sends a Notify message to User B. Finally, Originating Exchange (A) sends a CPG (Conf. establ.) message to Destination Exchange (C), which in turn sends a Notify message to User C. The state 'Calls A-B held and A-C active' is indicated at the top of the diagram. The reference T1175030-95 is shown at the bottom right. + +Figure 2-1/Q.734.2 – Request for a three-way conversation + +![Sequence diagram for Figure 2-2/Q.734.2 – Disconnection of user B. The diagram shows the interaction between User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The process starts with User A sending a Disconnect (A-B) message to Originating Exchange (A). Originating Exchange (A) sends a CPG (Conf. disc.) message to Transit Exchange. Transit Exchange sends a 'Call A-B released' message to Destination Exchange (B). Destination Exchange (B) sends a CPG (Conf. disc.) message to Destination Exchange (C), which in turn sends a Notify message to User C. The state 'Calls A-B held and A-C active (Note)' is indicated at the top of the diagram. The reference T1175040-95 is shown at the bottom right.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +T1175040-95 + +Sequence diagram for Figure 2-2/Q.734.2 – Disconnection of user B. The diagram shows the interaction between User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The process starts with User A sending a Disconnect (A-B) message to Originating Exchange (A). Originating Exchange (A) sends a CPG (Conf. disc.) message to Transit Exchange. Transit Exchange sends a 'Call A-B released' message to Destination Exchange (B). Destination Exchange (B) sends a CPG (Conf. disc.) message to Destination Exchange (C), which in turn sends a Notify message to User C. The state 'Calls A-B held and A-C active (Note)' is indicated at the top of the diagram. The reference T1175040-95 is shown at the bottom right. + +Figure 2-2/Q.734.2 – Disconnection of user B + +NOTE – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +![Sequence diagram for disconnection of user C. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence shows User A sending a Disconnect (A-C) to Originating Exchange (A), which results in 'Calls A-B held and A-C active (Note)' and 'Call A-C released' in the Transit Exchange. Originating Exchange (A) sends CPG (Rem. hold) to Transit Exchange, which then sends Notify to User B. User A then sends a Retrieve (A-B) to Originating Exchange (A), resulting in 'Call A-B released' in the Transit Exchange. Originating Exchange (A) sends CPG (Conf. disc.) to Transit Exchange, which then sends Notify to User B.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +T1175050-95 + +Sequence diagram for disconnection of user C. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence shows User A sending a Disconnect (A-C) to Originating Exchange (A), which results in 'Calls A-B held and A-C active (Note)' and 'Call A-C released' in the Transit Exchange. Originating Exchange (A) sends CPG (Rem. hold) to Transit Exchange, which then sends Notify to User B. User A then sends a Retrieve (A-B) to Originating Exchange (A), resulting in 'Call A-B released' in the Transit Exchange. Originating Exchange (A) sends CPG (Conf. disc.) to Transit Exchange, which then sends Notify to User B. + +NOTE – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-3/Q.734.2 – Disconnection of user C** + +![Sequence diagram for disconnection of both remote users, user B released first. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence shows User A sending a Disconnect (A-B) to Originating Exchange (A), resulting in 'Calls A-B held and A-C active (Note 3)' and 'Call A-B released (Note 1)' in the Transit Exchange. Originating Exchange (A) sends CPG (Conf. disc.) to Transit Exchange, which then sends Notify to User C. User A then sends a Disconnect (A-C) to Originating Exchange (A), resulting in 'Call A-C released (Note 2)' in the Transit Exchange.](8307f6b04df072c9332f9987e034272c_img.jpg) + +T1175060-95 + +Sequence diagram for disconnection of both remote users, user B released first. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence shows User A sending a Disconnect (A-B) to Originating Exchange (A), resulting in 'Calls A-B held and A-C active (Note 3)' and 'Call A-B released (Note 1)' in the Transit Exchange. Originating Exchange (A) sends CPG (Conf. disc.) to Transit Exchange, which then sends Notify to User C. User A then sends a Disconnect (A-C) to Originating Exchange (A), resulting in 'Call A-C released (Note 2)' in the Transit Exchange. + +NOTE 1 – The call between user A and user B is released by the served user according to the "Disconnection of user B" procedure (see Figure 2-2). + +NOTE 2 – The call between user A and user C is released by the served user according to the basic call procedures. + +NOTE 3 – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-4/Q.734.2 – Disconnection of both remote users, user B released first** + +![Sequence diagram for Figure 2-5/Q.734.2 showing the disconnection of two remote users, with user C released first. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence starts with User A sending a Disconnect (A-C) to Originating Exchange (A). The Transit Exchange notes 'Calls A-B held and A-C active (Note 3)'. The Originating Exchange sends a CPG (Rem. hold) to the Transit Exchange, which then sends a Notify to Destination Exchange (B). User A then sends a Disconnect (A-B) to Originating Exchange (A). The Transit Exchange notes 'Call A-B released (Note 2)'. The call between User A and User C is released (Note 1). The diagram ends with T1175070-95.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Sequence diagram for Figure 2-5/Q.734.2 showing the disconnection of two remote users, with user C released first. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence starts with User A sending a Disconnect (A-C) to Originating Exchange (A). The Transit Exchange notes 'Calls A-B held and A-C active (Note 3)'. The Originating Exchange sends a CPG (Rem. hold) to the Transit Exchange, which then sends a Notify to Destination Exchange (B). User A then sends a Disconnect (A-B) to Originating Exchange (A). The Transit Exchange notes 'Call A-B released (Note 2)'. The call between User A and User C is released (Note 1). The diagram ends with T1175070-95. + +NOTE 1 – The call between user A and user C is released by the served user according to the "Disconnection of user C" procedure (see Figure 2-3). + +NOTE 2 – The call between user A and user B is released by the served user according to the basic call procedures. + +NOTE 3 – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-5/Q.734.2 – Disconnection of both remote users, user C released first** + +![Sequence diagram for Figure 2-6/Q.734.2 showing the creation of a private communication with user B. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence starts with User A sending a Facility (A-B) to Originating Exchange (A), which responds with Facility (A-B). The Transit Exchange notes 'Calls A-B held and A-C active (Note)'. The Originating Exchange sends a CPG (Rem. hold) to the Transit Exchange, which then sends a Notify to Destination Exchange (B). User A sends a Hold (A-C) to Originating Exchange (A), which responds with (Conf. disc). The Originating Exchange sends a CPG (Rem. hold) to the Transit Exchange, which then sends a Notify to Destination Exchange (C). User A sends a Retrieve (A-B) to Originating Exchange (A), which responds with (Conf. disc). The Originating Exchange sends a CPG to the Transit Exchange, which then sends a Notify to Destination Exchange (B). The diagram ends with T1175080-95.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Sequence diagram for Figure 2-6/Q.734.2 showing the creation of a private communication with user B. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence starts with User A sending a Facility (A-B) to Originating Exchange (A), which responds with Facility (A-B). The Transit Exchange notes 'Calls A-B held and A-C active (Note)'. The Originating Exchange sends a CPG (Rem. hold) to the Transit Exchange, which then sends a Notify to Destination Exchange (B). User A sends a Hold (A-C) to Originating Exchange (A), which responds with (Conf. disc). The Originating Exchange sends a CPG (Rem. hold) to the Transit Exchange, which then sends a Notify to Destination Exchange (C). User A sends a Retrieve (A-B) to Originating Exchange (A), which responds with (Conf. disc). The Originating Exchange sends a CPG to the Transit Exchange, which then sends a Notify to Destination Exchange (B). The diagram ends with T1175080-95. + +NOTE – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-6/Q.734.2 – Creating a private communication with user B** + +![Sequence diagram for Figure 2-7/Q.734.2 – Creating a private communication with user C. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence shows User A sending Facility (A-C) to Originating Exchange (A), which responds with Facility (A-C). Simultaneously, a note indicates 'Calls A-B held and A-C active (Note)'. Originating Exchange (A) sends CPG (Conf. disc) to Transit Exchange, which forwards it to Destination Exchange (B) and then to User B. Originating Exchange (A) also sends CPG (Rem. hold) to Transit Exchange, which forwards it to Destination Exchange (B) and then to User B. Finally, Originating Exchange (A) sends CPG (Conf. disc) to Transit Exchange, which forwards it to Destination Exchange (B) and then to User C. A 'Notify' message is sent from Destination Exchange (B) to User B. The diagram is labeled T1175090-95.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Sequence diagram for Figure 2-7/Q.734.2 – Creating a private communication with user C. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence shows User A sending Facility (A-C) to Originating Exchange (A), which responds with Facility (A-C). Simultaneously, a note indicates 'Calls A-B held and A-C active (Note)'. Originating Exchange (A) sends CPG (Conf. disc) to Transit Exchange, which forwards it to Destination Exchange (B) and then to User B. Originating Exchange (A) also sends CPG (Rem. hold) to Transit Exchange, which forwards it to Destination Exchange (B) and then to User B. Finally, Originating Exchange (A) sends CPG (Conf. disc) to Transit Exchange, which forwards it to Destination Exchange (B) and then to User C. A 'Notify' message is sent from Destination Exchange (B) to User B. The diagram is labeled T1175090-95. + +NOTE – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-7/Q.734.2 – Creating a private communication with user C** + +![Sequence diagram for Figure 2-8/Q.734.2 – User B disconnects. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence starts with a note 'Calls A-B held and A-C active (Note)'. A message 'Call A-B released' is sent from Transit Exchange to Destination Exchange (B). User A sends a Disconnect (A-B) message to Originating Exchange (A). Originating Exchange (A) sends CPG (Conf. disc.) to Transit Exchange, which forwards it to Destination Exchange (C) and then to User C. A 'Notify' message is sent from Destination Exchange (C) to User C. The diagram is labeled T1175100-95.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Sequence diagram for Figure 2-8/Q.734.2 – User B disconnects. Lifelines: User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), User C. The sequence starts with a note 'Calls A-B held and A-C active (Note)'. A message 'Call A-B released' is sent from Transit Exchange to Destination Exchange (B). User A sends a Disconnect (A-B) message to Originating Exchange (A). Originating Exchange (A) sends CPG (Conf. disc.) to Transit Exchange, which forwards it to Destination Exchange (C) and then to User C. A 'Notify' message is sent from Destination Exchange (C) to User C. The diagram is labeled T1175100-95. + +NOTE – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-8/Q.734.2 – User B disconnects** + +![Sequence diagram showing the interaction between User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The diagram illustrates the process of User C disconnecting from a three-party call. Key messages include 'Disconnect (A-C)' from User A to Originating Exchange (A), 'Retrieve' from User A to Originating Exchange (A), 'CPG (Rem. hold)' from Originating Exchange (A) to Transit Exchange, 'CPG (Rem. hold)' from Transit Exchange to Destination Exchange (B), 'Notify' from Destination Exchange (B) to User B, 'CPG (Conf. disc.)' from Originating Exchange (A) to Transit Exchange, 'CPG (Conf. disc.)' from Transit Exchange to Destination Exchange (B), and 'Notify' from Destination Exchange (B) to User B. A note indicates 'Calls A-B held and A-C active' and 'Call A-C released'.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates the sequence of events when User C disconnects from a three-party call. The participants are User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The sequence starts with User A sending a 'Disconnect (A-C)' message to Originating Exchange (A). User A then sends a 'Retrieve' message to Originating Exchange (A). Originating Exchange (A) sends a 'CPG (Rem. hold)' message to Transit Exchange, which in turn sends a 'CPG (Rem. hold)' message to Destination Exchange (B). Destination Exchange (B) sends a 'Notify' message to User B. A note indicates that at this point, 'Calls A-B held and A-C active'. User A then sends a 'Retrieve' message to Originating Exchange (A). Originating Exchange (A) sends a 'CPG (Conf. disc.)' message to Transit Exchange, which sends a 'CPG (Conf. disc.)' message to Destination Exchange (B). Destination Exchange (B) sends a 'Notify' message to User B. A note indicates that at this point, 'Call A-C released'. + +Sequence diagram showing the interaction between User A, Originating Exchange (A), Transit Exchange, Destination Exchange (B), User B, Destination Exchange (C), and User C. The diagram illustrates the process of User C disconnecting from a three-party call. Key messages include 'Disconnect (A-C)' from User A to Originating Exchange (A), 'Retrieve' from User A to Originating Exchange (A), 'CPG (Rem. hold)' from Originating Exchange (A) to Transit Exchange, 'CPG (Rem. hold)' from Transit Exchange to Destination Exchange (B), 'Notify' from Destination Exchange (B) to User B, 'CPG (Conf. disc.)' from Originating Exchange (A) to Transit Exchange, 'CPG (Conf. disc.)' from Transit Exchange to Destination Exchange (B), and 'Notify' from Destination Exchange (B) to User B. A note indicates 'Calls A-B held and A-C active' and 'Call A-C released'. + +NOTE – These states relate to the states of the calls before the invocation of the three-party supplementary service. + +**Figure 2-9/Q.734.2 – User C disconnects** + +## 2.9 Parameter values (timers) + +No specific timers are required. + +## 2.10 Dynamic description + +No dynamic description is required. + +# ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Telephone network and ISDN +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media +- Series H Transmission of non-telephone signals +- Series I Integrated services digital network +- Series J Transmission of sound-programme and television signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits +- Series N Maintenance: international sound-programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality +- Series Q Switching and signalling** +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminal equipments and protocols for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communication +- Series Z Programming languages \ No newline at end of file diff --git a/marked/Q/T-REC-Q.735.6-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.735.6-199607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dd65986f37b8786beb33f7fea6fc40370fe982f6 --- /dev/null +++ b/marked/Q/T-REC-Q.735.6-199607-I_PDF-E/raw.md @@ -0,0 +1,1005 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.735.6** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/96) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – ISDN +supplementary services + +--- + +**Stage 3 description for community of interest +supplementary services using Signalling +System No. 7: Global Virtual Network Service +(GVNS)** + +ITU-T Recommendation Q.735.6 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATION OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part | Q.701–Q.709 | +| Signalling connection control part | Q.711–Q.719 | +| Telephone user part | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +# **ITU-T RECOMMENDATION Q.735.6** + +# **STAGE 3 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES USING SIGNALLING SYSTEM No. 7: GLOBAL VIRTUAL NETWORK SERVICE (GVNS)** + +## **Summary** + +The global virtual network service is a global switched service supported by multiple networks and is offered to customers over PSTN and/or ISDN. While minimizing the need for dedicated network resources, GVNS provides private network functions to users at geographically dispersed international locations. + +### **Source** + +ITU-T Recommendation Q.735.6 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | | Page | +|--------|-----------------------------------------------------------------------|------| +| 6 | Global virtual network service..... | 1 | +| 6.1 | Introduction..... | 1 | +| 6.1.1 | Scope ..... | 1 | +| 6.1.2 | References..... | 1 | +| 6.1.3 | Terms and definitions ..... | 1 | +| 6.1.4 | Abbreviations..... | 2 | +| 6.2 | Description..... | 2 | +| 6.2.1 | General description..... | 2 | +| 6.2.2 | Specific terminology..... | 3 | +| 6.2.3 | Qualification on the applicability to telecommunication services..... | 3 | +| 6.2.4 | State definitions ..... | 3 | +| 6.3 | Operational requirements..... | 3 | +| 6.3.1 | Provision and withdrawal ..... | 3 | +| 6.3.2 | Requirements on the originating network side ..... | 3 | +| 6.3.3 | Requirements in the network ..... | 3 | +| 6.3.4 | Requirements on the terminating network side ..... | 3 | +| 6.4 | Coding requirements..... | 3 | +| 6.4.1 | Messages..... | 3 | +| 6.4.2 | Parameters ..... | 3 | +| 6.5 | Signalling procedures..... | 7 | +| 6.5.1 | Activation/deactivation/registration ..... | 7 | +| 6.5.2 | Invocation and operation ..... | 8 | +| 6.6 | Interactions with other supplementary services..... | 15 | +| 6.6.1 | Call Waiting (CW)..... | 15 | +| 6.6.2 | Call transfer services..... | 15 | +| 6.6.3 | Connected line identification presentation (COLP) ..... | 15 | +| 6.6.4 | Connected line identification restriction (COLR) ..... | 15 | +| 6.6.5 | Calling Line Identification Presentation (CLIP)..... | 15 | +| 6.6.6 | Calling Line Identification Restriction (CLIR)..... | 15 | +| 6.6.7 | Closed User Group (CUG) ..... | 15 | +| 6.6.8 | Conference calling (CONF)..... | 16 | +| 6.6.9 | Direct-Dialing-In (DDI)..... | 16 | +| 6.6.10 | Call diversion services (CDIV) ..... | 16 | +| 6.6.11 | Line Hunting (LH)..... | 16 | +| 6.6.12 | Three-Party service (3PTY)..... | 16 | +| 6.6.13 | User-to-User Signalling (UUS) ..... | 16 | +| 6.6.14 | Multiple Subscriber Number (MSN)..... | 16 | + +| | Page | +|----------------------------------------------------------------|-------------| +| 6.6.15 Call hold (HOLD)..... | 16 | +| 6.6.16 Advice of Charge (AOC)..... | 16 | +| 6.6.17 Sub-addressing (SUB) ..... | 16 | +| 6.6.18 Terminal Portability (TP) ..... | 17 | +| 6.6.19 Completion of Calls to Busy Subscriber (CCBS)..... | 17 | +| 6.6.20 Malicious Call Identification (MCID)..... | 17 | +| 6.6.21 Reverse charging (REV)..... | 17 | +| 6.6.22 Multi-Level Precedence and Preemption (MLPP)..... | 17 | +| 6.6.23 Private Numbering Plan (PNP)..... | 17 | +| 6.6.24 International Telecommunication Charge Card (ITCC)..... | 17 | +| 6.7 Interaction with other networks ..... | 17 | +| 6.8 Signalling flows ..... | 17 | +| 6.9 Parameter values (timers) ..... | 17 | +| 6.10 Dynamic description ..... | 17 | + +# **STAGE 3 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES USING SIGNALLING SYSTEM No. 7: GLOBAL VIRTUAL NETWORK SERVICE (GVNS)** + +*(Geneva, 1996)* + +# **6 Global virtual network service** + +## **6.1 Introduction** + +### **6.1.1 Scope** + +The Global Virtual Network Service (GVNS) is a multi-network international service which provides private network functions to users at geographically dispersed international locations while minimizing the need for dedicated network resources. It may be offered to customers over the PSTN or ISDN. + +### **6.1.2 References** + +The following ITU-T Recommendations, and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN.* +- [2] ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs.* +- [3] ITU-T Recommendation Q.71 (1993), *ISDN circuit mode switched bearer services.* +- [4] ITU-T Recommendation F.16 (1995), *Global virtual network service.* +- [5] ITU-T Recommendation Q.85.6 (1996), *Stage 2 description for community of interest supplementary services: Global Virtual Network Service (GVNS).* +- [6] CCITT Recommendation E.164 (1991), *Numbering plan for the ISDN era.* +- [7] ITU-T Recommendation Q.763 (1993), *Formats and codes of the ISDN User Part of Signalling System No. 7.* +- [8] ITU-T Recommendation Q.730 (1993), *ISDN supplementary services.* + +### **6.1.3 Terms and definitions** + +This Recommendation defines the following terms. + +**6.1.3.1 dialled number:** The number which a GVNS user dialled excluding prefix digits. + +NOTE – This information, if required by the terminating network, will be included in the terminating network routing number. + +**6.1.3.2 ISDN number:** A number conforming to the numbering plan and the structure specified in Recommendation E.164 [6]. + +**6.1.3.3 terminating access indication:** Information used to identify the type of access that the GVNS terminating participating service provider actually used to complete the call. + +**6.1.3.4 GVNS user group identification:** Information that uniquely identifies the GVNS customer. An example for the usage of such information is to locate the address of the database record of a GVNS customer. + +**6.1.3.5 originating participating service provider identification:** Information that uniquely identifies the participating service provider that provides customer access to GVNS to the calling user/interface. + +**6.1.3.6 routing number:** Information used to complete a call to the terminating functional entity. This information is mandatory and is carried by an ISDN number (fully conforming to Recommendation E.164). + +NOTE – Whenever adjacent GVNS functional entities are implemented by separate GVNS Participating Service Providers, the Routing Number shall be an ISDN number (fully conforming to Recommendation E.164) unless another prior arrangement exists between the participating service providers. + +**6.1.3.7 terminating network routing number:** Information used by the terminating functional entity to route calls. This information is mandatory and is carried by either an ISDN number (fully conforming to Recommendation E.164) or a network-specific number. + +**6.1.3.8 terminating participating service provider identification:** Information that uniquely identifies the participating service provider that provides customer access to GVNS to the called user/interface. + +NOTE – This information is included in the Routing Number. + +### **6.1.4 Abbreviations** + +This Recommendation uses the following abbreviations. + +ISDN Integrated Services Digital Network + +NDC National Destination Code + +OPSP Originating Participating Service Provider Identification + +PSTN Public Switched Telephone Network + +TPSP Terminating Participating Service Provider Identification + +## **6.2 Description** + +This clause is specific to Signalling System No. 7 protocol for the ISDN User Part. Stage 3 identifies the protocol procedures and switching functions needed to support a telecommunication service. + +This clause is limited to the type A and B call mechanisms as defined by the GVNS Stage 2 [5]. It does not fully support the type C call mechanism. + +### **6.2.1 General description** + +GVNS allows service providers to offer subscribing customers a service with the features and functionality similar to that of a private network while minimizing the need for dedicated network resources; however, dedicated network resources may be used to access GVNS or in conjunction with GVNS. A GVNS customer is assigned a unique identifier which identifies the GVNS user group. GVNS user group identification provides a means by which various networks can recognize + +the customer. A GVNS customer may choose to group users into one or more subgroups in order to allow subgroup dependent service interactions and operations. + +The Stage 1 ITU-T definitions for the GVNS service are given in Recommendation F.16. + +The Stage 2 ITU-T descriptions are given in Recommendation Q.85.6. + +The Stage 3 description of GVNS service uses the ISDN user part protocol as defined in Recommendations Q.761-764. + +### **6.2.2 Specific terminology** + +See 6.1.3 terms and definitions. + +### **6.2.3 Qualification on the applicability to telecommunication services** + +This service is applicable to circuit mode bearer services in the ISDN. + +### **6.2.4 State definitions** + +No specific state definitions are required. + +## **6.3 Operational requirements** + +### **6.3.1 Provision and withdrawal** + +The GVNS is provided to the customer by subscription. Provision and coordination of GVNS may be required in multiple networks depending on the location of the customer's users. + +### **6.3.2 Requirements on the originating network side** + +Not applicable. + +### **6.3.3 Requirements in the network** + +No specific requirements. + +### **6.3.4 Requirements on the terminating network side** + +Not applicable. + +## **6.4 Coding requirements** + +### **6.4.1 Messages** + +The forward GVNS parameter is an optional part in the initial address message. For the GVNS service, in addition to the messages and parameters defined in the Recommendation Q.763, the initial address message always includes a forward GVNS parameter in order to convey GVNS-specific information between the participating Administrations. Its use is mandatory when the call is a GVNS call. For the GVNS service, in addition to the messages and parameters defined in Recommendation Q.763, the answer and connect messages in the backward direction shall contain a backward GVNS parameter. The forward GVNS parameter is described in 6.4.2.1 and its format is shown in Figure 6-1. The backward GVNS parameter is described in 6.4.2.2 and its format is shown in Figure 6-5. + +### **6.4.2 Parameters** + +#### **6.4.2.1 Forward GVNS parameter** + +The format of the forward GVNS parameter is given in Figure 6-1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---|----------------------------------------------------|---|---|---|---|---|---|---| +| 1 | Originating participating service provider
OPSP | | | | | | | | +| 2 | GVNS user group
GUG | | | | | | | | +| 3 | Terminating network routing number
TNRN | | | | | | | | + +**Figure 6-1/Q.735.6 – Forward GVNS parameter field** + +The following codes are used in the subfields of the forward GVNS parameter: + +- a) *Originating participating service provider* + +See Figure 6-2. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +|-----|-----------------------|-------|---|---|-----------------------|---|---|---|--|--|--| +| 1 | O/E | Spare | | | OPSP length indicator | | | | | | | +| 1a | 2 nd digit | | | | 1 st digit | | | | | | | +| ... | ... | | | | ... | | | | | | | +| 1n | Filler (if necessary) | | | | n th digit | | | | | | | + +**Figure 6-2/Q.735.6 – Originating participating service provider subfield** + +- 1) *Odd/even indicator (O/E)* + +- 0 even number of digits + +- 1 odd number of digits + +- 2) *OPSP length indicator* + +Number of octets to follow. The maximum number of octets is 4 allowing for a maximum number of digits to 7. + +- 3) *Digit* + +Digit string in BCD encoding of flexible length representing the originating participating service provider identification (OPSP). + +- 4) *Filler* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +##### b) *GVNS user group* + +See Figure 6-3. + +![](e9314c83043183351ed74908e9bf2f90_img.jpg) + +| | | | | | | | | | +|-----|-----|-----------------------|---|---|-----------------------|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 2 | O/E | Spare | | | GUG length indicator | | | | +| 2a | | 2 nd digit | | | 1 st digit | | | | +| ... | | ... | | | ... | | | | +| 2n | | Filler (if necessary) | | | n th digit | | | | + +**Figure 6-3/Q.735.6 – GVNS user group subfield** + +###### 1) *Odd/even indicator (O/E)* + +0 even number of digits + +1 odd number of digits + +###### 2) *GUG length indicator* + +Number of octets to follow. The maximum number of octets is 8 allowing for a maximum number of digits to 16. + +###### 3) *Digit* + +Digit string in BCD encoding of flexible length representing the GVNS User Group Identification (GUG). + +###### 4) *Filler* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +##### c) *Terminating network routing number* + +See Figure 6-4. + +![](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +| | | | | | | | | | +|-----|-------|-----------------------------|---|---|-----------------------|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 3 | O/E | Numbering plan indicator | | | TNRN length indicator | | | | +| 3a | Spare | Nature of address indicator | | | | | | | +| 3b | | 2 nd digit | | | 1 st digit | | | | +| ... | | ... | | | ... | | | | +| 3n | | Filler (if necessary) | | | n th digit | | | | + +**Figure 6-4/Q.735.6 – Terminating network routing number subfield** + +###### 1) *Odd/even indicator (O/E)* + +0 even number of digits + +1 odd number of digits + +###### 2) *Numbering plan indicator* + +See 3.9 d)/Q.763. + +###### 3) *TNRN length indicator* + +Number of octets to follow. The maximum number of octets is 9 allowing for a maximum number of digits to 15. + +###### 4) *Nature of address indicator* + +0000000 spare + +0000001 subscriber number @ + +0000010 unknown @ + +0000011 national (significant) number + +0000100 international number + +0000101 network specific number + +0000110 to 1101111 } spare + +1110000 to 1111110 } reserved for national use + +1111111 spare + +###### 5) *Digit* + +See 3.9 e)/Q.763. + +The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit fields. + +###### 6) *Filler* + +In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. + +#### **6.4.2.2 Backward GVNS parameter** + +The format of the backward GVNS parameter is given in Figure 6-5. + +![](b1296e107640b11ccb35d9c5fd989e2e_img.jpg) + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| H | G | F | E | D | C | B | A | + +**Figure 6-5/Q.735.6 – Backward GVNS parameter field** + +bits BA Terminating access indicator + +00 no information + +01 dedicated Terminating Access + +10 switched Terminating Access + +11 spare + +bits G-C Spare + +| | | | +|-----|---|----------------------------------------| +| bit | H | Extension indicator (EXT) | +| | 0 | octet continues through the next octet | +| | 1 | last octet | + +#### 6.4.2.3 Other existing parameter to support GVNS service + +##### 6.4.2.3.1 Called party number parameter + +A new coding in the nature of address indicator of the called party number parameter is defined to support a network specific number that is used in the terminating network that provides the GVNS service: + +- *Nature of address indicator* +0000101 network-specific number @ + +## 6.5 Signalling procedures + +This procedure describes only calls from on-net location to another on-net location (see Recommendation F.16). + +A possible physical configuration is presented in Figure 6-6. + +![Figure 6-6/Q.735.6 – Possible physical configuration diagram showing a sequence of network elements: OLE (circle), TE (circle), OIE (square), ITE (triangle), IIE (square), TE (circle), and DLE (circle). Below each element are labels for functionalities: OLE (A, OR), TE (A, OR), OIE (A, OR), ITE (none), IIE (TR), TE (TR), and DLE (TR). The diagram is labeled T1175120-95.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +Figure 6-6/Q.735.6 – Possible physical configuration diagram showing a sequence of network elements: OLE (circle), TE (circle), OIE (square), ITE (triangle), IIE (square), TE (circle), and DLE (circle). Below each element are labels for functionalities: OLE (A, OR), TE (A, OR), OIE (A, OR), ITE (none), IIE (TR), TE (TR), and DLE (TR). The diagram is labeled T1175120-95. + +### Exchanges + +- DLE Destination Local Exchange +- IIE Incoming International gateway Exchange +- ITE International Transit Exchange +- OIE Outgoing International gateway Exchange +- OLE Originating Local Exchange +- TE Transit Exchange + +### Functionalities + +- A Possible node for the GVNS access function to GVNS service +- OR Possible node for the originating GVNS routing function for GVNS service +- TR Possible node for the terminating GVNS routing function for GVNS service + +**Figure 6-6/Q.735.6 – Possible physical configuration** + +### 6.5.1 Activation/deactivation/registration + +Not applicable. + +### **6.5.2 Invocation and operation** + +#### **6.5.2.1 Actions at the originating local exchange** + +As an alternative, the GVNS access function and the originating GVNS routing function described in this subclause may be performed at either a transit exchange in the originating network or the outgoing international exchange. + +##### **6.5.2.1.1 In case the GVNS access function is performed** + +###### **6.5.2.1.1.1 Normal operation** + +Upon receipt of a request for GVNS service, the originating local exchange shall check its GVNS access validity. After the GVNS user group is identified and screening is passed, a GVNS call is set up by sending an initial address message to the succeeding exchange. + +###### **GVNS information in the answer or connect message** + +The procedures to process the information in the received backward GVNS parameter received in the answer or connect messages will be network dependent. + +###### **6.5.2.1.1.2 Exceptional procedures** + +If a GVNS access is not permitted, then the originating local exchange shall release the call, with cause value No. 29. + +The absence of the backward GVNS parameter in either an answer or a connect message shall not release the GVNS call. As a network dependent action, the operation and maintenance system may be alerted. + +##### **6.5.2.1.2 In case the originating GVNS routing function is performed** + +As a prerequisite to perform the routing function in the originating local exchange, the originating GVNS access function shall be performed at the originating local exchange, and before the routing function. + +###### **6.5.2.1.2.1 Normal operation** + +When the originating local exchange has determined that the call is to be routed to another GVNS provider and the call is allowed to be set up to the GVNS provider, selection of a suitable, free, inter-exchange circuit takes place and an initial address message is sent to the succeeding exchange. + +Appropriate GVNS routing information is either stored at the originating local exchange or at a remote database to which a request may be made. + +###### **a) *Circuit selection*** + +The selection of the route will depend on the routing number. The routing number is an ISDN number, i.e. a number fully conforming to Recommendation E.164. This selection process may be performed at the exchange or with the assistance of a remote database. + +###### **b) *GVNS information in the initial address message*** + +The Initial address message shall include all information required to route the GVNS call to the destination exchange and connect the call to the called party. + +The following information shall be included in an IAM: + +- Originating participating service provider identification, GVNS user group identification and terminating network routing number are included in the forward GVNS parameter. + +- The called party number parameter contains the routing number which, at the minimum, identifies the terminating participating service provider. + +###### **6.5.2.1.2.2 Exceptional procedures** + +None identified. + +##### **6.5.2.1.3 In case neither the GVNS access function nor the originating GVNS routing function is performed** + +###### **6.5.2.1.3.1 Normal operation** + +The procedures to set up a call are the same as the basic procedures. + +###### **6.5.2.1.3.2 Exceptional procedures** + +None identified. + +#### **6.5.2.2 Actions at the transit exchange (in the originating network)** + +As an alternative, the GVNS access function and the originating GVNS routing function described in this subclause may be performed at either the originating local exchange or the outgoing international exchange. In the case when the access function is performed in the originating local exchange, the transit exchange passes the forward GVNS parameter and the backward GVNS parameter received. + +##### **6.5.2.2.1 In case the GVNS access function is performed** + +###### **6.5.2.2.1.1 Normal operation** + +Upon receipt of a request for GVNS service, a transit exchange shall check its GVNS access validity. After the GVNS user group is identified and screening is passed, a GVNS call is set up by sending an initial address message to the succeeding exchange. + +###### **GVNS information in the answer or connect message** + +The procedures to process the information in the backward GVNS parameter received in the answer or connect messages will be network dependent. + +###### **6.5.2.2.1.2 Exceptional procedures** + +If a GVNS access is not permitted, then a transit exchange shall release the call, with cause value No. 29. + +The absence of the backward GVNS parameter in either an answer or a connect message shall not release the GVNS call. As a network dependent action, the operation and maintenance system may be alerted. + +##### **6.5.2.2.2 In case the originating GVNS routing function is performed** + +As a prerequisite to perform the routing function in the transit exchange, the originating GVNS access function shall be performed at the originating local exchange or at the transit exchange. The GVNS access function has to be performed before the GVNS routing function. + +###### **6.5.2.2.2.1 Normal operation** + +When a transit exchange in the originating network has received the complete selection information from the national network and has determined that the call is to be routed to another GVNS provider + +and that the call is allowed to be set-up to the GVNS provider, selection of a suitable, free, inter-exchange circuit takes place and an initial address message is sent to the succeeding exchange. + +Appropriate GVNS routing information is either stored at the originating local exchange or at a remote database to which a request may be made. + +###### a) *Circuit selection* + +The selection of the route will depend on the routing number. The routing number is an ISDN number, i.e. a number fully conforming to Recommendation E.164. This selection process may be performed at the exchange or with the assistance of a remote database. + +###### b) *GVNS information in the initial address message* + +The Initial address message shall include all information required to route the GVNS call to the destination exchange and connect the call to the called party. + +The following information shall be included in an IAM: + +- Originating participating service provider identification, GVNS user group identification and terminating network routing number are included in the forward GVNS parameter. +- The called party number parameter contains the routing number which, at the minimum, identifies the terminating participating service provider. + +The procedures to set up a call will be network dependent. + +###### **6.5.2.2.2.2 Exceptional procedures** + +None identified. + +##### **6.5.2.2.3 In case neither the GVNS access function nor the originating GVNS routing function is performed** + +###### **6.5.2.2.3.1 Normal operation** + +The procedures to set up a call are the same as the basic procedures. + +###### **6.5.2.2.3.2 Exceptional procedures** + +None identified. + +#### **6.5.2.3 Actions at the outgoing international exchange** + +As an alternative, the GVNS access function and the originating GVNS routing function described in this subclause may instead be performed at either the originating local exchange or a transit exchange in the originating network. In those cases, the outgoing international exchange passes the forward GVNS parameter and the backward GVNS parameter received. + +##### **6.5.2.3.1 In case the GVNS access function is performed** + +###### **6.5.2.3.1.1 Normal operation** + +Upon receipt of a request for GVNS service the outgoing international exchange shall check its GVNS access validity. After the GVNS user group is identified and screening is passed, a GVNS call is set up by sending an initial address message to the succeeding exchange. + +###### **GVNS information in the answer or connect message** + +The procedures to process the information in the backward GVNS parameter received in the answer or connect messages will be network dependent. + +###### **6.5.2.3.1.2 Exceptional procedures** + +If a GVNS access is not permitted, then the outgoing international exchange shall release the call, with cause value No. 29. + +The absence of the backward GVNS parameter in either an answer or a connect message shall not release the GVNS call. As a network dependent action, the operation and maintenance system may be alerted. + +##### **6.5.2.3.2 In case the originating GVNS routing function is performed** + +As a prerequisite to perform the routing function in the outgoing international exchange, the originating GVNS access function shall be performed at the originating local exchange, at the transit exchange, or at the outgoing international exchange. The GVNS access function has to be performed before the GVNS routing function. + +###### **6.5.2.3.2.1 Normal operation** + +When the outgoing international exchange has received the complete selection information from the national network and has determined that the call is to be routed to another GVNS provider and that the call is allowed to be set-up to the GVNS provider, selection of a suitable, free, inter-exchange circuit takes place and an initial address message is sent to the succeeding exchange. + +Appropriate GVNS routing information is either stored at the outgoing international exchange or at a remote database to which a request may be made. + +###### **a) *Circuit selection*** + +The selection of the route will depend on the routing number. The routing number is an ISDN number, i.e. a number fully conforming to Recommendation E.164. This selection process may be performed at the exchange or with the assistance of a remote database. + +###### **b) *GVNS information in the initial address message*** + +The Initial address message shall include all information required to route the GVNS call to the destination exchange and connect the call to the called party. + +The following information shall be included in an IAM: + +- Originating participating service provider identification, GVNS user group identification and terminating network routing number as contained in the forward GVNS parameter. +- The called party number parameter contains the routing number which, at the minimum, identifies the terminating participating service provider. + +The procedures to set up a call will be network dependent. + +###### **6.5.2.3.2.2 Exceptional procedures** + +None identified. + +##### **6.5.2.3.3 In case neither the GVNS access function nor the originating GVNS routing function is performed** + +###### **6.5.2.3.3.1 Normal operation** + +The procedures to set up a call are the same as the basic procedures. + +###### **6.5.2.3.3.2 Exceptional procedures** + +None identified. + +#### **6.5.2.4 Actions at an international transit exchange** + +##### **6.5.2.4.1 Normal operation** + +###### a) *Circuit selection* + +The circuit selection process is the same as for a basic call. + +###### b) *Information included in the IAM* + +No further action is required than for a basic call. + +##### **6.5.2.4.2 Exceptional procedures** + +None identified. + +#### **6.5.2.5 Actions at the incoming international exchange** + +As an alternative, the terminating GVNS routing function described in this subclause may be performed at either a transit exchange in the terminating network or the destination local exchange. In those cases, the incoming international exchange passes the forward GVNS parameter and the backward GVNS parameter received. + +##### **6.5.2.5.1 In case the terminating GVNS routing function is performed** + +###### **6.5.2.5.1.1 Normal operation** + +When the incoming international exchange has received the complete selection information from the preceding network and has checked that the call is allowed to be terminated in its VPN, then the following actions occur. The checks can be made either against information stored in the exchange or at a remote database. + +###### a) *Circuit selection* + +The selection of the route will depend on the terminating network routing number, received in the forward GVNS parameter. This selection process may be performed at the exchange or with the assistance of a remote database. + +###### b) *GVNS information in the initial address message* + +The Initial address message sent to the national network shall contain the called party number parameter that includes a routing number and that is used by the terminating network to complete the call to the destination location. Derivation of this routing number is network dependent. + +The Initial address message sent to the national network may also contain the forward GVNS parameter that includes the originating participating service provider identification, GVNS user group identification and terminating network routing number. The Initial address message may also carry the dialled number information. + +###### c) *GVNS information in the answer or connect message* + +The backward GVNS parameter shall be included in the answer or connect message. + +The terminating access indicator included in the parameter has four values. The setting should be as follows: + +- "(10) Switched terminating access" is used when a switched connection from the GVNS network to the terminating user is established via one or more networks on which: + - i) the particular GVNS is not supported; + - ii) the circuits from the GVNS participating service provider carry the GVNS traffic of various GVNS user groups and possibly non-GVNS traffic. + +- "(01) Dedicated terminating access" is sent when a customer dedicated physical connection is used from the network to a user that supports GVNS. +- "(11) Spare" is reserved for the future use. +- "(00) No information" means that no information is available. + +NOTE – This value is discouraged from being used by the terminating participating service provider, since it provides no useful information to the originating participating service provider. + +###### **6.5.2.5.1.2 Exceptional procedures** + +None identified. + +##### **6.5.2.5.2 In case the terminating GVNS routing function is not performed** + +###### **6.5.2.5.2.1 Normal operation** + +The procedures to set up a call are the same as the basic procedures. + +###### **6.5.2.5.2.2 Exceptional procedures** + +None identified. + +#### **6.5.2.6 Actions at a transit exchange (in the terminating network)** + +As an alternative, the terminating GVNS routing function described in this subclause may be performed at either the incoming international exchange or the destination local exchange. In the case when the terminating GVNS routing function is performed in the destination local exchange, the transit exchange passes the forward GVNS parameter and the backward GVNS parameter received. + +##### **6.5.2.6.1 In case the terminating GVNS routing function is performed** + +###### **6.5.2.6.1.1 Normal operation** + +When a transit exchange in the terminating network has received the complete selection information from the preceding network and has checked that the call is allowed to be terminated in its VPN, then the following actions occur. The checks can be made either against information stored in the exchange or at a remote database. + +###### **a) *Circuit selection*** + +The selection of the route will depend on the terminating network routing number. This selection process may be performed at the exchange or with the assistance of a remote database. + +###### **b) *GVNS information in the initial address message*** + +The Initial address message sent to the destination local exchange shall contain the called party number parameter that includes a routing number and that is used by the terminating network to complete the call to the destination location. Derivation of this routing number is network dependent. + +The Initial address message sent to the destination local exchange may also contain the forward GVNS parameter that includes the originating participating service provider identification, GVNS user group identification and terminating network routing number. The Initial address message may also carry the dialled number information. + +###### **c) *GVNS information in the answer or connect message*** + +The backward GVNS parameter shall be included in the answer or connect message. + +The terminating access indicator included in the parameter has four values. The setting should be as follows: + +- "(10) Switched terminating access" is used when a switched connection from the GVNS network to the terminating user is established via one or more networks on which: + - i) the particular GVNS is not supported; + - ii) the circuits from the GVNS participating service provider carry the GVNS traffic of various GVNS user groups and possibly non-GVNS traffic. +- "(01) Dedicated terminating access" is sent when a customer dedicated physical connection is used from the network to a user that supports GVNS. +- "(11) Spare" is reserved for the future use. +- "(00) No information" means that no information is available. + +NOTE – This value is discouraged from being used by the terminating participating service provider, since it provides no useful information to the originating participating service provider. + +###### **6.5.2.6.1.2 Exceptional procedures** + +None identified. + +##### **6.5.2.6.2 In case the terminating GVNS routing function is not performed** + +###### **6.5.2.6.2.1 Normal operation** + +The procedures to set up a call are the same as the basic procedures. + +###### **6.5.2.6.2.2 Exceptional procedures** + +None identified. + +#### **6.5.2.7 Actions at the destination local exchange** + +As an alternative, the terminating GVNS routing function described in this subclause may be performed at either the incoming international exchange or a transit exchange in the terminating network. + +##### **6.5.2.7.1 In case the terminating GVNS routing function is performed** + +###### **6.5.2.7.1.1 Normal operation** + +When the destination local exchange has received the complete selection information from the preceding network and has checked that the call is allowed to be terminated in its VPN, then the following actions occur. The checks can be made either against information stored in the exchange or at a remote database. + +###### **a) *Circuit selection*** + +The selection of the user access will depend on the terminating network routing number. This selection process may be performed at the exchange or with the assistance of a remote database. + +###### **b) *GVNS information in the answer or connect message*** + +The backward GVNS parameter shall be included in the answer or connect message. + +The terminating access indicator included in the parameter has four values. The setting should be as follows: + +- "(10) Switched terminating access" is used when a switched connection from the GVNS network to the terminating user is established via one or more networks on which: + - i) the particular GVNS is not supported; + - ii) the circuits from the GVNS participating service provider carry the GVNS traffic of various GVNS user groups and possibly non-GVNS traffic. +- "(01) Dedicated terminating access" is sent when a customer dedicated physical connection is used from the network to a user that supports GVNS. +- "(11) Spare" is reserved for the future use. +- "(00) No information" means that no information is available. + +NOTE – This value is discouraged from being used by the terminating participating service provider, since it provides no useful information to the originating participating service provider. + +###### **6.5.2.7.1.2 Exceptional procedures** + +None identified. + +##### **6.5.2.7.2 In case the terminating GVNS routing function is not performed** + +###### **6.5.2.7.2.1 Normal operation** + +The procedures to set up a call are the same as the basic procedures. + +###### **6.5.2.7.2.2 Exceptional procedures** + +None identified. + +## **6.6 Interactions with other supplementary services** + +"No applicable interaction at this time" means that the work on the service being interacted with has not finished yet. + +### **6.6.1 Call Waiting (CW)** + +No impact on ISUP. + +### **6.6.2 Call transfer services** + +For further study. + +### **6.6.3 Connected line identification presentation (COLP)** + +For further study. + +### **6.6.4 Connected line identification restriction (COLR)** + +No impact on ISUP. + +### **6.6.5 Calling Line Identification Presentation (CLIP)** + +For further study. + +### **6.6.6 Calling Line Identification Restriction (CLIR)** + +No impact on ISUP. + +### **6.6.7 Closed User Group (CUG)** + +For further study. + +### **6.6.8 Conference calling (CONF)** + +No impact on ISUP. + +### **6.6.9 Direct-Dialing-In (DDI)** + +No impact on ISUP. + +### **6.6.10 Call diversion services (CDIV)** + +#### **6.6.10.1 Call Forwarding Busy (CFB)** + +For further study. + +#### **6.6.10.2 Call Forwarding no Reply (CFNR)** + +For further study. + +#### **6.6.10.3 Call Forwarding Unconditional (CFU)** + +For further study. + +#### **6.6.10.4 Call Deflection (CD)** + +For further study. + +### **6.6.11 Line Hunting (LH)** + +No applicable interaction at this time. + +### **6.6.12 Three-Party service (3PTY)** + +No impact on ISUP. + +### **6.6.13 User-to-User Signalling (UUS)** + +#### **6.6.13.1 User-to-User Signalling service 1 (UUS1)** + +No impact on ISUP. + +#### **6.6.13.2 User-to-User Signalling service 2 (UUS2)** + +No impact on ISUP. + +#### **6.6.13.3 User-to-User Signalling service 3 (UUS3)** + +No impact on ISUP. + +### **6.6.14 Multiple Subscriber Number (MSN)** + +No impact on ISUP. + +### **6.6.15 Call hold (HOLD)** + +No impact on ISUP. + +### **6.6.16 Advice of Charge (AOC)** + +No impact on ISUP. + +### **6.6.17 Sub-addressing (SUB)** + +For further study. + +### **6.6.18 Terminal Portability (TP)** + +No impact on ISUP. + +### **6.6.19 Completion of Calls to Busy Subscriber (CCBS)** + +No applicable interaction at this time. + +### **6.6.20 Malicious Call Identification (MCID)** + +No applicable interaction at this time. + +### **6.6.21 Reverse charging (REV)** + +For further study. + +### **6.6.22 Multi-Level Precedence and Preemption (MLPP)** + +For further study. + +### **6.6.23 Private Numbering Plan (PNP)** + +No applicable interaction at this time. + +### **6.6.24 International Telecommunication Charge Card (ITCC)** + +For further study. + +## **6.7 Interaction with other networks** + +In the case of interworking with Q.767 exchange, all GVNS related information will be discarded. The call will be either released or routed based on the number in the called party number parameter. (but may not be completed successfully to the called party, since the necessary routing information in the terminating network routing number is not available). + +## **6.8 Signalling flows** + +The signalling flows of the basic call procedures are applicable. + +## **6.9 Parameter values (timers)** + +None identified. + +## **6.10 Dynamic description** + +The basic call control SDLs of the ISDN user part (Recommendation Q.764) apply for the GVNS because there is no change in the message sequence. + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|----------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Telephone network and ISDN | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media | +| Series H | Transmission of non-telephone signals | +| Series I | Integrated services digital network | +| Series J | Transmission of sound-programme and television signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound-programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminal equipments and protocols for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.752-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.752-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597350198bf183a462cef91611cc21dc746957d4 --- /dev/null +++ b/marked/Q/T-REC-Q.752-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30a6e102b1da0d13af03d660db963eef109c7d460e75a8e2594ffa6362039a83 +size 8212 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93128370c6e465847fe1b1e70d58e1c3a74a297a --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55f3d166aa61aef8e62f4082c6e505834ef22dbec7aa5c56b858e40be104d25d +size 34458 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ee6d1b99cb1a11390a73150f1ea502b7fe8cb1e --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2834cfd73e98ef568193df91528056db2414f7526d484ab26599234efd0a00a +size 52991 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef217a35c606f996aec24fcc6d998d1acd256f8 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:247ac7e691d9b397de6c25536f4e75ec7745dc147c743ea9971188d8020f638a +size 8239 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01c374f5645915ed30dc3290e9baeaef4b5db26e --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be865bafe27ce14b3f48fb7e2b4059e66d05327c3fd790461b9fa5a358704067 +size 54248 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cbe34282f179dfe6bcc8e138ea69bc7f489ea55 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a9403c965e598be31f57675cb50cefc85496c08a5b900aa108383ce9d187999 +size 60657 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55a53b472b8a19304b56ae4bef06289a18bd7f37 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:938671089684e5756a9438d577a316bcb76bba6fe601dddf764648f17d68e517 +size 35689 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81097380a5e37e6916eaa1fbdbc2a989d79c69e0 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b29075c984d454b00e1f4fda67693d0f2c2f5b0dca7781e551e2cde350644ae +size 114510 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1f17f722a548c601a3bbb3927610f98681a412c --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2780f1f0b14ba5f894a05cb2f42b673b198924ee6370c0aac5fa7b6f7584f0ae +size 35680 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9710b6c75b0cfdc67233f602f2d7ff278ff240f --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83a45e197d25871241987d02c8b04deb9912068796594795d60bfe33a0f35f72 +size 77604 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fd0c887d60c54786a39a082a85f5043f5fd22fd --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:639580e89ea161471dfcc0e8d9fd9d3e2e5da53de4af864b97b61222a739b7d1 +size 121657 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/5148ae85e7c243139ae6b37e24f01940_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/5148ae85e7c243139ae6b37e24f01940_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec74005717d41d91bb9cfc442477277a58cb1234 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/5148ae85e7c243139ae6b37e24f01940_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0db9049c62ebb66abff75ed8212c5ca62eaf09afd963fe331debe38b7558de7e +size 89139 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cf49dba85061b47993869266097a9b3168ec013 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7880c3ce9a5b2eec67487f94a07ae7e7ad3e78953a87133385990b5ee4e7de6f +size 58129 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bf4045482592ba8a31ead84173e477155ad13bc --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c84f8a442d1af1f0f3563ffc2535e796ebec1ed8964b84edd9dad96fbc53b32 +size 20763 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/5db6545aedab79741ebae9b27bb363b3_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/5db6545aedab79741ebae9b27bb363b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52c6f23185393ea31f6b2dea0ab54fac5042c303 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/5db6545aedab79741ebae9b27bb363b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:461720b535fff99231afb60d7d6d1d882e38840abba2ce1619868612b2b47d13 +size 168669 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90e3ee563527f721f8f4da409e8cf19c4ddb9b57 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d95f311794c704effe39dd18b4259a446c11161a8327c6ab0ec7b170923f77bf +size 120032 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..215a0dfe436fb59573be167d3f01f786538c2c1e --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b445f19bfd002335b8efd7942048e7d0d43cd4ee7d21b2f2621caa9472200572 +size 131245 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58270c759395212422cf79bc9f65a5b2e696a2e7 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:630d5b76bff8de69789806ce0e93ee9884c0e31aaf217f0d832a640dd2be44cb +size 154108 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53d0d7db150a071e8965a0f5734e8aa8c0306744 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e27454cc5bed59926b3334f6bc6b35aede101cc0dfa8bc7c6cb6f5c6878ed616 +size 90457 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6aa349440449bfcd252fabbdab9ee84a832c608 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:069b5a934164213dbe3641c9dde45c893cf8d5e482f185d28afad7b915396613 +size 97121 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29de0f496e4e8cbba10facfbd77a9dbd77edeb1b --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a44fc585bde78620f5cd551d0b047195d24e3293331f6c6f36dd89251538939b +size 37808 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f74d5591ca3620d2e0fb86fc766a8d9e79c4daa --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fa02f6494a0458fb77b340db074c64cbe1a1db13c62d0fab361486a7b0f4351 +size 55131 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c5ae218559b325ea5979bb6cb61019afd81f429 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:972fff055271caccc263a9b4a76721eebf7ca489ce3ede45f020e74f60234c37 +size 57353 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0090982eefd171ef6435d245b6a993720197f026 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dfd467f49920699ae88be0692f4ea406e8fbfbb0beeeaf1ab362d4bef1d7857 +size 182781 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ced9045044f7113f51ca2673845b417f010c186 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:399cb443e9f8655ec12a86f4c8fd52d19c63a757f1b61de688c649627998bba3 +size 35913 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d9986b157c67889e8ffc8259eb13f938a715cac --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e511bcf0254258dc69072483c61f3bdfd67476d7f897e86432ccf6aa4869345 +size 40787 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f15b58a08665656f35c34082428f2ee12dbfb111 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edfe28e3df46707564ad8522e0b03c9f47b16c33c73f4d8f15fcc72127d0d113 +size 139547 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2627036cf62da32cce28357a927efc13697b6518 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01449652394afd6e949ddac0d2b0ed68276c017bd51a02c153678c5ac26d0a17 +size 215946 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/cc98b584f9b31fe69948e3fa65a3ba69_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/cc98b584f9b31fe69948e3fa65a3ba69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..565a8eaf9757e30058f1cc52a2bc8c157c99c158 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/cc98b584f9b31fe69948e3fa65a3ba69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:424375d5c143e3cf454e14fc9e80700ca10bd71439d8c66613918fc229c7bd92 +size 60005 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55e7c415145982558962644978cbccb6427d4824 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d376e197daf94a77e56466107952038dd85ed3742f9c283f8d5d935b37000161 +size 72822 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aed762dfab8e92c1e55f37b9222820312de7cc0 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd07dc2f7b8f7338ff7500e383e53f6cb5f76e2643ab5bc91900e57676f9a7e9 +size 43023 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c89898a0e9f3bfb8bf403bce4dd478de3fdff73 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b959074ddd882f909e53d6faab19089436ac7f68c78695e85c95a7dcf1d45a52 +size 105226 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d02f94abdc76aadc2b4166bcae95780bdcfc7cb --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c62250ea39b5fab58d8c5a4577e8b46adec982cb6eef0dd9da74ff392e6a8932 +size 37179 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2aca4da6eb93f3d0505917ba02cd8dae1ae733e --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:739057e3e5f5753cb2b1c1c8ce5e9116bc81b8e9a8fddd56d19af84559f83c8d +size 53835 diff --git a/marked/Q/T-REC-Q.753-199706-I_PDF-E/fee87ee34f98efee162e918fbaeec613_img.jpg b/marked/Q/T-REC-Q.753-199706-I_PDF-E/fee87ee34f98efee162e918fbaeec613_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcd292b4dd2cef979118fb21a127e1cb1fbfad15 --- /dev/null +++ b/marked/Q/T-REC-Q.753-199706-I_PDF-E/fee87ee34f98efee162e918fbaeec613_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ffe1f2095c156d9203bc9f6fb377ffd99781815f447eeb57f4678a42f5e0a06 +size 44212 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a15674d5ba64e4c11fa77e0385e99fb4fde203d5 --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce8da34a7c517f9f072ad76a7bc6712140f2085738976f5b40e8ef18f565b11a +size 11168 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0567238e00df8e253788bf8530befe578ff3631 --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:960677700babf17d039eb3f82e57fe0bbc4db1c239872766816c666e1c62d248 +size 107284 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..753116a22e99beac5b4d74e28242423176eaecbc --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c5833c682979ad90a80b85bc8407198f198be75cab0b1a5f5c748b424a20d73 +size 20690 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06f09c90637b044f995fec2f1574381c81336d4d --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab1ba15cc6d4ae3d499bb79314bd583ab07120641414476d44b7a3b7fc5a8c3d +size 28261 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4368b4f4fba15d75e1d8a8e27c4b115b3aaee573 --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3d2bae9525990c67788a2a4c6a37fecc0c0b58da8521f72746385bc314b708c +size 15105 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.782-200204-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96036581e4a3c4e58b6e54584110225510aae909 --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fb4127a136c233ca5b2a968f0b9928c61092714ab3573e45333831d66e2a9d8 +size 56761 diff --git a/marked/Q/T-REC-Q.782-200204-I_PDF-E/raw.md b/marked/Q/T-REC-Q.782-200204-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d617068b9485c7c0c6864139ac97f5539fb662ed --- /dev/null +++ b/marked/Q/T-REC-Q.782-200204-I_PDF-E/raw.md @@ -0,0 +1,4660 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.782** + +(04/2002) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Test +specification + +--- + +**MTP level 3 test specification** + +ITU-T Recommendation Q.782 + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 | Q.120-Q.139 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 | Q.140-Q.199 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701-Q.709 | +| Signalling connection control part (SCCP) | Q.711-Q.719 | +| Telephone user part (TUP) | Q.720-Q.729 | +| ISDN supplementary services | Q.730-Q.739 | +| Data user part | Q.740-Q.749 | +| Signalling System No. 7 management | Q.750-Q.759 | +| ISDN user part | Q.760-Q.769 | +| Transaction capabilities application part | Q.770-Q.779 | +| Test specification | Q.780-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **ITU-T Recommendation Q.782** + +# **MTP level 3 test specification** + +## **Summary** + +This Recommendation contains a set of detailed tests of Signalling System No. 7, MTP level 3 protocol. These tests intend to validate the protocol specified in ITU-T Recs. Q.704 and Q.707. The level 3 performance aspects specified in ITU-T Rec. Q.706 are also partly checked whenever possible. This Recommendation conforms to ITU-T Rec. Q.780. However, in addition to the objectives and guidelines of the latter Recommendation, other general principles specific to level 3 tests are presented. + +###### **Source** + +ITU-T Recommendation Q.782 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 13 April 2002. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------|----| +| 1 | Introduction ..... | 1 | +| 2 | General principles of level 3 tests..... | 1 | +| 2.1 | Presentation of test descriptions ..... | 1 | +| 2.2 | Presentation of the test list..... | 1 | +| 2.3 | Test traffic ..... | 2 | +| 3 | Test configurations ..... | 3 | +| 3.1 | Definition..... | 3 | +| 3.2 | Presentation of test configurations ..... | 3 | +| 3.2.1 | General ..... | 3 | +| 3.2.2 | Configuration A..... | 4 | +| 3.2.3 | Configuration B..... | 4 | +| 3.2.4 | Configuration C..... | 5 | +| 3.2.5 | Configuration D..... | 6 | +| 4 | Test list ..... | 8 | +| 5 | Test descriptions ..... | 13 | + + + +# MTP level 3 test specification + +# 1 Introduction + +This Recommendation contains a set of detailed tests of Signalling System No. 7 MTP level 3 protocol. These tests intend to validate the protocol specified in ITU-T Recs. Q.704 and Q.707. The level 3 performance aspects specified in ITU-T Rec. Q.706 are also partly checked whenever possible. This Recommendation conforms to ITU-T Rec. Q.780. However, in addition to the objectives and guidelines of the latter Recommendation, other general principles specific to level 3 tests are presented below. + +# 2 General principles of level 3 tests + +### 2.1 Presentation of test descriptions + +Each test description mentions the type of SP involved in the test. Three cases are possible: + +- test applicable to an SP having no STP function: SP +- test applicable to an SP having STP function: STP +- test applicable to all types of SPs: ALL + +Each test description includes the environment in which the point under test must be inserted in order to pass the test. Four test configurations are necessary (named A, B, C and D); they are presented in clause 3. + +Each test is precisely described. Nevertheless, some events not directly concerning the point under test, or without direct link with the test nature, are not explicitly described. This is, for example, the case of TFPs propagation when a point becomes isolated, or of the changeover procedure in a test concerning transfer allowed procedure. + +In order to preserve the test description implementation independence, a certain flexibility has been left in the test descriptions. This is particularly the case when it is necessary to deactivate a link (where it is only mentioned "Deactivate" with no more precision). The operator will choose, if possible, according to the implementation particularities and the events expected in the test description, the appropriate deactivation means (MML, provoked failure, etc.). + +In the test descriptions, the signalling links are identified as follows: "number of linkset"—"number of link in the linkset" (e.g. 1–1 means link 1 of the linkset 1). This identification is independent of SLC attributed to these links. When the number of the link is X, that means that the concerned message can use any link of the linkset. When the field "number of link in the linkset" is, for example, "1, 2, . . .", that means that the traffic uses all indicated links. Finally, when the links are identified by the mention ALL, that means that the traffic will use all available links of the point. + +The orders "Start traffic", "Wait" and "Stop traffic" apply to the test configuration. They are placed at the beginning of the line. + +### 2.2 Presentation of the test list + +These tests, as a whole, aim at a complete validation of the level 3 protocol without redundancies. + +The test list is presented in clause 4. The national options and the various signalling link management "policies" are not included in this Recommendation. + +The first set of tests in the list checks that, before some more precise tests, the point under test can perform the basic functions, i.e. can connect itself to the external environment and exchange signalling messages. + +The second set basically validates the signalling message handling function of the point under test. A main point of this part concerns the validation of load sharing procedures. If an implementation does not use the load sharing between linksets, some tests would not be applicable, and others should be adapted. + +The third and fourth sets check changeover and changeback procedures. They include tests like changeover and changeback to/from two linksets which will be performed only if the point under test allows this possibility. + +Rerouting procedures are checked using the tests in sets 5 and 6. + +Set 7 concerns tests to check inhibition and uninhibition procedures. To limit the test numbers, it was not considered that the messages used in these procedures can be transferred via STPs. + +Set 8 concerns tests to check transfer controlled procedure and MTP user flow control for the international signalling network. + +Set 9 concerns tests to check signalling route management functions in a point having an STP function. To limit the test numbers and to avoid complicating the test configuration, it was not considered that TFPs and TFAs can be transferred via STPs. + +Set 10 concerns tests for the point restart procedure. + +Set 11 deals with STP traffic test. + +Set 12 checks the signalling link test procedure. + +Finally, set 13 contains solely validation tests and aims at checking the actions of the tested system on reception of invalid level 3 messages. + +### **2.3 Test traffic** + +Running the tests described in this Recommendation requires the exchange of traffic between the point under test and its environment. The traffic used is a test traffic especially generated for the test of the system. It uses variable length messages, structured as described below: + +![Diagram of a Level 3 message structure showing fields SIO, DPC, OPC, SLS, N, L, and DATA. It includes bit and octet transmission order arrows and descriptive text for each field.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the structure of a Level 3 message. At the top, an arrow labeled "Order of bit transmission" points left, with bits numbered 8 to 1. Below this, an arrow labeled "Order of octet transmission" points down. The message fields are as follows: + +- SIO**: SI (Note), SSF Any value +- DPC**, **OPC**, **SLS**: = A, B, C, D, E or F depending of the test +- N**: Number identifying one message among all messages pertaining to a given signalling relation +- L**: Length of DATA field. The diagram shows a byte with bits 0 0 0 0 0 0 0 0. +- DATA**: Variable field used for variable length message generation (SIF up to 272 octets). It is coded with 0. + +T1157730-02 + +Diagram of a Level 3 message structure showing fields SIO, DPC, OPC, SLS, N, L, and DATA. It includes bit and octet transmission order arrows and descriptive text for each field. + +NOTE – For compatibility testing (CPT), use SI value for MTP testing user part, for validation testing (VAT) value is to be chosen as required. + +The mechanisms of generation and reception of this test traffic may be internal to the point under test or external (using a simulator for example). The tests presented here do not impose the choice of one of these mechanisms except for the tests of the STP function itself (tests 2.7, 8.2, 10 and 11) where the test traffic is necessarily generated outside the STP. The test traffic should be recorded and analysed subsequently for each described test. + +# 3 Test configurations + +### 3.1 Definition + +The set of tests described in this Recommendation assumes that the point under test is inserted in a test environment called "test configuration". A **test configuration** is defined as being: + +- the set of points, real or simulated, linked between them by signalling linksets, real or simulated, and of which some are connected to the point under test by one or several signalling linksets; +- the set of routing rules applied in different points and also in point under test; +- the flows of test traffic generated and received by +- a set of generation and reception means (see 2.3); +- the means (program, operator interface, etc.) to run the described tests; notably the possibilities of storage and analysis of test traffic and level 3 messages and, in the case of validation tests, the possibility to send at any stage of a test, any messages (level 3 or test) valid or not. + +## 3.2 Presentation of test configurations + +### 3.2.1 General + +The set of tests described in this Recommendation requires 4 different configurations named A, B, C and D. For each test, only the three first aspects of the above definition are precisely defined (set of points, set of routing rules and test traffic flows, see 3.1). + +### 3.2.2 Configuration A + +This simple configuration is adapted to the validation of all procedures concerning only one or more signalling links belonging to one linkset. It is used for the tests: + +- of activation and deactivation of links; +- of changeover and changeback procedures; +- of inhibition and uninhibition of links; +- invalid messages. + +Configuration A is shown in Figure 1. + +![Diagram of Configuration A showing three signaling points: SP A, SP B, and SP C. SP A and SP B are connected by four parallel lines representing links, with a vertical dashed line labeled L1 passing through them. SP B is connected to SP C by a single line representing a link, with a label L2 above it. SP C is enclosed in a dashed box labeled 'in VAT only'. The diagram is labeled T1157740-02 at the bottom right.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Diagram of Configuration A showing three signaling points: SP A, SP B, and SP C. SP A and SP B are connected by four parallel lines representing links, with a vertical dashed line labeled L1 passing through them. SP B is connected to SP C by a single line representing a link, with a label L2 above it. SP C is enclosed in a dashed box labeled 'in VAT only'. The diagram is labeled T1157740-02 at the bottom right. + +**Figure 1/Q.782 – Configuration A** + +Configuration A, Table 1, makes use of a point C in all validation tests in order to check the impact of the procedures on various traffic flows. Point C is not used in configuration A in the case of compatibility tests. + +Linkset 1 has four signalling links in order to check, for example, changeover procedure to several links within a linkset (test 3.15). + +In real networks, the procedures checked with this configuration act on the traffic carried in both directions of a link. Consequently, the flows of test traffic used are, regarding the routing label of messages: + +- OPC = A, DPC = B and OPC = B, DPC = A +- OPC = A, DPC = C and OPC = C, DPC = A (in validation test only). + +**Table 1/Q.782 – Routing rules in configuration A** + +| → | A | B | C | +|---|----|----|----| +| A | – | L1 | L1 | +| B | L1 | – | L2 | +| C | L2 | L2 | – | + +### 3.2.3 Configuration B + +Configuration B is adapted to the validation of all procedures concerning several signalling linksets. It is used for the tests: + +- of signalling message handling; +- of changeover and changeback; +- of forced and controlled rerouting. + +Configuration B is shown in Figure 2. + +![Diagram of Configuration B showing five signaling points (SP A, SP B, SP C, SP D, SP E) and their interconnections via linksets L1 through L8. SP A is at the top, connected to SP B and SP C. SP B is connected to SP C and SP D. SP C is connected to SP E. SP D is connected to SP E. A dashed line separates SP A from the rest of the network. SP D is labeled 'in VAT only'. The diagram is labeled T1157750-02.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram of Configuration B showing five signaling points (SP A, SP B, SP C, SP D, SP E) and their interconnections via linksets L1 through L8. SP A is at the top, connected to SP B and SP C. SP B is connected to SP C and SP D. SP C is connected to SP E. SP D is connected to SP E. A dashed line separates SP A from the rest of the network. SP D is labeled 'in VAT only'. The diagram is labeled T1157750-02. + +**Figure 2/Q.782 – Configuration B** + +In configuration B, Table 2, the point under test A is linked to the external world with 3 signalling linksets. This is the minimum required number of linksets in order to check: + +- load sharing between three linksets; +- changeover and changeback from/to two linksets (see 5.3.1/Q.704). + +**Table 2/Q.782 – Routing rules in configuration B** + +| → | A | B | C | D | E | +|---|------------|--------|--------|----------|--------| +| A | – | L2, L3 | L3, L2 | L1-L2-L3 | L2-L3 | +| B | L2, L4 | – | L4 | L5, L4 | L6, L4 | +| C | L3, L4 | L4 | – | L8, L4 | L7, L4 | +| D | L1, L5, L8 | L5, L8 | L8, L5 | – | Any | +| E | L7, L6 | L6, L7 | L7, L6 | Any | – | + +Li, Lj Li normal linkset and Lj alternative linkset +Li-Lj Load sharing between Li and Lj + +When the SP A is an SP having no STP function, this configuration is also the minimum to run the tests in a network situation where associated mode and quasi-associated mode are used (see 3.1.2/Q.701). + +This configuration comprises point D in all validation tests in order to check the impact of the procedures on various traffic flows (relations A-D and A-E). The point D is not used in configuration B in case of compatibility tests. + +In a real network, some procedures (changeover, changeback) checked with this configuration act on the traffic in both directions on the concerned linksets. Consequently, the test traffic flows used are, regarding the routing label of messages: + +- OPC = A, DPC = E and OPC = E, DPC = A +- OPC = A, DPC = D and OPC = D, DPC = A (in validation test only). + +### 3.2.4 Configuration C + +This configuration is adapted to the validation of some functions specific to an STP like: + +- message transfer function; +- sending of TFC; +- traffic test. + +Configuration C is shown in Figure 3. + +![Diagram of Configuration C showing three signaling points: SP B, SP A, and SP C. SP B and SP A are connected by two parallel links labeled L1. SP C is connected to SP A by a single link labeled L2. A vertical dashed line passes through the links between SP B and SP A, and between SP C and SP A, indicating the location of the Signaling Transfer Point (STP) under test. The diagram is labeled T1157760-02.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +Diagram of Configuration C showing three signaling points: SP B, SP A, and SP C. SP B and SP A are connected by two parallel links labeled L1. SP C is connected to SP A by a single link labeled L2. A vertical dashed line passes through the links between SP B and SP A, and between SP C and SP A, indicating the location of the Signaling Transfer Point (STP) under test. The diagram is labeled T1157760-02. + +**Figure 3/Q.782 – Configuration C** + +In configuration C, Table 3, the point under test A carries the test traffic from B to C and from C to B. The linkset 1 has two links, this a minimum to create an overload situation to trigger the sending of TFC independently of the implementation of the flow control procedure. + +**Table 3/Q.782 – Routing rules in configuration C** + +| → | A | B | C | +|---|----|----|----| +| A | – | L1 | L2 | +| B | L1 | – | L1 | +| C | L2 | L2 | – | + +The tests performed with this configuration require that the traffic crosses the STP under test in both directions. Consequently the test traffic flows are, regarding the routing label of messages: + +- OPC = B, DPC = C and OPC = C, DPC = B. + +### 3.2.5 Configuration D + +This configuration is adapted to the validation of all procedures concerning exclusively the points having an STP function. It is used to check the signalling route management procedures. + +Configuration D is shown in Figure 4. + +![Diagram of Configuration D showing seven signaling points (SP A through F) and their interconnections via linksets L1 through L8. SP A is at the top, connected to SP F via linkset L3 (dashed line) and to SP B via linkset L1 (dashed line). SP A is also connected to SP C via linkset L2. SP B is connected to SP C via linkset L4. SP B is connected to SP D via linkset L5. SP C is connected to SP D via linkset L6. SP C is connected to SP E via linkset L7. SP D is connected to SP E via linkset L8. A dashed line separates the top part (SP A, F) from the bottom part (SP B, C, D, E). The text 'T1157770-02' is at the bottom right of the diagram.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +Diagram of Configuration D showing seven signaling points (SP A through F) and their interconnections via linksets L1 through L8. SP A is at the top, connected to SP F via linkset L3 (dashed line) and to SP B via linkset L1 (dashed line). SP A is also connected to SP C via linkset L2. SP B is connected to SP C via linkset L4. SP B is connected to SP D via linkset L5. SP C is connected to SP D via linkset L6. SP C is connected to SP E via linkset L7. SP D is connected to SP E via linkset L8. A dashed line separates the top part (SP A, F) from the bottom part (SP B, C, D, E). The text 'T1157770-02' is at the bottom right of the diagram. + +NOTE – The SPs E, D and F do not have an STP function. + +**Figure 4/Q.782 – Configuration D** + +Configuration D, Table 4, is used only to check the signalling route management: transfer prohibited and transfer allowed procedures. Consequently, all linksets of this configuration have only one signalling link. + +**Table 4/Q.782 – Routing rules in configuration D** + +| → | A | B | C | D | E | F | +|---|--------|--------|--------|--------|--------|-----| +| A | – | L1, L2 | L2, L1 | L1, L2 | L1, L2 | L3 | +| B | L1, L4 | – | L4 | L5, L4 | L6, L4 | L1 | +| C | L2, L4 | L4 | – | L8, L4 | L7, L4 | L2 | +| D | Any | | | – | Any | | +| E | Any | | | | – | Any | +| F | L3 | L3 | L3 | L3 | L3 | – | + +The STP under test is linked to the external world with three linksets: one terminal linkset (to an SP without STP function) and two inter STP linksets. This structure is minimal to check the various aspects of the broadcasting of TFPs and TFAs: + +- TFPs or TFAs concerning several destinations; +- TFPs or TFAs to several destinations. + +This configuration includes points D and E. This is necessary in order to check the sending of TFP on an alternative linkset: in A, the routing rules are such that the linksets 1 and 2 are used to reach D using normal/alternative routing and to reach E using load sharing routing (sending of TFP in the first case and not in the second). + +The tests performed with this configuration, which check the signalling route procedures, require that the test traffic uses the concerned signalling routes. The test traffic flows used in this Recommendation are, regarding the routing label messages: + +- OPC = F, DPC = D    OPC = D, DPC = F +- OPC = F, DPC = E    OPC = E, DPC = F +- OPC = A, DPC = D    OPC = A, DPC = E    OPC = A, DPC = F + +# 4 Test list + +All tests with the indication "\*" are validation and compatibility tests. The tests without asterisk are validation tests only. + +- 1 *Signalling link management* + - \* 1.1 First signalling link activation + - \* 1.2 Signalling linkset deactivation + - \* 1.3 Signalling linkset activation +- 2 *Signalling message handling* + - 2.1 Message received with an invalid SSF (discrimination function) + - 2.2 Message received with an invalid DPC (discrimination function) + - 2.3 Message received with an invalid SI (distribution function) + - 2.4 Load sharing within a linkset + - \* 2.4.1 All links available + - 2.4.2 With one link unavailable + - 2.5 Load sharing between linksets + - \* 2.5.1 Between two linksets + - 2.5.2 Between three linksets + - 2.5.3 Between three linksets and one route unavailable + - 2.5.4 Between three linksets and one linkset unavailable + - 2.6 Inaccessible destination + - 2.6.1 Due to a linkset failure + - 2.6.2 Due to a route failure + - 2.6.3 Due to a linkset and a route failure + - \* 2.7 Message transfer function +- 3 *Changeover* + - 3.1 Changeover initiated at one side of a linkset (COO $\leftrightarrow$ COA) + - 3.2 Changeover initiated at the both ends at the same time (COO $\leftrightarrow$ COO) + - 3.3 Changeover on expiration of timer T2 (COO or ECO $\rightarrow$ –) + - 3.4 Unreasonable FSN in COO/COA + - 3.5 Reception of a changeover acknowledgement without sending a changeover order (– $\leftarrow$ COA or ECA) + +- 3.6 Reception of an additional changeover order ( $\leftarrow$ COO or ECO) +- 3.7 Emergency changeover at one side of a linkset (COO $\leftrightarrow$ ECA) +- 3.8 Emergency changeover at one side of a linkset (COO $\leftrightarrow$ ECO) +- 3.9 Emergency changeover at one side of a linkset (ECO $\leftrightarrow$ COA) +- 3.10 Emergency changeover at both sides of a linkset (ECO $\leftrightarrow$ ECA) +- 3.11 Emergency changeover at one side of a linkset (ECO $\leftrightarrow$ COO) +- 3.12 Emergency changeover initiated at the both ends at the same time (ECO $\leftrightarrow$ ECO) +- 3.13 Reactivation of a link during a changeover procedure +- 3.14 Simultaneous changeover +- 3.15 Changeover to several alternative links within a linkset +- \* 3.16 Changeover to another linkset with the adjacent SP accessible +- \* 3.17 Changeover to another linkset with the adjacent SP inaccessible +- 3.18 Changeover to two linksets +- 3.19 Changeover due to various reasons +- 3.20 Changeover as compatibility test +- 3.21 Reception of a changeover order on an available link + +# 4 *Changeback* + +- \* 4.1 Changeback within a linkset +- 4.2 Additional CBA +- 4.3 Additional CBD +- 4.4 No acknowledgement to first CBD +- 4.5 No acknowledgement of repeat changeback declaration +- 4.6 Simultaneous changeback +- 4.7 Changeback from several alternative links within a linkset +- \* 4.8 Changeback from another linkset +- 4.9 Changeback from two linksets +- 4.10 Changeback due to various reasons +- \* 4.11 Time controlled diversion procedure + +## \* 5 *Forced rerouting* + +###### \* 6 *Controlled rerouting* + +# 7 *Management inhibiting* + +- 7.1 Inhibition of a link + - \* 7.1.1 Available link + - \* 7.1.2 Unavailable link + +- 7.2 Inhibition not permitted + - \* 7.2.1 Local reject on an available link + - \* 7.2.2 Local reject on an unavailable link + - 7.2.3 Sending of LID + - 7.2.4 Reception of LID +- 7.3 Expiration of T14 + - 7.3.1 On an available link + - 7.3.2 On an unavailable link +- 7.4 Additional inhibition messages (LIA, LID, LIN) +- 7.5 Inhibition asked by the both ends of a link +- 7.6 Manual uninhibition of a link + - \* 7.6.1 With changeback + - \* 7.6.2 Without changeback +- 7.7 Expiration of T12 +- \* 7.8 Not possible uninhibition +- 7.9 Automatic uninhibition of a link +- 7.10 Forced uninhibition of a link + - 7.10.1 Sending of LFU + - 7.10.2 Reception of LFU +- 7.11 Expiration of T13 +- 7.12 Additional uninhibition messages (LUA, LUN, LFU) +- 7.13 Uninhibition at one side after test 7.5 +- 7.14 Automatic uninhibition after test 7.5 +- 7.15 Automatic uninhibition with two links inhibited +- 7.16 Reception of traffic on an inhibited link +- 7.17 Management inhibiting test + - \* 7.17.1 Normal procedure + - 7.17.2 Reception of an LLT or LRT on an uninhibited link + - 7.17.3 Reception of an LLT on a link locally inhibited + - 7.17.4 Reception of an LRT on a link remotely inhibited +- 8 *Signalling traffic flow control* + - 8.1 Reception of a TFC + - 8.2 Sending of TFCs + - 8.3 Reception of an UPU + - 8.4 Sending of an UPU + +# 9 *Signalling route management* + +### 9.1 Sending of a TFP on an alternative route + +- \* 9.1.1 Failure of normal linkset +- \* 9.1.2 On reception of a TFP + +### 9.2 Broadcast of TFPs + +- \* 9.2.1 On one linkset failure +- \* 9.2.2 On multiple failures + +### 9.3 Reception of a message for an inaccessible destination + +### 9.4 Sending of a TFA on an alternative route + +- \* 9.4.1 Recovery of normal linkset +- \* 9.4.2 On reception of a TFA + +### 9.5 Broadcast of TFAs + +- \* 9.5.1 On one linkset recovery +- \* 9.5.2 Various reasons + +### 9.6 Periodic sending of Signalling-Route-Set-Test (SRST) messages + +### 9.7 Reception of a signalling-route-set-test message + +# 10 *Signalling point restart* + +### 10.1 Recovery of a linkset (SP A does not have the STP function) + +- \* 10.1.1 With use of point restart procedure +- 10.1.2 Not resulting in the signalling point restart procedure + +### 10.2 Recovery of a linkset (SP A has the STP function) + +- \* 10.2.1 Not resulting in the signalling point restart procedure +- 10.2.2 Not resulting in the signalling point restart procedure + +### 10.3 An adjacent signalling point becomes accessible via another signalling point (SP A does not have an STP function) + +### 10.4 An adjacent signalling point becomes accessible via another signalling point (SP A has STP function) + +- \* 10.5 Restart of an SP having no STP function + +- \* 10.6 Restart of an SP having STP function + +### 10.7 Reception of an unexpected TRA + +- 10.7.1 In an SP having no STP function +- 10.7.2 In an SP having the STP function + +## 11 *Traffic test* + +## 12 *Signalling link test* + +- \* 12.1 After activation of a link +- 12.2 No acknowledgement to first SLTM +- 12.3 No acknowledgement to second SLTM + +- 12.4 Unreasonable field in an SLTA +- 12.5 Reception of an SLTM in an attempt state + +- \* 12.6 Additional SLTA, SLTM + +## 13 *Invalid messages* + +- 13.1 Invalid H0-H1 in a signalling network management message +- 13.2 Invalid changeover messages +- 13.3 Invalid changeback messages +- 13.4 Invalid changeback code +- 13.5 Invalid inhibition messages +- 13.6 Invalid transfer control messages +- 13.7 Invalid signalling route management messages +- 13.8 Invalid signalling-route-set-test messages +- 13.9 Invalid traffic restart allowed message +- 13.10 Invalid H0-H1 in a signalling network testing and maintenance message +- 13.11 Invalid signalling link test messages +- 13.12 Invalid user part unavailable messages + +# **5 Test descriptions** + +## **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------|--|------|------|--|------|--|--|-------------------|-------------------|--|--|--|---|--------------|--------------|---|--|--------------|---|--|--|---|--------------|----------------|--|--|-----------------|---|--|--|---|-----------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 1.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 3/Q.704     Fig. 7, Fig. 36, Fig. 37, Fig. 38 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling link management | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: First signalling link activation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To put into service a signalling linkset with 1 signalling link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling links deactivated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
1-1     :Activate
1-1     :Activate
← 1-1     SLTM
1-1     SLTA →
1-1     SLTM →
← 1-1     SLTA
:Start traffic
1-1     TRAFFIC →
← 1-1     TRAFFIC
:Wait
:Stop traffic

NOTE – The MTP restart procedure is not described in this test and is checked in others tests.

| | | SP A | | SP B | Link | | Link | | | 1-1     :Activate | 1-1     :Activate | | | | ← | 1-1     SLTM | 1-1     SLTA | → | | 1-1     SLTM | → | | | ← | 1-1     SLTA | :Start traffic | | | 1-1     TRAFFIC | → | | | ← | 1-1     TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 1-1     :Activate | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1     :Activate | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1     SLTM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1     SLTA | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1     SLTM | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1     SLTA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1     TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the signalling link becomes available. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check the reception and sending of variable length messages on the activated linkset from/to the SP at the other end of this linkset (and, in case of VAT, from/to other SP crossing the SP at the other end of this linkset). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that, after the alignment, the level 2 does not send any message received before or during the deactivation. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that all messages are correctly received (no loss of messages, no duplication and no missequencing). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Repeat the test with different SLC values. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-----------------| +| TEST NUMBER: 1.2 | | PAGE: 1 of 1 | +| REFERENCE: clause 3/Q.704   Fig. 7, Fig. 36, Fig. 37, Fig. 38 | | | +| TITLE: Signalling link management | | | +| SUBTITLE: Signalling linkset deactivation | | | +| PURPOSE: To remove from service a signalling linkset with 1 signalling link | | | +| PRE-TEST CONDITIONS: One signalling link (1-1) activated | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A

Link
1-1   :Deactivate
SP B

Link
| | | +| TEST DESCRIPTION | | | +| 1. | Check that the signalling linkset becomes unavailable. | | + +###### **MTP Level 3** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 1.3 | | PAGE: 1 of 1 | +| REFERENCE: clause 3 and 12.2.4.1/Q.704      Fig. 7, Fig. 36, Fig. 37, Fig. 38 | | | +| TITLE: Signalling link management | | | +| SUBTITLE: Signalling linkset activation | | | +| PURPOSE: To put into service a signalling linkset with 4 signalling links | | | +| PRE-TEST CONDITIONS: Signalling links deactivated | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE: | | | +| SP A | | SP B | +| Link | | Link | +| 1-1 :Activate | | 1-1 :Activate | +| 1-2 :Activate | | 1-2 :Activate | +| 1-3 :Activate | | 1-3 :Activate | +| 1-4 :Activate | | 1-4 :Activate | +| :Start traffic | | | +| 1-1 TRAFFIC | —————→ | | +| | ←————— | 1-1 TRAFFIC | +| 1-2 TRAFFIC | —————→ | | +| | ←————— | 1-2 TRAFFIC | +| 1-3 TRAFFIC | —————→ | | +| | ←————— | 1-3 TRAFFIC | +| 1-4 TRAFFIC | —————→ | | +| | ←————— | 1-4 TRAFFIC | +| :Wait | | | +| :Stop traffic | | | +| NOTE – This test describes the activation of a linkset. The signalling link activation order is given simultaneously to all signalling links of the signalling linkset (see 12.2.4.1/Q.704). However, depending on which order the links are aligned, changeback procedures will be performed. This test does not describe the transitory states (signalling link test, changeback and restart procedures are checked in other tests). | | | +| TEST DESCRIPTION | | | +| 1. | Check that the signalling links become available and start traffic between A and B (and A and C in VAT). | | +| 2. | Check the reception and sending of variable length messages on the activated linkset from/to the SP at the other end of this linkset (and, in case of VAT, from/to other SP crossing the SP at the other end of this linkset). | | +| 3. | Check that, after the alignment, the level 2 does not send any message received before or during the deactivation. | | +| 4. | Check that all messages are correctly received (no loss of messages, no duplication and no missequencing). | | +| 5. | Stop traffic. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|------------------------------------|------|--|------|----------|--|----------|--|---|------------------------------------| +| TEST NUMBER: 2.1 | | PAGE: 1 of 1 | | | | | | | | | | +| REFERENCE: clause 3 and 2.4/Q.704 Fig. 24 | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | +| SUBTITLE: Message received with an invalid SSF (discrimination function) | | | | | | | | | | | | +| PURPOSE: To check the response to a message with an invalid SSF | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling linkset activated | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
← 1–1 :Invalid SLTM
(invalid SSF)
| | | SP A | | SP B |
Link | |
Link | | ← | 1–1 :Invalid SLTM
(invalid SSF) | +| SP A | | SP B | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | +| | ← | 1–1 :Invalid SLTM
(invalid SSF) | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | +| 1. | Send an SLTM with an erroneous SSF. | | | | | | | | | | | +| 2. | Check that no response is received. | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|------|--|------|------|--|------|--|---|-------------------------------------|------------|---|--------------------------------------------------| +| TEST NUMBER: 2.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | +| REFERENCE: clause 2/Q.704    Fig. 24, Fig. 26 | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | +| SUBTITLE: Message received with an invalid DPC | | | | | | | | | | | | | | | +| PURPOSE: To check the response to a message with an invalid DPC | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling linkset activated | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
← 1–1 :Invalid ECO
(erroneous DPC)
1–1    TFP → (only if the tested point A has an STP function)




















| | | SP A | | SP B | Link | | Link | | ← | 1–1 :Invalid ECO
(erroneous DPC) | 1–1    TFP | → | (only if the tested point A has an STP function) | +| SP A | | SP B | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | +| | ← | 1–1 :Invalid ECO
(erroneous DPC) | | | | | | | | | | | | | +| 1–1    TFP | → | (only if the tested point A has an STP function) | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +| 1. | Send a ECO message with an erroneous DPC. | | | | | | | | | | | | | | +| 2. | Check that no response is received if the tested point does not have an STP function. If the tested point has the STP function, check that a TFP is received. | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------| +| TEST NUMBER: 2.3 | | PAGE: 1 of 1 | +| REFERENCE: 2.4/Q.704 Fig. 24, Fig. 25 | | | +| TITLE: Signalling message handling | | | +| SUBTITLE: Message received with an invalid SI (distribution function) | | | +| PURPOSE: To check the response to a message received with an invalid SI | | | +| PRE-TEST CONDITIONS: Signalling linkset activated | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A

Link
SP B

Link
← 1–1 :Invalid SLTM
      :(invalid SI)
| | | +| TEST DESCRIPTION | | | +|
  1. 1. Send an SLTM message with an invalid SI.
  2. 2. Check that no response is received except perhaps a UPU (cause unequipped) when the SI used does not exist.
| | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|----------|--|----------|----------------|--|--|-------------|------------------------|--|--|------------------------|-------------|-------------|------------------------|--|--|------------------------|-------------|-------------|------------------------|--|--|------------------------|-------------|-------------|------------------------|--|--|------------------------|-------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 2.4.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 2.3/Q.704 Fig. 26 4.4/Q.705 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Load sharing within a linkset – All links available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the load sharing within a linkset with all the links available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling linkset activated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–1 TRAFFIC —————————————————————>
<————————————————————— 1–1 TRAFFIC
1–2 TRAFFIC —————————————————————>
<————————————————————— 1–2 TRAFFIC
1–3 TRAFFIC —————————————————————>
<————————————————————— 1–3 TRAFFIC
1–4 TRAFFIC —————————————————————>
<————————————————————— 1–4 TRAFFIC

:Wait
:Stop traffic










| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–1 TRAFFIC | —————————————————————> | | | <————————————————————— | 1–1 TRAFFIC | 1–2 TRAFFIC | —————————————————————> | | | <————————————————————— | 1–2 TRAFFIC | 1–3 TRAFFIC | —————————————————————> | | | <————————————————————— | 1–3 TRAFFIC | 1–4 TRAFFIC | —————————————————————> | | | <————————————————————— | 1–4 TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–3 TRAFFIC | —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— | 1–3 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–4 TRAFFIC | —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— | 1–4 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B (and C in VAT) for all SLS. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Stop traffic, check that the messages have been transmitted on the correct link in accordance with the SLS field. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that there was no loss of messages, no duplication and no missequencing. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|----------|--|----------|----------------|--|--|-------------|---|--|--|---|-------------|-------------|---|--|--|---|-------------|-------------|---|--|--|---|-------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 2.4.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 2.3/Q.704 Fig. 26 4.4/Q.705 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Load sharing within a linkset – With one link unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the load sharing within a linkset when one link is unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1–3 deactivated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–1 TRAFFIC →
← 1–1 TRAFFIC
1–2 TRAFFIC →
← 1–2 TRAFFIC
1–4 TRAFFIC →
← 1–4 TRAFFIC

:Wait
:Stop traffic














| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–1 TRAFFIC | → | | | ← | 1–1 TRAFFIC | 1–2 TRAFFIC | → | | | ← | 1–2 TRAFFIC | 1–4 TRAFFIC | → | | | ← | 1–4 TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–4 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–4 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start the traffic to B and C for all SLS, wait and stop. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the messages have been transmitted on the correct link in accordance with the SLS field on the remaining links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP Level 3 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|------|------|------|------|------|------|------|------|----------------|--|--|--|-------------|---|-------|--|--|---|-------|-------------|-------------|---|-------|--|--|---|-------|-------------|-------------|---|-------|--|-------------|---|-------|--|-----------|--|--|--|---------------|--|--|--| +| TEST NUMBER: 2.5.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 2.3/Q.704 Fig. 26 4.4/Q.705 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Load sharing between linksets – Between two linksets | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the load sharing between two linksets under normal conditions | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: All linksets and routes available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP E
Link Link Link Link
:Start traffic
3–1 TRAFFIC → 7–1 →
← 3–1 ← 7–1 TRAFFIC
3–2 TRAFFIC → 7–1 →
← 3–2 ← 7–1 TRAFFIC
2–1 TRAFFIC → 6–1 →
2–1 TRAFFIC → 6–1 →

:Wait
:Stop traffic
| | | | SP A | SP B | SP C | SP E | Link | Link | Link | Link | :Start traffic | | | | 3–1 TRAFFIC | → | 7–1 → | | | ← | 3–1 ← | 7–1 TRAFFIC | 3–2 TRAFFIC | → | 7–1 → | | | ← | 3–2 ← | 7–1 TRAFFIC | 2–1 TRAFFIC | → | 6–1 → | | 2–1 TRAFFIC | → | 6–1 → | |
:Wait | | | | :Stop traffic | | | | +| SP A | SP B | SP C | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TRAFFIC | → | 7–1 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 3–1 ← | 7–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–2 TRAFFIC | → | 7–1 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 3–2 ← | 7–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1 TRAFFIC | → | 6–1 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1 TRAFFIC | → | 6–1 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start the traffic to E for all SLS. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Stop the traffic and check that the messages have been transmitted on the correct linkset in accordance with the SLS and DPC. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that there was no loss of messages, no duplication and no missequencing. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------|------|------|------|------|------|------|------|----------------|--|--|--|----------------|--------------------------|--|--|--|--------------------------|--|----------------|----------------|--------------------------|--|--|--|--------------------------|--|----------------|----------------|----------|--------------|--|----------------|----------|--------------|--|----------------|----------|--------------|--|----------------|----------|--------------|--|-------|--|--|--|---------------|--|--|--| +| TEST NUMBER: 2.5.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 2.3/Q.704    Fig. 26    4.4/Q.705 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Load sharing between linksets – Between three linksets | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the load sharing between three linksets under normal conditions | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: All linksets and routes available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP E
Link Link Link Link
:Start traffic
1-1    TRAFFIC ———————————————————————>
<——————————————————————— 1-1    TRAFFIC
1-2    TRAFFIC ———————————————————————>
<——————————————————————— 1-2    TRAFFIC
3-1    TRAFFIC ———————> 8-1 ———————>
3-2    TRAFFIC ———————> 8-1 ———————>
2-1    TRAFFIC ———————> 5-1 ———————>
2-2    TRAFFIC ———————> 5-1 ———————>
:Wait
:Stop traffic
| | | SP A | SP B | SP C | SP E | Link | Link | Link | Link | :Start traffic | | | | 1-1    TRAFFIC | ———————————————————————> | | | | <——————————————————————— | | 1-1    TRAFFIC | 1-2    TRAFFIC | ———————————————————————> | | | | <——————————————————————— | | 1-2    TRAFFIC | 3-1    TRAFFIC | ———————> | 8-1 ———————> | | 3-2    TRAFFIC | ———————> | 8-1 ———————> | | 2-1    TRAFFIC | ———————> | 5-1 ———————> | | 2-2    TRAFFIC | ———————> | 5-1 ———————> | | :Wait | | | | :Stop traffic | | | | +| SP A | SP B | SP C | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    TRAFFIC | ———————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————————————————————— | | 1-1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC | ———————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————————————————————— | | 1-2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-1    TRAFFIC | ———————> | 8-1 ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-2    TRAFFIC | ———————> | 8-1 ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-1    TRAFFIC | ———————> | 5-1 ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-2    TRAFFIC | ———————> | 5-1 ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start the traffic to D for all SLS. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Stop the traffic and check that the messages have been transmitted on the correct linkset and on the correct link in accordance with the SLS. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that there was no loss of messages, no duplication and no missequencing. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|--------------------------------|------|-------------------|----------------|------|------|--|------|------|--|------|------|--|------|----------------|--|--|--|--|--|-----|---------|--------------------------------|--|--|--|--|--|--------------------------------|--|--|----------------|-----|---------|--------------------------------|--|--|--|--|--|--------------------------------|--|--|----------------|-----|---------|----------|-----|-------------------|--|-----|---------|----------|-----|-------------------|--|-------|--|--|--|--|--|---------------|--|--|--|--|--| +| TEST NUMBER: 2.5.3 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 2.3/Q.704    Fig. 26    4.4/Q.705 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Load sharing between linksets – Between three linksets and one route unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the load sharing between three linksets when one route is unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linksets 4 and 8 unavailable (TFP, PC = D from C to A) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP E
Link Link Link Link
:Start traffic
1–1 TRAFFIC —————————————————————————————>
<————————————————————————————— 1–1    TRAFFIC
1–2 TRAFFIC —————————————————————————————>
<————————————————————————————— 1–2    TRAFFIC
2–1 TRAFFIC ———————> 5–1 ————————————————>
2–2 TRAFFIC ———————> 5–1 ————————————————>
:Wait
:Stop traffic















| | | | SP A | | SP B | SP C | | SP E | Link | | Link | Link | | Link | :Start traffic | | | | | | 1–1 | TRAFFIC | —————————————————————————————> | | | | | | <————————————————————————————— | | | 1–1    TRAFFIC | 1–2 | TRAFFIC | —————————————————————————————> | | | | | | <————————————————————————————— | | | 1–2    TRAFFIC | 2–1 | TRAFFIC | ———————> | 5–1 | ————————————————> | | 2–2 | TRAFFIC | ———————> | 5–1 | ————————————————> | | :Wait | | | | | | :Stop traffic | | | | | | +| SP A | | SP B | SP C | | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 | TRAFFIC | —————————————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | <————————————————————————————— | | | 1–1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | TRAFFIC | —————————————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | <————————————————————————————— | | | 1–2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1 | TRAFFIC | ———————> | 5–1 | ————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–2 | TRAFFIC | ———————> | 5–1 | ————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start the traffic for all SLS, wait and stop. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the traffic to D via C has been shared on the remaining linksets. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-----------------|------|----------|-------------|------|------|--|------|------|--|------|------|--|------|----------------|--|--|--|--|--|-----|---------|----------|-----|----------|--|-----|---------|----------|-----|----------|--|-----|---------|----------|-----|----------|--|--|--|----------|-----|----------|-------------|-----|---------|----------|-----|----------|--|--|--|----------|-----|----------|-------------|-------|--|--|--|--|--|---------------|--|--|--|--|--| +| TEST NUMBER: 2.5.4 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 2.3/Q.704 Fig. 26 4.4/Q.705 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Load sharing between linksets – Between three linksets and one linkset unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the load sharing between two linksets after the unavailability of the third linkset | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset 1 deactivated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP D
Link Link Link Link
:Start traffic
3-1 TRAFFIC ———————> 8-1 ———————>
3-2 TRAFFIC ———————> 8-1 ———————>
2-1 TRAFFIC ———————> 5-1 ———————>
<——————— 2-1 <——————— 5-1 TRAFFIC
2-2 TRAFFIC ———————> 5-1 ———————>
<——————— 2-2 <——————— 5-1 TRAFFIC
:Wait
:Stop traffic















| | | | SP A | | SP B | SP C | | SP D | Link | | Link | Link | | Link | :Start traffic | | | | | | 3-1 | TRAFFIC | ———————> | 8-1 | ———————> | | 3-2 | TRAFFIC | ———————> | 8-1 | ———————> | | 2-1 | TRAFFIC | ———————> | 5-1 | ———————> | | | | <——————— | 2-1 | <——————— | 5-1 TRAFFIC | 2-2 | TRAFFIC | ———————> | 5-1 | ———————> | | | | <——————— | 2-2 | <——————— | 5-1 TRAFFIC | :Wait | | | | | | :Stop traffic | | | | | | +| SP A | | SP B | SP C | | SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-1 | TRAFFIC | ———————> | 8-1 | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-2 | TRAFFIC | ———————> | 8-1 | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-1 | TRAFFIC | ———————> | 5-1 | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | <——————— | 2-1 | <——————— | 5-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-2 | TRAFFIC | ———————> | 5-1 | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | <——————— | 2-2 | <——————— | 5-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start the traffic for all SLS to D, wait and stop. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the traffic has been shared on the remaining linksets. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 2.6.1 | | PAGE: 1 of 1 | +| REFERENCE: Q.704 Fig. 26 | | | +| TITLE: Signalling message handling | | | +| SUBTITLE: Inaccessible destination – Due to a linkset failure | | | +| PURPOSE: To check the signalling message handling when a destination becomes inaccessible due to a linkset failure | | | +| PRE-TEST CONDITIONS: Signalling linkset with one link available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

:Start traffic

1-1 TRAFFIC
→ ←
1-1 TRAFFIC

1-1 :Deactivate

| | | +| TEST DESCRIPTION | | | +| 1. | Start the traffic for all SLS to B and C. | | +| 2. | Deactivate the last link 1-1 and check that the linkset becomes unavailable. | | +| 3. | Check that the SPs B and C become inaccessible. | | +| 4. | Check that all messages stored or received after the unavailability of the linkset are discarded. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|-------------|--------|--|--|-------|-------------|-------------|--------|--|--|-------|-------------|-------------|--------|--|--|-------|-------------|-------------|--------|--|--|-------|-------------|--|-------|------------------| +| TEST NUMBER: 2.6.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.704 Fig. 26 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Inaccessible destination – Due to a route failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the signalling message handling when a destination becomes inaccessible on reception of a TFP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: All links and routes available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP ASP B
LinkLink
:Start traffic
1-1 TRAFFIC—————→
←————1-1 TRAFFIC
1-2 TRAFFIC—————→
←————1-2 TRAFFIC
1-3 TRAFFIC—————→
←————1-3 TRAFFIC
1-4 TRAFFIC—————→
←————1-4 TRAFFIC
←————1- X TFP, PC = C
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1 TRAFFIC | —————→ | | | ←———— | 1-1 TRAFFIC | 1-2 TRAFFIC | —————→ | | | ←———— | 1-2 TRAFFIC | 1-3 TRAFFIC | —————→ | | | ←———— | 1-3 TRAFFIC | 1-4 TRAFFIC | —————→ | | | ←———— | 1-4 TRAFFIC | | ←———— | 1- X TFP, PC = C | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-3 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-3 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-4 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-4 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1- X TFP, PC = C | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start the traffic to B and C for all SLS. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Provoke the sending of a TFP (PC = C) from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the SP C becomes inaccessible. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that all messages stored or received after the inaccessibility have been discarded. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Check that traffic to B has not been disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**MTP Level 3** + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------| +| TEST NUMBER: 2.6.3 | | PAGE: 1 of 1 | +| REFERENCE: Q.704 Fig. 26 | | | +| TITLE: Signalling message handling | | | +| SUBTITLE: Inaccessible destination – Due to a linkset and a route failure | | | +| PURPOSE: To check the signalling message handling when a destination becomes inaccessible due to a linkset and a route failure | | | +| PRE-TEST CONDITIONS: Linkset 4 unavailable | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: ALL | + +![](318886a86a1dcc59e1fc83db6f157c60_img.jpg) + +MESSAGE SEQUENCE: + +``` + + SP A SP B SP C SP • + + Link Link Link +:Start traffic +1–1, 2 TRAFFIC <———————————————————————————————————————————————————————————————> SP D +3–1 TRAFFIC —————————————————————————————————————> To D and E + <————————————————————————————————————— 3–1 TRAFFIC (from E) +3–2 TRAFFIC —————————————————————————————————————> To D and E + <————————————————————————————————————— 3–2 TRAFFIC (from E) +2–1 TRAFFIC ———————————————> To D and E +2–2 TRAFFIC ———————————————> To D and E + 7–1 :Deactivate + <————————————————————————————————————— 3–X TFP, PC = E +2–1 TRAFFIC ———————————————> To D and E + <——————————————— 2–1 TRAFFIC + (from E) +2–2 TRAFFIC ———————————————> To D and E + <——————————————— 2–2 TRAFFIC + (from E) +2–1 :Deactivate +2–2 :Deactivate +1–1, 2 TRAFFIC <———————————————————————————————————————————————————————————————> SP D +:Wait +:Stop traffic + +``` + +NOTE – The transitory states (signalling network management procedures) are not described in this test, which checks only the signalling message handling. + +| TEST DESCRIPTION | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1. | Start the traffic to the SPs D and E for all SLS. | +| 2. | Initiate the sending of a TFP (DPC = E) from SP C to SP A, check that the traffic to E is routed via B and check that the traffic to D is not disturbed. | +| 3. | Deactivate the linkset 2 and check that the destination E becomes inaccessible. Stop traffic. | +| 4. | Check that all messages stored or received during the inaccessibility have been discarded. | + +ITU-T Rec. Q.782 (04/2002) 27 + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|------|------|------|--|--|--|------|------|------|----------------|--|--|------------------|----------------|----------|--|-------------------|--------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 2.7 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 2/Q.704     Fig. 26 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling message handling | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Message transfer function | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the transfer function in an STP | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: All links available | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: C | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP B SP A SP C
Link Link Link
:Start traffic
1–1, 2   TRAFFIC ———————>   2–1 ———————>
<———————   1–1, 2 <———————   TRAFFIC
:Wait
:Stop traffic
















NOTE – The traffic used in this test is in conformance with the traffic model presented in ITU-T Rec. Q.706.

| | | SP B | SP A | SP C | | | | Link | Link | Link | :Start traffic | | | 1–1, 2   TRAFFIC | ———————>   2–1 | ———————> | | <———————   1–1, 2 | <———————   TRAFFIC | :Wait | | | :Stop traffic | | | +| SP B | SP A | SP C | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2   TRAFFIC | ———————>   2–1 | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————   1–1, 2 | <———————   TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic between B and C in both directions via A. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that transfer function is correctly performed. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that there was no loss of messages, no duplication and no missequencing. Check that the information field of these messages has not been corrupted. | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------|--|------|------|--|------|----------------|--|--|----------------|-------------|--|--|-------------|----------------|----------------|-------------|--|--|-------------|----------------|---------------------------------------------|--|--|---------------------|-------------|--|--|-------------|---------------------|---------------------------|-------------|--|--|-------------|---------------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Changeover initiated at one side of a linkset (COO $\leftrightarrow$ COA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the normal changeover procedure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1-1    TRAFFIC ——————————→
←—————————— 1-1    TRAFFIC
1-2    TRAFFIC ——————————→
←—————————— 1-2    TRAFFIC
1-1    :Deactivate (MML command or failure)
1-2    COO, SLC 1-1 ——————————→
←—————————— 1-2    COO, SLC 1-1
1-2    TRAFFIC (from 1-1) ——————————→
←—————————— 1-2    TRAFFIC (from 1-1)
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1    TRAFFIC | ——————————→ | | | ←—————————— | 1-1    TRAFFIC | 1-2    TRAFFIC | ——————————→ | | | ←—————————— | 1-2    TRAFFIC | 1-1    :Deactivate (MML command or failure) | | | 1-2    COO, SLC 1-1 | ——————————→ | | | ←—————————— | 1-2    COO, SLC 1-1 | 1-2    TRAFFIC (from 1-1) | ——————————→ | | | ←—————————— | 1-2    TRAFFIC (from 1-1) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    COO, SLC 1-1 | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    COO, SLC 1-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC (from 1-1) | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC (from 1-1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all the links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate link 1-1, check that a COO is sent (from A) for 1-1 on 1-2 and respond with a COA within T2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the time between the deactivation and the sending of the COO is inside the specified value (see ITU-T Rec. Q.706). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that the traffic from link 1-1 is changed over to 1-2 and check that the traffic normally carried by 1-2 is passed over to 1-2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Stop traffic and check it has been received correctly (no lost messages, no duplication and no missequencing). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Repeat the test by sending the COO from B (instead of A). In addition, check that the time between the reception of the COO and the sending of the COA is inside the specified value (see ITU-T Rec. Q.706). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | NOTE – In this case, A might also send a COO/ECO to B as well as the COA. As a consequence, B would then return a COA/ECA to A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|--|--|--| +| TEST NUMBER: 3.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704 Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Changeover initiated at both ends at the same time (COO ↔ COO) | | | | | | +| PURPOSE: To check the changeover procedure when the changeover is initiated at the both ends simultaneously | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | +| | ←———— | 1-1 TRAFFIC | | | | +| 1-2 TRAFFIC | —————→ | | | | | +| | ←———— | 1-2 TRAFFIC | | | | +| 1-1 :Deactivate (MML command or failure) | | | | | | +| 1-2 COO (SLC 1-1) | —————→ | | | | | +| | ←———— | 1-2 COO (SLC 1-1) | | | | +| 1-2 COA (SLC 1-1) | —————→ | | | | | +| | ←———— | 1-2 COA (SLC 1-1) | | | | +| 1-2 TRAFFIC (from 1-1) | —————→ | | | | | +| | ←———— | 1-2 TRAFFIC (from 1-1) | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start the traffic to B and C on all the links. | | | | | +| 2. | Deactivate the link 1-1, check that the COOs and COAs for 1-1 are received on link 1-2. | | | | | +| 3. | Check that the traffic from link 1-1 changed over to 1-2 and stop traffic. | | | | | +| 4. | Repeat the test without sending of COA from SP B to SP A. | | | | | + +###### **MTP Level 3** + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 3.3 | | PAGE: 1 of 1 | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | +| TITLE: Changeover | | | +| SUBTITLE: Changeover on expiration of timer T2 (COO or ECO → –) | | | +| PURPOSE: To check the changeover procedure when no COA is received in response of a COO previously sent | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

:Start traffic

1–1   TRAFFIC ——————————————————————————————————→
←—————————————————————————————————— 1–1   TRAFFIC
1–2   TRAFFIC ——————————————————————————————————→
←—————————————————————————————————— 1–2   TRAFFIC

1–1   :Deactivate (MML command or failure)

1–2   COO (SLC 1–1) ——————————————————————————————————→

T2
1–2   TRAFFIC (from 1–1) ——————————————————————————————————→
←—————————————————————————————————— 1–2   TRAFFIC (from 1–1)

:Wait

:Stop traffic

| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on all the links. | | +| 2. | Deactivate link 1–1, check that a COO is received for 1–1 on link 1–2. | | +| 3. | After the expiration of T2, check that the changeover procedure is performed. | | +| 4. | Check that the duration of T2 is inside the specified range. | | +| 5. | Stop traffic and check that there was no duplication and no missequencing, some messages may be lost as the system should not perform retrieval. | | +| 6. | Repeat the test but replacing COO by ECO. | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|--|--|--| +| TEST NUMBER: 3.4 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704      Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Unreasonable FSN in COO/COA | | | | | | +| PURPOSE: To check the changeover procedure on reception of a COO/COA containing an unreasonable FSN | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1    TRAFFIC | —————→ | | | | | +| | ←———— | 1-1    TRAFFIC | | | | +| 1-2    TRAFFIC | —————→ | | | | | +| | ←———— | 1-2    TRAFFIC | | | | +| 1-1    :Deactivate (MML command or failure) | | | | | | +| 1-2    COO, SLC 1-1 | —————→ | | | | | +| | ←———— | 1-2    COA, SLC 1-1
(unreasonable FSN) | | | | +| 1-2    TRAFFIC (from 1-1) | —————→ | | | | | +| | ←———— | 1-2    TRAFFIC (from 1-1) | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all the links. | | | | | +| 2. | Deactivate link 1-1, check that a COO is received for 1-1 on link 1-2 and respond within T2 with a COA containing an unreasonable FSN. | | | | | +| 3. | Stop traffic, check that the changeover procedure has been performed. | | | | | +| 4. | Check that there was no duplication and no missequencing. Some messages may be lost as the system should not perform retrieval. | | | | | +| 5. | Check that an indication is given by the system. | | | | | +| 6. | Repeat the test with a COO sent from B (instead COA) containing an unreasonable FSN. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|------------------|--|--|--| +| TEST NUMBER: 3.5 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704      Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Reception of a changeover acknowledgement without sending a changeover order (– ← COA or ECA) | | | | | | +| PURPOSE: To check the changeover procedure on reception of an unexpected changeover acknowledgement | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | +| | ←———— | 1-1 TRAFFIC | | | | +| 1-2 TRAFFIC | —————→ | | | | | +| | ←———— | 1-2 TRAFFIC | | | | +| | ←———— | 1-2 COA, SLC 1-1 | | | | +| 1-1 TRAFFIC | —————→ | | | | | +| | ←———— | 1-1 TRAFFIC | | | | +| 1-2 TRAFFIC | —————→ | | | | | +| | ←———— | 1-2 TRAFFIC | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all the links. | | | | | +| 2. | Send a COA for 1-1 on link 1-2, check that this message is ignored. | | | | | +| 3. | Stop traffic and check that it has been received correctly. | | | | | +| 4. | Repeat the test with an ECA instead of a COA. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------|------|--|------|----------|--|----------|----------------|--|--|----------------|------------------|--|--|------------------|----------------|--|------------------|---------------------|---------------------|------------------|--|----------------|------------------|--|--|------------------|----------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 3.6 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Reception of an additional changeover order (– ← COO or ECO) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the action of the system when a changeover order relating to a particular link is received after completion of changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with only the link 1–2 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–2    TRAFFIC ———————————————→
←——————————————— 1–2    TRAFFIC
←——————————————— 1–2    COO, SLC 1–1
1–2    ECA, SLC 1–1 ———————————————→
1–2    TRAFFIC ———————————————→
←——————————————— 1–2    TRAFFIC

:Wait
:Stop traffic















| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–2    TRAFFIC | ———————————————→ | | | ←——————————————— | 1–2    TRAFFIC | | ←——————————————— | 1–2    COO, SLC 1–1 | 1–2    ECA, SLC 1–1 | ———————————————→ | | 1–2    TRAFFIC | ———————————————→ | | | ←——————————————— | 1–2    TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2    TRAFFIC | ———————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←——————————————— | 1–2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←——————————————— | 1–2    COO, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2    ECA, SLC 1–1 | ———————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2    TRAFFIC | ———————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←——————————————— | 1–2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send a COO for 1–1 on link 1–2 and check that an ECA is received in T2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that it has been received correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat the test with an ECO instead of a COO. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------|--|------|------|--|------|----------------|--|--|----------------|-------------|--|--|-------------|----------------|----------------|-------------|--|--|-------------|----------------|---------------------------------------------|--|--|---------------------|-------------|--|--|-------------|---------------------|--|-------------|---------------------------|---------------------------|-------------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.7 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Emergency changeover at one side of a linkset (COO ↔ ECA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the emergency changeover procedure when a COO is acknowledged by an ECA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1-1    TRAFFIC ——————————→
←—————————— 1-1    TRAFFIC
1-2    TRAFFIC ——————————→
←—————————— 1-2    TRAFFIC
1-1    :Deactivate (MML command or failure)
1-2    COO, SLC 1-1 ——————————→
←—————————— 1-2    ECA, SLC 1-1
←—————————— 1-2    TRAFFIC (from 1-1)
1-2    TRAFFIC (from 1-1) ——————————→
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1    TRAFFIC | ——————————→ | | | ←—————————— | 1-1    TRAFFIC | 1-2    TRAFFIC | ——————————→ | | | ←—————————— | 1-2    TRAFFIC | 1-1    :Deactivate (MML command or failure) | | | 1-2    COO, SLC 1-1 | ——————————→ | | | ←—————————— | 1-2    ECA, SLC 1-1 | | ←—————————— | 1-2    TRAFFIC (from 1-1) | 1-2    TRAFFIC (from 1-1) | ——————————→ | | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    COO, SLC 1-1 | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    ECA, SLC 1-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC (from 1-1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC (from 1-1) | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check the sending of a COO (from A) for 1-1 on 1-2 and check that an ECA is sent inside T2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the traffic is changed over from 1-1 to 1-2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it has been received correctly; no duplication and no missequencing. Some messages may be lost as the system should not perform retrieval. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test by sending COO from B (instead of A).
NOTE – In this case, A might also send a COO/ECO to B as well as the COA. As a consequence, B would then return a COA/ECA to A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--|--|--| +| TEST NUMBER: 3.8 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704      Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Emergency changeover at one side of a linkset (COO ↔ ECO) | | | | | | +| PURPOSE: To check the emergency changeover procedure when a COO is acknowledged by an ECO | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1    TRAFFIC | —————→ | | | | | +| | ←————— | 1-1    TRAFFIC | | | | +| 1-2    TRAFFIC | —————→ | | | | | +| | ←————— | 1-2    TRAFFIC | | | | +| 1-1    :Deactivate (MML command or failure) | | | | | | +| 1-2    COO, SLC 1-1 | —————→ | | | | | +| | ←————— | 1-2    ECO, SLC 1-1 | | | | +| 1-2    COA, SLC 1-1 | —————→ | | | | | +| 1-2    TRAFFIC (from 1-1) | —————→ | | | | | +| | ←————— | 1-2    TRAFFIC (from 1-1) | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Check the sending of a COO (from A) for 1-1 on 1-2 and check that an ECO is sent (before T2 expires) and a COA is received. | | | | | +| 3. | Check that the traffic is changed over from 1-1 to 1-2. | | | | | +| 4. | Stop traffic and check that it has been received correctly; no duplication and no missequencing. Some messages may be lost as the system should not perform retrieval. | | | | | +| 5. | Repeat the test but send COO from B (instead of A). | | | | | +| | NOTE – In this case, A might also send a COO/ECO to B as well as the COA. As a consequence, B would then return a COA/ECA to A. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| TEST NUMBER: 3.9 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Emergency changeover at one side of a linkset (ECO ↔ COA) | | | | | | +| PURPOSE: To check the emergency changeover procedure when an ECO is acknowledged by a COA | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE:
SP A

Link
:Start traffic
1-1    TRAFFIC

1-2    TRAFFIC

1-1    :Deactivate (failure)
1-2    ECO, SLC 1-1


1-2    TRAFFIC (from 1-1)
:Wait
:Stop traffic



———————————→
←———————————
———————————→
←———————————

———————————→
←———————————
←———————————
———————————→ 		SP B

Link


1-1    TRAFFIC

1-2    TRAFFIC


1-2    COA, SLC 1-1
1-2    TRAFFIC (from 1-1)















| | | SP A

Link
:Start traffic
1-1    TRAFFIC

1-2    TRAFFIC

1-1    :Deactivate (failure)
1-2    ECO, SLC 1-1


1-2    TRAFFIC (from 1-1)
:Wait
:Stop traffic |



———————————→
←———————————
———————————→
←———————————

———————————→
←———————————
←———————————
———————————→ | SP B

Link


1-1    TRAFFIC

1-2    TRAFFIC


1-2    COA, SLC 1-1
1-2    TRAFFIC (from 1-1) | +| SP A

Link
:Start traffic
1-1    TRAFFIC

1-2    TRAFFIC

1-1    :Deactivate (failure)
1-2    ECO, SLC 1-1


1-2    TRAFFIC (from 1-1)
:Wait
:Stop traffic |



———————————→
←———————————
———————————→
←———————————

———————————→
←———————————
←———————————
———————————→ | SP B

Link


1-1    TRAFFIC

1-2    TRAFFIC


1-2    COA, SLC 1-1
1-2    TRAFFIC (from 1-1) | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Check that an ECO is received for 1-1 on 1-2 and that a COA is sent before T2 expires. | | | | | +| 3. | Check that traffic is changed over from 1-1 to 1-2. | | | | | +| 4. | Stop traffic and check that it has been received correctly; no duplication and no missequencing, some messages may be lost as the system should not perform retrieval. | | | | | +| 5. | Repeat the test but send ECO from B (instead of A).
NOTE – In this case, A might also send a COO/ECO to B as well as the COA. As a consequence, B would then return a COA/ECA to A. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------|--|------|------|--|------|----------------|--|--|----------------|-------------|--|--|-------------|----------------|----------------|-------------|--|--|-------------|----------------|------------------------------|--|--|---------------------|-------------|--|--|-------------|---------------------|--|-------------|---------------------------|---------------------------|-------------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.10 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Emergency changeover at both sides of a linkset (ECO ↔ ECA) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the emergency changeover procedure when an ECO is acknowledged by an ECA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1-1    TRAFFIC ——————————→
←—————————— 1-1    TRAFFIC
1-2    TRAFFIC ——————————→
←—————————— 1-2    TRAFFIC
1-1    :Deactivate (failure)
1-2    ECO, SLC 1-1 ——————————→
←—————————— 1-2    ECA, SLC 1-1
←—————————— 1-2    TRAFFIC (from 1-1)
1-2    TRAFFIC (from 1-1) ——————————→
:Wait
:Stop traffic 

 sequenceDiagram     participant SPA as SP A     participant SPB as SP B     Note over SPA, SPB: Start traffic     SPA->>SPB: 1-1 TRAFFIC     SPB->>SPA: 1-1 TRAFFIC     SPA->>SPB: 1-2 TRAFFIC     SPB->>SPA: 1-2 TRAFFIC     Note left of SPA: 1-1 :Deactivate (failure)     SPA->>SPB: 1-2 ECO, SLC 1-1     SPB->>SPA: 1-2 ECA, SLC 1-1     SPB->>SPA: 1-2 TRAFFIC (from 1-1)     SPA->>SPB: 1-2 TRAFFIC (from 1-1)     Note over SPA, SPB: Wait     Note over SPA, SPB: Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1    TRAFFIC | ——————————→ | | | ←—————————— | 1-1    TRAFFIC | 1-2    TRAFFIC | ——————————→ | | | ←—————————— | 1-2    TRAFFIC | 1-1    :Deactivate (failure) | | | 1-2    ECO, SLC 1-1 | ——————————→ | | | ←—————————— | 1-2    ECA, SLC 1-1 | | ←—————————— | 1-2    TRAFFIC (from 1-1) | 1-2    TRAFFIC (from 1-1) | ——————————→ | | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    :Deactivate (failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    ECO, SLC 1-1 | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    ECA, SLC 1-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC (from 1-1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC (from 1-1) | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that an ECO is received for 1-1 on 1-2 and that an ECA is sent before T2 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that traffic is changed over from 1-1 to 1-2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it has been received correctly; no duplication and no missequencing. Some messages may be lost as the system should not perform retrieval. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test but send ECO from B (instead of A). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--|--|--| +| TEST NUMBER: 3.11 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704      Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Emergency changeover at one side of a linkset (ECO ↔ COO) | | | | | | +| PURPOSE: To check the emergency changeover procedure when an COO is received in response to an ECO | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1    TRAFFIC | —————→ | | | | | +| | ←———— | 1-1    TRAFFIC | | | | +| 1-2    TRAFFIC | —————→ | | | | | +| | ←———— | 1-2    TRAFFIC | | | | +| 1-1    :Deactivate (failure) | | | | | | +| 1-2    ECO, SLC 1-1 | —————→ | | | | | +| | ←———— | 1-2    COO, SLC 1-1 | | | | +| 1-2    ECA, SLC 1-1 | —————→ | | | | | +| 1-2    TRAFFIC (from 1-1) | —————→ | | | | | +| | ←———— | 1-2    TRAFFIC (from 1-1) | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Check that an ECO is received for 1-1 on 1-2 and that a COO is sent before T2 expires and acknowledged with an ECA. | | | | | +| 3. | Check that traffic is changed over from 1-1 to 1-2. | | | | | +| 4. | Stop traffic and check that it has been received correctly; no duplication and no missequencing. Some messages may be lost as the system should not perform retrieval. | | | | | +| 5. | Repeat the test but sent ECO from B (instead of A). | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|-----|--------------------|---------------------|--|--|--|--|---------------------|-----|---------|-----|---------|---------------------|--|--|--|--|---------------------|-----|---------|-----|-----------------------|--|--|--|-----|--------------|---------------------|--|--|--|--|---------------------|-----|--------------|-----|--------------|---------------------|--|--|--|--|---------------------|-----|--------------|-----|--------------------|---------------------|--|--|--|--|---------------------|-----|--------------------| +| TEST NUMBER: 3.12 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704 Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Emergency changeover initiated at both ends at the same time (ECO ↔ ECO) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the emergency changeover procedure when it is initiated at the both ends simultaneously | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A

Link
SP B

Link

:Start traffic

1–1 TRAFFIC ——————————————————→
←—————————————————— 1–1 TRAFFIC
1–2 TRAFFIC ——————————————————→
←—————————————————— 1–2 TRAFFIC
1–1 :Deactivate (failure)
1–2 ECO, SLC 1–1 ——————————————————→
←—————————————————— 1–2 ECO, SLC 1–1
1–2 ECA, SLC 1–1 ——————————————————→
←—————————————————— 1–2 ECA, SLC 1–1
1–2 TRAFFIC (from 1–1) ——————————————————→
←—————————————————— 1–2 TRAFFIC (from 1–1)

:Wait

:Stop traffic

| | | 1–1 | TRAFFIC | ——————————————————→ | | | | | ←—————————————————— | 1–1 | TRAFFIC | 1–2 | TRAFFIC | ——————————————————→ | | | | | ←—————————————————— | 1–2 | TRAFFIC | 1–1 | :Deactivate (failure) | | | | 1–2 | ECO, SLC 1–1 | ——————————————————→ | | | | | ←—————————————————— | 1–2 | ECO, SLC 1–1 | 1–2 | ECA, SLC 1–1 | ——————————————————→ | | | | | ←—————————————————— | 1–2 | ECA, SLC 1–1 | 1–2 | TRAFFIC (from 1–1) | ——————————————————→ | | | | | ←—————————————————— | 1–2 | TRAFFIC (from 1–1) | +| 1–1 | TRAFFIC | ——————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ←—————————————————— | 1–1 | TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | TRAFFIC | ——————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ←—————————————————— | 1–2 | TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 | :Deactivate (failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | ECO, SLC 1–1 | ——————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ←—————————————————— | 1–2 | ECO, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | ECA, SLC 1–1 | ——————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ←—————————————————— | 1–2 | ECA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | TRAFFIC (from 1–1) | ——————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ←—————————————————— | 1–2 | TRAFFIC (from 1–1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1.Start traffic to B and C on all links.
  2. 2.Check that an ECO is received for 1–1 on 1–2 and that an ECO is sent before T2 expires and acknowledged with ECA.
  3. 3.Check that traffic is changed over from 1–1 to 1–2.
  4. 4.Stop traffic and check that it has been received correctly; no duplication and no missequencing. Some messages may be lost as the system should not perform retrieval.
  5. 5.Repeat the test without sending ECA from SP B to SP A.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 3.13 | | PAGE: 1 of 1 | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | +| TITLE: Changeover | | | +| SUBTITLE: Reactivation of a link during a changeover procedure | | | +| PURPOSE: To check the changeover procedure when the link failure causing the changeover is removed during the procedure | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–1    TRAFFIC —————————————————————>
<————————————————————— 1–1    TRAFFIC
1–2    TRAFFIC —————————————————————>
<————————————————————— 1–2    TRAFFIC
1–1    :Deactivate (failure)
1–1    : Activate (end of failure)
:Wait
:Stop traffic













NOTE – This test will be performed if applicable (some systems may terminate the changeover procedure, then perform the changeback). | | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on all links. | | +| 2. | Deactivate the link 1–1 and reactivate this link immediately. | | +| 3. | Stop traffic and check that the changeover procedure has not been performed. Depending on the time between the deactivation and the reactivation, a COO may be sent or not. | | +| 4. | Check that the traffic used the links 1–1 and 1–2 normally. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|------|--|------|------|--|------|----------------|--|--|---------------|---|--|--|---|---------------|---------------|---|--|--|---|---------------|---------------|---|--|--|---|---------------|-----------------------------------------------|--|--|--------------------|---|--|--------------------|---|--|--|---|--------------------|--|---|--------------------|-------------------------------------|---|--|--|---|-------------------------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.14 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704   Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Simultaneous changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the system can correctly handle simultaneous failures of several links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with three available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1-1   TRAFFIC →
← 1-1   TRAFFIC
1-2   TRAFFIC →
← 1-2   TRAFFIC
1-3   TRAFFIC →
← 1-3   TRAFFIC
1-1, 1-2 :Deactivate (MML command or failure)
1-3   COO, SLC 1-1 →
1-3   COO, SLC 1-1 →
← 1-3   COA, SLC 1-1
← 1-3   COA, SLC 1-2
1-3   TRAFFIC
(from 1-1 and 1-2)		 →
← 1-3   TRAFFIC
(from 1-1 and 1-2)
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1   TRAFFIC | → | | | ← | 1-1   TRAFFIC | 1-2   TRAFFIC | → | | | ← | 1-2   TRAFFIC | 1-3   TRAFFIC | → | | | ← | 1-3   TRAFFIC | 1-1, 1-2 :Deactivate (MML command or failure) | | | 1-3   COO, SLC 1-1 | → | | 1-3   COO, SLC 1-1 | → | | | ← | 1-3   COA, SLC 1-1 | | ← | 1-3   COA, SLC 1-2 | 1-3   TRAFFIC
(from 1-1 and 1-2) | → | | | ← | 1-3   TRAFFIC
(from 1-1 and 1-2) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1   TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1   TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2   TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-2   TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-3   TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-3   TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1, 1-2 :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-3   COO, SLC 1-1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-3   COO, SLC 1-1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-3   COA, SLC 1-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-3   COA, SLC 1-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-3   TRAFFIC
(from 1-1 and 1-2) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-3   TRAFFIC
(from 1-1 and 1-2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate the links 1-1 and 1-2 simultaneously. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that COOs are received on 1-3 for 1-1 and 1-2, and respond with COAs inside T2. Check that traffic is changed over from 1-1 and 1-2 to 1-3. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it has been received correctly (no lost messages, no duplication and no missequencing). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------|--|--| +| TEST NUMBER: 3.15 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704      Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Changeover to several alternative links within a linkset | | | | | | +| PURPOSE: To check the changeover procedure when there are several alternative links | | | | | | +| PRE-TEST CONDITIONS: Linkset with all links available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 | TRAFFIC | —————→ | | | | +| | | ←———— | 1-1    TRAFFIC | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←———— | 1-2    TRAFFIC | | | +| 1-3 | TRAFFIC | —————→ | | | | +| | | ←———— | 1-3    TRAFFIC | | | +| 1-4 | TRAFFIC | —————→ | | | | +| | | ←———— | 1-4    TRAFFIC | | | +| 1-1 | :Deactivate (MML command or failure) | | | | | +| 1-2, 3 or 4 | COO, SLC 1-1 | —————→ | | | | +| | | ←———— | 1-2, 3 or 4    COA, SLC 1-1 | | | +| 1-2 | TRAFFIC (from 1-1) | —————→ | | | | +| | | ←———— | 1-2    TRAFFIC (from 1-1) | | | +| 1-3 | TRAFFIC (from 1-1) | —————→ | | | | +| | | ←———— | 1-3    TRAFFIC (from 1-1) | | | +| 1-4 | TRAFFIC (from 1-1) | —————→ | | | | +| | | ←———— | 1-4    TRAFFIC (from 1-1) | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Deactivate the link 1-1 and check that the changeover is performed to links 1-2, 1-3 and 1-4. | | | | | +| 3. | Stop traffic and check that it has been shared on the alternative links according to the load sharing policy of this linkset. | | | | | +| 4. | Check that, for each destination and for each SLS, there were no lost messages, no duplication and no missequencing. | | | | | + +###### MTP Level 3 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|--|------|------|------|------|------|------|------|------|----------------|--|--|--|-------------|------------------|--------------------|------|--|--|--------------------|------|--|-------------------|--------------------|----------|----------------|------------------|--------------------|------|---------|------------------|--------------------|------|--|-------------------|-----------------------|----------|------------------------------------------|--|--|--|--------------|------------------|--------------------|-----|--|-------------------|--------------------|------------------|----------------|------------------|--------------------|------|------------|--|--------------------|------|--|-------------------|-----------------------|----------|--|-------------------|-----------------------|----------|-------|--|--|--|---------------|--|--|--| +| TEST NUMBER: 3.16 | | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704   Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Changeover to another linkset with the adjacent SP accessible | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the system performs changeover to an alternative route when the last link of a linkset becomes unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset 1 and link 3-1 unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: B | | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP •
Link Link Link Link
:Start traffic
3-2 TRAFFIC ———————————————> 7-1 —————————————> SP E
8-1 <————————————— SP D
<———————————————— 3-2 <————————————— 7-1 SP E
2-1, 2 TRAFFIC ———————————————> 6-1 —————————————> SP E
          TRAFFIC ———————————————> 5-1 —————————————> SP D
<———————————————— 2-1, 2 <————————————— 5-1 SP D
3-2 :Deactivate (MML command or failure)
2-X COO, SLC ———————————————> 4-1 —————————————> 3-2
<———————————————— 2-X <————————————— 4-1 COA, SLC 3-2
2-1, 2 TRAFFIC ———————————————> 6-1 —————————————> SP E
          (from 3-2) 5-1 —————————————> SP D
<———————————————— 2-1, 2 <————————————— 5-1 SP D
<———————————————— 2-1, 2 <————————————— 6-1 SP D
:Wait
:Stop traffic
| | | | | SP A | SP B | SP C | SP • | Link | Link | Link | Link | :Start traffic | | | | 3-2 TRAFFIC | ———————————————> | 7-1 —————————————> | SP E | | | 8-1 <————————————— | SP D | | <———————————————— | 3-2 <————————————— | 7-1 SP E | 2-1, 2 TRAFFIC | ———————————————> | 6-1 —————————————> | SP E | TRAFFIC | ———————————————> | 5-1 —————————————> | SP D | | <———————————————— | 2-1, 2 <————————————— | 5-1 SP D | 3-2 :Deactivate (MML command or failure) | | | | 2-X COO, SLC | ———————————————> | 4-1 —————————————> | 3-2 | | <———————————————— | 2-X <————————————— | 4-1 COA, SLC 3-2 | 2-1, 2 TRAFFIC | ———————————————> | 6-1 —————————————> | SP E | (from 3-2) | | 5-1 —————————————> | SP D | | <———————————————— | 2-1, 2 <————————————— | 5-1 SP D | | <———————————————— | 2-1, 2 <————————————— | 6-1 SP D | :Wait | | | | :Stop traffic | | | | +| SP A | SP B | SP C | SP • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-2 TRAFFIC | ———————————————> | 7-1 —————————————> | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 8-1 <————————————— | SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————— | 3-2 <————————————— | 7-1 SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-1, 2 TRAFFIC | ———————————————> | 6-1 —————————————> | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TRAFFIC | ———————————————> | 5-1 —————————————> | SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————— | 2-1, 2 <————————————— | 5-1 SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-2 :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-X COO, SLC | ———————————————> | 4-1 —————————————> | 3-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————— | 2-X <————————————— | 4-1 COA, SLC 3-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-1, 2 TRAFFIC | ———————————————> | 6-1 —————————————> | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (from 3-2) | | 5-1 —————————————> | SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————— | 2-1, 2 <————————————— | 5-1 SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————— | 2-1, 2 <————————————— | 6-1 SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to E (and D in VAT). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate link 3-2 and check that a COO (for 3-2) is sent from A to C via B and that a COA (from 3-2) is sent from C to A via B within T2.
NOTE – C might also send a COO/ECO to A as well as the COA. As a consequence, A would then return a COA/ECA to C. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that it has been shared on the alternative links 2-1 and 2-2 according to the load sharing rules of linkset 2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that, for each SLS, there were no lost messages, no duplication and no missequencing. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test but replace COO with ECO (some messages may have been lost). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|--|--| +| TEST NUMBER: 3.17 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704      Fig. 28, Fig. 29, Fig. 30 | | | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Changeover to another linkset with the adjacent SP inaccessible | | | | | | +| PURPOSE: To check that the system responds correctly when there is no path between the ends of an unavailable link. | | | | | | +| PRE-TEST CONDITIONS: Linkset 4 unavailable | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP | SP B | SP C | SP E | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC | → 6-1 | → | | | | +| 2-2 TRAFFIC | → 6-1 | → | | | | +| 2-2 TRAFFIC | → 7-1 | | → | | | +| | ← 3-1 | | ← 7-1 TRAFFIC | | | +| 3-2 TRAFFIC | → 7-1 | | → | | | +| | ← 3-2 | | ← 7-1 TRAFFIC | | | +| 2-1 | :Deactivate (MML command or failure) | | | | | +| 2-2 | :Deactivate (MML command or failure) | | | | | +| | T1 | | | | | +| 3-1 TRAFFIC
(from 2-1, 2) | → 7-1 | | → | | | +| | ← 3-1 | | ← 7-1 TRAFFIC | | | +| 3-2 TRAFFIC
(from 2-1, 2) | → 7-1 | | → | | | +| | ← 3-2 | | ← 7-1 TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to E on linkset 2 and 3. | | | | | +| 2. | Deactivate the linkset 2. | | | | | +| 3. | Check that traffic continues on linkset 3 at the expiration of T1. | | | | | +| 4. | Stop traffic and check that it has been shared on links 3-1 and 3-2 according to the load sharing rules of the linkset 3. | | | | | +| 5. | Check that the traffic has been received correctly. Some messages may have been lost but none should be missequenced or duplicated. | | | | | +| 6. | Check that the duration of T1 is inside the specified range. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------------------------|--|--| +| TEST NUMBER: 3.18 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 5/Q.704 | | Fig. 28, Fig. 29, Fig. 30 | | | | +| TITLE: Changeover | | | | | | +| SUBTITLE: Changeover to two linksets | | | | | | +| PURPOSE: To check the changeover procedure when it is performed to several links pertaining to two linksets | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 unavailable, all other available | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP D | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 1-2 TRAFFIC | —————→ | | 1-2 TRAFFIC | | | +| | ←———— | | 1-2 TRAFFIC | | | +| 1-2 :Deactivate (MML command or failure) | | | | | | +| 2-X COO, SLC 1-2 | —————→ 5-1 | —————→ | | | | +| or 3-X | —————→ | 8-1 —————→ | | | | +| | ←———— 2-X | ←———— | | | | +| | | | 5-1 COA, SLC 1-2 | | | +| 2-1 TRAFFIC
(from 1-2) | —————→ 5-1 | —————→ | | | | +| | ←———— 2-X | ←———— | | | | +| | | | 2-1 TRAFFIC
(from 1-2) | | | +| 2-2 TRAFFIC
(from 1-2) | —————→ 5-1 | —————→ | | | | +| 3-1 TRAFFIC
(from 1-2) | —————→ | 8-1 —————→ | | | | +| 3-2 TRAFFIC
(from 1-2) | —————→ | 8-1 —————→ | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D. | | | | | +| 2. | Deactivate the link 1-2 and check that a COO for 1-2 is sent to D via B or C and that a COA is sent from D to A via B or C inside T2. | | | | | +| 3. | Stop traffic and check that it has been shared on the alternative links 2-1, 2-2, 3-1 and 3-2 according to the load sharing rules in A. | | | | | +| 4. | Check that, for each SLS, there were no lost messages, no duplication and no missequencing. | | | | | +| 5. | Repeat the test but replace COO with ECO (some messages may have been lost). | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|--------------------|------|--|------|------|--|------|----------------|--|--|-----|--------------------------------|--|--|----------------------------|---------|-----|--------------------------------|--|--|----------------------------|---------|-----|---------------------------------------------|--|--|------------|--|-----|---------------------------------------|--|--|------------------------|--------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.19 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5 and 3.2.2/Q.704 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Changeover due to various reasons | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the interface L2-L3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1–1 TRAFFIC —————————————————————>
<————————————————————— 1–1 TRAFFIC
1–2 TRAFFIC —————————————————————>
<————————————————————— 1–2 TRAFFIC
1–1 :Deactivation due to various reasons (Note)
CHANGEOVER
1–2 TRAFFIC (from 1–1) —————————————————>
<————————————————— 1–2 TRAFFIC (from 1–1)
:Wait
:Stop traffic

NOTE – The object of this test is to check the interface L2-L3 by invoking a changeover by the different means listed in 3.2.2/Q.704. These reasons are: high error rate, expiration of timer T1, T2, T6 and T7 of L2, equipment failure, erroneous BSN or FIB, reception of SIOS, SIN, SIE and SIO of L2, and management request. The goal of this test is not to check the changeover procedure itself, but only that the COO is generated for each of these reasons.

| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1 | TRAFFIC —————————————————————> | | | <————————————————————— 1–1 | TRAFFIC | 1–2 | TRAFFIC —————————————————————> | | | <————————————————————— 1–2 | TRAFFIC | 1–1 | :Deactivation due to various reasons (Note) | | | CHANGEOVER | | 1–2 | TRAFFIC (from 1–1) —————————————————> | | | <————————————————— 1–2 | TRAFFIC (from 1–1) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 | TRAFFIC —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— 1–1 | TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | TRAFFIC —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— 1–2 | TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 | :Deactivation due to various reasons (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CHANGEOVER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 | TRAFFIC (from 1–1) —————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————— 1–2 | TRAFFIC (from 1–1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Invoke the deactivation of the link 1–1 (see Note above). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that traffic is changed over from 1–1 to 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it has been received correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test for each reason. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|---------------------------|------|--|------|----------|--|----------|----------------|--|--|----------------|-------------|--|--|-------------|----------------|----------------|-------------|--|--|-------------|----------------|---------------------------------------------|--|--|------------|--|--|---------------------------|-------------|--|--|-------------|---------------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.20 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704    Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Changeover as compatibility test | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the changeover procedure as compatibility test | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B

Link
Link
:Start traffic
1-1    TRAFFIC ——————————→
←—————————— 1-1    TRAFFIC
1-2    TRAFFIC ——————————→
←—————————— 1-2    TRAFFIC
1-1    :Deactivate (MML command or failure)
        CHANGEOVER
1-2    TRAFFIC (from 1-1) ——————————→
←—————————— 1-2    TRAFFIC (from 1-1)
:Wait
:Stop traffic














NOTE – In a compatibility test it is impossible to describe precisely the exchanges of changeover messages because the description depends on the type of deactivation of the link and of the time necessary to detect the deactivation.

| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1-1    TRAFFIC | ——————————→ | | | ←—————————— | 1-1    TRAFFIC | 1-2    TRAFFIC | ——————————→ | | | ←—————————— | 1-2    TRAFFIC | 1-1    :Deactivate (MML command or failure) | | | CHANGEOVER | | | 1-2    TRAFFIC (from 1-1) | ——————————→ | | | ←—————————— | 1-2    TRAFFIC (from 1-1) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHANGEOVER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC (from 1-1) | ——————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————— | 1-2    TRAFFIC (from 1-1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B on links 1-1 and 1-2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate link 1-1 and check that the changeover is performed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the sequence of changeover messages conforms to one of the descriptions 3.1 to 3.12.
Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat the test by invoking the different reasons listed in the Note in test 3.19. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|------|--|------|------|--|------|----------------|--|--|----------------|--------|--|--|--------|----------------|----------------|--------|--|--|--------|----------------|--|--------|----------------------------------------------------------------------------|---------------------|--------|--|---------------------------|--------|--|--|--------|---------------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 3.21 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 5/Q.704     Fig. 28, Fig. 29, Fig. 30 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeover | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Reception of a changeover order on an available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the changeover procedure on reception of a COO or ECO for a link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1-1    TRAFFIC —————→
←————— 1-1    TRAFFIC
1-2    TRAFFIC —————→
←————— 1-2    TRAFFIC
←————— 1-2    COO, SLC 1-1
(FSN corresponding to the
last received message)
1-2    COA, SLC 1-1 —————→
1-2    TRAFFIC (from 1-1) —————→
←————— 1-2    TRAFFIC (from 1-1)
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1    TRAFFIC | —————→ | | | ←————— | 1-1    TRAFFIC | 1-2    TRAFFIC | —————→ | | | ←————— | 1-2    TRAFFIC | | ←————— | 1-2    COO, SLC 1-1
(FSN corresponding to the
last received message) | 1-2    COA, SLC 1-1 | —————→ | | 1-2    TRAFFIC (from 1-1) | —————→ | | | ←————— | 1-2    TRAFFIC (from 1-1) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1    TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-2    COO, SLC 1-1
(FSN corresponding to the
last received message) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    COA, SLC 1-1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2    TRAFFIC (from 1-1) | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-2    TRAFFIC (from 1-1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all the links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send a COO from B to A for 1-1 on link 1-2 and check that the COA is received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the link 1-1 becomes unavailable. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that the changeover procedure has been performed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that there was no loss of messages, no duplication and no missequencing. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Repeat the test but send an ECO (instead of a COO) and check that a COA is received. Some messages may be lost. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 4.1 | | PAGE: 1 of 1 | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | +| TITLE: Changeback | | | +| SUBTITLE: Changeback within a linkset | | | +| PURPOSE: To check that the changeback procedure is correctly performed on restoration of a link in a linkset | | | +| PRE-TEST CONDITIONS: Linkset with one available link (end of test 3.1) | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

:Start traffic

1-2    TRAFFIC —————→
←————— 1-2    TRAFFIC

1-1    :Activate (depending on the deactivation mean previously used)

1-2    CBD, SLC 1-1 —————→
←————— 1-X    CBA, SLC 1-1
1-1    TRAFFIC (from 1-2) —————→
←————— 1-2    CBD, SLC 1-1
1-X    CBD, SLC 1-1 —————→
←————— 1-1    TRAFFIC (from 1-2)
1-2    TRAFFIC —————→
←————— 1-2    TRAFFIC

:Wait

:Stop traffic

| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B (and C in VAT) on link 1-2. | | +| 2. | Activate the link 1-1 and check that it enters the correct in service state. | | +| 3. | Check that a CBD for SLC 1-1 is received and that traffic for link 1-1 is switched back after a CBA is sent. | | +| 4. | Stop traffic and check that it has been received correctly; no lost messages, no duplication and no missequencing. | | +| 5. | Continue the test by activating the link 1-3, then 1-4. | | +| 6. | As a compatibility test, repeat the test for several reasons chosen among those listed in test 4.10. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------|------|--|------|----------|--|----------|----------------|--|--|----------------|-----------------|--|--|-----------------|----------------|--|-----------------|---------------------|----------------|-----------------|--|--|-----------------|----------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 4.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 6/Q.704     Fig. 28, Fig. 29, Fig. 31 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeback | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Additional CBA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of an additional CBA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with all links available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
ALL    TRAFFIC ——————————————→
←—————————————— ALL    TRAFFIC
←—————————————— 1–X    CBA, SLC 1–1
ALL    TRAFFIC ——————————————→
←—————————————— ALL    TRAFFIC

:Wait
:Stop traffic
| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | ALL    TRAFFIC | ——————————————→ | | | ←—————————————— | ALL    TRAFFIC | | ←—————————————— | 1–X    CBA, SLC 1–1 | ALL    TRAFFIC | ——————————————→ | | | ←—————————————— | ALL    TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALL    TRAFFIC | ——————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————————— | ALL    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————————— | 1–X    CBA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALL    TRAFFIC | ——————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←—————————————— | ALL    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send an unexpected CBA to A and check that this message is discarded without action on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|---------------------|--|--|--| +| TEST NUMBER: 4.3 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | | | | +| TITLE: Changeback | | | | | | +| SUBTITLE: Additional CBD | | | | | | +| PURPOSE: To check the action of the system on reception of an additional CBD | | | | | | +| PRE-TEST CONDITIONS: Linkset with all links available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| ALL    TRAFFIC | —————→ | | | | | +| | ←———— | ALL    TRAFFIC | | | | +| | ←———— | 1-X    CBD, SLC 1-1 | | | | +| 1-X    CBA, SLC 1-X | —————→ | | | | | +| ALL    TRAFFIC | —————→ | | | | | +| | ←———— | ALL    TRAFFIC | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Send an unexpected CBD to A and check that a CBA is send back in response without impact on the traffic. | | | | | +| 3. | Stop traffic and check that it has been received correctly. | | | | | + +###### **MTP Level 3** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 4.4 | | PAGE: 1 of 1 | +| REFERENCE: clause 6/Q.704     Fig. 28, Fig. 29, Fig. 31 | | | +| TITLE: Changeback | | | +| SUBTITLE: No acknowledgement to first CBD | | | +| PURPOSE: To check that a second CBD is sent if the first is not acknowledged | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

:Start traffic

1–2    TRAFFIC
——————>
<——————
1–2    TRAFFIC
1–1    :Activate
1–2    CBD, SLC 1–1
——————>
T4
1–2    CBD, SLC 1–1
——————>
<——————
1–X    CBA, SLC 1–1
1–1    TRAFFIC (from 1–2)
——————>
<——————
1–1    TRAFFIC (from 1–2, Note)
1–2    TRAFFIC
——————>
<——————
1–2    TRAFFIC

:Wait

:Stop traffic

| | | +| NOTE – B may perform a changeback or not. | | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on link 1–2. | | +| 2. | Activate link 1–1 and check that a CBD is received (no CBA in response). | | +| 3. | Check that after T4 a second CBD is received and CBA is sent in response before T5 expires. | | +| 4. | Check that the traffic is changed back on link 1–1. | | +| 5. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | +| 6. | Check that the duration of T4 is inside the specified range. | | + +###### **MTP Level 3** + +| | | | +|----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------------------------| +| TEST NUMBER: 4.5 | | PAGE: 1 of 1 | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | +| TITLE: Changeback | | | +| SUBTITLE: No acknowledgement of repeat changeback declaration | | | +| PURPOSE: To check that traffic is changed back after a repeat changeback declaration is not acknowledged | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE: | | | +| SP A | | SP B | +| Link | | Link | +| :Start traffic | | | +| 1-2    TRAFFIC | —————→ | | +| | ←———— | 1-2    TRAFFIC | +| 1-1    :Activate | | | +| 1-2    CBD, SLC 1-1 | —————→ | | +| | | | +| | T4 | | +| | | | +| 1-2    CBD, SLC 1-1 | —————→ | | +| | | | +| | T5 | | +| | | | +| 1-1    TRAFFIC (from 1-2) | —————→ | | +| | ←———— | 1-1    TRAFFIC (from 1-2) | +| 1-2    TRAFFIC | —————→ | | +| | ←———— | 1-2    TRAFFIC | +| :Wait | | | +| :Stop traffic | | | +| NOTE – B may perform a changeback or not. | | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on link 1-2. | | +| 2. | Check that a CBD is received and not acknowledged. | | +| 3. | Check that after T4, a CBD is repeated and not acknowledged by a CBA. | | +| 4. | Check that after T5, the traffic is changed back on link 1-1. | | +| 5. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | +| 6. | Check that the duration of T5 is inside the specified range. | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------|--|--| +| TEST NUMBER: 4.6 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | | | | +| TITLE: Changeback | | | | | | +| SUBTITLE: Simultaneous changeback | | | | | | +| PURPOSE: To check simultaneous changebacks of traffic onto two links | | | | | | +| PRE-TEST CONDITIONS: Linkset with one available link (end of test 3.14) | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-3 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-3      TRAFFIC | | | +| 1-1 | :Activate (depending on the deactivation mean previously used) | | | | | +| 1-2 | :Activate | | | | | +| 1-3 | CBD, SLC 1-1 | —————→ | | | | +| 1-3 | CBD, SLC 1-2 | —————→ | | | | +| | | ←————— | 1-X      CBA, SLC 1-1 | | | +| | | ←————— | 1-X      CBA, SLC 1-2 | | | +| 1-1 | TRAFFIC (from 1-3) | —————→ | | | | +| | | ←————— | 1-1      TRAFFIC (from 1-3,
Notes 1 and 2) | | | +| 1-2 | TRAFFIC (from 1-3) | —————→ | | | | +| | | ←————— | 1-2      TRAFFIC (from 1-3,
Notes 1 and 2) | | | +| 1-3 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-3      TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE 1 – B may perform changebacks or not. | | | | | | +| NOTE 2 – Changeback procedures may be performed in sequence. The traffic sequence presented here, after the changebacks, is the final situation. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on link 1-3. | | | | | +| 2. | Simultaneously activate links 1-1 and 1-2. | | | | | +| 3. | Check that CBDs are received and CBAs are sent (within T4) for 1-1 and 1-2 and that the traffic is changed back on links 1-1 and 1-2. | | | | | +| 4. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------------|--|--| +| TEST NUMBER: 4.7 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | | | | +| TITLE: Changeback | | | | | | +| SUBTITLE: Changeback from several alternative links within a linkset | | | | | | +| PURPOSE: To check the changeback procedure when it is performed to several links in a same linkset | | | | | | +| PRE-TEST CONDITIONS: Linkset with one unavailable link (end of test 3.15) | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2, 3, 4 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-2, 3, 4    TRAFFIC | | | +| 1-1 | :Activate (depending on the deactivation mean previously used) | | | | | +| 1-2 | CBD, SLC 1-1 | —————→ | | | | +| 1-3 | CBD, SLC 1-1 | —————→ | | | | +| 1-4 | CBD, SLC 1-1 | —————→ | | | | +| | | ←————— | 1-X    CBA, SLC 1-1 | | | +| | | ←————— | 1-X    CBA, SLC 1-1 | | | +| | | ←————— | 1-X    CBA, SLC 1-1 | | | +| 1-1 | TRAFFIC
(from 1-2, 3, 4) | —————→ | | | | +| | | ←————— | 1-1    TRAFFIC (from 1-2, 3, 4, Note) | | | +| 1-2, 3, 4 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-2, 3, 4    TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – B may perform changebacks or not. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on links 1-2, 1-3 and 1-4. | | | | | +| 2. | Activate link 1-1 and check that a CBD is sent on links 1-2, 1-3 and 1-4. Check that each CBD contains a different changeback code. | | | | | +| 3. | Check that the traffic is changed back on link 1-1. | | | | | +| 4. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------|----------|--|--| +| TEST NUMBER: 4.8 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | | | | +| TITLE: Changeback | | | | | | +| SUBTITLE: Changeback from another linkset | | | | | | +| PURPOSE: To check the changeback procedure when it is performed from another linkset | | | | | | +| PRE-TEST CONDITIONS: Linksets 1 and 3 unavailable (end of test 3.16) | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1, 2 TRAFFIC | → 5-1 | → | SP D | | | +| | 6-1 | → | SP E | | | +| | ← 2-1, 2 | ← | 5-1 SP D | | | +| | ← 2-1, 2 | ← | 6-1 SP E | | | +| 3-2 :Activate (depending on the deactivation mean previously used) | | | | | | +| 2-1 CBD, SLC 3-2 | → 4-1 | → | | | | +| 2-1 CBD, SLC 3-2 | → 4-1 | → | | | | +| | ← | 3-2 CBA, SLC 3-2 | | | | +| | ← | 3-2 CBA, SLC 3-2 | | | | +| | | CHANGEBACK | | | | +| 2-1, 2 TRAFFIC | → 5-1 | → | SP D | | | +| | 6-1 | → | SP E | | | +| | ← 2-1, 2 | ← | 5-1 SP D | | | +| 3-2 TRAFFIC | → | 8-1 → | SP D | | | +| (from 2-X) | | 7-1 → | SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE 1 – It is possible that A and/or B prefers to perform a time controlled diversion procedure. | | | | | | +| NOTE 2 – After activation of link 3-2, CBDs are sent from C to A via B and acknowledged by A. These messages are not presented to simplify the test description. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to E (and D in VAT). | | | | | +| 2. | Activate link 3-2 and check that CBDs are received and that CBAs are sent before T4 expires in A. | | | | | +| 3. | Check that the traffic is changed back on linkset 3 in accordance with the load sharing rules in A. | | | | | +| 4. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------------|--|--| +| TEST NUMBER: 4.9 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | | | | +| TITLE: Changeback | | | | | | +| SUBTITLE: Changeback from two linksets | | | | | | +| PURPOSE: To check the changeback procedure when it is performed from two linksets | | | | | | +| PRE-TEST CONDITIONS: Linkset 1 unavailable (end of test 3.18) | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP D | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC | —————→ 5-1 | —————→ | | | | +| | ←———— 2-1 | ←———— | 5-1 TRAFFIC | | | +| 2-2 TRAFFIC | —————→ 5-1 | —————→ | | | | +| | ←———— 2-2 | ←———— | 5-1 TRAFFIC | | | +| 3-1 TRAFFIC | —————→ | 8-1 —————→ | | | | +| 3-2 TRAFFIC | —————→ | 8-1 —————→ | | | | +| 1-2 :Activate (depending on the deactivation mean previously used) | | | | | | +| 2-1 CBD, SLC 1-2 | —————→ 5-1 | —————→ | | | | +| 2-2 CBD, SLC 1-2 | —————→ 5-1 | —————→ | | | | +| 3-1 CBD, SLC 1-2 | —————→ | 8-1 —————→ | | | | +| 3-2 CBD, SLC 1-2 | —————→ | 8-1 —————→ | CBA | | | +| | ←———— 2-X | ←———— | 5-1 SLC 1-2 | | | +| | ←———— 2-X | ←———— | 5-1 SLC 1-2 | | | +| | ←———— 2-X | ←———— | 5-1 SLC 1-2 | | | +| | ←———— 2-X | ←———— | 5-1 SLC 1-2 | | | +| 1-2 TRAFFIC (from linksets 2 and 3) | —————→ | | | | | +| | ←———— | | 1-2 TRAFFIC
(from linksets 5,
Notes 1 and 2) | | | +| 2-1, 2 TRAFFIC | —————→ 5-1 | —————→ | | | | +| 3-1, 2 TRAFFIC | —————→ | 8-1 —————→ | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE 1 – D may perform changebacks or not. | | | | | | +| NOTE 2 – It is possible that A and/or B prefers to perform a time controlled diversion procedure. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic on linksets 2 and 3 to D. | | | | | +| 2. | Activate the link 1-2 and check that CBDs are received and that CBAs are sent before T4 expires in A. Check that each CBD has a different changeback code. | | | | | +| 3. | Check that the traffic is changed back to link 1-2 in accordance with the load sharing rules in A. | | | | | +| 4. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|---------------------------|----------------|--------|--|--|-------|----------------|--------------------------------------------------|--|--|---------------------|--------|--|--|-------|---------------------|---------------------------|--------|--|--|-------|---------------------|---------------------|--------|--|--|-------|---------------------------|----------------|--------|--|--|-------|----------------| +| TEST NUMBER: 4.10 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 6/Q.704     Fig. 28, Fig. 29, Fig. 31 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Changeback | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Changeback due to various reasons | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the interface L2-L3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with one available link (end of 3.19) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A

Link
SP B

Link

:Start traffic

1–2    TRAFFIC —————→
←———— 1–2    TRAFFIC
1–1    :Activation due to various reasons (Note)
1–2    CBD, SLC 1–1 —————→
←———— 1–2    CBA, SLC 1–1
1–1    TRAFFIC (from 1–2) —————→
←———— 1–2    CBA, SLC 1–1
1–X    CBA, SLC 1–1 —————→
←———— 1–1    TRAFFIC (from 1–2)
1–2    TRAFFIC —————→
←———— 1–2    TRAFFIC

:Wait

:Stop traffic


NOTE – The object of this test is to check the interface L2-L3 by provoking a changeback by different means listed in clause 3/Q.704. These reasons are: initial alignment procedure completed with success, processor outage condition has ceased at the remote signalling terminal and management request.

| | | 1–2    TRAFFIC | —————→ | | | ←———— | 1–2    TRAFFIC | 1–1    :Activation due to various reasons (Note) | | | 1–2    CBD, SLC 1–1 | —————→ | | | ←———— | 1–2    CBA, SLC 1–1 | 1–1    TRAFFIC (from 1–2) | —————→ | | | ←———— | 1–2    CBA, SLC 1–1 | 1–X    CBA, SLC 1–1 | —————→ | | | ←———— | 1–1    TRAFFIC (from 1–2) | 1–2    TRAFFIC | —————→ | | | ←———— | 1–2    TRAFFIC | +| 1–2    TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1    :Activation due to various reasons (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2    CBD, SLC 1–1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2    CBA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1    TRAFFIC (from 1–2) | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2    CBA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–X    CBA, SLC 1–1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1    TRAFFIC (from 1–2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2    TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Provoke the activation of the link 1–1 (see Note above). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the traffic is changed back to 1–1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it has been received correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test for each reason. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--|--| +| TEST NUMBER: 4.11 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 6/Q.704      Fig. 28, Fig. 29, Fig. 31 | | | | | | +| TITLE: Changeback | | | | | | +| SUBTITLE: Time controlled diversion procedure | | | | | | +| PURPOSE: To check the correct operation of the time controlled diversion procedure | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 2 and 4 unavailable | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | | | | +| Link | Link | Link | | | | +| :Start traffic | | | | | | +| 3-1 TRAFFIC
(to D and E) | —————→ | | | | | +| | ←———— | 3-1 TRAFFIC
(from D and E) | | | | +| 3-2 TRAFFIC
(to D and E) | —————→ | | | | | +| | ←———— | 3-2 TRAFFIC
(from D and E) | | | | +| 2-1 :Activate (depending on the deactivation mean previously used) | | | | | | +| T21      → | | | | | | +| TRA      ← | 2-1 «TRA» | | | | | +| 3-1, 2 TRAFFIC STOPPED | | | | | | +| T3 | | | | | | +| 2-1 TRAFFIC
(from 3-1, 2) | —————→ | | | | | +| | ←———— 2-1 TRAFFIC (from D, Note) | | | | | +| 2-1, 2 TRAFFIC | —————→ | | | | | +| | ←———— 3-1, 2 TRAFFIC (from E) | | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – B performs the point restart procedure and D, on reception of a TFA for A, reroutes its traffic to A. These procedures are not presented to simplify the test description. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to E (and D in VAT) on linkset 3. | | | | | +| 2. | Activate link 2-1. | | | | | +| 3. | Check that T21 is started in A, and is stopped on reception of TRA from SP B (see Note). | | | | | +| 4. | Check that traffic on linkset 3 ceased in A and that after expiration T3 traffic diverts to link 2-1 in accordance with the load sharing rules in A. | | | | | +| 5. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | +| 6. | Check that the duration of T3 is inside the specified range. | | | | | +| 7. | Repeat the test (in VAT) without sending TRA from B to A and check that the time controlled diversion is performed when T21 expires. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------|------|------|------|------|------|----------------|--|--|----------------|-------------------|--|--|-------------------------------|--|----------------|-----------------------|------------|--|-----------------------|-------------------------|--|-----------------|--|--|-----------------------|--|----------------|-----------------------|--|-----------------------------|--|--|--|-----------------------|-------------------------|----------------|-------------|--|--|-------------------------------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 5 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 7/Q.704     Fig. 29, Fig. 32 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Forced rerouting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the system can perform forced rerouting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linksets 1 and 4 unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C
Link Link Link
:Start traffic
2–1, 2 TRAFFIC —————> to D and E
<———— 2–1, 2 TRAFFIC (from D)
3–1, 2 TRAFFIC ————————————————————> to D and E
<———————————————————— 3–1, 2 TRAFFIC (from E)
6–1 :Deactivate
<———— 2–X TFP, PC = E
3–1, 2 TRAFFIC ————————————————————>
(to D and from 2–1, 2 to E)
<———————————————————— 3–1, 2 TRAFFIC (from E)
2–1, 2 TRAFFIC —————> to D
<———— 2–1, 2 TRAFFIC (from D)
:Wait
:Stop traffic
| | | SP A | SP B | SP C | Link | Link | Link | :Start traffic | | | 2–1, 2 TRAFFIC | —————> to D and E | | | <———— 2–1, 2 TRAFFIC (from D) | | 3–1, 2 TRAFFIC | ————————————————————> | to D and E | | <———————————————————— | 3–1, 2 TRAFFIC (from E) | | 6–1 :Deactivate | | | <———— 2–X TFP, PC = E | | 3–1, 2 TRAFFIC | ————————————————————> | | (to D and from 2–1, 2 to E) | | | | <———————————————————— | 3–1, 2 TRAFFIC (from E) | 2–1, 2 TRAFFIC | —————> to D | | | <———— 2–1, 2 TRAFFIC (from D) | | :Wait | | | :Stop traffic | | | +| SP A | SP B | SP C | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1, 2 TRAFFIC | —————> to D and E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— 2–1, 2 TRAFFIC (from D) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1, 2 TRAFFIC | ————————————————————> | to D and E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 3–1, 2 TRAFFIC (from E) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 6–1 :Deactivate | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— 2–X TFP, PC = E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1, 2 TRAFFIC | ————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (to D and from 2–1, 2 to E) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 3–1, 2 TRAFFIC (from E) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1, 2 TRAFFIC | —————> to D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— 2–1, 2 TRAFFIC (from D) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic on linksets 2 and 3 to E (and D in VAT). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate the linkset 6 and check the sending of a TFP concerning E from B to A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that the forced rerouting has been performed correctly, messages may have been lost but not missequenced or duplicated. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that the traffic to D carried by the linksets 2 and 3 has not been disturbed (no lost messages, no duplication and no missequencing). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that an indication was given by the system. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 6 | | PAGE: 1 of 1 | +| REFERENCE: clause 8/Q.704     Fig. 29, Fig. 33 | | | +| TITLE: Controlled rerouting | | | +| SUBTITLE: | | | +| PURPOSE: To check that the system can perform controlled rerouting | | | +| PRE-TEST CONDITIONS: Linksets 1, 4 and 6 unavailable (end of test 5) | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP ASP BSP C
LinkLinkLink

:Start traffic

3-1, 2 TRAFFIC
———————>
to D and E
<———————
3-1, 2 TRAFFIC (from E)
2-1, 2 TRAFFIC
————>
to D
<————
1-1, 2 TRAFFIC (from D)
6-1 :Activate
<————
2-X TFA, PC = E
T6
2-1, 2 TRAFFIC
————>
(to D and from 3-1, 2 to E)
<————
3-1, 2 TRAFFIC (from D)
3-1, 2 TRAFFIC
———————>
<———————
3-1, 2 TRAFFIC (from E)

:Wait
:Stop traffic

| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to E (and D in VAT). | | +| 2. | Activate the linkset 6 and check the sending of a TFA concerning E from B to A. | | +| 3. | Stop traffic and check that the controlled rerouting has been performed correctly (for all traffic flows, no lost messages, no duplication and no missequencing). | | +| 4. | Check that the duration of T6 is inside the specified range. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------|------|--|------|------|--|------|----------------|--|--|-------------|---|--|--|---|-------------|-------------|---|--|--|---|-------------|-------------------------|--|--|------------------|---|--|--|---|------------------|-------------------------------------|--|--|------------------------|---|--|--|---|------------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.1.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Inhibition of a link–Available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check for the correct response when link inhibition is requested for an available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1–1 TRAFFIC →
← 1–1 TRAFFIC
1–2 TRAFFIC →
← 1–2 TRAFFIC
1–1 :Request inhibition
1–X LIN, SLC 1–1 →
← 1–X LIA, SLC 1–1
TIME – CONTROLLED CHANGEOVER (Note)
1–2 TRAFFIC (from 1–1) →
← 1–2 TRAFFIC (from 1–1)
:Wait
:Stop traffic

NOTE – A changeover is performed after the inhibition of link 1–1 but it is not described in this test which checks only the inhibition procedure.

| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1 TRAFFIC | → | | | ← | 1–1 TRAFFIC | 1–2 TRAFFIC | → | | | ← | 1–2 TRAFFIC | 1–1 :Request inhibition | | | 1–X LIN, SLC 1–1 | → | | | ← | 1–X LIA, SLC 1–1 | TIME – CONTROLLED CHANGEOVER (Note) | | | 1–2 TRAFFIC (from 1–1) | → | | | ← | 1–2 TRAFFIC (from 1–1) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 :Request inhibition | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–X LIN, SLC 1–1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–X LIA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TIME – CONTROLLED CHANGEOVER (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC (from 1–1) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC (from 1–1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1.Start traffic to B (and C in VAT) on links 1–1 and 1–2.
  2. 2.Initiate inhibition of link 1–1 and check that LIN is received and an LIA is received in A within T14.
  3. 3.Check that the traffic normally carried by link 1–1 is transferred to link 1–2.
  4. 4.Check that the link 1–1 enters in the "Local inhibiting" state.
  5. 5.Repeat test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------|------|--|------|----------|--|----------|----------------|--|--|-------------|----------|--|--|----------|-------------|-------------------------|--|--|------------------|----------|--|--|----------|------------------|--------------------------------------------------------------------|--|--|-------------|----------|--|--|----------|-------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 7.1.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Inhibition of a link – Unavailable link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check for the correct response when link inhibition is requested for an unavailable link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–1 TRAFFIC ———————>
<——————— 1–1 TRAFFIC
1–1 :Request inhibition
1–1 LIN, SLC 1–2 ———————>
<——————— 1–1 LIA, SLC 1–2
1–2 :Activate (depending on the deactivation mean previously used)
1–1 TRAFFIC ———————>
<——————— 1–1 TRAFFIC

:Wait
:Stop traffic
| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–1 TRAFFIC | ———————> | | | <——————— | 1–1 TRAFFIC | 1–1 :Request inhibition | | | 1–1 LIN, SLC 1–2 | ———————> | | | <——————— | 1–1 LIA, SLC 1–2 | 1–2 :Activate (depending on the deactivation mean previously used) | | | 1–1 TRAFFIC | ———————> | | | <——————— | 1–1 TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 :Request inhibition | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 LIN, SLC 1–2 | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————— | 1–1 LIA, SLC 1–2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 :Activate (depending on the deactivation mean previously used) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | ———————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B (and C in VAT) on link 1–1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Request inhibition of link 1–2, check the reception of LIN at B and send LIA in response within T14. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the inhibition was performed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Activate link 1–2 and check that it stays in inhibited state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Repeat test in reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|------|--|------|----------------|--|--|-------------|--------|--|--|-------|-------------|-------------------------|--|--|-------------|--------|--|--|-------|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.2.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Inhibition not permitted – Local reject on available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the inhibition procedure in case of local reject on an available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP ASP B
LinkLink
:Start traffic
1-1 TRAFFIC—————→
←————1-1 TRAFFIC
1-1 :Request inhibition
1-1 TRAFFIC—————→
←————1-1 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1 TRAFFIC | —————→ | | | ←———— | 1-1 TRAFFIC | 1-1 :Request inhibition | | | 1-1 TRAFFIC | —————→ | | | ←———— | 1-1 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 :Request inhibition | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B (and C in VAT) on link 1-1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Request inhibition of link 1-1 and check that this request is not permitted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that it has not been disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat the test but modify pre-test conditions as follows: link 1-1 available and link 1-2 inhibited by B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------| +| TEST NUMBER: 7.2.2 | | PAGE: 1 of 1 | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | +| TITLE: Management inhibiting | | | +| SUBTITLE: Inhibition not permitted – Local reject on an unavailable link | | | +| PURPOSE: To check the inhibition procedure in case of local reject on an unavailable link | | | +| PRE-TEST CONDITIONS: All links unavailable | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A

Link

1–1         :Request inhibition
SP B

Link
| | | +| TEST DESCRIPTION | | | +| 1. | Request inhibition of link 1–1 and check that it is rejected. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|-------------|--------|--|--|-------|-------------|--|-------|------------------|------------------|--------|--|-------------|--------|--|--|-------|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.2.3 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Inhibition not permitted – Sending of LID | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the reject of an inhibition asked on reception of an LIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP ASP B
LinkLink
:Start traffic
1-1 TRAFFIC—————→
←————1-1 TRAFFIC
←————1-1 LIN, SLC 1-1
1-1 LIN, SLC 1-1—————→
1-1 TRAFFIC—————→
←————1-1 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1 TRAFFIC | —————→ | | | ←———— | 1-1 TRAFFIC | | ←———— | 1-1 LIN, SLC 1-1 | 1-1 LIN, SLC 1-1 | —————→ | | 1-1 TRAFFIC | —————→ | | | ←———— | 1-1 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-1 LIN, SLC 1-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 LIN, SLC 1-1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1-1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send an LIN, SLC 1-1 from B to A and check the reception of an LID. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the inhibition is not performed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it has not been disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 7.2.4 | | PAGE: 1 of 1 | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | +| TITLE: Management inhibiting | | | +| SUBTITLE: Inhibition not permitted – Reception of LID | | | +| PURPOSE: To check the reject of an inhibition asked on sending of an LIN | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A

Link
:Start traffic
1–1, 2     TRAFFIC


1–1         :Request inhibition
1–X        LIN, SLC 1–1


1–1, 2     TRAFFIC

:Wait
:Stop traffic




—————→
←————


—————→
←————

—————→
←————
SP B

Link


1–1, 2     TRAFFIC



1–X        LID, SLC 1–1


1–1, 2     TRAFFIC
| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on links 1–1 and 1–2. | | +| 2. | Request the inhibition of link 1–1 and check the reception of LIN and response with an LID before T14 expires in A. | | +| 3. | Check that the inhibition is not performed. | | +| 4. | Stop traffic and check that it was not disturbed. | | + +###### **MTP Level 3** + +| | | | +|--------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| TEST NUMBER: 7.3.1 | | PAGE: 1 of 1 | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | +| TITLE: Management inhibiting | | | +| SUBTITLE: Expiration of T14 – On an available link | | | +| PURPOSE: To check that the inhibition procedure asked for an available link is restarted when T14 expires | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE: | | | +| SP A | | SP B | +| Link | | Link | +| :Start traffic | | | +| 1-1 TRAFFIC | —————→ | | +| | ←———— | 1-1 TRAFFIC | +| 1-2 TRAFFIC | —————→ | | +| | ←———— | 1-2 TRAFFIC | +| 1-1 :Request inhibition | | | +| 1-X LIN, SLC 1-1 | —————→ | | +| | | | +| | T14 | | +| | | | +| 1-X LIN, SLC 1-1 | —————→ | | +| | ←———— | 1-1 LIA, SLC 1-1 | +| TIME-CONTROLLED CHANGEOVER (Note) | | | +| 1-2 TRAFFIC (from 1-1) | —————→ | | +| | ←———— | 1-2 TRAFFIC (from 1-1) | +| :Wait | | | +| :Stop traffic | | | +| NOTE – A changeover is performed after the inhibition of link 1-1 but it is not described in this inhibition test. | | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on links 1-1 and 1-2. | | +| 2. | Request the inhibition of link 1-1, check that an LIN is received without response. Check that a new LIN is received after T14 expires and that an LIA is sent in response. | | +| 3. | Check that the inhibition is performed. Stop traffic and check that it was not disturbed. | | +| 4. | Repeat the test but without sending of an LIA. Check that after the second expiration of T14 the procedure is stopped. | | +| 5. | Check that the duration of T14 is inside the specified range. | | + +###### **MTP Level 3** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 7.3.2 | | PAGE: 1 of 1 | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | +| TITLE: Management inhibiting | | | +| SUBTITLE: Expiration of T14 – On an unavailable link | | | +| PURPOSE: To check that the inhibition procedure asked for an unavailable link is restarted when T14 expires. | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

:Start traffic

1–1 TRAFFIC —————————————————————>

<————————————————————— 1–1 TRAFFIC

1–2 :Request inhibition

1–1 LIN, SLC 1–2 —————————————————————>

T14

1–1 LIN, SLC 1–2 —————————————————————>

<————————————————————— 1–1 LIA, SLC 1–2

1–2 :Activate

1–1 TRAFFIC —————————————————————>

<————————————————————— 1–1 TRAFFIC

:Wait

:Stop traffic

| | | +| TEST DESCRIPTION | | | +| 1.
2.
3.
4.
5.
6. | Start traffic to B and C on link 1–1.
Request inhibition of link 1–2, check that an LIN is received without response. Check that a new LIN is received after T14 expires and that an LIA is sent in response.
Check that the inhibition is performed.
Activate link 1–2 and check that it stays unavailable.
Stop traffic and check that it was not disturbed.
Repeat the test but without sending of an LIA. Check that after the second expiration of T14, the procedure is stopped. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|-------------|---|--|--|---|-------------|--|---|------------------|--|---|------------------|-------------|---|--|--|---|-------------|--|---|------------------|------------------|---|--|-------------|---|--|--|---|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.4 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Additional inhibition messages (LIA, LID, LIN) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the action of the system on reception of an additional LIA, LID or LIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: End of test 7.1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–2 TRAFFIC →
← 1–2 TRAFFIC
← 1–2 LIA, SLC 1–1
← 1–2 LID, SLC 1–1
1–2 TRAFFIC →
← 1–2 TRAFFIC
← 1–2 LIN, SLC 1–1
1–1 LIA, SLC 1–1 →
1–2 TRAFFIC →
← 1–2 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–2 TRAFFIC | → | | | ← | 1–2 TRAFFIC | | ← | 1–2 LIA, SLC 1–1 | | ← | 1–2 LID, SLC 1–1 | 1–2 TRAFFIC | → | | | ← | 1–2 TRAFFIC | | ← | 1–2 LIN, SLC 1–1 | 1–1 LIA, SLC 1–1 | → | | 1–2 TRAFFIC | → | | | ← | 1–2 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 LIA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 LID, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 LIN, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 LIA, SLC 1–1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send an additional LIA and LID on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that these messages are ignored without impact on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Send an additional LIN on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that an LIA is received in response without impact on the traffic and that the link 1–1 enters in the "Local and remote inhibiting" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|------|--|------|------|--|------|----------------|--|--|----------------|--------|--|--|-------|----------------|-------------------------|--|--|------------------|--------|--|--|-------|------------------|------------------|--------|--|--|-------|------------------|-----------------------------------|--|--|------------------------|--------|--|--|-------|------------------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.5 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Inhibition asked by the both ends of a link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the action of the system on reception of an LIN after sending of an LIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1–1, 2 TRAFFIC —————→
←———— 1–1, 2 TRAFFIC
1–1 :Request inhibition
1–X LIN, SLC 1–1 —————→
←———— 1–X LIN, SLC 1–1
1–1 LIA, SLC 1–1 —————→
←———— 1–X LIA, SLC 1–1
TIME-CONTROLLED CHANGEOVER (Note)
1–2 TRAFFIC (from 1–1) —————→
←———— 1–2 TRAFFIC (from 1–1)
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1, 2 TRAFFIC | —————→ | | | ←———— | 1–1, 2 TRAFFIC | 1–1 :Request inhibition | | | 1–X LIN, SLC 1–1 | —————→ | | | ←———— | 1–X LIN, SLC 1–1 | 1–1 LIA, SLC 1–1 | —————→ | | | ←———— | 1–X LIA, SLC 1–1 | TIME-CONTROLLED CHANGEOVER (Note) | | | 1–2 TRAFFIC (from 1–1) | —————→ | | | ←———— | 1–2 TRAFFIC (from 1–1) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 :Request inhibition | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–X LIN, SLC 1–1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–X LIN, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 LIA, SLC 1–1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–X LIA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TIME-CONTROLLED CHANGEOVER (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC (from 1–1) | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 TRAFFIC (from 1–1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – A changeover procedure is performed but not described in this inhibition test. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–1 and 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Request inhibition of link 1–1. Check the reception of LIN and response with an LIN. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check the reception of an LIA and send an LIA. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that the inhibition is correctly performed and that the link enters in the "Local and remote inhibiting" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--|--| +| TEST NUMBER: 7.6.1 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Manual uninhibition of a link – With changeback | | | | | | +| PURPOSE: To check for correct restoration when link uninhibition is requested by an operator | | | | | | +| PRE-TEST CONDITIONS: End of test 7.1.1 | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2 | TRAFFIC | → | | | | +| | | ← | | | | +| 1-1 | :Request uninhibition | | | | | +| 1-2 | LUN, SLC 1-1 | → | | | | +| | | ← | | | | +| 1-2 | LUA, SLC 1-1 | | | | | +| CHANGEBACK (Note) | | CHANGEBACK (Note) | | | | +| 1-1 | TRAFFIC (from 1-2) | → | | | | +| | | ← | | | | +| 1-1 | TRAFFIC (from 1-2) | | | | | +| 1-2 | TRAFFIC | → | | | | +| | | ← | | | | +| 1-2 | TRAFFIC | | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – A changeback procedure is performed after uninhibition of link 1-1 but it is not described in this test which checks only uninhibition procedure. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on link 1-2. | | | | | +| 2. | Request uninhibition of link 1-1, check the reception of an LUN and response with an LUA inside T12. | | | | | +| 3. | Check that the uninhibition is performed and stop traffic. | | | | | +| 4. | Check that the traffic was shared on links 1-1 and 1-2 according to the load sharing rules. | | | | | +| 5. | Check that an uninhibition indication was given by the system. | | | | | +| 6. | When B has initiated inhibition (point 5, test 7.1.1), repeat test in reverse direction. Check that uninhibition is not possible when it is requested by an operation in A. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|-------------|--------|--|--|--------|-------------|---------------------------|--|--|------------------|--------|--|--|--------|------------------|-------------|--------|--|--|--------|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.6.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Manual uninhibition of a link – Without changeback | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check manual uninhibition procedure when the uninhibited link stays unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: End of test 7.1.2 without activation of link 1-2 (link 1-2 deactivated and inhibited) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–1 TRAFFIC —————→
←————— 1–1 TRAFFIC
1–2 :Request uninhibition
1–1 LUN, SLC 1–2 —————→
←————— 1–1 LUA, SLC 1–2
1–1 TRAFFIC —————→
←————— 1–1 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1 TRAFFIC | —————→ | | | ←————— | 1–1 TRAFFIC | 1–2 :Request uninhibition | | | 1–1 LUN, SLC 1–2 | —————→ | | | ←————— | 1–1 LUA, SLC 1–2 | 1–1 TRAFFIC | —————→ | | | ←————— | 1–1 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 :Request uninhibition | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 LUN, SLC 1–2 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1–1 LUA, SLC 1–2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic B (and C in VAT) on link 1–1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Request uninhibition of link 1–2 and check that an LUN is received and that an LUA is sent in response inside T12. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that uninhibition is performed correctly and that link 1–2 stays unavailable. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | When B has initiated inhibition (point 6, test 7.1.2), repeat test in reverse direction. Check that uninhibition is not possible when it is requested by an operator in A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--| +| TEST NUMBER: 7.7 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Expiration of T12 | | | | | | +| PURPOSE: To check uninhibition procedure on expiration of time T12 | | | | | | +| PRE-TEST CONDITIONS: End of test 7.1.1 (1-1 inhibited by A) | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2 TRAFFIC | —————→ | | | | | +| | ←———— | 1-2 TRAFFIC | | | | +| 1-2 :Request uninhibition | | | | | | +| 1-2 LUN, SLC 1-1 | —————→ | | | | | +| | | | | | | +| | T12 | | | | | +| | | | | | | +| 1-2 LUN, SLC 1-2 | —————→ | | | | | +| | ←———— | 1-2 LUA, SLC 1-1 | | | | +| CHANGEBACK (Note) | | CHANGEBACK (Note) | | | | +| 1-1 TRAFFIC (from 1-2) | —————→ | | | | | +| | ←———— | 1-1 TRAFFIC (from 1-2) | | | | +| 1-2 TRAFFIC | —————→ | | | | | +| | ←———— | 1-2 TRAFFIC | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – A changeback procedure is performed but not described in this uninhibition test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic B and C on link 1-2. | | | | | +| 2. | Request uninhibition of link 1-1 and check that an LUN is received. | | | | | +| 3. | Check that after expiration of T12, a new LUN is received and acknowledged by an LUA. | | | | | +| 4. | Check that uninhibition is performed correctly. | | | | | +| 5. | Stop traffic and check it was shared on links 1-1 and 1-2 according with the load sharing rules and that it was not disturbed. | | | | | +| 6. | Repeat the test but without sending of an LUA. Check that after the second expiration of T12, the procedure is stopped and an indication is given to the management. | | | | | +| 7. | Check that the duration of T12 is inside the specified range. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-----------------|------|--|------|----------|--|----------|-----|-------------|--|---------|---------------------------|--| +| TEST NUMBER: 7.8 | | PAGE: 1 of 1 | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | +| SUBTITLE: Not possible uninhibition | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system when the uninhibition is not possible | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link 1–2 unavailable and inhibited and link 1–1 available | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
1–1 :Deactivate

1–X
:Request uninhibition
| | | SP A | | SP B |
Link | |
Link | 1–1 | :Deactivate | |
1–X |
:Request uninhibition | | +| SP A | | SP B | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | +| 1–1 | :Deactivate | | | | | | | | | | | | | | +|
1–X |
:Request uninhibition | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +| 1. | Deactivate link 1–1. | | | | | | | | | | | | | | +| 2. | Check that uninhibition is not performed. | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------|--|------|----------|--|----------|----------------|--|--|-------------|-----------------------|--|--|-----------------------|-------------|---------------------------|--|--|------------------|-----------------------|--|--|-----------------------|------------------|-------------|-----------------------|--|--|-----------------------|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.9 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Automatic uninhibition of a link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the system performs uninhibition procedure when a point becomes inaccessible | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: End of test 7.1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B

Link
Link
:Start traffic
1–2 TRAFFIC ————————————————————>
<———————————————————— 1–2 TRAFFIC
1–2 :Deactivate (failure)
1–1 LUN, SLC 1–1 ————————————————————>
<———————————————————— 1–1 LUA, SLC 1–1
1–1 TRAFFIC ————————————————————>
<———————————————————— 1–1 TRAFFIC
:Wait
:Stop traffic

NOTE – When link 1–1 becomes available, point restart procedure is applied in A and B but it is not described in this inhibition test to simplify the test description.

| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–2 TRAFFIC | ————————————————————> | | | <———————————————————— | 1–2 TRAFFIC | 1–2 :Deactivate (failure) | | | 1–1 LUN, SLC 1–1 | ————————————————————> | | | <———————————————————— | 1–1 LUA, SLC 1–1 | 1–1 TRAFFIC | ————————————————————> | | | <———————————————————— | 1–1 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | ————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 :Deactivate (failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 LUN, SLC 1–1 | ————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 1–1 LUA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | ————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate link 1–2 and check that an LUN is received on link 1–1 and response with an LUA within T12. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that uninhibition is performed and that the traffic is restarted on link 1–1 (see Note). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic, some messages have been lost. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test but without sending of an LUA. Check that after the second expiration of T12 the procedure is stopped, an indication is given to the OMAP and the link 1–1 does not carry traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|-------------|--------------|--|--|--------------|-------------|---------------------------|--|--|------------------|--------------|--|--|--------------|------------------|------------------|--------------|--|-------------|--------------|--|--|--------------|-------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 7.10.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Forced uninhibition of a link – Sending of an LFU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check forced uninhibition procedure when a point becomes inaccessible | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link 1–1 available, link 1–2 inhibited by B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1–1 TRAFFIC ───────────>
<─────────── 1–1 TRAFFIC
1–1 :Deactivate (failure)
1–2 LFU, SLC 1–2 ───────────>
<─────────── 1–2 LUN, SLC 1–2
1–2 LUA, SLC 1–2 ───────────>
1–2 TRAFFIC ───────────>
<─────────── 1–2 TRAFFIC

:Wait
:Stop traffic

NOTE – When link 1–2 becomes available, point restart procedure is applied in A and B but it is not described in this inhibition test to simplify the test description.

| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1 TRAFFIC | ───────────> | | | <─────────── | 1–1 TRAFFIC | 1–1 :Deactivate (failure) | | | 1–2 LFU, SLC 1–2 | ───────────> | | | <─────────── | 1–2 LUN, SLC 1–2 | 1–2 LUA, SLC 1–2 | ───────────> | | 1–2 TRAFFIC | ───────────> | | | <─────────── | 1–2 TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | ───────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <─────────── | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 :Deactivate (failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 LFU, SLC 1–2 | ───────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <─────────── | 1–2 LUN, SLC 1–2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 LUA, SLC 1–2 | ───────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | ───────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <─────────── | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate link 1–1 and check the reception of an LFU on link 1–2. Response by an LUN. Check that T13 is stopped and that an LUA is received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that uninhibition is performed and that the traffic is restarted on link 1–2 (see Note). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic, some messages have been lost. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|-----|-----------|--|--|---|-------------|--|---|------------------|-----|----------------|--|--|---|------------------|--|-------------------|--|-----|-----------|--|--|---|-------------|-----|-----------|--|--|---|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.10.2 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Forced uninhibition of a link – Reception of an LFU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check uninhibition procedure on reception of an LFU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 available, link 1-2 inhibited by A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP ASP B
LinkLink
:Start traffic
1-1TRAFFIC →
←1-1 TRAFFIC
←1-2 LFU, SLC 1-2
1-1LUN, SLC 1-2 →
←1-1 LUA, SLC 1-2
CHANGEBACK (Note)
1-1TRAFFIC →
←1-1 TRAFFIC
1-1TRAFFIC →
←1-2 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1 | TRAFFIC → | | | ← | 1-1 TRAFFIC | | ← | 1-2 LFU, SLC 1-2 | 1-1 | LUN, SLC 1-2 → | | | ← | 1-1 LUA, SLC 1-2 | | CHANGEBACK (Note) | | 1-1 | TRAFFIC → | | | ← | 1-1 TRAFFIC | 1-1 | TRAFFIC → | | | ← | 1-2 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | TRAFFIC → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-2 LFU, SLC 1-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | LUN, SLC 1-2 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1 LUA, SLC 1-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CHANGEBACK (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | TRAFFIC → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | TRAFFIC → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1-2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – A changeback is performed but not described in this uninhibition test. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1-1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send an LFU to A on link 1-2 and check that an LUN is received within T13 and acknowledged by an LUA inside T12. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the uninhibition is performed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it was carried on 1-1 and 1-2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--|--| +| TEST NUMBER: 7.11 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Expiration of T13 | | | | | | +| PURPOSE: To check uninhibition procedure when T13 expires | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 available and link 1-2 inhibited by B | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 | TRAFFIC | —————→ | | | | +| | | ←————— | | | | +| 1-1 | :Deactivate (failure) | | | | | +| 1-2 | LFU, SLC 1-2 | —————→ | | | | +| |
T13
| | | | | +| 1-2 | LFU, SLC 1-2 | —————→ | | | | +| | | ←————— | | | | +| 1-2 | LUA, SLC 1-2 | —————→ | | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←————— | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on link 1-1. | | | | | +| 2. | Deactivate link 1-1 and check the reception of an LFU. After T13 expires, check the reception of a second LFU and send an LUN. Check the reception of an LUA. | | | | | +| 3. | Check that uninhibition is performed correctly. | | | | | +| 4. | Stop traffic and check that it has been restarted on link 1-2. Some messages have been lost. | | | | | +| 5. | Repeat the test but without sending an LUN. Check that after the second expiration of T13 the procedure is stopped, that an indication is given to the OMAP and that the link 1-2 does not carry traffic. | | | | | +| 6. | Check that the duration of T13 is inside the specified range. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------|------|--|------|------|--|------|----------------|--|--|----------------|--------|--|--|-------|----------------|--|-------|------------------|----------------|--------|--|--|-------|----------------|--|-------|------------------|------------------|--------|--|----------------|--------|--|--|-------|----------------|--|-------|------------------|------------------|--------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.12 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Additional uninhibition messages (LUA, LUN, LFU) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of an additional LUA, LUN or LFU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–1, 2 TRAFFIC —————→
←———— 1–1, 2 TRAFFIC
←———— 1–2 LUA, SLC 1–1
1–1, 2 TRAFFIC —————→
←———— 1–1, 2 TRAFFIC
←———— 1–2 LUN, SLC 1–1
1–X LUA, SLC 1–1 —————→
1–1, 2 TRAFFIC —————→
←———— 1–1, 2 TRAFFIC
←———— 1–2 LFU, SLC 1–1
1–X LUN, SLC 1–1 —————→
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1, 2 TRAFFIC | —————→ | | | ←———— | 1–1, 2 TRAFFIC | | ←———— | 1–2 LUA, SLC 1–1 | 1–1, 2 TRAFFIC | —————→ | | | ←———— | 1–1, 2 TRAFFIC | | ←———— | 1–2 LUN, SLC 1–1 | 1–X LUA, SLC 1–1 | —————→ | | 1–1, 2 TRAFFIC | —————→ | | | ←———— | 1–1, 2 TRAFFIC | | ←———— | 1–2 LFU, SLC 1–1 | 1–X LUN, SLC 1–1 | —————→ | | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 LUA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 LUN, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–X LUA, SLC 1–1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 LFU, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–X LUN, SLC 1–1 | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–1 and 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send an LUA (SLC 1–1) on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that this message has been ignored without impact on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Send an LUN (SLC 1–1) on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that an LUA is received in response without impact on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Send an LFU (SLC 1–1) on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | Check that an LUN is received in response without impact on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|----------------------|------|--|------|------|--|------|----------------|--|--|-----------------|--------|--|--|--------|-----------------|-------------------------------|--|--|----------------------|--------|--|--|--------|----------------------|-----------------|--------|--|--|--------|-----------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.13 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Uninhibition at one side after test 7.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check uninhibition procedure when the inhibition has been asked by the two ends of a link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: End of test 7.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1–2     TRAFFIC —————>
<————— 1–2     TRAFFIC
1–1     :Request uninhibition
1–2     LUN, SLC 1–1 —————>
<————— 1–2     LUA, SLC 1–1
1–2     TRAFFIC —————>
<————— 1–2     TRAFFIC
:Wait
:Stop traffic














| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–2     TRAFFIC | —————> | | | <————— | 1–2     TRAFFIC | 1–1     :Request uninhibition | | | 1–2     LUN, SLC 1–1 | —————> | | | <————— | 1–2     LUA, SLC 1–1 | 1–2     TRAFFIC | —————> | | | <————— | 1–2     TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2     TRAFFIC | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–2     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1     :Request uninhibition | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2     LUN, SLC 1–1 | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–2     LUA, SLC 1–1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2     TRAFFIC | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–2     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C on link 1–2. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Request uninhibition of link 1–1. Check that an LUN is received and response with an LUA within T12. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the link stays inhibited (by B). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat test in reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------|------------------|--|--| +| TEST NUMBER: 7.14 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Automatic uninhibition after test 7.5 | | | | | | +| PURPOSE: To check automatic uninhibition of a link when the inhibition has been initiated by the both ends | | | | | | +| PRE-TEST CONDITIONS: End of test 7.5 | | | | | | +| CONFIGURATION: A | | TYPE OF TEST: VAT | | | | +| TYPE OF SP: ALL | | | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | | SP B | | | +| Link | | | Link | | | +| :Start traffic | | | | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←———— | 1-2 TRAFFIC | | | +| 1-2 | :Deactivate (failure) | | | | | +| 1-1 | LUN, SLC 1-1 | —————→ | | | | +| 1-1 | LFU, SLC 1-1 | —————→ | | | | +| | | ←———— | 1-1 LUN, SLC 1-1 | | | +| | | ←———— | 1-1 LFU, SLC 1-1 | | | +| | | ←———— | 1-1 LUA, SLC 1-1 | | | +| | | ←———— | 1-1 LUN, SLC 1-1 | | | +| 1-1 | LUA, SLC 1-1 | —————→ | | | | +| 1-1 | LUN, SLC 1-1 | —————→ | | | | +| 1-1 | LUA, SLC 1-1 | —————→ | | | | +| | | ←———— | 1-1 LUA, SLC 1-1 | | | +| 1-1 | TRAFFIC | —————→ | | | | +| | | ←———— | 1-1 TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on link 1-2. | | | | | +| 2. | Deactivate link 1-2 and check that uninhibition and forced uninhibition are requested by the both ends which send LFU. | | | | | +| 3. | Check that one LUN is sent. Each LUA from B is acknowledgement by an LUA from A . | | | | | +| 4. | Check that the traffic is restarted on link 1-1 and stop traffic. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|-------------------|------|--|------|------|--|------|----------------|--|--|-------------|----------------|--|--|----------------|-------------|---------------------------|--|--|------------------|----------------|--|---------------------|----------------|--|-------------------------------------------------------------------|--|--|--|----------------|-------------------|--|--|--------|--|----------------|------------------|-------------|----------------|--|--------|----------------|-------------|-------------|----------------|--------|--|----------------|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 7.15 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Automatic uninhibition with two links inhibited | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system when two links are inhibited and when the third (and last) link is deactivated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Links 1–1 and 1–2 inhibited (by A) and link 1–3 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–3 TRAFFIC ─────────────>
<───────────── 1–3 TRAFFIC
1–3 :Deactivate (failure)
1–X LUN, SLC 1–1 ─────────────>
and/or LUN, SLC 1–2 ─────────────>
(implementation dependent: at least one link must be uninhibited)
<───────────── 1–X LUA, SLC 1–1,
and/or
<───────────── 1–X LUA, SLC 1–2
1–1 TRAFFIC ─────────────>
and/or <───────────── 1–1 TRAFFIC
1–2 TRAFFIC ─────────────> and/or
<───────────── 1–2 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–3 TRAFFIC | ─────────────> | | | <───────────── | 1–3 TRAFFIC | 1–3 :Deactivate (failure) | | | 1–X LUN, SLC 1–1 | ─────────────> | | and/or LUN, SLC 1–2 | ─────────────> | | (implementation dependent: at least one link must be uninhibited) | | | | <───────────── | 1–X LUA, SLC 1–1, | | | and/or | | <───────────── | 1–X LUA, SLC 1–2 | 1–1 TRAFFIC | ─────────────> | | and/or | <───────────── | 1–1 TRAFFIC | 1–2 TRAFFIC | ─────────────> | and/or | | <───────────── | 1–2 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–3 TRAFFIC | ─────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <───────────── | 1–3 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–3 :Deactivate (failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–X LUN, SLC 1–1 | ─────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| and/or LUN, SLC 1–2 | ─────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (implementation dependent: at least one link must be uninhibited) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <───────────── | 1–X LUA, SLC 1–1, | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | and/or | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <───────────── | 1–X LUA, SLC 1–2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | ─────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| and/or | <───────────── | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | ─────────────> | and/or | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <───────────── | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Deactivate link 1–3. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that at least one LUN is received and acknowledged with an LUA. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the traffic is restarted on linkset 1. Some messages have been lost. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|----------|--|----------|----------------|--|--|----------------|-----------------------|--|--|-----------------------|----------------|--|-----------------------|----------------|-----------|--|--|---------------|--|--| +| TEST NUMBER: 7.16 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Management inhibiting | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Reception of traffic on an inhibited link | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of traffic on an inhibited link | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link 1–1 inhibited by A, link 1–2 available | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–2    TRAFFIC ————————————————————>
<———————————————————— 1–2    TRAFFIC
<———————————————————— 1–1    TRAFFIC

:Wait
:Stop traffic
| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–2    TRAFFIC | ————————————————————> | | | <———————————————————— | 1–2    TRAFFIC | | <———————————————————— | 1–1    TRAFFIC |
:Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2    TRAFFIC | ————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 1–2    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———————————————————— | 1–1    TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | +|
:Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic on link 1–1. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send traffic from B to A on the inhibited link 1–2. Check that the messages received in A are normally treated. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------|--|--|--| +| TEST NUMBER: 7.17.1 | | PAGE: 1 of 3 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Management inhibiting test – Normal procedure | | | | | | +| PURPOSE: To check that the system performs correctly the management inhibiting test | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 inhibited by A, other links are available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| 1-X LLT, SLC 1-1 | —————→ | | | | | +| , , , , , T22 | ←————— | 1-X LRT, SLC 1-1 | | | | +| — | | , , , , , T23 | | | | +| | | — | | | | +| 1-X LLT, SLC 1-1 | —————→ | | | | | +| , , , , , | ←————— | 1-X LRT, SLC 1-1 | | | | +| | | , , , , , | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Check that an LLT is periodically sent by A and check (in VAT) that the duration of timer T22 is inside the specified range. | | | | | +| 2. | Check that on the reception of an LRT, no action is taken in A. | | | | | +| 3. | As compatibility test, check that an LRT is periodically sent from B to A. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|------------------|--|--|--| +| TEST NUMBER: 7.17.1 (continued) | | PAGE: 2 of 3 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Inhibiting test procedure – Normal procedure | | | | | | +| PURPOSE: See page 1 | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 inhibited by B, other links are available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| 1-X | LRT, SLC 1-1 | → | | | | +| | , , , , , T23 | ← | | | | +| | — | 1-X LLT, SLC 1-1 | | | | +| | | , , , , , T22 | | | | +| | | — | | | | +| 1-X | LRT, SLC 1-1 | → | | | | +| | , , , , , | ← | | | | +| | | 1-X LLT, SLC 1-1 | | | | +| | | , , , , , | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Check that an LRT is periodically sent by A and, in VAT, check that the duration of the timer T23 is inside the specified range. | | | | | +| 2. | Check that, on the reception of an LLT, no action is taken in A. | | | | | +| 3. | As compatibility test, check that an LLT is periodically sent from B to A. | | | | | + +###### **MTP Level 3** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 7.17.1 (concluded) | | PAGE: 3 of 3 | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | +| TITLE: Management inhibiting | | | +| SUBTITLE: Inhibit test procedure – Normal procedure | | | +| PURPOSE: See page 1 | | | +| PRE-TEST CONDITIONS: Link 1-1 inhibited by A and B. The other links are available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

1-X      LLT, SLC 1-1      —————→

         , , , , ,

1-X    LRT                      —————→

         , , , , ,      —

         —    SLC 1-1,,T22    ←————

         T23    LLT, SLC 1-1      —————→

1-X      , , , , ,      ←————

         LRT,                      —————→

1-X    , , , , , , SLC 1-1,, T22    ←————

         T23

1-X    LRT, SLC 1-1

         , , , , , , T23

1-X      —              LLT, SLC 1-1

1-X                      , , , , ,

                         LRT,

1-X                      , , , , , , T23    ,,T22,SLC 1-1

1-X                      —              LLT, SLC 1-1

                         , , , , , , T22

| | | +| TEST DESCRIPTION | | | +| 1. | Check that the LLT and LRT messages are periodically sent from A to B and from B to A. | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------|--------------|--|--| +| TEST NUMBER: 7.17.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Inhibit test procedure – Reception of an LLT or LRT on an uninhibited link | | | | | | +| PURPOSE: To check the actions of the system on reception of an LLT or LRT on an uninhibited link | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| | | 1-1 | LLT, SLC 1-1 | | | +| | ←————— | | | | | +| 1-1 | —————→ | | | | | +| LFU, SLC 1-1 | | | | | | +| , , , , , T13 | | | | | | +| — | | | | | | +| | | 1-1 | LUN, SLC 1-1 | | | +| | ←————— | | | | | +| 1-1 | —————→ | | | | | +| LUA, SLC 1-1 | | | | | | +| | | 1-1 | LRT, SLC 1-1 | | | +| | ←————— | | | | | +| 1-1 | —————→ | | | | | +| LLT, SLC 1-1 | | | | | | +| , , , , , T12 | | | | | | +| — | | | | | | +| | | 1-1 | LUA, SLC 1-1 | | | +| | ←————— | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Send an LLT from B to A and check that an LFU is received. Then, send an LUN and check that an LUA is received. | | | | | +| 2. | Send an LRT from B to A and check that an LUN is received. Answer with an LUA. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------|--------------|--|--| +| TEST NUMBER: 7.17.3 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | | | | +| TITLE: Management inhibiting | | | | | | +| SUBTITLE: Inhibit test procedure – Reception of an LLT on a link locally inhibited | | | | | | +| PURPOSE: To check the actions of the system on reception of an LLT on a link locally (not remotely) inhibited | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 inhibited in A, other links are available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| | | 1-X | LLT, SLC 1-1 | | | +| 1-1 | LFU, SLC 1-1 | ←—————→ | | | | +| | , , , , , T13 | | | | | +| | — | | | | | +| | | 1-X | LUN, SLC 1-1 | | | +| 1-X | LUA, SLC 1-1 | ←—————→ | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Send an LLT from B to A and check that an LFU is received as described above. | | | | | + +###### **MTP Level 3** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 7.17.4 | | PAGE: 1 of 1 | +| REFERENCE: clause 10/Q.704 Fig. 28 | | | +| TITLE: Management inhibiting | | | +| SUBTITLE: Inhibit test procedure – Reception of an LRT on a link remotely inhibited | | | +| PURPOSE: To check the actions of the system on reception of an LRT on a link remotely inhibited | | | +| PRE-TEST CONDITIONS: Link 1-1 inhibited by B, other links are available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

1-X    LUN, SLC 1-1

       , , , , , T12

      —

←—————

—————→

←—————

1-X    LRT, SLC 1-1


1-X    LUA, SLC 1-1

| | | +| TEST DESCRIPTION | | | +| 1. | Send an LRT from B to A and check that an LUN is received as described above. | | + +###### **MTP Level 3** + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 8.1 | | PAGE: 1 of 1 | +| REFERENCE: clause 11 and 12.6/Q.704     Fig. 46A | | | +| TITLE: Signalling traffic flow control | | | +| SUBTITLE: Reception of a TFC | | | +| PURPOSE: To check the actions of the system on reception of a TFC | | | +| PRE-TEST CONDITIONS: One or more link available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +|

MESSAGE SEQUENCE:

SP A

Link
:Start traffic
1–1    TRAFFIC


:Wait
:Stop traffic



—>
<—
<—
SP B

Link


1–1    TRAFFIC
1–1    TFC, DPC = C












NOTE – This test requires further study.

| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C. | | +| 2. | Send a TFC concerning C and check that this message is received correctly. | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|--------------------|--|--| +| TEST NUMBER: 8.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 11 and 12.6/Q.704 Fig. 46A | | | | | | +| TITLE: Signalling traffic flow control | | | | | | +| SUBTITLE: Sending of TFCs | | | | | | +| PURPOSE: To check the detection of a level 3 congestion | | | | | | +| PRE-TEST CONDITIONS: All links available | | | | | | +| CONFIGURATION: C | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | | | | +| Link | Link | Link | | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC | (>n/2 E) → | 2-1 — (n E) → | | | | +| | ← | 1-1 ← | 2-1 TRAFFIC (n/2 E) → | 2-1 — (n E) → | | | | +| | ← | 1-2 ← | 2-1 TRAFFIC (n/2 E) → | 2-1 → | | | | +| | ← | 1-1 ← | 2-1 TRAFFIC | | | +| 1-2 TRAFFIC | (>n/2 E) → | 2-1 → | | | | +| | ← | 1-2 ← | 2-1 TRAFFIC (MESSAGE SEQUENCE:

SP ASP B
LinkLink
:Start traffic
1-1TRAFFIC
(DPC = B, SI = X)		—————→
1-1TRAFFIC
(DPC = C, SI = X)		—————→
←—————1-1 TRAFFIC
(OPC = C, SI = X)
←—————1-1 UPU
(OPC = B, SI = X)
1-1TRAFFIC
(DPC = C, SI = X)		—————→
←—————1-1 TRAFFIC
(OPC = C, SI = X)
:Wait
:Stop traffic

NOTE – The impact of the reception of a UPU on the traffic from A to B requires further study. The SPs having user part(s) are concerned.

| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1 | TRAFFIC
(DPC = B, SI = X) | —————→ | 1-1 | TRAFFIC
(DPC = C, SI = X) | —————→ | | ←————— | 1-1 TRAFFIC
(OPC = C, SI = X) | | ←————— | 1-1 UPU
(OPC = B, SI = X) | 1-1 | TRAFFIC
(DPC = C, SI = X) | —————→ | | ←————— | 1-1 TRAFFIC
(OPC = C, SI = X) | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | TRAFFIC
(DPC = B, SI = X) | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | TRAFFIC
(DPC = C, SI = X) | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-1 TRAFFIC
(OPC = C, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-1 UPU
(OPC = B, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 | TRAFFIC
(DPC = C, SI = X) | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————— | 1-1 TRAFFIC
(OPC = C, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C with SI = X. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send a UPU from B to C with SI = X with the cause "unknown". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the UPU message is received correctly without impact on the traffic from A to C. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Wait and stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test with a UPU with the cause "unequipped", and with the cause "unavailable". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|------|--|------|------|--|------|----------------|--|--|-------------------------------------|--------|--|--|-------|---------------------------------------|--------------------------------|--|--|--|-------|--------------------------------------|------------------------------|--------|--|--|-------|--------------------------------------|------------------------------|--------|--|--|-------|--------------------------------------|------------------------------|--------|--|-------------------------|--|--|--|-------|--------------------------------------------|-------------------------------------|--------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 8.4 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 11.2.7/Q.704 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling traffic flow control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Sending of a UPU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the detection of an unavailability of a user part | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: One link available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: See Note | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B
Link Link
:Start traffic
1-1 TRAFFIC
(to B and C, SI = X)		 —————>
<———— 1-1 TRAFFIC
(from B and C, SI = X)
:Deactivate user part X (Note)
<———— 1-1 MESSAGE
(from B to A, SI = X)
1-1 UPU
(DPC = B, SI = X)		 —————>
<———— 1-1 MESSAGE
(from C to A, SI = X)
1-1 UPU
(DPC = C, SI = X)		 —————>
<———— 1-1 MESSAGE
(from B to A, SI = X)
1-1 UPU
(DPC = B, SI = X)		 —————>
:Reactivate user part X
<———— 1-1 TRAFFIC
(from B and C to A, SI = X)
1-1 TRAFFIC
(to B and C, SI = X)		 —————>
:Wait
:Stop traffic

NOTE – The notion of unavailability of a user part is specific to the implementation; consequently, the ability to deactivate a user part is implementation dependent. The SPs having user part(s) are concerned.

| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1-1 TRAFFIC
(to B and C, SI = X) | —————> | | | <———— | 1-1 TRAFFIC
(from B and C, SI = X) | :Deactivate user part X (Note) | | | | <———— | 1-1 MESSAGE
(from B to A, SI = X) | 1-1 UPU
(DPC = B, SI = X) | —————> | | | <———— | 1-1 MESSAGE
(from C to A, SI = X) | 1-1 UPU
(DPC = C, SI = X) | —————> | | | <———— | 1-1 MESSAGE
(from B to A, SI = X) | 1-1 UPU
(DPC = B, SI = X) | —————> | | :Reactivate user part X | | | | <———— | 1-1 TRAFFIC
(from B and C to A, SI = X) | 1-1 TRAFFIC
(to B and C, SI = X) | —————> | | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC
(to B and C, SI = X) | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— | 1-1 TRAFFIC
(from B and C, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Deactivate user part X (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— | 1-1 MESSAGE
(from B to A, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 UPU
(DPC = B, SI = X) | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— | 1-1 MESSAGE
(from C to A, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 UPU
(DPC = C, SI = X) | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— | 1-1 MESSAGE
(from B to A, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 UPU
(DPC = B, SI = X) | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Reactivate user part X | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <———— | 1-1 TRAFFIC
(from B and C to A, SI = X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC
(to B and C, SI = X) | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C with SI = X. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate the user part X. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Send a message from B to the user part X in A and check that this message is discarded and that a UPU is sent back with the cause "unavailable". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Send a message from C to the user part X in A and check that this message is discarded and that a UPU is sent back with the cause "unavailable". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat point 3 and reactivate the user part. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Check that the messages sent from B and C are received correctly and that no UPU is sent back. Wait and stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | Repeat the test for an unequipped user part, and verify that a UPU is sent back with the cause "unequipped". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|--|--| +| TEST NUMBER: 9.1.1 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Sending of a TFP on an alternative route – Failure of normal linkset | | | | | | +| PURPOSE: To check the sending of a TFP on the alternative route when the normal linkset becomes unavailable | | | | | | +| PRE-TEST CONDITIONS: All linksets available | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC →
(from A and F) | 5-1 →
6-1 → | → SP D
→ SP E | | | | +| 2-1 TRAFFIC
(from A and F) | → | 7-1 → | SP E | | | +| 1-1 :Deactivate | (MML command or failure) | | | | | +| 2-1 TFP, PC = B | → | | | | | +| 2-1 TFP, PC = D | → | | | | | +| 2-1 TRAFFIC
(from 1-1) | → | 7-1 →
8-1 → | SP E
SP D | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – A changeover procedure is performed after deactivation of link 1-1 but it is not described in this transfer prohibited test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E on linkset 1 and 2. | | | | | +| 2. | Deactivate link 1-1 and check that TFPs concerning B and D are sent from A to C (alternative route to reach B and D). Check that no TFP concerning E is sent from A to C (load sharing between linksets 1 and 2 in A to reach E). | | | | | +| 3. | Check that time out T8 is started for each TFP sent. | | | | | +| 4. | Check that the traffic to D and E is diverted to C. | | | | | +| 5. | Stop traffic and check that it was not disturbed. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-----------------|--------------|--|--| +| TEST NUMBER: 9.1.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Sending of a TFP on an alternative route – On reception of a TFP | | | | | | +| PURPOSE: To check the sending of a TFP on the alternative route when the normal route becomes unavailable on reception of a TFP | | | | | | +| PRE-TEST CONDITIONS: Linkset 4 unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP E • | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC
(from A and F) | → 5-1
→ 6-1 | | SP D
SP E | | | +| 2-1 TRAFFIC
(from A and F) | → | 7-1 → | SP E | | | +| | 5-1 :Deactivate | | | | | +| (Note) | ← 1-1 TFP, PC = D | | | | | +| 2-1 TFP, PC=D | → | | | | | +| 1-1 TRAFFIC
(from A and F) | → 6-1 | | SP E | | | +| 2-1 TRAFFIC
(from A and F, and from 1-1 to D) | → | 8-1 →
7-1 → | SP D
SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – A forced rerouting is performed after the reception of TFP for D in A but it is not described in this transfer prohibited test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E. | | | | | +| 2. | Deactivate link 5-1 and check that a TFP concerning D is sent to A. | | | | | +| 3. | Check that a TFP concerning D is received from A and that traffic to D is diverted via C. | | | | | +| 4. | Check that a time out T8 is started. | | | | | +| 5. | Stop traffic and check that traffic to E has not been disturbed. Some messages to D may have been lost. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-----------------|------|------|------|------|------|------|------|------|----------------|--|--|--|----------------------------------|---------------------------------------|--|--|-----------------|--------------------------|--|--|-----------------|-------|--|--|-----------------|---------------------|--|--|-------|--|--|--|---------------|--|--|--| +| TEST NUMBER: 9.2.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling route management | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Broadcast of TFPs – On one linkset failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the broadcast of TFPs when one point is inaccessible | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: All linksets available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP F
Link Link Link Link
:Start traffic
3–1 TRAFFIC
(from A, D and E)		 ————————————————————————————————————→
3–1 :Deactivate (MML command or failure)
1–1 TFP, PC = F ————→
2–1 TFP, PC = F ——————————————————→
:Wait
:Stop traffic
| | | SP A | SP B | SP C | SP F | Link | Link | Link | Link | :Start traffic | | | | 3–1 TRAFFIC
(from A, D and E) | ————————————————————————————————————→ | | | 3–1 :Deactivate | (MML command or failure) | | | 1–1 TFP, PC = F | ————→ | | | 2–1 TFP, PC = F | ——————————————————→ | | | :Wait | | | | :Stop traffic | | | | +| SP A | SP B | SP C | SP F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TRAFFIC
(from A, D and E) | ————————————————————————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 :Deactivate | (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TFP, PC = F | ————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1 TFP, PC = F | ——————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – The propagation of TFPs is not presented to simplify the test description. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to F. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate link 1–1 and check that TFPs concerning F are broadcasted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that a timer T8 is started. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------|----------------------|------|------|--|------|------|------|------|--|------|----------------|--|--|--|--|-------------|------------------|--|----------------------|------|----------------|--|--|----------------------|------|------------------------------------------|--|--|--|--|-----------------|-------------------------------------------------|--|--|------|-----------------|-------------------------------------------------|--|--|--|-----------------|-------------------------------------------------|--|--|--|-----------------|-------------------------------------------------|--|--|--|-------|--|--|--|--|---------------|--|--|--|--| +| TEST NUMBER: 9.2.2 | | PAGE: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling route management | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Broadcast of TFPs – On multiple failures | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the broadcast of TFPs when several points are inaccessible (various reasons) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset 1 unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B SP C SP •
Link Link Link Link
:Start traffic
2–1 TRAFFIC ───────────────> 7–1 ───────────────> SP E
(from A and F) 8–1 ───────────────> SP D
2–1 :Deactivate (MML command or failure)
3–1 TFP, PC = B ──────────────────────────────────────────────> SP F
3–1 TFP, PC = C ──────────────────────────────────────────────>
3–1 TFP, PC = D ──────────────────────────────────────────────>
3–1 TFP, PC = E ──────────────────────────────────────────────>
:Wait
:Stop traffic
















| | | SP A | SP B | SP C | | SP • | Link | Link | Link | | Link | :Start traffic | | | | | 2–1 TRAFFIC | ───────────────> | | 7–1 ───────────────> | SP E | (from A and F) | | | 8–1 ───────────────> | SP D | 2–1 :Deactivate (MML command or failure) | | | | | 3–1 TFP, PC = B | ──────────────────────────────────────────────> | | | SP F | 3–1 TFP, PC = C | ──────────────────────────────────────────────> | | | | 3–1 TFP, PC = D | ──────────────────────────────────────────────> | | | | 3–1 TFP, PC = E | ──────────────────────────────────────────────> | | | | :Wait | | | | | :Stop traffic | | | | | +| SP A | SP B | SP C | | SP • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1 TRAFFIC | ───────────────> | | 7–1 ───────────────> | SP E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (from A and F) | | | 8–1 ───────────────> | SP D | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2–1 :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TFP, PC = B | ──────────────────────────────────────────────> | | | SP F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TFP, PC = C | ──────────────────────────────────────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TFP, PC = D | ──────────────────────────────────────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TFP, PC = E | ──────────────────────────────────────────────> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to D and E. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate linkset 2 and check that TFPs concerning B, C, D and E are broadcasted (to F). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that for each TFP sent a timer T8 is started. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat test but with linkset 2 unavailable as pre-test condition and then deactivate linkset 1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|--| +| TEST NUMBER: 9.2.2 (concluded) | | PAGE: 2 of 2 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Broadcast of TFPs – On multiple failures | | | | | | +| PURPOSE: See page 1 | | | | | | +| PRE-TEST CONDITIONS: Linksets 1 and 4 unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP C | SP D | SP • | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC
(from A and F) | —————→ 8-1
—————→ 7-1 | | SP E | | | +| | 8-1 :Deactivate | | | | | +| | ←———— 2-1 TFP, PC = D | | | | | +| 3-1 TFP, PC = D | —————→ | | SP F | | | +| 2-1 TRAFFIC
(from A and F) | —————→ 7-1 | | SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E. | | | | | +| 2. | Deactivate linkset 8 and check that a TFP (PC = D) is sent. Check that TFPs are broadcasted (here to F). | | | | | +| 3. | Check that a time out T8 started. | | | | | +| 4. | Stop traffic and check that traffic to E has not been disturbed. | | | | | +| 5. | Repeat the test with linksets 2 and 4 unavailable as pre-test conditions and then deactivate linkset 5. Repeat the test with linksets 4 and 8 unavailable as pre-test conditions and then deactivate linkset 1. | | | | | +| 6. | Repeat the test with linksets 4 and 5 unavailable as pre-test conditions and then deactivate linkset 2. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------|--------------|--|--| +| TEST NUMBER: 9.3 | | PAGE: 1 of 2 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Reception of a message for an inaccessible destination | | | | | | +| PURPOSE: To check that a TFP is sent in response to a message received for an inaccessible destination | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 4 and 8 unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP F | | | | +| Link | | Link | | | | +| | | :Sent a message to D | | | | +| | ←————— | 3-1 | MESSAGE TO D | | | +| 3-1 | —————→ | | | | | +| TFP, PC = D | | | | | | +| | | | | | | +| T8 | | | | | | +| | | | | | | +| | ←————— | 3-1 | MESSAGE TO D | | | +| TEST DESCRIPTION | | | | | | +| 1. | Send from F a message with DPC = D to A. | | | | | +| 2. | Check that a TFP PC = D is sent in response. Check that a time out T8 is started. | | | | | +| 3. | During T8, send a new message with DPC = D to A and check that no TFP is sent. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------|---------------------|------|-----------------------------------------------------------|------|-------------------------------------------------------------------------------------------------|------|------|----------------|--|--|--|----------------------------------|---------------------------------------|--|------|------------------------------------------|--|--|--|-----------------|-----------------------|--|--|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------------------|--|--|--|--------------| +| TEST NUMBER: 9.3 ( concluded ) | | PAGE: 2 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 44 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling route management | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Reception of a message for an inaccessible destination | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: See page 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linksets 1 and 8 unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
MESSAGE SEQUENCE:
SP A SP B SP C SP •
Link Link Link Link
:Start traffic
3-1 TRAFFIC
(from A, D and E)		 ————————————————————————————————————→ SP F
3-1 :Deactivate (MML command or failure)
2-1 TFP, PC = F ————————————————————→
T8
←————————————————————————————————————
←————————————————————————————————————
4-1

2-1
MESSAGE TO F
| | | SP A | SP B | SP C | SP • | Link | Link | Link | Link | :Start traffic | | | | 3-1 TRAFFIC
(from A, D and E) | ————————————————————————————————————→ | | SP F | 3-1 :Deactivate (MML command or failure) | | | | 2-1 TFP, PC = F | ————————————————————→ | | |
T8
|
←————————————————————————————————————
←————————————————————————————————————
| |
4-1

2-1 | | | | MESSAGE TO F | +| SP A | SP B | SP C | SP • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-1 TRAFFIC
(from A, D and E) | ————————————————————————————————————→ | | SP F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3-1 :Deactivate (MML command or failure) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2-1 TFP, PC = F | ————————————————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
T8
|
←————————————————————————————————————
←————————————————————————————————————
| |
4-1

2-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | MESSAGE TO F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
1. Start traffic to F.
2. Deactivate linkset 3 and check that TFPs are broadcasted.
3. Within T8, send one message with DPC = F from C to A and check that no TFP is sent in response.
| | | 1. | Start traffic to F. | 2. | Deactivate linkset 3 and check that TFPs are broadcasted. | 3. | Within T8, send one message with DPC = F from C to A and check that no TFP is sent in response. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to F. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Deactivate linkset 3 and check that TFPs are broadcasted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Within T8, send one message with DPC = F from C to A and check that no TFP is sent in response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------|--|--| +| TEST NUMBER: 9.4.1 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 45 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Sending of a TFA on an alternative route – Recovery of normal linkset | | | | | | +| PURPOSE: To check the sending of a TFA on an alternative route when the normal linkset becomes available | | | | | | +| PRE-TEST CONDITIONS: Linkset 1 unavailable (end of test 9.1.1) | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 8-1 —————→
7-1 —————→ | SP D
SP E | | | +| 1-1 : Activate (depending on the activation mean previously used) | | | | | | +| 2-1 TFA, PC = B | —————→ | | | | | +| 2-1 TFA, PC = D | —————→ | | | | | +| 1-1 TFP, PC = D | —————→ | | | | | +| 1-1 TFP, PC = E | —————→ | | | | | +| 1-1 TRAFFIC
(from A and F
and from 2-1) | —————→ | 5-1 —————→
6-1 —————→ | SP D
SP E | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 7-1 —————→ | SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – A changeback procedure is performed after activation of link 1-1 but it is not described in this transfer allowed test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E. | | | | | +| 2. | Activate linkset 1 and check that traffic to D and E is diverted on linkset 1 and that a TFA concerning D is sent from A to C. Check that no TFA is sent concerning E (load sharing in A between linksets 1 and 2). | | | | | +| 3. | Stop traffic and check that it was rerouted correctly without loss of messages, duplication and missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------|------|--|--| +| TEST NUMBER: 9.4.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 45 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Sending of a TFA on an alternative route – On reception of a TFA | | | | | | +| PURPOSE: To check that a TFA is sent on the alternative route when the normal route becomes available on reception of a TFA | | | | | | +| PRE-TEST CONDITIONS: Linksets 4 and 5 unavailable (end of test 9.1.2) | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC
(from A and F) | —————→ 6-1 | —————→ | | | | +| 2-1 TRAFFIC
(from A and F) | —————→ 7-1 | | SP E | | | +| | —————→ 8-1 | | SP D | | | +| | 5-1 :Activate | | | | | +| (Note) | ←———— 1-1 TFA, PC = D | | | | | +| 1-1 TFP, PC = D | —————→ | | | | | +| 2-1 TFA, PC = D | —————→ | | | | | +| 1-1 TRAFFIC | —————→ 5-1 | —————→ | | | | +| (from A and F,
from 2-1 to D) | —————→ 6-1 | —————→ | | | | +| 2-1 TRAFFIC
(from A and F) | —————→ 7-1 | | SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – A controlled rerouting is performed after the activation of linkset 5 and it is not described in this transfer allowed test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E. | | | | | +| 2. | Activate link 5-1 and check that a TFA concerning D is sent to A. | | | | | +| 3. | Check that the traffic to D via B and check that a TFA concerning D is sent from A to C. | | | | | +| 4. | Stop traffic and check that traffic was not disturbed. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|-------------------|------|------|------|------|------|------|------|------|------|------------------------|--|--|--|-----------------|-------------------|--|--|-------------|--|-------------------|--|----------------|--|--|--|-------------------------------|--------------------------|--|------|-------|--|--|--|---------------|--|--|--| +| TEST NUMBER: 9.5.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 45 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling route management | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Broadcast of TFAs – On one linkset recovery | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the broadcast of TFA when a destination becomes accessible | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linksets 3 unavailable (end of test 9.2.1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B SP C SP F
Link Link Link Link
3–1 :Activate (Note 1)
1–1 TFA, PC = F ———————> (Note 2)
      TFA, PC = F ———————> (Note 2)
:Start traffic
3–1 TRAFFIC
      (from A and F)		 ———————————————————————> SP F
:Wait
:Stop traffic
| | | | SP A | SP B | SP C | SP F | Link | Link | Link | Link | 3–1 :Activate (Note 1) | | | | 1–1 TFA, PC = F | ———————> (Note 2) | | | TFA, PC = F | | ———————> (Note 2) | | :Start traffic | | | | 3–1 TRAFFIC
(from A and F) | ———————————————————————> | | SP F | :Wait | | | | :Stop traffic | | | | +| SP A | SP B | SP C | SP F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 :Activate (Note 1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TFA, PC = F | ———————> (Note 2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TFA, PC = F | | ———————> (Note 2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3–1 TRAFFIC
(from A and F) | ———————————————————————> | | SP F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

NOTE 1 – After activation of the linkset 3, SPs A and F perform a point restart procedure which is not explicitly described in this test.

NOTE 2 – The propagation of TFAs is not presented to simplify the test description.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Activate linkset 3. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that TFAs concerning F are broadcasted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Start traffic to F and check that it is routed correctly; stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------|------|--|--| +| TEST NUMBER: 9.5.2 | | PAGE: 1 of 2 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 45 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Broadcast of TFAs – Various reasons | | | | | | +| PURPOSE: To check the broadcast of TFA when several destinations become accessible in various network situations | | | | | | +| PRE-TEST CONDITIONS: Linksets 1 and 2 unavailable (end of test 9.2.2 page 1 of 2) | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| 2-1 :Activate | | | | | | +| 2-1 TFA, PC = B | —————→ | | SP F | | | +| 3-1 TFA, PC = C | —————→ | | SP F | | | +| 3-1 TFA, PC = D | —————→ | | SP F | | | +| 3-1 TFA, PC = E | —————→ | | SP F | | | +| 2-1 TFP, PC = B | —————→ | | | | | +| 2-1 TFP, PC = D | —————→ | | | | | +| 2-1 TFP, PC = E | —————→ | | | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC | —————→ | 7-1 ———→ | SP E | | | +| (from A, and F) | | 8-1 ———→ | SP D | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – After activation of the linkset 2, SPs A and C perform the point restart procedure which is not described in this test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Activate linkset 2. | | | | | +| 2. | Check that TFAs concerning B, C, D and E are broadcasted. | | | | | +| 3. | Start traffic and check that it is routed correctly; stop traffic. | | | | | +| 4. | Repeat test but activate linkset 1 instead of linkset 2. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|--| +| TEST NUMBER: 9.5.2 (concluded) | | PAGE: 2 of 2 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 45 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Broadcast of TFAs – Various reasons | | | | | | +| PURPOSE: See page 1 of 2 | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 4 and 8 unavailable (end of test 9.2.2 page 2 of 2) | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 7-1 —————→ | SP E | | | +| | ←————— | 8-1 :Activate | | | | +| | | 2-1 TFA, PC = D | | | | +| 2-1 TFA, PC = D | —————→ | | | | | +| 3-1 TFA, PC = D | —————→ | | SP F | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 7-1 —————→ | SP E | | | +| | | 8-1 —————→ | SP D | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to E. | | | | | +| 2. | Activate linkset 8 and check that a TFA concerning D is sent from C to A. Check that A broadcasts TFAs concerning D. | | | | | +| 3. | Check that the traffic to D is restarted. | | | | | +| 4. | Repeat test with linksets 2, 4 and 5 unavailable as pre-test conditions and activate linkset 5. Repeat test with linksets 1, 4 and 8 unavailable as pre-test conditions and activate linkset 1. Repeat test with linksets 2, 4 and 5 as pre-test conditions and activate linkset 2. | | | | | + +###### **MTP Level 3** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 9.6 | | PAGE: 1 of 1 | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 46 | | | +| TITLE: Signalling route management | | | +| SUBTITLE: Periodic sending of Signalling-Route-Set-Test (SRST) messages | | | +| PURPOSE: To check the periodic test of an unavailable signalling route is performed correctly | | | +| PRE-TEST CONDITIONS: Linkset 2 unavailable | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP F
Link Link

:Start traffic

1-1 TRAFFIC →

1-1 RST, PC = C →

T10

1-1 RST, PC = C →

T10

1-1 TRAFFIC →

← TRAFFIC 1-1

←

2-1 :Activate

← TFA, PC = C 1-1

→ TRAFFIC 1-1

:Wait

:Stop traffic

| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B. | | +| 2. | Check that at each expiration of T10, a signalling-Route-Set-Test message concerning C is received from A without response. | | +| 3. | Activate linkset 2 and check that a TFA is received and that T10 is stopped. | | +| 4. | Check that traffic to C is restarted and stop traffic. | | +| 5. | Repeat the test but without sending of TFA after activation of linkset 2 and check that when a RST is received a TFA is sent in response. Check that T10 and signalling-route-set-test procedure are stopped. | | +| 6. | Check that the duration of T10 is inside the specified range. | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------|--|--|--| +| TEST NUMBER: 9.7 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 13/Q.704 Fig. 29, Fig. 46 | | | | | | +| TITLE: Signalling route management | | | | | | +| SUBTITLE: Reception of a signalling-route-set-test-message | | | | | | +| PURPOSE: To check the actions of the system on reception of an SRST | | | | | | +| PRE-TEST CONDITIONS: Linksets 2 and 3 unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP F | | | | +| Link | Link | Link | | | | +| | ←———— 1-1 RST, PC = F | | | | | +| 3-1 :Activate | | T10 | | | | +| 1-1 TFA, PC = F | ————→ (Ignored) | | | | | +| | ←———— 1-1 RST, PC = F | , , , , , T10 | | | | +| | | | | | | +| | | — | | | | +| 1-1 TFA, PC = F | ————→ | | | | | +| 3-1 TRAFFIC
(from A, D and E) | ————→ | | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Send to A RST message concerning F and check that no response is received. | | | | | +| 2. | Activate linkset 3 and check that a TFA is received but ignored in B. | | | | | +| 3. | Send a RST message concerning F after activation of linkset 3 and check that a TFA is received in response. | | | | | +| 4. | Repeat the test but with linksets 1 and 3 unavailable as pre-test conditions and RST message sent from C. | | | | | + +###### MTP Level 3 + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| TEST NUMBER: 10.1.1 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Recovery of a linkset (SP A does not have an STP function) – With use of point restart procedure | | | | | | +| PURPOSE: To check that point restart procedure is performed correctly when the recovery of a linkset restores connexity between two adjacent SPs | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 2, 4 and 6 unavailable | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: SP | | | | +| MESSAGE SEQUENCE: | | | | | | +|

SP A

Link

3-1, 2 TRAFFIC

2-1 :Activate

2-1 Activation (link in service at level 2)

2-1 T21

2-1 TRA

2-1 TRAFFIC (from 3-1, 2)

3-1, 2 TRAFFIC

:Wait

:Stop traffic

|

SP B

Link

2-1 TFP (PC = C)

2-1 TFP (PC = E)

2-1 TRA

5-1 TFA (PC = A)

TIME CONTROLLED DIVERSION IS APPLIED

5-1

2-1

|

SP C

Link

7-1

8-1

3-1, 2

|

SP ?

Link

SP E

SP D

7-1 SP E

8-1 SP D

SP D

5-1 SP D

SP E

SP D

7-1 SP E

| | | +| NOTE – The time controlled diversion procedure is applied in A and a controlled rerouting is performed in D. These procedures are not described in this point restart test. | | | | | | +| TEST DESCRIPTION | | | | | | +|
  1. 1. Start traffic to E (and D in VAT).
  2. 2. Activate link 2-1.
  3. 3. Check that the time controlled diversion procedure is performed after reception of the TRA. Check that the traffic to D is diverted to the link 2-1 in accordance with the load sharing rules in A. Check that the traffic to E is not diverted.
  4. 4. Stop traffic and check that there were no lost messages, no duplication and no missequencing.
  5. 5. Repeat the test (in VAT) without sending of TRA and check that the duration of timer T21 is inside the specified range.
| | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------|----------|--|--| +| TEST NUMBER: 10.1.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Recovery of a linkset (SP A does not have an STP function) – Not resulting in the signalling point restart procedure | | | | | | +| PURPOSE: To check the actions of the system in case of restart of a linkset | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 2 and 6 are unavailable | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 3-1, 2 TRAFFIC | —————→ | 7-1 —————→ | SP E | | | +| | | 8-1 —————→ | SP D | | | +| | 4-1 ←————— | | 5-1 SP D | | | +| | └————→ 3-1, 2 | | | | | +| | ←—————┘ | | | | | +| | ←————— 3-1, 2 | ←————— | 7-1 SP E | | | +| 2-1 :Activate | | | | | | +| CHANGEBACKS ARE PERFORMED IN A AND B (Note) | | | | | | +| 2-1 TRAFFIC | —————→ 4-1 | —————→ 7-1 | SP E | | | +| 2-1 TRAFFIC | —————→ 5-1 | —————→ | SP D | | | +| 3-1, 2 TRAFFIC | —————→ | 7-1 —————→ | SP E | | | +| | | 8-1 —————→ | SP D | | | +| | ←————— 2-1 | | 5-1 SP D | | | +| | ←————— 3-1, 2 | ←————— | 7-1 SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – After activation of link 2-1, changebacks are performed in A and B but they are not explicitly described in this point restart test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to E and D. | | | | | +| 2. | Activate link 2-1. Check that the point restart procedure is not applied and that changebacks are performed. | | | | | +| 3. | Check that the traffic from A is diverted to the link 2-1 in accordance with the load sharing rules in A. | | | | | +| 4. | Check that the signalling route set test procedure is not applied after the activation of the link 2-1. | | | | | +| 5. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------------|----------|--|--| +| TEST NUMBER: 10.2.1 | | PAGE: 1 of 2 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Recovery of a linkset (SP A has STP function) – With use of point restart procedure | | | | | | +| PURPOSE: To check that restart procedure is performed correctly when the recovery of a linkset restores connectivity between two adjacent SPs | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 3, 4 and 6 are unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP ? | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC | —————→ | 7-1 —————→ | SP E | | | +| | | 8-1 —————→ | SP D | | | +| | ←————— | 2-1 ←————— | 7-1 SP E | | | +| | | | 8-1 SP D | | | +| 1-1 :Activate | | | | | | +| 1-1 Activation (link in service at level 2) | | | | | | +| | T21 | | | | | +| 1-1 TFP (PC = F) —————→ | | | | | | +| 1-1 TRA —————→ | | | | | | +| | ←————— 1-1 TFP (PC = C) | | | | | +| | ←————— 1-1 TFP (PC = E) | | SP D | | | +| | ←————— 1-1 TRA | | | | | +| | 5-1 TFA (PC = A) —————→ | | | | | +| 2-1 TFA (PC = B) —————→ | | | | | | +| 2-1 TFA (PC = D) —————→ | | | | | | +| 1-1 TFP (PC = D) —————→ | | | | | | +| TIME CONTROLLED DIVERSION IS APPLIED | | | | | | +| 1-1 TRAFFIC —————→ | 5-1 —————→ | | SP D | | | +| | ←————— 1-1 | | 5-1 SP D | | | +| | | 2-1 ←————— | 8-1 SP D | | | +| 2-1 TRAFFIC —————→ | | 7-1 —————→ | SP E | | | +| | ←————— | 2-1 ←————— | 7-1 SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E. | | | | | +| 2. | Activate link 1-1. Check that TFPs are sent from B to A for E and C, and that a TFP is sent from A to B for F. | | | | | +| 3. | Check that timer T21 in SP A and timer T21 in SP B stop at about the same time. Check that a TFA is sent from A to C for B. | | | | | +| 4. | Check that the controlled time diversion is applied in A. Check that the traffic to D is diverted on link 1-1. | | | | | +| 5. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | +| 6. | Repeat the test (in VAT) without sending TRA from B to A and check that the duration of timer T21 is inside the specified range. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|--| +| TEST NUMBER: 10.2.1 (concluded) | | PAGE: 2 of 2 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Recovery of a linkset (SP A has STP function) – With use of point restart procedure | | | | | | +| PURPOSE: See page 1 of 2 | | | | | | +| PRE-TEST CONDITIONS: Linksets 3, 4 and 6 are unavailable (end of page 1) | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP ? | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC | → 5-1 | → | SP D | | | +| | ← 1-1 | ← | SP D | | | +| | | ← 2-1 | ← 8-1 SP D | | | +| 2-1 TRAFFIC | → | → 7-1 | SP E | | | +| | | ← 2-1 | ← 7-1 SP E | | | +| 3-1 :Activate | | | | | | +| Activation (link service at level 2) | | | | | | +| 3-1 | | | T21 SP F | | | +| | ← | → 3-1 | | | | +| TRA | | | TRA SP F | | | +| 2-1 TFA (PC = F) | → | | | | | +| 1-1 TFA (PC = F) | → | | | | | +| 1-1 TRAFFIC
(from A and F) | → 5-1 | → | SP D | | | +| | ← 1-1 | ← | SP D | | | +| 2-1 TRAFFIC
(from A and F) | → | → 7-1 | SP E | | | +| | | ← 2-1 | ← 7-1 SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic. | | | | | +| 2. | Activate link 3-1. | | | | | +| 3. | Check that timer T21 in SP A and timer T21 in SP F stop at about the same time. Check that a TFA is sent from A to C for F and from A to B for F. | | | | | +| 4. | Stop traffic and check that there were no lost messages, duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------------------|--------------------------------------|--|--| +| TEST NUMBER: 10.2.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Recovery of a linkset (SP A has STP function) – Not resulting in the signalling point restart procedure | | | | | | +| PURPOSE: To check the actions of the system in case of restart of a linkset | | | | | | +| PRE-TEST CONDITIONS: Linkset 1 unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| :Start traffic | | | | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 8-1 —————→
7-1 —————→
2-1 ←————
←———— | SP D
SP E
7-1 SP E
8-1 SP D | | | +| 1-1 :Activate | | (Note 1) | | | | +| CHANGEBACKS ARE PERFORMED IN A AND B (Note 2) | | | | | | +| 1-1 TRAFFIC
(from A and F,
from 2-1) | —————→ 5-1 —————→
6-1 ←———— | | SP D
SP E | | | +| 2-1 TRAFFIC | —————→ | 7-1 —————→
2-1 ←————
←———— | SP E
7-1 SP E
8-1 SP D | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE 1 – Depending on the routing rules in D and E, the traffic to A and F may be carried either on linksets 5 or 8, or on linksets 6 or 7. | | | | | | +| NOTE 2 – Changebacks are performed but they are not explicitly described in this point restart test. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to D and E. | | | | | +| 2. | Activate link 1-1. Check that point restart procedure is not applied in this case and that changebacks are performed. | | | | | +| 3. | Check that the traffic to D and E is diverted on link 1-1 in accordance with the load sharing rules in A. | | | | | +| 4. | Check that the signalling route set test procedure is not used. | | | | | +| 5. | Stop traffic and check there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|----------|--|--| +| TEST NUMBER: 10.3 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: An adjacent SP becomes accessible via another SP (SP A does not have an STP function) | | | | | | +| PURPOSE: To check the actions of the system when an adjacent SP becomes accessible via another SP | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 3, 4, 5 and 6 are unavailable | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP • | | | +| Link | Link | Link | Link | | | +| | 4-1 :Activate | | | | | +| | ←———— | 4-1 TFP (A) | | | | +| TFPs
(D and E) | 4-1 —————→ | | | | | +| | T21 | T21 | | | | +| | ←———— | 4-1 TRA | | | | +| TRA | 4-1 —————→ | | | | | +| ←———— | 2-X TFAx | 7-1 TFAx (A, B) —————→ | SP E | | | +| | (PCs = C, D and E) | 8-1 TFAx (A, B) —————→ | SP D | | | +| | (Broadcasting mode) | | | | | +| 2-1, 2 TRAFFIC —————→ | 4-1 —————→ | 7-1 —————→ | SP E | | | +| ←———— | 2-1, 2 ←———— | 4-1 ←———— | 7-1 SP E | | | +| 2-1, 2 TRAFFIC —————→ | 4-1 —————→ | 8-1 —————→ | SP D | | | +| ←———— | 2-1, 2 ←———— | 4-1 ←———— | 8-1 SP D | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Activate link 4-1. | | | | | +| 2. | Check that on the reception of TFAx the traffic is immediately restarted in A to E and to D. | | | | | +| 3. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|----------|--|--| +| TEST NUMBER: 10.4 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: An adjacent SP becomes accessible via another SP (SP A has STP function) | | | | | | +| PURPOSE: To check the actions of the system when an adjacent SP becomes accessible via another SP on reception of a TFA | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 3 and 4 are unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP D | | | +| Link | Link | Link | Link | | | +| 2-1 TRAFFIC | —————→ | 7-1 —————→ | SP E | | | +| | | 8-1 —————→ | SP D | | | +| | ←————— | 2-1 ←————— | 7-1 SP E | | | +| | | ←————— | 8-1 SP D | | | +| | | 4-1 Activate | | | | +| | | 4-1 Activation (link in service at level 2) | | | | +| | T21 | T21 | | | | +| | ←————— | 4-1 TFP (PC = F) | | | | +| | ←————— | 4-1 TRA | | | | +| TFP (PC = A) | 4-1 —————→ | | | | | +| TFP (PC = F) | 4-1 —————→ | | | | | +| TRA | 4-1 —————→ | | | | | +| TFA (PC = F) | 4-1 —————→ | | | | | +| ←————— | | 2-1 | | | | +| TFA (PC = C) | 4-1 —————→ | | | | | +| ←————— | | 2-1 | | | | +| TFA (PC = C) | 5-1 —————→ | | SP D | | | +| TFA (PC = C) | 6-1 —————→ | | SP E | | | +| TFA (PC = A) | 5-1 —————→ | | SP D | | | +| TFA (PC = A) | 6-1 —————→ | | SP E | | | +| | | 7-1 TFA (PC = B) —————→ | SP E | | | +| | | 8-1 TFA (PC = B) —————→ | SP D | | | +| | ←————— | 2-1 TFA (PC = B) | | | | +| 2-1 TFP (PC = F) | —————→ | | | | | +| | ←————— | 4-1 | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – Messages between B and C are only present for understanding the global sequence of message.
Only messages received and sent by/from A are subject to this test | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic. | | | | | +| 2. | Activate link 4-1. | | | | | +| 3. | Check that, when the TFA is received for B, SP A is aware of that B is an adjacent point which restarts, and consequently, A sends a TFP concerning F on link 2-1 to B. | | | | | +| 4. | Stop traffic and check that there were no lost messages, no duplication and no missequencing. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------|----------|--|--|--|--|--| +| TEST NUMBER: 10.5 | | PAGE: 1 of 2 | | | | | | | +| REFERENCE: clause 9/Q.704 | | | | | | | | | +| TITLE: Signalling point restart | | | | | | | | | +| SUBTITLE: Restart of an SP having no STP function | | | | | | | | | +| PURPOSE: To check the restart procedure in an SP having no STP function | | | | | | | | | +| PRE-TEST CONDITIONS: SP A unavailable | | | | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT, CPT | TYPE OF SP: SP | | | | | | | +| MESSAGE SEQUENCE: | | | | | | | | | +| SP A | SP B | SP C | SP ? | | | | | | +| Link | Link | Link | Link | | | | | | +| :Activate | | | | | | | | | +| X-X | Activation (first link in service at level 2) | | | | | | | | +| | T20 | T21 | T21 SP D | | | | | | +| | ←————— TRA 2-1 | | | | | | | | +| | ←————— TRA 3-1 | | | | | | | | +| | ←————— TRA 1-1 | | | | | | | | +| when all (or sufficient) links are available | | | | | | | | | +| | TRA | | | | | | | | +| | ————→ TFA (PC = A) are broadcast | | | | | | | | +| 3-1 | TRA | | | | | | | | +| | ————→ TFA (PC = A) are broadcast | | | | | | | | +| 1-1 | TRA | | | | | | | | +| | ————→ | | | | | | | | +| 1-1, 2 | TRAFFIC | ————→ SP D | | | | | | | +| | ←————— 1-1, 2 SP D | | | | | | | | +| 2-1, 2 | TRAFFIC | ————→ 5-1 SP D | | | | | | | +| | ————→ 6-1 SP E | | | | | | | | +| 3-1, 2 | TRAFFIC | ————→ 8-1 SP E | | | | | | | +| | ————→ 7-1 SP E | | | | | | | | +| | ←————— 3-1, 2 SP E | | | | | | | | +| :Wait | | | | | | | | | +| :Stop traffic | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Activate SP A | | | | | | | | +| 2. | Check that when the first link is in service at level 2, the timer T20 is started. | | | | | | | | +| 3. | Check that when all (or sufficient) links are activated, and all TRAs are received from B, C and D timer T20 is stopped. | | | | | | | | +| 4. | Check that SP A broadcasts TRAs to B, C and D. | | | | | | | | +| 5. | Check that the traffic is carried as described above. | | | | | | | | +| 6. | Stop traffic. | | | | | | | | +| 7. | In VAT, repeat the test without sending TRA from B to A, and check that the duration of T20 is inside the specified range. | | | | | | | | +| 8. | In VAT, repeat the test without activating the link 1-1, and check that the duration of T20 is inside the specified range. | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|----------------|-------------|--|--| +| TEST NUMBER: 10.5 (concluded) | | PAGE: 2 of 2 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Restart of an SP having no STP function | | | | | | +| PURPOSE: To check the restart procedure in an SP having no STP function | | | | | | +| PRE-TEST CONDITIONS: SP A, linksets 6 and 7 unavailable | | | | | | +| CONFIGURATION: B | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP ? | | | +| Link | Link | Link | Link | | | +| :Activate | | | | | | +| X-X Activation (first link in service at level 2) | | | | | | +| T20 | T21 | T21 | T21 SP D | | | +| ← TFP (PC = E) 2-1 | | | | | | +| ← TRA 2-1 | | | | | | +| ← TFP (PC = E) 3-1 | | | | | | +| ← TRA 3-1 | | | | | | +| ← TRA | | | 1-1 | | | +| when all (or sufficient) links are available | | | | | | +| 2-1 TRA → | | | | | | +| TFAs (PC = A) are broadcast | | | | | | +| 3-1 TRA → | | | | | | +| TFAs (PC = A) are broadcast | | | | | | +| 1-1 TRA → | | | | | | +| 1-1 TRAFFIC → | | | SP D | | | +| | | | 1-1, 2 SP D | | | +| 2-1, 2 TRAFFIC → | 5-1 → | | SP D | | | +| | 6-1 → | | SP E | | | +| 3-1, 2 TRAFFIC → | | 8-1 → | SP D | | | +| | | 7-1 → | SP E | | | +| | | 3-1, 2 ← | 7-1 SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Activate SP A. | | | | | +| 2. | Check that when the first link is in service at level 2, the timer T20 is started. | | | | | +| 3. | Check that when all (or sufficient) links are activated, and all TRAs are received from B, C and D timer T20 is stopped. | | | | | +| 4. | Check that SP A broadcasts TRAs to B, C and D. | | | | | +| 5. | Check that the traffic is carried as described above. | | | | | +| 6. | Stop traffic. | | | | | +| 7. | Repeat the test without sending TRA from B to A, and check that the duration of T20 is inside the specified range. | | | | | +| 8. | Repeat the test without activating the link 1-1, and check that the duration of T20 is inside the specified range. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|--|--| +| TEST NUMBER: 10.6 | | PAGE: 1 of 2 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Restart of an SP having the STP function | | | | | | +| PURPOSE: To check the restart procedure in an SP having STP function | | | | | | +| PRE-TEST CONDITIONS: SP A unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A
Link | SP B
Link | SP C
Link | SP ?
Link | | | +| :Activate | | | | | | +| X-X | Activation (first link in service at level 2) | | | | | +| T18 | T20 | T21 | T21 SP F | | | +| | ← TFP (PC = F) 1-1 | | | | | +| | ← TRA 1-1 | | | | | +| | ← TFP (PC = F) 2-1 | | | | | +| | ← TRA 2-1 | | | | | +| | ← TRA 3-1 | | | | | +| when all (or sufficient) links are available and when all (or sufficient) TRAs have been received | | | | | | +| 1-1 | TFP (PC = D) → | | | | | +| 1-1 | TFP (PC = E) → | | | | | +| 2-1 | TFP (PC = E) → | | | | | +| 1-1 | TRA → | | | | | +| | ← TFP (PC = F) 1-1 | | | | | +| | TFAs (A&F) are broadcast | | | | | +| 2-1 | TRA → | | | | | +| | ← TFP (PC = F) 2-1 | | | | | +| | TFAs (A) are broadcast | | | | | +| 3-1 | TRA → | | | | | +| 1-1 | TRAFFIC → 5-1 → | | SP D | | | +| (from A and F) | Via B or C to A and F ← | | 5-1 or 8-1 SP D | | | +| | 6-1 → | | SP D | | | +| 2-1 | TRAFFIC → 7-1 → | | SP E | | | +| (from A and F) | Via B or C to A and F ← | | 6-1 or 7-1 SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – Preventive TFPs are possibly sent after the expiry of T20. Preventive TFPs for the highest priority routes might not be sent. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Activate SP A. | | | | | +| 2. | Check that when the first link is in service at level 2, the timer T20 is started. | | | | | +| 3. | Check that when all (or sufficient) links are activated, and all TRAs are received from B, C and D timer T18 is stopped. | | | | | +| 4. | Check that SP A broadcasts TRAs to B, C and F. | | | | | +| 5. | Check that the traffic is carried as described above. | | | | | +| 6. | Stop traffic. | | | | | +| 7. | Repeat the test (in VAT) but send the traffic from F to D and E via A immediately after alignment of link 3-1 and check that this traffic is discarded until the end of T20. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------|----------|--|--| +| TEST NUMBER: 10.6 (concluded) | | PAGE: 2 of 2 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Restart of an SP having the STP function | | | | | | +| PURPOSE: To check the restart procedure in an SP having STP function | | | | | | +| PRE-TEST CONDITIONS: SP A unavailable and linkset 2 and 4 definitively unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP F | SP ? | | | +| Link | Link | Link | Link | | | +| | :Activate | | | | | +| X-X | Activation (first link in service at level 2) | | | | | +| T18 | T20 | | T21 | | | +| | ← TFP (PC = F) 1-1 | | | | | +| | ← TFP (PC = C) 1-1 | | | | | +| | ← TRA 1-1 | | | | | +| | ← TRA | TRA | 3-1 | | | +| at the end of timer T18 | | | | | | +| 1-1 | TFP (PC = C) → | | | | | +| 1-1 | TFP (PC = D) → | | | | | +| 1-1 | TFP (PC = E) → | | | | | +| 3-1 | TFP (PC = C) → | | | | | +| 1-1 | TRA → | | | | | +| | ← TFP (PC = F) 1-1 | | | | | +| | TFAs (A & F) are broadcast | | | | | +| 3-1 | TRA → | | | | | +| 1-1 | TRAFFIC → | 5-1 → | SP D | | | +| (from A and F) | | 6-1 → | SP E | | | +| | | to A and F → | 5-1 SP D | | | +| | | to A and F → | 6-1 SP D | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| NOTE – Preventive TFPs may be sent after the expiry of T20. Preventive TFPs for the highest priority routes might not be sent. | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Activate SP A beginning by the activation of 3-1, activate link 1-1. | | | | | +| 2. | Stop traffic. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|----------------------------------------------------------------------------|---------------------------------------------------------------------------|----------------|---------|--|--| +| TEST NUMBER: 10.7.1 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Reception of an unexpected TRA – In an SP having no STP function | | | | | | +| PURPOSE: To check the system in case of reception of an unexpected TRA | | | | | | +| PRE-TEST CONDITIONS: Linkset with one available link | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 | TRAFFIC | → | | | | +| | | ← | | | | +| | | 1-1 | TRAFFIC | | | +| | | 1-1 | TRA | | | +| 1-1 | T19 | TRA → | | | | +| | | ← | | | | +| | | 1-1 | TRA | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on link 1-1. | | | | | +| 2. | Send a TRA from B to A and check that the timer T19 is started. | | | | | +| 3. | During T19 send a TRA from B to A and check that this message is ignored. | | | | | +| 4. | Stop traffic and check that it has not been disturbed. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------|--|--| +| TEST NUMBER: 10.7.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 9/Q.704 | | | | | | +| TITLE: Signalling point restart | | | | | | +| SUBTITLE: Reception of an unexpected TRA – In an SP having the STP function | | | | | | +| PURPOSE: See test 10.7.1 | | | | | | +| PRE-TEST CONDITIONS: Linksets 1, 4 and 8 are unavailable | | | | | | +| CONFIGURATION: D | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | SP B | SP C | SP ? | | | +| Link | Link | Link | Link | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 7-1 —————→ | SP E | | | +| | ←———— | 2-1 ←———— | 7-1 SP E | | | +| | ←———— | 2-1 TRA | | | | +| 2-1 T19 | TFP (PC = B) —————→ | | | | | +| | TFP (PC = D) —————→ | | | | | +| | TRA —————→ | | | | | +| | ←———— | 2-1 TRA | | | | +| 2-1 TRAFFIC
(from A and F) | —————→ | 7-1 —————→ | SP E | | | +| | ←———— | 2-1 ←———— | 7-1 SP E | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to E. | | | | | +| 2. | Send a TRA from C to A and check that the timer T19 is started, and that TFPs concerning B and D are received, then, check that a TRA is received from A. | | | | | +| 3. | During T19 send a TRA from C to A and check that this message is ignored. | | | | | +| 4. | Stop traffic and check that it has not been disturbed. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-----------------|------|------|------|------|------|------|----------------|--|--|---------------|-------|--|---------------|-------|--|--|-------|---------------|--|-------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 11 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.706 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Traffic test | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the behaviour of an STP in various traffic situations | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: All links available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: C | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP B SP A SP C
Link Link Link
:Start traffic
1-1 TRAFFIC → 2-1 →
1-2 TRAFFIC → 2-1 →
← 1-1 ← 2-1 TRAFFIC
← 1-2
:Wait
:Stop traffic
| | | SP B | SP A | SP C | Link | Link | Link | :Start traffic | | | 1-1 TRAFFIC → | 2-1 → | | 1-2 TRAFFIC → | 2-1 → | | | ← 1-1 | ← 2-1 TRAFFIC | | ← 1-2 | | :Wait | | | :Stop traffic | | | +| SP B | SP A | SP C | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | Link | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-1 TRAFFIC → | 2-1 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1-2 TRAFFIC → | 2-1 → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 1-1 | ← 2-1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 1-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic between B and C in both directions via A using the traffic models presented in ITU-T Rec. Q.706. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the time to cross the STP is better than 20 milliseconds. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat test but with a traffic model including 5% of messages with an SIF = 272 octets. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|----------|--|----------|----------------|--|--|-------------|---|--|--|---|-------------|---------------|--|--|----------|---|--|--|---|----------|--|---|----------|----------|---|--|------------|--|--|----------------|---|--|---------|---|----------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 12.1 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.707 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling link test | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: After activation of a link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the signalling link test procedure after activation of a signalling link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1–2 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP A SP B

Link
Link
:Start traffic
1–2 TRAFFIC →
← 1–2 TRAFFIC
1–1 :Activate
1–1 SLTM →
← 1–1 SLTA
← 1–1 SLTm
1–1 SLTA →
CHANGEBACK
1–1, 2 TRAFFIC →
TRAFFIC ← 1–1, 2 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–2 TRAFFIC | → | | | ← | 1–2 TRAFFIC | 1–1 :Activate | | | 1–1 SLTM | → | | | ← | 1–1 SLTA | | ← | 1–1 SLTm | 1–1 SLTA | → | | CHANGEBACK | | | 1–1, 2 TRAFFIC | → | | TRAFFIC | ← | 1–1, 2 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 :Activate | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 SLTM | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–1 SLTA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 1–1 SLTm | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 SLTA | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHANGEBACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TRAFFIC | ← | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B (and C in VAT). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Activate link 1–1 and check that an SLTM is received from A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Send an SLTM to A and check that an SLTA is received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that the link 1–1 becomes available and that changeback is performed correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | In VAT, repeat the test with link 1–1 unavailable and inhibited (in this case changeback is not performed). Check that the link 1–1 becomes available and stays inhibited. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------|--|--| +| TEST NUMBER: 12.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: Q.707 | | | | | | +| TITLE: Signalling link test | | | | | | +| SUBTITLE: No acknowledgement to first SLTM | | | | | | +| PURPOSE: To check that a second SLTM is sent if the first is not acknowledged | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1-2 available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-2 TRAFFIC | | | +| 1-1 | :Activate | | | | | +| 1-1 | SLTM | —————→ | | | | +| | , , , , T1 | | | | | +| | — | | | | | +| 1-1 | SLTM | —————→ | | | | +| | | ←————— | 1-1 SLTA | | | +| | | ←————— | 1-1 SLTM | | | +| 1-1 | SLTA | —————→ | | | | +| CHANGEBACK | | | | | | +| 1-1, 2 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-1, 2 TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C. | | | | | +| 2. | Activate link 1-1 and check that an SLTM is received and not acknowledged. | | | | | +| 3. | Check that when the time T1 expires a new SLTM is sent. Check that the duration of this time is inside of the specified range. | | | | | +| 4. | Check that the link 1-1 becomes available and that the changeback is performed correctly. | | | | | +| 5. | Stop traffic. | | | | | +| 6. | Repeat the test with link 1-1 unavailable and inhibited (in this case changeback is not performed). Check that the link becomes available and stays inhibited. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------|-------------|--|--| +| TEST NUMBER: 12.3 | | PAGE: 1 of 1 | | | | +| REFERENCE: Q.707 | | | | | | +| TITLE: Signalling link test | | | | | | +| SUBTITLE: No acknowledgement to second SLTM | | | | | | +| PURPOSE: To check that the link stays unavailable when the second SLTM is not acknowledged | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1-2 available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-2 TRAFFIC | | | +| 1-1 | :Activate | | | | | +| 1-1 | SLTM | —————→ | | | | +| | , , , , , T1 | | | | | +| | — | | | | | +| 1-1 | SLTM | —————→ | | | | +| | , , , , , T1 | | | | | +| | — | | | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-2 TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C. | | | | | +| 2. | Activate link 1-1 and check that two SLTMs are received from A. | | | | | +| 3. | Check that after the second expiration of T1, link 1-1 stays unavailable and that the management system is informed. | | | | | +| 4. | Repeat the test with link 1-1 unavailable and inhibited. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------------------|--|--| +| TEST NUMBER: 12.4 | | PAGE: 1 of 1 | | | | +| REFERENCE: Q.707 | | | | | | +| TITLE: Signalling link test | | | | | | +| SUBTITLE: Unreasonable field in an SLTA | | | | | | +| PURPOSE: To check the actions of the system on reception of an SLTA with an unreasonable field | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1-2 available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2 | TRAFFIC | → | | | | +| | | ← | | | | +| 1-1 | :Activate | | | | | +| 1-1 | SLTM | → | | | | +| | | ← | | | | +| | | 1-1 | SLTA (erroneous test pattern) | | | +| 1-1 | SLTM | → | | | | +| | | ← | | | | +| | | 1-1 | SLTA | | | +| CHANGEBACK | | | | | | +| 1-1, 2 | TRAFFIC | → | | | | +| | | ← | | | | +| | | 1-1, 2 | TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C. | | | | | +| 2. | Activate link 1-1 and check that an SLTM is received and acknowledged with an SLTA containing an erroneous test pattern. | | | | | +| 3. | Check that a second SLTM is sent from A and correctly acknowledged. | | | | | +| 4. | Check that link 1-1 becomes available and that changeback is performed correctly. | | | | | +| 5. | Wait and stop traffic. | | | | | +| 6. | Repeat the test with a first SLTA containing an erroneous SLC then OPC. | | | | | +| 7. | Repeat the test with the first and second erroneous SLTA and check that link 1-1 stays unavailable and that management system is informed. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------|----------------|--|--| +| TEST NUMBER: 12.5 | | PAGE: 1 of 1 | | | | +| REFERENCE: Q.707 | | | | | | +| TITLE: Signalling link test | | | | | | +| SUBTITLE: Reception of an SLTM in an attempt state | | | | | | +| PURPOSE: To check the actions of the system when an SLTM is received in an attempt state | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1-2 available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-2 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-2 TRAFFIC | | | +| 1-1 | :Activate | | | | | +| 1-1 | SLTM | —————→ | | | | +| | T1 | ←————— | 1-1 SLTM | | | +| 1-1 | SLTA | —————→ | | | | +| 1-1 | SLTM | —————→ | | | | +| | T1 | ←————— | 1-1 SLTM | | | +| 1-1 | SLTA | —————→ | | | | +| | | ←————— | 1-1 SLTA | | | +| CHANGEBACK | | | | | | +| 1-1, 2 | TRAFFIC | —————→ | | | | +| | | ←————— | 1-1, 2 TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C. | | | | | +| 2. | Activate link 1-1 and check that SLTM is received. Send an SLTM and check that an SLTA is received. | | | | | +| 3. | On reception of the second SLTM, send an SLTM and check that an SLTA is received. Send an SLTA to A. | | | | | +| 4. | Check that changeback is performed correctly, and stop traffic. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|-----------------|------|--|------|----------|--|----------|----------------|--|--|-------------|--------|--|--|-------|-------------|--|-------|----------|--|-------|----------|----------|--------|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 12.6 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.707 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Signalling link test | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Additional SLTA and SLTM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of additional SLTA and SLTM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Signalling link 1–2 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT, CPT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–2 TRAFFIC —————→
←———— 1–2 TRAFFIC
←———— 1–2 SLTA
←———— 1–2 SLTM
1–2 SLTA —————→
:Wait
:Stop traffic
















| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–2 TRAFFIC | —————→ | | | ←———— | 1–2 TRAFFIC | | ←———— | 1–2 SLTA | | ←———— | 1–2 SLTM | 1–2 SLTA | —————→ | | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 SLTA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–2 SLTM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–2 SLTA | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B (and C in VAT). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the reception of an SLTA is ignored. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Send an SLTM to A and check that an SLTA is received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 13.1 | | PAGE: 1 of 1 | +| REFERENCE: Table 1/Q.704 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid H0-H1 in a signalling network management message | | | +| PURPOSE: To check the actions of the system when a signalling network management message is received with a non-existing H0-H1 | | | +| PRE-TEST CONDITIONS: All links available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +|

MESSAGE SEQUENCE:

 sequenceDiagram     participant A as SP A     participant B as SP B     Note over A,B: Link     Note over A,B: :Start traffic     A->>B: ALL TRAFFIC     B->>A: ALL TRAFFIC     B->>A: 1-X SIGNALLING NETWORK MANAGEMENT MESSAGE (Invalid H0-H1)     A->>B: ALL TRAFFIC     B->>A: ALL TRAFFIC     Note over A,B: :Wait     Note over A,B: :Stop traffic
| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on all links. | | +| 2. | Send a signalling network management message with a non-existing H0-H1. | | +| 3. | Check that this message is discarded without impact on the traffic. | | +| 4. | Stop traffic. | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------|------------------------------------|--|--| +| TEST NUMBER: 13.2 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 15/Q.704 | | | | | | +| TITLE: Invalid messages | | | | | | +| SUBTITLE: Invalid changeover messages | | | | | | +| PURPOSE: To check the actions of the system on reception of changeover messages with an invalid SLC or OPC | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 | TRAFFIC | → | | | | +| | | ← | | | | +| 1-2 | TRAFFIC | → | | | | +| | | ← | | | | +| | | 1-1 | TRAFFIC | | | +| | | 1-2 | TRAFFIC | | | +| | | 1-2 | COO, SLC 1-X
(non-existing SLC) | | | +| | | 1-2 | COO, SLC 1-1
(non-existing OPC) | | | +| | | 1-2 | ECO, SLC 1-X
(non-existing SLC) | | | +| | | 1-2 | ECO, SLC 1-1
(non-existing OPC) | | | +| | | 1-2 | COA, SLC 1-X
(non-existing SLC) | | | +| | | 1-2 | COA, SLC 1-1
(non-existing OPC) | | | +| | | 1-2 | ECA, SLC 1-X
(non-existing SLC) | | | +| | | 1-2 | ECA, SLC 1-1
(non-existing OPC) | | | +| 1-1, 2 | TRAFFIC | → | | | | +| | | ← | | | | +| | | 1-1, 2 | TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Send the invalid messages as described above and check that they are ignored. | | | | | +| 3. | Stop traffic and check that it was not disturbed. | | | | | + +###### **MTP Level 3** + +| | | | | | | +|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------|------------------------------------|--|--| +| TEST NUMBER: 13.3 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 15/Q.704 | | | | | | +| TITLE: Invalid messages | | | | | | +| SUBTITLE: Invalid changeback messages | | | | | | +| PURPOSE: To check the actions of the system on reception of changeback messages with an invalid SLC or OPC | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 | TRAFFIC | → | | | | +| | | ← | | | | +| 1-2 | TRAFFIC | → | | | | +| | | ← | | | | +| | | 1-1 | TRAFFIC | | | +| | | 1-2 | TRAFFIC | | | +| | | 1-2 | CBD, SLC 1-X
(non-existing SLC) | | | +| | | 1-2 | CBD, SLC 1-1
(non-existing OPC) | | | +| | | 1-2 | CBA, SLC 1-X
(non-existing SLC) | | | +| | | 1-2 | CBA, SLC 1-1
(non-existing OPC) | | | +| 1-1, 2 | TRAFFIC | → | | | | +| | | ← | | | | +| | | 1-1, 2 | TRAFFIC | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C on all links. | | | | | +| 2. | Send the invalid messages described above and check that they are ignored. | | | | | +| 3. | Stop traffic and check that it was not disturbed. | | | | | + +###### **MTP Level 3** + +| | | | +|----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| TEST NUMBER: 13.4 | | PAGE: 1 of 1 | +| REFERENCE: clause 15/Q.704 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid changeback code | | | +| PURPOSE: To check the actions of the system on reception of an invalid changeback code in a changeback message | | | +| PRE-TEST CONDITIONS: Linkset with one link available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE: | | | +| SP A | | SP B | +| Link | | Link | +| :Start traffic | | | +| 1-2 TRAFFIC | —————→ | | +| | ←———— | 1-2 TRAFFIC | +| 1-1 :Activate (depending on the deactivation mean previously used) | | | +| 1-2 CBD, SLC 1-1 | —————→ | | +| | ←———— | 1-2 CBA, SLC 1-1
(invalid changeback
code ≠ CBD) | +| 1-2 CBD, SLC 1-1 | —————→ | | +| | ←———— | | +| 1-1 TRAFFIC
(from 1-2) | —————→ | | +| | ←———— | 1-1 TRAFFIC
(from 1-2, Note) | +| 1-2 TRAFFIC | —————→ | | +| | ←———— | 1-2 TRAFFIC | +| :Wait | | | +| :Stop traffic | | | +| NOTE – B may perform a changeback or not. | | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C on link 1-2. | | +| 2. | Activate link 1-1, check that a CBD is received and acknowledged by a CBA with an invalid changeback code. | | +| 3. | Check that a new CBD is received after T4 expires and acknowledged by a correct CBA. Check that changeback is performed. | | +| 4. | Stop traffic and check that the invalid message has been discarded without impact on the traffic. | | + +**MTP Level 3** + +| | | | +|-------------------------------------------------------------------------------------------|-------------------|-----------------| +| TEST NUMBER: 13.5 | | PAGE: 1 of 3 | +| REFERENCE: clause 15/Q.704 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid inhibition messages | | | +| PURPOSE: To check the actions of the system on reception of an invalid inhibition message | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | + +MESSAGE SEQUENCE: + +SP A +SP B + +Link +Link + +:Start traffic + +``` + + 1–1 TRAFFIC ——————————————————————————> + <—————————————————————————— 1–1 TRAFFIC + + 1–2 TRAFFIC ——————————————————————————> + <—————————————————————————— 1–2 TRAFFIC + <—————————————————————————— 1–2 LIN, SLC 1–X + (non-existing SLC) + <—————————————————————————— 1–2 LIN, SLC 1–2 + (non-existing OPC) + <—————————————————————————— 1–2 LIA, SLC 1–X + (non-existing SLC) + <—————————————————————————— 1–2 LIA, SLC 1–1 + (non-existing OPC) + <—————————————————————————— 1–2 LID, SLC 1–X + (non-existing SLC) + <—————————————————————————— 1–2 LID, SLC 1–1 + (non-existing OPC) + +``` + +| TEST DESCRIPTION | | +|------------------|-----------------------------------------------------------------------------| +| 1. | Start traffic to B and C. | +| 2. | Send the invalid messages described above and check that these are ignored. | +| 3. | Stop traffic and check that it was not disturbed. | + +134 **ITU-T Rec. Q.782 (04/2002)** + +###### **MTP Level 3** + +| | | | +|-------------------------------------------------------|-------------------|----------------------------------------| +| TEST NUMBER: 13.5 (continued) | | PAGE: 2 of 3 | +| REFERENCE: clause 15/Q.704 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid inhibition messages | | | +| PURPOSE: As page 1 | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE: | | | +| SP A | | SP B | +| Link | | Link | +| | ←————— | 1-2 LUN, SLC 1-X
(non-existing SLC) | +| | ←————— | 1-2 LUN, SLC 1-1
(non-existing OPC) | +| | ←————— | 1-2 LUA, SLC 1-X
(non-existing SLC) | +| | ←————— | 1-2 LUA, SLC 1-1
(non-existing OPC) | +| | ←————— | 1-2 LFU, SLC 1-X
(non-existing SLC) | +| | ←————— | 1-2 LFU, SLC 1-1
(non-existing OPC) | +| TEST DESCRIPTION | | | +| 1. | See page 1. | | + +###### **MTP Level 3** + +| | | | +|-------------------------------------------------------|-------------------|----------------------------------------| +| TEST NUMBER: 13.5 (concluded) | | PAGE: 3 of 3 | +| REFERENCE: clause 15/Q.704 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid inhibition messages | | | +| PURPOSE: As page 1 | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE: | | | +| SP A | | SP B | +| Link | | Link | +| | ←———— | 1-2 LLT, SLC 1-X
(non-existing SLC) | +| | ←———— | 1-2 LLT, SLC 1-1
(non-existing OPC) | +| | ←———— | 1-2 LRT, SLC 1-X
(non-existing SLC) | +| | ←———— | 1-2 LRT, SLC 1-1
(non-existing OPC) | +| ALL TRAFFIC | ————→ | | +| | ←———— | ALL TRAFFIC | +| :Wait | | | +| :Stop traffic | | | +| TEST DESCRIPTION | | | +| 1. | See page 1. | | + +###### **MTP Level 3** + +| | | | | | | +|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------|--|--|--| +| TEST NUMBER: 13.6 | | PAGE: 1 of 1 | | | | +| REFERENCE: clause 15/Q.704 | | | | | | +| TITLE: Invalid messages | | | | | | +| SUBTITLE: Invalid transfer control messages | | | | | | +| PURPOSE: To check that there is no problem on reception of a TFC with spare field or SLC not coded 00 | | | | | | +| PRE-TEST CONDITIONS: Link 1-1 available | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | +| MESSAGE SEQUENCE: | | | | | | +| SP A | | SP B | | | | +| Link | | Link | | | | +| :Start traffic | | | | | | +| 1-1 TRAFFIC | —————→ | | | | | +| | ←———— | 1-1 TRAFFIC | | | | +| | ←———— | 1-1 TFC, PC = C
(spare field ≠ 0) | | | | +| | ←———— | 1-1 TFC, PC = C
(SLC ≠ 0000) | | | | +| | ←———— | 1-1 TFC, PC = X
(non-existing PC) | | | | +| 1-1 TRAFFIC | —————→ | | | | | +| | ←———— | 1-1 TRAFFIC | | | | +| :Wait | | | | | | +| :Stop traffic | | | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Start traffic to B and C. | | | | | +| 2. | Send a TFC with invalid spare field to A, then a TFC with an invalid SLC then a TFC with a non-existing PC. | | | | | +| 3. | Check that these messages are correctly received without disturbances due to these incorrect values. | | | | | +| 4. | Stop traffic. | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------|--|------|------|--|------|----------------|--|--|-------------|--------|--|--|--------|-------------|--|--------|--------------------------------------|--|--------|--------------------------------------|--|--------|---------------------------------------|--|--------|--------------------------------------|--|--|-----------------|--|--------|-----------------|--|--------|---------------------------------------|--|--------|--------------------------------------|-------------|--------|--|--|--------|-------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 13.7 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 15/Q.704 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Invalid messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Invalid signalling route management messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of invalid TFA or TFP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Links 1–1 and 2–1 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGES SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–1 TRAFFIC —————>
<————— 1–1 TRAFFIC
<————— 1–1 TFP, PC = X
(non-existing PC)
<————— 1–1 TFA, PC = X
(non-existing PC)
<————— 1–1 TFP, PC = C
(non-existing OPC)
<————— 1–1 TFP, PC = C
(spare bits # 00)
2–1 :Deactivate
<————— 1–1 TFP, PC = C
<————— 1–1 TFA, PC = C
(non-existing OPC)
<————— 1–1 TFA, PC = C
(spare bits # 00)
1–1 TRAFFIC —————>
<————— 1–1 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | Link | | Link | :Start traffic | | | 1–1 TRAFFIC | —————> | | | <————— | 1–1 TRAFFIC | | <————— | 1–1 TFP, PC = X
(non-existing PC) | | <————— | 1–1 TFA, PC = X
(non-existing PC) | | <————— | 1–1 TFP, PC = C
(non-existing OPC) | | <————— | 1–1 TFP, PC = C
(spare bits # 00) | | | 2–1 :Deactivate | | <————— | 1–1 TFP, PC = C | | <————— | 1–1 TFA, PC = C
(non-existing OPC) | | <————— | 1–1 TFA, PC = C
(spare bits # 00) | 1–1 TRAFFIC | —————> | | | <————— | 1–1 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFP, PC = X
(non-existing PC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFA, PC = X
(non-existing PC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFP, PC = C
(non-existing OPC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFP, PC = C
(spare bits # 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 2–1 :Deactivate | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFP, PC = C | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFA, PC = C
(non-existing OPC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TFA, PC = C
(spare bits # 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1 TRAFFIC | —————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————— | 1–1 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send TFPs and TFAs with invalid values to A (as described above). Check that these messages are discarded without impact on the traffic, (except for spare bit # 0). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Deactivate linkset 2 and check that C becomes inaccessible. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Send TFAs concerning C with invalid values to A (as described above) and check that these messages are discarded without impact on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check the indications are given by the system (except for spare bits # 0). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|------|--|------|--|--|--|------|--|------|----------------|--|--|-----------------|------------|--|--|------------|-----------------|--|------------|------------------------------------------|--|------------|-------------------------------------------|--|------------|------------------------------------------|-----------------|------------|--|--|------------|-----------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 13.8 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 15/Q.704 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Invalid messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Invalid signalling-route-set-test messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of invalid RST messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link 1–1 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: STP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGES SEQUENCE:

SP A SP B
Link Link
:Start traffic
1–1     TRAFFIC —————————→
←————————— 1–1     TRAFFIC
←————————— 1–1     RST, PC = X
(non-existing PC)
←————————— 1–1     RST, PC = C
(non-existing OPC)
←————————— 1–1     RST, PC = C
(spare bits # 00)
1–1     TRAFFIC —————————→
←————————— 1–1     TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B | | | | Link | | Link | :Start traffic | | | 1–1     TRAFFIC | —————————→ | | | ←————————— | 1–1     TRAFFIC | | ←————————— | 1–1     RST, PC = X
(non-existing PC) | | ←————————— | 1–1     RST, PC = C
(non-existing OPC) | | ←————————— | 1–1     RST, PC = C
(spare bits # 00) | 1–1     TRAFFIC | —————————→ | | | ←————————— | 1–1     TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1     TRAFFIC | —————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————————— | 1–1     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————————— | 1–1     RST, PC = X
(non-existing PC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————————— | 1–1     RST, PC = C
(non-existing OPC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————————— | 1–1     RST, PC = C
(spare bits # 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1     TRAFFIC | —————————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←————————— | 1–1     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send to A the invalid messages described above and check that these messages are discarded without impact on the traffic, (except for spare bits # 0). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------------|------|--|------|----------|--|----------|----------------|--|--|----------------|--------|--|--|-------|----------------|--|-------|-----------------------|----------------|--------|--|--|-------|----------------|-------|--|--|---------------|--|--| +| TEST NUMBER: 13.9 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: clause 15/Q.704 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Invalid messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Invalid traffic restart allowed message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of an invalid traffic restart allowed message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Linkset with two available links | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B

Link
Link
:Start traffic
1–1, 2 TRAFFIC —————→
←———— 1–1, 2 TRAFFIC
←———— 1–1 TRA (unknown OPC)
1–1, 2 TRAFFIC —————→
←———— 1–1, 2 TRAFFIC
:Wait
:Stop traffic
| | | SP A | | SP B |
Link | |
Link | :Start traffic | | | 1–1, 2 TRAFFIC | —————→ | | | ←———— | 1–1, 2 TRAFFIC | | ←———— | 1–1 TRA (unknown OPC) | 1–1, 2 TRAFFIC | —————→ | | | ←———— | 1–1, 2 TRAFFIC | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Link | |
Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1 TRA (unknown OPC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1, 2 TRAFFIC | —————→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←———— | 1–1, 2 TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send the invalid message described above and check that this message is ignored. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic and check that it was not disturbed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP Level 3** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 13.10 | | PAGE: 1 of 1 | +| REFERENCE: Q.707 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid H0-H1 in a signalling network testing and maintenance message | | | +| PURPOSE: To check the actions of the system on reception of this invalid message | | | +| PRE-TEST CONDITIONS: Link 1–1 available | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP A
Link Link
:Start traffic
1–1 TRAFFIC ————————————————————> <———————————————————— 1–1 TRAFFIC <———————————————————— 1–1 SIGNALLING NETWORK TESTING AND MAINTENANCE MESSAGE (Invalid H0-H1)
1–1 TRAFFIC ————————————————————> <———————————————————— 1–1 TRAFFIC
:Wait
:Stop traffic | | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C. | | +| 2. | Send a signalling network testing and maintenance message with a non-existing H0-H1. | | +| 3. | Check that this message is discarded without impact on the traffic. | | +| 4. | Stop traffic. | | + +###### **MTP Level 3** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------|--|------|--|------|--|--|--|------|--|------|----------------|--|--|-----------------|--------------|--|--|--------------|-----------------|--|--------------|----------------------------|--|--------------|----------------------------|-----------------|--------------|--|--|--------------|-----------------|--|--|--|-------|--|--|---------------|--|--| +| TEST NUMBER: 13.11 | | PAGE: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.707 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Invalid messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Invalid signalling link test messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the actions of the system on reception of an invalid signalling link test message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link 1–1 available | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MESSAGE SEQUENCE:
SP A SP B
Link Link
:Start traffic
1–1     TRAFFIC ———————————>
<——————————— 1–1     TRAFFIC
<——————————— 1–1     SLTM (invalid SLC)
<——————————— 1–1     SLTA (invalid SLC)
1–1     TRAFFIC ———————————>
<——————————— 1–1     TRAFFIC
:Wait
:Stop traffic
| | | | SP A | | SP B | | | | Link | | Link | :Start traffic | | | 1–1     TRAFFIC | ———————————> | | | <——————————— | 1–1     TRAFFIC | | <——————————— | 1–1     SLTM (invalid SLC) | | <——————————— | 1–1     SLTA (invalid SLC) | 1–1     TRAFFIC | ———————————> | | | <——————————— | 1–1     TRAFFIC | | | | :Wait | | | :Stop traffic | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Start traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1     TRAFFIC | ———————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————————— | 1–1     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————————— | 1–1     SLTM (invalid SLC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————————— | 1–1     SLTA (invalid SLC) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1–1     TRAFFIC | ———————————> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <——————————— | 1–1     TRAFFIC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Wait | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| :Stop traffic | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start traffic to B and C. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send the invalid SLTM and SLTA described above and check that they are discarded without impact on the traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Stop traffic. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **MTP Level 3** + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------| +| TEST NUMBER: 13.12 | | PAGE: 1 of 1 | +| REFERENCE: clause 15/Q.704 | | | +| TITLE: Invalid messages | | | +| SUBTITLE: Invalid user part unavailable messages | | | +| PURPOSE: To check the actions of the system on reception of an invalid user part unavailable message | | | +| PRE-TEST CONDITIONS: Link 1-1 available? | | | +| CONFIGURATION: A | TYPE OF TEST: VAT | TYPE OF SP: ALL | +| MESSAGE SEQUENCE:
SP A SP B
Link Link

:Start traffic

1-1 TRAFFIC —————→
←————— 1-1 TRAFFIC
←————— 1-1 UPU (non-existing OPC)
←————— 1-1 UPU (non-existing SI)
1-1 TRAFFIC —————→
←————— 1-1 TRAFFIC

:Wait

:Stop traffic

| | | +| TEST DESCRIPTION | | | +| 1. | Start traffic to B and C. | | +| 2. | Send the invalid UPUs described above and check that these messages are ignored. | | +| 3. | Stop traffic and check that it was not disturbed. | | + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/06a315363e7801bba8c7489a6694af19_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/06a315363e7801bba8c7489a6694af19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da726bb950ce2e3c231af3e903ecfa1dd748fbc8 --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/06a315363e7801bba8c7489a6694af19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bfc85c8944d18f6ef487eaf8a5405a0b0bbcb8ffe6b0cf850d5b895408fa66f +size 1327 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92f01c3f31a68c0d533d60bc8101591b3883719e --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf73ea595d1c5e327247c54e1dafd3196ac840b293abe58a37555557a706d4cd +size 10136 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc6438bcedc9e72173b2d8e74cd31c264ae32aeb --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40203e46b9f9a68e88bdb204bdd4b7e5899358c088ed2f2902abbc4eb57db8cb +size 8190 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/33dd23d4cb06e31f8690602510a6d717_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/33dd23d4cb06e31f8690602510a6d717_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e149e5c33232c75c1b3be365d5731ee43e97ce32 --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/33dd23d4cb06e31f8690602510a6d717_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb05efbab6899164e4077b475cf74ddb11a182841a4efefc449c9d570dc6caef +size 1193 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/3a054417cf8a47517e5b4b04f5b8023f_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/3a054417cf8a47517e5b4b04f5b8023f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44e879560703696e54a4f4503b2e9d481cc59bdc --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/3a054417cf8a47517e5b4b04f5b8023f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5aeb85715cec2b231f452054361f16d47360f930b7502fc9336282ebf55f7947 +size 2131 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/683dba75afe26e28cd4de5730b776760_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/683dba75afe26e28cd4de5730b776760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2bea244808a34d4d8fee22089fb907b789b99d5 --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/683dba75afe26e28cd4de5730b776760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15ad2599441f04e8ea946645592be625add8cbf6dc5ea292381bf8692c2a160a +size 1203 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/b38a6bcbb9dbcdf5bb3c1f507e9a552c_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/b38a6bcbb9dbcdf5bb3c1f507e9a552c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2040d72934b0cd561e66033671ea8c07b526f998 --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/b38a6bcbb9dbcdf5bb3c1f507e9a552c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5583c8435dbf0d5f236c9e55e8b72eefb8b186c6c9ccace3c8ca84f3a46b9ac +size 1681 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/d623125183022a80db828904aabbca16_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/d623125183022a80db828904aabbca16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453634e98b870e5977e99af04940f3d93cfd678b --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/d623125183022a80db828904aabbca16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a06fdc366aee40d599742147b525179396e0809d1ca72b3a7a69a7727c2ed3b0 +size 2013 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/e6f65e539f48240963eb1d2334f13fbb_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/e6f65e539f48240963eb1d2334f13fbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f79dc4e773d03ab2d776bc89f6e40652297d144 --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/e6f65e539f48240963eb1d2334f13fbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b58bbc082da434459e7f98ab1713ff20134c339556d01dd26b720b32bb462184 +size 1629 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/f2982b253666d4d1350d748428db4031_img.jpg b/marked/Q/T-REC-Q.787-199709-I_PDF-E/f2982b253666d4d1350d748428db4031_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d23d4488cc4d311a2d9bcebbd7299eb0a0cc2b7e --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/f2982b253666d4d1350d748428db4031_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36f2d9325ff26d178ed5dd61f76410978462b6849f0eb8b1babce1878f19e38f +size 1252 diff --git a/marked/Q/T-REC-Q.787-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.787-199709-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3af8f088486e970048b776d3c75ddb6b5c812b52 --- /dev/null +++ b/marked/Q/T-REC-Q.787-199709-I_PDF-E/raw.md @@ -0,0 +1,10076 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.787** + +(09/97) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Test +specification + +--- + +**Transaction Capabilities (TC) test specification** + +ITU-T Recommendation Q.787 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.709 | +| Signalling connection control part (SCCP) | Q.711–Q.719 | +| Telephone user part (TUP) | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## ITU-T RECOMMENDATION Q.787 + +# TRANSACTION CAPABILITIES (TC) TEST SPECIFICATION + +## Summary + +This revised Recommendation Q.787 contains the test scripts for the SS No. 7 Transaction Capabilities. This revised Recommendation now covers the test descriptions for the Dialogue Portion of the *White Book* (1993) Recommendations Q.771 to Q.774 (Transaction capabilities application part). + +## Source + +ITU-T Recommendation Q.787 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|---------------------------------------------------------|-----| +| 1 | Introduction ..... | 1 | +| 2 | Objectives of the test specification..... | 1 | +| 3 | Scope ..... | 1 | +| 4 | General principles of test..... | 2 | +| 5 | Test environment..... | 2 | +| 5.1 | Signalling relation ..... | 2 | +| 5.2 | Configuration..... | 2 | +| 6 | Background traffic..... | 2 | +| 7 | Test list ..... | 2 | +| 7.1 | TC Transaction sublayer (TSL) test specification..... | 2 | +| 7.1.1 | Guidance on performing transaction sublayer tests ..... | 2 | +| 7.1.2 | Transaction sublayer tests ..... | 3 | +| 7.2 | TC Component Sublayer (CSL) test specification ..... | 114 | +| 7.2.1 | Guidance on performing component sublayer tests..... | 114 | +| 7.2.2 | Component sublayer test list ..... | 114 | + + + +# **TRANSACTION CAPABILITIES (TC) TEST SPECIFICATION** + +*(revised in 1997)* + +# **1 Introduction** + +This Recommendation contains a detailed set of tests for the SS No. 7 Transaction Capabilities (TC). These tests are intended to validate the protocol specified in Recommendations Q.771 to Q.774. This Recommendation conforms to *White Book* (1993) which describes the basic rules for a test specification, as specified in Recommendation Q.780. + +## **2 Objectives of the test specification** + +The objective of the test specification is to provide: + +*Validation* – A level of confidence that a given implementation conforms to the *White Book* (1993) Recommendations Q.771 to Q.774 for SS No. 7 TC. + +*Compatibility* – A level of confidence that two implementations of SS No. 7 TC are able to interwork. + +The following criteria have been used in the generation of this test specification: + +- 1) the test specification does not provide exhaustive testing of all aspects of the SS No. 7 TC; +- 2) all tests are of a practical nature and implementable using the available technology; +- 3) the test list concentrates on the testing of normal signalling procedures. Testing of abnormal signalling procedures are only identified where this is regarded as particularly useful; +- 4) the test list does not include any tests which are application specific. These tests should be contained in application specific testing documentation and are outside the scope of this test specification. + +## **3 Scope** + +The test scripts are divided into two subclauses: 7.1, TC Transaction Sublayer (TSL) test specification and 7.2, TC Component Sublayer (CSL) test specification. Most TSL and CSL functions are dependent on each other and will need to be performed together. The division between TSL and CSL is for clarification and understanding only and does not imply an implementation. + +This test specification is designed to verify the TCAP functionality by testing TCAP messages and their contents. Performance aspects such as the limits of numbers of transactions IDs are not taken into account in this test specification. + +Some tests in this Recommendation require the generation of primitives; therefore, when performing these tests, appropriate normal system actions of the TCAP user will have to be chosen which result in the indicated primitive being generated. + +The testing of primitives is outside the scope of this Recommendation. Both messages and primitives are shown in the expected message sequence diagrams as indicated below, but primitives are shown for ease of understanding only. + +PRIMITIVE: ![double-lined arrow](06a315363e7801bba8c7489a6694af19_img.jpg) + +MESSAGE: ![single-lined arrow](683dba75afe26e28cd4de5730b776760_img.jpg) + +The test description provides a guide for the correct interpretation and implementation of the test, but it does not constrain its realisation. In particular, any reference to the internal structure of the + +Implementation Under Test (IUT), such as confirmation of internal states of the TC state machines, is given for clarification only and its practical realisation can be application dependent or vary from one test to another. All questions and checks in the test description should be answered "YES" for correct operation. + +Throughout the test specification, mention is made of "state machines". This specification conceptual model is used in Recommendation Q.774 to aid understanding. It does not imply an implementation, even when the test script asks for the state to be confirmed at the end of some tests. + +Possible methods of ensuring that the software has returned to the required state are enumerated in the 7.1.1 and 7.2.1, Guidance on performing component sublayer tests. + +The test specification is independent of any specific application, or implementation. + +## 4 General principles of test + +The tests are described as "Validation" or "Validation and Compatibility" tests. Each test script indicates in the "Type of Test" field, whether the test is "VAT" (Validation) or "VAT and CPT" (Validation and Compatibility). + +## 5 Test environment + +## 5.1 Signalling relation + +A stable signalling relation is required between "SP A" and "SP B" in order to test TCAP effectively. A tested network service layer, e.g. MTP and SCCP signalling relation, should be used for compatibility tests. + +## 5.2 Configuration + +Only one configuration is required to perform the tests given in the proposed test list, as shown in Figure 1: + +![Diagram showing two boxes labeled SP A and SP B. SP A is labeled IUT. Two arrows point between them, one in each direction. The word (Note) is written below the arrows. The text T1185310-97 is written below SP B.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +The diagram illustrates a signalling relation between two entities, SP A and SP B. SP A is labeled as the Implementation Under Test (IUT). Two horizontal arrows point between the boxes: a top arrow pointing from SP A to SP B, and a bottom arrow pointing from SP B to SP A. The word "(Note)" is centered below these arrows. The text "T1185310-97" is located below the SP B box. + +Diagram showing two boxes labeled SP A and SP B. SP A is labeled IUT. Two arrows point between them, one in each direction. The word (Note) is written below the arrows. The text T1185310-97 is written below SP B. + +NOTE – The arrows indicate a signalling relation. + +**Figure 1/Q.787 – Configuration: 1** + +## 6 Background traffic + +These tests do not take into account any level of background traffic. + +# 7 Test list + +The test list categories are given in the following subclauses. + +## 7.1 TC Transaction sublayer (TSL) test specification + +### 7.1.1 Guidance on performing transaction sublayer tests + +For each test, the expected message sequence, a test description and a check table for Information Elements (IE) within messages are given. + +In the expected message sequence, primitives are shown at SP A [Implementation Under Test (IUT) side] only. + +The function of the check table is to provide the contents of both the initiating message and the expected results in order to perform the checks in the test descriptions. The check table for IE within messages does not include information on the Component Portion or the User Abort Information IE contents, which are dependent on a specific application. In the check tables, messages from the IUT are described using the short form for any IE length, except for 1.1.3.1.1 which tests the length variations. However different forms complying with 3.3/Q.773 may be used in any test. + +In order to test for pre and post test results such as the state machines being in the idle state, the following procedure is suggested: + +- Send a Continue to the IUT with the identical destination transaction ID (of a transaction that should be idle) and expect an Abort with unrecognized transaction ID cause value. If another message is received as a response, then this means that the transaction is not in the idle state. + +NOTE – The details of these confirmation tests are implementation dependant. + +### 7.1.2 Transaction sublayer tests + +NDA No Details Available + +FFS For Further Study + +\* Validation and Compatibility + +All other tests are Validation Only. + +1 *Transaction sublayer* + +1.1 Valid function + +1.1.1 Unstructured dialogue + +\* 1.1.1.1 Tested side sending + +\* 1.1.1.2 Tested side receiving + +1.1.2 Structured dialogue + +1.1.2.1 Clearing before subsequent Message + +1.1.2.1.1 Valid clearing from initiating side + +\* 1) Prearranged ending + +\* 2) Abort by the TR-User + +1.1.2.1.2 Valid clearing from responding side + +1.1.2.1.2.1 IUT sending + +\* 1) Basic ending + +\* 2) Prearranged ending + +\* 3) Abort by the TR-User + +1.1.2.1.2.2 IUT receiving + +\* 1) Abort by the TR-User + +\* 2) Abort by transaction sublayer + +\* 3) Basic ending + +1.1.2.2 Clearing after Continue Message + +1.1.2.2.1 Valid clearing from initiating side + +1.1.2.2.1.1 IUT sending + +\* 1) Basic ending + +\* 2) Prearranged ending + +\* 3) Abort by the TR-User + +1.1.2.2.1.2 IUT receiving + +\* 1) Basic ending + +2) Abort by the transaction sublayer + +- \* + - 3) Abort by the TR-User +- 1.1.2.2.2 Valid clearing from responding side + - 1.1.2.2.2.1 IUT sending + - \* 1) Basic ending + - \* 2) Prearranged ending + - \* 3) Abort by the TR-User + - 1.1.2.2.2.2 IUT receiving + - \* 1) Basic ending + - \* 2) Abort by the transaction sublayer + - \* 3) Abort by the TR-User +- 1.1.2.3 Clearing after Continue Message (component portion not present) + - 1.1.2.3.1 Basic ending IUT sending + - 1.1.2.3.2 Basic ending IUT receiving +- 1.1.2.4 Message exchange after transaction established + - 1.1.2.4.1 IUT initiating + - 1.1.2.4.2 IUT receiving +- 1.1.2.5 TC Addressing + - 1.1.2.5.1 Register address change +- 1.1.3 Encoding and value variations + - 1.1.3.1 Encoding variations + - 1.1.3.1.1 Length variations + - 1.1.3.1.1.1 Definite short + - 1) Component portion length in definite short form embedded in short form + - 2) Component portion length in definite short form embedded in long form + - 1.1.3.1.1.2 Definite long + - 1) Component portion length in definite long form embedded in long form + - 1.1.3.1.1.3 Indefinite form + - 1) Component portion length in indefinite form embedded in indefinite form + - 1.1.3.2 Value variations + - 1.1.3.2.1 Transaction ID + - \* 1) Length is one octet + - \* 2) Length is four octets +- 1.2 Syntactically Invalid Behaviour + - 1.2.1 Invalid values for information elements + - 1.2.1.1 Begin Message type + - 1) OTID length = 0 + - 2) OTID length > four octets + - 1.2.1.2 First Continue Message + - 1) DTID length = 0 + - 1.2.1.3 Subsequent Continue Message + - 1) Component portion length incorrect + - 1.2.1.4 End Message + - 1) DTID length > four octets + +- 1.2.1.5 Abort Message + - 1) Invalid P-Abort cause value + - 2) P-Abort cause length incorrect +- 1.2.2 Invalid structure + - 1.2.2.1 Unidirectional Message type + - 1) Unknown information element present + - 1.2.2.2 Begin Message type + - 1) OTID absent + - 2) Unknown information element present + - 1.2.2.3 First Continue Message + - 1) OTID absent + - 2) DTID absent + - 3) OTID duplicated + - 4) DTID duplicated + - 5) Unknown information element present + - 1.2.2.4 Subsequent Continue Message + - 1) OTID absent + - 2) Unknown information element present + - 1.2.2.5 End Message + - 1) DTID absent + - 1.2.2.6 Abort Message + - 1) DTID absent + - 1.2.2.7 Unknown Message + - 1) OTID not included + - 2) OTID included and DTID not included + - 3) OTID included and DTID included +- 1.2.3 Invalid encoding (i.e. Rec. X.209 BER violation) + - 1.2.3.1 Begin Message type + - 1) Invalid tag + - 1.2.3.2 Continue Message type + - 1) Invalid tag +- 1.3 Inopportune Messages + - 1.3.1 Continue Message type + - 1) Receipt of Continue Message in Idle state with unassigned DTID + - 1.3.2 End Message type + - 1) Receipt of End message in Idle state + - 1.3.3 Abort Message type + - 1) Receipt of Abort message in Idle state +- 1.4 Multiple Transaction Encoding + - 1.4.1 Valid Transaction Encoding + - 1) New transaction request during transaction establishment + - 2) New transaction request after transaction establishment + - 1.4.2 Inopportune Messages + - 1) Message with unassigned DTID during transaction establishment + - 2) Message with unassigned DTID after transaction establishment + + + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.1.1.2 | | Sheet: 1 of 1 | +| REFERENCE: 3.3.3.1.2/Q.774 | | | +| TITLE: Valid function; Unstructured dialogue | | | +| SUBTITLE: Tested side receiving | | | +| PURPOSE: To verify that signalling point A is able to correctly receive a Unidirectional message | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
← UNIDIRECTIONAL
TR-UNI ind.
| | | +| TEST DESCRIPTION | | | +| 1. | Send a Unidirectional message from SP B to SP A. | | +| 2. | CHECK A: WAS THE UNIDIRECTIONAL MESSAGE CORRECTLY RECEIVED AT SP A? | | +| 3. | CHECK B: WAS THE TSL STATE MACHINE ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | +| UNIDIRECTIONAL
Message type tag: 01100001
Message type length: correct number of octets
Component portion tag: 01101100
Component portion length: correct number of octets | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 1.1.2.1.1 1) | | Sheet: 1 of 1 | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.3/Q.774 | | | | | +| TITLE: Valid function; Structured dialogue | | | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from initiating side; Prearranged ending | | | | | +| PURPOSE: To verify that signalling point A is able to correctly send a Begin message and then terminate the transaction locally by the "prearranged end" method | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)

TR-BEGIN req.

=====>

BEGIN —————→

TR-END req.

=====>

(Prearranged)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Send a Begin message from SP A to SP B. | | | | +| 2. | Before a reply is received from SP B, arrange for a TR-END request primitive (prearranged) to be passed to the TSL at SP A. | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | +| 4. | CHECK B: VERIFY THAT AN END MESSAGE WAS NOT SENT BY SP A. | | | | +| 5. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | +|

BEGIN

Message type tag: 01100010

Message type length: correct number of octets

Originating transaction ID tag: 01001000

Originating transaction ID length: correct number of octets

Originating transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100

Component portion length: correct number of octets

| | | | | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.1.2.1.1 2) | | Sheet: 1 of 1 | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.4/Q.774 | | | +| TITLE: Valid function; Structured dialogue | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from initiating side; Abort by the TR-User | | | +| PURPOSE: To verify that signalling point A is able to correctly generate a Begin message and then terminate the transaction locally by the "abort" method | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
TR-BEGIN req.

BEGIN →
TR-U-ABORT req.
| | | +| TEST DESCRIPTION | | | +| 1. | Send a Begin message from SP A to SP B. | | +| 2. | Before a reply is received from SP B, arrange for a TR-U-ABORT request primitive to be passed to the TSL at SP A. | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | +| 4. | CHECK B: WAS THE TR-U-ABORT REQUEST PURELY LOCAL AT SP A? | | +| 5. | CHECK C: VERIFY THAT NO ABORT MESSAGE WAS SENT FROM SP A. | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | +| BEGIN
Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)
Component portion tag: 01101100
Component portion length: correct number of octets | | | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------|------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------| +| TEST NUMBER: 1.1.2.1.2.1 1) | | Sheet: 1 of 2 | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.3/Q.774 | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from responding side; IUT Sending; Basic ending | | | | | | +| PURPOSE: To verify that signalling point A is able to receive a Begin message and then terminate the transaction by the "basic end" method | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

TR-BEGIN ind.

TR-END req.

(Basic)
END

←




→ 		SP B (TSL)
BEGIN
| | | SP A (TSL)

TR-BEGIN ind.

TR-END req.

(Basic)
END |

←




→ | SP B (TSL)
BEGIN | +| SP A (TSL)

TR-BEGIN ind.

TR-END req.

(Basic)
END |

←




→ | SP B (TSL)
BEGIN | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Send a Begin message from SP B to SP A. | | | | | +| 2. | On receipt of BEGIN indication arrange for a TR-END request primitive (basic) to be passed to the TSL at SP A. | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER? | | | | | +| 4. | CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | | +| 5. | CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | +| 6. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|--|--|--|--------------------|--|--|--|--|--|----------------------|--|--| +| TEST NUMBER: 1.1.2.1.2.1 2) | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from responding side; IUT sending; Prearranged ending | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to receive a Begin message and then terminate the transaction by the "prearranged end" method | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
TR-END req.
(Prearranged)
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | | | | TR-END req. | | | | | | (Prearranged) | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| (Prearranged) | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Send a Begin message from SP B to SP A.
  2. 2. On receipt of the BEGIN indication arrange for a TR-END request primitive (prearranged) to be passed to the TSL at SP A.
  3. 3. CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A?
  4. 4. CHECK B: VERIFY THAT AN END MESSAGE WAS NOT SENT BY SP A.
  5. 5. CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A?
| | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | +|

BEGIN

Message type tag: 01100010
Message type length: correct number of octets

Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100
Component portion length: correct number of octets

| | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------| +| TEST NUMBER: 1.1.2.1.2.1 3) | | Sheet: 1 of 1 | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.4/Q.774 | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from responding side; IUT sending; Abort by the TR-User | | | | | | +| PURPOSE: To verify that the signalling point A is able to receive a Begin message and then terminate the transaction by the "abort" method | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

TR-BEGIN ind.

<=====

TR-U-ABORT req.

=====

ABORT (U)

←──────────────────────────────────

──────────────────────────────────→

SP B (TSL)

BEGIN
| | |

SP A (TSL)

TR-BEGIN ind.

<=====

TR-U-ABORT req.

=====

ABORT (U)

|

←──────────────────────────────────

──────────────────────────────────→

|

SP B (TSL)

BEGIN

| +|

SP A (TSL)

TR-BEGIN ind.

<=====

TR-U-ABORT req.

=====

ABORT (U)

|

←──────────────────────────────────

──────────────────────────────────→

|

SP B (TSL)

BEGIN

| | | | +| TEST DESCRIPTION | | | | | | +| 1. | Send a Begin message from SP B to SP A. | | | | | +| 2. | On receipt of the BEGIN indication arrange for a TR-U-ABORT request primitive to be passed to the TSL at SP A. | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | +| 4. | CHECK B: WAS AN ABORT MESSAGE CORRECTLY SENT BY SP A? | | | | | +| 5. | CHECK C: WAS THE DTID IN THE ABORT MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | +| BEGIN

Message type tag: 01100010

Message type length: correct number of octets

Originating transaction ID tag: 01001000

Originating transaction ID length: correct number of octets

Originating transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100

Component portion length: correct number of octets


ABORT (U)

Message type tag: 01100111

Message type length: correct number of octets

Destination transaction ID tag: 01001001

Destination transaction ID length: correct number of octets

Destination transaction ID value: OCTET STRING (1-4 octets long)
(OTID value received in BEGIN message)

User abort information tag: 01101011

User abort information length: correct number of octets

| | | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 1.1.2.1.2.2 1) | | Sheet: 1 of 1 | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.4/Q.774 | | | | | +| TITLE: Valid function; Structured dialogue | | | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from responding side; IUT receiving; Abort by the TR-User | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate a transaction on reception of an Abort (U) message | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE SEQUENCE:

 SP A (TSL)                                     SP B (TSL) TR-BEGIN req. =====> BEGIN                                     -> <----- TR-U-ABORT ind. <=====
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Send a Begin message from SP A to SP B. | | | | +| 2. | Arrange for SP B to send an U-Abort message to SP A. | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | +| 4. | CHECK B: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | | | +| 5. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | +|

BEGIN

Message type tag: 01100010

Message type length: correct number of octets

Originating transaction ID tag: 01001000

Originating transaction ID length: correct number of octets

Originating transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100

Component portion length: correct number of octets

ABORT (U)

Message type tag: 01100111

Message type length: correct number of octets

Destination transaction ID tag: 01001001

Destination transaction ID length: correct number of octets

Destination transaction ID value: OCTET STRING (1-4 octets long)
(OTID value received in BEGIN message)

User abort information tag: 01101011

User abort information length: correct number of octets

| | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|----|--|--|----|------------------|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.1.2.2 2) | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from responding side; IUT receiving; Abort by transaction sublayer | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate a transaction on reception of an Abort (P) message | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN —>
<— ABORT (P)
TR-P-ABORT ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | —> | | | <— | ABORT (P) | TR-P-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | —> | | | | | | | | | | | | | | | | | | | | | | | +| | <— | ABORT (P) | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send an P-Abort message to SP A. | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | +|

BEGIN

Message type tag: 01100010
Message type length: correct number of octets

Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100
Component portion length: correct number of octets

ABORT (P)

Message type tag: 01100111
Message type length: correct number of octets

Destination transaction ID tag: 01001001
Destination transaction ID length: correct number of octets
Destination transaction ID value: OCTET STRING (1-4 octets long)
(OTID value received in BEGIN message)

P-Abort cause tag: 01001010
P-Abort cause length: one octet
P-Abort cause value: INTEGER (between 0 and 4)

| | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.1.2.1.2.2 3) | | Sheet: 1 of 1 | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.3/Q.774 | | | +| TITLE: Valid function; Structured dialogue | | | +| SUBTITLE: Clearing before subsequent Message; Valid clearing from responding side; IUT receiving; Basic ending | | | +| PURPOSE: To verify that the signalling point A is able to terminate a transaction on reception of an END message | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)

TR-BEGIN req.
>

BEGIN
END

TR-END ind.
<

| | | +| TEST DESCRIPTION | | | +| 1. | Send a Begin message from SP A to SP B. | | +| 2. | Arrange for SP B to send an End message to SP A. | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | +| 4. | CHECK B: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | +| 5. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | +|

BEGIN

Message type tag: 01100010
Message type length: correct number of octets

Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100
Component portion length: correct number of octets

END

Message type tag: 01100100
Message type length: correct number of octets

Destination transaction ID tag: 01001001
Destination transaction ID length: correct number of octets
Destination transaction ID value: OCTET STRING (1-4 octets long)
(OTID value received in BEGIN message)

Component portion tag: 01101100
Component portion length: correct number of octets

| | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|---|--|--|---|-----------------|-------------------------|--|--|---|--|--|--------------------|--|--|---|--|--|---------|--|--|------------|---|--| +| TEST NUMBER: 1.1.2.2.1.1 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT sending; Basic ending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate the transaction by the "basic end" method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. SP B to respond with a Continue message on receipt of the Begin message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
>
BEGIN →
← CONTINUE
TR-CONTINUE ind.
<
TR-END req.
>
(Basic)
END →
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | > | | | BEGIN | → | | | ← | CONTINUE | TR-CONTINUE ind. | | | < | | | TR-END req. | | | > | | | (Basic) | | | END | → | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP A to SP B. Arrange for SP B to respond with a Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | On receipt of the CONTINUE indication arrange for a TR-END request primitive (basic) to be passed to the TSL at SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED BY THE TSL AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE END MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE CONTINUE MESSAGE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK E: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|--------------------|--|--|--|--|--|----------------------|--|--| +| TEST NUMBER: 1.1.2.2.1.1 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT sending; Prearranged ending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to terminate the transaction by the "prearranged end" method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. SP B to respond with a Continue message on receipt of the Begin message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
TR-END req.
(Prearranged)
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | TR-END req. | | | | | | (Prearranged) | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Prearranged) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP A to SP B. Arrange for SP B to respond with a Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | On receipt of the CONTINUE indication arrange for a TR-END request primitive (prearranged) to be passed to the TSL at SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: VERIFY THAT THE TR-END REQUEST PRIMITIVE WAS PURELY LOCAL AND THAT AN END MESSAGE WAS NOT GENERATED AND SENT BY SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|------------------------|--|--|--|--|--|------------------|--|--| +| TEST NUMBER: 1.1.2.2.1.1 3) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT sending; Abort by the TR-User | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate the transaction by the "abort" method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. SP B to respond with a Continue message on receipt of the Begin message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
TR-U-ABORT req.
ABORT (U)
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | TR-U-ABORT req. | | | | | | ABORT (U) | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (U) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP A to SP B. Arrange for SP B to respond with a Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | On receipt of the CONTINUE indication arrange for a TR-U-ABORT request primitive to be passed to TSL at SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE ABORT MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WAS THE DTID IN THE ABORT MESSAGE THE SAME AS THE OTID IN THE CONTINUE MESSAGE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK E: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +User abort information tag: 01101011 +User abort information length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-----------------|---|--|--|---|------------|--------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.2.1.2 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1.2/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT receiving; Basic ending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a Continue message and then terminate the transaction on reception of an End message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
TR-CONTINUE req.
CONTINUE →
← END
TR-END ind.
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | | | | TR-CONTINUE req. | | | | | | CONTINUE | → | | | ← | END | TR-END ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to respond with an End message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE END MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------|------------|--|------------|--|--|--------------|----------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-----------------|--|--|--|--|------------------|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.2.1.2 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1.2/Q.774 and 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT receiving; Abort by the transaction sublayer | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a Continue message and then terminate the transaction on reception of an Abort message by the peer TSL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
BEGIN
TR-BEGIN ind.
TR-CONTINUE req.
CONTINUE
ABORT (P)
TR-P-ABORT ind.
| | | SP A (TSL) | | SP B (TSL) | | | BEGIN | TR-BEGIN ind. | | | | | | TR-CONTINUE req. | | | | | | CONTINUE | | | | | ABORT (P) | TR-P-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ABORT (P) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to respond with an Abort (P) message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: one octet +P-Abort cause value: INTEGER (0 .. 4) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------|------------|--|------------|--|---|--------------|----------------------|--|--|---|--|--|-------------------------|--|--|--|--|--|-----------------|--|--|--|---|------------------|------------------------|--|--|---|--|--| +| TEST NUMBER: 1.1.2.2.1.2 3) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1.2/Q.774 and 3.3.3.2.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT receiving; Abort by the TR-User | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a Continue message and then terminate the transaction on reception of an Abort message by the peer TR-User | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
<
TR-CONTINUE req.
CONTINUE
← ABORT (U)
TR-U-ABORT ind.
<
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | < | | | TR-CONTINUE req. | | | | | | CONTINUE | | | | ← | ABORT (U) | TR-U-ABORT ind. | | | < | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | ABORT (U) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to respond with an Abort (U) message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (U) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +User abort information tag: 01101011 +User abort information length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-----------------|---|--|--------------------|--|--|--|--|--|---------|--|--|------------|---|--| +| TEST NUMBER: 1.1.2.2.2.1 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from responding side; IUT sending; Basic ending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a Continue message and then terminate the transaction by the "basic end" method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
TR-CONTINUE req.
CONTINUE →
TR-END req.
(Basic)
END →
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | | | | TR-CONTINUE req. | | | | | | CONTINUE | → | | TR-END req. | | | | | | (Basic) | | | END | → | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Terminate the transaction with an End (Basic) message from SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT BY THE TSL AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE DTID IN THE CONTINUE AND END MESSAGES THE SAME AS THE OTID IN THE BEGIN MESSAGE. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK E: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| TEST NUMBER: 1.1.2.2.2.1 2) | | Sheet: 1 of 2 | | | +| REFERENCE: 3.3.3.2.1/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.3/Q.774 | | | | | +| TITLE: Valid function; Structured dialogue | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from responding side; IUT sending; Prearranged ending | | | | | +| PURPOSE: To verify that signalling point A is able to generate a Continue message and then terminate the transaction by the "prearranged end" method | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

←

TR-BEGIN ind.

≡

TR-CONTINUE req.

⇒

CONTINUE

→

TR-END req.

⇒

(Prearranged)

SP B (TSL)

BEGIN
| | |

SP A (TSL)

←

TR-BEGIN ind.

≡

TR-CONTINUE req.

⇒

CONTINUE

→

TR-END req.

⇒

(Prearranged)

|

SP B (TSL)

BEGIN

| +|

SP A (TSL)

←

TR-BEGIN ind.

≡

TR-CONTINUE req.

⇒

CONTINUE

→

TR-END req.

⇒

(Prearranged)

|

SP B (TSL)

BEGIN

| | | | +| TEST DESCRIPTION | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A. | | | | +| 2. | Arrange for SP A to respond with a Continue message. | | | | +| 3. | Terminate the transaction with a TR-END request primitive (prearranged) from SP A. | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT BY THE TSL AT SP A? | | | | +| 6. | CHECK C: VERIFY THAT THE TR-END REQUEST PRIMITIVE WAS PURELY LOCAL AND THAT AN END MESSAGE WAS NOT GENERATED AND SENT BY SP A. | | | | +| 7. | CHECK D: WAS THE DTID IN THE CONTINUE MESSAGE THE SAME AS THE OTID IN THE BEGIN? | | | | +| 8. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------| +| TEST NUMBER: 1.1.2.2.2.1 3) | | Sheet: 1 of 2 | | | | +| REFERENCE: 3.3.3.2.1/Q.774, 3.3.3.2.2/Q.774 and 3.3.3.2.4/Q.774 | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from initiating side; IUT sending; Abort by the TR-User | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a Continue message and then terminate the transaction by the "abort" method | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

TR-BEGIN ind.

TR-CONTINUE req.

CONTINUE
TR-U-ABORT req.

ABORT (U)

←


→


→ 		SP B (TSL)
BEGIN
| | | SP A (TSL)

TR-BEGIN ind.

TR-CONTINUE req.

CONTINUE
TR-U-ABORT req.

ABORT (U) |

←


→


→ | SP B (TSL)
BEGIN | +| SP A (TSL)

TR-BEGIN ind.

TR-CONTINUE req.

CONTINUE
TR-U-ABORT req.

ABORT (U) |

←


→


→ | SP B (TSL)
BEGIN | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Arrange for a Begin message to be sent from SP B to SP A. | | | | | +| 2. | Arrange for SP A to respond with a Continue message, then abort the transaction by passing a TR-U-ABORT request primitive to the TSL at SP B. | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | +| 4. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | +| 5. | CHECK C: WAS THE ABORT MESSAGE CORRECTLY SENT FROM SP A? | | | | | +| 6. | CHECK D: WAS THE DTID IN THE CONTINUE AND ABORT MESSAGES THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | +| 7. | CHECK E: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +User abort information tag: 01101011 +User abort information length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|---|--|--|---|-----------------|-------------------------|--|--|--|--|--|--|---|------------|--------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.2.2.2 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from responding side; IUT receiving; Basic ending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate the transaction on reception of an End message following a Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN →
← CONTINUE
TR-CONTINUE ind.
← END
TR-END ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | → | | | ← | CONTINUE | TR-CONTINUE ind. | | | | | | | ← | END | TR-END ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Terminate the transaction with an End (basic) message from SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE END MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|--|--|------------------|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.2.2.2 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from responding side; IUT receiving; Abort by the transaction sublayer | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate the transaction on reception of an Abort (P) message following a Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
ABORT (P)
TR-P-ABORT ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | | | ABORT (P) | TR-P-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ABORT (P) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Terminate the transaction with an Abort (P) message from SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +##### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +P-Abort cause tag: 01001010 +P-Abort cause length: one octet +P-Abort cause value: INTEGER (0 .. 4) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|--|--|------------------|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.2.2.2 3) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2.1/Q.774 and 3.3.3.2.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message; Valid clearing from responding side; IUT receiving; Abort by the TR-User | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to terminate the transaction on reception of an Abort (U) message following a Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
ABORT (U)
TR-U-ABORT ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | | | ABORT (U) | TR-U-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ABORT (U) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to respond with a Continue message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Terminate the transaction with an Abort (U) message from SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE ABORT MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (U) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +User abort information tag: 01101011 +User abort information length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|---|--|--|---|-----------------|-------------------------|--|--|---|--|--|--------------------|--|--|---|--|--|------------|---|--| +| TEST NUMBER: 1.1.2.3.1 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message (component portion not present); Basic ending IUT sending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that SP A is able to accept a Continue message without CP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
>
BEGIN →
← CONTINUE
TR-CONTINUE ind.
<
TR-END req.
>
END →

| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | > | | | BEGIN | → | | | ← | CONTINUE | TR-CONTINUE ind. | | | < | | | TR-END req. | | | > | | | END | → | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a Continue message to SP A without CP. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP A to send an End message to SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE END MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE TSL STATE MACHINE LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets (range 1-4) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets (range 1-4) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|---|--|--|-------------------------|--|--|----|--|--|-----------------|----|--|--|---|------------|--------------------|--|--|---|--|--| +| TEST NUMBER: 1.1.2.3.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clearing after continue Message (component portion not present); Basic ending IUT receiving | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that SP A is able to accept a Begin message without CP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
<
TR-CONTINUE req.
═>
CONTINUE ─>
← END
TR-END ind.
<
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | < | | | TR-CONTINUE req. | | | ═> | | | CONTINUE | ─> | | | ← | END | TR-END ind. | | | < | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ═> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a BEGIN message to SP A without CP. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to send a CONTINUE message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send an END message to SP A without CP. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE END MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE TSL STATE MACHINE LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets (range 1-4) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets (range 1-4) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-----------------|--|--|--|--|------------|--------------------|--|--|--|--|--| +| TEST NUMBER: 1.1.2.4.1 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Message exchange after transaction established; IUT initiating | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify the correct message flow between SP A and SP B, after transaction established (IUT initiating) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
TR-CONTINUE req.
CONTINUE
END
TR-END ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | TR-CONTINUE req. | | | | | | CONTINUE | | | | | END | TR-END ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a Continue message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP A to send a Continue message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Arrange for SP B to send an END message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK C: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK D: WAS THE END MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | CHECK E: WAS THE TSL STATE MACHINE LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: 0 (invalid length) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: 0 (invalid length) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100101 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: 0 (invalid length) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------|------------|--|------------|--|---|--------------|----------------------|--|--|---|--|--|-------------------------|--|--|----|--|--|-----------------|----|--|--|---|-----------------|-------------------------|--|--|---|--|--|--------------------|--|--|----|--|--|------------|----|--| +| TEST NUMBER: 1.1.2.4.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Structured dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Message exchange after transaction established; IUT receiving | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify the correct message flow between SP A and SP B, after transaction established (IUT receiving) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
<
TR-CONTINUE req.
─>
CONTINUE ─>
← CONTINUE
TR-CONTINUE ind.
<
TR-END req.
─>
END ─>
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | < | | | TR-CONTINUE req. | | | ─> | | | CONTINUE | ─> | | | ← | CONTINUE | TR-CONTINUE ind. | | | < | | | TR-END req. | | | ─> | | | END | ─> | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to send a Continue message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send a Continue message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Arrange for SP A to send an END message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK C: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK D: WAS THE END MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | CHECK E: WAS THE TSL STATE MACHINE LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: 0 (invalid length) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets (range 1-4) +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets (range 1-4) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100101 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets (range 1-4) +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.1.2.5.1 | | Sheet: 1 of 1 | +| REFERENCE: 3.1.2.2.2.2/Q.771 | | | +| TITLE: Valid function, Structured dialogue | | | +| SUBTITLE: TC addressing; Register address change | | | +| PURPOSE: To verify that a correctly reported address change of the peer implementation is registered and used in subsequent messages. | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
UDT ( CLG A, CLD B)

BEGIN

—————→

TR-CONTINUE ind.

<═══════

TR-END req

═══════>

TR-BEGIN ind.

═══════>

TR-CONTINUE req.

<═══════

UDT ( CLG B*, CLD A)

CONTINUE

UDT ( CLG A, CLD B*)

END

—————→

| | | +| TEST DESCRIPTION | | | +| 1.
2.
3.
4. |

Arrange for SP A to send a Begin message to SP B.

Arrange for SP B to respond with a Continue message in which the calling address has been optimized.

Arrange for SP A to respond with an End message.

CHECK A: WAS THE CALLED ADDRESS IN THE SCCP MESSAGE HEADER FOR THE END THE SAME AS THE CALLING ADDRESS IN THE SCCP MESSAGE HEADER FOR THE CONTINUE MESSAGE?

| | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.1.3.1.1.1 1) | | Sheet: 1 of 2 | +| REFERENCE: 3.3/Q.774 | | | +| TITLE: Valid function; Encoding and value variations | | | +| SUBTITLE: Encoding variations; Length variations; Definite short; Component portion length in definite short form embedded in short form | | | +| PURPOSE: To verify that signalling point A is able to accept a Begin message whose length is encoded using the definite short form and with a component portion whose length is encoded using the definite short form | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

SP B (TSL)

←

BEGIN

TR-BEGIN ind.

<=====

TR-END req.

===== >

(Basic)

→

END

| | | +| TEST DESCRIPTION | | | +|

1.

2.

3.

4.

5.

6.

|

Arrange for SP B to send a Begin message to SP A with lengths encoded as described in the purpose of the test.

Arrange for SP A to respond with an End message.

CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER?

CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A?

CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE?

CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A?

| | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 + +Message type length: correct number of octets coded in definite short form + +Originating transaction ID tag: 01001000 + +Originating transaction ID length: one octet + +Originating transaction ID value: OCTET STRING (1 octet) + +Component portion tag: 01101100 + +Component portion length: correct number of octets coded in definite short form + +###### END + +Message type tag: 01100100 + +Message type length: correct number of octets + +Destination transaction ID tag: 01001001 + +Destination transaction ID length: one octet + +Destination transaction ID value: OCTET STRING (1 octet) + +(OTID value received in BEGIN message) + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|--|--|--|--------------------|--|--|--|--|--|----------------|--|--|------------|---|--| +| TEST NUMBER: 1.1.3.1.1.1 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Encoding and value variations | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Encoding variations; Length variations; Definite short; Component portion length in definite short form embedded in long form | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to accept a Begin message whose length is encoded using the definite long form and with a component portion whose length is encoded using the definite short form | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
TR-END req.
(Basic)
END →







| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | | | | TR-END req. | | | | | | (Basic) | | | END | → | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | → | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A with lengths encoded as described in the purpose of the test. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with an End message. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 + +Message type length: correct number of octets coded in definite long form + +Originating transaction ID tag: 01001000 + +Originating transaction ID length: one octet + +Originating transaction ID value: OCTET STRING (1 octet) + +Component portion tag: 01101100 + +Component portion length: correct number of octets coded in definite short form + +###### END + +Message type tag: 01100100 + +Message type length: correct number of octets + +Destination transaction ID tag: 01001001 + +Destination transaction ID length: one octet + +Destination transaction ID value: OCTET STRING (1 octet) + +(OTID value received in BEGIN message) + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|---|--|--|--------------------|--|--|--|--|--|----------------|--|--|------------|---|--| +| TEST NUMBER: 1.1.3.1.1.2 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Encoding and value variations | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Encoding variations; Length variations; Definite long; Component portion length in definite long form embedded in long form | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to accept a Begin message whose length is encoded using the definite long form and with a component portion whose length is encoded using the definite long form | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
<
TR-END req.
(Basic)
END ➔
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | < | | | TR-END req. | | | | | | (Basic) | | | END | ➔ | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A with lengths encoded as described in the purpose of the test. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with an End message. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 + +Message type length: correct number of octets coded in definite long form + +Originating transaction ID tag: 01001000 + +Originating transaction ID length: one octet + +Originating transaction ID value: OCTET STRING (1 octet) + +Component portion tag: 01101100 + +Component portion length: correct number of octets coded in definite long form + +###### END + +Message type tag: 01100100 + +Message type length: correct number of octets + +Destination transaction ID tag: 01001001 + +Destination transaction ID length: one octet + +Destination transaction ID value: OCTET STRING (1 octet) + +(OTID value received in BEGIN message) + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|---|--|--|--------------------|--|--|-------------|--|--|----------------|--|--|------------|-------------|--| +| TEST NUMBER: 1.1.3.1.1.3 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Encoding and value variations | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Encoding variations; Length variations; Indefinite form; Component portion length in indefinite form embedded in indefinite form | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to accept a Begin message whose length is encoded using the indefinite form and with a component portion whose length is encoded using the indefinite form | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
<
TR-END req.
>
(Basic)
END >
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | < | | | TR-END req. | | | > | | | (Basic) | | | END | > | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A with lengths encoded as described in the purpose of the test. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with an End message. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets coded in indefinite form +Originating transaction ID tag: 01001000 +Originating transaction ID length: one octet +Originating transaction ID value: OCTET STRING (1 octet) +Component portion tag: 01101100 +Component portion length: correct number of octets coded in indefinite form +Component contents provided by TC user +EOC Tag: 00000000, Length: 00000000 + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: one octet +Destination transaction ID value: OCTET STRING (1 octet) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|---|--------------|----------------------|--|--|--|--|--|--------------------|--|--|--|--|--|----------------|--|--|------------|---|--| +| TEST NUMBER: 1.1.3.2.1 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid function; Encoding and value variations | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Value variations; Transaction ID; Length is one octet | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to deal with correct encoding of OTID information element (1 octet long) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
TR-END req.
(Basic)
END →
| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | | | | TR-END req. | | | | | | (Basic) | | | END | → | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | → | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A with an OTID 1 octet long. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to respond with an End message. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: one octet +Originating transaction ID value: OCTET STRING (1 octet) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: one octet +Destination transaction ID value: OCTET STRING (1 octet) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| TEST NUMBER: 1.1.3.2.1 2) | | Sheet: 1 of 2 | | | +| REFERENCE: 5.3/Q.774 | | | | | +| TITLE: Valid function; Encoding and value variations | | | | | +| SUBTITLE: Value variations; Transaction ID; Length is four octets | | | | | +| PURPOSE: To verify that signalling point A is able to deal with correct encoding of OTID information element (4 octets long) | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

←

TR-BEGIN ind.

=====

TR-END req.

=====

(Basic)

END

SP B (TSL)

BEGIN

→
| | |

SP A (TSL)

←

TR-BEGIN ind.

=====

TR-END req.

=====

(Basic)

END

|

SP B (TSL)

BEGIN

→

| +|

SP A (TSL)

←

TR-BEGIN ind.

=====

TR-END req.

=====

(Basic)

END

|

SP B (TSL)

BEGIN

→

| | | | +| TEST DESCRIPTION | | | | | +| 1. | Arrange for SP B to send a Begin message to SP A with an OTID four octets long. | | | | +| 2. | Arrange for SP A to respond with an End message. | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A AND PASSED TO THE TR-USER? | | | | +| 4. | CHECK B: WAS AN END MESSAGE CORRECTLY SENT BY SP A? | | | | +| 5. | CHECK C: WAS THE DTID IN THE END MESSAGE THE SAME AS THE OTID IN THE BEGIN MESSAGE? | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: four octets +Originating transaction ID value: OCTET STRING (4 octets) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: four octets +Destination transaction ID value: OCTET STRING (4 octets) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|------------|--|------------|----------------------------|---|--------------| +| TEST NUMBER: 1.2.1.1 1) | | Sheet: 1 of 1 | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | | | | | +| SUBTITLE: Begin message type; OTID length = 0 | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Begin message, signalling point A is able to discard the message | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the Begin message contains an OTID length of 0 | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
Detect syntax error ← BEGIN
| | | SP A (TSL) | | SP B (TSL) | Detect syntax error | ← | BEGIN | +| SP A (TSL) | | SP B (TSL) | | | | | | | +| Detect syntax error | ← | BEGIN | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Arrange for SP B to send the corrupted Begin message to SP A, with an OTID length of 0. | | | | | | | | +| 2. | CHECK A: THAT THE USER WAS NOT INFORMED OF THE BEGIN MESSAGE. | | | | | | | | +| 3. | CHECK B: WERE NO MESSAGES SENT FROM SP A? | | | | | | | | +| 4. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | +| BEGIN
Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: 0
Originating transaction ID value: not present
Component portion tag: 01101100
Component portion length: correct number of octets | | | | | | | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.2.1.1 2) | | Sheet: 1 of 1 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | +| SUBTITLE: Begin message type; OTID length > four octets | | | +| PURPOSE: To verify that signalling point A is able to deal with invalid encoding of OTID information element | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the Begin message contains an OTID length of > four octets | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)
Detect syntax error
←
SP B (TSL)
BEGIN
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send the corrupted Begin message to SP A, with an OTID five octets long. | | +| 2. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | +| 3. | CHECK B: VERIFY THAT THE TR-USER AT SP A WAS NOT INFORMED OF THIS EVENT. | | +| 4. | CHECK C: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE BEGIN MESSAGE. | | +| 5. | CHECK D: WERE ALL TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | +|

BEGIN

Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: five octets
Originating transaction ID value: OCTET STRING (5 octets long)
Component portion tag: 01101100
Component portion length: correct number of octets

| | | + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|----------------------------|--|-----------------|-----------------------------|--|--| +| TEST NUMBER: 1.2.1.2 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: First continue Message; DTID length = 0 | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message, with DTID length = 0, SP A is able to discard the message or abort the transaction correctly | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the first Continue message contains a DTID of length = 0 | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
Detect syntax error CONTINUE
ABORT (P) (see Note)
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | Detect syntax error | | CONTINUE | ABORT (P) (see Note) | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | +| Detect syntax error | | CONTINUE | | | | | | | | | | | | | | | | | | | +| ABORT (P) (see Note) | | | | | | | | | | | | | | | | | | | | | +| NOTE – If the Abort is not sent, this may be valid behaviour depending on the implementation. | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send the corrupted Continue message. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE TR-USER AT SP A WAS NOT INFORMED OF THE CONTINUE MESSAGE AT SP A. | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WERE THE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION PRIOR TO THE CONTINUE MESSAGE LEFT IN INITIATION SENT STATE ? | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND P-ABORT CAUSE VALUE? | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: incorrect transaction portion + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|---------------------|--|-----------------|-----------------------------|--|--|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.2.1.3 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Subsequent continue Message; Component portion length incorrect | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message with OTID derivable and DTID derivable and assigned, after transaction establishment, SP A is able to abort the transaction | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
Detect error CONTINUE
ABORT (P) (see Note)
TR-P-ABORT ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | Detect error | | CONTINUE | ABORT (P) (see Note) | | | TR-P-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect error | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (P) (see Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – If the Abort is not sent, this may be valid behaviour depending on the implementation. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a correct Continue message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send a corrupted Continue message to SP A (incorrect CP length). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND P-ABORT CAUSE VALUE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: IF THE ABORT WAS SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE (1st) + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE (2nd) + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: badly formatted transaction portion 00000010 + +| | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|--|--|---------------------|--|------------| +| TEST NUMBER: 1.2.1.4 1) | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | | | | | | | | | | | | | | +| SUBTITLE: End message; DTID length > four octets | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted End message, SP A is able to discard the message | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the End message DTID length > four octets | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
>
BEGIN
Detect error END
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | > | | | BEGIN | | | Detect error | | END | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | +| Detect error | | END | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to Send a Begin message to SP B. | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a corrupted End message to SP A (invalid DTID length). | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE END MESSAGE. | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION PRIOR TO THE END MESSAGE, LEFT IN THE INITIATION SENT STATE? | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | +|

BEGIN

Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)
Component portion tag: 01101100
Component portion length: correct number of octets

END

Message type tag: 01100100
Message type length: correct number of octets
Destination transaction ID tag: 01001001
Destination transaction ID length: 00000101 (Invalid length)
Destination transaction ID value: OCTET STRING (5 octets long)
(OTID value received in BEGIN message)
Component portion tag: 01101100
Component portion length: correct number of octets

| | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------|------------|----------------------|--|--|--|--------------|--|----------------------------|--|------------------|------------------------|--|--|--| +| TEST NUMBER: 1.2.1.5 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | | | | | | | | | | | | | | +| SUBTITLE: Abort message; Invalid P-Abort cause value | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to deal with incorrect encoding of P-Abort cause information element (illegal value) | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that an Abort message with a DTID that is derivable and assigned, contains a syntax error and is sent to SP A in response to the Begin message | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
Detect syntax error ABORT (P)
TR-P-ABORT ind.

NOTE – The sending of the TR-Abort ind. is implementation dependent.

| | | SP A (TSL) | SP B (TSL) | TR-BEGIN req. | | | | BEGIN | | Detect syntax error | | ABORT (P) | TR-P-ABORT ind. | | | | +| SP A (TSL) | SP B (TSL) | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | +| Detect syntax error | | ABORT (P) | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B and for SP B to respond with the corrupted Abort message. (Illegal P-Abort cause value). | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES ARE GENERATED BY SP A IN RESPONSE TO THE CORRUPTED ABORT MESSAGE. | | | | | | | | | | | | | | | | | +| 4. | CHECK C: IF THE TR-ABORT IND. WAS SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +##### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: INTEGER (5 – Illegal value for this field) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|----------------------------|--|------------------|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.2.1.5 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Abort message; P-Abort cause length incorrect | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Abort message with incorrect cause length, signalling point A is able to discard the message and advise the local user | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that an Abort message with a DTID that is derivable and assigned, contains a syntax error and is sent to SP A in response to the Begin message | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

 sequenceDiagram     participant A as SP A (TSL)     participant B as SP B (TSL)     Note over A: TR-BEGIN req.     A->>B: BEGIN     Note over B: Detect syntax error     B->>A: ABORT (P)     Note over A: TR-P-ABORT ind.
SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
Detect syntax error ABORT (P)
TR-P-ABORT ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | Detect syntax error | | ABORT (P) | TR-P-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | +| Detect syntax error | | ABORT (P) | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – The sending of the TR-Abort ind. is implementation dependent. | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B and for SP B to respond with the corrupted Abort message. (Corrupted P-Abort cause length). | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES ARE GENERATED BY SP A IN RESPONSE TO THE CORRUPTED ABORT MESSAGE. | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: IF THE TR-ABORT IND. WAS SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets (i.e. not one) +P-Abort cause value: INTEGER (0 .. 4) + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.2.2.1 1) | | Sheet: 1 of 1 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Unidirectional Message type; Unknown information element present | | | +| PURPOSE: To verify that on receipt of a corrupted Unidirectional message, signalling point A is able to discard the message | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that an Unidirectional message contains a syntax error and is sent to SP A | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
Detect syntax error ← UNIDIRECTIONAL
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send the corrupted Unidirectional message to SP A. | | +| 2. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE UNIDIRECTIONAL MESSAGE AT SP A. | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES WERE GENERATED IN RESPONSE TO THE UNIDIRECTIONAL MESSAGE. | | +| 4. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | +| UNIDIRECTIONAL
Message type tag: 01100001
Message type length: correct number of octets
Component portion missing | | | + +| | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|------------|--|------------|----------------------------|--------|--------------| +| TEST NUMBER: 1.2.2.2 1) | | Sheet: 1 of 1 | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | +| SUBTITLE: Begin Message type; OTID absent | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Begin message; signalling point A is able to discard the message | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the Begin message contains a syntax error and the OTID is not derivable | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL)SP B (TSL)
Detect syntax error←-----BEGIN
| | | SP A (TSL) | | SP B (TSL) | Detect syntax error | ←----- | BEGIN | +| SP A (TSL) | | SP B (TSL) | | | | | | | +| Detect syntax error | ←----- | BEGIN | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Arrange for SP B to send the corrupted Begin message to SP A, with OTID not present. | | | | | | | | +| 2. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THIS EVENT AT SP A. | | | | | | | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES WERE GENERATED IN RESPONSE TO THE THE CORRUPTED BEGIN MESSAGE. | | | | | | | | +| 4. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | +| BEGIN
Message type tag: 01100010
Message type length: correct number of octets
OTID absent | | | | | | | | | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.2.2.2 2) | | Sheet: 1 of 2 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Begin Message type; Unknown information element present | | | +| PURPOSE: To verify that on receipt of a corrupted Begin message, with an invalid information element, signalling point A is able to discard the message and generate an Abort message | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the Begin message contains a syntax error | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)
Detect syntax error
ABORT (P)

←
→
SP B (TSL)
BEGIN
 

| | | +| NOTE – If the Abort is not sent, this may be valid behavior depending on the implementation. | | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send the corrupted Begin message to SP A, with an invalid information element after the OTID. | | +| 2. | CHECK A: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | +| 3. | CHECK B: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Information element tag: unknown (eg. 01101101) +Information element length: correct number of octets +Information element value: OCTET STRING + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: incorrect transaction portion 00000011 + +| | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|-----------------|--|----------------------------|-----------------|-----------------| +| TEST NUMBER: 1.2.2.3 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | +| SUBTITLE: First Continue Message; OTID absent | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message, signalling point A is able to discard the message | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. SP B to respond with a Continue message on receipt of the Begin message. Arrange the data at SP B such that the Continue message contains a syntax error and the OTID is not derivable | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
→
BEGIN ——————————————→
Detect syntax error ←—————————————— CONTINUE








| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | → | | | BEGIN | ——————————————→ | | Detect syntax error | ←—————————————— | CONTINUE | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | +| → | | | | | | | | | | | | | | | | | | +| BEGIN | ——————————————→ | | | | | | | | | | | | | | | | | +| Detect syntax error | ←—————————————— | CONTINUE | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send the corrupted Continue message (OTID not derivable) to SP A. | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE CONTINUE MESSAGE AT SP A. | | | | | | | | | | | | | | | | | +| 5. | CHECK C: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE CORRUPTED CONTINUE MESSAGE? | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THE TRANSACTION, PRIOR TO THE CONTINUE MESSAGE, LEFT IN THE INITIATION SENT STATE AT SP A? | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets + +###### OTID absent + +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|----------------------------|--|-----------------|--|---------------|--|------------------|--|--| +| TEST NUMBER: 1.2.2.3 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: First Continue Message; DTID absent | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message containing no DTID, signalling point A is able to discard the message or abort the transaction | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. SP B to respond with a Continue message on receipt of the Begin message. Arrange the data at SP B such that the Continue message contains no DTID | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
Detect syntax error CONTINUE
(DTID absent)
ABORT (P)
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | Detect syntax error | | CONTINUE | | (DTID absent) | | ABORT (P) | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | +| Detect syntax error | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | +| | (DTID absent) | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (P) | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – If the Abort is not sent, this may be valid behaviour depending on the implementation. | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send the corrupted Continue message (DTID absent). | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE CONTINUE MESSAGE AT SP A. | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WERE THE TSL STATE MACHINES ASSOCIATED WITH THE TRANSACTION, PRIOR TO THE CONTINUE MESSAGE, LEFT IN THE INITIATION SENT STATE? | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) + +###### DTID absent + +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: incorrect transaction portion 00000011 + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.2.2.3 3) | | Sheet: 1 of 2 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: First Continue Message; OTID duplicated | | | +| PURPOSE: To check the correct behaviour of the implementation under test on receipt of a first Continue message with a duplicated OTID | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

TR-BEGIN req.

⇒⇒⇒⇒⇒

BEGIN

SP B (TSL)

→ (with duplicated OTID)

← CONTINUE

→

ABORT (P)

TR-P-ABORT ind.

⇒⇒⇒⇒⇒

NOTE – If the ABORT message and primitive are not sent, this may be valid behaviour depending on the implementation.

| | | +| TEST DESCRIPTION | | | +|

1.

2.

3.

4.

5.

|

Arrange SP A to send a Begin message.

Arrange for SP B to send a Continue message to SP A with a duplicated OTID.

CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A?

CHECK B: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID VALUE AND CORRECT P-ABORT CAUSE VALUE?

CHECK C: IF THE ABORT MESSAGE AND PRIMITIVE WERE SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A?

| | + + + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.2.2.3 4) | | Sheet: 1 of 2 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: First Continue Message; DTID duplicated | | | +| PURPOSE: To check the correct behaviour of the implementation under test on receipt of a first Continue message with a duplicated DTID | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

 SP  A (TSL)                                     SP  B (TSL) TR-BEGIN req. =====> BEGIN                                     ->                                 (with duplicated DTID)                                 <->                CONTINUE ABORT (P)                                     -> TR-P-ABORT ind. <=====

NOTE – If the ABORT message and primitive are not sent, this may be valid behaviour depending on the implementation.

| | | +| TEST DESCRIPTION | | | +| 1. | Arrange SP A to send a Begin message. | | +| 2. | Arrange for SP B to send a Continue message to SP A with a duplicated DTID. | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | +| 4. | CHECK B: WAS AN ABORT MESSAGE WITH CORRECT DTID VALUE AND CORRECT P-ABORT CAUSE VALUE CORRECTLY SENT FROM SP A? | | +| 5. | CHECK C: IF THE ABORT MESSAGE AND PRIMITIVE WERE SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 + Message type length: correct number of octets + Originating transaction ID tag: 01001000 + Originating transaction ID length: correct number of octets + Originating transaction ID value: OCTET STRING (1-4 octets long) + Component portion tag: 01101100 + Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 + Message type length: correct number of octets + Originating transaction ID tag: 01001000 + Originating transaction ID length: correct number of octets + Originating transaction ID value: OCTET STRING (1-4 octets long) + Destination transaction ID tag: 01001001 } + Destination transaction ID length: correct number of octets } + Destination transaction ID value: OCTET STRING (1-4 octets long) } + (OTID value received in BEGIN message) } + } Duplicated + Destination transaction ID tag: 01001001 } + Destination transaction ID length: correct number of octets } + Destination transaction ID value: OCTET STRING (1-4 octets long) } + (OTID value received in BEGIN message) } + Component portion tag: 01101100 + Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 + Message type length: correct number of octets + Destination transaction ID tag: 01001001 + Destination transaction ID length: correct number of octets + Destination transaction ID value: OCTET STRING (1-4 octets long) + (OTID value received in CONTINUE message) + P-Abort cause tag: 01001010 + P-Abort cause length: correct number of octets + P-Abort cause value: incorrect transaction portion 00000011 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|--------|--|--|--------------|--------|--|----------------------------|--------|-----------------|------------------|--------|--|------------------------|--|--|--------|--|--| +| TEST NUMBER: 1.2.2.3 5) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: First Continue Message; Unknown information element present | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message, signalling point A behaves correctly | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that a Continue message with an OTID that is derivable and a DTID that is derivable and assigned, contains a syntax error and is sent to SP A in response to the Begin message | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
=====>
BEGIN =====>
Detect syntax error <===== CONTINUE
ABORT (P) =====>
TR-P-ABORT ind.
<=====

NOTE – If the ABORT message and primitive are not sent, this may be valid behaviour depending on the implementation.

| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | =====> | | | BEGIN | =====> | | Detect syntax error | <===== | CONTINUE | ABORT (P) | =====> | | TR-P-ABORT ind. | | | <===== | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| =====> | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | =====> | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect syntax error | <===== | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (P) | =====> | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| <===== | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send the corrupted Continue message with an extra information element after the DTID information element (eg P-Abort Cause). | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE CONTINUE MESSAGE AT SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: IF THE ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A, WITH CORRECT DTID AND THE CORRECT P-ABORT CAUSE VALUE? (INCORRECT TRANSACTION PORTION) | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: IF THE MESSAGE AND PRIMITIVE ABORT WERE SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Information element tag: unknown (eg. 01101101) +Information element length: correct number of octets +Information element value: OCTET STRING + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: incorrect transaction portion 00000011 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|---|--|--|---------------------|--|-----------------| +| TEST NUMBER: 1.2.2.4 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Subsequent Continue Message; OTID absent | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message after transaction establishment, SP A is able to discard the message | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
>
BEGIN
CONTINUE
TR-CONTINUE ind.
<
Detect error CONTINUE
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | > | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | < | | | Detect error | | CONTINUE | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect error | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a correct Continue message to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send a corrupted Continue message to SP A (OTID not derivable). | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE FIRST CONTINUE MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: VERIFY THAT THE TR-USER AT SP A WAS NOT INFORMED OF THE CORRUPTED CONTINUE MESSAGE. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE CORRUPTED CONTINUE MESSAGE. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK E: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION, PRIOR TO THE CORRUPTED CONTINUE MESSAGE, LEFT IN THE ACTIVE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE (1st) + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE (2nd) + +Message type tag: 01100101 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--|------------|--|---|--------------|----------------------|--|--|--|--|--|-------------------------|--|--|--|---|--|-----------------|--|--|--|---|-----------------|---------------------|--|--|------------------|---|--|------------------------|--|--|--|--|--| +| TEST NUMBER: 1.2.2.4 2) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Subsequent Continue Message; Unknown information element present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message with OTID derivable and DTID derivable and assigned, after transaction establishment, SP A behaves correctly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← BEGIN
TR-BEGIN ind.
TR-CONTINUE req.
→
CONTINUE
← CONTINUE
Detect error
ABORT (P) →
TR-P-ABORT ind.

NOTE – If the ABORT message and primitive are not sent, this may be valid behaviour depending on the implementation.

| | | SP A (TSL) | | SP B (TSL) | | ← | BEGIN | TR-BEGIN ind. | | | | | | TR-CONTINUE req. | | | | → | | CONTINUE | | | | ← | CONTINUE | Detect error | | | ABORT (P) | → | | TR-P-ABORT ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect error | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (P) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a Begin message from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to send a correct Continue message to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send a corrupted Continue message to SP A (extra Information Element after the DTID Information Element). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE FIRST CONTINUE MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: IF THE ABORT WAS SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +##### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE (1st) + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUED (2nd) + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +(OTID value used in BEGIN message) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +Information element tag: unknown (eg. 01101101) +Information element length: correct number of octets +Information element value: OCTET STRING + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: incorrect transaction portion 00000011 + +| | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------|------------|--|------------|----------------------|--|--|--------|--|--|--------------|--|--|----------------------------|---|------------| +| TEST NUMBER: 1.2.2.5 1) | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | +| SUBTITLE: End Message; DTID absent | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted End message, SP A is able to discard the message | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the End message contains a syntax error ( DTID absent) | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
TR-BEGIN req.
=====>
BEGIN
Detect syntax error < END
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | =====> | | | BEGIN | | | Detect syntax error | < | END | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | +| =====> | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | +| Detect syntax error | < | END | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a corrupted End message to SP A.(DTID absent.) | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE MESSAGE AT SP A. | | | | | | | | | | | | | | | | | +| 5. | CHECK C: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE CORRUPTED END MESSAGE? | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION, PRIOR TO THE END MESSAGE, LEFT IN THE INITIATION SENT STATE AT SP A? | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | +| BEGIN
Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)
Component portion tag: 01101100
Component portion length: correct number of octets

END
Message type tag: 01100100
Message type length: correct number of octets
DTID absent
Component portion tag: 01101100
Component portion length: correct number of octets | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------|------------|------------|----------------------|--|--------------------------------------|--|--------------|--------------------------------------------------------------------------------------------------|--|----------------------------|-------------------------------------------------------------------------------------------------|--------------| +| TEST NUMBER: 1.2.2.6 1) | | Sheet: 1 of 1 | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | +| SUBTITLE: Abort Message; DTID absent | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Abort message, SP A is able to discard the message | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that the Abort message contains a syntax error ( DTID absent) | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
TR-BEGIN req.
\xRightarrow{\quad\quad\quad\quad}
BEGIN \xrightarrow{\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad}
Detect syntax error \xleftarrow{\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad} ABORT
| | | SP A (TSL) | SP B (TSL) | TR-BEGIN req. | | $\xRightarrow{\quad\quad\quad\quad}$ | | BEGIN | $\xrightarrow{\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad}$ | | Detect syntax error | $\xleftarrow{\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad}$ | ABORT | +| SP A (TSL) | SP B (TSL) | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | +| $\xRightarrow{\quad\quad\quad\quad}$ | | | | | | | | | | | | | | | +| BEGIN | $\xrightarrow{\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad}$ | | | | | | | | | | | | | | +| Detect syntax error | $\xleftarrow{\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad}$ | ABORT | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a corrupted Abort message to SP A. | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE MESSAGE AT SP A. | | | | | | | | | | | | | | +| 5. | CHECK C: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE CORRUPTED ABORT MESSAGE. | | | | | | | | | | | | | | +| 6. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION, PRIOR TO THE ABORT MESSAGE, LEFT IN THE INITIATION SENT STATE AT SP A? | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | | | | +| BEGIN
Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long)
Component portion tag: 01101100
Component portion length: correct number of octets
ABORT (P)
Message type tag: 01100111
Message type length: correct number of octets
DTID absent
P-Abort cause tag: 01101100
P-Abort cause length: correct number of octets
P-Abort cause value: e.g. incorrect transaction portion 00000011 | | | | | | | | | | | | | | | + +| | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|------------------------------------|---|------------------------| +| TEST NUMBER: 1.2.2.7 1) | | Sheet: 1 of 1 | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | +| SUBTITLE: Unknown Message; OTID not included | | | | | | | | | +| PURPOSE: To verify that on receipt of an Unknown message, signalling point A is able to discard the message | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such that an Unknown message with an OTID that is not derivable is sent to SP A | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (TSL) SP B (TSL)
Detect Unknown message type ← UNKNOWN MESSAGE






| | | SP A (TSL) | | SP B (TSL) | Detect Unknown message type | ← | UNKNOWN MESSAGE | +| SP A (TSL) | | SP B (TSL) | | | | | | | +| Detect Unknown message type | ← | UNKNOWN MESSAGE | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Arrange for SP B to send the Unknown message to SP A. | | | | | | | | +| 2. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THIS EVENT AT SP A. | | | | | | | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE UNKNOWN MESSAGE. | | | | | | | | +| 4. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | +| UNKNOWN MESSAGE
Message type tag: unknown (e.g. 01100110)
Message type length: correct number of octets
OTID absent | | | | | | | | | + +| | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|------------------------------------|--------|------------------------|------------------|--------|--| +| TEST NUMBER: 1.2.2.7 2) | | Sheet: 1 of 1 | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | +| SUBTITLE: Unknown Message; OTID included and DTID not included | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of an Unknown message, signalling point A behaves correctly | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B that an Unknown message with an OTID that is derivable and a DTID that is not derivable or derivable but unassigned is sent to SP A | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
Detect Unknown message type ←————— UNKNOWN MESSAGE
ABORT (P) —————→
| | | SP A (TSL) | | SP B (TSL) | Detect Unknown message type | ←————— | UNKNOWN MESSAGE | ABORT (P) | —————→ | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | +| Detect Unknown message type | ←————— | UNKNOWN MESSAGE | | | | | | | | | | +| ABORT (P) | —————→ | | | | | | | | | | | +| NOTE – If the Abort message is not sent, this may be valid behaviour depending on the implementation. | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | +| 1. | Arrange for SP B to send the Unknown message to SP A. | | | | | | | | | | | +| 2. | CHECK A: IF A P-ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH THE CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | | | | | | | | | | +| 3. | CHECK B: IF THE ABORT WAS SENT, WERE TSL THE STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | +|

UNKNOWN MESSAGE

Message type tag: unknown (e.g. 01100110)

Message type length: correct number of octets

Originating transaction ID tag: 01001000

Originating transaction ID length: correct number of octets

Originating transaction ID value: OCTET STRING (1-4 octets long)

ABORT (P)

Message type tag: 01100111

Message type length: correct number of octets

Destination transaction ID tag: 01001001

Destination transaction ID length: correct number of octets

Destination transaction ID value: OCTET STRING (1-4 octets long)
(OTID value received in UNKNOWN message)

P-Abort cause tag: 01001010

P-Abort cause length: one octet

P-Abort cause value: unrecognized message type 00000000

| | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|----|--|------------------------------------|----|------------------------|------------------|----|--|------------------------|--|--|---|--|--| +| TEST NUMBER: 1.2.2.7 3) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unknown Message; OTID included and DTID included | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of an Unknown message with assigned DTID, SP A is able to behave correctly | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B such than an Unknown message with an OTID that is derivable and a DTID that is derivable and assigned is sent to SP A in response to the Begin message | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
>
BEGIN —>
Detect Unknown message type <— UNKNOWN MESSAGE
ABORT (P) —>
TR-P-ABORT ind.
<

NOTE – If the ABORT message and primitive are not sent, this may be valid behaviour depending on the implementation.

| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | > | | | BEGIN | —> | | Detect Unknown message type | <— | UNKNOWN MESSAGE | ABORT (P) | —> | | TR-P-ABORT ind. | | | < | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | —> | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect Unknown message type | <— | UNKNOWN MESSAGE | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (P) | —> | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B and for SP B to respond with the Unknown message. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IF THE P-ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH THE CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: IF THE ABORT WAS SENT, WAS THE TR-USER AT SP A ADVISED BY A TR-P-ABORT INDICATION PRIMITIVE THAT THIS TRANSACTION HAD BEEN ABORTED? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: IF THE ABORT WAS SENT, WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### UNKNOWN MESSAGE + +Message type tag: unknown (e.g. 01100110) +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in UNKNOWN message) +P-Abort cause tag: 01001010 +P-Abort cause length: one octet +P-Abort cause value: unrecognized message type 00000000 + +| | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------------|------------|--|------------|----------------------------|--------|--------------|------------------|--------|--| +| TEST NUMBER: 1.2.3.1 1) | | Sheet: 1 of 1 | | | | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid encoding | | | | | | | | | | | | +| SUBTITLE: Begin Message type; Invalid tag | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a corrupted Begin message with Invalid tag, signalling point A behaves correctly | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. Arrange the data at SP B that the Begin message contains an Invalid tag | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
Detect syntax error ←————— BEGIN
ABORT (P) —————→

NOTE – If the Abort message is not sent, this may be valid behaviour depending on the implementation.

| | | SP A (TSL) | | SP B (TSL) | Detect syntax error | ←————— | BEGIN | ABORT (P) | —————→ | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | +| Detect syntax error | ←————— | BEGIN | | | | | | | | | | +| ABORT (P) | —————→ | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | +| 1. | Arrange for SP B to send the corrupted Begin message to SP A. | | | | | | | | | | | +| 2. | CHECK A: CHECK THAT THE USER WAS NOT INFORMED OF THE BEGIN MESSAGE. | | | | | | | | | | | +| 3. | CHECK B: WERE THE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | +| 4. | CHECK C: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | +|

BEGIN

Message type tag: 01100010

Message type length: correct number of octets

Invalid tag: e.g. 00100010

Originating transaction ID tag: 01001000

Originating transaction ID length: correct number of octets

Originating transaction ID value: OCTET STRING (1-4 octets long)

ABORT (P)

Message type tag: 01100111

Message type length: correct number of octets

Destination transaction ID tag: 01001001

Destination transaction ID length: correct number of octets

Destination transaction ID value: OCTET STRING (1-4 octets long)
(OTID value received in BEGIN message)

P-Abort cause tag: 01001010

P-Abort cause length: correct number of octets

P-Abort cause value: incorrect transaction portion 00000011

| | | | | | | | | | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.2.3.2 1) | | Sheet: 1 of 2 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid encoding | | | +| SUBTITLE: Continue Message type; Invalid tag | | | +| PURPOSE: To verify that on receipt of a corrupted Continue message with Invalid tag, signalling point A behaves correctly | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state. SP B to respond with a Continue message on receipt of the Begin message. Arrange the data at SP B such that Continue message contains a syntax error (invalid tag) | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)
TR-BEGIN req.

BEGIN
Detect syntax error
ABORT (P)
TR-P-ABORT ind.



—>
<—
—>

SP B (TSL)




CONTINUE



NOTE – If the ABORT message and the primitive are not sent, this may be valid behaviour depending on the implementation.

| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | +| 2. | Arrange for SP B to send the corrupted Continue message to SP A. | | +| 3. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT FROM SP A? | | +| 4. | CHECK B: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE CONTINUE MESSAGE AT SP A. | | +| 5. | CHECK C: IF AN ABORT MESSAGE WAS SENT, WAS IT SENT CORRECTLY FROM SP A WITH CORRECT DTID AND CORRECT P-ABORT CAUSE VALUE? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +##### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Invalid tag: e.g. 00011111 +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in BEGIN message) + +##### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: correct number of octets +P-Abort cause value: incorrect transaction portion 00000011 + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.3.1 1) | | Sheet: 1 of 2 | +| REFERENCE: 3.3.4/Q.774 | | | +| TITLE: Inopportune Messages; Continue message type | | | +| SUBTITLE: Receipt of Continue Message in idle state with unassigned DTID | | | +| PURPOSE: To verify that on receipt of a Continue message with unassigned DTID, signalling point A is able to discard the message and generate an Abort message | | | +| PRE-TEST CONDITIONS: SP A (TSL) to be in the idle state and SP B (TSL) to be in the IR/Active state. Arrange the data at SP B such that a Continue message with an OTID that is derivable and a DTID that is derivable but unassigned is sent to SP A | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
←
CONTINUE
ABORT (P)
→
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send the Continue message with unassigned DTID to SP A. | | +| 2. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE CONTINUE MESSAGE AT SP A. | | +| 3. | CHECK B: WAS THE DTID IN THE ABORT MESSAGE EQUAL TO THE OTID IN THE CONTINUE MESSAGE? | | +| 4. | CHECK C: WAS AN ABORT MESSAGE CORRECTLY SENT FROM SP A WITH A P-ABORT CAUSE VALUE OF UNRECOGNIZED TRANSACTION ID? | | +| 5. | CHECK D: WERE TSL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: one octet +P-Abort cause value: unrecognized transaction ID 00000001 + +| | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|----------------|------------|--|------------|--|--------|-----| +| TEST NUMBER: 1.3.2.1) | | Sheet: 1 of 1 | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | +| TITLE: Inopportune Messages; End Message type | | | | | | | | | +| SUBTITLE: Receipt of End Message in Idle state | | | | | | | | | +| PURPOSE: To verify that on receipt of an End message with unassigned DTID, signalling point A is able to discard the message | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) to be in the idle state and SP B (TSL) to be in the IR/Active state. Arrange the data at SP B such that an End message with a DTID that is derivable but unassigned is sent to SP A | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
←----- END
| | | SP A (TSL) | | SP B (TSL) | | ←----- | END | +| SP A (TSL) | | SP B (TSL) | | | | | | | +| | ←----- | END | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Arrange for SP B to send the End message with unassigned DTID to SP A. | | | | | | | | +| 2. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE END MESSAGE AT SP A. | | | | | | | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE END MESSAGE. | | | | | | | | +| 4. | CHECK C: WERE TSL STATE MACHINES ASSOCIATED WITH THE TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | +|

END

Message type tag: 01100100

Message type length: correct number of octets

Destination transaction ID tag: 01001001

Destination transaction ID length: correct number of octets

Destination transaction ID value: OCTET STRING (1-4 octets long)

Component portion tag: 01101100

Component portion length: correct number of octets

| | | | | | | | | + +| | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------|------------|--|------------|--|---|------------------| +| TEST NUMBER: 1.3.3 1) | | Sheet: 1 of 1 | | | | | | | +| REFERENCE: 3.3.4/Q.774 | | | | | | | | | +| TITLE: Inopportune Messages; Abort Message type | | | | | | | | | +| SUBTITLE: Receipt of Abort message in Idle state | | | | | | | | | +| PURPOSE: To verify that on receipt of an Abort message with unassigned DTID, signalling point A is able to discard the message | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) to be in the idle state and SP B (TSL) to be in the IR/Active state. Arrange the data at SP B such that an Abort message with a DTID that is derivable but unassigned is sent to SP A | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
← ABORT (P)


| | | SP A (TSL) | | SP B (TSL) | | ← | ABORT (P) | +| SP A (TSL) | | SP B (TSL) | | | | | | | +| | ← | ABORT (P) | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Arrange for SP B to send the Abort message with unassigned DTID to SP A. | | | | | | | | +| 2. | CHECK A: VERIFY THAT THE TR-USER WAS NOT INFORMED OF THE ABORT MESSAGE AT SP A. | | | | | | | | +| 3. | CHECK B: VERIFY THAT NO MESSAGES WERE GENERATED BY SP A IN RESPONSE TO THE ABORT MESSAGE. | | | | | | | | +| 4. | CHECK C: WERE ALL STATE MACHINES ASSOCIATED WITH THIS TRANSACTION LEFT IN THE IDLE STATE AT SP A? | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | +| ABORT (P)
Message type tag: 01100111
Message type length: correct number of octets
Destination transaction ID tag: 01001001
Destination transaction ID length: correct number of octets
Destination transaction ID value: OCTET STRING (1-4 octets long)
P-Abort cause tag: 01001010
P-Abort cause length: one octet
P-Abort cause value: INTEGER {0, 1, 2, 3, 4} | | | | | | | | | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 1.4.1 1) | | Sheet: 1 of 2 | +| REFERENCE: 3.3.3.2/Q.774 | | | +| TITLE: Multiple Transaction Encoding; Valid Transaction Encoding | | | +| SUBTITLE: New transaction request during transaction establishment | | | +| PURPOSE: To verify that the signalling point A is able to correctly react to a Begin message during the establishment of another transaction | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)

TR-BEGIN req.

⇒⇒⇒⇒

BEGIN

TR-BEGIN ind.

⇒⇒⇒⇒

TR-END req.

⇒⇒⇒⇒

(Basic)

(end new transaction)

END

TR-END ind.

⇒⇒⇒⇒

SP B (TSL)

←──────────────────────────────────

BEGIN (new transaction)

←──────────────────────────────────

END

| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | +| 2. | Arrange for SP B to send a Begin message to SP A (new transaction). | | +| 3. | Arrange for SP A to respond with an End message to the 2nd Begin message. | | +| 4. | Arrange for SP B to respond with an End message to the 1st Begin message. | | +| 5. | CHECK A: WAS THE FIRST BEGIN MESSAGE CORRECTLY SENT BY SP A? | | +| 6. | CHECK B: WAS THE SECOND BEGIN MESSAGE CORRECTLY RECEIVED BY SP A? | | +| 7. | CHECK C: WAS THE DTID IN THE FIRST END MESSAGE THE SAME AS THE OTID IN THE SECOND BEGIN MESSAGE? | | +| 8. | CHECK D: WAS THE SECOND END MESSAGE CORRECTLY RECEIVED BY SP A? | | +| 9. | CHECK E: WERE TSL STATE MACHINES ASSOCIATED WITH THESE TRANSACTIONS LEFT IN THE IDLE STATE AT SP A? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN (1st) + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) X +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### BEGIN (2nd) + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) Y +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END (1st) + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) Y +(OTID value received in 2nd BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END (2nd) + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) X +(OTID value received in 1st BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------|------------|--|------------|----------------------|--|--|---|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|---|--|--|--|--|--------------------------------|----------------------|--|--|---|--|--|--------------------|--|--|---|--|--|----------------------------------|--|--|------------|--|--|--|--|------------|--------------------|--|--|---|--|--| +| TEST NUMBER: 1.4.1 2) | | Sheet: 1 of 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Multiple Transaction Encoding; Valid Transaction Encoding | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: New transaction request after transaction establishment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to correctly react to a Begin message after the establishment of another transaction | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
>
BEGIN
CONTINUE
TR-CONTINUE ind.
<
BEGIN (new transaction)
TR-BEGIN ind.
<
TR-END req.
>
(Basic)
(end new transaction)
END
END
TR-END ind.
<
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | > | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | < | | | | | BEGIN (new transaction) | TR-BEGIN ind. | | | < | | | TR-END req. | | | > | | | (Basic)
(end new transaction) | | | END | | | | | END | TR-END ind. | | | < | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BEGIN (new transaction) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Basic)
(end new transaction) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------|--|--| +| TEST NUMBER: 1.4.1 2) | | Sheet: 2 of 3 | | | +| TEST DESCRIPTION | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | +| 2. | Arrange for SP B to respond with a Continue message to Begin message. | | | | +| 3. | Arrange for SP B to send a Begin message to SP A (new transaction). | | | | +| 4. | Arrange for SP A to respond with an End message to the 2nd Begin message. | | | | +| 5. | Arrange for SP B to respond with an End message to the 1st Begin message. | | | | +| 6. | CHECK A: WAS THE FIRST BEGIN MESSAGE CORRECTLY SENT BY SP A? | | | | +| 7. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED BY SP A? | | | | +| 8. | CHECK C: WAS THE SECOND BEGIN MESSAGE CORRECTLY RECEIVED BY SP A? | | | | +| 9. | CHECK D: WAS THE DTID IN THE FIRST END MESSAGE THE SAME AS THE OTID IN THE SECOND BEGIN MESSAGE? | | | | +| 10. | CHECK E: WAS THE SECOND END MESSAGE CORRECTLY RECEIVED BY SP A? | | | | +| 11. | CHECK F: WERE TSL STATE MACHINES ASSOCIATED WITH THESE TRANSACTIONS LEFT IN THE IDLE STATE AT SP A? | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | +| BEGIN (1st) | | | | | +| Message type tag: 01100010
Message type length: correct number of octets
Destination transaction ID tag: 01001000
Destination transaction ID length: correct number of octets
Destination transaction ID value: OCTET STRING (1-4 octets long) X
Component portion tag: 01101100
Component portion length: correct number of octets | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) Y +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) X +(OTID value received in 1st BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### BEGIN (2nd) + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) Z +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END (1st) + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) Z +(OTID value received in 2nd BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### END (2nd) + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) X +(OTID value received in 1st BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------|----------------------------------------|--|------------|--------------|-------------------------|--|--|-------------------------|-----------------------------------|------------------------------------------------|-------------------------|--|--|-------------------------|------------|------------------------|--|--| +| TEST NUMBER: 1.4.2 1) | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2/Q.774 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Multiple Transaction Encoding; Inopportune Messages | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Message with unassigned DTID during transaction establishment | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to correctly react to a Continue message with DTID unassigned during the establishment of another transaction | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL)
TR-BEGIN req.
 SP B (TSL)
BEGIN ——————————————————————>
<—————————————————————— CONTINUE (new transaction)
ABORT (P)
TR-P-ABORT ind.
 ——————————————————————>
<—————————————————————— END
TR-END ind.







| | | SP A (TSL)
TR-BEGIN req.
| | SP B (TSL) | BEGIN | ——————————————————————> | | | <—————————————————————— | CONTINUE (new transaction) | ABORT (P)
TR-P-ABORT ind.
| ——————————————————————> | | | <—————————————————————— | END | TR-END ind.
| | | +| SP A (TSL)
TR-BEGIN req.
| | SP B (TSL) | | | | | | | | | | | | | | | | | | | +| BEGIN | ——————————————————————> | | | | | | | | | | | | | | | | | | | | +| | <—————————————————————— | CONTINUE (new transaction) | | | | | | | | | | | | | | | | | | | +| ABORT (P)
TR-P-ABORT ind.
| ——————————————————————> | | | | | | | | | | | | | | | | | | | | +| | <—————————————————————— | END | | | | | | | | | | | | | | | | | | | +| TR-END ind.
| | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to send a Continue message with unassigned DTID to SP A. | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to respond with an End message to the Begin message. | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT BY SP A? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: WAS THE CONTINUE MESSAGE CORRECTLY RECEIVED BY SP A? | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: WAS THE DTID IN THE ABORT MESSAGE THE SAME AS THE OTID IN THE CONTINUE MESSAGE? | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE P-ABORT CAUSE IN THE ABORT MESSAGE THE CORRECT VALUE, (UNRECOGNIZED TRANSACTION ID)? | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK E: WAS THE END MESSAGE CORRECTLY RECEIVED BY SP A? | | | | | | | | | | | | | | | | | | | | +| 9. | CHECK F: WERE TSL STATE MACHINES ASSOCIATED WITH THESE TRANSACTIONS LEFT IN THE IDLE STATE AT SP A? | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### BEGIN + +Message type tag: 01100010 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) X +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### CONTINUE + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) Y +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) Z +(Not equal to X) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) Y +(OTID value received in CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: one octet +P-Abort cause value: 00000001 Unrecognized Transaction ID + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) X +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|------------|--|------------|----------------------|--|--|--|--|--|--------------|--|--|--|--|-----------------|-------------------------|--|--|--|--|--|--|--|-----------------------------------|------------------|--|--|------------------------|--|--|--|--|--|--|--|------------|--------------------|--|--|--|--|--| +| TEST NUMBER: 1.4.2 2) | | Sheet: 1 of 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.3.3.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Multiple Transaction Encoding; Inopportune Messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Message with unassigned DTID after transaction establishment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the signalling point A is able to correctly react to a Continue message with DTID unassigned after the establishment of another transaction | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (TSL) SP B (TSL)
TR-BEGIN req.
BEGIN
CONTINUE
TR-CONTINUE ind.
CONTINUE (new transaction)
ABORT (P)
TR-P-ABORT ind.
END
TR-END ind.
| | | SP A (TSL) | | SP B (TSL) | TR-BEGIN req. | | | | | | BEGIN | | | | | CONTINUE | TR-CONTINUE ind. | | | | | | | | CONTINUE (new transaction) | ABORT (P) | | | TR-P-ABORT ind. | | | | | | | | END | TR-END ind. | | | | | | +| SP A (TSL) | | SP B (TSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE (new transaction) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (P) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | END | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| TEST NUMBER: 1.4.2 2) | Sheet: 2 of 3 | +| TEST DESCRIPTION | | +| 1. | Arrange for SP A to send a Begin message to SP B. | +| 2. | Arrange for SP B to send a Continue message in response to Begin message from SP A. | +| 3. | Arrange for SP B to send a Continue message with unassigned DTID to SP A. | +| 4. | Arrange for SP B to respond with an End message to the Begin message. | +| 5. | CHECK A: WAS THE BEGIN MESSAGE CORRECTLY SENT BY SP A? | +| 6. | CHECK B: WERE THE CONTINUE MESSAGES CORRECTLY RECEIVED BY SP A? | +| 7. | CHECK C: WAS THE DTID IN THE ABORT MESSAGE THE SAME AS THE OTID IN THE SECOND CONTINUE MESSAGE? | +| 8. | CHECK D: WAS THE P-ABORT CAUSE IN THE ABORT MESSAGE THE CORRECT VALUE, (UNRECOGNIZED TRANSACTION ID)? | +| 9 | CHECK E: WAS THE END MESSAGE CORRECTLY RECEIVED BY SP A? | +| 10. | CHECK F: WERE TSL STATE MACHINES ASSOCIATED WITH THESE TRANSACTIONS LEFT IN THE IDLE STATE AT SP A? | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | +| BEGIN | | +| Message type tag: 01100010
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long) W
Component portion tag: 01101100
Component portion length: correct number of octets | | +| CONTINUE (1st) | | +| Message type tag: 01100101
Message type length: correct number of octets
Originating transaction ID tag: 01001000
Originating transaction ID length: correct number of octets
Originating transaction ID value: OCTET STRING (1-4 octets long) X
Destination transaction ID tag: 01001001
Destination transaction ID length: correct number of octets
Destination transaction ID value: OCTET STRING (1-4 octets long) W
(OTID value received in BEGIN message)
Component portion tag: 01101100
Component portion length: correct number of octets | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +###### CONTINUE (2nd) + +Message type tag: 01100101 +Message type length: correct number of octets +Originating transaction ID tag: 01001000 +Originating transaction ID length: correct number of octets +Originating transaction ID value: OCTET STRING (1-4 octets long) Y +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) Z +(Not equal to W) +Component portion tag: 01101100 +Component portion length: correct number of octets + +###### ABORT (P) + +Message type tag: 01100111 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) Y +(OTID value received in 2nd CONTINUE message) +P-Abort cause tag: 01001010 +P-Abort cause length: one octet +P-Abort cause value: 00000001 Unrecognized Transaction ID + +###### END + +Message type tag: 01100100 +Message type length: correct number of octets +Destination transaction ID tag: 01001001 +Destination transaction ID length: correct number of octets +Destination transaction ID value: OCTET STRING (1-4 octets long) W +(OTID value received in BEGIN message) +Component portion tag: 01101100 +Component portion length: correct number of octets + +## 7.2 TC Component Sublayer (CSL) test specification + +### 7.2.1 Guidance on performing component sublayer tests + +- a) For all the tests, the phrase "... component with correct information" in the test description means that the detail values in the indicated component will be syntactically verified against the information listed in the check table for components within messages. +- b) In some tests, a check is required to verify that the Invocation State Machine has returned to idle. One possible procedure to perform this check is to send a Return Result-Last component with the presumed idled Invoke ID. If the IUT (Implementation Under Test) returns a Reject with problem code = "unrecognized Invoke ID," the IUT has passed this check. +- c) For all tests of the CSL, the component has to be carried in a TSL message, e.g. the Invoke component in Test No. 2.1.1.1 is carried from SP A to SP B in a Begin message and the Return Result-Last component is carried in an End message. In fact, if a transaction is first established between SP A and SP B, it is possible to carry the Invoke and the Return Result components in Continue messages. +- d) The assumption used in these CSL tests is that the transaction is kept alive until the last component in the message flow has been delivered to the peer. In case this assumption does not hold for a real application (e.g. because of the use of an Abort or End message), one cannot reach any conclusive verdict on the test. +- e) CSL tests assume that the TSL and SCCP operate correctly. Thus, CSL tests assume that, in particular, components are carried in valid TSL messages within valid transaction states so that abnormal occurrences in the underlying (sub) layer(s) do not occur. +- f) TC-User related information, such as specific operation code and parameters, are not specified. It is up to the test implementers to include application dependent information, where applicable, in order to provoke the expected component flow. +- g) For the dialogue portion tests, the check table sometimes has a "protocol version" shown and sometimes it is not shown. In the main recommendations this information is optional and if not present the default value is "version 1". + +### 7.2.2 Component sublayer test list + +All tests are validation tests + +Tests marked "\*" are compatibility tests + +# 2 Component Sublayer + +## 2.1 Valid Functions + +### 2.1.1 Invoke component, unlinked operations + +#### 2.1.1.1 Class 1 single operation invocation + +- \* 2.1.1.1.1 IUT as sender: receive result + - \* 2.1.1.1.2 IUT as receiver: report result + - \* 2.1.1.1.3 IUT as sender: receive error + - \* 2.1.1.1.4 IUT as receiver: report error + - \* 2.1.1.1.5 IUT as sender: timer expiry +- ###### 2.1.1.2 Class 2 single operation invocation +- \* 2.1.1.2.1 IUT as sender: receive error + - \* 2.1.1.2.2 IUT as sender: timer expiry + +- 2.1.1.3 Class 3 single operation invocation + - \* 2.1.1.3.1 IUT as sender: receive result + - \* 2.1.1.3.2 IUT as sender: timer expiry +- 2.1.1.4 Class 4 single operation invocation + - \* 2.1.1.4.1 IUT as sender +- 2.1.2 Invoke component, linked operations + - 2.1.2.1 Class 1 original operation invocation + - \* 2.1.2.1.1 IUT as sender: receive a linked Class 1 operation invocation, report result + - \* 2.1.2.1.2 IUT as receiver: send a linked Class 1 operation invocation, receive result + - \* 2.1.2.1.3 IUT as sender: receive a linked Class 1 operation invocation, report error + - \* 2.1.2.1.4 IUT as receiver: send a linked Class 1 operation invocation, receive error + - 2.1.2.2 Class 4 original operation invocation + - \* 2.1.2.2.1 IUT as sender: receive a linked Class 2 operation invocation, no outcome + - \* 2.1.2.2.2 IUT as receiver: send a linked Class 2 operation invocation, timer expiry +- 2.1.3 Remote Reject + - 2.1.3.1 Remote Reject by CSL + - 2.1.3.1.1 General problem code + - 2.1.3.1.2 Invoke problem code + - 2.1.3.1.3 Return Result problem code + - 2.1.3.1.4 Return Error problem code + - 2.1.3.2 Remote Reject by TC-User + - 2.1.3.2.1 Invoke problem code + - 2.1.3.2.2 Return Result problem code + - 2.1.3.2.3 Return Error problem code + - 2.1.3.3 Remote Reject with an Invoke problem code + - 2.1.3.3.1 Class 1 operation invocation + - 2.1.3.3.2 Class 2 operation invocation + - 2.1.3.3.3 Class 3 operation invocation + - 2.1.3.3.4 Class 4 operation invocation +- 2.1.4 Reception of component leading to TC-User reject + - 2.1.4.1 Invoke problem + - 2.1.4.1.1 Unrecognized operation code + - 2.1.4.1.2 Unexpected linked operation + - 2.1.4.1.3 Linked response unexpected + - 2.1.4.1.4 Wrong type parameter + - 2.1.4.2 Return Result problem + - 2.1.4.2.1 Wrong type parameter + - 2.1.4.3 Return Error problem + - 2.1.4.3.1 Unrecognized error + - 2.1.4.3.2 Unexpected error + - 2.1.4.3.3 Wrong type parameter +- 2.1.5 Segmentation for Return Result + - 2.1.5.1 Class 1 single operation invocation + - \* 2.1.5.1.1 IUT as sender: receive segmented components + +- \* + - 2.1.5.1.2 IUT as receiver: send segmented components +- 2.1.5.2 Class 3 single operation invocation +- \* + - 2.1.5.2.1 IUT as sender: receive segmented components +- 2.1.6 User Cancel +- 2.1.7 Encoding variations + - 2.1.7.1 Component length definite short + - 2.1.7.2 Component length definite long + - 2.1.7.3 Component length indefinite + - 2.1.7.4 Value variations + - 2.1.7.4.1 Invoke ID + - 2.1.7.4.1.1 Invoke ID = -127 (FFh) + - 2.1.7.4.1.2 Invoke ID = 0 (00h) + - 2.1.7.4.2 Global operation code +- 2.1.8 Multiple components grouping + - 2.1.8.1 Multiple operations invocation; receiving success + - 2.1.8.2 Multiple operations invocation; reporting success + - 2.1.8.3 A malformed component received +- 2.1.9 Dialogue Portion + - 2.1.9.1 Accept application context proposal + - 2.1.9.1.1 Send AARQ in begin message + - 2.1.9.1.2 Accept AARQ and continue dialogue + - 2.1.9.1.3 Accept AARQ and end dialogue + - 2.1.9.2 Propose alternative Application context + - 2.1.9.2.1 Send AARE with alternative + - 2.1.9.2.2 Receive AARE with alternative + - 2.1.9.3 Dialogue refused + - 2.1.9.4 Dialogue abort + - 2.1.9.5 Transport of User Information + - 2.1.9.5.1 Accept User Information in Begin message + - 2.1.9.5.2 Accept User Information in first Continue message + - 2.1.9.5.3 Accept User Information in subsequent Continue message + - 2.1.9.5.4 Accept several User Information elements in Continue message + - 2.1.9.6 Unstructured dialogue + - 2.1.9.7 Dialogue control APDU Version + - 2.1.9.7.1 Structured dialogue, NOT Version 1 + - 2.1.9.7.2 Structured dialogue, Version 1 + - 2.1.9.7.3 Unstructured dialogue, NOT Version 1 + - 2.1.9.7.4 Unstructured dialogue, Version 1 +- 2.2 Syntactically invalid behaviour + - 2.2.1 Invalid values for information elements + - 2.2.1.1 Length of Invoke ID > 1 in Invoke component + - 2.2.1.2 Length of Invoke ID = 0 in Invoke component + - 2.2.2 Invalid structure + - 2.2.2.1 Invoke component + - 2.2.2.1.1 Invoke ID missing + - 2.2.2.1.2 Operation code missing + - 2.2.2.2 Return Result component + - 2.2.2.2.1 Invoke ID missing + - 2.2.2.2.2 Operation code missing while parameters included + - 2.2.2.2.3 Sequence tag missing while parameters included + +- 2.2.2.3 Return Error + - 2.2.2.3.1 Invoke ID missing + - 2.2.2.3.2 Error code missing +- 2.2.2.4 Unknown component type + - 2.2.2.4.1 Invoke ID unrecognizable + - 2.2.2.4.2 invoke ID derivable +- 2.2.2.5 Dialogue Portion + - 2.2.2.5.1 Missing application context in APDU AARQ + - 2.2.2.5.2 Incorrect length + - 2.2.2.5.3 Missing result-source-diagnostic + - 2.2.2.5.4 Missing application context in APDU AUDT + - 2.2.2.5.5 External type without direct reference + - 2.2.2.5.6 Indirect reference in external type + - 2.2.2.5.7 User information without direct reference + - 2.2.2.5.8 Indirect reference in User information +- 2.2.3 Invalid encoding for Invoke component + - 2.2.3.1 Invalid tag + - 2.2.3.2 Wrong component length + - 2.2.3.3 Missing EOC in indefinite form +- 2.3 Inopportune behaviour + - 2.3.1 Inopportune Invoke component + - 2.3.1.1 Invalid linked ID + - 2.3.2 Unrecognized Invoke ID + - 2.3.2.1 Inopportune Return Result-Last component + - 2.3.2.2 Inopportune Return Result Not-Last component + - 2.3.2.3 Inopportune Return Error component + - 2.3.2.4 Inopportune Reject component + - 2.3.3 Unexpected Components + - 2.3.3.1 Return Result-Last for Class 2 + - 2.3.3.2 Return Result-Last for Class 4 + - 2.3.3.3 Return Result Not-Last for Class 2 + - 2.3.3.4 Return Result Not-Last for Class 4 + - 2.3.3.5 Return Error for Class 3 + - 2.3.3.6 Return Error for Class 4 + - 2.3.4 Dialogue Portion, unexpected APDUs + - 2.3.4.1 Begin message with APDU AARE + - 2.3.4.2 Dialogue confirmation with any APDU other than AARE + - 2.3.4.3 Dialogue confirmation with APDU ABRT + - 2.3.4.4 Dialogue continuation with the presence of a Dialogue PDU in the active state + - 2.3.4.5 Unidirectional message with unexpected abstract syntax + - 2.3.4.6 Unexpected dialogue portion in Continue message + - 2.3.4.7 Missing dialogue portion in Continue message + - 2.3.4.8 Begin message with unexpected abstract syntax + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1.1.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | +| SUBTITLE: Class 1 single operation invocation; IUT as sender: receive result | | | | | +| PURPOSE: To verify that a single Class 1 operation can be successfully invoked and the successful completion of the operation can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result-Last component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKE req.
⇒
INVOKE (i)
→
←
SP B (CSL)

RETURN RESULT-LAST (i)
TC-RESULT-L ind.
⇒
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-user) + +##### RETURN RESULT-LAST component in TSL messages from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1.1.2 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | +| SUBTITLE: Class 1 single operation invocation; IUT as receiver: report result | | | | | +| PURPOSE: To verify that a Class 1 operation can be successfully invoked and the successful completion of the operation can be sent | | | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-INVOKE ind.

<=====

TC-RESULT-L req.

===== >

RETURN-RESULT-LAST (i)

←───────────────────────────────────────────────────

SP B (CSL)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single operation invocation from SP B to SP A. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOKE ID IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| 5. | CHECK D: WAS THE OPERATION CODE IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

| | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL messages from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1.1.3 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | +| SUBTITLE: Class 1 single operation invocation; IUT as sender: receive error | | | | | +| PURPOSE: To verify that a Class 1 operation can be successfully invoked and the unsuccessful completion of the operation can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Error component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKED req.

Image: double line arrow pointing right


INVOKE (i)

Image: single line arrow pointing right


Image: single line arrow pointing left

SP B (CSL)

RETURN ERROR (i)
TC-U-ERROR ind.

Image: double line arrow pointing left

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE RETURN ERROR COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL messages from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y (y is a valid error code) + +parameters (provided by the TC-User) + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.1.1.4 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | +| SUBTITLE: Class 1 single operation invocation; IUT as receiver: report error | | | +| PURPOSE: To verify that a Class 1 operation can be successfully invoked and the unsuccessful completion of the operation can be sent | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the TC-User at SP A such that a Return-Error component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL) 
                                             ←                                            INVOKE (i)  TC-U-ERROR ind.  <   TC-RESULT-L req.  >   RETURN-ERROR (i)                            →

Image: Sequence diagram showing INVOKE(i) from SP B to SP A, followed by internal TC-User error indication and result request at SP A, then RETURN-ERROR(i) from SP A to SP B.

 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     B->>A: INVOKE (i)     Note over A: TC-U-ERROR ind.     Note over A: TC-RESULT-L req.     A->>B: RETURN-ERROR (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single operation invocation from SP B to SP A. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 3. | CHECK B: WAS THE RETURN ERROR COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOKE ID IN THE RETURN ERROR COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | +| 5. | CHECK D: WAS THE ERROR CODE IN THE RETURN ERROR COMPONENT VALID? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR COMPONENT in TSL message from SP A to SP B + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y + +parameters (provided by the TC-User) + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1.1.5 | | Sheet: 1 of 1 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | +| SUBTITLE: Class 1 single operation invocation; IUT as sender: timer expiry | | | | | +| PURPOSE: To verify that a Class 1 operation can be successfully invoked and the timer expiry indication can be delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that no component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.

Image: Double-lined arrow pointing right

INVOKE (i) —————→
timer expiry for invocation (i)
TC-L-CANCEL ind. (i)

Image: Double-lined arrow pointing left

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE COMPONENT FLOW AS SHOWN ABOVE? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer)
Operation code tag: 00000010 (local) or 000000110 (global)
Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)
Operation code: x (x represents a valid operation code)
parameters (provided by the TC-User) | | | | | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.1.2.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | +| SUBTITLE: Class 2 single operation invocation; IUT as sender: receive error | | | +| PURPOSE: To verify that a Class 2 operation can be successfully invoked and the failure report can be received and delivered to the TC-User | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Error component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKE req.
=====>
INVOKE (i)


TC-U-ERROR ind.
<===== 
 —————→ ←—————
SP B (CSL)



RETURN ERROR (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single Class 2 operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE RETURN ERROR COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR COMPONENT in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y + +parameters (provided by the TC-User) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|--|--|---------------------------------|--|--|-------------------------|--|--|--|--|--| +| TEST NUMBER: 2.1.1.2.2 | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Class 2 single operation invocation; IUT as sender: timer expiry | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a Class 2 operation can be successfully invoked and the timer expiry indication can be delivered to the TC-User | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that no component will be generated | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
timer expiry for invocation (i)
TC-L-CANCEL ind.
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | | | timer expiry for invocation (i) | | | TC-L-CANCEL ind. | | | | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | +| timer expiry for invocation (i) | | | | | | | | | | | | | | | | | | | | | | | | +| TC-L-CANCEL ind. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a single Class 2 operation invocation from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE COMPONENT FLOW AS SHOWN ABOVE? | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE TC-USER AT SP A INFORMED OF TIMER EXPIRY? | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer)
Operation code tag: 00000010 (local) or 00000110 (global)
Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)
Operation code: x (x represents a valid operation code)
parameters (provided by the TC-User) | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1.3.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | +| SUBTITLE: Class 3 single operation invocation; IUT as sender: receive result | | | | | +| PURPOSE: To verify that a single Class 3 operation can be successfully invoked and the successful report of the operation can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result-Last component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKE req.
=====>
INVOKE (i)
—————→
←—————
SP B (CSL)


RETURN RESULT-LAST (i)
TC-RESULT-L ind.
<=====
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single Class 3 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### **CHECK TABLE FOR COMPONENTS WITHIN MESSAGES** + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1.3.2 | | Sheet: 1 of 1 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | +| SUBTITLE: Class 3 single operation invocation; IUT as sender: timer expiry | | | | | +| PURPOSE: To verify that a Class 3 operation can be successfully invoked and the timer expiry indication can be delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that no component will be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
⇒
INVOKE (i) —————→
timer expiry for invocation (i)
TC-L-CANCEL ind.
⇐
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a Class 3 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE COMPONENT FLOW AS SHOWN ABOVE? | | | | +| 4. | CHECK C: WAS THE TC-USER AT SP A INFORMED OF TIMER EXPIRY? | | | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer)
Operation code tag: 00000010 (local) or 00000110 (global)
Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)
Operation code: x (x represents a valid operation code)
parameters (provided by the TC-User) | | | | | + +| | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|----------| +| TEST NUMBER: 2.1.1.4.1 | | Sheet: 1 of 1 | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | +| TITLE: Valid functions; Invoke component, unlinked operations | | | | | | | +| SUBTITLE: Class 4 single operation invocation; IUT as sender | | | | | | | +| PURPOSE: To verify that a Class 4 operation can be successfully initiated and no response is received. | | | | | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-INVOKE req.

⇒

INVOKE (i)

timer expiry for invocation (i)

TC-L-CANCEL ind.

⇐

SP B (CSL)

→

| | |

SP A (CSL)

TC-INVOKE req.

⇒

INVOKE (i)

timer expiry for invocation (i)

TC-L-CANCEL ind.

⇐

|

SP B (CSL)

| |

→

| +|

SP A (CSL)

TC-INVOKE req.

⇒

INVOKE (i)

timer expiry for invocation (i)

TC-L-CANCEL ind.

⇐

|

SP B (CSL)

| | | | | | +| |

→

| | | | | | +| TEST DESCRIPTION | | | | | | | +| 1. | Initiate a single Class 4 operation invocation from SP A to SP B. | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | +| 3. | CHECK B: WAS THE TC-USER AT SP A INFORMED OF TIMER EXPIRY? | | | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP A to SP B

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

Operation code tag: 00000010 (local) or 00000110 (global)

Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)

Operation code: x (x represents a valid operation code)

parameters (provided by the TC-User)

| | | | | | | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.2.1.1 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, Linked operations | | | +| SUBTITLE: Class 1 original operation invocation; IUT as sender: receive a linked Class 1 operation invocation, report result | | | +| PURPOSE: To verify that a linked Class 1 operation can be successfully received and the successful completion of the original operation can be performed | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a linked Invoke component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-INVOKE req.

⇒⇒⇒

INVOKE (i)

⇒

TC-INVOKE ind.

⇒⇒⇒

TC-RESULT-L req.

⇒⇒⇒

RETURN-RESULT-LAST (j)

⇒

TC-RESULT-L ind.

⇒⇒⇒

SP B (CSL)

⇒

INVOKE (j, i)

⇒

RETURN-RESULT-LAST (i)

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a linked operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS A LINKED INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 5. | CHECK D: WAS THE INVOKE ID IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT SENT BY SP B ? | | +| 6. | CHECK E: WAS THE OPERATION CODE IN THE RETURN RESULT-LAST COMPONENT SENT BY SP A THE SAME AS THE ONE IN THE INVOKE COMPONENT SENT BY SP B ? | | +| 7. | CHECK F: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 8. | CHECK G: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in TSL message sent by SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in 2nd TSL message sent by SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) (see Note) + +Operation code: y (see Note) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.2.1.2 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, Linked operations | | | +| SUBTITLE: Class 1 original operation invocation; IUT as receiver: send a linked Class 1 operation invocation, receive result | | | +| PURPOSE: To verify that a linked Class 1 operation can be successfully invoked and the successful completion of the original operation can be performed | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component which will invoke a linked operation | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
SP B (CSL)
TC-INVOKE ind.
<=====
←-----
INVOKE (i)
TC-INVOKE req.
=====>
→-----
INVOKE (j, i)
RETURN-RESULT-LAST (i)
←-----
RETURN RESULT-LAST (j)
TC-RESULT-L ind.
<=====
←-----
RETURN-RESULT-LAST (j)
TC-RESULT-L req.
=====>
→-----
RETURN-RESULT-LAST (i)
| | | +| TEST DESCRIPTION | | | +| 1.
2.
3.
4.
5.
6.
7.
8.
9. | Initiate a linked operation invocation from SP B to SP A.
CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A?
CHECK B: WAS A LINKED INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A?
CHECK C: WAS THE LINKED ID THE SAME AS THE ORIGINAL INVOKE ID SENT BY SP B?
CHECK D: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A?
CHECK E: WAS THE SECOND RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A?
CHECK F: WAS THE INVOKE ID IN THE SECOND RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE ORIGINAL INVOKE COMPONENT SENT BY SP B?
CHECK G: WAS THE OPERATION CODE IN THE SECOND RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE ORIGINAL INVOKE COMPONENT ?
CHECK H: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +#### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in initial TSL message from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in TSL message sent from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message sent by SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) (see Note) + +Operation code: y (see Note) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message sent by SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-------------------------------| +| TEST NUMBER: 2.1.2.1.3 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, Linked operations | | | +| SUBTITLE: Class 1 original operation invocation; IUT as sender: receive a linked Class 1 operation invocation, report error | | | +| PURPOSE: To verify that a linked Class 1 operation can be successfully received and the reporting error will not impact the completion of the original operation | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a linked invocation can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW: | | | +| SP A (CSL) | | SP B (CSL) | +| TC-INVOKE req. | | | +| ⇒⇒⇒ | | | +| INVOKE (i) | → | | +| | ← | INVOKE (j, i) | +| TC-INVOKE ind. | | | +| ⇒⇒⇒ | | | +| TC-U-ERROR req. | | | +| ⇒⇒⇒ | | | +| RETURN-ERROR (j) | → | | +| | ← | RETURN-RESULT-LAST (i) | +| TC-RESULT-L ind. | | | +| ⇒⇒⇒ | | | +| TEST DESCRIPTION | | | +| 1. | Initiate a linked operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS A LINKED INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE RETURN ERROR COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 5. | CHECK D: WAS THE INVOKE ID IN THE RETURN ERROR COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT SENT BY SP B ? | | +| 6. | CHECK E: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 7. | CHECK F: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in the TSL messages sent by SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in the TSL message sent by SP A + +Component type tag: 10100010 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +#### **CHECK TABLE FOR COMPONENTS WITHIN MESSAGES** + +Error code tag: 00000010 (local) or 00000110 (global) (see Note) + +Error code length: correct number of octets (e.g. 00000001 if z is one octet long) (see Note) + +Error code: z (see Note) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in the TSL message sent by SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.2.1.4 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, Linked operations | | | +| SUBTITLE: Class 1 original operation invocation; IUT as receiver: send a linked Class 1 operation invocation, receive error | | | +| PURPOSE: To verify that a linked Class 1 operation can be successfully invoked and the receiving error will not impact the completion of the original operation | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW
SP A (CSL) SP B (CSL)

Image: Sequence diagram showing message flow between SP A and SP B. SP B sends INVOKE (i) to SP A. SP A processes TC-INVOKE ind. and TC-INVOKE req., then sends a linked INVOKE (j, i) back to SP B. SP B responds with RETURN ERROR (j). SP A processes TC-U-ERROR ind. and TC-RESULT-L req., then sends RETURN-RESULT-LAST (i) to SP B.

 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note right of B: INVOKE (i)     B->>A:      Note left of A: TC-INVOKE ind.     Note left of A: TC-INVOKE req.     Note left of A: INVOKE (j, i)     A->>B:      Note right of B: RETURN ERROR (j)     B->>A:      Note left of A: TC-U-ERROR ind.     Note left of A: TC-RESULT-L req.     Note left of A: RETURN-RESULT-LAST (i)     A->>B:
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a linked operation invocation from SP B to SP A. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 3. | CHECK B: WAS A LINKED INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 4. | CHECK C: WAS THE LINKED ID THE SAME AS THE ORIGINAL INVOKE ID SENT BY SP B? | | +| 5. | CHECK D: WAS THE RETURN ERROR COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 6. | CHECK E: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 7. | CHECK F: WAS THE INVOKE ID IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE ORIGINAL INVOKE COMPONENT SENT BY SP B ? | | +| 8. | CHECK G: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +#### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in TSL messages by SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message sent by SP B + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if z is one octet long) + +Error code: z + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message sent by SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.2.2.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Invoke component, Linked operations | | | +| SUBTITLE: Class 4 original operation invocation; IUT as sender: receive a linked Class 2 operation invocation, no outcome | | | +| PURPOSE: To verify that a linked Class 2 operation can be successfully received and the successful completion of the original Class 4 operation can be performed | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains a Class 4 Invoke component
2) Arrange the data at SP B such that a linked Class 2 Invoke component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKE req.
==========>

INVOKE (i)


TC-INVOKE ind.
<==========

timer expiry for invocation (i)

TC-L-CANCEL ind.
<==========
>

<
SP B (CSL)




INVOKE (j, i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a linked operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS A LINKED INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in TSL message sent by SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + + + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +INVOKE component in TSL message sent from SP A to SP B + +Component type tag: 10100010 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.3.1.1 | | Sheet: 1 of 2 | | | +| REFERENCES: 3.2.1/Q.774; 3.7.1/Q.772 | | | | | +| TITLE: Valid functions; Remote Reject | | | | | +| SUBTITLE: Remote Reject by CSL; General problem code | | | | | +| PURPOSE: To verify that a remote rejection by CSL with general problem code can be delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Reject component with general problem code can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKED req.
=====>
INVOKE (i)
----->
<-----
TC-R-REJECT ind.
<=====
SP B (CSL)



REJECT (i)
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single Class 1 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) +Operation code: x (x represents a valid operation code) +parameters (provided by the TC-User) + +REJECT component in TSL message sent from SP B to SP A + +Component type tag: 10100100 (REJECT) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Problem code tag: 10000000 (General Problem) +Problem code length: 00000001 +Problem code: 00000000 (unrecognized component) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------|------------|--|------------|--|---|-------------------|-----------------------|--|--|---|--|--|-----------------------|--|--|----|--|--|---------------------|----|--|--|---|-------------------|-------------------------|--|--|---|--|--| +| TEST NUMBER: 2.1.3.1.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCES: 3.2.1/Q.774; 3.7.2/Q.772 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Remote Reject | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Remote Reject by CSL; Invoke problem code | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the remote rejection by CSL with Invoke problem code can be received and delivered to the TC-User | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP B such that a Reject component with Invoke problem code can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
← INVOKE (i)
TC-INVOKE ind.
<
TC-INVOKE req.
─>
INVOKE (j,i) ─>
← REJECT (j)
TC-R-REJECT ind.
<
| | | SP A (CSL) | | SP B (CSL) | | ← | INVOKE (i) | TC-INVOKE ind. | | | < | | | TC-INVOKE req. | | | ─> | | | INVOKE (j,i) | ─> | | | ← | REJECT (j) | TC-R-REJECT ind. | | | < | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (j,i) | ─> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | REJECT (j) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-R-REJECT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a linked Class 1 operation invocation from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents an operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +##### REJECT component in TSL messages from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000101 (unrecognized linked ID) + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------------------------------------------------| +| TEST NUMBER: 2.1.3.1.3 | | Sheet: 1 of 2 | | | | +| REFERENCE: 3.2.1/Q.774; 3.7.3/Q.772 | | | | | | +| TITLE: Valid functions; Remote Reject | | | | | | +| SUBTITLE: Remote Reject by CSL; Return Result problem code | | | | | | +| PURPOSE: To verify that a single Class 1 operation can be successfully invoked and the remote rejection can be received and delivered to the TC-User | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)


TC-INVOKE ind.
<

TC-RESULT-L req.
>

RETURN RESULT-LAST (i)


TC-R-REJECT ind.
<

←






→
← 		SP B (CSL)
INVOKE (i)








REJECT (i)
| | | SP A (CSL)


TC-INVOKE ind.
<

TC-RESULT-L req.
>

RETURN RESULT-LAST (i)


TC-R-REJECT ind.
< |

←






→
← | SP B (CSL)
INVOKE (i)








REJECT (i) | +| SP A (CSL)


TC-INVOKE ind.
<

TC-RESULT-L req.
>

RETURN RESULT-LAST (i)


TC-R-REJECT ind.
< |

←






→
← | SP B (CSL)
INVOKE (i)








REJECT (i) | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Initiate a single Class 1 operation invocation from SP B to SP A. | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +Parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized Invoke ID) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------|------------|--|------------|--|---|-------------------|-----------------------|--|--|---|--|--|------------------------|--|--|--|--|--|-------------------------|---|--|--|---|-------------------|-------------------------|--|--|---|--|--| +| TEST NUMBER: 2.1.3.1.4 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774; 3.7.4/Q.772 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Remote Reject | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Remote Reject by CSL; Return Error problem code | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a single Class 1 operation can be successfully invoked and the remote rejection can be received and delivered to the TC-User | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
← INVOKE (i)
TC-INVOKE ind.
<
TC-U-ERROR req.
RETURN ERROR (i) →
← REJECT (i)
TC-R-REJECT ind.
<
| | | SP A (CSL) | | SP B (CSL) | | ← | INVOKE (i) | TC-INVOKE ind. | | | < | | | TC-U-ERROR req. | | | | | | RETURN ERROR (i) | → | | | ← | REJECT (i) | TC-R-REJECT ind. | | | < | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-ERROR req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RETURN ERROR (i) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | REJECT (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-R-REJECT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a single Class 1 operation invocation from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Component portion in TSL messages

  • Component portion tag: 01101100
  • Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

  • Component type tag: 10100001 (INVOKE)
  • Component length: correct number of octets
  • Invoke ID tag: 00000010
  • Invoke ID length: 00000001 (one octet)
  • Invoke ID: i (i represents an integer)
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) +Operation code: x (x represents a valid operation code) +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP A to SP B + +Component type tag: 10100011 (RETURN ERROR) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Error code tag: 00000010 (local) or 00000110 (global) +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) +Error code: y +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Problem code tag: 10000011 (RETURN ERROR) +Problem code length: 00000001 +Problem code: 00000001 (unrecognized Invoke ID) + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.3.2.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774; 3.7.2/Q.772 | | | | | +| TITLE: Valid functions; Remote Reject | | | | | +| SUBTITLE: Remote Reject by TC-User; Invoke problem code | | | | | +| PURPOSE: To verify that the remote rejection by TC-User with Invoked problem code can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKE req.
=====>
INVOKE (i)


TC-U-REJECT ind.
<=====
→
←
SP B (CSL)



REJECT (i)
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single Class 1 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents an operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized Invoke ID) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------|------------|--|------------|--|---|-------------------|----------------------------|--|--|-----------------------------|--|--|-------------------------------|--|--|--|---|-------------------|------------------------------|--|--| +| TEST NUMBER: 2.1.3.2.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774; 3.7.3/Q.772 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Remote Reject | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Remote Reject by TC-User; Return Result problem code | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the remote rejection by TC-User with Return Result problem code can be received and delivered to the TC-User | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP B such that a Reject component with Return Result problem code can be generated | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
← INVOKE (i)
TC-INVOKE ind.
<
TC-RESULT-L req.
RETURN RESULT-LAST (i)
← REJECT (i)
TC-U-REJECT ind.
<
| | | SP A (CSL) | | SP B (CSL) | | ← | INVOKE (i) | TC-INVOKE ind.
< | | | TC-RESULT-L req.
| | | RETURN RESULT-LAST (i) | | | | ← | REJECT (i) | TC-U-REJECT ind.
< | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| | ← | INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE ind.
< | | | | | | | | | | | | | | | | | | | | | | | | +| TC-RESULT-L req.
| | | | | | | | | | | | | | | | | | | | | | | | +| RETURN RESULT-LAST (i) | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | REJECT (i) | | | | | | | | | | | | | | | | | | | | | | +| TC-U-REJECT ind.
< | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a single Class 1 operation invocation from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents an operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.3.2.3 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774; 3.7.4/Q.772 | | | | | +| TITLE: Valid functions; Remote Reject | | | | | +| SUBTITLE: Remote Reject by TC-User; Return Error problem code | | | | | +| PURPOSE: To verify that the remote rejection by TC-User with Return Error problem code can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP B such that a Reject component with Return Error problem code can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)

TC-INVOKED ind.
<=====
←-----
SP B (CSL)
INVOKE (i)
TC-U-ERROR req.
=====
→-----
RETURN ERROR (i)
RETURN ERROR (i)
←-----
REJECT (i)
TC-U-REJECT ind.
<=====
→-----
REJECT (i)
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single Class 1 operation invocation from SP B to SP A. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents an operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP A to SP B + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000011 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000010 (unrecognized error) + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.3.3.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Remote Reject | | | +| SUBTITLE: Remote Reject with an Invoke problem code; Class 1 operation invocation | | | +| PURPOSE: To verify that a single Class 1 operation can be successfully invoked and the remote rejection can be received and delivered to the TC-User | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 SP A (CSL)                                     SP B (CSL) TC-INVOKE req.  ===========>   INVOKE (i) --------------------------------->               <--------------------------------- REJECT (i)  TC-U-REJECT ind.  <===========
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single Class 1 operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.3.3.2 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Remote Reject | | | | | +| SUBTITLE: Remote Reject with an Invoke problem code; Class 2 operation invocation | | | | | +| PURPOSE: To verify that a single Class 2 operation can be successfully invoked and the remote rejection can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKED req.
=====>
INVOKE (i)
—————→
←—————
SP B (CSL)

REJECT (i)
TC-U-REJECT ind.
<=====
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single Class 2 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.3.3.3 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Valid functions; Remote Reject | | | | | +| SUBTITLE: Remote Reject with an Invoke problem code; Class 3 operation invocation | | | | | +| PURPOSE: To verify that a single Class 3 operation can be successfully invoked and the remote rejection can be received and delivered to the TC-User | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKES req.
=====>
INVOKE (i)


TC-U-REJECT ind.
<=====
—————→
←—————
SP B (CSL)



REJECT (i)
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single Class 3 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents an operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.3.3.4 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Remote Reject | | | +| SUBTITLE: Remote Reject with an Invoke problem code; Class 4 operation invocation | | | +| PURPOSE: To verify that a single Class 4 operation can be successfully invoked and the remote rejection can be received and delivered to the TC-User | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Reject component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)
TC-INVOKE req.
=====>
INVOKE (i)


—————→
←—————
SP B (CSL)


REJECT (i)
TC-U-REJECT ind.
<=====
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single Class 4 operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP B to SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.4.1.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.2.2/Q.774 | | | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | | | +| SUBTITLE: Invoke problem; Unrecognized operation code | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be performed | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with an error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

SP B (CSL)

TC-INVOKE ind.

<=====

TC-U-REJECT req.

>=====

REJECT (i)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with an unrecognized operation code. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

| | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents an invalid operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message sent from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (INVOKE problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (unrecognized operation) + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.4.1.2 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | +| SUBTITLE: Invoke problem; Unexpected linked operation | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an unexpected linked operation and without affecting the original invocation. | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that an Invoke with a linked ID is contained in an appropriate TSL message | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)

TC-INVOKE req.

INVOKE (i)

INVOKE (j, i)
TC-INVOKE ind.
TC-U-REJECT req.

REJECT (j)

RETURN RESULT-LAST (i)
TC-RESULT-L ind.
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate an unlinked operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS A LINKED INVOKE COMPONENT PASSED TO THE TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 5. | CHECK D: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE INVOKE ID IN THE INVOKE COMPONENT SENT BY SP B? | | +| 6. | CHECK E: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### INVOKE component in the TSL message sent by SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i (i is an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents an operation code not linked to x) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message sent by SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000111 (unexpected linked operation) + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-------------------------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|--|--|--|--|----------------------|-----------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-------------------|--|--|--|--|-------------------------------|-------------------------|--|--|--|--|--| +| TEST NUMBER: 2.1.4.1.3 | | Sheet: 1 of 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Invoke problem; Linked response unexpected | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an unexpected linked response can be rejected | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component which will invoke a linked operation
2) Arrange the data at SP B such that a linked response contains at least one parameter which is not associated with the outcome of the operation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
INVOKE (j, i)
TC-INVOKE ind.
TC-U-REJECT req.
REJECT (j)
RETURN RESULT-LAST (i)
TC-RESULT-L ind.
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | | | | | INVOKE (j, i) | TC-INVOKE ind. | | | | | | TC-U-REJECT req. | | | | | | REJECT (j) | | | | | RETURN RESULT-LAST (i) | TC-RESULT-L ind. | | | | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVOKE (j, i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-REJECT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (j) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RETURN RESULT-LAST (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-RESULT-L ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate an operation invocation from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS A LINKED INVOKE COMPONENT PASSED TO THE TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK E: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +#### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code that does not allow any linked operation) + +parameters (provided by the TC-User) + +##### INVOKE component in the TSL message sent from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: j (j represents an integer) + +Linked ID tag: 10000000 + +Linked ID length: 00000001 (one octet) + +Linked ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Operation code: y (y represents a valid operation code) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message sent by SP A + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: 00000111 (linked response unexpected) + +RETURN RESULT-LAST component in TSL message by SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.4.1.4 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.2.2/Q.774 | | | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | | | +| SUBTITLE: Invoke problem; Wrong type parameter | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be performed | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with an error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

SP B (CSL)

TC-INVOKE ind.

<=====

TC-U-REJECT req.

>=====

REJECT (i)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with a wrong type parameter included. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

| | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User, including at least one parameter which is not one of those associated with the operation) + +REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (Invoke problem type) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|--|--|--|--|-------------------------------|-------------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-------------------|--|--| +| TEST NUMBER: 2.1.4.2.1 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Result problem; Wrong type parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an invalid operation code included in the Return Result-Last component | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component for Class 1 or 3
2) Arrange the data at SP B such that a Return Result-Last with an invalid operation code is generated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
RETURN RESULT-LAST (i)
TC-RESULT-L ind.
TC-U-REJECT req.
REJECT (i)

| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | | | | | RETURN RESULT-LAST (i) | TC-RESULT-L ind. | | | | | | TC-U-REJECT req. | | | | | | REJECT (i) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RETURN RESULT-LAST (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-RESULT-L ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-REJECT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate an operation invocation from SP A to SP B.
Generate a response from SP B to SP A with a valid Invoke ID but a different operation code. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) (see Note) + +Operation code: y (y is different from x) (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000010 (wrong type parameter) + +NOTE – Omitted when no parameter is present. + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.4.3.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | +| SUBTITLE: Return Error problem; Unrecognized error | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an unrecognized error code included in the Return Error component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component of Class 1
2) Arrange the data at SP B such that a Return Error with an invalid error code is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     B->>A: RETURN ERROR (i)     Note over A: TC-U-ERROR ind.     Note over A: TC-U-REJECT req.     A->>B: REJECT (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate A Class 1 operation invocation from SP A to SP B.
Generate an unsuccessful response from SP B to SP A with a valid Invoke ID but an invalid error code for this operation. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE RETURN ERROR COMPONENT PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y (y is an invalid error code for this operation) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000011 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000010 (unrecognized error) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|---|--|--|---|-------------------------|------------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-------------------|---|--| +| TEST NUMBER: 2.1.4.3.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Error problem; Unexpected error | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an unexpected error code included in the Return Error component | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component of Class 1
2) Arrange the data at SP B such that a Return Error with an unexpected error code is generated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL) 
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     B->>A: RETURN ERROR (i)     Note over A: TC-U-ERROR ind.     Note over A: TC-U-REJECT req.     A->>B: REJECT (i)
SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i) →
← RETURN ERROR (i)
TC-U-ERROR ind.
TC-U-REJECT req.
REJECT (i) →
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | → | | | ← | RETURN ERROR (i) | TC-U-ERROR ind. | | | | | | TC-U-REJECT req. | | | | | | REJECT (i) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | RETURN ERROR (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-ERROR ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-REJECT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a Class 1 operation invocation from SP A to SP B.
Generate an unsuccessful response from SP B to SP A with a valid Invoke ID but an unexpected error code for this operation. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE RETURN ERROR COMPONENT PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y (y is an error code that is not one of those which the invoked operation may report) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000011 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000011 (unexpected error) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|--|--|--|--|-------------------------|------------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|-------------------|--|--| +| TEST NUMBER: 2.1.4.3.3 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Reception of component leading to TC-User reject | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Error problem; Wrong type parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to a wrong type parameter included in the Return Error component | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component of Class 1
2) Arrange the data at SP B such that a Return Error with a wrong type parameter is generated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
RETURN ERROR (i)
TC-U-ERROR ind.
TC-U-REJECT req.
REJECT (i)
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | | | | | RETURN ERROR (i) | TC-U-ERROR ind. | | | | | | TC-U-REJECT req. | | | | | | REJECT (i) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RETURN ERROR (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-ERROR ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-U-REJECT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a Class 1 operation invocation from SP A to SP B.
Generate an unsuccessful response from SP B to SP A with a valid Invoke ID but a wrong type parameter for this operation. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE RETURN ERROR COMPONENT PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y (y is a valid error code for this operation) + +parameters (provided by the TC-User, including at least one parameter tag which is not one of those associated with the outcome of the operation) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000011 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000100 (wrong type parameter) + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.5.1.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Segmentation for Return Result | | | +| SUBTITLE: Class 1 single operation invocation; IUT as sender: receive segmented components | | | +| PURPOSE: To verify that a single Class 1 operation can be completed by receiving segmented Return Result components | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result Not-Last component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL) 
 TC-INVOKE req. =====> INVOKE (i) ---------------------------->             <---------------------------- RETURN RESULT NOT-                                          LAST (i) TC-RESULT-NL ind. <=========             <---------------------------- RETURN RESULT-LAST (i) TC-RESULT-L ind. <=========

Image: Sequence diagram showing INVOKE from SP A to SP B, followed by RETURN RESULT NOT-LAST and RETURN RESULT-LAST from SP B to SP A.

 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     B->>A: RETURN RESULT NOT-LAST (i)     Note over A: TC-RESULT-NL ind.     B->>A: RETURN RESULT-LAST (i)     Note over A: TC-RESULT-L ind.
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE RETURN RESULT NOT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------------|------------|--|------------|---------------------------|-------|-----------------------|---|--|--|--------------------------|--|--|---|--|--|---------------------------------------|---|--|-------------------------|--|--|---|--|--|-------------------------------|---|--| +| TEST NUMBER: 2.1.5.1.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Segmentation for Return Result | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Class 1 single operation invocation; IUT as receiver: send segmented components | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a single Class 1 operation can be completed by sending segmented Return Result components | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the TC-User stimulus at SP A such that a Return Result Not-Last component can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)

TC-INVOKE ind.
←
INVOKE (i)
<
TC-RESULT-NL req.
>
RETURN RESULT
NOT-LAST (i)		 →
TC-RESULT-L req.
>
RETURN RESULT-LAST (i) →
| | | SP A (CSL) | | SP B (CSL) |
TC-INVOKE ind. |
← |
INVOKE (i) | < | | | TC-RESULT-NL req. | | | > | | | RETURN RESULT
NOT-LAST (i) | → | | TC-RESULT-L req. | | | > | | | RETURN RESULT-LAST (i) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
TC-INVOKE ind. |
← |
INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-RESULT-NL req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RETURN RESULT
NOT-LAST (i) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-RESULT-L req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RETURN RESULT-LAST (i) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a single operation invocation from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE RETURN RESULT NOT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### RETURN RESULT LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.5.2.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions; Segmentation for Return Result | | | +| SUBTITLE: Class 3 single operation invocation; IUT as sender: Receive segmented components | | | +| PURPOSE: To verify that a single Class 3 operation can be completed by receiving segmented Return Result components | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result Not-Last component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
>
<
RETURN RESULT
NOT-LAST (i)
TC-RESULT-NL ind.
<
RETURN RESULT-LAST (i)
TC-RESULT-L ind.
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single Class 3 operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE RETURN RESULT NOT-LAST COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A ? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.6 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Valid functions | | | +| SUBTITLE: User Cancel | | | +| PURPOSE: To verify that an operation invocation can be canceled by TC-User | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result-Last component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     Note over A: TC-U-CANCEL req.     B-->>A: RETURN-RESULT-LAST (i)     Note over A: TC-L-REJECT ind.     A->>B: REJECT (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single Class 1 operation invocation from SP A to SP B.
Arrange TC-User to cancel the operation immediately after the Invoke component is sent. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 4. | CHECK C: WAS THE COMPONENT FLOW AS SHOWN ABOVE? | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized invoke ID) + +NOTE – Omitted when no parameter is present. + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.7.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.3/Q.773 | | | +| TITLE: Valid functions; Encoding variations | | | +| SUBTITLE: Component length definite short | | | +| PURPOSE: To verify that a component portion with a definite short form can be accepted | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP A such that a Return Result-Last component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
SP B (CSL)
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note right of B: INVOKE (i)     B->>A:      Note left of A: TC-INVOKE ind.     Note left of A: <==========     Note left of A: TC-RESULT-L req.     Note left of A: ==========>     Note left of A: RETURN RESULT-LAST (i)     A->>B:

Image: Diagram showing message flow between SP A and SP B. An arrow points from SP B to SP A for INVOKE (i). Below, arrows indicate TC-INVOKE indication and TC-RESULT-L request at SP A. Finally, an arrow points from SP A to SP B for RETURN RESULT-LAST (i).

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 1 or 3 operation invocation from SP B to SP A. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets (definite short form)
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100011 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.7.2 | | Sheet: 1 of 2 | +| REFERENCE: 3.3/Q.773 | | | +| TITLE: Valid functions; Encoding variations | | | +| SUBTITLE: Component length definite long | | | +| PURPOSE: To verify that a component portion with a definite long form can be accepted | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP A such that a Return Result-Last component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over B: INVOKE (i)     B->>A:      Note over A: TC-INVOKE ind.     Note over A: TC-RESULT-L req.     A->>B: RETURN RESULT-LAST (i)
SP A (CSL)

TC-INVOKE ind.
<
SP B (CSL)
INVOKE (i)

←


TC-RESULT-L req.
>

→
RETURN RESULT-LAST (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 1 or 3 operation invocation from SP B to SP A. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets (definite long)
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00000010 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.7.3 | | Sheet: 1 of 2 | +| REFERENCE: 3.3/Q.773 | | | +| TITLE: Valid functions; Encoding variations | | | +| SUBTITLE: Component length indefinite | | | +| PURPOSE: To verify that a component portion with a indefinite form can be accepted | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component
2) Arrange the data at SP A such that a Return Result-Last component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL) 
 sequenceDiagram     Note right of SP B (CSL): INVOKE (i)     SP B (CSL) ->> SP A (CSL):      Note left of SP A (CSL): TC-INVOKE ind.     Note left of SP A (CSL):       Note left of SP A (CSL): TC-RESULT-L req.     Note left of SP A (CSL):       SP A (CSL) ->> SP B (CSL): RETURN RESULT-LAST (i)

Image: Diagram showing message flow between SP A and SP B. SP B sends INVOKE (i) to SP A. SP A processes TC-INVOKE ind. and TC-RESULT-L req., then sends RETURN RESULT-LAST (i) back to SP B.

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 1 or 3 operation invocation from SP B to SP A. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets (indefinite form)
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +EOC Tag: 00000000 + +EOC Length: 00000000 + +RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.7.4.1.1 | | Sheet: 1 of 2 | +| REFERENCE: 6.2/Q.773 | | | +| TITLE: Valid functions; Encoding variations | | | +| SUBTITLE: Value variations; Invoke ID; Invoke ID = -127 (FFh) | | | +| PURPOSE: To verify that the IUT (SP A) is able to deal with correct encoding of component ID (upper value) | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)


TC-INVOKE ind.

<


TC-RESULT-L req.

>

RETURN RESULT-LAST (i)

←




→

SP B (CSL)

INVOKE (i)

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single operation invocation from SP B to SP A with Invoke ID set to 11111111. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOKE ID IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | +| 5. | CHECK D: WAS THE OPERATION CODE IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +|

Component portion in TSL messages

  • Component portion tag: 01101100
  • Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

  • Component type tag: 10100001 (INVOKE)
  • Component length: correct number of octets
  • Invoke ID tag: 00000010
  • Invoke ID length: 00000001 (one octet)
  • Invoke ID: 11111111 (FFh)
| | | + +#### **CHECK TABLE FOR COMPONENTS WITHIN MESSAGES** + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: 11111111 (FFh) + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.7.4.1.2 | | Sheet: 1 of 2 | | | +| REFERENCE: 6.2/Q.773 | | | | | +| TITLE: Valid functions; Encoding variations | | | | | +| SUBTITLE: Value variations; Invoke ID; Invoke ID = 0 (00h) | | | | | +| PURPOSE: To verify that the IUT (SP A) is able to deal with correct encoding of component ID (lower value) | | | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-INVOKE ind.

<=====

TC-RESULT-L req.

>=====

RETURN RESULT-LAST (i)

←───────────────────────────────────────────────────

SP B (CSL)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single operation invocation from SP B to SP A with Invoke ID set to 0. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION PASSED TO TC-USER BY SP A? | | | | +| 3. | CHECK B: WAS THE RETURN RESULT-LAST COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOKE ID IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| 5. | CHECK D: WAS THE OPERATION CODE IN THE RETURN RESULT-LAST COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: 0

| | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: 0 + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.7.4.2 | | Sheet: 1 of 2 | | | +| REFERENCE: 6.3/Q.773 | | | | | +| TITLE: Valid functions; Encoding variations | | | | | +| SUBTITLE: Value variations; Global operation code | | | | | +| PURPOSE: To verify that a global operation code is correctly decoded by TCAP | | | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with a global operation code. The global value does not correspond to a supported operation | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)

Image: Sequence diagram showing message flow from SP B to SP A. SP B sends an INVOKE (i) to SP A. SP A responds with TC-INVOKED ind. (double line), then TC-U-REJECT req. (double line), and finally REJECT (i) (single line).

SP B (CSL)
INVOKE (i)
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with a non-supported global operation code. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP B to SP A
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer)
Operation code tag: 00000110 (global)
Operation code length: 00000011 (3)
Operation code: 0000 0000
0001 0001
1000 0101 | | | | | + +TEST NUMBER: 2.1.7.4.2 + +Sheet: 2 of 2 + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +REJECT component in TSL message from SP A to SP B + +Component type tag: 10100001 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000001 (INVOKE problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (unrecognized operation) + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.8.1 | | Sheet: 1 of 2 | +| REFERENCE: Q.774 | | | +| TITLE: Valid functions; Multiple components grouping | | | +| SUBTITLE: Multiple operations invocation; receiving success | | | +| PURPOSE: To verify that multiple operations can be successfully invoked and the successful completions of the operations can be received | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains multiple components
2) Arrange the TC-User at SP B to send successful completions with an appropriate TSL message | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req. (#1)

Image: Double-lined arrow pointing right from SP A towards SP B

  • •
  • •
  • •
TC-INVOKE req. (#n)

Image: Double-lined arrow pointing right from SP A towards SP B

INVOKE #1, ..., #na)

Image: Single-lined arrow pointing right from SP A to SP B

RETURN RESULT-LAST #1, ..., #na)

Image: Single-lined arrow pointing left from SP B to SP A

TC-RESULT-L ind. (#1)

Image: Double-lined arrow pointing left from SP B towards SP A

  • •
  • •
  • •
TC-RESULT-L ind. (#n)

Image: Double-lined arrow pointing left from SP B towards SP A

a) The sequence of the components is provided by the TC-User.
NOTE – Number of components is subject to the TC-User.

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate multiple operations within a TSL message from SP A to SP B. | | +| 2. | CHECK A: WERE ALL THE INVOKE COMPONENTS WITHIN A TSL MESSAGE SENT BY SP A WITH CORRECT INFORMATION? | | +| 3. | CHECK B: WERE ALL THE RETURN-LAST COMPONENTS INSIDE A TSL MESSAGE PASSED TO TC-USER IN THE SAME ORDER AS PROVIDED BY SP B WITH CORRECT INFORMATION? | | +| 4. | CHECK C: WERE ALL THE INVOKE STATE MACHINES (1, ..., n) IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: 1, or, ..., n corresponding to the INVOKE #1, ..., #n + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x1, ..., xn representing valid operation codes + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: 1, or, ..., n + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x1, or, ..., xn (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.8.2 | | Sheet: 1 of 2 | +| REFERENCE: Q.774 | | | +| TITLE: Valid functions; Multiple components grouping | | | +| SUBTITLE: Multiple operations invocation; reporting success | | | +| PURPOSE: To verify that multiple operations can be successfully invoked and the successful completions of the operations can be sent | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains multiple components
2) Arrange the TC-User at SP A to send successful completions with an appropriate TSL message | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
INVOKE #1, ..., #na)

Image: Arrow pointing from SP B to SP A

TC-INVOKE ind. (#1)

Image: Double arrow pointing from SP A to SP B

  • •
  • •
  • •
TC-INVOKE ind. (#n)

Image: Double arrow pointing from SP A to SP B

TC-RESULT-L req. (#1)

Image: Double arrow pointing from SP A to SP B

  • •
  • •
  • •
TC-RESULT-L req. (#n)

Image: Double arrow pointing from SP A to SP B

RETURN RESULT-LAST #n, ..., #1a)

Image: Arrow pointing from SP A to SP B

| | | +| a) The sequence of the components is provided by the TC-User.
NOTE – Number of components is subject to the TC-User. | | | +| TEST DESCRIPTION | | | +| 1. | Initiate multiple operations within a TSL message from SP B to SP A. | | +| 2. | CHECK A: WERE ALL THE INVOKE COMPONENTS WITHIN A TSL MESSAGE PASSED TO TC-USER IN THE SAME ORDER AS PROVIDED BY SP B WITH CORRECT INFORMATION? | | +| 3. | CHECK B: WERE ALL THE RETURN RESULT-LAST COMPONENTS WITHIN A TSL MESSAGE SENT BY SP A WITH CORRECT INFORMATION? | | +| 4. | CHECK C: WAS THE INVOKE ID IN EACH OF THE RETURN RESULT-LAST COMPONENTS ONE-TO-ONE CORRESPONDENT WITH THE ONE IN EACH OF THE INVOKE COMPONENTS? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: 1, or, ..., n corresponding to the INVOKE #1, ..., #n + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x1, ..., xn representing valid operation codes + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: 1, or, ..., n + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x1, or, ..., xn (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.8.3 | | Sheet: 1 of 3 | | | +| REFERENCE: 3.2.2.2/Q.774 | | | | | +| TITLE: Valid functions; Multiple components grouping | | | | | +| SUBTITLE: A malformed component received | | | | | +| PURPOSE: To verify that subsequent components in the message can be discarded when a badly structured component is detected by the component sublayer | | | | | +| PRE-TEST CONDITIONS: Arrange the TC-User stimulus such that an appropriate TSL message generated at SP B contains multiple components, the second of which is badly structured | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL)

INVOKE #1, #2, #3 (Note 1)

←

(#2 badly structured, e.g.
operation code missing)

TC-INVOKE ind. (#1)

=====

TC-L-REJECT ind. (#2)

=====

TC-RESULT-L req. (#1)

=====

REJECT #2, RETURN RESULT-LAST #1

(Note 2)

→

NOTE 1 – The sequence of the Invoke components is important.

NOTE 2 – The sequence of these components is not important.

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate multiple operations within a TSL message from SP B to SP A with the order shown in the diagram. | | | | +| 2. | CHECK A: WAS THE FIRST INVOKE COMPONENT PASSED TO TC-USER? | | | | +| 3. | CHECK B: WERE ONLY THE RETURN RESULT-LAST COMPONENT FOR THE FIRST OPERATION AND THE REJECT COMPONENT FOR THE SECOND OPERATION SENT BY SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### INVOKE #1 component in TSL message from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: 1 + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x is a valid operation code + +parameters (provided by the TC-User) + +##### INVOKE #2 component in TSL message from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: 2 + +parameters (provided by the TC-User) + +##### INVOKE #3 component in TSL message from SP B to SP A + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: 3 + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x is a valid operation code + +parameters (provided by the TC-User) + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +RETURN RESULT-LAST #1 component in TSL message from SP A to SP B + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: 1 + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x + +parameters (provided by the TC-User) + +REJECT #2 component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: 2 + +Problem code tag: 10000000 (General Problem) + +Problem code length: 00000001 + +Problem code: 00000010 (badly structured component) + +NOTE – Omitted when no parameter is present. + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.9.1.1 | | Sheet: 1 of 1 | +| REFERENCE: 3.2.1.2/Q.774 | | | +| TITLE: Valid functions; Dialogue Portion | | | +| SUBTITLE: Accept application context proposal; Send AARQ in Begin message | | | +| PURPOSE: To verify that an IUT can generate and send the dialogue control APDU AARQ within the dialogue portion in a Begin message | | | +| PRE-TEST CONDITIONS: SP A ( TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
TR-BEGIN req.

Image: Double arrow pointing right

BEGIN (AARQ) →
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion. | | +| 2. |

CHECK A: DOES THE DIALOGUE PORTION IN THE BEGIN MESSAGE CONTAIN THE APDU AARQ?

Also arrange an END message to be sent by IUT or by the Tester. When the last message has been sent by Tester, the END message sent by IUT can be used to check that the last message has been correctly received.

| | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | | +|

Dialogue portion in Begin message

Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets

External data type in dialogue portion

External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
direct reference: H'00118605010101 (structured dialogue abstract syntax)

single ASN.1 type tag: 10100000
single ASN.1 type length: correct number of octets

Dialogue PDU

Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets

Application context tag: 10100001
Application context length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: correct number of octets
direct reference: any object identifier

| | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------|--|------------|--|---|---------------------|----------------------|--|--|---|--|--|-------------------------|--|--|--|--|--|------------------------|---|--| +| TEST NUMBER: 2.1.9.1.2 | | Sheet: 1 of 3 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Accept application context proposal; accept AARQ and continue dialogue | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can receive a Begin message with APDU 'AARQ' and then can generate and send the dialogue control APDU 'AARE' within the dialogue portion of a Continue message | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
← BEGIN (AARQ)
TR-BEGIN ind.
<
TR-CONTINUE req.
CONTINUE (AARE) ➔
| | | SP A (CSL) | | SP B (CSL) | | ← | BEGIN (AARQ) | TR-BEGIN ind. | | | < | | | TR-CONTINUE req. | | | | | | CONTINUE (AARE) | ➔ | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE (AARE) | ➔ | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue request. | | | | | | | | | | | | | | | | | | | | | | | +| 2. |

CHECK A: DOES THE DIALOGUE PORTION IN THE CONTINUE MESSAGE CONTAIN THE APDU AARE AND IS THE APPLICATION CONTEXT THE SAME AS IN THE RECEIVED AARQ?

Also arrange an END message to be sent by IUT or by the Tester. When the last message has been sent by Tester, the END message sent by IUT can be used to check that the last message has been correctly received.

| | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Begin message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 (see Note) + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Request tag: 01100000 + +Dialogue Request length: correct number of octets + +Protocol Version tag: 10000000 + +Protocol Version length: 00000010 + +Protocol Version value: 00000111 10000000 + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +NOTE – Instead of the encoding option Single ASN.1 type, this test can also be done with the 2 other options – octet aligned and arbitrary. + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in AARQ + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------|--|------------|--|---|---------------------|----------------------|--|--|---|--|--|--------------------|--|--|---|--|--|-------------------|----|--| +| TEST NUMBER: 2.1.9.1.3 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Accept application context proposal; accept AARQ and end dialogue | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can receive a Begin message with APDU AARQ and then can generate and send the dialogue control APDU 'AARE' within the dialogue portion of an End message | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A ( TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
← BEGIN (AARQ)
TR-BEGIN ind.
<
TR-END req.
>
END (AARE) ─>
| | | SP A (CSL) | | SP B (CSL) | | ← | BEGIN (AARQ) | TR-BEGIN ind. | | | < | | | TR-END req. | | | > | | | END (AARE) | ─> | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | +| TR-END req. | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | +| END (AARE) | ─> | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue request | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: DOES THE DIALOGUE PORTION IN THE END MESSAGE CONTAIN THE APDU AARE AND IS THE APPLICATION CONTEXT THE SAME AS IN THE RECEIVED AARQ? | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in End message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in AARQ + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------|--|------------|--|---|---------------------|----------------------|--|--|--|--|--|-------------------------|--|--|--|--|--|------------------------|---|--| +| TEST NUMBER: 2.1.9.2.1 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Propose alternative application context; Send AARE with alternative | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can generate and send dialogue control APDU 'AARE' with an alternative application context within the dialogue portion of a Continue message | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A ( TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
← BEGIN (AARQ)
TR-BEGIN ind.
TR-CONTINUE req.
CONTINUE (AARE) →
| | | SP A (CSL) | | SP B (CSL) | | ← | BEGIN (AARQ) | TR-BEGIN ind. | | | | | | TR-CONTINUE req. | | | | | | CONTINUE (AARE) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE (AARE) | → | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue request. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to propose an alternative application context. | | | | | | | | | | | | | | | | | | | | | | | +| 3. |

CHECK A: DOES THE DIALOGUE PORTION IN THE CONTINUE MESSAGE CONTAIN THE APDU AARE AND IS THE APPLICATION CONTEXT DIFFERENT THAN THE ONE IN THE RECEIVED AARQ?

Also arrange an END message to be sent by IUT or by the Tester. When the last message has been sent by Tester, the END message sent by IUT can be used to check that the last message has been correctly received.

| | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: correct number of octets different than those in AARQ + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. Length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|----------------------|--|--|---|--|--|---------------------|---|--|--|---|------------------------|-------------------------|--|--|---|--|--| +| TEST NUMBER: 2.1.9.2.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Propose alternative application context; receive AARE with alternative | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can accept the dialogue control APDU 'AARE' with an alternative application context within the dialogue portion of a Continue message | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
TR-BEGIN req.
→
BEGIN (AARQ) →
← CONTINUE (AARE)
TR-CONTINUE ind.
←
| | | SP A (CSL) | | SP B (CSL) | TR-BEGIN req. | | | → | | | BEGIN (AARQ) | → | | | ← | CONTINUE (AARE) | TR-CONTINUE ind. | | | ← | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | +| → | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN (AARQ) | → | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE (AARE) | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | +| ← | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to confirm the dialogue proposing an alternative application context | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: DOES THE IUT ACCEPT THE APDU 'AARE' WITH THE ALTERNATIVE APPLICATION CONTEXT?
Also arrange an END message to be sent by IUT or by the Tester. When the last message has been sent by Tester, the END message sent by IUT can be used to check that the last message has been correctly received. | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: correct number of octets different than those in AARQ + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. Length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------|------------|--|------------|--|---|---------------------|----------------------|--|--|---|--|--|---------------------------|--|--|---|--|--|---------------------|---|--| +| TEST NUMBER: 2.1.9.3 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue refused | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can generate and send dialogue control APDU 'AARE' within the dialogue portion in an Abort message to indicate that the application context is not supported | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
< BEGIN (AARQ)
TR-BEGIN ind.
<
TR- U - ABORT req.
>
ABORT (AARE) >
| | | SP A (CSL) | | SP B (CSL) | | < | BEGIN (AARQ) | TR-BEGIN ind. | | | < | | | TR- U - ABORT req. | | | > | | | ABORT (AARE) | > | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| | < | BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | +| TR- U - ABORT req. | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (AARE) | > | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue request. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to refuse the dialogue because of application context not supported. | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'AARE'? | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Abort message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax ) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in dialogue request + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000001 (Reject -Permanent) + +Result source diagnostic tag: 10100011 + +Result source length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000010 (Application Context Not Supported) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------|------------|--|------------|----------------------|--|--|--|--|--|---------------------|--|--|--|--|------------------------|-------------------------|--|--|--|--|--|------------------------|--|--|--|--|--|-------------------------|--|--| +| TEST NUMBER: 2.1.9.4 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue abort | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can generate and send the dialogue control APDU 'ABRT' within the dialogue portion in an Abort message after the dialogue has been established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
TR-BEGIN req.
BEGIN (AARQ)
CONTINUE (AARE)
TR-CONTINUE ind.
TR-U-ABORT req.
ABORT (U) (ABRT)
| | | SP A (CSL) | | SP B (CSL) | TR-BEGIN req. | | | | | | BEGIN (AARQ) | | | | | CONTINUE (AARE) | TR-CONTINUE ind. | | | | | | TR-U-ABORT req. | | | | | | ABORT (U) (ABRT) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE (AARE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (U) (ABRT) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to confirm the dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP A to Abort the dialogue for some reason. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: DOES THE DIALOGUE PORTION IN THE ABORT MESSAGE CONTAIN APDU 'ABRT'? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Abort message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax ) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Abort tag: 01100100 + +Dialogue Abort length: 00000011 + +Abort Source tag: 10000000 + +Abort source length: 00000001 + +Abort source: 00000000 (dialogue service user) + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.9.5.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1.2/Q.774 | | | +| TITLE: Valid functions; Dialogue Portion | | | +| SUBTITLE: Transport of User information; accept user information in Begin message | | | +| PURPOSE: To verify that an IUT can receive a Begin message with APDU AARQ including an user information element | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL)

SP B (CSL)

←

TR-BEGIN ind.

⇐

←

BEGIN (AARQ)

| | | +| TEST DESCRIPTION | | | +|

1.

2.

|

Arrange for SP B to send a Begin message containing a dialogue request containing user information.

CHECK A: DOES THE IUT ACCEPT USER INFORMATION IN THE RECEIVED DIALOGUE REQUEST?

Also arrange an END message to be sent by IUT. The END message sent by IUT can be used to check that the last message has been correctly received.

| | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Begin message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax ) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Request tag: 01100000 + +Dialogue Request length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +##### User information in dialogue PDU + +User Information tag: 10111110 + +User information length: correct number of octets + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +Single ASN.1 type tag: 10100000 (see Note) + +Single ASN.1 type length: correct number of octets + +Some bytes of user data in the user defined abstract syntax + +NOTE – This test can also be done with the 2 other encoding options – octet aligned and arbitrary. + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.9.5.2 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1.2/Q.774 | | | +| TITLE: Valid functions; Dialogue Portion | | | +| SUBTITLE: Transport of User information; accept user information in first Continue message | | | +| PURPOSE: To verify that an IUT can accept a Continue message with APDU 'AARE' including a user information element | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)

TR-BEGIN req.

⇒

BEGIN (AARQ)

⇒

←

CONTINUE (AARE)

TR-CONTINUE ind.

⇐

| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion. | | +| 2. | Arrange for SP B to confirm the dialogue including user information in the dialogue portion. | | +| 3. |

CHECK A: DOES THE IUT ACCEPT USER INFORMATION IN THE RECEIVED DIALOGUE RESPONSE?

Also arrange an END message to be sent by IUT or by the tester. When the last message has been sent by the tester, the END message sent by IUT can be used to check that the last message has been correctly received.

| | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 (structured dialogue abstract syntax ) + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. Length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +##### User information in dialogue PDU + +User Information tag: 10111110 + +User information length: correct number of octets + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +Some bytes of user data in the user defined abstract syntax + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------|--|------------|--|---|---------------------|----------------------|--|--|-----------------------------|--|--|--|--|--|------------------------|---|--|--|---|-----------------|-------------------------|--|--|--|--|--| +| TEST NUMBER: 2.1.9.5.3 | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Transport of User information; accept user information in subsequent Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that SP A can accept a user information element in a subsequent Continue message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state and test cases 2.1.9.5.2 has to be executed successfully | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)
← BEGIN (AARQ)
TR-BEGIN ind.

TR-CONTINUE req.
CONTINUE (AARE) →
← CONTINUE
TR-CONTINUE ind.
| | | SP A (CSL) | | SP B (CSL) | | ← | BEGIN (AARQ) | TR-BEGIN ind. | | |
TR-CONTINUE req. | | | | | | CONTINUE (AARE) | → | | | ← | CONTINUE | TR-CONTINUE ind. | | | | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONTINUE (AARE) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | CONTINUE | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message with dialogue request to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP A to confirm the dialogue. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send a Continue message including an user information element as dialogue portion. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK A: VERIFY THAT THE IUT AT SP A ACCEPTED THE USER INFORMATION ELEMENT
Also arrange an END message to be sent by IUT or by the Tester. When the last message has been sent by Tester, the END message sent by IUT can be used to check that the last message has been correctly received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dialogue portion in Continue message
Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets
External data type in dialogue portion (user information element)
External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: correct number of octets
Direct reference: any abstract syntax
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets
Some bytes of user data in the user defined abstract syntax | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|--------------------------|--|--|---|--|--|---------------------|--|--|--|--|------------------------|-----------------------------|--|--|---|--|--| +| TEST NUMBER: 2.1.9.5.4 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Transport of User information, accept several user information elements in Continue message | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can accept a Continue message with APDU 'AARE' including several user information elements | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A ( TSL) and SP B (TSL) are to be in the idle state and test cases 2.1.9.5.2 has to be executed successfully | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)

TR-BEGIN req.
>
BEGIN (AARQ)
CONTINUE (AARE)

TR-CONTINUE ind.
<
| | | SP A (CSL) | | SP B (CSL) |
TR-BEGIN req. | | | > | | | BEGIN (AARQ) | | | | | CONTINUE (AARE) |
TR-CONTINUE ind. | | | < | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +|
TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | +| | | CONTINUE (AARE) | | | | | | | | | | | | | | | | | | | | | | +|
TR-CONTINUE ind. | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to confirm the dialogue including user information elements in the dialogue portion. | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: DOES THE IUT ACCEPT USER INFORMATION IN THE RECEIVED DIALOGUE RESPONSE?
Also arrange an END message to be sent by IUT or by the Tester. When the last message has been sent by Tester, the END message sent by IUT can be used to check that the last message has been correctly received. | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. Length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +##### User information in dialogue PDU + +User Information tag: 10111110 + +User information length: correct number of octets + +External type tag: 00101000 (external number 1) + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any user defined abstract syntax + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Some bytes representing element 1 + +External type tag: 00101000 (external number 2) + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any user defined abstract syntax + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +###### Some bytes of user data in user information element number 2 + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|------------|------------|--|------------------------------|---|--|--------------------|--|--|--| +| TEST NUMBER: 2.1.9.6 | | Sheet: 1 of 1 | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | +| SUBTITLE: Unstructured dialogue | | | | | | | | | | | | | +| PURPOSE: To verify that the IUT can accept the dialogue control APDU 'AUDT' in an Unidirectional message | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)
UNIDIRECTIONAL (AUDT)
←
TR-UNI ind.
| | | SP A (CSL) | SP B (CSL) | | UNIDIRECTIONAL (AUDT) | ← | | TR-UNI ind. | | | | +| SP A (CSL) | SP B (CSL) | | | | | | | | | | | | +| | UNIDIRECTIONAL (AUDT) | | | | | | | | | | | | +| ← | | | | | | | | | | | | | +| TR-UNI ind. | | | | | | | | | | | | | +| | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | +| 1. | Arrange SP B to send an Unidirectional message containing a dialogue portion to SP A. | | | | | | | | | | | | +| 2. | CHECK A: WAS THE UNIDIRECTIONAL MESSAGE WITH APDU 'AUDT' CORRECTLY RECEIVED AT SP A? | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | | | | | | | | | +| Dialogue portion in Unidirectional message
Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets
External data type in dialogue portion
External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010201
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets
Dialogue PDU
Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets
Application context tag: 10100001
Application context length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: correct number of octets
Direct reference: any object identifier | | | | | | | | | | | | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.9.7.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.3/Q.774 | | | +| TITLE: Valid functions; Dialogue Portion | | | +| SUBTITLE: Dialogue control APDU Version Structured dialogue; Version not 1 | | | +| PURPOSE: To verify that an IUT can abort the dialogue if the first bit of the protocol version field in the dialogue request, is not set to 1. The dialogue has to be aborted with APDU 'AARE' (reject permanent, no common dialogue) | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)

Image: Diagram showing the message sequence. SP B (CSL) sends a BEGIN (AARQ) message to SP A (CSL). SP A (CSL) responds with a TR-U-ABORT req. message. SP A (CSL) then sends an ABORT (AARE) message to SP B (CSL).

 sequenceDiagram     participant SP B as SP B (CSL)     participant SP A as SP A (CSL)     Note right of SP B: BEGIN (AARQ)     SP B->>SP A: BEGIN (AARQ)     Note left of SP A: TR-U-ABORT req.     SP A->>SP A: TR-U-ABORT req.     Note left of SP A: ABORT (AARE)     SP A->>SP B: ABORT (AARE)
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue request indicating that Version 1 is not supported | | +| 2. | CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'AARE' INDICATING NO COMMON DIALOGUE PORTION? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Abort message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in dialogue request + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000001 (Reject-Permanent) + +Result source diagnostic tag: 10100011 + +Result source length: 00000101 + +Dialogue Service Provider tag: 10100010 + +Dialogue Service Provider length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service provider value: 00000010 (No common dialogue portion) + +| | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------|------------|------------|--|------------------------|--|--|----------------------|--|--|--|-------------------------|--|--|--|---------------------------|--| +| TEST NUMBER: 2.1.9.7.2 | | Sheet: 1 of 1 | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.3/Q.774 | | | | | | | | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue control APDU Version Structured dialogue; Version 1 | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can accept a dialogue request offering several versions including version 1.
The IUT response must be of version 1 | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)
BEGIN (AARQ-Vx)
TR-BEGIN ind.
TR-CONTINUE req.
CONTINUE (AARE-V1)
| | | SP A (CSL) | SP B (CSL) | | BEGIN (AARQ-Vx) | | | TR-BEGIN ind. | | | | TR-CONTINUE req. | | | | CONTINUE (AARE-V1) | | +| SP A (CSL) | SP B (CSL) | | | | | | | | | | | | | | | | | | +| | BEGIN (AARQ-Vx) | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | +| TR-BEGIN ind. | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | +| TR-CONTINUE req. | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | +| CONTINUE (AARE-V1) | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue request offering several versions including Version 1. | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: DOES THE DIALOGUE PORTION IN THE CONTINUE MESSAGE CONTAIN THE APDU AARE AND IS IT OF VERSION 1? | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | | | | | | | | | | | | | | | | | | +| Dialogue portion in Begin message
Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets
External data type in dialogue portion
External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010101
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets
Dialogue PDU
Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets
Protocol Version tag: 10000000
Protocol Version length: 00000010
Protocol Version: 00000110 11000000 (versions 1 and 2 supported)
Application context tag: 10100001
Application context length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: correct number of octets
Direct reference: any object identifier | | | | | | | | | | | | | | | | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------|--|--| +| TEST NUMBER: 2.1.9.7.3 | | Sheet: 1 of 1 | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | +| SUBTITLE: Dialogue control APDU Version Unstructured dialogue; Version not 1 | | | | | +| PURPOSE: To verify that an IUT can discard a UNIDIRECTIONAL msg if the first bit of the protocol version field in the dialogue request AUDT, is not set to 1 | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state and test case 2.1.9.6 has to be executed successfully | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE SEQUENCE: | | | | | +| SP A (CSL) | | SP B (CSL) | | | +| msg discarded | ← | UNIDIRECTIONAL (AUDT) | | | +| TEST DESCRIPTION | | | | | +| 1. | Arrange SP B to send an Unidirectional msg containing APDU AUDT indicating that Version 1 is not supported to SP A. | | | | +| 2. | CHECK A: WAS THE UNIDIRECTIONAL MESSAGE WITH APDU 'AUDT' DISCARDED AT SP A? | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | | | +| Dialogue portion in Unidirectional message
Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets
External data type in dialogue portion
External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010201
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets
Dialogue PDU
Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets
Protocol Version tag: 10000000
Protocol Version length: 00000010
Protocol Version: 00000110 01000000 (only version 2 supported)
Application context tag: 10100001
Application context length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: correct number of octets
Direct reference: any object identifier | | | | | + +| | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------|------------|--|------------|--|---|------------------------------|-------------------------|--|--| +| TEST NUMBER: 2.1.9.7.4 | | Sheet: 1 of 2 | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | +| TITLE: Valid functions; Dialogue Portion | | | | | | | | | | | | +| SUBTITLE: Dialogue control APDU Version Unstructured dialogue; Version 1 | | | | | | | | | | | | +| PURPOSE: To verify that an IUT can accept a UNIDIRECTIONAL msg if the first bit of the protocol version is set to 1 and also other bits are set to 1 | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state and test case 2.1.9.6 has to be executed successfully | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)
← UNIDIRECTIONAL (AUDT)
TR-UNI ind.
<
| | | SP A (CSL) | | SP B (CSL) | | ← | UNIDIRECTIONAL (AUDT) | TR-UNI ind.
< | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | +| | ← | UNIDIRECTIONAL (AUDT) | | | | | | | | | | +| TR-UNI ind.
< | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | +| 1. | Arrange SP B to send an Unidirectional msg containing APDU AUDT offering several versions including Version 1, to SP A. | | | | | | | | | | | +| 2. | CHECK A: WAS THE UNIDIRECTIONAL MESSAGE WITH APDU 'AUDT' ACCEPTED AT SP A? | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES + +##### Dialogue portion in Unidirectional message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010201 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Request tag: 01100000 + +Dialogue Request length: correct number of octets + +Protocol Version tag: 10000000 + +Protocol Version length: 00000010 + +Protocol Version: 00000110 11000000 (version 1 and version 2 supported) + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.1.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 6.2/Q.773 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | +| SUBTITLE: Length of Invoke ID >1 in Invoke component | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be performed due to incorrect encoding of component ID (value out of range) | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with an error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.

<=====

REJECT (NULL)

←-----→

SP B (CSL)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with Invoke ID equal to 2 octets (illegal value). | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000010 (two octets)

Invoke ID: 129

| | | | | + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| TEST NUMBER: 2.2.1.1 | Sheet: 2 of 2 | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | +|

Operation code tag: 00000010 (local) or 00000110 (global)
Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)
Operation code: x (x represents a valid operation code)
parameters (provided by the TC-User)

REJECT component in TSL message from SP A to SP B

Component type tag: 10100100 (REJECT)
Component length: correct number of octets
NULL tag: 00000101
NULL length: 00000000

Problem code tag: 10000000 (General problem type)
Problem code length: 00000001
Problem code: 00000001 (mistyped component)

| | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.1.2 | | Sheet: 1 of 1 | | | +| REFERENCE: 6.2/Q.773 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid values for information elements | | | | | +| SUBTITLE: Length of Invoke ID = 0 in Invoke component | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be performed due to incorrect encoding of component ID (length equals 0) | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with an error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.

<=====

REJECT (NULL)

←-----→

SP B (CSL)

INVOKE

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with Invoke ID equal to 0 octets (illegal value). | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000000 (zero octet)

Operation code tag: 00000010 (local) or 000000110 (global)

Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)

Operation code: x (x represents a valid operation code)

parameters (provided by the TC-User)

REJECT component in TSL message from SP A to SP B

Component type tag: 10100100 (REJECT)

Component length: correct number of octets

NULL tag: 00000101

NULL length: 00000000

Problem code tag: 10000000 (General problem type)

Problem code length: 00000001

Problem code: 00000001 (wrong type component)

| | | | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.2.1.1 | | Sheet: 1 of 1 | | | +| REFERENCE: 6.2/Q.773 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | +| SUBTITLE: Invoke component; Invoke ID missing | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be performed due to Invoke ID missing | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with an error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.

REJECT (NULL)

←—————

—————→

SP B (CSL)

INVOKE

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a single operation invocation from SP B to SP A with Invoke ID missing. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Operation code tag: 00000110 (global)

Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)

Operation code: x (x represents a valid operation code)

parameters (provided by the TC-User)

REJECT component in TSL message from SP A to SP B

Component type tag: 10100100 (REJECT)

Component length: correct number of octets

NULL tag: 00000101

NULL length: 00000000

Problem code tag: 10000000 (General problem type)

Problem code length: 00000001

Problem code: 00000001 (wrong type component)

| | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.2.1.2 | | Sheet: 1 of 1 | | | +| REFERENCE: 3.2.2.2/Q.774 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | +| SUBTITLE: Invoke component; Operation code missing | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be performed due to operation code missing | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with a syntax error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.

REJECT (i)

←──────────────────────────────────────────────────

══════════════════════════════════════════════════

──────────────────────────────────────────────────→

SP B (CSL)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with operation code missing. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

parameters (provided by the TC-User)

REJECT component in TSL message from SP A to SP B

Component type tag: 10100100 (REJECT)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001

Invoke ID: i

Problem code tag: 10000000 (General problem type)

Problem code length: 00000001

Problem code: 00000001 (wrong type component)

| | | | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.2.2.2.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Return Result component; Invoke ID missing | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to the absence of the Invoke ID in the Return Result-Last component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result-Last without an Invoke ID is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL)
TC-INVOKE req.
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     B-->>A: RETURN RESULT-LAST     Note over A: TC-L-REJECT ind.     A->>B: REJECT (NULL)     Note over A: time expiry for invocation (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 1 or 3 operation invocation from SP A to SP B.
Generate a response from SP B to SP A without an Invoke ID. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets

INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### **CHECK TABLE FOR COMPONENTS WITHIN MESSAGES** + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### **RETURN RESULT-LAST component in TSL message from SP B to SP A** + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: y (y is different from x) (see Note) + +parameters (provided by the TC-User) + +##### **REJECT component in TSL message from SP A to SP B** + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +NULL tag: 00000101 + +NULL length: 00000000 + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (wrong type component) + +NOTE – Omitted when no parameter is present. + +| TEST NUMBER: 2.2.2.2.2 | | Sheet: 1 of 2 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Return Result component; Operation code missing while parameters included | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to the operation code being missing in the Return Result-Last component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component for Class 1 or 3
2) Arrange the data at SP B such that a Return Result-Last without an operation code is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     B->>A: RETURN RESULT-LAST (i)     Note over A: TC-L-REJECT ind.     A->>B: REJECT (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate an operation invocation from SP A to SP B.
Generate a response from SP B to SP A with a valid Invoke ID but a different operation code. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 + +Sequence length: correct number of octets + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (wrong type component) + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.2.2.3 | | Sheet: 1 of 2 | | | +| REFERENCE: 6.4/Q.773; 3.2.2.2/Q.774 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | +| SUBTITLE: Return Result component; Sequence tag missing while parameters included | | | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to Sequence tag missing while parameters included | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that an appropriate TSL message contains a Return Result-Last component with an invalid Sequence tag | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKE req.

Image: Right arrow


INVOKE (i)
SP B (CSL)

Image: Left arrow


RETURN RESULT-LAST (i)
TC-L-REJECT ind.

Image: Left arrow


REJECT (i)
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +#### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (wrong type component) + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.2.2.3.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Return Error; Invoke ID missing | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to the absence of the Invoke ID in the Return Error component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component of the Class 1
2) Arrange the data at SP B such that a Return Error without an Invoke ID is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL) SP B (CSL)
TC-INVOKE req.
⇒
INVOKE (i) —————————————————→
←————————————————— RETURN ERROR
TC-L-REJECT ind.
⇐
REJECT (NULL) —————————————————→
time expiry for invocation (i) | | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 1 operation invocation from SP A to SP B.
Generate an unsuccessful response from SP B to SP A without an Invoke ID. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### **CHECK TABLE FOR COMPONENTS WITHIN MESSAGES** + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### **RETURN ERROR component in TSL message from SP B to SP A** + +Component type tag: 10100010 (RETURN ERROR) + +Component length: correct number of octets + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y (y is an error code which the invoked operation may report) + +parameters (provided by the TC-User) + +##### **REJECT component in TSL message from SP A to SP B** + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +NULL tag: 00000101 + +NULL length: 00000000 + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (mistyped component) + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.2.2.3.2 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Return Error; Error code missing | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to the absence of the error code in the Return Error component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component of Class 1
2) Arrange the data at SP B such that a Return Error without an error code is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 SP A (CSL)                                     SP B (CSL) TC-INVOKE req.  ===========> INVOKE (i)         ---------------------------->                     <----------------------------  RETURN ERROR (i)  TC-L-REJECT ind.  <=========== REJECT (i)         ---------------------------->

Image: Sequence diagram showing message flow between SP A and SP B. SP A sends an INVOKE (i) to SP B. SP B responds with a RETURN ERROR (i). SP A then generates a REJECT (i) message.

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 1 operation invocation from SP A to SP B.
Generate an unsuccessful response from SP B to SP A with a valid Invoke ID but without error code for this operation. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A ? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000101 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000001 (mistyped component) + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.2.2.4.1 | | Sheet: 1 of 1 | +| REFERENCE: 3.2.2.2/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Unknown component type; Invoke ID unrecognizable | | | +| PURPOSE: To verify that a rejection can be initiated due to Unknown component type with unrecognized Invoke ID | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Unknown component as described below | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.
<
REJECT (NULL)
←


→
SP B (CSL)
Unknown component
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate an operation invocation from SP B to SP A with an Unknown component type with any content. | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +|

Component portion in TSL messages

  • Component portion tag: 01101100
  • Component portion length: correct number of octets

Unknown component in TSL message from SP B to SP A

  • Component type tag: any values except 10100001, 10100010, 10100011, 10100100 and 10100111
  • Component length: correct number of octets
  • Component content: any

REJECT component in TSL message from SP A to SP B

  • Component type tag: 10100100 (REJECT)
  • Component length: correct number of octets
  • NULL tag: 00000101
  • NULL length: 00000000
  • Problem code tag: 10000000 (General problem type)
  • Problem code length: 00000001
  • Problem code: 00000000 (unrecognized component)
| | | + + + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------| +| TEST NUMBER: 2.2.2.5.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2.1/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Dialogue Portion; Missing Application Context in APDU AARQ | | | +| PURPOSE: To verify that the IUT aborts the transaction upon reception of a Begin message containing an APDU 'AARQ' without application context parameter. | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | + +EXPECTED MESSAGE SEQUENCE: + +SP A (CSL) +SP B (CSL) + + + +*Detect syntax error* +← +**BEGIN (AARQ)** + + + +*TR-U-ABORT req.* + +**ABORT (ABRT)** + → + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TEST DESCRIPTION | +| 1. Arrange for SP B to send a Begin message containing a dialogue request without application context.
2. CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'ABRT'? | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | +| Dialogue portion in Abort message
Dialogue portion tag: 01101011
Dialogue portion length: 00010010
External data type in dialogue portion
External type tag: 00101000
External length: 00010000
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010101 (structured dialogue abstract syntax)
Single ASN.1 type tag: 10100000
Single ASN.1 type length: 00000101
Dialogue PDU
Dialogue Abort tag: 01100100
Dialogue Abort length: 00000011
Abort Source tag: 10000000
Abort source length: 00000001
Abort source: 00000001 (dialogue service provider) | + +262 **Recommendation Q.787 (09/97)** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| TEST NUMBER: 2.2.2.5.1 | Sheet: 2 of 2 | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | +| Dialogue portion in Begin message
Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets
External data type in dialogue portion
External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010101
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets
Dialogue PDU
Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets
Application context tag: Missing | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|---------------------------|--|--|---------------------|--|--|----------------------------|--|------------------------|---------------------------------|--|--|-----------------------------|--|--|---------------------|--|--| +| TEST NUMBER: 2.2.2.5.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue Portion; Incorrect length | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the IUT aborts the transaction upon reception of a Continue message containing an APDU 'AARE' with an incorrect AARE length indicator | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
TR-BEGIN req.
>
BEGIN (AARQ)
Detect syntax error CONTINUE (AARE)

TR-P-ABORT ind.
<
TR-U-ABORT req.
>
ABORT (ABRT)
| | | SP A (CSL) | | SP B (CSL) | TR-BEGIN req.
> | | | BEGIN (AARQ) | | | Detect syntax error | | CONTINUE (AARE) |
TR-P-ABORT ind.
< | | | TR-U-ABORT req.
> | | | ABORT (ABRT) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req.
> | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | +| Detect syntax error | | CONTINUE (AARE) | | | | | | | | | | | | | | | | | | | | | | +|
TR-P-ABORT ind.
< | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT req.
> | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (ABRT) | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to confirm the dialogue with an incorrect AARE length indicator in the APDU AARE. | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: DOES THE DIALOGUE PORTION IN THE ABORT MESSAGE CONTAIN APDU 'ABRT'? | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE DIALOGUE AT SP A HAS BEEN TERMINATED. | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +#### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: 01111111 ( incorrect) + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in dialogue request + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 ( Null) + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.2.2.5.3 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2.1/Q.774 | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | +| SUBTITLE: Dialogue Portion; Missing result-source-diagnostic | | | +| PURPOSE: To verify that the IUT aborts the transaction upon reception of a Continue message containing an APDU 'AARE' with a missing result-source-diagnostic parameter | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)

TR-BEGIN req.
double line with arrow pointing right

BEGIN (AARQ) single line with arrow pointing right

Detect syntax error single line with arrow pointing left CONTINUE (AARE)

TR-P-ABORT ind.
double line with arrow pointing left

TR-U-ABORT req.
double line with arrow pointing right

ABORT (ABRT) single line with arrow pointing right

| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion. | | +| 2. | Arrange for SP B to confirm the dialogue with an incorrect AARE, parameter missing. | | +| 3. | CHECK A: VERIFY THAT THE DIALOGUE AT SP A HAS BEEN TERMINATED. | | +| 4. | CHECK B: DOES THE DIALOGUE PORTION IN THE ABORT MESSAGE CONTAIN APDU 'ABRT'? | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in dialogue request + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: Missing + +| | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------|------------|--|------------|----------------------------|---|------------------------------| +| TEST NUMBER: 2.2.2.5.4 | | Sheet: 1 of 1 | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | +| SUBTITLE: Dialogue Portion; Missing application context in APDU AUDT | | | | | | | | | +| PURPOSE: To verify that the IUT discards an Unidirectional message containing a dialogue request without AC parameter | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
Detect syntax error ← UNIDIRECTIONAL (AUDT)
| | | SP A (CSL) | | SP B (CSL) | Detect syntax error | ← | UNIDIRECTIONAL (AUDT) | +| SP A (CSL) | | SP B (CSL) | | | | | | | +| Detect syntax error | ← | UNIDIRECTIONAL (AUDT) | | | | | | | +| TEST DESCRIPTION | | | | | | | | | +| 1. | Arrange for SP B to send an Unidirectional message with corrupted dialogue request to SP A. | | | | | | | | +| 2. | CHECK A: VERIFY THAT NO MESSAGE IS GENERATED IN RESPONSE TO THE RECEIVED MESSAGE. | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | | | | | | | | +| Dialogue Portion in Unidirectional message
Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets
External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010201
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets
Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets
Protocol Version tag: 10000000
Protocol Version length: 00000010
Protocol Version: 00000110
11000000
Application context tag: missing | | | | | | | | | + + + +| | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------|--|------------|----------------------------------|---|-------------------------|--------------------------------|--|--|---------------------|---|--| +| TEST NUMBER: 2.2.2.5.6 | | Sheet: 1 of 1 | | | | | | | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue Portion; Indirect reference in External type | | | | | | | | | | | | | | | +| PURPOSE: To verify that the IUT aborts the transaction on reception of a Begin message containing an external type which contains both a direct reference and indirect reference | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)

Detect semantic error		 ←
BEGIN (AARQ)

TR-U-ABORT req.
ABORT (ABRT) →
| | | SP A (CSL) | | SP B (CSL) |
Detect semantic error | ← |
BEGIN (AARQ) |
TR-U-ABORT req.
| | | ABORT (ABRT) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | +|
Detect semantic error | ← |
BEGIN (AARQ) | | | | | | | | | | | | | +|
TR-U-ABORT req.
| | | | | | | | | | | | | | | +| ABORT (ABRT) | → | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue portion with an external type also containing an indirect reference. | | | | | | | | | | | | | | +| 2. | CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'ABRT'? | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | | | | | | | | | | | | | | +|

Dialogue portion in Begin message

Dialogue portion tag: 01101011
Dialogue portion length: correct number of octets

External data type in dialogue portion

External type tag: 00101000
External length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: 00000111
Direct reference: H'00118605010101
INTEGER type tag: 00000010
INTEGER length: 00000001
Indirect reference: 00000001
Single ASN.1 type tag: 10100000
Single ASN.1 type length: correct number of octets

Dialogue PDU

Dialogue Request tag: 01100000
Dialogue Request length: correct number of octets
Application context tag: 10100001
Application context length: correct number of octets
Object Identifier tag: 00000110
Object Identifier length: correct number of octets
Direct reference: any object identifier

| | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------|--|------------|----------------------------------|---|-------------------------|----------------------------|--|--|---|--|--|---------------------|---|--| +| TEST NUMBER: 2.2.2.5.7 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue Portion; User information without direct reference | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the IUT aborts a dialogue on reception of an User information element without direct reference | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)

Detect semantic error		 ←
BEGIN (AARQ)

TR-U-ABORT req.
>
ABORT (ABRT) →








| | | SP A (CSL) | | SP B (CSL) |
Detect semantic error | ← |
BEGIN (AARQ) |
TR-U-ABORT req. | | | > | | | ABORT (ABRT) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | +|
Detect semantic error | ← |
BEGIN (AARQ) | | | | | | | | | | | | | | | | +|
TR-U-ABORT req. | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | +| ABORT (ABRT) | → | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue portion including a user information element whose external type does not contain a direct reference. | | | | | | | | | | | | | | | | | +| 2. | CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'ABRT'? | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Begin message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Request tag: 01100000 + +Dialogue Request length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +##### User information in dialogue PDU + +User Information tag: 10111110 + +User information length: correct number of octets + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: missing + +Object Identifier length: missing + +Direct reference: missing + +Octet-aligned tag: 10000001 + +Octet aligned length: correct number of octets + +Octet string value: any number of octets + +| | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------|--|------------|--|--|---------------------|------------------------------|---|--|----------------------------|--|--|---|--|--|-------------------------|---|--| +| TEST NUMBER: 2.2.2.5.8 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Syntactically invalid behaviour; Invalid structure | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue Portion; Indirect reference in User information | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the IUT aborts a dialogue on reception of an User information element which contains both a direct reference and an indirect reference | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)
BEGIN (AARQ)
Detect semantic error ←

TR-U-ABORT req.
>

ABORT (ABRT)		 →
| | | SP A (CSL) | | SP B (CSL) | | | BEGIN (AARQ) | Detect semantic error | ← | |
TR-U-ABORT req. | | | > | | |
ABORT (ABRT) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | +| | | BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | +| Detect semantic error | ← | | | | | | | | | | | | | | | | | | | | +|
TR-U-ABORT req. | | | | | | | | | | | | | | | | | | | | | +| > | | | | | | | | | | | | | | | | | | | | | +|
ABORT (ABRT) | → | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue portion with an external type also containing an indirect reference. | | | | | | | | | | | | | | | | | | | | +| 2 | CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'ABRT'? | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Begin message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Request tag: 01100000 + +Dialogue Request length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +##### User information in dialogue PDU + +User Information tag: 10111110 + +User information length: correct number of octets + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Indirect reference: 00000001 + +Octet-aligned tag: 10000001 + +Octet aligned length: correct number of octets + +Octet string value: any number of octets + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.3.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.2.2/Q.774; 3.2.3/Q.773 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid encoding for Invoke component | | | | | +| SUBTITLE: Invalid tag | | | | | +| PURPOSE: To verify that a rejection is generated because of an invalid tag | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with an error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.

<=====

REJECT (i or NULL)

←-----

SP B (CSL)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with an invalid tag. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: correct number of octets

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

| | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Invalid tag: 00100010 + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +or + +NULL tag: 00000101 + +NULL length: 00000000 + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000010 (badly structured component) + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.2.3.2 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.2.2/Q.774 | | | | | +| TITLE: Syntactically invalid behaviour; Invalid encoding for Invoke component | | | | | +| SUBTITLE: Wrong component length | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be initiated due to wrong component length | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component with a syntax error as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +|

EXPECTED MESSAGE AND COMPONENT FLOW:

SP A (CSL)

TC-L-REJECT ind.

REJECT (i or NULL)

←—————

—————→

SP B (CSL)

INVOKE (i)

| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP B to SP A with an invalid component length value. | | | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT ? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +|

Component portion in TSL messages

Component portion tag: 01101100

Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

Component type tag: 10100001 (INVOKE)

Component length: wrong number of octets (e.g. 00000000)

Invoke ID tag: 00000010

Invoke ID length: 00000001 (one octet)

Invoke ID: i (i represents an integer)

| | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +or + +NULL tag: 00000101 + +NULL length: 00000000 + +Problem code tag: 10000000 (General problem type) + +Problem code length: 00000001 + +Problem code: 00000010 (badly structured component) + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.2.3.3 | | Sheet: 1 of 1 | +| REFERENCE: 3.3/Q.773 | | | +| TITLE: Syntactically invalid behaviour; Invalid encoding for Invoke component | | | +| SUBTITLE: Missing EOC in indefinite form | | | +| PURPOSE: To verify that a component portion with an indefinite form but EOC missing is rejected | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that an appropriate TSL message generated at SP B contains an Invoke component | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
 sequenceDiagram     participant SPA as SP A (CSL)     participant SPB as SP B (CSL)     Note over SPB: INVOKE (i)     SPB->>SPA:      Note over SPA: TC-L-REJECT ind.     SPA->>SPB: REJECT (i or NULL)
SP A (CSL)

TC-L-REJECT ind.
<
SP B (CSL)
INVOKE (i)
←
REJECT (i or NULL) →
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a single operation invocation from SP B to SP A. | | +| 2. | CHECK A: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +|

Component portion in TSL messages

  • Component portion tag: 01101100
  • Component portion length: correct number of octets

INVOKE component in TSL message from SP B to SP A

  • Component type tag: 10100001 (INVOKE)
  • Component length: correct number of octets (indefinite form)
  • Invoke ID tag: 00000010
  • Invoke ID length: 00000001 (one octet)
  • Invoke ID: i (i represents an integer)
  • Operation code tag: 00000010 (local) or 00000110 (global)
  • Operation code length: correct number of octets (e.g. 00000001 if x is one octet long)
  • Operation code: x (x represents a valid operation code)
  • parameters (provided by the TC-User)

REJECT component in TSL message from SP A to SP B

  • Component type tag: 10100100 (REJECT)
  • Component length: correct number of octets
  • Invoke ID tag: 00000010
  • Invoke ID length: 00000001
  • Invoke ID: i
  • or
  • NULL tag: 00000101
  • NULL length: 00000000
  • Problem code tag: 10000000 (General problem type)
  • Problem code length: 00000001
  • Problem code: 00000010 (badly structured component)
| | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.3.1.1 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.2/Q.774 | | | | | +| TITLE: Inopportune Behaviour; Inopportune Invoke component | | | | | +| SUBTITLE: Invalid linked ID | | | | | +| PURPOSE: To verify that a rejection of a requested operation can be initiated due to invalid linked ID | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a linked Invoke component can be generated as described below | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL)
TC-INVOKEReq.
→
INVOKE (i)
→
←
TC-L-REJECTind.
←
REJECT (j)
time expiry for invocation (i)
→
TC-L-CANCELind.
←
SP B (CSL)



INVOKE (j, k)



| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate an operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOKE ID IN THE REJECT COMPONENT THE SAME AS THE ONE IN THE INVOKE COMPONENT SENT BY SP B? | | | | +| 5. | CHECK D: WAS THE INVOCATION STATE MACHINE IDLE AT SP A ? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) +Operation code: x (x represents a valid operation code) +parameters (provided by the TC-User) + +##### INVOKE component in TSL message sent by SP B + +Component type tag: 10100001 (INVOKE) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 (one octet) +Invoke ID: j (j represents an integer) +Linked ID tag: 10000000 +Linked ID length: 00000001 (one octet) +Linked ID: k (k is an integer which is different from i) +Operation code tag: 00000010 (local) or 00000110 (global) +Operation code length: correct number of octets (e.g. 00000001 if y is one octet long) +Operation code: y (y represents a valid operation code) +parameters (provided by the TC-User) + +##### REJECT component in the TSL message sent by SP A + +Component type tag: 10100100 (REJECT) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: j +Problem code tag: 10000001 (INVOKE) +Problem code length: 00000001 +Problem code: 00000101 (unrecognized linked ID) + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.2.1 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Inopportune Behaviour; Unrecognized Invoke ID | | | +| SUBTITLE: Inopportune Return Result-Last component | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an unrecognized Invoke ID (never used and just released) in the received Return Result-Last component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component for operation Class 1 or 3
2) Arrange the data at SP B such that a Return Result-Last with an invalid Invoke ID is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.

Image: Right arrow

INVOKE (i)

Image: Right arrow

Image: Left arrow

RETURN RESULT-LAST (j)
TC-L-REJECT ind.

Image: Left arrow

REJECT (j)
time expiry for invocation (i)

Image: Right arrow

Image: Left arrow

RETURN RESULT-LAST (i)
TC-L-REJECT ind.

Image: Left arrow

REJECT (i)

Image: Right arrow

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate an operation invocation from SP A to SP B.
Generate a response from SP B to SP A with an unrecognized Invoke ID. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT SENT BY SP A ? | | +| 4. | Generate a Return Result-Last component from SP B to SP A. | | +| 5. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 6. | CHECK D: WAS THE COMPONENT FLOW AS SHOWN IN ABOVE ? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j (j is different from i) + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized invoke ID) + +The contents of the last two components, RETURN-RESULT-LAST (i) and REJECT (i), are the same as above except the Invoke ID is (i). + +NOTE – Omitted when no parameter is present. + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.2.2 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Inopportune Behaviour; Unrecognized Invoke ID | | | +| SUBTITLE: Inopportune Return Result Not-Last component | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an unrecognized Invoke ID (never used and just released) in the received Return Result Not-Last component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component for operation Class 1 or 3
2) Arrange the data at SP B such that a Return Result Not-Last with an invalid Invoke ID is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKED req.

Image: Double-lined arrow pointing right

INVOKE (i)

Image: Arrow pointing right

Image: Arrow pointing left

RETURN RESULT NOT-LAST (j)
TC-L-REJECT ind.

Image: Double-lined arrow pointing left

REJECT (j)
time expiry for invocation (i)

Image: Arrow pointing right

Image: Arrow pointing left

RETURN RESULT NOT-LAST (i)
TC-L-REJECT ind.

Image: Double-lined arrow pointing left

REJECT (i)

Image: Arrow pointing right

| | | +| TEST DESCRIPTION | | | +| 1.
2.
3.
4.
5.
6. | Initiate an operation invocation from SP A to SP B.
Generate a response from SP B to SP A with an unrecognized Invoke ID.
CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A?
CHECK B: WAS THE REJECT COMPONENT SENT BY SP A ?
Generate a Return Result Not-Last component from SP B to SP A.
CHECK C: WAS THE REJECT COMPONENT SENT BY SP A?
CHECK D: WAS THE COMPONENT FLOW AS SHOWN IN ABOVE ? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j (j is different from i) + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized invoke ID) + +RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized invoke ID) + +NOTE – Omitted when no parameter is present. + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.2.3 | | Sheet: 1 of 3 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Inopportune Behaviour; Unrecognized Invoke ID | | | +| SUBTITLE: Inopportune Return Error component | | | +| PURPOSE: To verify that a rejection can be successfully initiated due to an unrecognized Invoke ID (never used and just released) in the received Return Error component | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component for unrecognized operation Class 1 or 2
2) Arrange the data at SP B such that a Return Error with an invalid Invoke ID is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.

Image: Double-lined arrow pointing right from SP A to SP B

INVOKE (i)

Image: Single-lined arrow pointing right from SP A to SP B

Image: Single-lined arrow pointing left from SP B to SP A

RETURN ERROR (j)
TC-L-REJECT ind.

Image: Double-lined arrow pointing left from SP B to SP A

REJECT (j)
time expiry for invocation (i)

Image: Single-lined arrow pointing right from SP A to SP B

TC-L-CANCEL ind.

Image: Double-lined arrow pointing left from SP B to SP A

Image: Single-lined arrow pointing left from SP B to SP A

RETURN ERROR (i)
TC-L-REJECT ind.

Image: Double-lined arrow pointing left from SP B to SP A

REJECT (i)

Image: Single-lined arrow pointing right from SP A to SP B

| | | +| TEST DESCRIPTION | | | +| 1. | Initiate an operation invocation from SP A to SP B.
Generate an unsuccessful response from SP B to SP A with an invalid Invoke ID. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT SENT BY SP A ? | | +| 4. | Generate a Return Error component from SP B to SP A. | | +| 5. | CHECK C: WAS THE REJECT COMPONENT SENT BY SP A? | | +| 6. | CHECK D: WAS THE COMPONENT FLOW AS ABOVE ? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j (j is different from i) + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j + +Problem code tag: 10000011 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized invoke ID) + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Error code tag: 00000010 (local) or 00000110 (global) + +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) + +Error code: y + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000011 (RETURN ERROR) + +Problem code length: 00000001 + +Problem code: 00000000 (unrecognized invoke ID) + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.2.4 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2/Q.774 | | | +| TITLE: Inopportune Behaviour; Unrecognized Invoke ID | | | +| SUBTITLE: Inopportune Reject component | | | +| PURPOSE: To verify that receipt of a Reject component with an Invoke ID not corresponding to any active invocation has no effect on an active invocation | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component for Class 1 or 2
2) Arrange the data at SP B such that a Reject with an unrecognized Invoke ID is generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
⇒
INVOKE (i) →
← REJECT (j)
TC-R-REJECT ind.a)
⇐
← RETURN RESULT-LAST (i)
TC-L-RESULT ind.
⇐
| | | +| a) The issuing of the TC-R-REJECT ind. is implementation dependent. | | | +| TEST DESCRIPTION | | | +| 1. | Initiate an operation invocation from SP A to SP B.
Generate a reject from SP B to SP A with an invalid Invoke ID. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | Generate a Reject component from SP B to SP A. | | +| 4. | CHECK B: WAS THE COMPONENT FLOW AS ABOVE? | | +| 5. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +##### Component portion in TSL messages + +Component portion tag: 01101100 + +Component portion length: correct number of octets + +##### INVOKE component in TSL message from SP A to SP B + +Component type tag: 10100001 (INVOKE) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 (one octet) + +Invoke ID: i (i represents an integer) + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: j (j is different from i) + +Problem code tag: 10000001 (INVOKE) + +Problem code length: 00000001 + +Problem code: any value + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000101 (Global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------------------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|--|--|--|--|-------------------------------|-------------------------|--|--|--|--|--|-------------------|--|--| +| TEST NUMBER: 2.3.3.1 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Unexpected Components | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Result-Last for Class 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be sent if a Return Result-Last component is received for a Class 2 operation | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result-Last component can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
RETURN RESULT-LAST (i)
TC-L-REJECT ind.
REJECT (i)
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | | | | | RETURN RESULT-LAST (i) | TC-L-REJECT ind. | | | | | | REJECT (i) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RETURN RESULT-LAST (i) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-L-REJECT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a Class 2 operation invocation from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000001 (return result unexpected) + +NOTE – Omitted when no parameter is present. + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.3.3.2 | | Sheet: 1 of 2 | | | +| REFERENCE: 3.2.1/Q.774 | | | | | +| TITLE: Inopportune Behaviour; Unexpected Components | | | | | +| SUBTITLE: Return Result-Last for Class 4 | | | | | +| PURPOSE: To verify that a rejection can be sent if a Return Result-Last component is received for a Class 4 operation | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result-Last component can be generated | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKES req.

Image: Double-lined arrow pointing right

INVOKE (i) —————→
←————— RETURN RESULT-LAST (i)
TC-L-REJECT ind.

Image: Double-lined arrow pointing left

REJECT (i) —————→
| | | | | +| TEST DESCRIPTION | | | | | +| 1. | Initiate a Class 4 operation invocation from SP A to SP B. | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100010 (RETURN RESULT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000001 (return result unexpected) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------|------------|--|------------|-----------------------|--|--|---|--|--|-------------------|---|--|--|---|-----------------------------------|-------------------------|--|--|---|--|--|-------------------|---|--| +| TEST NUMBER: 2.3.3.3 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Unexpected Components | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Result Not-Last for Class 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be sent if a Return Result Not-Last component is received for a Class 2 operation | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result Not-Last component can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
=
INVOKE (i) -
< RETURN RESULT NOT-LAST (i)
TC-L-REJECT ind.
<
REJECT (i) -
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | = | | | INVOKE (i) | - | | | < | RETURN RESULT NOT-LAST (i) | TC-L-REJECT ind. | | | < | | | REJECT (i) | - | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| = | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | - | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RETURN RESULT NOT-LAST (i) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-L-REJECT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| < | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | - | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a Class 2 operation invocation from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000001 (return result unexpected) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------|------------|--|------------|-----------------------|--|--|--|--|--|-------------------|--|--|--|--|-----------------------------------|-------------------------|--|--|--|--|--|-------------------|--|--| +| TEST NUMBER: 2.3.3.4 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Unexpected Components | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Result Not-Last for Class 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be sent if a Return Result Not-Last component is received for a Class 4 operation | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Result Not-Last component can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
INVOKE (i)
RETURN RESULT NOT-LAST (i)
TC-L-REJECT ind.
REJECT (i)
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | | | | INVOKE (i) | | | | | RETURN RESULT NOT-LAST (i) | TC-L-REJECT ind. | | | | | | REJECT (i) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RETURN RESULT NOT-LAST (i) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-L-REJECT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a Class 4 operation invocation from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) + +Operation code: x (x represents a valid operation code) + +parameters (provided by the TC-User) + +##### RETURN RESULT NOT-LAST component in TSL message from SP B to SP A + +Component type tag: 10100111 (RETURN RESULT NOT-LAST) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Sequence tag: 00110000 (see Note) + +Sequence length: correct number of octets (see Note) + +Operation code tag: 00000010 (local) or 00000110 (global) (see Note) + +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) (see Note) + +Operation code: x (see Note) + +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) + +Component length: correct number of octets + +Invoke ID tag: 00000010 + +Invoke ID length: 00000001 + +Invoke ID: i + +Problem code tag: 10000010 (RETURN RESULT) + +Problem code length: 00000001 + +Problem code: 00000001 (return result unexpected) + +NOTE – Omitted when no parameter is present. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------------------|------------|--|------------|-----------------------|--|--|--------|--|--|-------------------|------------------------|--|--|------------------------|-------------------------|-------------------------|--|--|--------|--|--|-------------------|------------------------|--| +| TEST NUMBER: 2.3.3.5 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Unexpected Components | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Return Error for Class 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a rejection can be sent if a Return Error component is received for a Class 3 operation | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Error component can be generated | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL)
TC-INVOKE req.
=====>
INVOKE (i) —————————————————————>
<————————————————————— RETURN ERROR (i)
TC-L-REJECT ind.
<=====
REJECT (i) —————————————————————>
| | | SP A (CSL) | | SP B (CSL) | TC-INVOKE req. | | | =====> | | | INVOKE (i) | —————————————————————> | | | <————————————————————— | RETURN ERROR (i) | TC-L-REJECT ind. | | | <===== | | | REJECT (i) | —————————————————————> | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-INVOKE req. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| =====> | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVOKE (i) | —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <————————————————————— | RETURN ERROR (i) | | | | | | | | | | | | | | | | | | | | | | | | | +| TC-L-REJECT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| <===== | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REJECT (i) | —————————————————————> | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate a Class 3 operation invocation from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) +Operation code: x (x represents a valid operation code) +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Error code tag: 00000010 (local) or 00000110 (global) +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) +Error code: y +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Problem code tag: 10000011 (RETURN ERROR) +Problem code length: 00000001 +Problem code: 00000001 (unexpected return error) + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.3.6 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.1/Q.774 | | | +| TITLE: Inopportune Behaviour; Unexpected Components | | | +| SUBTITLE: Return Error for Class 4 | | | +| PURPOSE: To verify that a rejection can be sent if a Return Error component is received for a Class 4 operation | | | +| PRE-TEST CONDITIONS:
1) Arrange the TC-User stimulus such that an appropriate TSL message generated at SP A contains an Invoke component
2) Arrange the data at SP B such that a Return Error component can be generated | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE AND COMPONENT FLOW:
SP A (CSL) SP B (CSL) 
 TC-INVOKE req.    INVOKE (i) ------------------------------------>             <------------------------------------ RETURN ERROR (i)  TC-L-REJECT ind.    REJECT (i) ------------------------------------>

Image: Message flow diagram showing INVOKE from SP A to SP B, followed by RETURN ERROR from SP B to SP A, and finally REJECT from SP A to SP B.

  sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TC-INVOKE req.     A->>B: INVOKE (i)     B->>A: RETURN ERROR (i)     Note over A: TC-L-REJECT ind.     A->>B: REJECT (i)
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate a Class 4 operation invocation from SP A to SP B. | | +| 2. | CHECK A: WAS THE INVOKE COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 3. | CHECK B: WAS THE REJECT COMPONENT WITH CORRECT INFORMATION SENT BY SP A? | | +| 4. | CHECK C: WAS THE INVOCATION STATE MACHINE IDLE AT SP A? | | +| CHECK TABLE FOR COMPONENTS WITHIN MESSAGES | | | +| Component portion in TSL messages
Component portion tag: 01101100
Component portion length: correct number of octets
INVOKE component in TSL message from SP A to SP B
Component type tag: 10100001 (INVOKE)
Component length: correct number of octets
Invoke ID tag: 00000010
Invoke ID length: 00000001 (one octet)
Invoke ID: i (i represents an integer) | | | + +#### CHECK TABLE FOR COMPONENTS WITHIN MESSAGES + +Operation code tag: 00000010 (local) or 00000110 (global) +Operation code length: correct number of octets (e.g. 00000001 if x is one octet long) +Operation code: x (x represents a valid operation code) +parameters (provided by the TC-User) + +##### RETURN ERROR component in TSL message from SP B to SP A + +Component type tag: 10100011 (RETURN ERROR) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Error code tag: 00000010 (local) or 00000110 (global) +Error code length: correct number of octets (e.g. 00000001 if y is one octet long) +Error code: y +parameters (provided by the TC-User) + +##### REJECT component in TSL message from SP A to SP B + +Component type tag: 10100100 (REJECT) +Component length: correct number of octets +Invoke ID tag: 00000010 +Invoke ID length: 00000001 +Invoke ID: i +Problem code tag: 10000011 (RETURN ERROR) +Problem code length: 00000001 +Problem code: 00000001 (unexpected return error) + +| | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|---------------------|------------|--|------------|--|--|---------------------|------------------------------|--------|--|-----------------------|--|--|------|--|--|-------------------------|--------|--| +| TEST NUMBER: 2.3.4.1 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.1.2/Q.774 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Begin message with APDU AARE | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT aborts the transaction on reception of a Begin message containing a dialogue portion that carries an APDU 'AARE' | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
BEGIN (AARE)
Detect semantic error ←—————
TR-U-ABORT req
⇒⇒⇒⇒
ABORT (U) (ABRT) —————→
| | | SP A (CSL) | | SP B (CSL) | | | BEGIN (AARE) | Detect semantic error | ←————— | | TR-U-ABORT req | | | ⇒⇒⇒⇒ | | | ABORT (U) (ABRT) | —————→ | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | +| | | BEGIN (AARE) | | | | | | | | | | | | | | | | | | | +| Detect semantic error | ←————— | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT req | | | | | | | | | | | | | | | | | | | | | +| ⇒⇒⇒⇒ | | | | | | | | | | | | | | | | | | | | | +| ABORT (U) (ABRT) | —————→ | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a Begin message containing a dialogue response. | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: DOES SP A TRANSMIT THE EXPECTED ABORT MESSAGE WITH APDU 'ABRT'? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION | | | | | | | | | | | | | | | | | | | | | +|

Dialogue portion in Abort message

Dialogue portion tag: 01101011

Dialogue portion length: correct number of octets

External data type in dialogue portion

External type tag: 00101000

External length: correct number of octets

Object Identifier tag: 00000110

Object Identifier length: 00000111

Direct reference: H'00118605010101

Single ASN.1 type tag: 10100000

Single ASN.1 type length: correct number of octets

Dialogue PDU

Dialogue Abort tag: 01100100

Dialogue Abort length: 00000011

Abort Source tag: 10000000

Abort source length: 00000001

Abort source: 00000001 (dialogue service provider)

| | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Begin + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: 00011001 + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|------------------------|------------|--|------------|----------------------|--|--|---|--|--|---------------------|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|---|--|------------------------------|---|------------------------|------------------------|--|--|---|--|--|------------------------|--|--|---|--|--|-------------------------|---|--| +| TEST NUMBER: 2.3.4.2 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue confirmation with any APDU other than AARE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT aborts the transaction on reception of a Continue message containing a dialogue portion that carries an APDU 'AARQ' | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
TR-BEGIN req.
⇒
BEGIN (AARQ)
→
Detect semantic error ← CONTINUE (AARQ)
TR-P-ABORT ind.
⇐
TR-U-ABORT req.
⇒
ABORT (U) (ABRT) →
| | | SP A (CSL) | | SP B (CSL) | TR-BEGIN req. | | | ⇒ | | | BEGIN (AARQ) | | |
| | | | → | | Detect semantic error | ← | CONTINUE (AARQ) | TR-P-ABORT ind. | | | ⇐ | | | TR-U-ABORT req. | | | ⇒ | | | ABORT (U) (ABRT) | → | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⇒ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect semantic error | ← | CONTINUE (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⇐ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ⇒ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (U) (ABRT) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to confirm the dialogue with a dialogue portion containing an AARQ APDU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: DOES THE DIALOGUE PORTION IN THE ABORT MESSAGE CONTAIN APDU 'ABRT'? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE DIALOGUE AT SP A HAS BEEN TERMINATED. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Request tag: 01100000 + +Dialogue Request length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: any object identifier + +##### Dialogue portion in Abort message + +Dialogue portion tag: 01101011 + +Dialogue portion length: 00010010 + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: 00010000 + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: 00000101 + +##### Dialogue PDU + +Dialogue Abort tag: 01100100 + +Dialogue Abort length: 00000011 + +Abort Source tag: 10000000 + +Abort source length: 00000001 + +Abort source: 00000001 (dialogue service provider) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------|--|------------|----------------------|--|--|--|--|--|---------------------|--|--|------------------------------|--|------------------------|------------------------|--|--|--|--|--|------------------------|--|--|--|--|--|-------------------------|--|--| +| TEST NUMBER: 2.3.4.3 | | Sheet: 1 of 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 3.2.2.1/Q.774 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dialogue confirmation with APDU ABRT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an IUT aborts the transaction on reception of a Continue message containing a dialogue portion that carries an 'ABRT' APDU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
TR-BEGIN req.
BEGIN (AARQ)
Detect semantic error CONTINUE (ABRT)
TR-P-ABORT ind.
TR-U-ABORT req.
ABORT (U) (ABRT)
| | | SP A (CSL) | | SP B (CSL) | TR-BEGIN req. | | | | | | BEGIN (AARQ) | | | Detect semantic error | | CONTINUE (ABRT) | TR-P-ABORT ind. | | | | | | TR-U-ABORT req. | | | | | | ABORT (U) (ABRT) | | | +| SP A (CSL) | | SP B (CSL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-BEGIN req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BEGIN (AARQ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Detect semantic error | | CONTINUE (ABRT) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-P-ABORT ind. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TR-U-ABORT req. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ABORT (U) (ABRT) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send a Begin message containing a dialogue portion. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Arrange for SP B to confirm the dialogue with a dialogue portion containing a ABRT APDU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: DOES THE DIALOGUE PORTION IN THE ABORT MESSAGE CONTAIN APDU 'ABRT'?
(refer to test number 2.3.4.2 check table for ABRT). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT THE DIALOGUE AT SP A HAS BEEN TERMINATED. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: 00010010 + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: 00010000 + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: 00000101 + +##### Dialogue PDU + +Dialogue Abort tag: 01100100 + +Dialogue Abort length: 00000011 + +Abort Source tag: 10000000 + +Abort source length: 00000001 + +Abort source: 00000001 (dialogue service provider) + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------| +| TEST NUMBER: 2.3.4.4 | | Sheet: 1 of 2 | +| REFERENCE: 3.2.2.1/Q.774 | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | +| SUBTITLE: Presence of a Dialogue Portion APDU in the active state. | | | +| PURPOSE: To verify that an IUT aborts the transaction on reception of a Continue message containing a dialogue portion that carries an ’AARE’ APDU | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state and test case 2.1.9.1.2 has to be executed successfully | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL)

← BEGIN (AARQ)
TR-BEGIN ind.

TR-CONTINUE req.

CONTINUE (AARE) →

← CONTINUE (AARE)
TR-P-ABORT ind.

TR-U-ABORT req.

ABORT (U) (ABRT) →


| | | +| TEST DESCRIPTION | | | +|
  1. Arrange for SP B to send a Begin message with dialogue request to SP A.
  2. Arrange for SP A to confirm the dialogue.
  3. Arrange for SP B to send a Continue msg containing a dialogue portion carrying an AARE APDU.
  4. CHECK A: VERIFY THAT THE IUT AT SP A TERMINATES THE TRANSACTION.
| | | + +310 Recommendation Q.787 (09/97) + +#### CHECK TABLE FOR INFORMATION ELEMENTS WITHIN DIALOGUE PORTION + +##### Dialogue portion in Continue message + +Dialogue portion tag: 01101011 + +Dialogue portion length: correct number of octets + +##### External data type in dialogue portion + +External type tag: 00101000 + +External length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: 00000111 + +Direct reference: H'00118605010101 + +Single ASN.1 type tag: 10100000 + +Single ASN.1 type length: correct number of octets + +##### Dialogue PDU + +Dialogue Response tag: 01100001 + +Dialogue Response length: correct number of octets + +Application context tag: 10100001 + +Application context length: correct number of octets + +Object Identifier tag: 00000110 + +Object Identifier length: correct number of octets + +Direct reference: same octets as in AARQ + +Result tag: 10100010 + +Result length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Result value: 00000000 (Accepted) + +Result source diagnostic tag: 10100011 + +Result source diag. length: 00000101 + +Dialogue Service User tag: 10100001 + +Dialogue Service User length: 00000011 + +INTEGER type tag: 00000010 + +INTEGER length: 00000001 + +Dialogue service user value: 00000000 (NULL) + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.4.5 | | Sheet: 1 of 1 | +| REFERENCE: 3.2.2.1/Q.774 | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | +| SUBTITLE: Unidirectional message with unexpected abstract syntax | | | +| PURPOSE: To verify that an IUT discards an UNIDIRECTIONAL message containing a dialogue portion that is referring to an unexpected abstract syntax | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)
Detect error ← UNIDIRECTIONAL (AARQ)
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send a Unidirectional message containing a dialogue portion but referring to the structured dialogue abstract syntax. | | +| 2. | CHECK A: DOES SP A DISCARD THE MESSAGE? | | +| CHECK TABLE FOR INFORMATION ELEMENTS WITHIN MESSAGES | | | +|

Dialogue portion in Unidirectional message

  • Dialogue portion tag: 01101011
  • Dialogue portion length: correct number of octets

External data type in dialogue portion

  • External type tag: 00101000
  • External length: correct number of octets
  • Object Identifier tag: 00000110
  • Object Identifier length: 00000111
  • Direct reference: H'00118605010101 (structured dialogue abstract syntax)
  • Single ASN.1 type tag: 10100000
  • Single ASN.1 type length: correct number of octets

Dialogue PDU

  • Dialogue Request tag: 01100000
  • Dialogue Request length: correct number of octets
  • Application context tag: 10100001
  • Application context length: correct number of octets
  • Object Identifier tag: 00000110
  • Object Identifier length: correct number of octets
  • Direct reference: any object identifier
| | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.3.4.6 | | Sheet: 1 of 1 | +| REFERENCE: 3.2.2.1/Q.774 | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | +| SUBTITLE: Unexpected dialogue portion in Continue message | | | +| PURPOSE: To verify that an IUT aborts the transaction on reception of a Continue message which includes a dialogue portion while no dialogue portion was sent in the Begin message | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A (CSL) SP B (CSL)

TR-BEGIN req.
→
BEGIN ————————————————→
Detect error ←———————————————— CONTINUE (AARE)

TR-P-ABORT ind.
←
TR-U-ABORT req
→
ABORT (U) (ABRT) ————————————————→
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP A to send a Begin message (without dialogue portion) | | +| 2. | Arrange for SP B to confirm the dialogue with a dialogue portion containing an AARE APDU. (Refer to check table of test number 2.3.4.4.) | | +| 3. | CHECK A: DOES THE DIALOGUE PORTION IN THE ABORT MESSAGE CONTAIN APDU 'ABRT'?
(Refer to check table of test number 2.3.4.2.) | | +| 4. | CHECK B: VERIFY THAT THE DIALOGUE AT SP A HAS BEEN TERMINATED. | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------| +| TEST NUMBER: 2.3.4.7 | | Sheet: 1 of 1 | +| REFERENCE: 3.2.2.1/Q.774 | | | +| TITLE: Inopportune Behaviour; Dialogue Portion | | | +| SUBTITLE: Missing dialogue portion in Continue message | | | +| PURPOSE: To verify that an IUT aborts the transaction on reception of a Continue message without dialogue portion while a dialogue portion was sent in the Begin message | | | +| PRE-TEST CONDITIONS: SP A (TSL) and SP B (TSL) are to be in the idle state | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:
SP A (CSL) SP B (CSL) 

 sequenceDiagram     participant A as SP A (CSL)     participant B as SP B (CSL)     Note over A: TR-BEGIN req.     A->>B: BEGIN (AARQ)     B->>A: CONTINUE     Note over A: Detect error     Note over A: TR-P-ABORT ind.     Note over A: TR-U-ABORT req.     A->>B: ABORT (U) (ABRT)

| | | +| TEST DESCRIPTION
  1. 1. Arrange for SP A to send a Begin message containing a dialogue portion.
  2. 2. Arrange for SP B to confirm the dialogue with a Continue without a dialogue portion.
  3. 3. CHECK A: VERIFY THAT THE DIALOGUE AT SP A HAS BEEN TERMINATED.
| | | + +314 Recommendation Q.787 (09/97) + + + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.8-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.8-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..42d5bba82dc9e97e75276f1a354f96be62586059 --- /dev/null +++ b/marked/Q/T-REC-Q.8-198811-I_PDF-E/raw.md @@ -0,0 +1,716 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.8** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**SIGNALLING SYSTEMS TO BE USED FOR +INTERNATIONAL MANUAL AND AUTOMATIC +WORKING ON ANALOGUE LEASED +CIRCUITS** + +**ITU-T Recommendation Q.8** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.8 was published in Fascicle VI.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## Recommendation Q.8 + +# SIGNALLING SYSTEMS TO BE USED FOR INTERNATIONAL MANUAL AND AUTOMATIC WORKING ON ANALOGUE LEASED CIRCUITS + +The CCITT, + +*considering* + +(a) that standardization of signalling systems to be used for international manual and automatic working on analogue leased circuits brings advantages to Administrations, manufacturers and users; + +(b) that manual and automatic operation of international leased circuits require different technical arrangements; + +(c) that the standard signalling systems set out in Recommendation Q.7 are primarily intended for the public service; + +(d) that the national circuit sections of international leased circuits may need to conform to local regulations of the Administration(s) concerned; + +(e) that the method of signalling will be affected by the type of transmission and vice versa; + +(f) that the method of signalling will be affected by the characteristics of the service(s) carried on the circuit; + +*recommends* + +that Administrations should use for manual international analogue leased circuits the standard signalling system specified in § 1 below; + +and *draws the attention* of Administrations + +to the guidance clauses and related annexes concerning automatic signalling on international analogue leased circuits, as set out in § 2 below. + +## **1 Signalling on manual international analogue leased circuits** + +1.1 Signalling shall take place by the transmission of a single frequency signalling current, analogous to the signalling method used in the international manual service and specified in Recommendations Q.1 and Q.2. + +1.2 The signalling current shall have a nominal frequency of either 2280 Hz or 2600 Hz. One of these frequencies shall be chosen for both directions of transmission by bilateral agreement between the Administrations concerned. Failing such an agreement, each Administration shall determine which of the two frequencies it wishes to receive. + +1.3 The duration of the transmitted tone shall be between 300 ms and 2 seconds. The upper limit of 2 seconds allows the partial use of signalling equipment designed for 500/20 Hz working according to Recommendation Q.1. + +1.4 The signal recognition time shall be between 100 ms and 200 ms: + +- The minimum duration of 100 ms has been chosen so as to avoid the recognition of false signals due to imitation by speech currents; +- The maximum duration of 200 ms has been chosen so as to allow a safe margin between this time and the minimum transmission time. + +Exceptionally, a maximum signal recognition time of 1200 ms may be used where it is known that the transmitted signal has a 2 second duration. Such arrangements allow the partial use of signalling equipment designed for 500/20 Hz working according to Recommendation Q.1. + +1.5 Other technical clauses for 2280 Hz signalling are set out in Annex A to this Recommendation. + +1.6 Other technical clauses for 2600 Hz signalling are set out in Annex B to this Recommendation. + +## 2 **Signalling on automatic international analogue leased circuits** + +2.1 This section refers to international analogue leased circuits employing automatic signalling. Such circuits are considered to form part of a private network extending across international frontiers and linking exchanges carrying out the switching function in a private network. The exchanges may be Private Automatic Branch Exchanges (PABXs). Private tandem exchanges, or switching equipments provided by the Administration to carry out switching functions in a private network. Where the exchanges are privately owned, part of the signalling function may be provided by the Administration. + +This Recommendation does not cover the case of international leased circuits directly connecting subscriber lines to remote switching equipment. However, most of the following text is equally applicable to this case. Annex D, § D.3 and Annex E give further information on such signalling. + +2.2 Many Administrations have regulations concerning the use of signalling frequencies on leased circuits and these may apply to international leased circuits also. These regulations are intended to ensure non-interference between parts of the voice spectrum used for signalling and those available for use by subscriber apparatus. This does not create exceptional difficulties for manual working since the frequencies used (2280 Hz, 2600 Hz) can be converted to other acceptable frequencies at the Terminal International Centre. However, for automatic circuits it should be the aim to provide an uninterrupted path between the ends of the leased circuit. + +Some World regions have existing or proposed signalling systems which meet the regulatory arrangements in those regions and a summary of two such systems are given in Annexes C and D to this Recommendation. Administrations are invited to note these existing systems that may meet their needs for automatic signalling on analogue leased circuits. + +2.3 In order to reduce the cost of providing leased circuits some inter-regional leased circuits may be provided with various forms of bandwidth economizing systems, such as speech interpolation systems and digital voice compression. These systems usually have their own internal digital signalling capability and these are not covered by this Recommendation, except that the effect that speech interpolation equipment has on analogue signalling is discussed. + +2.4 In the most general case, the choice of signalling and transmission in a private network will be determined by the availability of suitable equipment, and by the decisions of the network user and the Administrations concerned. The following sections give guidance on transmission factors which affect signalling, the important characteristics of signalling systems which could affect the choice of transmission medium, and the interaction between signalling and non-voice services. + +## 2.5 *Transmission factors* + +2.5.1 Recommendations for the transmission characteristics of leased circuits forming part of a private telephone network are given in Recommendation G.171. + +2.5.2 Where large groups of circuits are concerned and the transmission multiplex equipment is on the renter's premises, it is advisable to protect against the effects of faulty transmission on groups of circuits. Recommendation Q.33 gives details of such measures. + +### 2.5.3 *Satellite systems* + +- i) Some signalling systems will not function correctly over satellite links since the long propagation delay ( $270 \pm 20$ ms one way) exceeds that assumed by the line signalling specification. Amongst the standard systems for public telephony, Signalling System R2 incorporates special precautions because of this delay. In addition the speed of multi-frequency compelled interregister signalling is affected, which may cause undesirable post-dialling delay. If signalling systems based on R2 are used in private networks then reference should be made to information contained in Recommendations Q.7 and Q.400 to Q.490. + +- ii) Consideration should be given to the possibility that two satellite links may, in some cases, need to be connected in tandem. Means to prevent this may also need to be considered. (Further information is contained in Recommendations E.171, G.131, Q.14 and Q.115.) +- iii) If satellite links via Time Division Multiple Access Systems with Digital Speech Interpolation (TDMA/DSI) are used, then guidance on circuit supervision signalling arrangements can be found in Recommendation Q.33. However, Digital Non-Interpolated (DNI) channels are usually assigned for leased circuits and these exhibit fewer problems for signalling. +- iv) If satellite links via Single Channel Per Carrier (SCPC) systems are used, then it should be noted that these systems employ voice activated carriers for telephony type circuits. On transmission systems of this type, the use of tone-on-idle signalling systems should be avoided, since such signalling systems would override the voice activation feature of SCPC systems. + +### 2.5.4 *Echo control* + +Paragraph 9 of Recommendation G.171 should be observed concerning the location of echo control devices where these are required. All analogue channel associated signalling systems operate more effectively if the line signal receiver, and often the line signal sender also, are located on the line side of any echo control device. In addition, some signalling systems require echo control devices to be locally disabled during interregister signalling. For these reasons, the echo control device should be located at the private renter's premises and not the terminal international centre. + +### 2.5.5 *Speech interpolation* + +Some signalling systems may not be compatible with speech interpolation systems for the following + +reasons: + +- i) Signalling systems employing continuous state tone signalling will cause permanent operation of the speech detectors and thus permanent trunk to channel association. This prevents the correct operation of the interpolation process. +- ii) The speech interpolation equipment may not be transparent to out-band signalling. +- iii) The speech interpolation equipment may cause excessive clipping of pulse signals resulting in their non-recognition by the distant signalling equipment. +- iv) The speech interpolation equipment may not provide sufficient speech detector hangover to allow the successful transmission of some signals, e.g. en bloc multi-frequency signals. + +Information on the characteristics of some speech interpolation systems is given in Supplement No. 2 of Fascicle VI.1, though different systems may also be used on leased circuits. + +In the case of continuous state tone signalling, compatibility with speech interpolation systems can be achieved by converting the tone signalling to interface with any in-built signalling capability the system may provide. If the transmission difficulty only exists in the interregister signalling phase, then this can be obviated by the simultaneous transmission of a speech interpolation locking tone, e.g. 2800 Hz. + +Note that fully compelled signalling techniques are compatible with speech interpolation systems. + +## 2.6 *Characteristics of signalling systems* + +### 2.6.1 *Line signalling systems* + +Analogue line signalling systems can be divided into in-band and out-band systems. In addition, two signalling techniques may be employed: pulse signalling or continuous signalling. + +Information on the comparative advantages of in-band and out-band systems can be found in Recommendation Q.20. General requirements for signalling equipment are contained in Recommendations Q.112 to Q.114. + +- i) *In-band systems* + +According to Recommendation Q.22, signalling frequencies above 2000 Hz should be used (but see also §§ 2.7.1 and 2.7.2 below). + +The preferred power level for in-band signalling is -9 dBm0 for pulsed signals and -20 dBm0 for continuous signals (also see Recommendation Q.16). + +In-band systems require the use of a guarding characteristic to prevent false operation of the signalling equipment by speech currents. Even so, occasional receiver misoperation by speech can occur, and thus in the speech phase a suitable minimum signal recognition time should be chosen. + +In-band systems require the use of splitting techniques in order to confine the signalling frequencies to the link concerned, and this has an impact on minimum signal recognition times. Further information can be found in Recommendation Q.25. + +If the leased circuit contains a digital transmission system in the terminal national section and this connects directly to a renter's digital PABX using a first order PCM system, then the detection of in-band signalling requires digital filtering techniques. + +#### ii) *Out-band systems* + +Recommendation G.171 does not provide for the use of out-band signalling on leased circuits. Because of the frequencies used, out-band signalling requires the use of a transparent 4 kHz bandwidth between the two signalling equipments. Part of the signalling equipment is usually provided within the transmission equipment. + +Nevertheless, where the required transmission facilities can be assured, out-band signalling may provide a useful alternative to in-band signalling. Preferred signalling frequencies and power levels for out-band signalling are set out in Recommendation Q.21. + +##### iii) *Pulsed signalling* + +Pulsed signalling allows a greater signal repertoire than continuous signalling, but requires more complex signal recognition arrangements. In general, the signalling tone is recognized by the signal receiver but requires persistence checking and correlation with the circuit state before the signal is validated. + +##### iv) *Continuous signalling* + +Usually continuous signalling is arranged to operate with "*tone-on-idle*". Such systems have the inherent advantage of allowing immediate identification of circuit availability. + +Since only two signal states are available in each direction, the possible signal repertoire is lower than pulsed systems, but recognition arrangements are simpler. A single persistence timing is usually provided to validate changes of signalling state. + +Where continuous in-band signalling uses the "*tone-on*" condition after the interregister signalling phase, means must be provided to prevent the calling or called parties from hearing the signalling tone without undue interference to the transmission of speech currents and tones. A band stop filter as used in Signalling System R1 (see Recommendation Q.313, § 2.3.4) may be suitable. Alternatively, to obviate these difficulties, pulsed signalling could be used in the speech phase. + +### 2.6.2 *Interregister signalling* + +The following types of interregister signalling may be suitable for use on leased circuits: + +#### i) *Decadic signalling* + +Signalling takes place using the same frequency and sender/receiver equipment as the line signalling. Forward signals are composed of a sequence of tone pulses analogous to subscriber line signalling employing rotary dials. Backward signals may not always be provided, but *proceed-to-send* and *address complete* signals can be used to advantage. + +#### ii) *Multi-frequency signalling* + +Multi-frequency (MF) signalling has the advantage of greater speed and signal repertoire than decadic systems. To provide both an adequate repertoire and signalling reliability, signals are composed of two frequencies from a set of 4, 5, 6 or 8 frequencies. Different frequencies may be used for signalling in the backward direction. The frequencies used for MF signalling should lie below 2000 Hz in order that they do not interfere with in-band line signalling. + +MF systems may transmit signals in pulse form, or in a compelled sequence with signals in the opposite direction. The preferred signal power level is -9 dBm0 for each constituent tone. + +Three existing MF systems may be suitable as the basis for signalling on leased circuits. These are: + +- 1) The dual tone multi-frequency system as specified in Recommendation Q.23 and modified to act as an interregister signalling system. (See also Recommendation Q.24.) +- 2) Signalling System R1. See Recommendations Q.7 and Q.310 to Q.331. +- 3) Signalling System R2. See Recommendations Q.7 and Q.400 to Q.490. + +### 2.6.3 *Overall signalling repertoire* + +Consideration should be given to providing a set of signals capable of being adapted for different situations to provide a signal capability for extending the scope of PABX supplementary services to encompass the private network as a whole, and to provide other network facilities. This is best achieved by the inclusion in the signalling repertoire of a set of auxiliary signals that are separate from the basic call set-up and supervisory signals and can therefore be allocated in a flexible manner to the required function. + +### 2.6.4 *Position of signalling equipment* + +Normally all signalling equipment for automatic leased circuits will be located at the renter's premises. Some Administrations may wish or may be able to provide part of the signalling equipment at the Terminal National Centre or the Terminal International Centre. In these cases, suitable signalling arrangements need to be made to interconnect the exchange at the renter's premises with the remote elements of the signalling equipment. This will be determined by the Administration concerned. Any echo control device could in this case also be remote, but see Recommendation G.171, § 9.2. + +## 2.7 *Interaction between signalling and non-voice services* + +As well as normal speech transmission, leased circuits can be used to provide for other types of service (see Recommendation M.1015). + +The most common types are: + +- Voice-frequency telegraphy, +- Data transmission, +- Facsimile, +- Phototelegraphy. + +Since these services use in-band frequencies, there is a possibility of interaction with signalling, and the following general guidance is given below. + +### 2.7.1 *Voice-frequency telegraphy* + +Where voice-frequency telegraphy is carried on a telephone-type leased circuit it will be by one of two methods: + +- *Alternate use* (see Recommendation M.1015). The circuit is switched at both ends between the telephone equipment and the photo-telegraph equipment. +- Subdivision of the frequency band between telephone and telegraph services. (See Recommendation H.34.) + +In the former case, the signalling equipment is disconnected during telegraph use and no interaction can take place. (Outgoing telephone circuits should be removed from service and blocked prior to service switching). + +In the latter case, the in-band telephone signalling must be confined to frequencies below 2500 Hz since the attenuation at higher frequencies due to the separation filter cannot provide a reliable signalling path. + +### 2.7.2 Data transmission + +Data transmission systems for use over leased circuits are specified in Recommendations V.16, V.19 to V.23, V.26 and V.27. These systems do not interact with the Standard Systems for the following reasons: + +- i) In most cases, the data carriers lie below 2000 Hz and thus below the range for voice frequency line signalling. However, when the carrier is modulated, energy may be present in the signalling band but false receiver operation is prevented by there being at all times a greater energy in the pass-band of the guard circuit. +- ii) In some cases, the carriers do lie in the signalling band above 2000 Hz, but with constant phase modulation the guard circuit will operate as outlined in i) above. In the case of 1200 bits/sec duplex transmission according to Recommendation V.22, a guard tone of 1800 Hz is required in order to ensure guard circuit operation. + +For signalling systems on automatic leased circuits therefore, providing the signalling frequency is above 2000 Hz and that a guard circuit with a pass-band covering the common data carrier frequencies is used, no problems are foreseen with interaction. + +In order that duplex data transmission can take place on circuits equipped with echo control devices, the data set will transmit a tone disabling signal with the following characteristics (see also Recommendation G.164). + +$2100 \pm 15$ Hz at a level of $-12 \pm 6$ dBm0 + +Duration greater than 400 ms + +In order that false operation of signalling equipment does not take place, it is essential that the lowest possible operating frequency of the signalling receiver be above the highest possible tone disabling frequency. This requires that the lowest usable signalling frequency be higher than the 2000 Hz referred to above in § 2.6.1. + +For example: + +| | | | +|--------------------------------------------------|---|---------| +| Highest tone disabling frequency | = | 2115 Hz | +| Allowance for frequency deviation in channel | = | 5 Hz | +| Margin of safety | = | 30 Hz | +| Typical maximum receiver deviation for operation | = | 75 Hz | +| | |
| +| Giving | | 2225 Hz | + +Thus on the basis of this example, frequencies above 2225 Hz should be suitable for signalling. + +Since the tone disabling circuit of echo control devices may respond in the range 1900-2350 Hz, the unintentional disabling of echo control devices may occur during signalling if this frequency range is used. However, this is not considered detrimental since the echo control device serves no essential function during the time when signalling tones are present on the circuit. + +### 2.7.3 Facsimile + +Facsimile apparatus for use on telephone circuits are specified in Recommendations T.2, T.3, T.4 and T.10. + +- i) *Group 1 apparatus* (Recommendation T.2) + +Since leased circuits in an automatic private network form part of a switched connection, the centre frequency $f_0$ should be 1700 Hz as used on the public switched network. This implies, for frequency modulation, a transmitted frequency between 1300 Hz (white) and 2100 Hz (black). With a maximum frequency deviation of 32 Hz, and by analogy with the calculations in § 2.7.2 above, frequencies above 2242 Hz should be suitable for signalling. This must be carefully observed since facsimile transmission may result in a single tone for a significant period, and without energy in the pass-band of the guard circuit. + +#### ii) *Group 2 apparatus* (Recommendation T.3) + +The transmission method for Group 2 machines uses vestigial sideband amplitude modulation. The 2100 Hz carrier frequency is permanently modulated and the effect of this and the vestigial sideband filter is such that the energy spectrum of the transmitted signal is biased towards frequencies in the pass-band of the guard circuit and receiver misoperation should not occur. + +#### iii) *Group 3 apparatus* (Recommendation T.4) + +The transmission method for Group 3 machines uses the data transmission method of Recommendation V.27 *ter* or V.29. False operation should not occur for the reasons described in § 2.7.2 above. + +### 2.7.4 *Phototelegraphy* + +For Phototelegraphy on leased circuits, Recommendations T.1 and T.11 apply. + +The transmitted centre frequency is 1900 Hz with deviation (in the case of frequency modulation) from 1500 Hz (white) to 2300 Hz (black). For amplitude modulated systems the carrier may be between 1300 and 1900 Hz. + +In many cases a phototelegraph circuit is derived by *alternate use* where the telephone signalling equipment is disconnected. However, where automatic switching of phototelegraph circuits is required, the guidance of Recommendation T.11, § 3.2 applies; that is, a guard tone (*blocking signal*) should be transmitted in order to prevent false receiver operation on single-frequency signalling systems. + +#### 2.7.5 *Interference of service signals* + +With the systems referred to in §§ 2.7.1-2.7.4 above, the precautions included to prevent false recognition of service signals will usually be reliable. However, where the precautions are dependent on the statistical probability of the transmitted power spectrum operating the guard circuit, there is always a small risk of receiver operation for very short periods (in a similar fashion to the occasional false operation by speech). It should be noted that if such operation persists long enough, then the receiver splitting function will operate and thus cause a discontinuity in the service signal. This should be borne in mind when deciding the minimum receiver splitting time. In the call connected phase it is advisable that the minimum tone recognition time for a valid signal should be chosen such that occasional short receiver operation does not cause a change of signalling state. + +# ANNEX A + +(to Recommendation Q.8) + +## **Technical clauses for 2280 Hz signalling on manual circuits** + +### A.1 *Signal sender* + +#### A.1.1 *Signalling frequency* + +$2280 \pm 5$ Hz. + +#### A.1.2 *Transmitted signal level* + +$-13 \pm 1$ dBm0. + +The permissible noise level measured at the output of the signal sender shall be as low as practicable, but in any event at least 35 dB below signal level. + +The level of leak current transmitted to line should be at least 50 dB below signal level. + +### A.2 *Signal receiver* + +#### A.2.1 *Operating limits* + +The signal receiver must operate satisfactorily if a signal is received satisfying the following conditions: + +- the frequency received is within $2280 \pm 15$ Hz; +- the absolute power level $N$ of each unmodulated signal shall be within the limits $(-19 + n \leq N \leq -7 + n)$ dBm where $n$ is the relative power level at the receiver input. + +The limits give a margin of $\pm 6$ dB on the nominal absolute power level of the 2280 Hz signal received at the receiver input, to allow for variations in transmission conditions on the international circuits. + +#### A.2.2 *Non-operate conditions* + +- Selectivity* + +The signal receiver shall not operate on a signal having an absolute power level at the receiving end within the limits specified in § 2.1 b) when the frequency is outside: $2280 \pm 75$ Hz. + +- Maximum sensitivity of the signal receiver* + +The signal receiver shall not operate on a signal in the range $2280 \pm 15$ Hz whose absolute power level at the point of connection of the receiver is $(-29 - 13 + n)$ dBm, $n$ being the relative power level at this point. + +#### A.2.3 *Guard circuit* + +##### A.2.3.1 *Efficiency of the guard circuit* + +The signal receiver must be protected by a guard circuit against false operation due to speech currents, circuit noise, or other currents of miscellaneous origin circulating in the line. + +The purpose of the guard circuit is to prevent signal imitation, and operation of the splitting device by interfering speech. + +To minimize signal imitation by speech current it is advisable that the guard circuit be tuned as follows: + +To minimize signal interference by low-frequency noise it is advisable that the response of the guard circuit fails off towards the lower frequencies and that the sensitivity of the guard circuit at 200 Hz is at least 10 dB less than at 1000 Hz. + +An indication of the efficiency of the guard circuit is given by the following: + +- during 10 hours of speech, normal speech currents should not, on average, cause more than one false operation of the receiver lasting more than the minimum recognition time of the signal; +- the number of false splits of the speech path caused by speech currents should not cause an appreciable reduction in the transmission quality of the circuit. + +##### A.2.3.2 *Guard circuit limits* + +Considering: + +- that unweighted noise of a level $-40$ dBm0 and uniform spectrum energy may arise on the longest international circuit; +- that an oversensitive guard circuit might give rise to signalling difficulties. + +It is recommended that, the guard circuit shall not operate in the presence of noise at a level of less than $-35$ dBm0 and uniform spectral energy over the frequency range 300-3400 Hz. + +### A.3 *Splitting arrangements* + +Sending and receiving line splitting shall be provided. + +#### A.3.1 *Sending line split* + +- a) the sending line transmission path of the signalling termination shall be disconnected 30-50 ms before a voice-frequency signal is sent over the circuit; +- b) the sending line transmission path of the signalling termination will not be reconnected for 30-50 ms following the end of the sending of a voice-frequency signal over the circuit. + +#### A.3.2 *Receiving line split* + +- a) the receiving line transmission path of the signalling termination shall be split when the 2280 Hz signal is received. The splitting time should be less than 20 ms; +- b) the split must be maintained for the duration of the signal but must cease within 25 ms of the cessation of the 2280 Hz signal; +- c) the splitting device may be any suitable arrangement for example, physical line disconnection, insertion of a bandstop filter, etc. The level of leak current transmitted to the subsequent circuit should be at least 40 dB below the received signal level. + +# ANNEX B + +(to Recommendation Q.8) + +## **Technical clauses for 2600 Hz signalling on manual circuits** + +### B.1 *Signalling sender* + +#### B.1.1 *Signalling frequency* + +$2600 \pm 5$ Hz. + +#### B.1.2 *Transmitted signal level* + +The transmitted signal level shall be $-8 \pm 1$ dBm0 for the duration of the signal or for a minimum of 300 ms (whichever is shorter) and for a maximum of 550 ms after which the level of the signal shall be reduced to $-20 \pm 1$ dBm0. + +#### B.1.3 *Signal frequency leak* + +The level of signal frequency leak power transmitted to the line should not exceed -70 dBm0, during the tone-off condition. + +#### B.1.4 *Extraneous frequency components* + +The total extraneous frequency components accompanying a tone signal should be at least 35 dB below the fundamental signal power. + +#### B.1.5 *Sending line split* + +The following splitting arrangements are required when transmitting line signals to prevent incorrect operation of the receiving equipment: + +- a) when a tone-on signal is to be transmitted, the sending line transmission path shall be split, within an interval from 20 ms before, to 5 ms after tone is applied to the line, and remain split for a minimum of 350 ms and a maximum of 750 ms; +- b) when a tone-off signal is to be transmitted, the sending line transmission path shall be split, within an interval from 20 ms before, to 5 ms after tone is removed from the line, and remain split for a minimum of 75 ms and a maximum of 160 ms after the tone is removed. + +Further details are given in § 2.2.6 of Recommendation Q.312. + +### B.2 *Signal receiver* + +#### B.2.1 *Operating limits* + +The receiving equipment shall operate on a received tone signal that meets the conditions listed below: + +- 2600 $\pm$ 15 Hz; +- to ensure proper operation in the presence of noise, the signal level of the initial portion of each tone-on signal is augmented by 12 dB. The absolute power level of the signal shall be within the limits $(-27 + n \leq N \leq -1 + n)$ dBm where $n$ is the relative power level at the input to the receiving equipment. + +#### B.2.2 *Non-operate limits*EF + +- The receiving equipment shall neither operate on signals originating from subscriber stations (or other sources) if the total power in the band from 800 Hz to 2450 Hz equals or exceeds the total power present at the same time in the band from 2450 Hz to 2750 Hz as measured at the station, nor degrade these signals. +- The receiving equipment shall not operate on any tone or signal whose absolute power level at the point of connection of the receiving equipment is $(-17 - 20 + n)$ dBm or less, $n$ being the relative power level at this point. + +On average during 10 hours of speech, normal speech currents should not cause more than one operation lasting more than 50 ms. + +#### B.2.3 *Receiving line split* + +To prevent line signals of the signalling system from causing disturbances to signalling systems on subsequent circuit sections, the receiving line transmission path should be split when the signal frequency is received to ensure that no portion of any signal exceeding 20 ms duration may pass out of the circuit section. + +This should be achieved by use of a bandstop filter in which case the level of signal leak current transmitted to the subsequent circuit section with the bandstop filter inserted should be at least 35 dB below the received signal level. In addition, the bandstop filter must not introduce more than 5 dB loss at frequencies 200 Hz or more above or below the midband frequency nor more than 0.5 dB loss at frequencies 400 Hz or more above or below the midband frequency. + +The receiving line split must be maintained for the duration of the incoming tone signal, but must cease within 300 ms of tone removal. + +*Note* - In some existing designs, the initial cut may be a physical line disconnection but the filter must be inserted within 100 ms of tone reception. + +# ANNEX C + +(to Recommendation Q.8) + +## **The standard European inter-PABX signalling system** + +### C.1 *Introduction* + +Recognizing the increasing use of leased lines between private automatic branch exchanges (PABXs) in the European telecommunication networks, a specification has been developed covering the need for signalling on such lines. The system emerged is called Signalling System L1. Distinction is made between line signalling (call supervisory signals) and interregister signalling (set-up including routing and additional service control). Taking into account different applications, existing interregister signalling techniques have been adopted for use with the basic line signalling as follows: + +- decadic pulsing (DP); +- multi-frequency push-button (MFPB) type signalling; +- System R2 multi-frequency code (MFC) type signalling. + +### C.2 *Principles and field of application* + +C.2.1 The line signalling system is to provide automatic and semi-automatic working between PABXs in different countries. + +C.2.2 The signalling system is a single voice frequency (1 vf) tone-on-idle line signalling system using a signalling frequency of 2280 Hz. The use of voice frequency signals renders the system suitable for all voice transmission media, except those using speech interpolation. + +C.2.3 The system is intended for use on bothway inter-PABX circuits, with first party clearing. + +C.2.4 Either decadic pulsing or multi-frequency interregister signalling may be used with the line signalling system. The provision of particular line signals will depend upon the requirements of the associated interregister signalling system. + +C.2.5 The system operates on a four-wire basis, forward and backward signals being segregated by utilizing the four-wire circuits as two separate signalling paths. + +C.2.6 In addition to the application or removal of signalling frequency (tone-on and tone-off) in continuous form, the transmission of pulses of signalling frequency is applied. + +C.2.7 When in the idle condition, the signalling frequency applied to the line is reduced in power level to conform to the transmission loading requirements of Recommendation Q.15. + +C.2.8 The line signalling operates on a link-by-link basis and may be used to establish a multi-link tandem connection using one or more private automatic exchange(s) as a transit switch. In accordance with Recommendation Q.25 sending fine and receiving line splitting arrangements are provided so that signals are contained within the appropriate link and are not allowed to spill over into subsequent or preceding links. + +### C.3 *Line signal conditions and signalling codes* + +C.3.1 The line signal conditions and the signalling codes shall be as shown in Table C-1/Q.8. Signal sending and detection requirements are given in §§ C.3.2 and C.3.3. + +C.3.2 A continuous tone-on condition shall be the application of the signalling frequency to the send signalling path for a period exceeding 300 ms. + +A tone-on pulse signal shall be the application of the signalling frequency to the send signalling path for a period of 45-135 ms. A continuous tone-off condition shall exist when any signalling frequency is absent from the send signalling path for a period exceeding 80 ms. + +TABLE C-1/Q.8 + +#### Line signal conditions and signalling codes + +| Signal | From outgoing PABX | From incoming PABX | +|--------------------------------------------|---------------------|--------------------------------| +| Idle | Continuous tone-on | Continuous tone-on | +| Seizing | Continuous tone-off | Continuous tone-on | +| Seizing-acknowledgement or proceed-to-send | Continuous tone-off | Continuous tone-off | +| Answer | Continuous tone-off | Single tone-on pulse | +| Clear-forward | Continuous tone-on | Continuous tone-on or tone-off | +| Clear-back | Continuous tone-off | Continuous tone-on | + +C.3.3 A tone-on condition applied to the receive signalling path PABX termination may be recognized as a continuous tone-on condition for signalling when it has persisted for 150 ms, while for a tone-off condition a value of 40 ms has to be taken into account. + +A tone-on condition applied to the receive signalling path PABX termination and persisting for 35-150 ms, followed by a tone-off condition longer than 200 ms, may be recognized as a pulse tone-on signal. + +### C.4 *Line signalling transmission requirements* + +#### C.4.1 *Signal sender* + +C.4.1.1 The signalling tone shall be at a frequency of $2280 \pm 5$ Hz. + +C.4.1.2 The tone-on condition shall have two power levels: a high level and a low level. + +A high level tone shall be sent for the duration of the signal or for a minimum of 300 ms (whichever is shorter) and for a maximum of 550 ms after which it must be reduced to low level. + +- A high level tone-on condition shall be a signalling tone transmitted at a level of $-10 \text{ dBm}0 \pm 1 \text{ dB}$ . +- A low level tone-on condition shall be a signalling tone transmitted at a level of $-20 \text{ dBm}0 + 1 \text{ dB}$ . + +#### C.4.2 *Signal receiver* + +C.4.2.1 A frequency within the range $2280 \pm 15$ Hz at an absolute level $N$ , within the range $(-30 + n \leq N \leq -4 + n)$ dBm, shall be recognized as a tone-on condition; where $n$ is the relative power level at the receive signalling path PABX termination (see Recommendation G.171). + +C.4.2.2 Any frequency or combination of frequencies having a total absolute power level or less than $(-40 + n)$ dBm shall be recognized as a tone-off condition; where $n$ is the relative power level at the receive signalling path PABX termination as in § C.4.2.1. + +### C.5 *General line signal transfer procedures* + +C.5.1 Depending upon the capabilities of the incoming PABX, recognition of the seizing signal will initiate either proceed-to-send or seizing acknowledgement. The sending of the latter signal does not imply that the incoming PABX is ready to receive address information. + +C.5.2 Some PABXs do not use the answer signal, others require it for correct operation. Therefore the answer signal is optional and subject to mutual agreement, + +C.5.3 A continuous tone-on signal shall be applied when, after recognition of a seizing signal, no address or incomplete address information is received and the incoming PABX times-out. + +A continuous tone-on signal may be applied when an incoming PABX encounters congestion or an engaged extension. + +### C.6 *Decadic pulsing* + +For decadic pulsing interregister signalling the 2280 Hz line signalling is used. Some characteristics are given below. + +C.6.1 The break periods of dial pulses shall be applied to the send signalling path as pulses of tone-on condition within the following limits. + +| SPEED (pulses per sec.) | 7 | | 9 | | 11 | | 12 | | +|-------------------------|-----|-----|-----|-----|-----|-----|-----|-----| +| BREAK PULSE | MIN | MAX | MIN | MAX | MIN | MAX | MIN | MAX | +| DURATION (ms) | 45 | 112 | 45 | 81 | 45 | 61 | 45 | 52 | + +C.6.2 Pulses of tone-on condition applied to the receive signalling path PABX termination and consistent with the following speed and duration limits, are break periods of dial pulses (address signal). + +SPEED (pulses per sec.) + +| BREAK PULSE | 7 | | 9 | | 11 | | 12 | | +|---------------|-----|-----|-----|-----|-----|-----|-----|-----| +| | MIN | MAX | MIN | MAX | MIN | MAX | MIN | MAX | +| DURATION (ms) | 35 | 112 | 35 | 91 | 35 | 71 | 35 | 62 | + +# ANNEX D + +(to Recommendation Q.8) + +## A typical North American private analogue network signalling system + +### D.1 *Introduction* + +D.1.1 A Private Switched Network is a common control switching arrangement which provides interconnections of subscriber locations via dedicated access lines and inter-exchange circuits and shared common control switching with the Public Switched Telephone Network. The Private Switched Networks are terminated at the subscriber location by directly-homed telephone sets, multi-line telephone systems or by main PBX or PABXs. This annex describes the signalling on a typical North American switched private network. + +### D.2 *General signalling applications* + +D.2.1 The line signalling system provides for semi-automatic and automatic working between subscribers on the private network and the ability to go off network to the Public Switched Network. + +D.2.2 In general, four-wire transmission links employing an in-band single frequency of 2600 Hz, tone-on-idle, are used on the inter-exchange circuits, directly-homed stations and PBX access lines. + +D.2.3 Signalling on an inter-exchange circuit is in accordance with Recommendations Q.310 to Q.331 - System R1 signalling. + +D.2.4 Either decadic pulsing (DP) or multi-frequency pushbutton is used for address signalling on access lines. + +D.2.5 Multi-frequency pushbutton signalling is in accordance with Recommendation Q.23. (See also Recommendation Q.24.) + +D.2.6 Address signalling on inter-exchange circuits is multi-frequency (MF) using a combination of two out of six frequencies in accordance with Recommendations Q.320 to Q.326. + +D.2.7 Interregister signalling techniques are used for controlling outpulsing to accommodate different equipment designs and to improve register usage. + +### D.3 *Signalling on access lines* + +D.3.1 Either decadic pulsing (DP) or multi-frequency push-button (MFPB) is used on access lines for address signalling. + +D.3.2 Supervisory signalling may use either the single frequency 2600 Hz or direct current loop. + +D.3.3 Called party ringing is controlled by the terminating exchange or PABX in a conventional manner. + +### D.4 *Signalling on inter-exchange trunks* + +D.4.1 Supervisory signalling is single frequency 2600 Hz in accordance with Recommendations Q.310 to Q.313, Q.317 and Q.318. + +D.4.2 Register signalling uses multi-frequency (MF) signals consisting of two out of six frequencies in accordance with Recommendation Q.320. + +### D.5 *Decadic pulsing* + +The decadic pulsing represents the numeric value of each digit by the number of on-hook intervals in a train of pulses. + +D.5.1 The general characteristics of decadic pulsing are shown below: + +| Equipment | Pulsing Speed (PPS) | Percent Break (BK) | +|------------------|----------------------------|---------------------------| +| Customer Dial | 8-11 PPS | 58-64 BK | +| 10-PPS PBX | $10 \pm 0.3$ PPS | 62-66 BK | +| Sender Pulsing | $10 \pm 1$ PPS | 57-64 BK | + +### D.6 *Multi-frequency pushbutton* + +See Recommendations Q.11, Q.23 and Q.24. Signal combinations A-D are not usually used in North American private switched networks. + +# ANNEX E + +(to Recommendation Q.8) + +## **The standard European signalling system for leased circuits connecting subscribers to remote PABXs and public exchanges** + +### E.1 *Introduction* + +Recognizing the increasing use of leased lines for interconnection of telephone instruments and public exchanges or private automatic branch exchanges (PABXs) in the European telecommunication networks, a specification has been developed covering the need for signalling on such lines. The system emerged is called Signalling System L2. Distinction is made between line signalling (call supervisory signals) and interregister signalling (set-up including routing and additional service control). Taking into account different applications, existing interregister signalling techniques have been adopted for use with the basic line signalling as follows: + +- decadic pulsing (DP); +- multi-frequency pushbutton (MFPB) type signalling. + +### E.2 *Principles and fields of application* + +E.2.1 The line signalling system is to provide supervisory signals (e.g. loop signalling in one direction and ringing in the other) between a telephone instrument or its equivalent and a public exchange or PABX in different countries, via an extra long line. + +E.2.2 For the purpose of description, this specification refers to an instrument signalling unit (ISU) and an exchange signalling unit (ESU). + +E.2.3 The system is intended for use over four-wire circuits but, as an option for national use, it may be used over two-wire circuits. In the four-wire case, forward and backward signals are segregated by utilizing the four-wire circuit as two separate signalling paths. + +E.2.4 The system is a single voice frequency (1 vf) line signalling system using a signalling frequency of: + +- 2280 Hz in both directions on four-wire circuits; +- 2280 Hz in the direction ISU to ESU and 2400 Hz in the direction ESU to ISU on two-wire circuits (national). + +The use of voice frequency signals renders the system suitable for all voice transmission media, except those using speech interpolation. + +E.2.5 In addition to the application or removal of signalling frequency (tone-on and tone-off) in continuous form, the transmission of pulses of signalling frequency is applied. + +E.2.6 When in the idle condition, the signalling frequency applied to the line by the ISU is reduced in power level to conform to the transmission loading requirements of Recommendation Q.15. + +E.2.7 In accordance with Recommendation Q.25, sending and receiving line splitting arrangements are provided so that signals are contained within the ISU-ESU link and not allowed to spill over into the next link. + +E.2.8 When making an outgoing call, a through speech path shall be provided in the direction ESU-ISU prior to the answered state. + +E.2.9 Signals may be passed in the direction ISU to ESU while speech or audible indications are being received in the direction ESU to ISU. + +### E.3 *Line signal conditions and signalling codes* + +E.3.1 The line signal conditions and the signalling codes shall be as shown in Tables E-1/Q.8 and E-2/Q.8. Signal sending and detection requirements are given in §§ E.3.2 and E.3.3. + +TABLE E-1/Q.8 + +#### **Calls originated by the telephone instrument** + +| Signal | Conditions from ISU | Conditions from ESU | +|---------|----------------------|---------------------| +| Idle | Continuous tone-on | Continuous tone-off | +| Seizing | Continuous tone-off | Continuous tone-off | +| Answer | Continuous tone-off | Tone-on pulse | +| Recall | Recall tone-on pulse | Continuous tone-off | +| Clear | Continuous tone-on | Continuous tone-off | + +TABLE E-2/Q.8 + +#### **Calls from the exchange** + +| Signal | Conditions from ESU | Conditions from ISU | +|---------|-----------------------|----------------------| +| Idle | Continuous tone-off | Continuous tone-on | +| Calling | Calling tone-on-pulse | Continuous tone-on | +| Answer | Continuous tone-off | Continuous tone-off | +| Recall | Continuous tone-off | Recall tone-on pulse | +| Clear | Continuous tone-off | Continuous tone-on | + +E.3.2 A continuous tone-on condition shall be the application of the signalling frequency to the send signalling path for a period exceeding 350 ms. A tone-on pulse signal shall be the application of the signalling frequency to the send signalling path for a period of 45-135 ms or 210-240 ms (see § E.5.2). + +A continuous tone-off condition shall exist when any signalling frequency is absent from the send signalling path for a period exceeding 80 ms. + +E.3.3 A tone-on condition applied to the receive signalling path line termination may be recognized as a continuous tone-on condition for signalling, when it has persisted for 250 ms, while for a tone-off condition a value of 40 ms has to be taken into account. + +A tone-on condition applied to the receive signalling path line termination, and persisting for a period of 35-150 ms or 200-250 ms (see § E.5.2) may be recognized as a tone-on pulse signal. + +### E.4 *Line signalling transmission requirements* + +#### E.4.1 *Signal sender* + +E.4.1.1 The signalling tone shall be at a frequency of 2280 (2400 Hz in the ESU for two-wire working) $\pm 5$ Hz. + +E.4.1.2 The tone-on condition shall have two power levels: a high level and a low level. + +A high level tone shall be sent for the duration of the signal or for a minimum of 300 ms (whichever is shorter), and for a maximum of 550 ms after which it must be reduced to low level. + +- A high level tone-on condition shall be a signalling tone transmitted at a level of $-10 \text{ dBm}0 \pm 1 \text{ dB}$ . +- A low level tone-on condition shall be a signalling tone transmitted at a level of $-20 \text{ dBm}0 \pm 1 \text{ dB}$ . + +#### E.4.2 *Signal receiver* + +E.4.2.1 A frequency within the range 2280 (2400 Hz in the ISU for two-wire working) $\pm 15$ Hz at an absolute level $N$ , within the range $(-30 + n \leq N \leq -4 + n)$ dBm shall be recognized as a tone-on condition; where $n$ is the relative power level at the receive signalling path line termination (see Recommendation G.171). + +E.4.2.2 Any frequency or combination of frequencies having a total absolute power level of less than $(-40 + n)$ dBm shall be recognized as a tone-off condition; where $n$ is the relative power level at the receive signalling path line termination as in § E.4.2.1. + +### E.5 *General line signal transfer procedures* + +E.5.1 The calling signal is a series of tone-on pulses with a duration of each pulse according to the length of the original ringing pulse and in step with the period of the ringing signal. + +E.5.2 As an option and subject to mutual agreement by the parties involved, the ISU applies a recall signal in the form of a tone-on pulse to the signalling path. + +The length of tone-on pulse applied by the ISU depends upon the type of recall employed by the associated telephone, e.g. timed break or earthed loop. + +E.5.3 As an option and subject to mutual agreement by the parties involved, the answer signal is sent by the ESU. + +### E.6 *Decadic pulsing* + +For decadic pulsing interregister signalling, the 2280 Hz line signalling is used. Some characteristics are given below. + +E.6.1 The break periods of decadic pulses shall be applied to the send signalling path of the ISU, as pulses of tone-on condition within the following limits. + +| | | | | | | | | | +|-------------------------|-----|-----|-----|-----|-----|-----|-----|-----| +| SPEED (pulses per sec.) | | | | | | | | | +| BREAK PULSE | 7 | | 9 | | 11 | | 12 | | +| | MIN | MAX | MIN | MAX | MIN | MAX | MIN | MAX | +| DURATION (ms) | 45 | 112 | 45 | 81 | 45 | 61 | 45 | 52 | + +E.6.2 Pulses of tone-on condition applied to the receive signalling path line termination of the ESU, consistent with the following speed and duration limits, are break periods of dial pulses (address signal). + +| | | | | | | | | | +|-------------------------|-----|-----|-----|-----|-----|-----|-----|-----| +| SPEED (pulses per sec.) | | | | | | | | | +| BREAK PULSE | 7 | | 9 | | 11 | | 12 | | +| | MIN | MAX | MIN | MAX | MIN | MAX | MIN | MAX | +| DURATION (ms) | 35 | 122 | 35 | 91 | 35 | 71 | 35 | 62 | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44d3876f79c67d6423285d69ff7f544b86482ae2 --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e6e91fdf97d1da4fe551f979219cddb40dfafc0d75df83ddf3cd089a4c1d69b +size 37678 diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..933fb9bb34fffef4be1b64970eec802edfbb7b9a --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7711e8da7905f78090af292a8c8c73848a5833f7a59b854f7195cae0499a8cb3 +size 142718 diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74874537f530c34646be76923d3ca5b016d15cd9 --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:462b47290d18373ed7711968266d8f0149a6328a3aa8dad33931db31d606ae26 +size 81529 diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cdd7c2388278f99403222d9be8906970e842c93 --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21ee4e0e8daccffa7b19f4728a383e1f233d7b60dba83cb527f320f943021fe7 +size 101646 diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65280bfbcd414ab416fe090de15853982d1197d6 --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56f2fddaa92f5549015868d2bbc53abb89ea16b1948130a421f10af95206b6e9 +size 67109 diff --git a/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0af2180de27472a643e8b4c44d4c0bf954de4389 --- /dev/null +++ b/marked/Q/T-REC-Q.81.1-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f11959d87f055c36d3a2b0ba05051e1db8e42e9833f091b54433cc3f577abbd +size 32544 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b49a7e4f8629c230ea26f639358f4f810746e356 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ac92bc52e5f4c519370b4ad9becbff0076880ab649592c921345df5fbccf1be +size 72986 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8938b59041c640ba55041c064dba115e5a7043c --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:308adb92564464180cdd632c7ac79d7957bd78266da19f6b78cdc6dc62ff1159 +size 103864 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a4a3fb6e6ecea1245b1281fd015af36985a7181 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e71a7250efee11dbff458f099ce68098bbafd19b478471841b0011f0769083a7 +size 8410 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..273633521351e0e7f0719b51b7979dfbbef1bb80 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0722cb6d12e0d5a87c8a8a373a0baac5bc8198572dda8fb5f43d4d838f60dd0 +size 38117 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/4d5d6207a6d444ae745057ebc3ddcd86_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/4d5d6207a6d444ae745057ebc3ddcd86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a574b25b278aaa2d78c3cd181bc96d42d17fd5de --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/4d5d6207a6d444ae745057ebc3ddcd86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e2c92f53fa23ed4044dd86dc9f07f962397c43ff4a73928b7992c7687d30378 +size 35258 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9d205c8adb5986397702165e8ecfc44f4467adf --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0274cf10103fa017cc662c1e2034e81de162346aaf6279a5cd2949169e53b2fe +size 61951 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..836dda5a4f56de2e2bb00eb567a68be158d1c810 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1475cfb02b7b71e0aa06be262156248d211266330629c56dc0d391cf29a775a7 +size 68541 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19cc63b6588ec9c4b4006da971080e739bd0c371 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32b58d8052c3be1c1e7a179ba6b122b53c3a0009bb81ac37f59cec7e59b284c3 +size 75775 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8990fbd6b7f97a358056ec754eea705401338e4 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4be7c2606eb5e8868a54448e5badc64ec0c920999aedb517e7280a59c6ac05a +size 125467 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/c649cad02e45d7d9a16f3f5bdb332219_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/c649cad02e45d7d9a16f3f5bdb332219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e100810cf0df8ad4615c4556268be08f93cf906 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/c649cad02e45d7d9a16f3f5bdb332219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a15b4f59763b3f8e60583a752b0e55683294931e130e9bd0ab16c20580c9c95c +size 39909 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d2b7898035ef87456e9f5bb37f235653d544606 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f525e5f0be03dca1437a146a0ad9bac573ea711882df934beeb7b971c647e38 +size 26203 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26e3479a90a0fae7338bfb29b27c21ec56045eea --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd4b999f548e85cbe7c1deb93fbda640d5f797a57c0f8a3afbe5e93bec3b9d90 +size 82306 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5b11f22bf3a633eed5c62a11410b48226ea430b --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56828210cb132863ae3c8b224784e72936db7e33d8154586799c2e0949792590 +size 44995 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg b/marked/Q/T-REC-Q.816-200101-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b8e3f271a303d900ec94c26d59c110d6774cb37 --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea7464847f8170c7eb0f3c5cdc1fca24b1916e9c84579f1a4fe37134bbc70b31 +size 50845 diff --git a/marked/Q/T-REC-Q.816-200101-I_PDF-E/raw.md b/marked/Q/T-REC-Q.816-200101-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9434258bf2f821bd2ef51fe09f6bdf8c57d097fd --- /dev/null +++ b/marked/Q/T-REC-Q.816-200101-I_PDF-E/raw.md @@ -0,0 +1,2822 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.816** + +(01/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Q3 interface + +--- + +**CORBA-based TMN services** + +ITU-T Recommendation Q.816 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **CORBA-based TMN services** + +## **Summary** + +This Recommendation defines a set of services that along with ITU-T X.780 composes a framework for CORBA-based TMN interfaces. It specifies protocol requirements, CORBA Common Object Service usage requirements, and TMN-specific support services. A CORBA IDL module defining the interfaces to the TMN-specific support services is provided. + +## **Source** + +ITU-T Recommendation Q.816 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. + +## **Keywords** + +Common Object Request Broker Architecture (CORBA), Interface Definition Language (IDL), CORBA services, Distributed Processing, TMN Interfaces, Managed Objects + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------|----| +| 1 | Scope ..... | 7 | +| 1.1 | Purpose ..... | 7 | +| 1.2 | Application..... | 8 | +| 1.3 | Recommendation Roadmap ..... | 9 | +| 1.4 | Recommendation Conventions ..... | 9 | +| 1.5 | Compiling the IDL ..... | 10 | +| 2 | References..... | 10 | +| 3 | Definitions and abbreviations ..... | 11 | +| 3.1 | Definitions from ITU-T X.701..... | 11 | +| 3.2 | Definitions from ITU-T X.703..... | 11 | +| 3.3 | Additional definitions ..... | 11 | +| 3.4 | Abbreviations ..... | 11 | +| 4 | CORBA-based TMN services goals and requirements ..... | 13 | +| 4.1 | Goals..... | 13 | +| 4.1.1 | Application interoperability ..... | 13 | +| 4.1.2 | Common usage of CORBA Common Object Services ..... | 14 | +| 4.1.3 | Information model transparency..... | 14 | +| 4.2 | Information modeling dependencies ..... | 14 | +| 4.2.1 | Access granularity ..... | 14 | +| 4.2.2 | Representation of containment and naming..... | 14 | +| 4.2.3 | Object creation and deletion..... | 15 | +| 4.3 | Scoping and filtering ..... | 15 | +| 4.3.1 | Scoping ..... | 15 | +| 4.3.2 | Filtering..... | 16 | +| 4.4 | Notifications..... | 17 | +| 5 | Framework overview and protocol requirements..... | 17 | +| 5.1 | Framework overview ..... | 17 | +| 5.2 | Framework protocol requirements ..... | 18 | +| 6 | Framework common object services requirements ..... | 19 | +| 6.1 | The Naming Service ..... | 20 | +| 6.1.1 | Translating managed object names to strings ..... | 24 | +| 6.2 | Notification Service..... | 25 | +| 6.3 | Telecom Log Service..... | 29 | +| 6.4 | Messaging Service..... | 30 | +| 6.5 | Security Service..... | 32 | + +| | Page | +|----------------------------------------------------|-------------| +| 6.6    Transaction Service ..... | 32 | +| 7      Framework support services ..... | 33 | +| 7.1    The Factory Finder Service..... | 33 | +| 7.2    The Channel Finder Service..... | 34 | +| 7.2.1    Channel Finder interface..... | 34 | +| 7.2.2    Channel Finder requirements ..... | 37 | +| 7.3    The Terminator Service ..... | 38 | +| 7.4    The Multiple-Object Operation Service ..... | 39 | +| 7.4.1    The MOO Service interface ..... | 39 | +| 7.4.2    The default filter language ..... | 45 | +| 7.4.3    MOO Service requirements..... | 48 | +| 7.5    The Heartbeat Service ..... | 49 | +| 7.6    Other support services ..... | 50 | +| 8      Compliance and conformance..... | 50 | +| 8.1    System conformance ..... | 51 | +| 8.1.1    Conformance points..... | 51 | +| 8.1.2    Basic conformance profile ..... | 52 | +| 8.2    Conformance statement guidelines ..... | 52 | +| ANNEX A – Framework Support Services IDL ..... | 52 | +| // Data Types and Structures..... | 53 | +| // Constants ..... | 56 | +| // Exceptions ..... | 56 | +| // Interfaces ..... | 57 | +| // Factory Finder Interface ..... | 57 | +| // Channel Finder Interface ..... | 58 | +| // Heartbeat Service Interface ..... | 59 | +| // Terminator Service Interface ..... | 60 | +| // DeleteResultsIterator Interface ..... | 60 | +| // GetResultsIterator Interface..... | 61 | +| // UpdateResultsIterator Interface ..... | 61 | +| // BasicMooService Interface ..... | 62 | +| // AdvancedMooService Interface ..... | 63 | +| // Notifications Interface..... | 64 | + +| | Page | +|------------------------------------------------------------------------------------------------------------------|-------------| +| ANNEX B – The Constraint Language BNF ..... | 65 | +| B.1   The constraint language proper in terms of lexical tokens ..... | 65 | +| B.2   "BNF" for lexical tokens up to character set issues ..... | 66 | +| B.3   Character set issues..... | 67 | +| APPENDIX I – Interworking scenarios between models using ITU framework and
ADSL- /ATMF-compliant models ..... | 67 | +| I.1   Introduction..... | 67 | +| I.2   Terminology..... | 68 | +| I.3   Interworking scenarios..... | 68 | +| I.3.1   Grain-Neutral Server migrating to ITU Framework Server..... | 68 | +| I.3.2   Grain-neutral Client migrating to ITU Framework client..... | 69 | +| APPENDIX II – Filtering native and translated structured events ..... | 69 | +| APPENDIX III – Bibliography..... | 72 | + + + +## CORBA-based TMN services + +# 1 Scope + +The TMN architecture defined in ITU-T M.3010 (2000) introduces concepts from distributed processing and includes the use of multiple management protocols. The initial TMN interface specifications for intra- and inter-TMN interfaces were developed using the Guidelines for the Definition of Managed Objects (GDMO) notation from OSI Systems Management with Common Management Information Protocol (CMIP) as the protocol. The inter-TMN interface (X) included both CMIP and CORBA GIOP/IIOP as possible choices at the application layer. + +CORBA, a distributed processing technology, is being considered for use in the TMN communication architecture primarily due to its acceptance by the Information Technology industry. This acceptance is expected to enhance the availability of CORBA-based interfaces due to better development tools and widespread expertise in developing CORBA-based interfaces. This technology, developed by the Object Management Group (OMG), is also being considered by multiple industries. Specifications using this technology provide support for standard application programming interfaces (APIs) and language bindings to programming languages, and they also facilitate software portability. The interoperability solutions offered by the object request broker combined with the inter-ORB protocols address interoperability between client and server. While CMIP and information models provide solutions for interoperability between manager and agent systems, CORBA defines inter-object interactions where the objects may be distributed. + +## 1.1 Purpose + +Several groups are developing network management specifications that use CORBA modeling techniques with IDL as the notation along with CORBA services. The scope of this Recommendation is to define protocol requirements and common services suitable for use in the specification of interoperable CORBA-based network management interfaces. The demands placed on "X" interfaces are different from those used "inside" a TMN, "Q" interfaces. The scope of this Recommendation covers all interfaces in the TMN where CORBA may be used. It is expected that not all capabilities and services defined here are required in all TMN interfaces. This implies that the framework can be used for interfaces between management systems at all levels of abstractions (inter- and intra-administration) as well as between management systems and network elements. + +This Recommendation is intended for use by various groups specifying network management interfaces. A number of factors are considered: the version of CORBA to use, the set of CORBA Common Object Services employed, and additional services. This Recommendation, along with the object modeling guidelines defined in ITU-T X.780 form a *framework* for CORBA-based TMN interfaces. Use of a common framework on telecommunications management interfaces has several advantages. Some examples are: + +- facilitating reuse of models that are developed to meet the generic requirements of telecommunications; +- profiling CORBA services for use by the telecommunications industry; +- easing the definition of new services for TMN, reusing the semantics of the existing rich set of models; and +- harmonizing the modeling approach across groups using a single source similar to ITU-T X.720, ITU-T X.721 and ITU-T X.722 for CMIP. + +Re-using a common framework and generic information model for a variety of network technologies and network management applications will speed the introduction of new network services while keeping network management system development costs down. + +The telecommunications industry has invested a great deal of time and energy in the development of information models for the CMIP network management protocol. A primary goal of this framework is the reuse of these information models by enabling their translation to CORBA Interface Definition Language (IDL) with little change in semantics (see ITU-T X.780). As a result, initial IDL information models are expected to be derived from CMIP models. + +In addition to taking advantage of CMIP information models, another purpose of the framework is to take advantage of CORBA. The framework leverages the functions defined in the CORBA specifications, including a set of Common Object Services. Also, the framework tries to reuse CORBA approaches and design patterns wherever they fit. Finally, while re-using existing models is important, it is equally important that the framework support the development of new models. This framework does not require a GDMO model to be developed prior to the development of an IDL model. In fact, developing a new IDL information model for use within this framework is straightforward and guidelines for doing so are provided. + +## 1.2 Application + +As CORBA is introduced in TMN, different scenarios are possible that range from the use of gateways performing translations between systems using different network management protocols to cases where CORBA is natively supported by the communicating systems. The application of this framework is intended for scenarios where both the managed system and the managing system provide CORBA interfaces. + +The framework does not address other interworking scenarios requiring "gateway" systems where protocol and information model conversions are necessary for achieving interoperability. In particular, this framework is not specifically designed to support the construction of gateways between CORBA and CMIP network management applications even though the semantics of the existing models are retained by this framework. A management system, however, might have to support multiple protocols, to interwork in different environments. + +A gateway approach has already been developed and standardized by the Joint Inter-Domain Management (JIDM) group. This gateway approach provides a one-to-one mapping of all constructs and capabilities available with CMIP and GDMO. However, many of the CORBA services and capabilities are not reused by this approach because the problem solved is to facilitate interworking with systems that have been deployed using CMIP. In contrast, the problem domain for applying this framework is to support standards-based native CORBA network management interfaces. Such an approach takes advantage of the benefits offered by CORBA as a technology used by multiple industries. + +ITU-T X.780 [1] accompanies this Recommendation and defines object modeling guidelines, superclasses for all managed objects and managed object factories for use with this framework, and a standard set of notifications. Together, ITU-T X.780 and this Recommendation define a *framework* for CORBA-based TMN interfaces. Also, ITU-T M.3120 provides a CORBA IDL version of the generic network information model originally defined in ITU-T M.3100. The IDL version follows the object modeling guidelines in ITU-T X.780 and is designed to fit with the services defined here. + +## 1.3 Recommendation Roadmap + +This Recommendation has the following structure: + +- Clause 1 Introduction, Recommendation roadmap, updates, and list of issues +- Clause 2 References +- Clause 3 Definitions of terms and abbreviations used throughout the rest of the Recommendation +- Clause 4 Requirements for the TMN CORBA-based services. These are the design goals the services must meet +- Clause 5 CORBA ORB and Service version requirements. Also provided is an overview of the services +- Clause 6 Requirements on the use of CORBA Common Object Services for network management interfaces +- Clause 7 Definition of TMN-specific support services. IDL interfaces for the support services are defined in Annex A +- Clause 8 Compliance and conformance guidelines +- Annex A TMN-specific support service IDL +- Appendix I Interworking Scenarios Between Models Using ITU Framework and ADSL/ATMF Compliant Models +- Appendix II Filtering native and translated structured events +- Appendix III Bibliography + +## 1.4 Recommendation Conventions + +A few conventions are followed in this Recommendation to make the reader aware of the purpose of the text. While most of the Recommendation is normative, paragraphs succinctly stating mandatory requirements to be met by a management system (managing and/or managed) are preceded by a boldface "R" enclosed in parentheses, followed by a short name indicating the subject of the requirement, and a number. For example: + +**(R) EXAMPLE-1** An example mandatory requirement. + +Requirements that may be optionally implemented by a management system are preceded by an "O" instead of an "R." For example: + +**(O) OPTION-1** An example optional requirement. + +The requirement statements are used to create compliance and conformance profiles. + +Many examples of CORBA IDL are included in this Recommendation, and IDL specifying the TMN specific services, and supporting data types, included in a normative annex. The IDL is written in a 9-point courier typeface: + +``` +// Example IDL +interface foo { + void operation1 (); +}; +``` + +Instructions for extracting the IDL from an electronic version of this Recommendation and compiling it are presented in the next clause. + +## 1.5 Compiling the IDL + +An advantage of using IDL to specify network management interfaces is that IDL can be "compiled" into programming code by tools that accompany an ORB. This actually automates the development of some of the code necessary to enable network management applications to interoperate. This Recommendation has one annex that contains code that implementers will want to extract and compile. Annex A is normative and should be used by developers implementing systems that conform with this standard. The IDL in this Recommendation has been checked with two compilers to ensure its correctness. A compiler supporting the CORBA version specified in 5.2 must be used. + +Annex A has been formatted to make it simple to cut and paste it into a plain text file that may then be compiled. Below are tips on how to do this. + +- 1) Cutting and pasting seems to work better from the Microsoft® Word® version of this Recommendation. Cutting and pasting from the Adobe® Acrobat® file format seems to include page headers and footers, which cannot be compiled. +- 2) All of Annex A, beginning with the line "/\* This IDL code..." through the end should be stored in a file named "itut\_q816.idl" in a directory where it will be found by the IDL compiler. +- 3) The headings embedded in Annex A need not be removed. They have been encapsulated in IDL comments and will be ignored by the compiler. +- 4) Comments that begin with the special sequence "/\*\*" are recognized by compilers that convert IDL to HTML. These comments often have special formatting instructions for these compilers. Those that will be working with the IDL may want to generate HTML as the resulting HTML files have links that make for quick navigation through the files. +- 5) Annex A has been formatted with tab spaces at 8-space intervals and hard line feeds that should enable almost any text editor to work with the text. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T X.780 (2001), *Guidelines for defining CORBA managed objects*. +- [2] OMG Document formal/1999-10-07, *The Common Object Request Broker: Architecture and Specification*, Revision 2.3.1. +- [3] OMG Document formal/2000-11-1, *Interoperable Naming Service Specification*. +- [4] OMG Document formal/2000-06-20, *Notification Service Specification*, Version 1.0. +- [5] OMG Document formal/00-01-04, *Telecom Log Service Specification*, Version 1.0. +- [6] OMG Document formal/2000-06-25, *Security Services Specification*, Version 1.5. +- [7] OMG Document formal/2000-06-28, *Transaction Service Specification*, Version 1.1. + +- [8] OMG Document formal/2000-10-58, *CORBA Messaging*. +- [9] OMG Document formal/2000-08-01, *Interworking between CORBA and TMN Systems Specification*. +- [10] IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*. +- [11] IEEE/ANSI Std 1003.2-1992, *Information Technology – Portable Operating System Interface (POSIX) Part 2: Shell and Utilities*. +- [12] IETF RFC 2253 (1997), *Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names*. +- [13] ETSI TS 132 106-3 (2000), *Universal Mobile Telecommunications System (UMTS), Telecommunication Management; Configuration Management; Part 3: Notification Integration Reference Point: CORBA solution set version 1.1* (3G TS 32 106-3 Release 1999). +- [14] ITU-T X.701 (1997), *Information technology – Open Systems Interconnection – Systems management overview*. +- [15] ITU-T X.703 (1997), *Information technology – Open Distributed Management Architecture*. + +# 3 Definitions and abbreviations + +## 3.1 Definitions from ITU-T X.701 + +The following terms used in this Recommendation are defined in ITU-T X.701: + +- managed object class; +- manager; +- agent. + +## 3.2 Definitions from ITU-T X.703 + +The following term used in this Recommendation is defined in ITU-T X.703: + +- notification. + +## 3.3 Additional definitions + +**3.3.1 event channel:** a support object in a managed system with one or more interfaces allowing a managing system to receive notifications from that managed system. + +NOTE – There are two models for event channel delivery of notifications (see ITU-T X.703): + +- In the push model of event delivery, the managing system uses one or more event channel interface instances to register one or more managing system interface references that may be used by the channel to invoke event push operations. +- In the pull model of event delivery, the managing system uses one or more event channel interface references to invoke operations which return notification information. + +## 3.4 Abbreviations + +This Recommendation uses the following abbreviations: + +AMI      Asynchronous Messaging Invocation + +| | | +|-------|----------------------------------------------------------------------------------| +| API | Application Programming Interface | +| ASN.1 | Abstract Syntax Notation One | +| ATM | Asynchronous Transfer Mode | +| AVA | Attribute Value Assertion | +| CMIP | Common Management Information Protocol | +| CORBA | Common Object Request Broker Architecture | +| COS | Common Object Services | +| DN | Distinguished Name | +| EMS | Element Management System | +| FIFO | First In, First Out | +| GDMO | Guidelines for the Definition of Managed Objects | +| GIOP | General Interoperability Protocol | +| HTML | HyperText Markup Language | +| ID | Identifier | +| IDL | Interface Definition Language | +| IEEE | Institute of Electrical and Electronics Engineers | +| IETF | Internet Engineering Task Force | +| IIOP | Internet Interoperability Protocol | +| IOR | Interoperable Object Reference | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| JIDM | Joint Inter-Domain Management | +| MO | Managed Object | +| MOO | Multiple Object Operation | +| NE | Network Element | +| NMS | Network Management System | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OID | Object Identifier | +| OMG | Object Management Group | +| ORB | Object Request Broker | +| OSI | Open Systems Interconnection | +| PDU | Protocol Data Unit | +| PM | Performance Management | +| POA | Portable Object Adapter | +| POP | Point of Presence | +| POSIX | Portable Operating System Interface | + +| | | +|-------|---------------------------------------| +| QoS | Quality of Service | +| RDN | Relative Distinguished Name | +| SDH | Synchronous Digital Hierarchy | +| SONET | Synchronous Optical Network | +| SSL | Secure Socket Layer | +| TII | Time-Independent Invocation | +| TLS | Transport Layer Security | +| TMN | Telecommunications Management Network | +| TTP | Trail Termination Point | +| UID | Universal Identifier | +| UML | Unified Modeling Language | +| UTC | Universal Time Code | + +# 4 CORBA-based TMN services goals and requirements + +This clause describes the key goals of the services framework and the requirements that help the CORBA-based TMN services support these goals. Subclause 4.1 introduces the goals of the CORBA framework. Subclause 4.2 then provides terminology and requirements. The requirements in this clause are requirements that the framework must satisfy. They are based on the telecommunications management needs. Clauses 5, 6, 7, and 8 then describe a framework that meets these needs and define how to achieve the requirements of this clause by using CORBA in a certain way. The rules in Clauses 5, 6, 7, and 8 on how to use CORBA also are referred to as requirements. + +## 4.1 Goals + +This Recommendation sets out to define a framework for defining how interfaces supported by management systems and network elements should be modeled. Some key goals of the framework are identified here: + +- Application interoperability; +- Common usage of CORBA common object services; +- Information model transparency. + +This clause elaborates on these three goals. + +### 4.1.1 Application interoperability + +A key goal of the TMN architecture, and in particular the information architecture, is to promote a standard framework for providing interoperability and information exchange between systems from a diverse set of network management system suppliers. Interoperability between systems involves many aspects of development. At its lowest layer, a common communication mechanism must be in place to support a common syntax, the establishment of connectivity and the exchange of operation requests/replies between systems. This aspect of interoperability is inherently supported by the CORBA specification. + +For TMN, there is the need to provide application interoperability. That is, management systems from diverse suppliers will be utilized within a single administration's TMN to support different functions necessary to support management of its networks. To simplify integration of these various + +suppliers' systems, they must agree on the semantics of the information being exchanged. This is accomplished with the specification of an information model. Guidelines for the definition of CORBA-based information models are specified in ITU-T X.780, but the services defined here must support those guidelines. + +### 4.1.2 Common usage of CORBA Common Object Services + +A second aspect of this framework is the definition of common usage and profiling of the distributed processing environment of choice. This aspect of the framework should indicate the reasonable expectations network management system suppliers may have for one another. Rather than redefining the interface capabilities needed to support common network management functions such as object naming and notification filtering with each information model, the modeling guidelines in ITU-T X.780 rely upon a set of support services. These support services enable the information models to be simpler, and also enhance interoperability. + +In defining these services, special effort will be taken to make use of the CORBA common object services. Specifically, this Recommendation will address the use of the CORBA ORB and CORBA Common Object Services (COS) that will impact system interoperability (i.e., issues involving the use of CORBA within a single system are outside the scope of this Recommendation). Where network management needs cannot be met by CORBA COS, additional services will be defined. + +### 4.1.3 Information model transparency + +If CORBA is used in places within the TMN architecture where existing information models (e.g., GDMO) are well established, then the framework must support the reuse of those models without any major changes. + +The focus of this Recommendation is on the set of services required to allow the existing models to be used as they were originally intended with a reasonable amount of efficiency. + +## 4.2 Information modeling dependencies + +As described in the previous clause, the explicit modeling of resources that are manageable across an interface is central to application interoperability. The guidelines for defining CORBA-managed objects detailed in ITU-T X.780 describe the rules for modeling manageable resources. They also embody several decisions that must be supported by the TMN CORBA-based services framework. This clause summarizes those points. + +### 4.2.1 Access granularity + +CORBA interface *granularity* refers to the relationship between the resources that are modeled on an interface and the means by which they are accessed using CORBA. ITU-T X.780 uses an *instance-grain* modeling approach, which means each modeled resource is accessible using a unique CORBA object reference, known as an *interoperable object reference* (IOR). The objects that represent manageable resources are called *managed objects*. + +### 4.2.2 Representation of containment and naming + +Containment is a logical representation of how modeled resources contain other modeled resources. Containment has traditionally been a very important relationship in network management applications because it is a convenient means of identifying the large number of resources that typically must be managed. ITU-T X.780 guidelines require that a unique name be assigned to each managed object, based in part on the name of the object that contains it. The TMN CORBA-based services must provide a means to store these names (and hence the containment relationships they represent) as well as a means to find the IOR of an object based on its name. + +### 4.2.3 Object creation and deletion + +The CORBA ORB does not provide clients with a means to create objects on remote systems. Instead, typically *factory* objects are instantiated by remote systems, and these factory objects provide operations that may be invoked by clients to create objects on the remote system. For a number of information modeling purposes, ITU-T X.780 specifies that a factory IDL interface shall be defined for each managed object IDL interface in an information model. So, object creation will be model-dependent and is not a good candidate for a TMN CORBA service. However, a service for managing system seeking a factory in order to request creation of an object in a managed system is defined in this Recommendation. + +Object deletion is also an area in need of support. Often, CORBA objects are deleted by simply invoking some delete operation on the object, but this is not a good approach for network management applications because of their reliance on containment relationships. Deleting an object that contains other objects has impacts beyond the object being deleted. Also, as described in the previous clause, support is required for storing the names of managed object instances, and this data must be updated when objects are deleted. The TMN CORBA services therefore need to provide support for deleting managed objects in an orderly fashion. + +## 4.3 Scoping and filtering + +The ability to perform complex queries (i.e., GET operations), updates (i.e., SET operations), and delete operations on a group of Entities with a single operation request is a valuable component of TMN. Management systems may have to manage up to $10^{7}$ instances of managed objects. Due to the size of the management information base, a managing system can not efficiently perform ad hoc queries on individual instances of Managed Objects (i.e., Entities). Rather, the managing system expects a level of intelligence to be supported by the managed system. + +The intelligence in the managed system allows the managing system to select a group of managed entities on which some operation will be performed. Managed entity selection involves two phases: scoping and filtering. This managed entity selection process is supported by a service defined later in this Recommendation. This service allows a managing system to select a scope of objects to act on (scope is defined through containment relationships; see 4.2.2). Once the scope of Entities is determined, the operation (specified by the scope and filtered request) is performed only on those Entities which meet criteria defined by a filter. + +The use of scoping and filtering in this framework supports: + +- Scoped and Filtered get: Returns the values (for a list of attributes) from each of the Entities that meet the scope and filter criteria. +- Scoped and Filtered update: Replaces an attribute value or adds/removes values to/from set-valued attributes, in the group of Entities meeting the scope and filter criteria, to the values specified in the scoped and filtered request. May be used to update one or multiple attributes in a single object or multiple objects. +- Scoped and Filtered deletion: Deletes all Entities that meet the scope and filter criteria. + +### 4.3.1 Scoping + +Scoping entails the identification of the Entities to which a filter is to be applied. Scoping is applied based on the containment hierarchy as defined in 4.2.2. The scope is applied from some base managed entity down to some depth in the containment tree. + +The base entity for the scope is defined as the root of the containment tree from which the search is to commence. A scoped request must specify the base managed entity of the scope. The depth of the scoping level can then be specified in one of four manners within the scoped request: + +- 1) the base entity; +- 2) the nth level subordinates of the base entity; +- 3) the base entity and all of its subordinates down to and including the nth level; +- 4) the base entity and all of its subordinates (i.e., the whole subtree). + +### 4.3.2 Filtering + +Filters allow for the specification of criteria that Entities must meet in order to have a management operation performed. Together with scoping, filtering allows a single operation to be performed across multiple managed objects with a single operation request. + +A filter parameter is used to determine whether or not an operation should be performed on a managed object. A filter parameter applies a test that is either satisfied or not by a particular managed object. The filter is expressed in terms of assertions about the presence or value of certain attributes of the managed object, and it is satisfied if and only if it evaluates to TRUE. + +#### 4.3.2.1 Attribute matching rules + +The following matching rules are defined that may be used in attribute value assertions (AVAs). These rules are: + +- **Equality:** Evaluates to TRUE if and only if the value supplied in the AVA is equal to the value of the attribute. +For SET valued attributes, the AVA evaluates to TRUE if and only if the set of members supplied in the AVA is equal to the set of members in the attribute. +- **Greater or equal:** Evaluates to TRUE if and only if the value supplied in the AVA is greater than or equal to the value of the attribute. +For SET valued attributes, the value in the AVA shall contain exactly one member. The AVA evaluates to TRUE if and only if that member is greater than or equal to at least one of the members in the attribute value. +- **Less or Equal:** Evaluates to TRUE if and only if the value supplied in the AVA is less than or equal to the value of the attribute. +For SET valued attributes, the value in the AVA shall contain exactly one member. The AVA evaluates to TRUE if and only if that member is less than or equal to at least one of the members in the attribute value. +- **Present:** Evaluates to TRUE if and only if such an attribute is present in the managed object. +- **Substrings:** Evaluates to TRUE if and only if all of the substrings specified in the AVA appear in the attribute in the given order without overlapping and separated from the ends of the attribute value and from one another by zero or more string elements. In addition, for the AVA to evaluate to TRUE, + - the first element in the initial substring, if present, shall match the first element in the attribute value; + - the other substrings, if present, shall appear in the attribute value in the order that the substrings appear in the AVA; and + - the last element in the final substring, if present, shall match the last element in the attribute value. + +For SET valued attributes, each value in the AVA shall contain exactly one member. The AVA evaluates to TRUE if and only if there is at least one of the members of the attribute value in which all of the substrings supplied in the AVA appear as described above. + +(The remaining three matching tests apply to SET valued attributes only) + +- **subset of:** Evaluates to TRUE if and only if all asserted members are present in the attribute. +- **superset of:** Evaluates to TRUE if and only if all members of attribute are present in the attribute value assertion. +- **non-null set intersection:** Evaluates to TRUE if and only if at least one of the asserted members is present in the attribute. + +## 4.4 Notifications + +The framework needs to support the ability to: + +- deliver notifications; +- subscribe for notification types; +- forward notifications to multiple destinations; +- filter notifications; +- uniquely identify the resource that emits the notification. + +The framework must also support the requirements on notification content, clearing, and correlation algorithms found in ITU-T X.733 and ITU-T Q.821. + +# 5 Framework overview and protocol requirements + +The previous clause outlined the network management functions the framework must support. This clause and the rest of the Recommendation provide the details on how the CORBA-based TMN services will provide these functions. The aspects of the framework related to modeling objects are included in ITU-T X.780. First, a brief overview of the framework is presented; then, some basic protocol requirements are defined. + +## 5.1 Framework overview + +This framework for CORBA-based TMN interfaces is a collection of capabilities. A central piece of the framework is a set of CORBA Common Object Services. This framework defines their role in network management interfaces, and defines conventions for their use. The framework also defines support services that have not been standardized as CORBA Common Object Services, but are expected to be standard on network management interfaces conforming to this framework. IDL interfaces for these services are defined later in Annex A. + +To support the software objects representing manageable resources, the framework requires that they implement some common basic capabilities. Therefore, two base classes are defined in ITU-T X.780 for use in modeling network management resources. Managed object classes (or object classes) in information models must inherit and implement a basic set of capabilities from these base classes in order to operate within this framework. Finally, some rules and conventions are defined for information modelers developing models for use with this framework. These consist of modeling guidelines, rules for converting GDMO models for CMIP to CORBA IDL definitions, and IDL style idioms. All of these are depicted graphically in Figure 1. + +![Figure 1/Q.816 – Overview of framework. This diagram illustrates the architecture of the framework, organized into three horizontal layers. The top layer, labeled 'Superclasses:', contains 'Managed Object' and 'Managed Object Factory' as primary inheritance bases. 'Managed Object' is inherited by 'Network', 'Connection', and 'Managed Element'. 'Managed Object Factory' is inherited by 'Network Factory', 'Managed Element Factory', and 'Connection Factory'. 'Connection Factory' further branches into 'Link Factory'. 'Link' is shown as a component of 'Connection'. The middle layer, labeled 'Application-specific Objects', includes 'Heartbeat Service', 'Channel Finder' (with a database icon), 'Factory Finder' (with a database icon), 'Notification Service', 'Telecom Log Service' (with a database icon), 'Terminator Service', 'Naming Service' (with a 'Names' database icon), and 'Multiple Object Operation Service'. The bottom layer is a box labeled 'CORBA 2.3 ORB'. To the right of the top layer are icons for 'Std. Data Types', 'GDMO to IDL', 'Conventions', and 'Notification Specifications'. A small text 'T0414890-00' is in the bottom right corner.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Figure 1/Q.816 – Overview of framework. This diagram illustrates the architecture of the framework, organized into three horizontal layers. The top layer, labeled 'Superclasses:', contains 'Managed Object' and 'Managed Object Factory' as primary inheritance bases. 'Managed Object' is inherited by 'Network', 'Connection', and 'Managed Element'. 'Managed Object Factory' is inherited by 'Network Factory', 'Managed Element Factory', and 'Connection Factory'. 'Connection Factory' further branches into 'Link Factory'. 'Link' is shown as a component of 'Connection'. The middle layer, labeled 'Application-specific Objects', includes 'Heartbeat Service', 'Channel Finder' (with a database icon), 'Factory Finder' (with a database icon), 'Notification Service', 'Telecom Log Service' (with a database icon), 'Terminator Service', 'Naming Service' (with a 'Names' database icon), and 'Multiple Object Operation Service'. The bottom layer is a box labeled 'CORBA 2.3 ORB'. To the right of the top layer are icons for 'Std. Data Types', 'GDMO to IDL', 'Conventions', and 'Notification Specifications'. A small text 'T0414890-00' is in the bottom right corner. + +T0414890-00 + +**Figure 1/Q.816 – Overview of framework** + +Figure 1 shows the framework in gray. In the middle are the application-specific objects that are supported by the framework. Along the bottom is a box representing the CORBA ORB. Above that are a number of boxes with names in them representing the services that compose the framework. (Some also have icons depicting the databases they would have to maintain to perform their functions.) Along the top of the figure are icons representing two superclasses, one for managed objects and one for managed object factories. Each of the managed objects and managed object factories supported by this framework must ultimately inherit from these superclasses, respectively. Also shown on Figure 1 are icons of pages with up-turned corners representing standard object modeling conventions. + +The framework services, represented as boxes with square corners, are defined in this Recommendation. The superclasses, notifications, and object modeling conventions are defined in ITU-T X.780. + +## 5.2 Framework protocol requirements + +This clause defines the versions of the services that are required to support this framework. CORBA services and protocol specifications are defined by the Object Management Group (OMG). Table 1 shows which version of the applicable OMG specification must be supported to comply with this framework and indicates the clause in this Recommendation where detailed requirements are defined + +for the service. A later version of a service that includes all the required capabilities of the stated version complies with this framework. + +**Table 1/Q.816 – CORBA service versions** + +| Service | Version | Clause | +|------------------------------------|-----------------------------------------------------------------------------------------------|--------| +| ORB | 2.3.1 [2] | 5.2 | +| Naming Service | 1.0 [3] | 6.1 | +| Notification Service | 1.0 [4] | 6.2 | +| Telecommunications Logging Service | 1.0 [5] | 6.3 | +| Asynchronous Messaging | (determined by client system) | 6.4 | +| Security (if required) | Either the "Secure IOP protocol", or "CORBA Security SSL Interoperability", as defined in [6] | 6.5 | +| Transaction Service | 1.1 [7] | 6.6 | + +The choice of version 2.3.1 for the basic ORB capabilities is important. CORBA 2.3 includes support for the Portable Object Adapter (POA) as well as for passing objects by value. POA is important to the framework because it enables implementations based on this framework to scale up to millions of instantiated objects, a magnitude required for network management applications. The framework also makes use of value-type inheritance (which supports polymorphism) to retain flexibility but reduce the usage of CORBA "any" types, which can be inefficient and tedious for programmers. + +The Naming, Notification, and Logging services are all the initial versions available from the OMG. + +Asynchronous Messaging is really only a client-side consideration. An ORB with Asynchronous Messaging capabilities enables a client to use synchronous CORBA interfaces (those that would normally cause the client to block) in an asynchronous fashion. This capability is essential for clients that are single-threaded and cannot afford to block during network management operations. The availability of Asynchronous Messaging capabilities is important to this framework because it frees it from having to define both synchronous and asynchronous interfaces. Clients need not use an ORB with Asynchronous Messaging if they are multi-threaded and therefore can afford to block during synchronous CORBA calls. + +If security is required, this framework condones the use of ORBs that use SSL 3.0 for security until products supporting TLS become available, and the OMG migrates the CORBA Security. Until the OMG CORBA Security Service specification references TLS, the choice of which is supported in a product (if any) will have to be negotiated between individual suppliers and users. So, for now, the use of either one (or none) is compliant with this framework. + +# 6 Framework common object services requirements + +The CORBA ORB provides basic object-to-object interaction capabilities [2]. Additional capabilities are defined as separate "Common Object Services." The CORBA Common Object Services are general purpose, domain-independent services that are fundamental for developing CORBA applications composed of distributed objects. They also provide the basic building blocks for application interoperability. The services are defined with object interfaces and can be combined in many different ways and put to many uses in different applications. In a specific domain, CORBA + +Common Object Services can be used to construct higher-level facilities and object frameworks that can inter-operate across multiple platform environments. + +Many of these CORBA Common Object Services have already been implemented and are available as commercial, off-the-shelf software products. Also, programmers working in many industries will likely have experience with them in the near future. Reusing these Common Object Services instead of defining new ones strictly for the telecommunications industry or re-implementing the functionality in application-specific code will result in a quicker, more cost-efficient adoption of CORBA for network management. + +The following subclauses specify requirements on the use of CORBA Common Object Services to ensure interoperability between different network management systems and to preserve the telecommunications context. + +## 6.1 The Naming Service + +The OMG Naming Service is CORBA's directory service, or "white pages"[3]. It allows a client to build a name-to-object association called a *name binding* that other clients can then use to find the object. (CORBA object references are binary and difficult for use by humans.) A name binding is always defined relative to a *naming context*. A naming context is an object that contains a set of name bindings in which each name is locally unique. A name binding is a data structure containing two strings and an object reference (address). The *ID* string is the identifier for the binding. A second string, called "kind," is also part of the data structure. Together, the ID and kind uniquely identify an object relative to a context. Different names can be bound to an object in the same or different contexts at the same time. The naming context can also be bound to a name in another naming context. Binding contexts in other contexts creates a *naming graph* – a directed graph with nodes and labeled edges where nodes are contexts. Given a context in a naming graph, a sequence of name components (*ID-kind* pairs) can reference an object. This sequence of structures, called a *compound name*, defines a path in the naming graph that may be navigated to resolve the name and find the object. + +There is no requirement that CORBA name bindings represent a containment relationship between objects, but the concept of containment is important in network management and needs to be communicated across network management interfaces. The CORBA Naming Service is the best way to accomplish this. The following paragraphs define a series of requirements on using the CORBA Naming Service to represent the containment relationships among managed object instances. + +**(R) NAME-1** Every managed object shall have one and only one name (DN). The components of the name may be obtained from multiple federated servers. Although the OMG Naming Service supports multiple names per object, this framework restricts a managed object to using a single name. Support for multiple names is outside the scope of the framework. + +**(R) NAME-2** Since a simple name binding cannot identify an object and also contained objects, each managed object must actually have a corresponding Naming Context. A specially-named binding in each such context will bind the *ID* value "Object" with a reference to the actual managed object. (The *kind* field of this binding will be null.) Other naming contexts, representing contained managed objects, may also be bound to names in this context. + +**(R) NAME-3** The *ID* field of a name binding for a naming context representing a managed object will be application-dependent, and it may actually have semantic value beyond uniquely identifying a managed object, for a particular class of objects. For example, an *ID* value of "7" for an equipment holder object representing a slot in a shelf may indicate that this object represents the 7th slot in the shelf. Special semantic value attached to IDs will be documented for each class of managed objects as part of the managed object interface specification. Note that the *ID* field is a string. + +**(R) NAME-4** The *kind* field of a name binding for a naming context representing a managed object shall be determined by *managed object name binding information*. This is information defined as constants in IDL modules specifically for the purpose of representing possible containment relationships. See ITU-T X.780 for details on the representation of managed object name binding information. In short, however, a name binding module will contain a constant string named "kind" that will be used as the value for the *kind* field in CORBA name bindings. The value of this string will usually be the unscoped class name of the managed object. This adds value by making it easier to identify the type of an object and by reducing the likelihood of name collisions. One factor complicating this is the release of new versions of an object, for example, an *equipmentR1* that extends an *equipment* object. When the new class merely extends the capabilities of an existing class without changing its purpose (that is, it still represents the same managed resource), the *kind* field will usually be the original base class name. This, however, is ultimately up to the object modeler who defines the name binding IDL module. Using the original value will enable existing applications to continue to use the new class as if it was the old version. + +Figure 2 gives an example of name bindings according to the above requirements. In the figure, CORBA Naming Contexts are represented as folders. The contents of the folders are name bindings. The convention for representing a name component as a string with the format . is used. (Some example name bindings do not have a pointer shown in the diagram to reduce the complexity of the diagram.) The graph represents a Network object, named "CentralNet," that contains a Managed Element object named "Element9" and a Connection named "R5698." + +![Figure 2/Q.816 – Naming graph of Managed Objects. A hierarchical diagram showing naming contexts as folders and managed objects as boxes. The root context 'CentralNet' contains 'CentralNet.Network', 'NorthernNet.Network', and 'SouthernNet.Network'. It points to a context containing 'Object', 'Element9.ManagedElement', 'R5698.Connection', and 'A549.Trail'. This context points to 'Bay1.Equipment' (containing 'Version7.Software' and 'Object') and another 'Object' context. 'Bay1.Equipment' points to an 'MO' box labeled '(The Element9 ME Managed Object)'. The 'Object' context points to an 'MO' box labeled '(The R5698 Connection Managed Object)'. A separate 'MO' box labeled '(The CentralNet Network Managed Object)' is also shown.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +The diagram illustrates a naming graph of managed objects using folder-like containers for naming contexts and boxes for objects. + +- CentralNet (The local root Naming Context)**: Contains bindings for `CentralNet.Network`, `NorthernNet.Network`, and `SouthernNet.Network`. An arrow points from this context to a box labeled **MO (The CentralNet Network Managed Object)**. +- CentralNet Managed Object Context**: Contains bindings for `Object`, `Element9.ManagedElement`, `R5698.Connection`, and `A549.Trail`. Arrows point from `Element9.ManagedElement` to the **Bay1.Equipment** context and from `R5698.Connection` to the **Object** context. +- Bay1.Equipment (The Naming Context for Element9)**: Contains bindings for `Bay1.Equipment`, `Version7.Software`, and `Object`. An arrow points from `Object` to an **MO (The Element9 ME Managed Object)** box. +- Object (The Naming Context for Connection R5698)**: Contains a binding for `Object`. An arrow points from `Object` to an **MO (The R5698 Connection Managed Object)** box. + +Figure 2/Q.816 – Naming graph of Managed Objects. A hierarchical diagram showing naming contexts as folders and managed objects as boxes. The root context 'CentralNet' contains 'CentralNet.Network', 'NorthernNet.Network', and 'SouthernNet.Network'. It points to a context containing 'Object', 'Element9.ManagedElement', 'R5698.Connection', and 'A549.Trail'. This context points to 'Bay1.Equipment' (containing 'Version7.Software' and 'Object') and another 'Object' context. 'Bay1.Equipment' points to an 'MO' box labeled '(The Element9 ME Managed Object)'. The 'Object' context points to an 'MO' box labeled '(The R5698 Connection Managed Object)'. A separate 'MO' box labeled '(The CentralNet Network Managed Object)' is also shown. + +T0414900-00 + +**Figure 2/Q.816 – Naming graph of Managed Objects** + +**(R) NAME-5** Each managed system shall provide at least one local root naming context. Note on Figure 2 that the topmost naming context is referred to as a "local root" naming context. This is the naming context in which names for the topmost managed objects on the system will be bound, as well as names for certain support service objects. + +A managed system may have multiple local root naming contexts. Since managed objects cannot have multiple names, they may be bound under only one local root. Support service objects, however, may have names bound under multiple root naming contexts on the same system. One factor to consider when determining how many local root naming contexts a managed system will have is if the possibility exists that some of the managed objects might sometime have to be moved to another system. Moving an entire tree of managed objects, including the local root naming context, will be simpler than moving a subtree of objects. + +**(R) NAME-6** A managed system shall provide a local administrative procedure for assigning a CORBA name to each local root naming context on the system. All names exchanged across the managed interface will include the local root context name unless otherwise noted. This includes operation parameters and notifications. + +This feature is to enable an administration to make names globally unique. Since the managed system must ensure that all names are unique relative to the local root naming context, by assigning a globally unique name to the local root naming context an administration can ensure that all names on a managed system are unique. The mechanism used to choose a globally unique name for the local root context is up to the administration. The format of the name will be the same as used by the CORBA Naming Service, *CosNaming::Name*. Multiple components are allowed, but administrations will likely want to keep local root context names short to reduce overhead. + +In addition to making names unique, assigning a name to the local root naming context will make it easier for a managing system to resolve names. This is because the managing system can bind the local root naming contexts for all the systems it manages into its own local naming service. The name it uses for this binding will be the same name assigned to the root naming context on the managed system. See Figure 3 for an example. + +![Diagram illustrating the assignment of names to root naming contexts. A Managing System at the top contains three points labeled A, B, and C. Below it are two Managed Systems, X and Y. Managed System X contains two 'Local Root' contexts, 'Local Root = A' and 'Local Root = B'. Each local root contains an 'Element1: ManagedElement' object and an 'Object' object. Managed System Y contains one 'Local Root = C' context, which also contains an 'Element1: ManagedElement' object and an 'Object' object. Arrows from points A, B, and C in the Managing System point to the corresponding local root contexts in the managed systems. A small code snippet 'T0414910-00' is visible in the bottom right corner of the diagram area.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Diagram illustrating the assignment of names to root naming contexts. A Managing System at the top contains three points labeled A, B, and C. Below it are two Managed Systems, X and Y. Managed System X contains two 'Local Root' contexts, 'Local Root = A' and 'Local Root = B'. Each local root contains an 'Element1: ManagedElement' object and an 'Object' object. Managed System Y contains one 'Local Root = C' context, which also contains an 'Element1: ManagedElement' object and an 'Object' object. Arrows from points A, B, and C in the Managing System point to the corresponding local root contexts in the managed systems. A small code snippet 'T0414910-00' is visible in the bottom right corner of the diagram area. + +**Figure 3/Q.816 – Assigning names to root naming contexts** + +Figure 3 shows two element management systems on the bottom. System "X" has two objects of type *ManagedElement*, and System "Y" has 1. Each *ManagedElement* object belongs to its own local root naming context, which means System X has two local roots and System Y has one. There is also a network management system, and the local root contexts of both EMSs have been bound into the naming service on this system. This administration has chosen to assign the unique names "A" and "B" to the local root contexts on System X, and "C" to the local root context on System Y. References to the local root naming contexts have been bound with these names in the network management System. + +Say System Y emits a notification concerning its *ManagedElement* object. The full name of that object (contained in the notification) will be "C/Element1.ManagedElement". Now let's say the NMS wants to retrieve more data from the object. In order to do so, it will have to resolve the name into a CORBA object reference. The NMS can accomplish this by simply performing a resolve operation using the full name on the local context where it bound the EMS local root contexts. Because the NMS' naming service is federated with the EMS naming services, the NMS' naming service can automatically forward the resolve operation to the naming service on the proper EMS, and return the object reference to the NMS application. + +It is anticipated that the local root naming context name will be assigned during the initialization of a new system. Once in operation, it will be extremely difficult if not impossible to change. + +Once assigned a name, the local root context's CORBA Interoperable Object Reference (IOR) will have to be bound to a naming context on the managing system, since up to now it has no idea the new system exists. This means the managed system will also have to provide a means for accessing + +the "stringified" IOR of the local root naming context. This value will then be transferred to the managing system by some means other than the management interface (e-mail, ftp, etc.). The managing system will require a way to accept this stringified IOR and bind it to a name on the managing system. As soon as the local root context's IOR is bound to a name on the managing system, the managing system can begin discovering the objects on the new system (using the Multiple Object Operation Service described later) and begin to manage it. + +![Diagram illustrating the movement of a local root naming context and its objects between systems. A Managing System at the top contains entries A, B, and C. Managed System X contains two local roots, A and B. Managed System Y contains one local root, C. Each local root contains an Element1: ManagedElement and an Object. Arrows show the mapping: A in X to A in the Managing System, B in X to B in the Managing System, and C in the Managing System to C in Y. Within each system, arrows show Element1 pointing to Object, and Object pointing to its own container.](0c08e48c08f96934cd6bc6911f3069dc_img.jpg) + +The diagram shows three main components: a Managing System at the top, Managed System X at the bottom left, and Managed System Y at the bottom right. The Managing System contains a list of entries labeled A, B, and C. Managed System X contains two local root naming contexts, 'Local Root = A' and 'Local Root = B'. Each local root contains an 'Element1: ManagedElement' and an 'Object'. Arrows indicate that 'Element1: ManagedElement' points to 'Object', and 'Object' points to its containing local root. Managed System Y contains one local root context, 'Local Root = C', which also contains an 'Element1: ManagedElement' and an 'Object' with similar internal arrows. Long arrows connect the local roots in the managed systems to the entries in the managing system: 'Local Root = A' to entry A, 'Local Root = B' to entry B, and entry C to 'Local Root = C' in Managed System Y. A small code 'T0414920-00' is visible in the bottom right corner of the diagram area. + +Diagram illustrating the movement of a local root naming context and its objects between systems. A Managing System at the top contains entries A, B, and C. Managed System X contains two local roots, A and B. Managed System Y contains one local root, C. Each local root contains an Element1: ManagedElement and an Object. Arrows show the mapping: A in X to A in the Managing System, B in X to B in the Managing System, and C in the Managing System to C in Y. Within each system, arrows show Element1 pointing to Object, and Object pointing to its own container. + +**Figure 4/Q.816 – Moving a local root naming context and contained objects** + +Figure 4 shows how a local root naming context and all of the objects contained below it can be moved to another system without changing the names of the objects. The only change that might be required would be to change the object reference bound to the name in the network management system(s). Also, any outstanding references to moved objects would have to be refreshed. Moving only part of a tree contained below a local root naming context would require re-naming those objects. + +### 6.1.1 Translating managed object names to strings + +In this framework, managed object names are represented with data structures. There may at times, however, be a need to represent managed object names as strings. The CORBA Interoperable Naming Service[Ref] specification defines rules for translating CORBA Naming Service names (which are used by this framework) to strings. Network management systems may, however, find the need to store managed object names in Lightweight Directory Access Protocol (LDAP) servers. This clause defines the rules for translating managed object names to strings suitable for use with LDAP. + +A managed object name is a data structure containing sequences of data structures with two strings named *kind* and *ID*. Managed object names are converted to Distinguished Name strings by concatenating the strings from each of the data structures in the sequence, along with equal signs ('=') and commas (,) in the order defined below. + +DN string = "0=0,1=1,2=2..." + +"0 refers to the value of the *kind* string in the first component of the sequence,1 refers to the value of the *kind* string in the second component of the sequence, etc. When placed into the LDAP DN string form, the *kind* and *ID* strings may have to contain escape sequences. See [12] for details. + +## 6.2 Notification Service + +The CORBA Notification Service supports the asynchronous exchange of event messages between clients using a subscribe-and-publish paradigm [4]. The Notification Service introduces event channels that broker event messages, notification suppliers that supply event messages, and notification consumers that consume event messages. The CORBA Notification Service preserves all of the semantics specified for the CORBA Event Service, allowing for backward compatibility with Event Service clients. The extended functionality that is important to the network management domain is the structured event, event filtering, and QoS (Quality of Service). Figure 5 depicts the general architecture of the Notification Service. + +![Diagram illustrating the Architecture of the Notification Service. A central 'Notification Service Event Channel' is shown. On the left, multiple 'Supplier' boxes are connected to the channel via 'Filter' (F) boxes. On the right, multiple 'Consumer' boxes are connected to the channel via 'Filter' (F) boxes. Each connection is labeled 'QoS'. A legend at the bottom left shows a box labeled 'F' next to the text 'Filter'. A code 'T0414930-00' is in the bottom right.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +The diagram shows a central vertical rectangle labeled "Notification Service Event Channel". To its left, three "Supplier" boxes are arranged vertically. Each Supplier box has a double-headed arrow labeled "QoS" pointing to a small box labeled "F". Each "F" box is connected to the central channel. To the right of the channel, three "Consumer" boxes are arranged vertically. Each Consumer box has a double-headed arrow labeled "QoS" pointing to a small box labeled "F". Each "F" box is connected to the central channel. Vertical dotted lines between the second and third boxes on both sides indicate additional suppliers and consumers. At the bottom left, a small box labeled "F" is shown next to the text "Filter". At the bottom right, the text "T0414930-00" is present. + +Diagram illustrating the Architecture of the Notification Service. A central 'Notification Service Event Channel' is shown. On the left, multiple 'Supplier' boxes are connected to the channel via 'Filter' (F) boxes. On the right, multiple 'Consumer' boxes are connected to the channel via 'Filter' (F) boxes. Each connection is labeled 'QoS'. A legend at the bottom left shows a box labeled 'F' next to the text 'Filter'. A code 'T0414930-00' is in the bottom right. + +Figure 5/Q.816 – Architecture of the Notification Service + +**(R) NOTIF-1** The Notification Service shall support the push interface model. The managed object interface to the event channel shall be a push supplier. + +**(R) NOTIF-2** The managed system shall instantiate the event channel object(s) that it will use. A managed system must instantiate at least one channel and may instantiate more than one. (These channels may either be OMG Notification event channels [4] or OMG Telecom Log event channels [5], or an object supporting the 3GPP NotificationIRPOperation interface [13].) The framework does not support the creation or deletion of event channels across the management interface. Local administrative procedures may be provided for this purpose. (Event channels do, however, support the creation and deletion of filters across the management interface.) + +**(R) NOTIF-3** Each event channel shall be registered with the Channel Finder service. The Channel Finder service is a support service defined by this framework in 7.2. During registration, the channel shall be associated with one or more managed objects that each forms the base of a scope of managed objects that send their events to the channel. Multiple channels may be associated with the same base managed object. A likely use of this is to have different channels for different types of events. For example, one channel might handle performance management events while another handles alarms. When the channel is registered with the Channel Finder service, it is also tied with a set of event types it handles and a set of managed object types that send their events to it. Every notification from every managed object must go to at least one channel. + +While this approach is quite flexible and enables complex arrangements of channels, because channels cannot be created across the management interface, the complexity is under the control of the implementation of the managed system. It might be as simple as a single channel monitoring all managed objects on the system. (Please note again that while channels cannot be created across the interface, individual channels do support the creation and deletion of filters across the management interface. Thus, any number of clients may register for the events they wish to receive.) + +**(R) NOTIF-4** The Notification Service shall support structured events. + +**(O) NOTIF-5** The use of sequences of structured events is optional. Sequences of structured events are defined in [4] and are used to send multiple events in one message. + +**(O) NOTIF-6** The use of typed events is optional. + +**NOTE** – If the managed system supports typed events it still must enable managing systems to receive structured events if the manager chooses. This may be accomplished by using a Notification Event Channel that supports the translation of typed event to structured events as defined in the OMG's Notification Service specification [4]. + +The message interface between suppliers and consumers shall be defined in IDL as if they were using typed events. This is done to enable capturing the notification in IDL (which cannot be done for structured events except with comments) as well as to support typed notifications for applications that wish to use them. + +Rules for creating structured notifications based on these typed operations are provided below. + +The OMG Notification Service definition does define rules for channels to automatically convert typed notifications to structured notifications. If the managed objects natively create typed notifications, but the client wishes to receive structured notifications, the OMG translation rules shall be followed by the channel. Note, however, that this arrangement is likely less efficient than both systems using typed events. If the managed objects natively create structured notifications, they shall do so according to the rules below. + +The structured notifications natively created by a managed system will differ slightly from the structured notifications created by automatic conversion from typed notifications. One reason for this is to make it possible for a managing system to tell the difference, and accept typed notifications if they are supported by the managed system. Another is to more efficiently use structured notifications. Managed systems that natively create structured notifications may exclude optional parameters from those notifications. Because a typed notification is created from a strongly-typed method invocation, a commercial notification channel that translates this to a structured notification will include any null values as name-value pairs in the body of the structured event rather than exclude them. Note that allowing managed systems that natively create structured notifications to exclude optional parameters makes it unlikely that commercial notification channels will be able to support the automatic conversion of structured events to typed events. + +In summary, if the managed objects natively create structured events, they shall do so according to the rules below. Because, for efficiency, these rules allow managed systems to exclude optional parameters from structured notifications, support for automatic conversion of these structured notifications to typed notifications by commercial notification channels is not expected. Thus, the managing system must accept structured events. If the managed system natively creates typed events, the managing system may rely on the notification channel to automatically convert them to structured events based on the OMG Notification Service's rules. Structured notifications rely upon the heavy use of CORBA "any" data types, however, which can be inefficient. Thus, in this case, the managing system will likely prefer to accept typed notifications. + +**(R) NOTIF-7** The suppliers and consumers of structured events shall follow these rules for constructing and receiving the structured events. (See Figure 6 which depicts the Notification Structure and how elements from the IDL notification definition are to be mapped into it.) + +- The `domain_type` string in the fixed header of the structured event shall be set to "telecommunications". +- The `type_name` string in the fixed header of the structured event shall be set to the scoped name of the operation defining the notification in IDL, for example, "itut\_x780::Notifications::attributeValueChange". +- The `event_name` string in the fixed header of the structured event is not used by this framework. +- Optional header fields may be included to support features like Quality of Service as appropriate. +- Each parameter in the operation shall be placed in a name-value pair in the filterable body portion of the structured event. The `fd_name` string of this pair shall be set to the name of the parameter and the type placed in the associated `fd_value` will be the type specified for the parameter. Using as an example the `equipmentAlarm` notification from the IDL presented later in this document, the first `fd_name` string would be set to "eventTime" and the first `fd_value` would contain an `ExternalTimeType` data type. Although all notification parameters go in the filterable body of the notification structure, depending on the data type of the parameter it may be difficult or even impossible to create a useful filter utilizing that parameter. Filter "matching rules" are based on the capabilities of the channel. +- Parameters that are denoted "optional" may optionally be excluded from the notification structure. If typed notifications are used, these parameters are included, but will usually have a special null value if not supported. For types for which there is no special null value (such as integers) a special type consisting of a union between the base type (such as integer) and the null type is usually defined. These union types may be excluded from structured notifications when they have a null value, but if they are included, the union type must be used. This is to enable the same filters to be used for both structured and typed notifications. +- The remainder of the body of the structured event (the non-filterable part) shall be null. +- Parameters named "operation" shall be avoided in notification operations to potentially support the use of typed notifications. (When converting typed notifications to structured notifications, the parameters of an operation are automatically placed into a notification structure by the event channel. Unfortunately, the rules developed for doing this state that the name of the operation used to issue the notification goes not in the header of the event, but in the body of the of the structure as the first name-value pair. The `fd_name` string is set to "operation" and the `fd_value` is set to a string containing the name of the operation. Using a parameter named "operation" would then result in a second name-value pair with the name "operation", and the two could be confused.) + +![Diagram showing the mapping of a notification function call to a structured event format. Arrows show 'Telecommunications' mapping to domain_type, '' mapping to type_name, and function parameters mapping to filterable body fields. The event structure is divided into Fixed Header, Variable Header, and Event Body (Filterable Body Fields and Remaining Body).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +void equipmentAlarm ( + in ExternalTimeType + in NameType + in ObjectClassType +...); + +``` + +eventTime, +source, +sourceClass, + + + +| | | | +|---------------------------------------|--------------------------------------------------|---------------------------| +| domain_type | | Fixed Header | +| type_name | | | +| event_name | | | +| ohf_name 1 | ohf_value 1 | Variable Header | +| ohf_name 2 | ohf_value 2 | | +| ... | | | +| ohf_name n | ohf_value n | | +| fd_name 1 =
"eventTime" | fd_value 1 =
value of
eventTime | Filterable Body
Fields | +| fd_name 2 =
"source" | fd_value 2 =
value of source | | +| ... | | | +| fd_name n | fd_value n | | +| remainder_of_body | | Remaining Body | + +T0414940-00 + +Diagram showing the mapping of a notification function call to a structured event format. Arrows show 'Telecommunications' mapping to domain\_type, '' mapping to type\_name, and function parameters mapping to filterable body fields. The event structure is divided into Fixed Header, Variable Header, and Event Body (Filterable Body Fields and Remaining Body). + +**Figure 6/Q.816 – Mapping notifications to structured events** + +**(R) NOTIF-8** The Notification Service specification supports filter expressions that are used to determine if the event is to be forwarded. It also supports filter expressions that "map" values in the notification to parameters used to impact the operation of the event channel, such as the QoS used in delivering the event. For example, a mapping filter might be used to map a "severity=major" field from an event (which means nothing to an event channel) to a QoS parameter "priority=1" (which does mean something to the channel). The Notification Service shall support event filtering with filter objects that support constraints expressed in the default constraint grammar specified by the OMG. The Notification Service shall also support mapping filters. + +**(R) NOTIF-9** The Notification Service reliability QoS shall support EventReliability = Persistent & ConnectionReliability = Persistent. + +*Each event is guaranteed to be delivered to all consumers registered to receive it at the time the event was delivered to the channel, within expiry limits. If the connection between the channel and a consumer is lost for any reason, the channel will persistently store any events destined for that consumer until each event time out due to expiry limits, or the consumer once again becomes* + +*available and the channel is subsequently able to deliver the events to all registered consumers. In addition, upon start from a failure the notification channel will automatically re-establish connections to all clients that were connected to it at the time the failure occurred [4].* + +**(R) NOTIF-10** The Notification Service order policy QoS shall allow the events to be delivered in the order of their arrival, i.e. FIFO. The Notification Service may also optionally support a priority-order QoS in which events could be buffered in priority order, such that higher priority events will be delivered before lower priority events. + +**(R) NOTIF-11** The Notification Service implementation deployed shall be compliant to the conformance statements of the OMG Notification Service specification with the exception of the pull interface model. + +## 6.3 Telecom Log Service + +The CORBA Telecom Log Service [5] is a CORBA-based Log Service that fully supports ITU-T X.735. The log is implemented as an Event Service or Notification Service event channel. The Log Service supports the following functionality: + +- Writing to the log: Events supplied to the log are persistently stored as log records. +- Forwarding from the log: Events supplied to the log are also forwarded to other logs or to any application that wishes to receive them. +- Log-generated events: The log itself will generate events. + +Also the Log Service provides functions of log control and management, log record manipulation, log lifecycle management. Figure 7 gives a graphic representation of the Log Service. + +![Figure 7/Q.816 – Telecom Log Service diagram](fc0735d325f0ebd9214171975c68a888_img.jpg) + +The diagram illustrates the Telecom Log Service architecture. At the center is a large rectangle labeled "Notification Service Event Channel". On the left, three boxes labeled "Supplier" are connected to the channel via arrows labeled "QoS". Each arrow points to a small box labeled "F" (Filter) which is inside the channel. On the right, three boxes labeled "Consumer" are connected to the channel via arrows labeled "QoS". Each arrow points from a small box labeled "F" (Filter) which is inside the channel. Vertical dotted lines between the suppliers and consumers indicate additional instances. Below the channel, a box labeled "Log Filter" is connected to the channel. Below the "Log Filter", a box labeled "Non-Event Writer" points to a cylinder labeled "Log Persistent Store". A double-headed arrow connects the "Log Filter" to the "Log Persistent Store". At the bottom left, a small box labeled "F" is next to the text "Filter". The code "T0414950-00" is in the bottom right corner. + +Figure 7/Q.816 – Telecom Log Service diagram + +**Figure 7/Q.816 – Telecom Log Service** + +By manipulating the Log Filter, a managing system is able to control which events are logged and which aren't, in exactly the same way it is able to control which events are forwarded and which aren't. The only exception is the "Non-event Writer," which is an application that writes data directly to the log. + +Note that the definition of the OMG's Telecom Log pre-dates this framework. The notifications from the Telecom Log are structurally different from the other notifications in this framework even though some of the names of the notifications and parameters are semantically the same. + +**(R) LOG-1** The Log Service shall support all the Notification Service requirements. Log Event Channels must be registered with the Channel Finder service. + +**(R) LOG-2** The Log Record supported by the Log Service shall be the normal `struct LogRecord`. The support of `struct TypedLogRecord` is optional. + +**(R) LOG-3** The Log Service implementation shall be compliant with the conformance statement in the OMG Telecom Log Service specification with the exception of the pull interface model. + +## 6.4 Messaging Service + +The CORBA Messaging Service covers three areas: Asynchronous Method Invocation (AMI), Time-Independent Invocation (TII), and Messaging Quality of Service (QoS) [8]. Of the three areas, the AMI has a significant role in the network management domain because it allows clients to make non-blocking requests on a CORBA object. + +Note that CORBA is designed to enable an application to invoke a method on an object as if the object was local to the application, regardless of the object's actual location. Typically, when a method is invoked on an object in a non-distributed application, control passes to that object and the calling routine blocks until the method completes and control is passed back. These semantics are maintained in CORBA. In a distributed application, however, network latency can lead to poor performance. There are five possible solutions to consider: + +- 1) Applications simply live with the delays. +- 2) TMN IDL interfaces are defined to be asynchronous. That is, management operations are always defined to return no results. Thus, invocations can be made without blocking. (This is supported by CORBA.) Results are returned later when the managed system performs a "callback" on the managing system. +- 3) TMN IDL interfaces always have two sets of operations, one that is asynchronous, and the other synchronous. +- 4) TMN IDL interfaces are defined to be synchronous, and manager applications improve performance by being multi-threaded and capable of blocking on multiple outstanding requests while continuing to process other work. +- 5) TMN IDL interfaces are defined to be synchronous, and manager applications improve performance by using the Asynchronous Method Invocation service, and an ORB that supports it. + +This framework chooses a combination of solutions 4 and 5. TMN IDL interfaces are defined to be synchronous. Manager applications that are multi-threaded can use these interfaces directly and experience good performance. Manager applications that cannot be multi-threaded shall use the AMI service to improve performance. Since multi-threaded managers do not need the AMI service, its use is optional. + +The AMI is treated as a client side language mapping issue only. In most cases, server side implementations are not required to change. In certain situations, such as with a transactional server, + +the asynchrony of a client does matter and requires server side changes if it is expected to handle transactional asynchronous requests. Transactional asynchronous requests, however, will not be addressed in this Recommendation. Figure 8 depicts the basic concept of the OMG AMI model. + +![Diagram of the OMG AMI model showing a Sync Client and an Async Client connected to an Async-aware ORB, which is connected to a Servant.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +``` + +graph TD + SC[Sync Client] -- "IDL – Stub (sync)" --> AO[Async-aware ORB] + AC[Async Client] -- "Implied-IDL – Stub (async)" --> AO + AO -- "IDL – Skeleton (sync)" --> S[Servant] + +``` + +The diagram illustrates the OMG AMI model architecture. At the top, there are two client boxes: 'Sync Client' on the left and 'Async Client' on the right. The 'Sync Client' is connected to a central 'Async-aware ORB' box via a line labeled 'IDL – Stub (sync)'. The 'Async Client' is also connected to the 'Async-aware ORB' box via a line labeled 'Implied-IDL – Stub (async)'. The 'Async-aware ORB' box is connected to a 'Servant' box at the bottom via a line labeled 'IDL – Skeleton (sync)'. Below the 'Servant' box, there is a small text label 'T0414960-00'. + +Diagram of the OMG AMI model showing a Sync Client and an Async Client connected to an Async-aware ORB, which is connected to a Servant. + +**Figure 8/Q.816 – Asynchronous-aware ORB** + +The AMI specification provides two models of asynchronous requests: *callback* and *polling*. In the *callback* model, the client passes an object reference for a `ReplyHandler` object as a parameter when it invokes a two-way asynchronous operation on a server. When the server responds, the client ORB receives the response and dispatches it to the appropriate method on the `ReplyHandler` servant so the client can handle the reply. In other words, the ORB turns the response into a request on the client's `ReplyHandler`. The `ReplyHandler` is a normal CORBA object that is implemented by the programmer as with any object implementation. In the *polling* model, the client makes the request passing in all the parameters needed for the invocation, and is returned a `Poller` object which can be queried to obtain the results of the invocation. This `Poller` is an instance of a `valueType`, which is a new IDL type introduced by the new *Objects-by-Value* specification. A `valueType` has both data members and methods, which when invoked are just local function calls and not distributed CORBA operation invocations. + +The value of the Asynchronous Method Invocation capability in network management applications is that it enables managing systems that wish to use asynchronous method calls to inter-operate with managed systems using the same interface definitions as those used by synchronous clients. No changes are required in the interface definition or the implementation of the managed system. The following requirements are proposed for implementations that optionally wish to support asynchronous method invocations (but not transactions with "ACID" capabilities). + +**(O) AMI-1** The AMI-aware CORBA implementation shall at least support the callback programming model. + +**(O) AMI-2** For each operation in an IDL interface, the AMI-aware CORBA implementation shall generate corresponding asynchronous callback method signatures. These signatures are described in implied-IDL which is used to generate language-specific operation signatures. + +**(O) AMI-3** The AMI-aware CORBA ORB shall pass a type-specific `ExceptionHolder` value instance that contains the marshaled exceptions as its state to the `ReplyHandler` when exception + +replies are returned from the CORBA object. The AMI-aware IDL compiler would generate a type-specific `ExceptionHolder` for each IDL interface. + +**(O) AMI-4** The AMI-aware IDL compiler shall generate a type-specific reply handler for each IDL interface. The client will implement and register a reply handler with each asynchronous request and receive a callback when the reply is returned for that request. This reply handler is derived from the generic `Messaging::ReplyHandler`. + +## 6.5 Security Service + +The CORBA Security Service comprises the security functionality of authentication of principals (human users and objects), authorization of access to objects by principals, security auditing, communication security, non-repudiation, and administration [6]. All of this may be overkill for many applications, though. Instead, applications might require only the communication security and system-level authentication functionality based on Transport Layer Security (TLS) technology (and its precursor, SSL) for availability and simplicity reasons. Finally, some applications might require no security. The optional requirements below, therefore, reflect three possible choices: + +- 1) No security. +- 2) ORBs use SSL to provide communications security and system-level authentication, which is essentially "session" security. +- 3) ORBs use the CORBA Security Service to provide communications security, authentication, non-repudiation, access control lists for groups or individuals accessing individual objects and operations, etc. + +The actual level of service to be provided on an interface is left as a matter to be negotiated between the parties supplying the managed and managing systems. + +**(O) SEC-1** The CORBA interface may optionally support either the "Secure IOP protocol," or "CORBA Security SSL Interoperability," as defined in the CORBA Security Service Specification [6]. + +**(O) SEC-2** The CORBA Security Service may be used to support its wide range of capabilities. + +**(O) SEC-3** Support for the exchange of authentication certificates shall be an option left up to the administration. + +## 6.6 Transaction Service + +In a distributed computing environment such as CORBA, it is possible that updates from some clients could be overwritten by concurrent (or near concurrent) updates from other clients unless suitable safeguards are provided. Even though the Notification Service and Telecom Log Service provide a basis for making a client aware that its update has been overwritten, they do not provide a locking mechanism to prevent the occurrence of such overwrites. The OMG Transaction Service [7] provides a comprehensive locking mechanism for preventing the overwriting of one client's update by a concurrent update from a different client. This solution is designed for high reliability. However, the OMG Transaction Service may not be required in all applications and the additional overhead incurred may not be justified. If consistency of data after concurrent updates must be supported, the transaction service from the OMG should be considered. + +**(O) TRANS-1** The CORBA interface may optionally support the OMG Transaction Service to guarantee data consistency. + +# 7 Framework support services + +This clause defines common support services included in the framework that are not standard OMG CORBA Common Object Services. Many network management applications perform functions that are not commonly required by general-purpose business applications, so it is not reasonable to expect the standard CORBA framework to supply all the necessary services for network management. This clause defines services that will be broadly used by network management applications but are not as likely to be used by many other types of applications and are therefore unlikely to become CORBA Common Object Services. These services also provide functionality required to enable the reuse of existing information models without significant changes in semantics. + +The advantages of placing this functionality in common support services is that it unburdens the managed object implementations from providing these services and allows the services to evolve to provide greater functionality without changing the managed object interfaces or implementations. The IDL describing the interfaces to these services can be found in Annex A. + +## 7.1 The Factory Finder Service + +The Factory Finder Service enables clients to find factories. A client finds a factory by querying this service with the class name of a factory. The service responds with a reference to a factory of that type. Note that the class name supplied by the client is the factory's class, not the class of the object to be created. + +The Factory Finder Service is found by looking it up in the Naming Service. + +Before factories can be found in the service, the service must know about them. Therefore, the Factory Finder Service also provides a means for factories to register and unregister themselves with the service. While it is not necessary to expose this capability across the management interface, these operations are defined to enable the implementation of the Factory Finder Service as a component, separate from the objects comprising a specific information model. Thus, once implemented, the Factory Finder Service implementation will not have to be changed when new information models with new factories are defined. The Factory Finder Service could even be acquired from a third party. + +The operations used to register and unregister channels are in a separate interface that is subclassed from the Factory Finder interface. Only the Factory Finder interface needs to be implemented to conform with this framework. The subclassed interface is provided for implementations that wish to use it to construct the Factory Finder service as a separate component. + +This is the IDL that defines the interface to the Factory Finder Service (without comments): + +``` +interface FactoryFinder { + + itut_x780::ManagedObjectFactory find ( + in ObjectType factoryClass) + raises (FactoryNotFound, itut_x780::ApplicationError); + + FactoryInfoSetType list() + raises (itut_x780::ApplicationError); + +}; // end of FactoryFinder interface + +interface FactoryFinderComponent : FactoryFinder { + + void register (in ObjectType factoryClass, + in itut_x780::ManagedObjectFactory factoryRef) + raises (itut_x780::ApplicationError); +``` + +``` + + void unregister (in ObjectClassType factoryClass, + in itut_x780::ManagedObjectFactory factoryRef) + raises (FactoryNotFound, itut_x780::ApplicationError); + + }; // end of FactoryFinderComponent interface + +``` + +The *find* operation on the *FactoryFinder* interface is used by a client to find a factory of a particular type. The *list* operation returns a list of all the factories registered with the Factory Finder. The *register* operation on the *FactoryFinderComponent* interface is used by a factory to register itself with the service, and the *unregister* operation is used by a factory to delete its registration. These last two operations should not be used by managing systems. + +**(R) FACTORY\_FINDER-1** A managed system shall instantiate at least one Factory Finder Service object. Also, each local root naming context on a system shall have at least one name binding for a Factory Finder Server Object. The value of the *ID* string in this binding shall simply identify the server, perhaps with a value similar to "FactoryFinder1". The *kind* string in the binding shall identify the class of the object ("itut\_q816::FactoryFinder"). + +**(R) FACTORY\_FINDER-2** The Factory Finder server object(s) shall support the Factory Finder interface described above and defined in the CORBA IDL in Annex A. The Factory Finder server object(s) may support the Factory Finder Component interfaces defined above. The functionality described above shall be supported. + +## 7.2 The Channel Finder Service + +It is anticipated that a large network management system might have multiple event channels. These channels might handle different types of events, or they might handle events from different sets of objects. To ensure that a client does not miss any of the events in which it is interested, a means of identifying the channels present on a managed system, and the events they are handling, is needed. The Channel Finder Service performs this function. A client can invoke an operation on this service to list all of the event channels present on a managed system, along with the events they are handling. Once the client knows about the channels, it can interact with them to arrange to receive notifications. + +A client finds a Channel Finder object by looking it up in the Naming Service. + +Before channels can be listed by the service, the service must know about them. Therefore, the Channel Finder Service also provides a means for channels to be registered and unregistered with the service. While it is not necessary to expose this capability across the management interface, these operations are defined to enable the implementation of the Channel Finder Service as a component, separate from the objects comprising a specific information model. Thus, once implemented, the Channel Finder Service implementation will not have to be changed when new information models are defined. The Channel Finder Service could even be acquired from a third party. + +The operations used to register and unregister channels are in a separate interface that is subclassed from the Channel Finder interface. Only the Channel Finder interface needs to be implemented to conform with this framework. The subclassed interface is provided for implementations that wish to use it to construct the channel finder service as a separate component. + +### 7.2.1 Channel Finder interface + +This is the IDL that defines the interface to the Channel Finder Service (without comments): + +``` + +interface ChannelFinder { + + ChannelInfoSetType list() + raises (itut_x780::ApplicationError); +}; + +``` + +``` + +}; // end of ChannelFinder interface + +interface ChannelFinderComponent : ChannelFinder { + void register (in ChannelIDType channelID, + in ObjectClassType channelClass, + in BaseAndScopeSetType baseAndScopes, + in EventSetType eventTypes, + in EventSetType excludedEventTypes, + in ScopedNameSetType sourceClasses, + in ScopedNameSetType excludedSourceClasses, + in EventChannel channel) + raises (ChannelAlreadyRegistered, + itut_x780::ApplicationError); + + void unregister (in ChannelIDType channelID) + raises (ChannelNotFound, itut_x780::ApplicationError); +}; // end of ChannelFinderComponent interface + +``` + +The *list* operation on the *ChannelFinder* interface can be used by a managing system to discover all the channels present on a managed system. The information returned is the same information included when a channel is registered, which is discussed below. The two operations on the *ChannelFinderComponent* interface are used by the managed system to register and unregister its channels with the service. These operations are not intended for use by a managing system. + +#### 7.2.1.1 Channel Finder data + +When a channel is registered, seven pieces of data are associated with the reference to the channel. First, a string identifier for the channel is specified. Second, the type of channel is identified (this framework has two types of channels: Notification channels and Log channels). + +After that, the set of objects covered by the channel is specified by a set of managed object names and "scopes" of objects contained below them. See 7.4.1.1 for more on scopes. There is a scope for each base managed object in the set. These base objects and the objects within their associated scopes are the sets of objects that send events to this channel. If multiple channels have scopes that overlap, the channel with the base object that is the closest ancestor to the source object handles the events from that object, pursuant to some restrictions discussed below. If multiple channels have the same base object and it is the closest ancestor to a source object, all of those channels process the events from that source object. An empty set has the special meaning that all managed objects directly bound to the local root naming context that also contains this channel finder are base objects and the scope of objects sending events to the channel are the whole subtrees contained by those objects. + +Next, the types of events sent to this channel are identified. This is done with two sets of strings. The *eventTypes* set explicitly includes the name of each type of event sent to this channel. An example event type is "itut\_x780::Notifications::equipmentAlarm". An empty set has the special meaning that all types of events are sent to this channel. The *excludedEventTypes* set lists the types of events that are not sent to this channel. If the *eventTypes* string set is null, then all events except those listed in the *excludedEventTypes* set are sent to the channel. If the *eventTypes* string set is not null, the *excludedEventTypes* parameter should be empty and is ignored. + +Finally, the types of objects sending events to this channel are identified. This is also done with two sets of strings. The *sourceClasses* set explicitly includes the name of each managed object class that sends events to this channel. An example object class name is "itut\_m3120::Equipment". An empty set has the special meaning that all types of managed objects send events to this channel. The *excludedSourceClasses* set lists the names of managed object classes that do not send events to this + +channel. If the *sourceClasses* string set is null, then all managed object classes except those listed in the *excludedSourceClasses* set send events to the channel. If the *sourceClasses* string set is not null, the *excludedSourceClasses* parameter should be empty and is ignored. + +#### 7.2.1.2 Channel coverage + +The combination of the base objects, list of event types, and source classes identifies the events handled by a channel. This can lead to some confusing combinations. While not all of these are expected to be implemented in systems, they are explained below just in case. + +- 1) A channel may be registered with multiple base objects and scopes. +- 2) Multiple channels may be registered with the same base object. If the event lists and source object types associated with these channels also overlap, the events from objects in the overlapping scopes must be made available at all channels listing the matching event and source object types. +- 3) An attempt to re-register a channel will result in an update to that channel registration. The new information will be associated with the channel and the old information will be discarded. A notification reporting the change will be sent. +- 4) A managed object always sends an event to the channel with the associated base object that: + - has a base object and scope that includes the object; + - has the base object that is the managed object's closest superior (if other channels also have base objects and scopes that include the object); + - handles that type of event; and + - handles that class of object. + +If multiple channels tie, the managed object sends the event to all channels that tie. + +Figure 9 also graphically depicts some examples for further clarification. + +![Diagram illustrating channel coverage with two channels and a hierarchy of managed objects.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +The diagram shows a hierarchy of managed objects represented by circles. At the top is a single circle. Below it are three circles, each connected to the top circle by a line labeled "Containment Relationship". The leftmost of these three circles is labeled "Managed Object". Below each of these three circles are three more circles, forming a tree structure. On the right side, a large oval encloses the bottom two sub-trees (the middle and rightmost circles and their descendants). An arrow labeled "Channel Finder Association" points from a box for "Channel 2" to the top circle of this oval. Another arrow points from a box for "Channel 1" to the top-most circle of the entire hierarchy. + +Channel 1 +Event types = all +Source classes = all + +Channel 2 +Event types = equipmentAlarm +Source classes = circuitPack + +Managed Object + +Containment Relationship + +Equipment alarms from circuit packs in this subtree go to Channel 2. All other notifications go to Channel 1. + +T0414970-00 + +Diagram illustrating channel coverage with two channels and a hierarchy of managed objects. + +Figure 9/Q.816 – Channel Example Event + +#### 7.2.1.3 Channel Finder notification + +A special notification has been defined that must be sent whenever a channel registration is added, removed, or modified. This notification must be sent on all channels registered immediately before the change occurred. Since this notification is emitted by the channel finder instead of a managed object, and since it is sent to all channels, the channel finder shall not list the channel change notification along with the other notifications handled by a channel. The IDL describing this notification is: + +``` +void channelChange ( + in ChannelModificationType channelModification, + in ChannelInfoType channelInfo +); +``` + +The channel modification parameter indicates if a channel has been added, deleted, or modified (in terms of the event types it handles). The channel information parameter provides a string describing the type of channel, a reference to the channel, the base object(s) with which it is associated, and the source object classes and event types it handles. + +It should be noted that while this approach to supporting multiple event channels is quite flexible and therefore complicated, the degree of complication is under the control of the managed system implementation. The creation and registration of event channels across the management interface is not supported. A complex managed system might support a local administrative procedure for adding, modifying, or removing channels to tune performance, or it might just update channels through software releases. A simple system will likely have one or perhaps two channels (one for high-priority events like equipment alarms and the other for everything else) associated with the root managed object. Also, please note that precluding a managing system from creating event channels does not preclude it from creating filters and "proxy suppliers" on existing channels. This gives the client capabilities equal to creating event forwarding discriminators in OSI network management systems. + +### 7.2.2 Channel Finder requirements + +**(R) CHANNEL\_FINDER-1** A managed system shall instantiate at least one Channel Finder Service object. Also, each local root naming context on a system shall have at least one name binding for a Channel Finder Service object. The value of the *ID* string in this binding shall simply identify the server, perhaps with a value similar to "ChannelFinder1". The *kind* string in the binding shall identify the class of the object ("itut\_q816::ChannelFinder"). + +**(R) CHANNEL\_FINDER-2** The Channel Finder server object(s) shall support the Channel Finder interface described above and defined in the CORBA IDL in Annex A. The Channel Finder server object(s) may support the Channel Finder Component interfaces defined above. The functionality described above shall be supported. + +**(R) CHANNEL\_FINDER-3** Whenever a change to the channel registrations is made, the Channel Finder shall send a channel change notification on all channels registered immediately before the change. + +**(R) CHANNEL\_FINDER-4** The network of event channels reported by a managed system shall handle all alarms from all managed objects on the system. A system that lists a set of channels that does not cover all events from all managed objects on the system does not comply with this framework. + +## 7.3 The Terminator Service + +The purpose of the Terminator Service is to provide a place in the framework to implement common functionality that would otherwise have to be implemented in the managed objects. The Terminator Service is used by managing systems to delete managed objects. It does so according to the delete policy of the managed object. (ITU-T X.780 requires that every managed object have a *deletePolicy* attribute with one of three values: *notDeletable*, *deleteOnlyIfNoContainedObjects*, and *deleteContainedObjects*.) If the delete policy of the managed object is *notDeletable*, the Terminator Service does not delete the object, and instead raises an exception. If the delete policy is *deleteOnlyIfNoContainedObjects*, and the object does not contain any objects, then the Terminator Service deletes the object. Otherwise, it raises an exception. Finally, if the delete policy of the object is *deleteContainedObjects*, then the Terminator Service will delete the object as well as all of its contained objects, pursuant to some rules defined below. + +ITU-T X.780 also defines a destroy operation to be supported by all managed objects that is intended for use by the Terminator Service for actually deleting the managed object and releasing its resources. In addition to following the delete policies and actually deleting the managed objects, though, the Terminator Service is also a good place to implement code to maintain the integrity of the naming tree by removing name bindings for managed objects that are being deleted. Implementations may choose to implement this function elsewhere, but a goal of the framework is to enable implementations of managed objects that focus on representing network resources. It is believed that a service like this will help to make the implementation of managed objects simpler. + +The IDL describing the Terminator Service provides two methods for deleting a managed object. One identifies the managed object by name, the other by reference. This is the IDL that defines the delete service interface: + +``` +interface TerminatorService { + + void deleteByName (in NameType name) + raises (itut_x780::ApplicationError, + itut_x780::DeleteError); + + void deleteByRef (in itut_x780::ManagedObject mo) + raises (itut_x780::ApplicationError, + itut_x780::DeleteError); + +}; // end of TerminatorService interface +``` + +**(R) TERM-1** A managed system shall instantiate at least one Terminator Service object. Also, each local root naming context on a system shall have at least one name binding for a Terminator Service object. The value of the *ID* string in this binding shall simply identify the server, perhaps with a value similar to "Terminator1". The *kind* string in the binding shall identify the class of the object ("itut\_q816::TerminatorService"). + +**(R) TERM-2** The interface supported by the Terminator Server object(s) shall be the Terminator interface described above and defined in the CORBA IDL in Annex A. The functionality described above must be supported. + +**(R) TERM-3** The Terminator Service shall delete objects according to the objects' delete policy attribute, which is set at creation and cannot be changed. Note that the Terminator Service is not a scoped service. The Terminator Service may actually delete multiple objects in response to a single request, but its focus is on the single object requested to be deleted. The Terminator Service shall implement the following rules when deleting an object: + +- 1) No object shall ever be "orphaned." That is, no object may be deleted without deleting its subordinates. +- 2) If the object has a delete policy of *notDeletable*, the object shall not be deleted, nor are any of its subordinates if it has any. The *DeleteError* exception shall be raised with the error identifier set to the value *notDeletable*. +- 3) If the object has a delete policy of *deleteOnlyIfNoContainedObjects*, and it does not have any subordinates, the object shall be deleted. If the object has subordinates, regardless of their delete policies, it shall not be deleted nor shall any of its subordinates. The *DeleteError* exception shall be raised with the error identifier set to the value *containsObjects*. +- 4) If the object has a delete policy of *deleteContainedObjects*, and it does not have any subordinates, the object shall be deleted. If the object has subordinates, the Terminator Service shall check the delete policies of all the subordinates. If any are *notDeletable*, no objects are deleted. If any are *deleteOnlyIfNoContained* and they contain subordinates, no objects are deleted. Otherwise, the object and its subordinates are deleted. +- 5) The Terminator Service shall delete contained objects from the bottom up. If any contained object raises an exception during deletion, the Terminator Service shall not remove that object's name and shall not delete any of its superiors. The Terminator Service shall, however, continue trying to delete other contained objects. When all objects that can be deleted are deleted, the Terminator Service shall raise a *DeleteError* exception with the error identifier set to the value *undeletableContainedObject*. This best-effort approach to deleting contained objects is required to make the results deterministic. The client can identify the undeletable objects because they will be at the leaves of the tree remaining beneath the target object. +- 6) If the base object raises a *DeleteError* exception, the Terminator Service shall return the same exception (and included data). The object is not deleted and the object's name is not removed from the naming tree. + +## 7.4 The Multiple-Object Operation Service + +With potentially millions of entities to manage, there is a need for the framework to support operations on multiple objects with a single method invocation or perhaps a small number of invocations. The Multiple-Object Operation (MOO) Service provides this capability. + +It is expected that each network management platform supporting a CORBA interface will provide at least one instance of the MOO Service. (For performance reasons, it is recommended that the MOO Service, Naming Service, and the managed objects be located on the same computing platform.) Managers will interact with the service using a limited number of interactions requiring relatively low bandwidth. The service will in turn interact with managed objects using either their published CORBA interfaces or some proprietary means. This high number of interactions is expected to require higher bandwidth, thus the need to co-locate the service with the managed objects. + +Note that the MOO service is an example of application-specific access granularity discussed in clause 4. + +### 7.4.1 The MOO Service interface + +The MOO Service's interface, defined in Annex A, is weakly-typed. It provides a set of generic capabilities that may be invoked on sets of any kinds of managed objects, even objects of different types. The operations supported are: + +- Scoped get: Returns the values from each of the objects for a list of attributes. + +- Scoped update: Used to replace an attribute value or to add or remove values to/from set-valued attributes. May be used to update one or multiple attributes in a single object or multiple objects. +- Scoped delete: Deletes multiple objects. + +The scoped get operation is defined on the *BasicMooService* interface. The scoped update and delete operations are defined on the *AdvancedMooService* interface, which inherits the scoped get operation from the basic service interface. This was done to allow for some flexibility in the implementation of multiple-object operation services. A basic service need only implement the scoped get operation. + +#### 7.4.1.1 Common parameters in MOO Service operations + +Each of the scoped operations requires four parameters to define the set of objects on which the operation will be performed: + +- Base object name: The name of the object at the root of a tree of objects on which the operation will potentially be performed. +- Scope: A discriminated union identifying the objects contained under the base object on which the operation potentially will be performed. The union has four cases. Two of the cases include an integer specifying a level of objects contained below the base object. The four choices are: + - Base Object Only. If the scope is *baseObjectOnly*, then only the named target (base) object is included in the scope. + - Whole Subtree. If the scope is *wholeSubtree*, the scope is all of the objects contained below the base object, along with the base object. + - Individual Level. If the scope is *individualLevel*, the scope will also include an integer-valued *level*. All of the objects contained at a level below the base object equal to this value are in the scope. The objects directly contained by the base object are level one. If *level* equals zero, the scope is the base object. + - Base to Level. If the scope is *baseToLevel*, the scope will also include an integer-valued *level*. The scope will be all of the objects down to the given level, including the base object and the object at the given level. If *level* equals zero, the scope is the base object only. + +Note that because this framework uses some unique naming conventions, the service has to do a little work to determine the actual depth for containment-based scopes. The goal is to make it as simple as possible for the client. First, the base object name will be the entire compound name including the final component with an ID value of "Object". The service will have to "back up" to the naming context that contains this binding and start counting from there. Also, the service shall automatically follow the "Object" bindings in the managed object naming contexts within the scope. This last hop will not count towards the depth. + +- Filter: An expression written in a constraint language that is used to evaluate the attributes of an object. The operation is applied to those objects within the scope for which the filter expression evaluates to *true*. +- Language: A string indicating the language in which the filter expression is written. + +The object names are the same as the *Name* type defined by the CORBA Naming Service. The scope is a union with values as described above. Finally, the filter and language parameters are strings. + +Each of the operations may raise one of these exceptions: + +- an *InvalidParameter* exception if one of the parameters has an invalid value. The name of the invalid parameter is returned. Here are some conditions under which this exception would be raised: + - The base object name is not valid. + - An unrecognized filter language value is supplied. +- an *InvalidFilter* exception if the syntax of the filter is incorrect. This exception returns the text near the syntax error for trouble-shooting purposes. +- a *FilterComplexityLimit* exception if the syntax of the filter is correct, but the filter is too complex to be processed by the managed system. +- an *ApplicationError* exception to relate other problems on the server (such as a lack of resources) that make it impossible to carry out the requested operation. + +Note that if an expression cannot be evaluated for a particular object because the types of its attributes do not match the expression, the filter is not invalid. That object may simply fail to pass the filter. + +The other parameters for the operations as well as the return types are specific to the operation. For example, the scoped get operation takes a list of attribute names and returns a sequence of results, one from each object, with the name of the object associated with the results from that object. + +#### 7.4.1.2 MOO Service Iterators + +Because each of the operations could potentially return large amounts of data, the iterator design pattern is used for returning the results. An iterator is an object that is created to contain the results of an operation so that they may be returned to the client at a rate determined by the client. The client receives a reference to the iterator as part of the information returned by the method. The client may then invoke operations on the iterator to receive batches of results in sizes determined by the client. The iterator keeps track of how far through the results the client has progressed. + +Each time a client invokes a *get* operation on an iterator, it supplies the maximum number of responses it wishes to receive. The iterator shall return no more than the batch size requested, in a *sequence* data structure. The iterator also returns a Boolean indication if there are more results to be retrieved. The iterator may return less than the requested batch size, balancing the efficiency of returning results in a large batch with the possible need to block until more results are available. The iterator shall not return an empty sequence unless there are no more results to return, as doing so would force the client to poll the iterator. + +The managed system controls the life-cycle of the iterator. A *destroy* operation, however, is provided if the manager wants to stop retrieving results before reaching the last iteration. Upon returning the last result, the iterator shall destroy itself. The iterator may also be destroyed by the managed system if it is unused for an unreasonably long period of time. + +Note that the iterators are used to pace the return of information from the operations only, and should not control when the operations are actually invoked on individual objects. A scoped operation should be invoked on the objects and the results queued as soon as possible. Delaying the invocation of the operation on the individual managed objects until the results are requested through the iterator may be more efficient, but could lead to incorrect results or race conditions. + +The following clauses give additional details on each of the scoped operations. + +#### 7.4.1.3 Scoped Get + +The IDL signature for the scoped get operation on the basic MOO Service is: + +``` +GetResultsSetType scopedGet ( + in NameType baseName, + in ScopeType scope, + in FilterType filter, + in LanguageType language, + in StringSetType attributes, + in unsigned short howMany, + out GetResultsIterator resultsIterator) +raises (InvalidParameter, + InvalidFilter, + FilterComplexityLimit, + Itut_x780::ApplicationError); +``` + +As described above, the first four parameters are used to select a set of object on which to perform the get operation. For each of these the service will try to return a value for each of the attributes named in the "attributes" parameter, which is just a list of strings. A submitted null attribute list, however, has the special meaning that *all* attribute values for the objects that pass the filter should be returned. The types involved in the return value are: + +``` +struct AttributeValueType { // from itut_x780 framework + string attributeName; + any value; // type will depend on the attribute +}; + +typedef sequence AttributeSetType; // framework + +struct GetResultsType { + NameType name; + boolean notFilterable; + AttributeSetType attributes; + StringSetType failedAttributes; +}; + +typedef sequence GetResultsSetType; +``` + +The first two types form a *name-value pair* list. The return type is a sequence of structures, one for each object that passed the filter. In that structure is an object's name, a flag that will be true if the object could not be evaluated to see if it passed the filter, the list of attribute values from that object, and the names of any attributes that could not be retrieved from that object. Objects that could not be filtered are flagged as a special case because they may be objects in which the client was not even interested. If the object could not be filtered, the client will know the MOO server could not retrieve any attributes for that object, so the other two data members shall be empty. If an object passes the filter but an attribute value could not be retrieved either because the object did not have a matching attribute or some exception was raised on access, that attribute's name should be put on the failed attribute list for that object. + +The *howMany* parameter indicates to the service how many objects' results should be included in the first batch of responses. (Zero is allowed, forcing all results to be returned through the iterator.) The *resultsIterator* output parameter is a reference to an iterator object that may be used to retrieve additional results in batches. If all the results were returned by the *scopedGet* operation, this reference will be null. The client must destroy this object when it is finished with it, and may do so before all the results are retrieved. The functionality of the CMIP Cancel Get operation is provided in this framework by destroying the results iterator. + +#### 7.4.1.4 Scoped Update + +The IDL signature for the scoped update operation on the advanced MOO Service is: + +``` +UpdateResultsSetType scopedUpdate ( + in NameType baseName, + in ScopeType scope, + in FilterType filter, + in LanguageType language, + in ModificationSeqType modifications, + in boolean failuresOnly, + in unsigned short howMany, + out UpdateResultsIterator resultsIterator) +raises (InvalidParameter, + InvalidFilter, + filterComplexityLimit, + itut_x780::ApplicationError); +``` + +Again, the first four parameters are used to select the set of objects on which the update is performed. The modifications list is a list of structures, each with the name of an attribute, a value for that attribute, and an enumerated value indicating if the value should replace the attribute's current value, be added to the attribute's current value, or removed from it. The add and remove options are valid only if the attribute's type is a CORBA sequence and if the interface has add and remove operations for the attribute. The values in the modification list structures are passed across as CORBA *any* types. If the attribute's type is a CORBA sequence, a sequence of the proper type should be put in the *any* field, even if it contains only a single value. The IDL describing the modification list is: + +``` +enum ModificationOpType {set, add, remove}; + +struct ModificationType { + string attribute; + ModificationOpType op; + any value; +}; + +typedef sequence ModificationSeqType; +``` + +The *failuresOnly* flag is used to indicate if the client wants the service to return results for all objects meeting the scope and filter, or just those objects for which at least one of the modifications could not be performed even though the scope and filter are satisfied. + +The return value is a list of structures, each containing an object's name along with a Boolean value indicating if the object could not be evaluated to see if it passed the filter and a list of any attributes that could not be modified. If the service cannot interact with the object to determine if it passes the filter, the results for that object will have the *notFilterable* set to true and the *failedAttributes* data member will be empty. (This is flagged as a special case because the object may be one in which the client was not even interested.) The service will try to perform all the modifications in the list, in order, continuing to try the rest even if one modification fails. If any operation fails on an attribute, that attribute's name is added to the list of failures. If the *notFilterable* flag is false, and the *failedAttributes* data member is empty, the client will know all updates were performed on that object. The new types involved in the return value are: + +``` +struct UpdateResultsType { + NameType name; + boolean notFilterable; + StringSetType failedAttributes; +}; + +typedef sequence UpdateResultsSetType; +``` + +The *howMany* parameter indicates to the service how many objects' results should be included in the first batch of responses. (Zero is allowed, forcing all results to be returned through the iterator.) The *resultsIterator* output parameter is a reference to an iterator object that may be used to retrieve additional results in batches. If all the results were returned by the *scopedUpdate* operation, this reference will be null. The client must destroy this object when it is finished with it, and may do so before all the results are retrieved. + +#### 7.4.1.5 Scoped Delete + +The IDL signature for the scoped delete operation on the advanced MOO Service is: + +``` +DeleteResultsSetType scopedDelete ( + in NameType baseName, + in ScopeType scope, + in FilterType filter, + in LanguageType language, + in boolean failuresOnly, + in unsigned short howMany, + out DeleteResultsIterator resultsIterator) + raises (InvalidParameter, + InvalidFilter, + FilterComplexityLimit, + Itut_x780::ApplicationError); +``` + +Rather than accessing attribute values, this operation simply attempts to delete each object in the scope that passes the filter. + +The *failuresOnly* flag is used to indicate if the client wants the service to return results for all objects meeting the scope and filter, or just those objects that could not be deleted. Because object deletion notification are typically sent, clients may often want to choose to receive results for only those objects that could not be deleted. + +The return value lists the name of each object along with two flags that might indicate that the object could not be deleted. The *notFilterable* flag shall be true if the MOO service could not interact with the object to even determine if it passed the filter. The *notDeletable* flag shall be true if the object passed the filter, but could not be deleted, either due to its delete policy, or because it raised an exception. An object that cannot be evaluated against the filter is flagged as a special case to let the client know it may be an object that it did not even intend for deletion. + +``` +struct DeleteResultsType { + NameType name; + boolean notFilterable; + boolean notDeletable; +}; + +typedef sequence DeleteResultsSetType; +``` + +The *howMany* parameter indicates to the service how many objects' results should be included in the first batch of responses. (Zero is allowed, forcing all results to be returned through the iterator.) The *resultsIterator* output parameter is a reference to an iterator object that may be used to retrieve additional results in batches. If all the results were returned by the *scopedDelete* operation, this reference will be null. The client must destroy this object when it is finished with it, and may do so before all the results are retrieved. + +Because many objects cannot be deleted if they contain other objects, for scopes based on containment relationships the service must begin deleting the "leaf" objects that are within scope and work toward the "root" object. When deleting objects, the MOO service must follow the rules for deleting an object based on the object's delete policy as described in 7.3. Because the rules are being applied to each of the objects in the scope, starting from the bottom up, however, the effect will be different than simply trying to delete the object at the root of a subtree. Also, the MOO service is best-effort. Therefore, it is possible for some of the objects in a scoped subtree to be deleted while others aren't. These are the rules that must be applied to scoped delete operations: + +- 1) No objects may be "orphaned." That is, an object may not be deleted without deleting all of its contained (child) objects. +- 2) Performing a scoped delete on an entire subtree results in all of the objects in that subtree being deleted unless an object has a delete policy of *notDeletable*, the object raised an exception on the destroy operation, or an object has a subordinate that is not deletable. +- 3) Performing a scoped delete on part of a subtree requires evaluating each of the objects at the lowest scoped layer using the delete rules in 7.3. If an object at the lowest layer of the scope may be deleted according to these rules, it and any subordinates are deleted. If a lowest layer object cannot be deleted, it is not deleted nor are any of its superior objects. Other objects in the scope may be deleted, however, if the delete rules allow it. The service then moves up to the next layer, and so on. + +### 7.4.2 The default filter language + +This clause describes the default filtering constraint language that must be supported by all conformant implementations of the MOO Service. Conforming implementations may support other constraint grammars in addition to the grammar described here. An operation is provided on the Basic MOO Service interface to enable a client to retrieve the languages supported by a service. The grammar used in a request is indicated by a string-valued parameter named "language" on each scoped operation. A value of "MOO 1.0" (one space between "MOO" and "1.0") shall indicate the grammar described here. (A constant named *defaultLanguage* with this value is provided in the IDL module.) + +The default grammar supported by each conformant implementation shall be the default constraint grammar defined for version 1.0 of the Notification Service [4] with changes as described in the following subclauses. Note that by taking this approach, the framework fixes the support for comparison rules (or "matching rules") with the filter grammar. New rules (e.g., a case-insensitive string match) cannot be added with the addition of a new data type or attribute type. Instead, the grammar will have to be updated if new capabilities are required. + +#### 7.4.2.1 Applying the constraint language to object attributes + +The default Notification Service constraint grammar introduced the special token '\$' to denote the current event and run-time variables. For multiple-object operations, the '\$' token shall denote the "current" object as well as run-time variables. That is, one can think of the MOO Service as selecting a set of objects based on the supplied base name and scope parameter, then applying the filter expression individually to each of the objects in that set. The "current" object is the object against which the expression is being evaluated. The following examples illustrate the use of the '\$' token: + +\$administrativeState    The administrative state attribute of the current object. + +\$curtime                    A "built-in" variable named "curtime". + +The identifiers that come after the "\$." (dollar-sign period) are names of the attributes of the current object as found in the value object defined to return the attributes of an object. (See ITU-T X.780 for + +details on managed object attributes.) That is, "\$.administrativeState" refers to the member named "administrativeState" in the value type returned by a call to the *getAttributes()* operation on the current object. (It is assumed that many implementations of the MOO Service will use the *getAttributes()* operation to retrieve the attributes from an object before evaluating the filter.) + +The Notification Service constraint language, on which the MOO Service constraint language is built, has a "dot" operator (".") that can be used to access the individual members within a data structure, and data structures can be nested. Thus, an identifier like this one may be used to access a value within an attribute that has a data structure value: + +`$.systemTimingSource.primaryTimingSource` + +A comparison with an attribute name that is not present in an object always evaluates to false. To illustrate, in the expression "(A == 0) || (A != 0)" if there is no attribute named "A" present in the object both comparisons will evaluate to false and the expression will actually evaluate to false. The default Notification Service language does support an "exists" operation that can be used to test the existence of an attribute before including it in a comparison. Also, a comparison always evaluates to false if the types of the operands do not match. In the example above, if "A" is a string, the expression will be false. + +Notice that the default Notification Service constraint grammar defines a set of run-time variables (which may be better thought of as "built-in" or "pre-defined" variables) but does not allow user-defined variables in filter expressions. In fact, there is no assignment operator that would support the use of user-defined variables. There are currently no built-in variables defined for the Scoping and Filtering Service and user-defined variables are not supported. + +NOTE – Since the Notification Service evaluates objects based on the names of their attributes, care must be taken when defining attribute names (the names of the members of the attribute value object defined for an interface). An attribute of type *AdministrativeStateType* named "adminState" with a value of "unlocked" will fail a filter of "administrativeState == unlocked" because the name does not match. + +#### 7.4.2.2 Support for regular expressions + +The default Notification Service constraint language defines a substring operator to work like this: "A ~ B" is true if A is a substring of B. The default MOO Service constraint language extends the language by defining a regular expression matching operator. The '#' character is designated for this operator. Using this, "A # B" evaluates to true if the regular expression pattern defined in A is matched in B. For this framework, regular expressions are "modern" regular expressions as defined in 2.8 of POSIX 1003.2 [11]. + +A regular expression is a pattern that describes a set of strings. The inclusion of special characters known as "meta-characters" enables one string to describe a set of strings. The manual page for the "grep" command on most POSIX-compliant systems gives a complete description of regular expressions and their use. + +Regular expression matching is added to the constraint language to satisfy the requirement to match sub-strings at the beginning, middle, or end of a string. POSIX regular expressions support this capability by using meta-characters that represent the beginning or end of a string("^" and "\$"). Matching in the middle of a string is done by excluding these characters from the regular expression. Certainly, this requirement could have been met by only adding a couple of meta-characters to the string matching function. It was felt, however, that since regular expression matching is supported as a utility on POSIX-compliant systems, it made sense to go ahead and use this capability, which adds rich pattern matching to the language, rather than to require developers to implement a special capability offering far less functionality. + +Since both the notification filter language for strings and the regular expression language use "\" for the escape character, "\\\" must be used in a filter string (which will be changed by the filter string parser to "\") whenever the "\" character is to be included in the regular expression. Consider this example. The "." in a regular expression can match any single character. To make sure that the character matched is actually a "." character, the following operation might be used in a filter: 'itu\\.int' # \$.domain\_name + +#### 7.4.2.3 Support for testing set-valued and sequence-valued attributes + +Network management applications tend to rely heavily on the attributes of the managed objects, and often these attributes are actually sets or sequences of values. (Sets and sequences differ. Sets should not contain duplicates and the order of the elements is unimportant. In sequences, duplicate elements are allowed and order is important.) To support the use of set-valued and sequence-valued attributes in filter expressions, the default Notification Service constraint language needs to be extended. Two groups of extensions are required to support the use of sets and sequences. The first enables sets and sequences of literal values to be included in filter expression. The second defines operators for sets and sequences. + +##### 7.4.2.3.1 Sets and sequences of literal values + +Sets and sequences of literal values are included in filter expressions by enclosing a comma-separated list of literal values in curly braces. For example: + +| | | +|--------------------------|---------------------------------------------| +| {1, 16, 21} | A set or sequence of integers | +| {5.2, 6.8, 7.01} | A set or sequence of floating-point numbers | +| {'apple', 'orange'} | A set or sequence of strings | +| {Critical, Major, Minor} | A set or sequence of enumerated values | +| {} | A null set or sequence. | + +The literal values must be of the "simple" types defined for the Notifications Service constraint language (Boolean, short, unsigned short, long, unsigned long, float, double, char, wchar, string, wstring), or enumerated values. All values in a set or sequence must be of the same type. + +Obviously, in this constraint language, literal sets and sequences are defined in the same way. Actually, this matches the case with CORBA interface attribute types. Unlike some other interface syntax languages, OMG IDL has only a sequence structure, and no set type. To account for this, different operations for sets and sequences are defined. When a sequence operator is applied to a pair of sequences (either literal or attribute values), the sequences are treated as true sequences. That is, order is taken into account. When two sequences are involved in a set operation, however, the sequences are actually treated as sets. That is, the order of the values in the set does not matter. Also, while managed objects should never return duplicates in the value of a set-valued attribute, any duplicates should be ignored. + +##### 7.4.2.3.2 Set operators + +In order to include set-valued attributes in filter expressions, operators that work on sets are needed. This clause extends the Notification Service constraint language by defining how the operators already defined for that service are to be applied to sets. One new operator, using the caret symbol ("^"), is defined for testing the interclause of two sets. Also, two built-in functions that take sets as arguments are defined. + +Note that the default Notification Service constraint language already defines one operator that works on sets: the "in" operator. The expression "A in B" can only be applied if A is a simple type as + +defined above and B is a sequence of the same simple type. The expression evaluates to true if the value represented by A is equal to a value in B. Also, the default Notification Service constraint language supports the use of the "exist" operation on set-valued parameters. This behavior will also be supported for multiple object operations. + +In general, to use any of the set operators in an expression such as "A B" one or both operands must be a sequence of one of the types listed above in the clause on sets of literal values. If one operand is a sequence of type X, the other must either be a sequence of type X or a value of type X. Because one or both of the operands are actually sequences, not sets, the operations must ignore any duplicate values within a sequence and must not depend on any order of the values in a sequence. The operators extended to work on set-valued attributes are defined below: + +- A == B True if all the values in each operand are present in the other. +- A != B False if all the values in each operand are present in the other. +- A < B True if all the values in A are in B and B contains at least one other value not in A. +- A <= B True if all the values in A are in B. (If A is a singly-valued attribute, this is the same as "A in B".) +- A > B True if all the values in B are in A and A contains at least one other value not in B. +- A >= B True if all the values in B are in A. +- A ^ B True if any value in A is present in B (the intersection is not null). + +In addition to these operations, two built-in functions that take a set or sequence as an argument and return a single value from that set or sequence are defined: + +- MAX() Returns the highest value in the set or sequence. +- MIN() Returns the lowest value in the set or sequence. + +If no maximum or minimum can be derived from the set (because the values are not numeric), the returned value should be indeterminate and any comparison to this indeterminate value should evaluate to false. + +##### 7.4.2.3.3 Sequence operators + +To support the inclusion of sequence-valued attributes in filter expressions, operators that work on sequences are needed. This clause extends the Notification Service constraint language by defining operators that work on sequences. + +Only a single operator is defined for sequences, since the only requirement was to do equality matching on sequences. The operator defined to work on sequence-valued operands is: + +- A % B True if A and B have the same number of values and all the values in A match those in B, in order. + +The MAX and MIN built-in function, defined in the previous clause, can also be applied to sequences. + +### 7.4.3 MOO Service requirements + +This clause summarizes the Multiple Object Operation Service requirements. + +**(R) MOO-1** A managed system shall instantiate at least one MOO Server object. Also, each local root naming context on a system shall have at least one name binding for a MOO Service object. The value of the *ID* string in this binding shall simply identify the server, perhaps with a value similar to + +"MOO1". The *kind* string in the binding shall identify the class of the object ("itut\_q816::BasicMooService" or a sub-class). + +**(R) MOO-2** The interface supported by the MOO Server object(s) shall be the "Basic" MOO Service interface described above and defined in the CORBA IDL in Annex A. + +**(O) MOO-3** Optionally, the interface supported by the MOO Server object(s) may be the "Advanced" MOO Service interface described above and defined in the CORBA IDL in Annex A. + +**(R) MOO-4** The MOO Server object(s) shall at least support the default constraint language defined above for the specification of filters, and may support other grammars. The default constraint language, identified as "MOO 1.0", is the default constraint language defined by the CORBA Notification Service but extended as described above to support: + +- filtering on object attribute values rather than notification structure member values; +- regular expression matching; +- filtering on attributes containing sets or sequences of values. + +## 7.5 The Heartbeat Service + +The Heartbeat Service is used to verify the operation of the notification channels on a managed system, as well as the communications network between the managed system and managing system. It periodically sends a small notification to a managing system interested in receiving it that identifies the system that emitted the heartbeat, as well as the notification channel through which it was emitted. After configuring this service, a managing system can then set a filter for heartbeat notifications on any of the channels it is interested in to ensure that they are functioning. Since these notifications flow through the same channels, software, and networks as notifications from other resources, they periodically verify the operation of these resources. + +The Heartbeat Service is found by looking it up in the Naming Service. + +The following IDL (without comments) describes the Heartbeat Service interface: + +``` +interface Heartbeat { + + attribute SystemLabelType systemLabel; + + HeartbeatPeriodType periodGet() + raises (itut_x780::ApplicationError); + + void periodSet(in HeartbeatPeriodType period) + raises (itut_x780::ApplicationError);; + +}; // end of Heartbeat interface + +interface Notifications { + ... + void heartbeat ( + in SystemLabelType systemLabel, + in ChannelIDType channelID, + in HeartbeatPeriodType period, + in GeneralizedTimeType timeStamp + ); + ... +}; // end of Notifications interface +``` + +As can be seen, the Heartbeat service has an attribute named *systemLabel*, and operations to set and get the period between heartbeats. *SystemLabel* is a user-supplied identifier. The intended use is to allow a managing system to insert a label to identify the system providing the heartbeat. + +The Heartbeat Service periodically emits a notification on each event channel that it can find in the Channel Finder Service. The Channel Finder Service provides a listing of each channel on the system, with a channel ID for each, as well as additional information on the use of the channel. (The Channel Finder shall not list the heartbeat notification as one of the notifications it handles. Heartbeat notifications are not sent by managed objects, and are sent to all channels.) At the end of each period, the Heartbeat Service sends a notification on each of the channels listed. The notification sent to each channel includes the channel ID of that channel. + +The period between heartbeats is controlled using the *periodSet* operation. The value submitted to this operation is the period, in seconds, that the Heartbeat Service waits between emitting notifications. Updating the period causes the service to immediately emit a notification with the new period value, and begin a new period. Setting the period to zero causes the service to emit one final notification with a period value of zero, then no more (until the period is reset). + +Each notification includes the value of the *systemLabel* attribute, the ID of the channel through which the notification was sent, the current value for the period, and a timestamp. + +**(R) HEARTBEAT-1** A managed system may instantiate at least one Heartbeat Service object. If the Heartbeat Service is supported, each local root naming context on a system shall have at least one name binding for a Heartbeat Service Object. The value of the *ID* string in this binding shall simply identify the server, with a value similar to "Heartbeat1". The *kind* string in the binding shall identify the class of the object ("itut\_q816::Heartbeat"). + +**(R) HEARTBEAT-2** The Heartbeat server object(s) shall support the Heartbeat interface described above and defined in the CORBA IDL in Annex A. The functionality described above shall be supported. + +**(R) HEARTBEAT-3** Updating of the period shall cause the service to deliver a notification to all channels with the new period value and then begin a new period. Setting the period to zero shall cause the service to emit one final notification with a period value of zero, then no more (until the period is reset). + +**(R) HEARTBEAT-4** Until the period is changed, the heartbeat notifications shall be sent to all the channels once within each period. The time between heartbeat notifications being sent to a channel shall never be greater than twice the period. + +## 7.6 Other support services + +This framework anticipates the need for other network management support services but recognizes it is impractical to make them all part of one framework document. Exactly where the line gets drawn is a bit arbitrary, though. Because of its focus on TMN and the need to support existing information models, this framework includes services that equate to those provided by the CMIP protocol and the most basic TMN management information capabilities. Just as with CMIP, it is expected that additional support services will be defined, most likely in separate Recommendations. + +# 8 Compliance and conformance + +This clause defines the criteria that must be met by other standards documents claiming compliance to this framework and the functions that must be implemented by systems claiming conformance to this Recommendation. + +## 8.1 System conformance + +### 8.1.1 Conformance points + +This clause summarizes the individual functions described earlier in this Recommendation. These conformance points are then combined in profiles that must be supported by systems claiming conformance to this specification. + +- 1) An implementation claiming conformance to the Naming Service requirements must: + - support the CORBA Naming Service version specified in 5.2. + - support all of the Naming Service requirements specified in 6.1. +- 2) An implementation claiming conformance to the Notification Service requirements must: + - support either: + - the CORBA Notification Service version specified in 5.2; or + - the 3GPP NotificationIRPOperations interface specified in [13]. + - support all of the Notification Service requirements specified in 6.2. + +NOTE – Further study is required to identify a minimum subset of Notification Service capabilities that must be supported for compliance to the framework. + +- 3) An implementation claiming conformance to the Telecom Logging Service requirements must: + - support the CORBA Telecom Logging Service version specified in 5.2. + - support all of the Logging Service requirements specified in 6.3. +- 4) An implementation claiming conformance to the Security Service requirements must: + - support the Security Service version specified in 5.2. + - support all of the Security Service requirements specified in 6.5. +- 5) An implementation claiming conformance to the Transaction Service requirements must: + - support the CORBA Transaction Service version specified in 5.2. + - support the Transaction Service requirements specified in 6.6. +- 6) An implementation claiming conformance to the Factory Finder Service must: + - support the Factory Finder service interface described in 7.1 and defined in the CORBA IDL in Annex A. +- 7) An implementation claiming conformance to the Channel Finder Service must: + - support the Channel Finder service interface described in 7.2 and defined in the CORBA IDL in Annex A. +- 8) An implementation claiming conformance to the Terminator Service must: + - support the Terminator Service interface described in 7.3 and defined by the CORBA IDL in Annex A. +- 9) An implementation claiming conformance to the Basic MOO Service must: + - support the mandatory MOO Service requirements described in 7.4.3. +- 10) An implementation claiming conformance to the Advanced MOO Service must: + - support the mandatory and optional MOO Service requirements described in 7.4.3. + +- 11) An implementation claiming conformance to the Heartbeat Service must: +- support the Heartbeat Service interface described in 7.5 and defined in the CORBA IDL in Annex A. + +### 8.1.2 Basic conformance profile + +A system claiming conformance to the ITU-T.Q.816 Basic Profile shall support: + +- 1) the version of CORBA specified in 5.2. +- 2) the Naming Service requirements (See conformance point 1). +- 3) the Notification Service requirements (See conformance point 2). +- 4) the Factory Finder Service (See conformance point 6). +- 5) the Channel Finder Service (See conformance point 7). +- 6) the Terminator Service (See conformance point 8). +- 7) the Basic MOO Service (See conformance point 9). + +## 8.2 Conformance statement guidelines + +The users of this framework must be careful when writing conformance statements. Because IDL modules are being used as name spaces, they may, as allowed by OMG IDL rules, be split across files. Thus, when a module is extended its name won't change. Instead, a new IDL file will simply be added. Simply stating the name of a module in a conformance statement, therefore, will not suffice to identify a set of IDL interfaces. The conformance statement must identify a document and year of publication to make sure the right version of IDL is identified. + +# ANNEX A + +## Framework Support Services IDL + +``` +/* This IDL code is intended to be stored in a file named "itut_q816.idl" +located in the search path used by IDL compilers on your system. */ + +#ifndef ITUT_Q816_IDL +#define ITUT_Q816_IDL + +#include +#include + +#pragma prefix "itu.int" + +module itut_q816 { + + // Types imported from CosTime + typedef TimeBase::UtcT UtcT; + + // Types imported from itut_x780 + typedef itut_x780::AttributeSetType AttributeSetType; + typedef itut_x780::GeneralizedTimeType GeneralizedTimeType; + typedef itut_x780::NameType NameType; + typedef itut_x780::NameSetType NameSetType; + typedef itut_x780::ObjectClassType ObjectClassType; + typedef itut_x780::ObjectClassSetType ObjectClassSetType; + typedef itut_x780::ScopedNameType ScopedNameType; + typedef itut_x780::ScopedNameSetType ScopedNameSetType; + typedef itut_x780::StringSetType StringSetType; + typedef itut_x780::SystemLabelType SystemLabelType; +``` + +``` + +// Interfaces imported from itut_x780 (interfaces are not typedefed) +// for efficiency and clarity reasons) +// itut_x780::ManagedObject +// itut_x780::ManagedObjectFactory + +// Exceptions imported from itut_x780 (exceptions can't be typedefed) +// itut_x780::ApplicationError +// itut_x780::DeleteError + +``` + +### **// Data Types and Structures** + +``` + +/** ScopeChoice enumerates four possible choices for a scope. A +scope may include just the named base object, the entire subtree +of object below and including the base object, the objects at a certain +level below the base object (level 1 objects are directly contained by +the base object), or all of the objects down to a level, including the +base object and the level. +*/ +enum ScopeChoiceType {baseObjectOnly, wholeSubtree, individualLevel, + baseToLevel}; + +/** Scope is used to convey which objects contained under the base +object, if any, are to be included in the scope of a scoped and +filtered operation. A level does not make sense for the baseObjectOnly +and wholeSubtree choices, but does for the other two. To illustrate +the difference between the two options that include a level, a +scope choice of individualLevel with level = 1 would include all +of the objects directly contained by the base object. A scope choice +of baseToLevel with level = 1 would include all of the objects +directly contained by the base object, and the base object. +*/ + +union ScopeType switch (ScopeChoiceType) +{ + /* The baseObjectOnly and wholeSubtree cases carry no value. */ + case individualLevel: /* fall through */ + case baseToLevel: short level; +}; + +/** BaseAndScopeType combines the name of a base managed object with +a "scope" of objects contained below it. */ + +struct BaseAndScopeType { + NameType base; + ScopeType scope; +}; + +/** BaseAndScopeSetType is a set of BaseAndScopeTypes. */ + +typedef sequence BaseAndScopeSetType; + +/** ChannelIDType is a string used to contain a channel ID. */ + +typedef string ChannelIDType; + +/** EventSetType is a list of event types. It is actually just a list +of strings. The values of the strings are the names of the event types +(the strings that go in the "type_name" field of the structured event), +which are the same as the scoped names of the operation defined on the +Notifications interfaces to send the events. For example: +itut_x780::Notifications::objectCreation */ + +typedef sequence EventSetType; + +/** A channelInfo structure contains information about an event +channel. +@member channelID A string identifier for the channel. +@member channelClass the channel's scoped class name. + +``` + +``` + +@member baseAndScopes The objects and the scopes of managed objects + below them sending events to this channel. + A null list indicates that all base managed + objects on the system are covered by this + channel. +@member eventTypes The list of event types handled by this + channel. A null list indicates all event types + are handled by this channel. +@member excludedEventTypes If the eventTypes parameter is null, this + can be used to exclude event types. If + eventTypes is not null, this should be null + and is ignored. +@member sourceClasses The list of types of objects that send events + to this channel. A null list indicates all + types of managed objects send events to this + channel. +@member excludedSourceClasses If the sourceClasses parameter is null, + this can be used to exclude source classes. + If sourceClasses is not null, this should be + null and is ignored. +@member channel a reference to the channel. +*/ + +struct ChannelInfoType { + ChannelIDType channelID; + ObjectClassType channelClass; + BaseAndScopeSetType baseAndScopes; + EventSetType eventTypes; + EventSetType excludedEventTypes; + ObjectClassSetType sourceClasses; + ObjectClassSetType excludedSourceClasses; + Object channel; +}; + +/** A channel info set contains a list of channel references and the + data associated with them. */ + +typedef sequence ChannelInfoSetType; + +/** ChannelModification indicates the type of event channel + modification. */ + +enum ChannelModificationType {ChannelCreate, ChannelDelete, + ChannelUpdate}; + +/** The DeleteResultsType holds, for a single object, the results + of a scoped delete operation. If both boolean flags in the result + are false, the object was deleted. + @member name The name of the object to which these results + apply. + @member notFilterable This flag will be true if the service could not + interact with the object to see if it even + passed the filter. + @member notDeletable This flag will be true if the object could not + be deleted due to its delete policy or because + it raised an exception. + */ + + struct DeleteResultsType { + NameType name; + boolean notFilterable; + boolean notDeletable; + }; + + /** The DeleteResultsSetType is a set of results returned by the + scoped delete operation. */ + + typedef sequence DeleteResultsSetType; + +``` + +``` + +/** A factory info structure contains information about a managed +object factory. +@member factoryClass the factory's scoped class name +@member factoryRef a reference to the factory +*/ +struct FactoryInfoType { + ObjectClassType factoryClass; + itut_x780::ManagedObjectFactory factoryRef; +}; + +/** A factory info set contains a list of factory references and +their class names. */ +typedef sequence FactoryInfoSetType; + +/** A FilterType parameter conveys the filter expression used in a +scoped and filtered operation. +*/ +typedef string FilterType; + +/** GetResults structures hold a list of attribute values per object. +@member name The CORBA name of the object +@member notFilterable This flag will be true if the service could not + interact with the object to see if it even + passed the filter. If true, the attributes and + failedAttributes members will be empty. +@member attributes The list of attributes retrieved from the + object. +@member failedAttributes The list of attributes whose values could + not be retrieved from the object. +*/ +struct GetResultsType { + NameType name; + boolean notFilterable; + AttributeSetType attributes; + StringSetType failedAttributes; +}; + +/** The GetResultsSet is a set of results returned by a scoped get +operation. */ +typedef sequence GetResultsSetType; + +/** HeartbeatPeriodType contains the length of the interval between +heartbeats emitted by the Heartbeat Service. Using an unsigned short +to contain this interval limits the longest possible interval to +a little over 18 hours. */ +typedef unsigned short HeartbeatPeriodType; + +/** A LanguageType parameter conveys the filter expression language +used in a scoped and filtered operation. +*/ +typedef string LanguageType; + +/** A LanguageSetType parameter contains a sequence of Languages. */ +typedef sequence LanguageSetType; + +/** ModificationOp is used to indicate the type of update to be made to +an attribute. */ +enum ModificationOpType {set, add, remove}; + +``` + +``` + +/** Modification structures identify an attribute and a modification to + be made to it. Multiple updates may be made to a single attribute by + including multiple structures with the same attribute name in the + modification Set. + @member attrib The name of the attribute to update. + @member op The operation to be performed on the attribute. + @member val The value to be used for the update operation. + It's type will depend on the attribute. +*/ + +struct ModificationType { + string attrib; // the name of the attribute + ModificationOpType op; // operation to be performed + any value; // value used to update attrib. +}; + +/** The Modification Sequence contains a sequence of modifications to + be made (in order) to each object in a scoped update operation. */ + +typedef sequence ModificationSeqType; + +/** Update Results structures hold the name of an object, a boolean + flag indicating if all modifications to that object were successful, + and a list of the attributes that could not be updated on that object. + The list will be null if the success flag is true. + @member name the CORBA name of the object + @member notFilterable This flag will be true if the service could not + interact with the object to see if it even + passed the filter. If true, the client will + know no attributes could be set, so + the failedAttributes member will be empty. + @member failedAttributes the list of attributes that were not + correctly updated. +*/ + +struct UpdateResultsType { + NameType name; + boolean notFilterable; + StringSetType failedAttributes; +}; + +/** An Update Results Set is returned in response to a scoped update + operation (one that sets, adds to, or removes from the value of an + attribute). */ + +typedef sequence UpdateResultsSetType; + +``` + +### // Constants + +``` + +/** Default filter is to allow everything through the filter*/ + +const FilterType defaultFilter = "TRUE"; + +/** Default language is the grammar described in this document */ + +const LanguageType defaultLanguage = "MOO 1.0"; + +``` + +### // Exceptions + +``` + +/** A channel already registered exception is returned when an attempt + is made to register a channel with multiple channel IDs. */ + +exception ChannelAlreadyRegistered {}; + +/** A channel not found exception is returned when an event channel + cannot be found. */ + +``` + +``` + +exception ChannelNotFound {}; + +/** A FactoryNotFound exception is raised when a requested factory +can't be found. */ + +exception FactoryNotFound {}; + +/** A Filter Complexity Limit is raised when a filter expression in a +scoped operation is valid, but too complex to be processed. */ + +exception FilterComplexityLimit {}; + +/** An invalid filter exception is raised when a client includes a +filter expression that cannot be parsed. The text surrounding the +syntax error should be returned for trouble-shooting purposes. */ + +exception InvalidFilter {string badText;}; + +/** An Invalid Parameter exception is raised when the value of a +parameter is not valid for the operation. +@param parameter the name of the bad parameter +*/ + +exception InvalidParameter {string parameter;}; + +``` + +### **// Interfaces** + +### **// Factory Finder Interface** + +``` + +/** +This interface defines a simple service for locating a managed object +factory. +*/ + +interface FactoryFinder { + + /** This method is used to find a managed object factory. + @param factoryClass The scoped class name of the factory, + NOT the managed object to be created. + */ + + itut_x780::ManagedObjectFactory find ( + in ObjectClassType factoryClass) + raises (FactoryNotFound, itut_x780::ApplicationError); + + /** This method returns the list of factories registered + with the factory finder. */ + + FactoryInfoSetType list() + raises (itut_x780::ApplicationError); + +}; // end of FactoryFinder interface + +/** +This interface extends the FactoryFinder interface to add methods +to support the registration and unregistration of factories. +*/ + +interface FactoryFinderComponent : FactoryFinder { + + /** This method is used by factories to register themselves. + It should not be used by managing systems. + @param factoryClass The scoped class name of the factory, + NOT the managed object to be created. + */ + +``` + +``` + + @param factoryRef A reference to the factory. + */ + + void register (in ObjectClassType factoryClass, + in itut_x780::ManagedObjectFactory factoryRef) + raises (itut_x780::ApplicationError); + + /** This method is used by factories to unregister themselves, + if necessary. It should not be used by managing systems. + @param factoryClass The scoped class name of the factory, + NOT the managed object to be created. + @param factoryRef A reference to the factory. + */ + + void unregister (in ObjectClassType factoryClass, + in itut_x780::ManagedObjectFactory factoryRef) + raises (FactoryNotFound, itut_x780::ApplicationError); + +}; // end of FactoryFinderComponent interface + +``` + +### **// Channel Finder Interface** + +``` + +/** +This interface defines a simple service for locating event channels. +*/ + +interface ChannelFinder { + + /** This method returns the list of channels registered + with the channel finder. */ + + ChannelInfoSetType list() + raises (itut_x780::ApplicationError); + +}; // end of ChannelFinder interface + +/** +This interface extends the ChannelFinder interface to add methods +to support the registration and unregistration of channels. +*/ + +interface ChannelFinderComponent : ChannelFinder { + + /** This method is used by channels to register themselves. + It should not be used by managing systems. Re-registering + a channel (re-using an existing channelID) results in + updating that entry. The other information previously + associated with that entry is overwritten. A + ChannelAlreadyRegistered exception may be raised when an + attempt is made to register a channel with multiple channelIDs. + This should not be done. (The service cannot guarantee that + because two object references differ, they do not reference + the same object. It is therefore required that the managed + system ensure that the same channel is not registered twice.) + A channel change notification is sent whenever calling this + method results in a change. + @param channelID A string identifier for the channel. + @param channelClass The scoped class name of the event + channel. + @param baseAndScopes The objects and the scopes of managed + objects below them sending events to + this channel. A null list indicates + that all base managed objects on the + system are covered by this channel. + */ + +``` + +``` + + @param eventTypes The list of event types handled by + this channel. A null list indicates one + of the following: +- for event channel interfaces that do not provide an explicit query for the events types +handled by the channel (e.g. the OMG Notification channel), it implies all event types are +handled by this channel +- for event channel interfaces that do provide an explicit query for the event types +handled by the channel (e.g. 3GPP NotificationIRPOperations interface), it implies that +the explicit query must be used to determine the types of events handled. + + @param excludedEventTypes If the eventTypes parameter is null, + this can be used to exclude event + types. If eventTypes is not null, this + should be null and is ignored. + @param sourceClasses The list of types of objects that send + events to this channel. A null list + indicates all types of managed objects + send events to this channel. + @param excludedSourceClasses If the sourceClasses parameter is + null, this can be used to exclude + source classes. If sourceClasses is + not null, this should be null and is + ignored. + @param channel A reference to the channel. + */ + + void register (in ChannelIDType channelID, + in ObjectClassType channelClass, + in BaseAndScopeSetType baseAndScopes, + in EventSetType eventTypes, + in EventSetType excludedEventTypes, + in ScopedNameSetType sourceClasses, + in ScopedNameSetType excludedSourceClasses, + in Object channel) + raises (ChannelAlreadyRegistered, + itut_x780::ApplicationError); + + /** This method is used by managed systems to unregister + channels, if necessary. It should not be used by managing + systems. + @param channelID A string identifier for the channel. + */ + + void unregister (in ChannelIDType channelID) + raises (ChannelNotFound, itut_x780::ApplicationError); + +}; // end of ChannelFinderComponent interface + +``` + +### ***// Heartbeat Service Interface*** + +``` + +/** +This interface defines a service used to periodically test the +operation of the notification channels on a system. The service +supporting this interface periodically emits a short "heartbeat" +notification on each channel on the system. +*/ + +interface Heartbeat { + + /** The systemLabel attribute is sent in heartbeat + notifications. It is used to identify the heartbeat service + instance from which the notification came. Resetting this does + not cause the service to immediately emit a notification, but + the new value will be sent with the next notification. */ + + attribute SystemLabelType systemLabel; + +``` + +``` + + /** The period is the interval, in seconds, at which the + heartbeat service emits the heartbeat notification. If it is + zero, the service does not emit notifications. */ + + HeartbeatPeriodType periodGet() + raises (itut_x780::ApplicationError); + + /** Updating of the period shall cause the service to deliver a + notification to all channels with the new period value and then + begin a new period. Setting the period to zero shall cause the + service to emit one final notification with a period value of + zero, then no more (until the period is reset). + Implementations may limit the range of values supported by this + operation, particularly on the low end as excessive heartbeats + would present a drain on the managed system. An attempt to + set the period to a value outside the range supported will + result in an ApplicationError with the error code set to + invalidParameter. */ + + void periodSet(in HeartbeatPeriodType period) + raises(itut_x780::ApplicationError); + +}; // end of Heartbeat interface + +``` + +### ***// Terminator Service Interface*** + +``` + +/** +This interface defines a service that supports the deletion of managed +objects by clients. A goal of the framework is to enable +implementations in which the managed objects do not have to maintain +the naming tree information. The factories are one place to implement +the functions needed to create name bindings, and this service can be +used to clean up the naming tree after object deletion.

+ +``` + +Also, this service can implement the rules for deleting objects based +on the delete policy of the managed objects. +\*/ + +``` + +interface TerminatorService { + + /** This method is used to delete a managed object by + specifying its name. */ + + void deleteByName (in NameType name) + raises (itut_x780::ApplicationError, + itut_x780::DeleteError); + + /** This method is used to delete a managed object by + reference. */ + + void deleteByRef (in itut_x780::ManagedObject mo) + raises (itut_x780::ApplicationError, + itut_x780::DeleteError); + +}; // end of TerminatorService interface + +``` + +### ***// DeleteResultsIterator Interface*** + +``` + +/** The Delete Results Iterator interface is used to retrieve the +results from a scoped delete operation using the iterator design +pattern. */ + +``` + +``` + +interface DeleteResultsIterator { + + /** This method is used to retrieve the next "howMany" results + in the result set. + +``` + +``` + + @param howMany The maximum number of items to be returned in + the results. + @param results The next batch of results. + @return True if there are more results after those + being returned. The return value should not + be true if the results set is empty, as this + forces the client to poll for results. + Instead the call should block. + + */ + + boolean getNext(in unsigned short howMany, + out DeleteResultsSetType results) + raises (itut_x780::ApplicationError); + + /** This method is used to destroy the iterator and release its + resources. */ + + void destroy(); + +}; // end of Delete Results Iterator interface + +``` + +### ***// GetResultsIterator Interface*** + +``` + +/** The Get Results Iterator interface is used to retrieve the results +from a scoped get operation using the iterator design pattern. */ + +interface GetResultsIterator { + + /** This method is used to retrieve the next "howMany" results + in the result set. + @param howMany The maximum number of items to be returned in + the results. + @param results The next batch of results. + @return True if there are more results after those + being returned. The return value should not + be true if the results set is empty, as this + forces the client to poll for results. + Instead the call should block. + + */ + + boolean getNext(in unsigned short howMany, + out GetResultsSetType results) + raises (itut_x780::ApplicationError); + + /** This method is used to destroy the iterator and release its + resources. */ + + void destroy(); + +}; // end of Get Results Iterator interface + +``` + +### ***// UpdateResultsIterator Interface*** + +``` + +/** The Update Results Iterator interface is used to retrieve the +results from a scoped update (set, add, remove) operation using the +iterator design pattern. +*/ + +interface UpdateResultsIterator { + + /** This method is used to retrieve the next "howMany" results + in the result set. + @param howMany The maximum number of items to be returned in + the results. + @param results The next batch of results. + +``` + +``` + +@return True if there are more results after those + being returned. The return value should not + be true if the results set is empty, as this + forces the client to poll for results. + Instead the call should block. + +*/ + +boolean getNext(in unsigned short howMany, + out UpdateResultsSetType results) + raises (itut_x780::ApplicationError); + +/** This method is used to destroy the iterator and release its + resources. */ + +void destroy(); + +}; // end of Update Results Iterator interface + +``` + +### ***// BasicMooService Interface*** + +``` + +/** The basic scoping and filtering interface provides a common service + for performing attribute retrieval operations on multiple objects. +*/ + +interface BasicMooService { + + /** This operation is used to retrieve the list of filter + languages supported by the service. At the least, the + list must include the value of the defaultLanguage constant + defined above. */ + + LanguageSetType getFilterLanguages() + raises (itut_x780::ApplicationError); + + /** This operation is used to retrieve attributes from multiple + objects using a small number of method invocations. The method + returns the first batch of results, one per object. Each + result has the name of the object and a list of name-value + pairs indicating the attributes that could be retrieved with + their values. + + @param baseName The name of the object at the base of the scope + tree. + @param scope A value indicating the contained objects to + include in the scope of the operations. See + ScopeType for details. + @param filter A string containing an expression to be + evaluated with attribute values from each + object in the scope. Attribute values are + returned only for those objects for which the + expression evaluates to true. + @param language A string identifying the language in which the + filter expression is written. + @param attributes The names of the attributes for which values + should be returned. If this list is null, all + attributes are to be returned. + @param howMany The maximum number of objects for which results + should be returned in the first batch. + @param resultsIterator A reference to an iterator that can be + used to retrieve the rest of the results. This + reference will be null if all results were + returned in the first batch. + + */ + + GetResultsSetType scopedGet ( + in NameType baseName, + in ScopeType scope, + +``` + +``` + + in FilterType filter, + in LanguageType language, + in StringSetType attributes, + in unsigned short howMany, + out GetResultsIterator resultsIterator) + raises (InvalidParameter, + InvalidFilter, + FilterComplexityLimit, + itut_x780::ApplicationError); + +}; // end of BasicMooService interface + +``` + +### ***// AdvancedMooService Interface*** + +``` + +/** The advanced scoping and filtering interface provides a common +service for performing multiple-attribute updates on multiple objects, +and for deleting multiple objects. +*/ + +interface AdvancedMooService : BasicMooService { + + /** This operation is used to modify multiple attributes in +multiple objects using a small number of method invocations. +The method returns the first batch of results, a list of +objects for which one or more modifications failed. Each +result indicates the attribute(s) on that object that could not +be updated. + + @param baseName The name of the object at the base of the scope +tree. + @param scope A value indicating the contained objects to +include in the scope of the operations. See +ScopeType for details. + @param filter A string containing an expression to be +evaluated with attribute values from each +object in the scope. Updates are performed +only on those objects for which the expression +evaluates to true. + @param language A string identifying the language in which the +filter expression is written. + @param modifications The list of modifications to be made to +each object. + @param failuresOnly If true only results for failed objects +will be returned. + @param howMany The maximum number of objects for which results +should be returned in the first batch. + @param resultsIterator A reference to an iterator that can be +used to retrieve the rest of the results. This +reference will be null if all results were +returned in the first batch. + + */ + + UpdateResultsSetType scopedUpdate ( + in NameType baseName, + in ScopeType scope, + in FilterType filter, + in LanguageType language, + in ModificationSeqType modifications, + in boolean failuresOnly, + in unsigned short howMany, + out UpdateResultsIterator resultsIterator) + raises (InvalidParameter, + InvalidFilter, + FilterComplexityLimit, + itut_x780::ApplicationError); + +``` + +``` + +/** This operation is used to delete multiple objects using a +small number of method invocations. The method returns the +first batch of results, a list of the objects that could not be +deleted. + +@param baseName The name of the object at the base of the scope + tree. +@param scope A value indicating the contained objects to + include in the scope of the operations. See + ScopeType for details. +@param filter A string containing an expression to be + evaluated with attribute values from each + object in the scope. Only those objects for + which the expression evaluates to true are + deleted. +@param language A string identifying the language in which the + filter expression is written. +@param failuresOnly If true only results for failed objects + will be returned. +@param howMany The maximum number of objects for which results + should be returned in the first batch. +@param resultsIterator A reference to an iterator that can be + used to retrieve the rest of the results. This + reference will be null if all results were + returned in the first batch. + +*/ + +DeleteResultsSetType scopedDelete ( + in NameType baseName, + in ScopeType scope, + in FilterType filter, + in LanguageType language, + in boolean failuresOnly, + in unsigned short howMany, + out DeleteResultsIterator resultsIterator) + raises (InvalidParameter, + InvalidFilter, + FilterComplexityLimit, + itut_x780::ApplicationError); + +}; // end of AdvancedMooService interface + +``` + +### ***// Notifications Interface*** + +``` + +/** The notifications interface defines the notifications emitted by +the framework services, not the managed objects themselves. +*/ + +interface Notifications { + + /** The Channel Change notification is a special notification +because it is emitted by the framework (the Channel Finder) and +not a managed object. It reports the addition, deletion, or +change of a registered event channel. +@param channelModification indicates if a channel has been + added, removed, or updated. +@param channelInfo provides the information about + the affected channel. + +*/ + + void channelChange ( + in ChannelModificationType channelModification, + in ChannelInfoType channelInfo + ); + + /** This operation signature defines the notification emitted +by the heartbeat service. + +``` + +``` + + @param systemLabel the current value of the Heartbeat + service systemLabel attribute. + @param channelID the ID of the channel through which the + notification was sent. + @param period the current value of the Heartbeat + service period attribute. + @param timeStamp the current time when the notification + is emitted. + */ + + void heartbeat ( + in SystemLabelType systemLabel, + in ChannelIDType channelID, + in HeartbeatPeriodType period, + in GeneralizedTimeType timeStamp + ); + + /** These constants defines the names of the notification + declared above and are provided to help reduce errors. */ + + const string channelChangeTypeName = + "itut_q816::Notifications::channelChange"; + + const string heartbeatTypeName = + "itut_q816::Notifications::heartbeat"; + + /** These constants define the names of the parameters used in + the notifications declared above and are provided to help + reduce errors. */ + + const string channelIDName = "channelID"; + const string channelModificationName = "channelModification"; + const string channelInfoName = "channelInfo"; + const string periodName = "period"; + const string systemLabelName = "systemLabel"; + const string timeStampName = "timeStamp"; + +}; // end of Notifications interface + +}; // end of module itut_q816 + +#endif // end of #ifndef ITUT_Q816_IDL + +``` + +# ANNEX B + +## The Constraint Language BNF + +The BNF in this annex is an extension of the BNF used by the OMG's Notification Service filter language. The extensions are shown in a larger, bold font. + +## B.1 The constraint language proper in terms of lexical tokens + +``` + +:=/* empty */ + | +:=/* */ + | min + | max + | with + | random + | first +:= +:= or + | +:= and + +``` + +``` + + | +:= == + | != + | < + | <= + | > + | >= + | + | ^ /* non-null set intersection test*/ + | % /* true if sequence + operands have identical values */ +:= in + | + | in $ < Component> +:= ~ + | + | # +:= + + | - + | +:= * + | / + | +:=not + | +:= ( ) + | exist + | + | + | - + | + | TRUE + | FALSE + | + < Number> + | exist $ < Component> + | $ < Component> + | default $ < Component> + | MAX ( ) + | MIN ( ) + | + := + | + := { } + := /*empty*/ + | , + | + +``` + +## B.2 "BNF" for lexical tokens up to character set issues + +``` + +:= + | \ < Leader> < FollowSeq>< Component> := /* empty */ + | . < CompDot> + | + | + | < CompExt> /* run-time variable */ +< CompExt> := /* empty */ + | . < CompDot> + | + | +< CompDot>:= < CompExt> + | + | + | length + | d + | _type_id + | _repos_id +< CompArray>:= [ < Digits> ] < CompExt> +< CompAssoc>:= ( < Ident> ) < CompExt> +< CompPos>:= < CompExt> +< UnionPos>:= ( < UnionVal> ) < CompExt> + +``` + +``` + +< UnionVal> := /* empty */ +| +| - < Digits> +| + < Digits> +| + +:=/* */ +| +:= +| +:= +| . +| . +| . +:= +:= + +| -< +Exp>:= E +| e +:= +| +:= ' ' +:=/* */ +| +:= +| +| +| +:=\\ +|\\' + +``` + +## B.3 Character set issues + +The previous BNF has been complete up to the non-terminals , , , , and . For a particular character set, one must define the characters which make up these character classes. + +Each character set which the trading service is to support must define these character classes. This annex defines these character classes for the ASCII character set. + +``` + +:= +:= +| +| _ + is the set of alphabetic characters [A-Za-z] + is the set of digits [0-9] + is the set of ASCII characters that are not , , or + +``` + +# APPENDIX I + +## Interworking scenarios between models using ITU framework and ADSL-/ATMF-compliant models + +(Informative) + +## I.1 Introduction + +This appendix describes how systems designed using the approach in this framework may interwork with systems designed using the approach specified in the ATM Forum and the ASDM Forum. + +The following approaches have been used to define interfaces for CORBA-based managed objects: + +- A fine-grained model has a one-to-one relationship between CORBA interface instances (i.e., having their own Interoperable Object Reference, (IOR)) and managed object instances. + +- A class-grained model has one CORBA interface for each managed object class. Some other mechanism (such as managed object name placed as an input parameter for every operation in that interface) has to be supported by the CORBA class-grained interface to allow management of each managed object instance. + +A so-called grain-neutral approach uses a structure holding both the managed object name and the IOR used to provide access to each managed objects. Note that the grain-neutral approach, while requiring the client to pass the managed object instance as a parameter to each operation (i.e., looks like class-grained to the client), allows the implementation in the server to be either class-grained or fine-grained. + +The framework in this Recommendation uses a fine-grained approach, along with a value-type based *attributesGet* operation, for defining CORBA-based managed objects. The value type associated with a CORBA managed object subclass uses value-type inheritance to extend the elements of the value type associated with its superclass. + +The ATM Forum and ASDM Forum specifications includes the IOR for the class and the name of the managed object as a paired list of parameters for the operations (i.e., they are grain-neutral). The client uses the name to reference the specific entity and does not require a separate IOR for each entity. These specifications also use structures (i.e., they do not employ inheritance) for their *attributesGet* operations. + +## I.2 Terminology + +The following terms are introduced for the purpose of discussion: + +- Grain-Neutral Server – A managed system which implements objects defined using a grain-neutral model with CORBA 2.1. +- ITU Framework Server – A managed system which implements objects defined using the framework in this Recommendation, thus supporting CORBA 2.3 features. +- Grain-Neutral Managing System – A client capable of managing CORBA objects defined using grain-neutral model with CORBA 2.1. +- ITU Framework Managing System – A client capable of managing CORBA objects defined according to the framework in this Recommendation, thus supporting CORBA 2.3 features. + +## I.3 Interworking scenarios + +### I.3.1 Grain-Neutral Server migrating to ITU Framework Server + +Upon migration from a grain-neutral server, an ITU Framework server may add new capabilities; however, it must preserve the old capabilities as found in the grain-neutral version. + +The new server should implement an adapter function. This function should present the grain-neutral interfaces to existing grain-neutral managing systems. An implementation approach can employ delegation of operations invoked on grain-neutral objects to the objects built according to the framework. Such a delegation approach will issue the same operations on the individual objects as would be invoked by an ITU Framework-based managing system. + +The class-specific grain-neutral *get all attribute* operation parameters should be converted to the value type structured as per the framework in this Recommendation. + +There are functions to be performed by the interworking software beyond the differences resulting from the use of POA and value object. The delegation software needs to be customized to address the differences in the naming structure, including this framework's use of the *kind* field. For example, + +explain how the context object reference used in constructing the name needs to be replaced with *kind* field of COS naming structure. + +### I.3.2 Grain-neutral Client migrating to ITU Framework client + +Such an ITU Framework client needs to manage both grain-neutral servers as well as ITU Framework servers. + +ITU Framework client with CORBA 2.3 needs, in addition to using the naming tree for ITU Framework servers, to use the naming tree for grain-neutral servers. CORBA 2.3 implementation may require an adaptation function where the application issuing the request to an object has to be converted to be appropriate for the grain-neutral server. If the application uses the value type it has to be decomposed into the object-specific get operation for the old server. + +For an ITU Framework-based client to manage both ITU Framework-based servers and pre-ITU Framework servers, the ITU client will need to support stubs for both the ITU and pre-ITU servers. In addition, some interworking function may be needed, as discussed above and as shown in Figure I.1. + +![Diagram illustrating interworking scenarios between a Grain-neutral client and an ITU Framework client.](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +The diagram shows two client types and two server types. On the left, a 'Grain-neutral client' box is at the top, and an 'ITU Framework client' box is at the bottom. The 'ITU Framework client' box contains three ovals: 'IWF', 'Grain-Neutral stubs, etc.', and 'ITU stubs, etc.'. On the right, a 'Grain-neutral server' box is at the top, and an 'ITU Framework server' box is at the bottom. An 'Adaptation function' box is positioned between the 'ITU Framework client' and the 'ITU Framework server'. Arrows indicate the following connections: from 'Grain-neutral client' to 'Grain-neutral server'; from 'Grain-neutral client' to 'Adaptation function'; from 'ITU Framework client' to 'Grain-neutral server'; from 'ITU Framework client' to 'Adaptation function'; and from 'Adaptation function' to 'ITU Framework server'. A small text 'T0414980-00' is located at the bottom right of the diagram. + +Diagram illustrating interworking scenarios between a Grain-neutral client and an ITU Framework client. + +Figure I.1/Q.816 – Interworking scenarios + +# APPENDIX II + +## Filtering native and translated structured events + +This Recommendation defines notifications using IDL operation signatures, with the event type as the operation name, and with a separate *in* parameter of the operation for each data element of the notification. These operation signatures may be used for directly posting notifications to a channel via Typed proxy consumers, as defined in the OMG Notification Service. This is shown as the arrow labeled as (1) in Figure II.1. + +![Figure II.1/Q.816 – Example of Typed and Structured Notification Posting, with Structured Delivery. The diagram shows two notification channels. The top channel is for 'Typed Notification Posting' and involves a 'Typed Notification Provider' (1) sending to a 'Typed Notification Proxy Consumer' inside a 'Notification Channel with Typed Proxy Consumer and Structured Proxy Provider', which then sends to a 'Structure Notification Consumer' (3). The bottom channel is for 'Structured Notification Posting' and involves a 'Structured Notification Provider' (2) sending to a 'Structured Notification Proxy Consumer' inside a 'Notification Channel with Structured Notification Proxies', which then sends to a 'Structured Notification Consumer' (4).](a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg) + +Figure II.1/Q.816 – Example of Typed and Structured Notification Posting, with Structured Delivery. The diagram shows two notification channels. The top channel is for 'Typed Notification Posting' and involves a 'Typed Notification Provider' (1) sending to a 'Typed Notification Proxy Consumer' inside a 'Notification Channel with Typed Proxy Consumer and Structured Proxy Provider', which then sends to a 'Structure Notification Consumer' (3). The bottom channel is for 'Structured Notification Posting' and involves a 'Structured Notification Provider' (2) sending to a 'Structured Notification Proxy Consumer' inside a 'Notification Channel with Structured Notification Proxies', which then sends to a 'Structured Notification Consumer' (4). + +T0415600-01 + +**Figure II.1/Q.816 – Example of Typed and Structured Notification Posting, with Structured Delivery** + +Since structured events are widely supported, this Recommendation also provides an algorithm for defining a structured event report for each of the notifications defined. This defined format is used for native structured notifications posted by providers to structured proxy consumers on channels, as shown in the arrow labeled (2) in Figure II.1, and for non-translated delivery, as shown in the arrow labeled (4) in Figure II.1. + +![Figure X-2- Native Structured Notification. This diagram shows the structure of a native structured notification. It is divided into four sections: Fixed Header (domain_type, type_name, event_name), Variable Header (ohf_name_1 to ohf_name_n), Filterable Body Fields (fd_name_1 to fd_name_n), and Remaining Body (remainder_of_body). The Fixed Header is shown as a table with three columns: field name, field value, and a bracket indicating it's part of the Fixed Header. The Variable Header and Filterable Body Fields are shown as tables with two columns: field name and field value. The Remaining Body is shown as a single column: remainder_of_body.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +Figure X-2- Native Structured Notification. This diagram shows the structure of a native structured notification. It is divided into four sections: Fixed Header (domain\_type, type\_name, event\_name), Variable Header (ohf\_name\_1 to ohf\_name\_n), Filterable Body Fields (fd\_name\_1 to fd\_name\_n), and Remaining Body (remainder\_of\_body). The Fixed Header is shown as a table with three columns: field name, field value, and a bracket indicating it's part of the Fixed Header. The Variable Header and Filterable Body Fields are shown as tables with two columns: field name and field value. The Remaining Body is shown as a single column: remainder\_of\_body. + +**Figure X-2- Native Structured Notification** + +![Figure X-3 - Translated Typed to Structured Notification. This diagram shows the structure of a translated typed notification. It includes a C code snippet for 'equipmentAlarm' and a table representing the notification structure. The table is divided into sections: Fixed Header (domain_type, type_name, event_name), Variable Header (fd_name_1 to fd_name_n), Filterable Body Fields (fd_name_1 to fd_name_n), and Variable Header and Remaining Body are not used. The Fixed Header is shown as a table with three columns: field name, field value, and a bracket indicating it's part of the Fixed Header. The Variable Header and Filterable Body Fields are shown as tables with two columns: field name and field value.](4d5d6207a6d444ae745057ebc3ddcd86_img.jpg) + +Figure X-3 - Translated Typed to Structured Notification. This diagram shows the structure of a translated typed notification. It includes a C code snippet for 'equipmentAlarm' and a table representing the notification structure. The table is divided into sections: Fixed Header (domain\_type, type\_name, event\_name), Variable Header (fd\_name\_1 to fd\_name\_n), Filterable Body Fields (fd\_name\_1 to fd\_name\_n), and Variable Header and Remaining Body are not used. The Fixed Header is shown as a table with three columns: field name, field value, and a bracket indicating it's part of the Fixed Header. The Variable Header and Filterable Body Fields are shown as tables with two columns: field name and field value. + +**Figure X-3 - Translated Typed to Structured Notification** + +These native structured events are defined from typed notification definitions, as follows (summarized in Figure 6): + +- 1) The domain\_type data member is set to "Telecommunications". +- 2) The type\_name data member is set to the full name of the operation defining the event type, e.g., "itut\_X780::Notifications::communicationsAlarm". +- 3) The event\_name data member is set to the empty string. + +- 4) The name elements of the filterable body field name-value pairs are set to indicate the name of each parameter (as an example, "eventTime", "source", "sourceClass", etc.). The nth name element contains the name of the nth parameter. +- 5) The value elements of the filterable body field name-value pairs are set to indicate the value that is passed to the corresponding parameter. + +An example of a native structured event, corresponding to the standard mapping, using the normal X.780 rules, would look like the following: + +``` +domain_type = "Telecommunications" +type_name = "" +event_name = "" +fd_name1 = "" fd_value1 = +fd_name2 = "" fd_value2 = +fd_name3 = "" fd_value3 = +``` + +The OMG Notification Service defines procedures for notification channels to automatically convert Typed Events received from providers (see arrow labeled (1) in Figure II.1) into Structured notifications for delivery to consumers (see arrow labeled (2) in Figure II.1), summarized as follows: + +- 1) The domain\_type data member is set to the empty string. +- 2) The type\_name data member is set to the "%TYPED" string. +- 3) The event\_name data member is set to the empty string. +- 4) The name element of the first filterable body field name-value pair is set to the "operation" string. +- 5) The value element of the first filterable body field name-value pair is set to a string containing the fully scoped operation name. In this case, e.g., "itu\_X780::Notifications::communicationsAlarm". +- 6) The remaining name elements of the filterable body field name-value pairs are set to indicate the name of each parameter (as an example, "eventTime", "source", "sourceClass", etc.). The nth name element contains the name of the nth-1 parameter. + +The remaining value elements of the filterable body field name-value pairs are set to indicate the value that was passed for each parameter (as an example, value of eventTime, value of source, value of sourceClass, etc.). The nth value element contains the value of the nth-1 parameter. + +*Using the same example as above for native structured notification, for a translated typed event, the channel would distribute something like the following, (where fd\_namei: and fd\_valuei denote the name and value of the ith element of the filterable data name value pair list):* + +``` +domain_type = "" +type_name = "%TYPED" +event_name = "" +fd_name1 = "operation" fd_value1 = "" +fd_name2 = "" fd_value2 = +fd_name3 = "" fd_value3 = +fd_name4 = "" fd_value4 = +``` + +Note that the fully scoped operation name is inserted as the first element of the filterable data name value pair list, and each *in* parameter of the typed event operation is a subsequent element. + +An example sketch of a filter construct, using run time variables, which would test for the event type `itut_x780::Notifications::attributeValueChange` and which would work for both forms of the structured event (native and channel translated typed) above is as follows: + +``` +$typename == "%TYPED" and +$operation == "itut_x780::Notifications::attributeValueChange" + +or +$typename == "itut_x780::Notifications::attributeValueChange" +``` + +# APPENDIX III + +## Bibliography + +The following Recommendations contain information that was used in the development of this framework. As stated in the introduction, a primary design goal of this framework is to enable the reuse of existing network management information models, at least without significant semantic changes. These Recommendations provide many of the details on the ITU-T's CMIP framework, and therefore define some of the functionality the CORBA framework must support. + +- ITU-T M.3010 (2000), *Principles for a Telecommunications management network.* +- ITU-T M.3120 (2001), *CORBA generic network and NE level information model.* +- ITU-T Q.821 (2000), *Stage 2 and Stage 3 description for the Q3 interface – Alarm Surveillance.* +- ITU-T X.703 (1997), *Information technology – Open Distributed Management Architecture.* +- ITU-T X.710 (1997) | ISO/IEC 9595:1998, *Information technology – Open Systems Interconnection – Common Management Information Service.* +- ITU-T X.711 (1997) | ISO/IEC 9596-1:1998, *Information technology – Open Systems Interconnection – Common Management Information Protocol: Specification.* +- ITU-T X.711/Cor.2 (2000) *Information technology – Open Systems Interconnection – Common management information protocol: Specification – Technical Corrigendum 2: Revision to include ASN.1: 1997.* +- ITU-T X.720 (1992) | ISO/IEC 10165-1:1993, *Information technology – Open Systems Interconnection – Structure of management information: Management information model.* +- ITU-T X.720/Cor.1 (1994), *Information technology – Open Systems Interconnection – Structure of management information: Management information model – Technical Corrigendum 1.* +- ITU-T X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- ITU-T X.721/Cor.1 (1994) *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information – Technical Corrigendum 1.* +- ITU-T X.721/Cor.2 (1996) *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information – Technical Corrigendum 2.* +- ITU-T X.722 (1992) | ISO/IEC 10165-4:1992, *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects.* + +- ITU-T X.722/Amd.1 (1995) *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects – Amendment 1: Set by create and component registration.* +- ITU-T X.722/Amd.2 (1997) *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects – Amendment 2: Addition of the NO-MODIFY syntax element and guidelines extension.* +- ITU-T X.722/Amd.3 (1997) *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects – Amendment 3: Guidelines for the use of Z in formalizing the behaviour of managed objects.* +- ITU-T X.722/Cor.1 (1996) *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects – Technical Corrigendum 1.* +- ITU-T X.722/Cor.2 (2000) *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects – Technical Corrigendum 2: Revision of GDMO to include ASN.1:1997.* +- ITU-T X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function.* + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.82.7-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.82.7-199607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5cdde830a4ea1ed044525a8ff94328b624a8b965 --- /dev/null +++ b/marked/Q/T-REC-Q.82.7-199607-I_PDF-E/raw.md @@ -0,0 +1,1175 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.82.7** + +(07/96) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Functions and information flows for services in the ISDN – +Supplementary services + +--- + +Stage 2 description for call offering supplementary +services: + +## **Explicit call transfer** + +ITU-T Recommendation Q.82.7 + +(Previously CCITT Recommendation) + +--- + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------------------------|------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| Basic Recommendations | Q.4–Q.9 | +| Numbering plan and dialling procedures in the international service | Q.10–Q.11 | +| Routing plan for international service | Q.12–Q.19 | +| General Recommendations relative to signalling and switching systems (national or international) | Q.20–Q.34 | +| Tones for use in national signalling systems | Q.35–Q.39 | +| General characteristics for international telephone connections and circuits | Q.40–Q.47 | +| Signalling for satellite systems | Q.48–Q.49 | +| Signalling for circuit multiplication equipment | Q.50–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| Methodology | Q.60–Q.67 | +| Basic services | Q.68–Q.79 | +| Supplementary services | Q.80–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATION OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION Q.82.7** + +# **STAGE 2 DESCRIPTION FOR CALL OFFERING SUPPLEMENTARY SERVICES: EXPLICIT CALL TRANSFER** + +### **Summary** + +This Recommendation defines the Stage 2 of the Explicit Call Transfer (ECT) supplementary service. + +The ECT supplementary service enables a user who has two calls, each of which can be an incoming or an outgoing call, to connect the other users in the two calls. + +### **Source** + +ITU-T Recommendation Q.82.7 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996 . + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +© ITU 1996 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|--------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | Normative references..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Symbols and abbreviations ..... | 2 | +| 5 | Description..... | 2 | +| 6 | Derivation of the functional model..... | 3 | +| 6.1 | Functional model description..... | 3 | +| 6.2 | Description of functional entities..... | 4 | +| 6.3 | Relationship with a basic service..... | 4 | +| 7 | Information flows..... | 4 | +| 7.1 | Information flow diagrams..... | 4 | +| 7.2 | Definition of the individual information flows..... | 7 | +| 7.2.1 | Relationship rq..... | 7 | +| 7.2.2 | Relationship rr ..... | 7 | +| 7.2.3 | Relationship rs1 ..... | 8 | +| 7.2.4 | Relationship rs2 ..... | 9 | +| 7.2.5 | Relationship rt..... | 10 | +| 7.2.6 | Relationship ru..... | 10 | +| 8 | SDL diagrams for functional entities..... | 11 | +| 8.1 | FE1 ..... | 12 | +| 8.2 | FE2..... | 14 | +| 8.3 | FE3..... | 15 | +| 8.4 | FE4..... | 19 | +| 8.5 | FE5..... | 22 | +| 8.6 | FE6..... | 25 | +| 9 | Functional Entity Actions (FEAs)..... | 26 | +| 9.1 | FEAs of FE1 ..... | 26 | +| 9.2 | FEAs of FE2 ..... | 26 | +| 9.3 | FEAs of FE3 ..... | 26 | +| 9.4 | FEAs of FE4 ..... | 27 | +| 9.5 | FEAs of FE5 ..... | 27 | +| 9.6 | FEAs of FE6 ..... | 28 | +| 10 | Allocation of functional entities to physical locations..... | 28 | + + + +# **STAGE 2 DESCRIPTION FOR CALL OFFERING SUPPLEMENTARY SERVICES: EXPLICIT CALL TRANSFER** + +*(Geneva, 1996)* + +## **1 Scope** + +This Recommendation defines the Stage 2 of the Explicit Call Transfer (ECT) supplementary service. Stage 2 identifies the functional capabilities and the information flows needed to support the service as described in Stage 1. The Stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [2]). + +This Recommendation is specified according to the methodology specified in Recommendation Q.65 [3]. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN, it does however define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. + +The ECT supplementary service enables a user who has two calls, each of which can be an incoming or an outgoing call, to connect the other users in the two calls. + +The ECT supplementary service is applicable to all circuit-switched telecommunication services. + +This Recommendation is applicable to the Stage 3 Recommendations for the integrated services digital network. + +## **2 Normative references** + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs*. +- [2] CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*. +- [3] CCITT Recommendation Q.65 (1988), *Stage 2 of the method for the characterization of services supported by an ISDN*. +- [4] ITU-T Recommendation Q.71 (1993), *ISDN circuit mode switched bearer services*. +- [5] ITU-T Recommendation Z.100 (1993), *CCITT Specification and Description Language (SDL)*. + +## 3 Definitions + +For the purposes of this Recommendation, the following definitions apply: + +- 3.1 **integrated services digital network (ISDN)**: See 2.3/I.112 [1], definition 308. +- 3.2 **primary call**: One of the user A's (answered) calls. +- 3.3 **secondary call**: The other user A call (answered or alerting). +- 3.4 **service; telecommunications service**: See 2.2/I.112 [1], definition 201. +- 3.5 **transfer by join**: The effecting of transfer by joining together the primary and secondary calls at user A's local exchange. +- 3.6 **transfer by re-routing**: The effecting of transfer by establishing a new connection to replace the primary and secondary calls. +- 3.7 **user A**: The served user, i.e. the user requesting the ECT supplementary service. +- 3.8 **user B**: The other user in user A's primary call. +- 3.9 **user C**: The other user in user A's secondary call. + +## 4 Symbols and abbreviations + +For the purposes of this Recommendation, the following abbreviations are used. + +- CC Call Control +- CCA Call Control Agent +- ECT Explicit Call Transfer +- FE Functional Entity +- FEA Functional Entity Action +- ISDN Integrated Services Digital Network +- LE Local Exchange +- PTNX Private Telecommunications Network Exchange +- SDL Specification and Description Language +- TE Terminal Equipment + +## 5 Description + +This Stage 2 supports only one variant of the ECT supplementary service, that of transfer by join. The functional model supports interworking with transfer by re-routing, which may occur within a private network but involving users of a public network. + +Table 1 shows the states for the invocation of the ECT supplementary service. + +TABLE 1/Q.82.7 + +### **States for invocation of the ECT supplementary service** + +| Primary call | Secondary call | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Active, idle | Active, idle | +| Active, held | Active, idle (Note 2) | +| Active, idle | Active, held (Note 2) | +| Active, idle | Alerting, idle (Note 1) | +| Active, held | Alerting, idle (Note 1) | +| Active, idle | Alerting, held (Note 1) | +| NOTES
1 Only applicable for an outgoing call.
2 These two entries are identical and there is no distinction between the information flows for the two calls, the only distinction being the held state of one of the calls. | | + +The procedures are currently restricted to basic telecommunication services involving a single 64 kbit/s connection. This Recommendation is not applicable to a videotelephony call involving two 64 kbit/s connections. + +## **6 Derivation of the functional model** + +### **6.1 Functional model description** + +The functional model for the ECT supplementary service is shown in Figure 1. + +![Functional model diagram for the ECT supplementary service showing functional entities FE1 through FE6 and their interconnections labeled rq, rr, rs1, rs2, rt, and ru. It shows a primary call path and two secondary call paths to user B and user C.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates the functional model for the ECT supplementary service. It consists of several functional entities (FEs) and their interconnections: + + +- FE1** is connected to **FE2** via a link labeled **rq**. +- FE2** is connected to **FE3** via a link labeled **rr**. +- FE3** has two outgoing links labeled **rs1**, each leading to a **FE4** entity. +- From the top **FE4**, a link labeled **rs2** leads to **FE5**, which in turn connects to **FE6** (labeled **user B**) via a link labeled **rt**. +- From the bottom **FE4**, a link labeled **rs2** leads to another **FE5**, which connects to **FE6** (labeled **user C**) via a link labeled **rt**. +- Both **FE6** entities (user B and user C) have a return link labeled **ru** that connects back to **FE3**. + +Functional model diagram for the ECT supplementary service showing functional entities FE1 through FE6 and their interconnections labeled rq, rr, rs1, rs2, rt, and ru. It shows a primary call path and two secondary call paths to user B and user C. + +FIGURE 1/Q.82.7 + +#### **Functional model for the ECT supplementary service** + +### 6.2 Description of functional entities + +The Functional Entities (FEs) required by the ECT supplementary service in addition to those of basic call are as follows: + +- FE1: Transfer invoke entity; +- FE2: Transfer validate entity; +- FE3: Transfer execute entity; +- FE4: Transfer screen entity; +- FE5: Transfer complete receive entity; +- FE6: Transfer inform receive entity. + +### 6.3 Relationship with a basic service + +The relationship with a basic service is as shown in Figure 2. + +![Figure 2/Q.82.7: Relationship with a basic service. This is a complex state transition diagram showing the interaction between functional entities (FE1-FE6) and call control (CC) states. The diagram is organized into two main horizontal tracks. The top track shows a sequence of CC boxes connected by arrows labeled r2, rs1, r2, rs2, r1 or r3, and rt. FE4, FE5, and FE6 are positioned below these CC boxes. FE6 connects to a CCA box. The bottom track shows a similar sequence of CC boxes connected by arrows labeled r2, rs1, r2, rs2, r1 or r3, and rt. FE4, FE5, and FE6 are positioned above these CC boxes. FE6 connects to a CCA box. On the left, FE1, FE2, and FE3 are shown. FE1 connects to a CCA box. FE2 connects to a CC box. FE3 connects to a CC box. Arrows labeled r1 or r3, rq, rr, r2, and r1 or r3 connect these entities. Vertical arrows labeled ru connect FE6 boxes to FE3 boxes. A small code T1175230-95 is in the bottom right corner.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Figure 2/Q.82.7: Relationship with a basic service. This is a complex state transition diagram showing the interaction between functional entities (FE1-FE6) and call control (CC) states. The diagram is organized into two main horizontal tracks. The top track shows a sequence of CC boxes connected by arrows labeled r2, rs1, r2, rs2, r1 or r3, and rt. FE4, FE5, and FE6 are positioned below these CC boxes. FE6 connects to a CCA box. The bottom track shows a similar sequence of CC boxes connected by arrows labeled r2, rs1, r2, rs2, r1 or r3, and rt. FE4, FE5, and FE6 are positioned above these CC boxes. FE6 connects to a CCA box. On the left, FE1, FE2, and FE3 are shown. FE1 connects to a CCA box. FE2 connects to a CC box. FE3 connects to a CC box. Arrows labeled r1 or r3, rq, rr, r2, and r1 or r3 connect these entities. Vertical arrows labeled ru connect FE6 boxes to FE3 boxes. A small code T1175230-95 is in the bottom right corner. + +FIGURE 2/Q.82.7 + +#### Relationship with a basic service + +## 7 Information flows + +### 7.1 Information flow diagrams + +The information flow diagrams assume the existence of a primary call and a secondary call and that both calls are maintained until the completion of the transfer. Clearing of the primary and secondary calls with respect to the served user is not shown as this uses basic call information flows only. Similarly any information flows concerned with holding and retrieving the primary and secondary calls are outside the scope of this Recommendation. + +The TERMINAL DETAILS information flow may occur between both FE6s. Where there is no information to be sent at all, the information flow is not present in either direction. The information flow is only shown in one direction in Figure 3 for reasons of clarity. + +The TRANSFER ACTIVE information flow will only occur in the case of an alerting transfer where the alerting user subsequently answers. In such a case, a TERMINAL DETAILS information flow from user B's FE6 may also occur as a result of receiving the second TRANSFER INFORM indication. + +![Sequence diagram for a successful call transfer (Figure 3/Q.82.7 sheet 1 of 2).](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +The diagram illustrates a sequence of messages between several entities: FE6, FE5, FE4, FE1, FE2, FE3, FE4, FE5, and FE6. The sequence is as follows: + +- FE1 to FE2:** TRANSFER INVOKE (911, 912, 914) with *req.ind* (921, 922, 923). +- FE2 to FE3:** TRANSFER INVOKE (931, 932, 933) with *req.ind* (934). +- FE3 to FE2:** TRANSFER (Note) (934) with *resp.conf* (924, 925). +- FE2 to FE1:** TRANSFER INVOKE (915, 916, 917) with *resp.conf* (915, 916, 917). +- FE1 to FE4:** TRANSFER COMPLETE (941, 942) with *req.ind* (943, 944). +- FE4 to FE5:** TRANSFER COMPLETE (951, 952) with *req.ind* (953, 954). +- FE5 to FE6:** TRANSFER INFORM (961, 962, 963) with *req.ind* (961, 962, 963). + +Timing constraints are indicated by dashed lines and labels: *rt* (FE6 to FE5), *rs2* (FE5 to FE4), *ru* (FE4 to FE1), *rq* (FE1 to FE2), *rr* (FE2 to FE3), *rs1* (FE3 to FE4), *rs2* (FE4 to FE5), and *rt* (FE5 to FE6). A dashed box labeled *ru* encloses FE1, FE2, and FE3. A dashed box labeled *rs1* encloses FE1, FE2, FE3, and FE4. A dashed box labeled *ru* encloses FE1, FE2, FE3, FE4, and FE5. + +Sequence diagram for a successful call transfer (Figure 3/Q.82.7 sheet 1 of 2). + +T1175240-95 + +NOTE – If the optional procedures for preventing loops are provided, the information flow shown in Figure 4 occurs at this point, before proceeding with the rest of the information flow shown in this figure. + +FIGURE 3/Q.82.7 (sheet 1 of 2) + +#### **Successful call transfer** + +![Sequence diagram for a successful call transfer in Q.82.7. Lifelines: FE6 (rt), FE5 (rs2), FE4 (rq), FE1 (r), FE2 (rr), FE3 (rs1), FE4 (rs2), FE5 (rt), FE6. The process involves: 1. FE6 sends req.ind to FE5. 2. FE5 sends TERMINAL DETAILS to FE4. 3. FE4 sends req.ind to FE3. 4. FE3 sends TERMINAL DETAILS to FE6. 5. FE6 sends req.ind to FE3. 6. FE3 sends SETUP <<<<|<-- resp. conf to FE4. 7. FE4 sends TRANSFER ACTIVE to FE5. 8. FE5 sends req.ind to FE6. 9. FE6 sends TRANSFER INFORM to FE5. 10. FE5 sends req.ind to FE6. Dashed boxes labeled 'ru' and 'rs1' indicate specific protocol regions.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Sequence diagram for a successful call transfer in Q.82.7. Lifelines: FE6 (rt), FE5 (rs2), FE4 (rq), FE1 (r), FE2 (rr), FE3 (rs1), FE4 (rs2), FE5 (rt), FE6. The process involves: 1. FE6 sends req.ind to FE5. 2. FE5 sends TERMINAL DETAILS to FE4. 3. FE4 sends req.ind to FE3. 4. FE3 sends TERMINAL DETAILS to FE6. 5. FE6 sends req.ind to FE3. 6. FE3 sends SETUP <<<<|<-- resp. conf to FE4. 7. FE4 sends TRANSFER ACTIVE to FE5. 8. FE5 sends req.ind to FE6. 9. FE6 sends TRANSFER INFORM to FE5. 10. FE5 sends req.ind to FE6. Dashed boxes labeled 'ru' and 'rs1' indicate specific protocol regions. + +T1175250-95 + +FIGURE 3/Q.82.7 (sheet 2 of 2) +**Successful call transfer** + +Figure 4 shows the optional procedure for preventing loops. + +![Sequence diagram illustrating the optional loop test procedure. Lifelines are FE5, FE4, FE3, FE4, FE5. The sequence starts with FE3 sending a 'LOOP TEST' message to the second FE4. The second FE4 sends 'req.ind' to FE5. FE5 performs a 'LOOP TEST' and returns 'req.ind' to the second FE4. The second FE4 sends 'LOOP TEST' to FE3. FE3 performs a 'LOOP TEST' and returns 'resp.conf' to the second FE4. The second FE4 sends 'resp.conf' to FE4. FE4 performs a 'LOOP TEST' and returns 'resp.conf' to FE5. FE5 performs a 'LOOP TEST' and returns 'req.ind' to the first FE5. The first FE5 performs a 'LOOP TEST' and returns 'resp.conf' to the first FE4. The first FE4 performs a 'LOOP TEST' and returns 'resp.conf' to FE3. The diagram is labeled T1175260-95.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Sequence diagram illustrating the optional loop test procedure. Lifelines are FE5, FE4, FE3, FE4, FE5. The sequence starts with FE3 sending a 'LOOP TEST' message to the second FE4. The second FE4 sends 'req.ind' to FE5. FE5 performs a 'LOOP TEST' and returns 'req.ind' to the second FE4. The second FE4 sends 'LOOP TEST' to FE3. FE3 performs a 'LOOP TEST' and returns 'resp.conf' to the second FE4. The second FE4 sends 'resp.conf' to FE4. FE4 performs a 'LOOP TEST' and returns 'resp.conf' to FE5. FE5 performs a 'LOOP TEST' and returns 'req.ind' to the first FE5. The first FE5 performs a 'LOOP TEST' and returns 'resp.conf' to the first FE4. The first FE4 performs a 'LOOP TEST' and returns 'resp.conf' to FE3. The diagram is labeled T1175260-95. + +FIGURE 4/Q.82.7 +**Optional loop test procedure** + +### 7.2 Definition of the individual information flows + +#### 7.2.1 Relationship rq + +##### 7.2.1.1 Contents of TRANSFER INVOKE + +This confirmed information flow initiates a transfer. It contains the identities of the calls involving user B and user C. + +The contents of the TRANSFER INVOKE req.ind and TRANSFER INVOKE resp.conf information flows are shown in Table 2. + +TABLE 2/Q.82.7 +**TRANSFER INVOKE** + +| Name | req.ind | resp.conf | +|------------------------|---------|-----------| +| Call identities (Note) | M | - | +| Transfer result | - | M | + +NOTE – Means of providing such an identifier are outside the scope of this Recommendation. Such identification is local to relationship rq and may involve a local information flow across rq. + +#### 7.2.2 Relationship rr + +##### 7.2.2.1 Contents of TRANSFER INVOKE + +This confirmed information flow requests execution of a transfer. It contains the identities of the calls involving user B and user C. + +The contents of the TRANSFER INVOKE req.ind and TRANSFER INVOKE resp.conf information flows are shown in Table 3. + +TABLE 3/Q.82.7 +**TRANSFER INVOKE** + +| Name | req.ind | resp.conf | +|------------------------|---------|-----------| +| Call identities (Note) | M | - | +| Transfer result | - | M | + +NOTE – Means of providing such an identifier are outside the scope of this Recommendation. Such identification is local to relationship rr and may involve a local information flow across rr. + +#### 7.2.3 Relationship rs1 + +##### 7.2.3.1 Contents of TRANSFER COMPLETE + +This unconfirmed information flow indicates that a transfer has been effected. + +The contents of the TRANSFER COMPLETE req.ind information flow are shown in Table 4. + +TABLE 4/Q.82.7 +**TRANSFER COMPLETE** + +| Name | req.ind | +|-------------------------------------------------------------------------------|------------| +| Transferred number | O (Note 1) | +| Alerting indication | O (Note 2) | +| NOTES
1 Mandatory if known.
2 Mandatory if other user is being alerted. | | + +##### 7.2.3.2 Contents of TRANSFER ACTIVE + +This unconfirmed information flow indicates that answer has taken place subsequent to an alerting transfer. The contents are the same as those of a basic call SETUP resp.conf. + +##### 7.2.3.3 Contents of LOOP TEST + +This confirmed information flow indicates that a loop test has been invoked. + +There are no contents of the LOOP TEST req.ind or LOOP TEST resp.conf information flows. + +##### 7.2.3.4 Contents of LOOP TEST REJECT + +This unconfirmed information flow indicates that a loop test has failed. + +The contents of the LOOP TEST REJECT req.ind information flow is shown in Table 5. + +TABLE 5/Q.82.7 +**Contents of LOOP TEST REJECT** + +| Name | req.ind | +|--------|---------| +| Reason | M | + +#### 7.2.4 Relationship rs2 + +##### 7.2.4.1 Contents of TRANSFER COMPLETE + +This unconfirmed information flow indicates that a transfer has been effected. + +The contents of the TRANSFER COMPLETE req.ind information flow are shown in Table 6. + +TABLE 6/Q.82.7 + +###### TRANSFER COMPLETE + +| Name | req.ind | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Transferred number | O (Note 1) | +| Transferred subaddress | O (Note 2) | +| Alerting indication | O (Note 3) | +| NOTES
1 Mandatory if known and not restricted.
2 Mandatory if transfer occurs with the other user alerting, and if the TRANSFER INFORM req.ind is being sent as a result of the answer to the alerting call, and if the subaddress is known and not restricted. Otherwise, the information shall not be sent.
3 Mandatory if the other user is being alerted. | | + +##### 7.2.4.2 Contents of TRANSFER ACTIVE + +This unconfirmed information flow indicates that answer has taken place subsequent to an alerting transfer. The contents are the same as those of a basic call SETUP resp.conf. + +##### 7.2.4.3 Contents of TERMINAL DETAILS + +This unconfirmed information flow informs users of any subaddress associated with the other user involved in the transfer. + +The contents of the TERMINAL DETAILS req.ind information flow are shown in Table 7. + +TABLE 7/Q.82.7 + +###### TERMINAL DETAILS + +| Name | req.ind | +|------------------------|---------| +| Transferred subaddress | M | + +##### 7.2.4.4 Contents of LOOP TEST + +This confirmed information flow indicates that a loop test has been invoked. + +There are no contents of the LOOP TEST req.ind or LOOP TEST resp.conf information flows. + +##### 7.2.4.5 Contents of LOOP TEST REJECT + +This unconfirmed information flow indicates that a loop test has failed. + +The contents of the LOOP TEST REJECT req.ind information flow are shown in Table 8. + +TABLE 8/Q.82.7 + +###### **Contents of LOOP TEST REJECT** + +| | | +|--------|---------| +| Name | req.ind | +| Reason | M | + +#### **7.2.5 Relationship rt** + +##### **7.2.5.1 Contents of TRANSFER INFORM** + +This unconfirmed information flow informs users of the successful completion of a call transfer, and the identity of the other user. + +The contents of the TRANSFER INFORM req.ind information flow are shown in Table 9. + +TABLE 9/Q.82.7 + +###### **TRANSFER INFORM** + +| | | +|------------------------------------------------------------------------------------------------------|------------| +| Name | req.ind | +| Transferred number | O (Note 1) | +| Alerting indication | O (Note 2) | +| NOTES
1 Mandatory if known and not restricted.
2 Mandatory if the other user is being alerted. | | + +##### **7.2.5.2 Contents of TERMINAL DETAILS** + +This unconfirmed information flow informs users of any subaddress associated with the other user involved in the transfer. + +The contents of the TERMINAL DETAILS req.ind information flow are shown in Table 10. + +TABLE 10/Q.82.7 + +###### **TERMINAL DETAILS** + +| | | +|------------------------|---------| +| Name | req.ind | +| Transferred subaddress | M | + +#### **7.2.6 Relationship ru** + +##### **7.2.6.1 Contents of TERMINAL DETAILS** + +This unconfirmed information flow informs users of any subaddress associated with the other user involved in the transfer. + +The contents of the TERMINAL DETAILS req.ind information flow are shown in Table 11. + +TABLE 11/Q.82.7 + +###### **TERMINAL DETAILS** + +| | | +|------------------------|---------| +| Name | req.ind | +| Transferred subaddress | M | + +## **8      SDL diagrams for functional entities** + +The Specification and Description Language (SDL) diagrams are provided according to Recommendation Z.100 [5]. + +### 8.1 FE1 + +The SDL diagram for FE1 is shown in Figure 5. + +![SDL diagram for FE1 showing states Idle, Awaiting confirmation, and an unnamed state, with transitions for user requests and system responses.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +The diagram is an SDL (State Definition Language) diagram for FE1. It consists of the following elements: + +- States:** + - Idle**: Initial state, represented by a double circle. + - Awaiting confirmation**: State reached after a successful transfer, represented by a double circle. + - Unnamed state**: State reached after an invalid request, represented by a double circle with a dashed line inside. +- Transitions:** + - User request transfer B and C together**: A transition from the Idle state to the Request valid? decision. It is associated with FEA 911, user. + - Request valid?**: A decision diamond. It is associated with FEA 912. It has two outgoing transitions: + - Yes**: Leads to the TRANSFER INVOKE req.ind transition. + - No**: Leads to the Request invalid transition. + - TRANSFER INVOKE req.ind**: A transition from the Request valid? (Yes) decision to the Awaiting confirmation state. It is associated with FEA 914, to FE2. + - Request invalid**: A transition from the Request valid? (No) decision to the unnamed state. It is associated with FEA 913, user. +- Functional Areas (FEA):** + - FEA 911, user**: Associated with the initial request transition. + - FEA 912**: Associated with the Request valid? decision. + - FEA 913, user**: Associated with the Request invalid transition. + - FEA 914, to FE2**: Associated with the TRANSFER INVOKE req.ind transition. + +SDL diagram for FE1 showing states Idle, Awaiting confirmation, and an unnamed state, with transitions for user requests and system responses. + +T1175270-95 + +FIGURE 5/Q.82.7 (sheet 1 of 2) + +#### SDL diagrams for FE1 + +![State transition diagram for Process FE1_ECT. It starts at 'Awaiting confirmation', goes to 'TRANSFER INVOKE resp.conf' (linked to FEA 915 from FE2), then to a decision 'Transfer successful?'. 'Yes' leads to 'Transfer complete' (linked to FEA 917 user) and then to 'Idle'. 'No' leads to 'Transfer failed' (linked to FEA 918, user) and then to 'Idle'. FEA 916 is also associated with the decision.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` +stateDiagram-v2 + [*] --> Awaiting_confirmation : Awaiting confirmation + Awaiting_confirmation --> TRANSFER_INVOKE_resp_conf : TRANSFER INVOKE resp.conf + TRANSFER_INVOKE_resp_conf --> Transfer_successful? : Transfer successful? + Transfer_successful? -- Yes --> Transfer_complete : Transfer complete + Transfer_successful? -- No --> Transfer_failed : Transfer failed + Transfer_complete --> Idle1 : Idle + Transfer_failed --> Idle2 : Idle +``` + +The diagram illustrates the state transitions for Process FE1\_ECT. It begins in the 'Awaiting confirmation' state. A transition labeled 'TRANSFER INVOKE resp.conf' (associated with FEA 915 from FE2) leads to a decision state 'Transfer successful?'. This decision is influenced by FEA 916. If the transfer is successful ('Yes'), it proceeds to 'Transfer complete' (associated with FEA 917 user) and then to an 'Idle' state. If the transfer fails ('No'), it proceeds to 'Transfer failed' (associated with FEA 918, user) and then to another 'Idle' state. + +State transition diagram for Process FE1\_ECT. It starts at 'Awaiting confirmation', goes to 'TRANSFER INVOKE resp.conf' (linked to FEA 915 from FE2), then to a decision 'Transfer successful?'. 'Yes' leads to 'Transfer complete' (linked to FEA 917 user) and then to 'Idle'. 'No' leads to 'Transfer failed' (linked to FEA 918, user) and then to 'Idle'. FEA 916 is also associated with the decision. + +T1175280-95 + +FIGURE 5/Q.82.7 (sheet 2 of 2) +**SDL diagrams for FE1** + +### 8.2 FE2 + +The SDL diagram for FE2 is shown in Figure 6. + +![SDL diagram for FE2 process. It starts at an 'Idle' state, followed by a 'TRANSFER INVOKE req.ind' message. A decision diamond asks 'Is transfer barred by virtue of call states or supplementary service interactions?'. If 'Yes', it goes to 'TRANSFER INVOKE (barred) resp.conf' (FEA 924, to FE1). If 'No', it goes to 'TRANSFER INVOKE req.ind' (FEA 923, to FE3), then to 'Awaiting confirmation' state, then to 'TRANSFER INVOKE resp.conf' (FEA 925, from FE3), and finally to 'TRANSFER INVOKE resp.conf' (FEA 926, to FE1). Both final messages lead to end states.](5445597cceefaca1ac89e710fe339325_img.jpg) + +Process FE2\_ECT + +SE0368\_F6(1) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> T1: TRANSFER INVOKE req.ind + T1 --> Decision: Is transfer barred by virtue of call states or supplementary service interactions? + Decision -- Yes --> T2: TRANSFER INVOKE (barred) resp.conf + Decision -- No --> T3: TRANSFER INVOKE req.ind + T3 --> Awaiting: Awaiting confirmation + Awaiting --> T4: TRANSFER INVOKE resp.conf + T4 --> T5: TRANSFER INVOKE resp.conf + T2 --> [*] + T5 --> [*] +``` + +FEA 921, from FE1 + +FEA 922 + +FEA 923, to FE3 + +FEA 924, to FE1 + +FEA 925, from FE3 + +FEA 926, to FE1 + +T1175290-95 + +SDL diagram for FE2 process. It starts at an 'Idle' state, followed by a 'TRANSFER INVOKE req.ind' message. A decision diamond asks 'Is transfer barred by virtue of call states or supplementary service interactions?'. If 'Yes', it goes to 'TRANSFER INVOKE (barred) resp.conf' (FEA 924, to FE1). If 'No', it goes to 'TRANSFER INVOKE req.ind' (FEA 923, to FE3), then to 'Awaiting confirmation' state, then to 'TRANSFER INVOKE resp.conf' (FEA 925, from FE3), and finally to 'TRANSFER INVOKE resp.conf' (FEA 926, to FE1). Both final messages lead to end states. + +FIGURE 6/Q.82.7 +SDL diagrams for FE2 + +### 8.3 FE3 + +The SDL diagram for FE3 is shown in Figure 7. + +![SDL diagram for Process FE3_ECT. The diagram shows a state transition from 'Idle' through various transfer and loop prevention steps, leading to 'Wait transfer active' or other terminal states. It includes labels for FEA 931 through FEA 939 and a note about operational reasons or CUG restrictions.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +``` + +graph TD + Idle([Idle]) --> TI_req[TRANSFER INVOKE +req.ind] + TI_req --- FEA931[FEA 931, +from FE2] + TI_req --> Identify[Identify primary +and secondary +calls] + Identify --- FEA932[FEA 932] + Identify --> Unacceptable{Transfer request +unacceptable? +(Note)} + Unacceptable --- FEA933[FEA 933] + + Unacceptable -- Yes --> TI_reject[TRANSFER +INVOKE +(reject) +resp.conf] + TI_reject --- FEA935[FEA 935, +to FE2] + TI_reject --> Term1([ ]) + + Unacceptable -- No --> LoopPrev[Loop +prevention +procedure] + LoopPrev --> LoopTest[Loop +Test] + LoopTest -- Yes --> LoopPrev + + LoopPrev -- success --> TI_accept[TRANSFER +INVOKE +(accept) +resp.conf] + TI_accept --- FEA934[FEA 934, +to FE2] + + TI_accept --> Connect[Connect call paths +between user B and +user C together] + Connect --- FEA936[FEA 936] + + Connect --> Clear[Clear call paths +to user A] + Clear --- FEA937[FEA 937] + + Clear --> TC_req1[TRANSFER +COMPLETE +req.ind] + TC_req1 --- FEA938[FEA 938, +to B's FE4] + + TC_req1 --> TC_req2[TRANSFER +COMPLETE +req.ind] + TC_req2 --- FEA939[FEA 939, +to C's FE4] + + TC_req2 --> Alerted{Is user C +being alerted?} + + Alerted -- Yes --> WaitActive([Wait transfer +active]) + Alerted -- No --> Term2([ ]) + + LoopTest -- failure --> Term3([ ]) + + subgraph NoteBox [ ] + direction TB + Note[NOTE - For example, may be for operational reasons, +or because CUG restrictions have been infringed.] + end + +``` + +The diagram is an SDL for Process FE3\_ECT, labeled SE0368\_F7.1(2). It begins at the 'Idle' state. The first transition is 'TRANSFER INVOKE req.ind', which leads to a process block 'Identify primary and secondary calls'. A note indicates this may be for operational reasons or due to CUG restrictions. This process is associated with FEA 931 (from FE2), FEA 932, and FEA 933. A decision diamond 'Transfer request unacceptable? (Note)' follows. If 'Yes', it leads to 'TRANSFER INVOKE (reject) resp.conf', which is associated with FEA 935 (to FE2), and then to a terminal state. If 'No', it leads to a 'Loop prevention procedure' block. This block is associated with FEA 934 (to FE2), FEA 936, FEA 937, FEA 938 (to B's FE4), and FEA 939 (to C's FE4). A 'Loop Test' block is also shown. From the 'Loop prevention procedure', a 'success' path leads to 'TRANSFER INVOKE (accept) resp.conf', which then leads to 'Connect call paths between user B and user C together', then 'Clear call paths to user A', then 'TRANSFER COMPLETE req.ind', then another 'TRANSFER COMPLETE req.ind', and finally to a decision 'Is user C being alerted?'. If 'Yes', it leads to 'Wait transfer active' state. If 'No', it leads to a terminal state. A 'failure' path from the 'Loop prevention procedure' leads to a terminal state. + +SDL diagram for Process FE3\_ECT. The diagram shows a state transition from 'Idle' through various transfer and loop prevention steps, leading to 'Wait transfer active' or other terminal states. It includes labels for FEA 931 through FEA 939 and a note about operational reasons or CUG restrictions. + +FIGURE 7/Q.82.7 (sheet 1 of 4) +**SDL diagrams for FE3** + +![State transition diagram for Process FE3_ECT showing states 'Wait transfer active' and 'Idle', and transitions 'Transfer active indication' and 'TRANSFER ACTIVE req.ind' with associated message details.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +``` +stateDiagram-v2 + [*] --> Wait_transfer_active : Wait transfer active + state "Wait transfer active" as Wait_transfer_active + state "TRANSFER ACTIVE req.ind" as TRANSFER_ACTIVE_req_ind + state "Idle" as Idle + Wait_transfer_active --> Transfer_active_indication : Transfer active indication + state "Transfer active indication" as Transfer_active_indication + Transfer_active_indication --> TRANSFER_ACTIVE_req_ind + TRANSFER_ACTIVE_req_ind --> Idle +``` + +The diagram illustrates the state transitions for Process FE3\_ECT. It begins with an initial state leading to 'Wait transfer active'. A transition labeled 'Transfer active indication' occurs, with a message 'FEA 93A from co-located CC' being received. This is followed by a transition labeled 'TRANSFER ACTIVE req.ind', with a message 'FEA 93A, to B's FE4' being sent. The process then transitions to the 'Idle' state. + +State transition diagram for Process FE3\_ECT showing states 'Wait transfer active' and 'Idle', and transitions 'Transfer active indication' and 'TRANSFER ACTIVE req.ind' with associated message details. + +T1175310-95 + +FIGURE 7/Q.82.7 (sheet 2 of 4) +**SDL diagrams for FE3** + +![State transition diagram for Macro Loop_Test](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +The diagram illustrates a state transition process for 'Macro Loop\_Test'. It begins with an initial state 'Loop Test' (oval). A transition arrow points to a state 'LOOP TEST req.ind' (chevron). From this state, a dashed line branches to the right, leading to a dashed box containing the text 'FEA 93B, to B's FE4'. Another transition arrow points down from 'LOOP TEST req.ind' to a second 'LOOP TEST req.ind' state (chevron). From this second state, another dashed line branches to the right, leading to a dashed box containing the text 'FEA 93B, to C's FE4'. A transition arrow points down from the second 'LOOP TEST req.ind' state to a rectangular state 'SET NOW + Loop, TLoop'. Finally, a transition arrow points down to the terminal state 'Test in progress' (oval). + +``` +graph TD; A([Loop Test]) --> B{{LOOP TEST req.ind}}; B -.-> B1[FEA 93B, to B's FE4]; B --> C{{LOOP TEST req.ind}}; C -.-> C1[FEA 93B, to C's FE4]; C --> D[SET NOW + Loop, TLoop]; D --> E([Test in progress]) +``` + +State transition diagram for Macro Loop\_Test + +T1175320-95 + +FIGURE 7/Q.82.7 (sheet 3 of 4) +**SDL diagrams for FE3** + +![State transition diagram for Macro Loop_Test (SE0368_F7.4(2)).](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +The diagram is a State Transition Diagram (STD) for a state machine named "Macro Loop\_Test" (SE0368\_F7.4(2)). It begins with an initial state "Test in progress" (oval). The main state is a composite state "Loop Test" (rectangle), which contains two sub-states: "FEA 93C, from B's or C's FE4" (dashed box) and "FEA 93C" (dashed box). Transitions include "LOOP TEST req.ind" (input), "TRANSFER INVOKE (reject) resp.conf" (input), "LOOP TEST REJECT req.ind" (input), "FEA 935 to FE2" (input), "TLoop" (output), "RESET (TLoop)" (output), and "Reason?" (output). The "Reason?" output leads to a decision diamond with options "simultaneous transfer" (leading to "TRANSFER INVOKE (reject) resp.conf"), "insufficient information" (leading to "Implementation option?" which then leads to "reject transfer" or "proceed with transfer"), and "FEA 935, to FE2" (leading to "Failure"). The diagram ends with four terminal states: "Failure" (circle), "Failure" (circle), "Success" (circle), and "Success" (circle). + +``` + +stateDiagram-v2 + [*] --> TestInProgress : Test in progress + TestInProgress --> LoopTest + state "Loop Test" as LoopTest { + state "FEA 93C, from B's or C's FE4" as FEA93C1 { + [*] --> FEA93C1 + } + state "FEA 93C" as FEA93C2 { + [*] --> FEA93C2 + } + } + LoopTest --> FEA93C1 : LOOP TEST req.ind + FEA93C1 --> FEA93C2 : FEA 93C + FEA93C2 --> FEA93C1 : FEA 93C + FEA93C1 --> LoopTest : LOOP TEST REJECT req.ind + FEA93C2 --> LoopTest : FEA 93C + FEA93C1 --> FEA935 : FEA 935 to FE2 + FEA935 --> Failure1 : Failure + FEA93C1 --> TransferInvoke : TRANSFER INVOKE (reject) resp.conf + TransferInvoke --> Failure2 : Failure + FEA93C1 --> Reset1 : RESET (TLoop) + Reset1 --> Success1 : Success + FEA93C2 --> TLoop : TLoop + TLoop --> Reset2 : RESET (TLoop) + Reset2 --> Success2 : Success + FEA93C1 --> Reason : Reason? + Reason --> SimultaneousTransfer : simultaneous transfer + SimultaneousTransfer --> TransferInvoke + Reason --> InsufficientInformation : insufficient information + InsufficientInformation --> ImplementationOption : Implementation option? + ImplementationOption --> RejectTransfer : reject transfer + RejectTransfer --> Failure3 : Failure + ImplementationOption --> ProceedWithTransfer : proceed with transfer + ProceedWithTransfer --> Success3 : Success + FEA93C2 --> FEA935 : FEA 935, to FE2 + FEA935 --> Failure4 : Failure + +``` + +State transition diagram for Macro Loop\_Test (SE0368\_F7.4(2)). + +T1175330-95 + +FIGURE 7/Q.82.7 (sheet 4 of 4) +**SDL diagrams for FE3** + +### 8.4 FE4 + +The SDL diagram for FE4 is shown in Figure 8. + +![SDL diagram for FE4 showing state transitions from Idle to various terminal states based on specific events and conditions.](552265bdbcf6d43d341fd018a9076269_img.jpg) + +Process FE4\_ECT SE0368\_F8.1(3) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> T1: TRANSFER COMPLETE req.ind + Idle --> T2: FEA 941, from FE3 + Idle --> T3: FEA 945 from local FE5 + Idle --> T4: TERMINAL DETAILS req.ind + T1 --> T1_1: TRANSFER COMPLETE req.ind + T1_1 --> T1_2: FEA 942, to local FE5 + T1_2 --> T1_3: Cancel any active user-to-user signalling supplementary service + T1_3 --> T1_4: FEA 943 + T1_4 --> T1_5: Store call details + T1_5 --> T1_6: FEA 944 + T1_6 --> D1: Other party being alerted? + D1 -- Yes --> S1: Wait transfer active + D1 -- No --> S2: ----- + T3 --> D2: Transmission of terminals details permitted? + D2 -- No --> S3: ----- + D2 -- Yes --> T4_1: TERMINAL DETAILS req.ind + T4_1 --> T4_2: FEA 947, to remote FE6 + T4_2 --> S4: ----- + +``` + +The diagram illustrates the state transitions for Process FE4\_ECT. It begins at the 'Idle' state. From 'Idle', four main transitions are possible: + + +- TRANSFER COMPLETE req.ind**: This transition leads to a sequence of actions: 'TRANSFER COMPLETE req.ind', 'FEA 942, to local FE5', 'Cancel any active user-to-user signalling supplementary service', 'FEA 943', 'Store call details', and 'FEA 944'. This is followed by a decision 'Other party being alerted?'. If 'Yes', the state becomes 'Wait transfer active'. If 'No', the state becomes a terminal state '-----'. +- FEA 941, from FE3**: This transition leads directly to a terminal state '-----'. +- FEA 945 from local FE5**: This transition leads directly to a terminal state '-----'. +- TERMINAL DETAILS req.ind**: This transition leads to a decision 'Transmission of terminals details permitted?'. If 'No', the state becomes a terminal state '-----'. If 'Yes', it leads to 'TERMINAL DETAILS req.ind', then 'FEA 947, to remote FE6', and finally to a terminal state '-----'. + +SDL diagram for FE4 showing state transitions from Idle to various terminal states based on specific events and conditions. + +T1175340-95 + +FIGURE 8/Q.82.7 (sheet 1 of 3) + +#### SDL diagrams for FE4 + +![SDL diagram for Process FE4_ECT. The process starts at 'Wait transfer active'. It branches into two paths. The left path involves 'TRANSFER ACTIVE req.ind' (FEA 948 from FE3), 'Store call details' (FEA 949), and 'TRANSFER ACTIVE req.ind' (FEA 94A, to local FE5), leading to 'Idle'. The right path involves 'TERMINAL DETAILS req.ind' (FEA 945, from local FE5), a decision 'Transmission of terminal details permitted?' (FEA 946), 'TERMINAL DETAILS req.ind' (FEA 947, to remote FE6), and an unlabeled terminal state.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) + +``` +stateDiagram-v2 + [*] --> Wait_transfer_active + state "Wait transfer active" as Wait_transfer_active + state "TRANSFER ACTIVE req.ind" as TRANSFER_ACTIVE_req_ind_L + state "Store call details" as Store_call_details + state "TRANSFER ACTIVE req.ind" as TRANSFER_ACTIVE_req_ind_R + state "Idle" as Idle + state "TERMINAL DETAILS req.ind" as TERMINAL_DETAILS_req_ind + state "Transmission of terminal details permitted?" as Transmission_permitted + state "TERMINAL DETAILS req.ind" as TERMINAL_DETAILS_req_ind_2 + state "-----" as Terminal_1 + state "-----" as Terminal_2 + + Wait_transfer_active --> TRANSFER_ACTIVE_req_ind_L + Wait_transfer_active --> TERMINAL_DETAILS_req_ind + + TRANSFER_ACTIVE_req_ind_L --> Store_call_details + Store_call_details --> TRANSFER_ACTIVE_req_ind_R + TRANSFER_ACTIVE_req_ind_R --> Idle + + TERMINAL_DETAILS_req_ind --> Transmission_permitted + Transmission_permitted -- No --> Terminal_2 + Transmission_permitted -- Yes --> TERMINAL_DETAILS_req_ind_2 + TERMINAL_DETAILS_req_ind_2 --> Terminal_1 +``` + +SDL diagram for Process FE4\_ECT. The process starts at 'Wait transfer active'. It branches into two paths. The left path involves 'TRANSFER ACTIVE req.ind' (FEA 948 from FE3), 'Store call details' (FEA 949), and 'TRANSFER ACTIVE req.ind' (FEA 94A, to local FE5), leading to 'Idle'. The right path involves 'TERMINAL DETAILS req.ind' (FEA 945, from local FE5), a decision 'Transmission of terminal details permitted?' (FEA 946), 'TERMINAL DETAILS req.ind' (FEA 947, to remote FE6), and an unlabeled terminal state. + +T1175350-95 + +FIGURE 8/Q.82.7 (sheet 2 of 3) +SDL diagrams for FE4 + +![SDL diagram for Process FE4_ECT showing states and transitions for loop testing.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) + +The diagram illustrates the state transitions for Process FE4\_ECT. It begins with an initial state labeled 'Idle' (represented by a double oval). From 'Idle', three transitions are possible: 'LOOP TEST req.ind' (left), 'LOOP TEST resp.conf' (center), and 'LOOP TEST reject req.ind' (right). Each transition is associated with specific data flows indicated by dashed boxes: 'FEA 94B, from FE3' and 'FEA 94C, from FE5' for the left path; 'FEA 94D, from FE5' for the center path; and 'FEA 94D, from FE3' for the right path. Each transition leads to a 'Loop prevention procedure' (represented by a triangle). From each procedure, a 'Yes' or 'No' decision is made. The 'Yes' path leads to a state transition ('LOOP TEST req.ind' or 'LOOP TEST reject req.ind') which then leads to a final state (double oval with dashes). The 'No' path leads to another state transition ('FEA 94B, to FE5', 'FEA 94C, to FE3', or 'FEA 94D, to FE3') which then leads to a 'LOOP TEST resp.conf' state transition, which finally leads to a final state. The 'Yes' and 'No' labels are placed near the decision points. + +SDL diagram for Process FE4\_ECT showing states and transitions for loop testing. + +T1175360-95 + +FIGURE 8/Q.82.7 (sheet 3 of 3) +**SDL diagrams for FE4** + +### 8.5 FE5 + +The SDL diagram for FE5 is shown in Figure 9. + +![SDL diagram for FE5 showing state transitions from Idle to various service handling paths based on input signals like TRANSFER COMPLETE, TRANSFER INFORM, and TERMINAL DETAILS.](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +Process FE5\_ECT SE0368\_F9.1(3) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> TRANSFER_COMPLETE_req.ind + Idle --> TERMINAL_DETAILS_req.ind + TRANSFER_COMPLETE_req.ind --> FEA_951_from_FE4 + TRANSFER_COMPLETE_req.ind --> TRANSFER_INFORM_req.ind + TRANSFER_INFORM_req.ind --> FEA_952_to_local_FE6 + TRANSFER_INFORM_req.ind --> FEA_956 + TRANSFER_INFORM_req.ind --> Cancel_active_user_to_user_signalling_supplementary_service + Cancel_active_user_to_user_signalling_supplementary_service --> Outstanding_notifications + Outstanding_notifications --> FEA_953_to_local_FE6 + Outstanding_notifications --> FEA_957_to_local_FE4 + Outstanding_notifications --> Store_call_details + Store_call_details --> Other_user_being_alerted + Other_user_being_alerted -- Yes --> Wait_transfer_active + Other_user_being_alerted -- No --> End1 + TERMINAL_DETAILS_req.ind --> FEA_955_from_local_FE6 + TERMINAL_DETAILS_req.ind --> Transmission_permitted + Transmission_permitted -- Yes --> TERMINAL_DETAILS_req.ind + Transmission_permitted -- No --> End2 + +``` + +The diagram illustrates the state transitions for Process FE5\_ECT. It begins at the 'Idle' state. From 'Idle', two primary transitions are available: 'TRANSFER COMPLETE req.ind' and 'TERMINAL DETAILS req.ind'. The 'TRANSFER COMPLETE' path leads to a sequence of operations: 'FEA 951, from FE4', 'TRANSFER INFORM req.ind', 'FEA 952, to local FE6', 'FEA 956', 'Cancel any active user-to-user signalling supplementary service', 'Outstanding notifications', 'FEA 953, to local FE6', 'FEA 957, to local FE4', and 'Store call details'. This is followed by a decision 'Other user being alerted?'. If 'Yes', it goes to 'Wait transfer active'; if 'No', it ends. The 'TERMINAL DETAILS' path from 'Idle' leads to 'FEA 955, from local FE6' and a decision 'Transmission of terminal details permitted?'. If 'Yes', it loops back to 'TERMINAL DETAILS req.ind'; if 'No', it ends. There are also dashed boxes for FEA 95E and FEA 954 connected to the 'Store call details' state. + +SDL diagram for FE5 showing state transitions from Idle to various service handling paths based on input signals like TRANSFER COMPLETE, TRANSFER INFORM, and TERMINAL DETAILS. + +T1175370-95 + +FIGURE 9/Q.82.7 (sheet 1 of 3) + +#### SDL diagrams for FE5 + +![SDL diagram for Process FE5_ECT showing states and transitions between FEA 958, 959, 95A, 955, 956, and 957.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) + +The diagram is an SDL (State Transition Diagram) for Process FE5\_ECT. It starts with an initial state 'Wait transfer active' (oval). From this state, two transitions are possible: 'TRANSFER ACTIVE req.ind' (trapezoid) and 'TERMINAL DETAILS req.ind' (trapezoid). The 'TRANSFER ACTIVE' path leads to state 'FEA 958, from FE4' (dashed box), then to action 'Store call details' (rectangle), then to state 'FEA 959' (dashed box), then to action 'TRANSFER INFORM req.ind' (trapezoid), then to state 'FEA 95A, to local FE6' (dashed box), and finally to the 'Idle' state (oval). The 'TERMINAL DETAILS' path leads to state 'FEA 955, from local FE6' (dashed box), then to a decision diamond 'Transmission of terminal details permitted?'. If 'Yes', it leads to action 'TERMINAL DETAILS req.ind' (trapezoid), then to state 'FEA 956' (dashed box), then to state 'FEA 957 to local FE4' (dashed box), and finally to a terminal state (oval with dashes). If 'No', it leads directly to another terminal state (oval with dashes). + +``` +stateDiagram-v2 + [*] --> Wait_transfer_active + state "Wait transfer active" as Wait_transfer_active + state "FEA 958, from FE4" as FEA_958 + state "FEA 959" as FEA_959 + state "FEA 95A, to local FE6" as FEA_95A + state "FEA 955, from local FE6" as FEA_955 + state "FEA 956" as FEA_956 + state "FEA 957 to local FE4" as FEA_957 + state "Idle" as Idle + state "-----" as T1 + state "-----" as T2 + + Wait_transfer_active --> FEA_958 : TRANSFER ACTIVE req.ind + Wait_transfer_active --> FEA_955 : TERMINAL DETAILS req.ind + FEA_958 --> FEA_959 : Store call details + FEA_959 --> FEA_95A : TRANSFER INFORM req.ind + FEA_95A --> Idle + FEA_955 --> Decision{Transmission of terminal details permitted?} + Decision -- Yes --> FEA_956 : TERMINAL DETAILS req.ind + FEA_956 --> FEA_957 + FEA_957 --> T1 + Decision -- No --> T2 +``` + +SDL diagram for Process FE5\_ECT showing states and transitions between FEA 958, 959, 95A, 955, 956, and 957. + +T1175380-95 + +FIGURE 9/Q.82.7 (sheet 2 of 3) +SDL diagrams for FE5 + +![State transition diagram for Process FE5_ECT. It starts at 'Idle', receives 'LOOP TEST req.ind' (from FEA 95B, FE4), checks 'Loop prevention procedure?'. If 'Yes', it checks 'Collected FE3 in state "Test in progress"?'. If 'No', it sends 'LOOP TEST REJECT resp.conf' (to FEA 95C, FE4) and ends. If 'Yes', it sends 'LOOP TEST REJECT req.ind' (to FEA 95D, FE4) and ends. If 'No' to the loop prevention check, it ends.](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +``` +graph TD; Idle([Idle]) --> L1{LOOP TEST req.ind}; FEA95B[FEA 95B, from FE4] -.-> L1; L1 --> LPP{Loop prevention procedure?}; LPP -- Yes --> C{Collected FE3 in state "Test in progress"?}; LPP -- No --> End1([-----]); C -- No --> L2{LOOP TEST REJECT resp.conf}; FEA95C[FEA 95C, to FE4] -.-> L2; L2 --> End2([-----]); C -- Yes --> L3{LOOP TEST REJECT req.ind}; FEA95D[FEA 95D, to FE4] -.-> L3; L3 --> End3([-----]); +``` + +State transition diagram for Process FE5\_ECT. It starts at 'Idle', receives 'LOOP TEST req.ind' (from FEA 95B, FE4), checks 'Loop prevention procedure?'. If 'Yes', it checks 'Collected FE3 in state "Test in progress"?'. If 'No', it sends 'LOOP TEST REJECT resp.conf' (to FEA 95C, FE4) and ends. If 'Yes', it sends 'LOOP TEST REJECT req.ind' (to FEA 95D, FE4) and ends. If 'No' to the loop prevention check, it ends. + +T1175390-95 + +FIGURE 9/Q.82.7 (sheet 3 of 3) +**SDL diagrams for FE5** + +### 8.6 FE6 + +The SDL diagram for FE6 is shown in Figure 10. + +![SDL diagram for FE6 showing state transitions between Idle, TRANSFER INFORM, User indication, Any terminal specific details to send?, TERMINAL DETAILS, and terminal states.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +Process FE6\_ECT SE0368\_F10(1) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> TRANSFER_INFORM: FEA 961, from FE5 + Idle --> TERMINAL_DETAILS: FEA 965, from remote FE4 + TRANSFER_INFORM --> User_indication_1: FEA 962, user + User_indication_1 --> Any_terminal_specific_details: FEA 963 + Any_terminal_specific_details -- Yes --> TERMINAL_DETAILS_1: FEA 964, to FE5 + Any_terminal_specific_details -- No --> State_2 + TERMINAL_DETAILS --> User_indication_2: FEA 966, user + User_indication_2 --> State_3 +``` + +The diagram illustrates the state transitions for Process FE6\_ECT. It begins at the 'Idle' state. Two possible transitions are available: 'TRANSFER INFORM req.ind' triggered by FEA 961 from FE5, and 'TERMINAL DETAILS req.ind' triggered by FEA 965 from remote FE4. The 'TRANSFER INFORM' path leads to 'User indication "transferred" call state and identity' (FEA 962, user), which then leads to a decision 'Any terminal specific details to send?' (FEA 963). If 'Yes', it leads to 'TERMINAL DETAILS req.ind' (FEA 964, to FE5) and then to a terminal state. If 'No', it leads directly to another terminal state. The 'TERMINAL DETAILS' path leads to 'User indication further details of other user' (FEA 966, user), which then leads to a third terminal state. + +SDL diagram for FE6 showing state transitions between Idle, TRANSFER INFORM, User indication, Any terminal specific details to send?, TERMINAL DETAILS, and terminal states. + +T1175400-95 + +FIGURE 10/Q.82.7 +SDL diagrams for FE6 + +## **9 Functional Entity Actions (FEAs)** + +### **9.1 FEAs of FE1** + +- 911: FE1 receives the request for transfer. +- 912: FE1 optionally performs local checks with respect to the compatibility of the two calls against information held with the CCAs. +- 913: If the request is found locally to be invalid, the requesting user is informed that the transfer has failed. +- 914: If the request is found locally to be valid, FE2 is requested to execute the transfer. +- 915: FE1 receives the result of the transfer from FE2. +- 916: FE1 examines the result of the transfer. +- 917: If the transfer is successful, the requesting user is informed of the successful completion. Optionally the calls involved may be released (if they have not already been cleared by FE2). +- 918: If the transfer is unsuccessful, the requesting user is informed. + +### **9.2 FEAs of FE2** + +- 921: FE2 receives the request for invocation of transfer from FE1. +- 922: FE2 determines whether the transfer is valid in terms of the two calls to be transferred. Such checks are network specific; when FE2 resides in the public network it shall check that one call is answered and held and that the other call is not held and is answered or alerting (see Table 1), that the requesting user is not a conference controller, that the three-party supplementary service has not been invoked by the requesting user, and that closed user group restrictions would not be violated if the transfer were allowed to proceed. Checks performed when FE2 is in another network are outside the scope of this Recommendation. +- 923: If the transfer is permitted, a request for transfer is sent to FE3. +- 924: If the transfer is barred, a response indicating rejection is returned to FE1. +- 925: The result of the transfer is received from FE3. +- 926: The result of the transfer is relayed to FE1. + +### **9.3 FEAs of FE3** + +- 931: FE3 receives the request for invocation of transfer from FE2. +- 932: FE3 identifies the primary and secondary calls. +- 933: FE3 shall verify whether the requested transfer is allowed or, for example, should be rejected for operational reasons, or would violate closed user group restrictions if allowed to proceed. +- 934: If the transfer is permitted, a response indicating success is returned to FE2. +- 935: If the transfer is barred, a response indicating rejection is returned to FE2. +- 936: The call paths from user A's exchange toward user B and user C are joined together. +- 937: The call paths from user A's exchange toward user A are cleared. +- 938: Completion of the transfer is indicated to user B's exchange. This includes the identity of user C where known and an indication of whether user C is being alerted. +- 939: Completion of the transfer is indicated to user C's exchange. This includes the identity of user B where known. +- 93A: Following an alerting transfer, answer by user C is indicated to user B's FE4 on receipt of the basic call setup confirmation by the Call Control (CC) collocated with FE3. + +93B: As a network option, a LOOP TEST req.ind is sent to both FE4s to determine if a loop exists. + +93C: As a network option, the results of the loop test are processed. + +### **9.4 FEAs of FE4** + +941: FE4 receives the indication of transfer completion from FE3. + +942: The indication of transfer completion is passed to the local FE5. + +943: If FE4 is not allocated to a gateway, any active user-to-user supplementary service is cancelled. + +944: Details received in the transfer complete indication relevant to the network are stored. + +945: FE4 receives terminal specific details intended for the remote user from the local FE5. + +946: FE4 determines whether or not such information transfer is allowed. The mechanism for deciding upon this (for example a timer or counter) is implementation dependent. + +947: If the information can be transferred, it is sent to the remote FE6. + +948: FE4 receives the indication that answer has taken place subsequent to an alerting transfer. + +949: Details received in the transfer active indication relevant to the network are stored. + +94A: The indication that answer has taken place is passed to the local FE5. + +94B: As a network option, a LOOP TEST req.ind received from FE3 is relayed to FE5. + +94C: As a network option, a LOOP TEST resp.conf received from FE5 is relayed to FE3. + +94D: As a network option, a LOOP TEST REJECT req.ind received from FE5 is relayed to FE3. + +### **9.5 FEAs of FE5** + +951: FE5 receives the indication of transfer completion from FE4. + +952: The indication of transfer completion is passed to the local FE6. + +953: Any outstanding notifications (for example that the local user is holding) are sent to the remote user. + +954: Details received in the transfer complete indication relevant to the network are stored. + +955: FE5 receives terminal specific details intended for the remote user from the local FE6. + +956: FE5 determines whether or not such information transfer is allowed. The mechanism for deciding upon this (for example a timer or counter) is implementation dependent. + +957: If the information can be transferred, it is relayed to the local FE4. + +958: FE5 receives the indication that answer has taken place subsequent to an alerting transfer. + +959: Details received in the transfer active indication relevant to the network are stored. + +95A: The indication that answer has taken place is passed to the local FE6. + +95B: As a network option, a LOOP TEST req.ind received from FE4 is processed. + +95C: As a network option, if there is no colocated FE3 in state "TEST IN PROGRESS" for the same call, a LOOP TEST resp.conf is sent to FE4. + +95D: As a network option, if there is no colocated FE3 in state "TEST IN PROGRESS" for the same call, a LOOP TEST REJECT req.ind is sent to FE4. + +95E: Any active user-to-user signalling supplementary service is cancelled. + +### 9.6 FEAs of FE6 + +- 961: FE6 receives the indication that a transfer or answer following an alerting transfer has taken place. +- 962: The local user is informed of the transfer or the answer and the other details associated with it, such as other party number (if received). +- 963: FE6 determines whether there is any subaddress to be sent to the other user. +- 964: If there is a subaddress to be sent, this is indicated to the local FE5. +- 965: FE6 receives the subaddress associated with the remote terminal. +- 966: The local user is informed of the other terminal's subaddress. + +## 10 Allocation of functional entities to physical locations + +The possible physical locations of functional entities are shown in Table 12. + +TABLE 12/Q.82.7 + +### Allocation of functional entities + +| | FE1 | FE2 | FE3 | FE4 | FE5 | FE6 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------|--------|------------------|----------------------|------------------| +| Scenario 1 (Note 1) | A's TE | A's LE | A's LE | B's LE
C's LE | B's LE
C's LE | B's TE
C's TE | +| Scenario 2 (Note 1) | A's TE | A's LE | A's LE | B's LE
C's LE | B's PTNX
C's LE | B's TE
C's TE | +| Scenario 3 (Note 1) | A's TE | A's LE | A's LE | B's LE
C's LE | B's LE
C's PTNX | B's TE
C's TE | +| Scenario 4 (Note 1) | A's TE | A's LE | A's LE | B's LE
C's LE | B's PTNX
C's PTNX | B's TE
C's TE | +| Scenario 5 | A's TE | A's PTNX | PTNX | B's LE
C's LE | B's LE
C's LE | B's TE
C's TE | +| Scenario 6 | A's TE | A's PTNX | PTNX | B's LE
C's LE | B's PTNX
C's LE | B's TE
C's TE | +| Scenario 7 | A's TE | A's PTNX | PTNX | B's LE
C's LE | B's LE
C's PTNX | B's TE
C's TE | +| Scenario 8 | A's TE | A's PTNX | PTNX | B's LE
C's LE | B's PTNX
C's PTNX | B's TE
C's TE | +| Scenario 9 (Note 2) | A's TE | A's PTNX | A's LE | B's LE
C's LE | B's LE
C's LE | B's TE
C's TE | +| Scenario 10 (Note 2) | A's TE | A's PTNX | A's LE | B's LE
C's LE | B's PTNX
C's LE | B's TE
C's TE | +| Scenario 11 (Note 2) | A's TE | A's PTNX | A's LE | B's LE
C's LE | B's LE
C's PTNX | B's TE
C's TE | +| Scenario 12 (Note 2) | A's TE | A's PTNX | A's LE | B's LE
C's LE | B's PTNX
C's PTNX | B's TE
C's TE | +| NOTES
1 FE4 can also be allocated in the gateway of user A's network.
2 FE2 and FE3 shall exist in adjacent basic call CC's in this scenario. The primary and secondary calls may exist in separate access links between the same PBX and same LE. | | | | | | | + +Scenario 1 represents transfer by join either entirely within one public network, or between different public networks. + +Scenarios 2, 3 and 4 represent transfer by join where user B, user C, and both user B and user C are in a private network respectively. + +Scenarios 5, 6, 7 and 8 represent transfer (by join or re-routing) where the transfer is invoked from and controlled within a private network for the cases where both user B and user C, only user C, only user B, and neither user B nor user C, are in the public network respectively. In these scenarios, the PTNX where the functionality of FE3 is realized may or may not be user A's PTNX and in the case of transfer by re-routing the functionality may be split across a number of PTNXs. + +# ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Telephone network and ISDN +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media +- Series H Transmission of non-telephone signals +- Series I Integrated services digital network +- Series J Transmission of sound-programme and television signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits +- Series N Maintenance: international sound-programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality +- Series Q Switching and signalling** +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminal equipment and protocols for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communication +- Series Z Programming languages \ No newline at end of file diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7e12a2a85ad4fe7a1acaa81a4209a2d23e5ba6b --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa441490d26df5c065741584bdb14c88537f79f48a9607317da7334e379df8dc +size 51749 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5023cb5190259d0e36c78a3995c78525bfbbddb4 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d126c71de386c9b812ed28c5d5401ae7c23da9fb92fb2de8b5317fdc402aaa9e +size 119059 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c1dfa8ee22ad063471e82648f8515dd37ce784d --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1699fae88e3fee843d3e7c6630ffd354a895d007811a17ddd3575320a6443bfe +size 8191 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e86d31240f943599983c5177b2da4b184b859ae --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fefe271cb3034f9f56579247ed414ce92046c77486a0076ac8e317f1819e12c +size 46137 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0808f1d29a42984ae0391d83d7e79be91f109601 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ed7d650df82e6628fbc775e43dfd942d7a3ed811a0c81183e74da905c4102f4 +size 73173 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b59081fd931ba1787bb73bdf234d68684c1c2af --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28dc6dc431d183d3e502713d12014496cd1aae4fe4984269ded0d554529aeb5c +size 18442 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/384ca4ed072674dbb16642cd334b1c15_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/384ca4ed072674dbb16642cd334b1c15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df0c965d4c599a8dd1c4304c167b562642c08f66 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/384ca4ed072674dbb16642cd334b1c15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad9b7a59fd3e109632b0e9b7809895db85cbd0801c20e24c144f41236d03e02b +size 79212 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab6a82a311a1834b7ac8d0fe5509ed758dd2bb51 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddbfca55988cbb10fdcbc95eefcf5a28a16406a956cb5d53203c28f72bc3fe9d +size 91702 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12b0a558adf2dc76a2e5195e652280402c2f9f32 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f92a5ec57e5d552cdf12f2f70b773d138c8e04938064d27ead7054537f5b97dd +size 63555 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec6efda972d1365657c4415a56c0c155c9e4200 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8940c79f13123b6d8fed8f113e511f647111f30f1d5f65e3de5f054dd0e94a2 +size 73161 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af4b9449c58393ba3cc80f77bf5ee90f7aec1519 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c39a26d52606b6cf81c3b3fac79f6c44bdef2b45e04de147b0be6ed7dc417fb +size 54622 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b1457c6cc9c66e21017f1696067abeb1564725d --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b23bdd3fdabc25396178eddceab8a4681f3be04427b4213e660900beb341fb28 +size 88094 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..489e5066b55f7297cd951366554434421aa5d42f --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c825c7454df35a2c0536de4a619a672928eff13e726bd546f4114c8dd99f4f80 +size 96199 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ee657e2ae5bcc6a17d34c09cbec83e0f7b31887 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df79393d486f79e36d9e19d22dbce2d2f07caf523cf9247d6f5388b06ab0eb5a +size 41343 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a60ef3dfb7637503b5b3b8e7bc69cfb4ee012883 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd95adfd324da1a1f0200039a20d6af73ff763c9267d2b2e08f63266766ab27f +size 85985 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd49aee93913465f02bf32c6a9d03a5d798de1a9 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a742162fbdde7cb003e2167e2a0b35011f35196bd634a451e97effc2d51aeb0 +size 62172 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..865b546fae6a904e2c9f965de24db5427f1fcc85 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b81df0c5cb7b61f53d614f6fdc4440560018621192e73b48e1b64ba16f39a84 +size 45379 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ea15d2a9ee910a6a1824a849ad8d024ed6c7bba --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8f39f70a70862a6b502813832705e132d3f9ccd0bef87cbd53e7eaafa04ebe6 +size 160745 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e17ace188c96747cb20620dfe22b2f9722f112b1 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3489d48c3651595851c17836d0ca9272e833d40468eca78b23ca810fdea0e638 +size 83451 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..744c39816179c0b121650729ed8a5971d9bdb0b7 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5481490c4d44a44a266bd23c2ce3bf484259d549d95da282fd843c44fd9985a3 +size 64421 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3940a2cd993ca5e82c1d08e09ee2be2272d3e2ce --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3ca23a6b379cf0fa44934dbc2115d2bddec9e5a46bf86c044ed06d5c00b3091 +size 51102 diff --git a/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..991affd701851750aa3e823b066084c58c9c5781 --- /dev/null +++ b/marked/Q/T-REC-Q.824.5-199710-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26cfbbd695a3f5eefa8ecc34f021b00e5ac8ec06bbe2e512840048adf2932155 +size 24585 diff --git a/marked/Q/T-REC-Q.824.7-200002-I_PDF-E/raw.md b/marked/Q/T-REC-Q.824.7-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ad11e58d860de57cb9abb8a91b8a75b4ec1365d8 --- /dev/null +++ b/marked/Q/T-REC-Q.824.7-200002-I_PDF-E/raw.md @@ -0,0 +1,1349 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.824.7** + +(02/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Q3 interface + +--- + +**Stage 2 and stage 3 description for the Q3 +interface – Customer administration: Enhanced +broadband switch management** + +ITU-T Recommendation Q.824.7 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701-Q.709 | +| Signalling connection control part (SCCP) | Q.711-Q.719 | +| Telephone user part (TUP) | Q.720-Q.729 | +| ISDN supplementary services | Q.730-Q.739 | +| Data user part | Q.740-Q.749 | +| Signalling System No. 7 management | Q.750-Q.759 | +| ISDN user part | Q.760-Q.769 | +| Transaction capabilities application part | Q.770-Q.779 | +| Test specification | Q.780-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Stage 2 and stage 3 description for the Q3 interface – Customer administration: Enhanced broadband switch management** + +## **Summary** + +This Recommendation specifies the Q3 interface between an ATM switch with enhanced functionality and the Telecommunications Management Network (TMN). The interface specified is that between TMN Network Elements or Q-Adapters which interface to TMN Operations Systems (OSs) without mediation and between OSs and Mediation Devices, as defined in ITU-T Recommendation M.3010. + +The scope of this Recommendation includes the management of switched VPs as defined in ITU-T Recommendations Q.2766.1 and Q.2934 and of soft PVCs as defined in ITU-T Recommendation Q.2767.1. + +## **Source** + +ITU-T Recommendation Q.824.7 was prepared by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------------------------------|----| +| 1 | Purpose and Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Definitions, abbreviations and conventions ..... | 2 | +| 3.1 | Definitions ..... | 2 | +| 3.2 | Abbreviations ..... | 3 | +| 3.3 | Conventions ..... | 4 | +| 4 | General overview ..... | 4 | +| 4.1 | Entity relationship models ..... | 5 | +| 4.1.1 | Entity relationship diagram for the switched virtual paths ..... | 5 | +| 4.1.2 | Entity relationship diagram for the soft PVCs ..... | 6 | +| 4.2 | Inheritance hierarchy ..... | 7 | +| 5 | Formal definitions ..... | 7 | +| 5.1 | Object classes ..... | 7 | +| 5.1.1 | Profiling notes for imported classes ..... | 8 | +| 5.1.2 | Definition of classes ..... | 8 | +| 5.2 | Name bindings ..... | 11 | +| 5.2.1 | softPvc-managedElementR1 ..... | 11 | +| 5.2.2 | vpPool-tcAdaptorTTPBidirectional ..... | 11 | +| 5.3 | Definition of packages ..... | 12 | +| 5.3.1 | atmTrafficDescriptorPtrPkg (ATM traffic descriptor pointer package) ..... | 12 | +| 5.3.2 | calledPartyVciPkg (called party VCI package) ..... | 12 | +| 5.3.3 | calledPartyVpciPkg (called party VPCI package) ..... | 12 | +| 5.3.4 | callingPartyNumberPtrPkg (calling party number pointer package) ..... | 12 | +| 5.3.5 | callingPartyVciPkg (calling party VCI package) ..... | 12 | +| 5.3.6 | callingPartyVpciPkg (calling party VPCI package) ..... | 12 | +| 5.3.7 | retryPkg (retry package) ..... | 13 | +| 5.3.8 | uniAccessPtrPkg (uni access pointer package) ..... | 13 | +| 5.4 | Definition of attributes ..... | 13 | +| 5.4.1 | atmTrafficDescriptorPtr (ATM traffic descriptor pointer) ..... | 13 | +| 5.4.2 | calledPartyNumber (called party number) ..... | 13 | +| 5.4.3 | calledPartySelectionType (called party selection type) ..... | 13 | +| 5.4.4 | calledPartyVci (called party VCI) ..... | 14 | +| 5.4.5 | calledPartyVpci (called party VPCI) ..... | 14 | +| 5.4.6 | callingPartyDirectoryNumberPtr (calling party directory number pointer) ..... | 14 | +| 5.4.7 | callingPartyVci (calling party VCI) ..... | 14 | +| 5.4.8 | callingPartyVpci (calling party VPCI) ..... | 14 | + +| | Page | +|-------------------------------------------------------------------|-------------| +| 5.4.9 egressBandwidth (egress bandwidth) ..... | 15 | +| 5.4.10 ingressBandwidth (ingress bandwidth)..... | 15 | +| 5.4.11 retryInterval (retry interval) ..... | 15 | +| 5.4.12 retryLimit (retry limit) ..... | 15 | +| 5.4.13 softPvcCause (soft PVC cause) ..... | 15 | +| 5.4.14 softPvcId (soft PVC identifier)..... | 16 | +| 5.4.15 switchingModes (switching modes) ..... | 16 | +| 5.4.16 uniAccessPtr (uni access pointer)..... | 16 | +| 5.4.17 vpiRange (VPI range)..... | 16 | +| 5.4.18 vpPoolAndVpciPtrList (VP pool and VPCI pointer list) ..... | 16 | +| 5.4.19 vpPoolId (VP pool identifier)..... | 17 | +| 6 Type definitions ..... | 17 | +| 7 Protocol stacks ..... | 18 | +| Annex A – Management requirements ..... | 19 | +| A.1 Management requirements for switched virtual paths ..... | 19 | +| A.2 Management requirements for user-to-user soft PVCs..... | 19 | +| Appendix I – Bibliography..... | 20 | +| Appendix II – Instantiation examples for switched VPs..... | 22 | + +# **Stage 2 and stage 3 description for the Q3 interface – Customer administration: Enhanced broadband switch management** + +# **1 Purpose and Scope** + +This Recommendation specifies the Q3 interface between an ATM switch with enhanced functionality and the Telecommunications Management Network (TMN). The interface specified is that between TMN Network Elements or Q-Adapters which interface to TMN Operations Systems (OSs) without mediation and between OSs and Mediation Devices, as defined in ITU-T Recommendation M.3010 [5]. + +The scope of this Recommendation includes the management of switched VPs as defined in ITU-T Recommendations Q.2766.1 [8] and Q.2934 [11] and of soft PVCs as defined in ITU-T Recommendation Q.2767.1 [9]. The associated management for customer administration and for call routing is also within the scope of this Recommendation. The object model in this Recommendation is based on and extends the model in ITU-T Recommendation Q.824.6 [12]. + +The definition of the functionality of TMN Operations Systems is outside the scope of this Recommendation. Security management is also outside the scope of this Recommendation. + +Existing protocols are used where possible, and the focus of the work is on defining the object model. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation I.311 (1996), *B-ISDN general network aspects*. +- [2] ITU-T Recommendation I.363.5 (1996), *B-ISDN ATM Adaptation Layer (AAL) specification: Type 5 AAL*. +- [3] ITU-T Recommendation I.610 (1999), *B-ISDN operation and maintenance principles and functions*. +- [4] ITU-T Recommendation I.751 (1996), *Asynchronous transfer mode management of the network element view*. +- [5] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [6] ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- [7] ITU-T Recommendations Q.2761 (1999), Q.2762 (1999), Q.2763 (1999), Q.2764 (1999), *B-ISDN User Part (B-ISUP) of Signalling System No. 7*. +- [8] ITU-T Recommendation Q.2766.1 (1998), *Switched virtual path capability*. +- [9] ITU-T Recommendation Q.2767.1 (2000), *Soft PVC capability*. + +- [10] ITU-T Recommendation Q.2931 (1995), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control.* +- [11] ITU-T Recommendation Q.2934 (1998), *Digital subscriber signalling system No. 2 – Switched virtual path capability.* +- [12] ITU-T Recommendation Q.824.6 (1998), *Broadband Switch Management.* +- [13] CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1992, *Information technology – Open Systems Interconnection – Structure of management information: Management information model.* +- [14] CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- [15] CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1992, *Information technology – Open Systems Interconnection – Systems management: State management function.* +- [16] CCITT Recommendation X.732 (1992) | ISO/IEC 10164-3:1992, *Information technology – Open Systems Interconnection – Systems management: Attributes for representing relationships.* + +# 3 Definitions, abbreviations and conventions + +### 3.1 Definitions + +This Recommendation defines the following terms: + +**3.1.1 permanent VCC:** A permanent VCC is a virtual circuit connection which is established by configuration management, not by on-demand call control. + +**3.1.2 soft PVC:** A connection which is provisioned via management at the soft PVC Calling Endpoint (at the source interface) and established by signalling procedures across a network to the soft PVC Called Endpoint (at the destination interface). + +**3.1.3 virtual channel trail:** This corresponds to a VCC in standard ATM terminology. + +**3.1.4 virtual channel trail termination point:** This corresponds to the end point of a VCC and marks the extremity of an end-to-end F5 OAM flow. + +**3.1.5 virtual channel connection termination point:** This corresponds to an intermediate point of a VCC and may mark the extremity of a segment F5 OAM flow. + +**3.1.6 virtual path trail:** This corresponds to a VPC in standard ATM terminology. + +**3.1.7 virtual path trail termination point:** This corresponds to the end point of a VPC and marks the extremity of an end-to-end F4 OAM flow. + +**3.1.8 virtual path connection termination point:** This corresponds to an intermediate point of a VPC and may mark the extremity of a segment F4 OAM flow. + +In addition, this Recommendation uses terms defined in ITU-T Recommendations: + +**3.1.9 F4 OAM flow:** See ITU-T I.610 [3]. + +**3.1.10 F5 OAM flow:** See ITU-T I.610 [3]. + +**3.1.11 soft PVC called endpoint:** See ITU-T Q.2767.1 [9]. + +**3.1.12 soft PVC calling endpoint:** See ITU-T Q.2767.1 [9]. + +**3.1.13 trail termination point:** See ITU-T M.3100 [6]. + +- 3.1.14 virtual channel:** See ITU-T I.311 [1]. +- 3.1.15 virtual channel connection:** See ITU-T I.311 [1]. +- 3.1.16 virtual path:** See ITU-T I.311 [1]. +- 3.1.17 virtual path connection:** See ITU-T I.311 [1]. + +### **3.2 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------------------------| +| AAL | ATM Adaptation Layer | +| AIS | Alarm Indication Signal | +| ASN.1 | Abstract Syntax Notation One | +| ATM | Asynchronous Transfer Mode | +| ERD | Entity Relationship Diagram | +| GDMO | Guidelines for the Definition of Managed Objects | +| MIB | Management Information Base | +| MOC | Managed Object Class | +| NNI | Network-Network Interface | +| OAM | Operations, Administration and Maintenance | +| OS | Operations System | +| PVC | Permanent Virtual Connection | +| PVCC | Permanent Virtual Channel Connection | +| PVPC | Permanent Virtual Path Connection | +| RDI | Remote Defect Indication | +| RDN | Relative Distinguished Name | +| SDH | Synchronous Digital Hierarchy | +| SVP | Switched Virtual Path | +| TMN | Telecommunications Management Network | +| TTP | Trail Termination Point | +| UNI | User-Network Interface | +| VC | Virtual Channel | +| VCC | Virtual Channel Connection | +| VCI | Virtual Channel Identifier | +| VP | Virtual Path | +| VPC | Virtual Path Connection | +| VPCI | Virtual Path Connection Identifier | +| VPI | Virtual Path Identifier | + +### 3.3 Conventions + +Objects and their characteristics and associated ASN.1 defined here are given names with capitals used to indicate the start of the next word and acronyms are treated as if they were words. + +Throughout this Recommendation, all new attributes are named according to the following guidelines: + +- The name of an attribute ends in the string "Ptr" if and only if the attribute value is intended to identify a single object. +- The name of an attribute ends in the string "PtrList" if and only if the attribute value is intended to identify one or more objects. +- The name of an attribute is composed of the name of an object class followed by the string "Ptr" if and only if the attribute value is intended to identify a specific object class. +- If an attribute is intended to identify different object classes, a descriptive name is given to that attribute and a description is provided in the attribute behaviour. +- The name of an attribute ends in the string "Id" if and only if the attribute value is intended to identify the name of an object, in which case this attribute should be the first one listed, should use ASN.1 NameType and should not be used to convey other information. +- The name of an attribute is composed of the name of an object class followed by the string "Id" if and only if the attribute value is intended to identify the name of the object class holding that attribute. + +# 4 General overview + +The following information model diagrams have been drawn for the purpose of clarifying the relations between the different object classes of the model. + +- 1) Entity Relationship Models showing the relations of the different managed objects. +- 2) Inheritance Hierarchy showing how managed objects are derived from each other (i.e. the different paths of inherited characteristics of the different managed objects). + +These diagrams are only for clarification. The formal specification in terms of GDMO templates and ASN.1 type definitions are the relevant information for implementations. + +## 4.1 Entity relationship models + +The following conventions are used in the diagrams (see Figure 1): + +![Legend for Entity Relationship Models showing various relationship and class types.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +The legend defines the following conventions: + +- c**: is contained in +- 1:1 containment**: represented by a double-headed arrow with a single arrowhead at each end. +- 1:N containment**: represented by a double-headed arrow with a single arrowhead at one end. +- a**: is associated with +- 1:1 association**: represented by a dashed double-headed arrow with a single arrowhead at each end. +- 1:N association**: represented by a dashed double-headed arrow with a single arrowhead at one end. +- bidirectional**: represented by a double-headed arrow with two arrowheads. +- unidirectional**: represented by a single-headed arrow. +- i**: "is-a" relationship (represented by a dashed box with a solid border). +- moc**: managed object class (represented by a solid box). +- moc**: uninstantiable object class (superclass) (represented by a dashed box). +- moc**: managed object class outside the actual fragment (represented by a shaded box). + +T0412880-99 + +Legend for Entity Relationship Models showing various relationship and class types. + +Figure 1/Q.824.7 – Conventions used in diagrams for Entity Relationship Models + +Where the directionality of containment is not clear, it can be identified by implications since the root class is unique. + +#### 4.1.1 Entity relationship diagram for the switched virtual paths + +See Figure 2. + +![Entity relationship diagram for switched virtual paths showing relationships between various network elements.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +The diagram illustrates the following entities and relationships: + +- tcAdaptorTTP Bidirectional (I.751)**: A shaded box at the top, connected via a **c** relationship to **vpPool**. +- customerProfileBb (Q.824.6)**: A shaded box on the left, connected via a **c** relationship to **vpSwitchingInd** and via an **a** relationship to **uniAccessR1**. +- uniAccessR1**: A white box in the center-left, connected via an **a** relationship to **vpPool**. +- vpPool**: A white box in the center, connected via an **a** relationship to **virtualPathGroupR1**. +- nniAccess (Q.824.6)**: A shaded box on the right, connected via a **c** relationship to **virtualPathGroupR1**. +- vpSwitchingInd**: A white box at the bottom left. +- virtualPathGroupR1**: A white box at the bottom center. + +T0412890-99 + +Entity relationship diagram for switched virtual paths showing relationships between various network elements. + +Figure 2/Q.824.7 – Entity relationship diagram – switched virtual paths + +#### 4.1.2 Entity relationship diagram for the soft PVCs + +See Figure 3. + +![Entity relationship diagram for soft PVCs showing relationships between managedElementR1, Q.824.0 directoryNumber, Q.824.6 uniAccess, softPvc, softPvpc, and softPvcc.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +The diagram illustrates the following entities and relationships: + +- managedElementR1 (M.3100)**: A solid rectangle at the top. It has a solid line labeled 'c' pointing down to **softPvc**. +- Q.824.0 directoryNumber**: A solid rectangle on the left. It has a dashed line labeled 'a' pointing left from **softPvc**. There is also a self-looping dashed line labeled 'a' on this entity. +- Q.824.6 uniAccess**: A solid rectangle on the left, below **Q.824.0 directoryNumber**. It has a dashed line labeled 'a' pointing left from **softPvc**. There is also a self-looping dashed line labeled 'a' on this entity. +- softPvc**: A dashed rectangle in the center. It receives a solid line labeled 'c' from **managedElementR1** and dashed lines labeled 'a' from **Q.824.0 directoryNumber** and **Q.824.6 uniAccess**. It has a solid line labeled 'i' pointing down to a junction. +- softPvpc** and **softPvcc**: Solid rectangles at the bottom. They both receive solid lines from the junction point labeled 'i'. + +T0412900-99 + +Entity relationship diagram for soft PVCs showing relationships between managedElementR1, Q.824.0 directoryNumber, Q.824.6 uniAccess, softPvc, softPvpc, and softPvcc. + +Figure 3/Q.824.7 – Entity relationship diagram – soft PVCs + +## 4.2 Inheritance hierarchy + +See Figure 4. + +![Inheritance hierarchy diagram for Q.824.7](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +``` +graph LR; top["\"X.721\": top"] --- Q824_6_1["\"Q.824.6\": postAnalysis Evaluation"]; top --- softPvc["softPvc"]; top --- Q824_6_2["\"Q.824.6\": uniAccess"]; top --- Q824_6_3["\"Q.824.6\": virtualPathGroup"]; top --- vpPool["vpPool"]; top --- Q824_6_4["\"Q.824.6\": supplementary ServiceIndBb"]; Q824_6_1 --- postAnalysisEvaluationR1["postAnalysis EvaluationR1"]; softPvc --- softPvcc["softPvcc"]; softPvc --- softPvpc["softPvpc"]; Q824_6_2 --- uniAccessR1["uniAccessR1"]; Q824_6_3 --- virtualPathGroupR1["virtualPathGroup R1"]; Q824_6_4 --- vpSwitchingInd["vpSwitchingInd"]; +``` + +The diagram illustrates the inheritance hierarchy for the Q.824.7 standard. At the top level is the base class "X.721": top. This class inherits from several intermediate classes: "Q.824.6": postAnalysis Evaluation, softPvc, "Q.824.6": uniAccess, "Q.824.6": virtualPathGroup, vpPool, and "Q.824.6": supplementary ServiceIndBb. These intermediate classes further inherit from specific classes: postAnalysis EvaluationR1, softPvcc, softPvpc, uniAccessR1, virtualPathGroup R1, and vpSwitchingInd. A small code T0412910-99 is visible at the bottom right of the diagram. + +Inheritance hierarchy diagram for Q.824.7 + +Figure 4/Q.824.7 – Inheritance hierarchy + +# 5 Formal definitions + +This clause gives the formal definitions of the managed object classes, name bindings, general packages, behaviours, attributes, actions and notifications. + +## 5.1 Object classes + +This subclause specifies the object classes for all of the managed objects used in the management information model. These object classes are either defined here or by reference to other specifications. Classes of managed objects which are defined elsewhere and which are only used for containment are not included, but are identified by the name bindings for the classes specified here. + +Unidirectional trails are modelled by bidirectional objects with the traffic descriptor in the unused direction set to a null value. + +All of the instantiable classes that are defined in ITU-T I.751 [4] may be instantiated. + +The following class which is defined in ITU-T M.3100 [6] may be instantiated: + +- managedElementR1. + +All of the instantiable classes that are defined in ITU-T Q.824.6 [12] may be instantiated. + +The following class which is defined in ITU-T X.721 [14] may be instantiated: + +- log. + +#### 5.1.1 Profiling notes for imported classes + +No profiling notes are required. + +#### 5.1.2 Definition of classes + +##### 5.1.2.1 postAnalysisEvaluationR1 (post analysis evaluation revision 1) + +postAnalysisEvaluationR1 MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Q.824.6":postAnalysisEvaluation; +CHARACTERIZED BY +postAnalysisEvaluationR1Pkg PACKAGE +BEHAVIOUR postAnalysisEvaluationR1Beh; +ATTRIBUTES +switchingModes +DEFAULT VALUE Q824-7Asn1Module.switchingModesDefault +GET-REPLACE;;; +REGISTERED AS {q824-7ManagedObjectClass 1}; + +postAnalysisEvaluationR1Beh BEHAVIOUR +DEFINED AS +"This subclass of postAnalysisEvaluation is enhanced to support VP switching."; + +##### 5.1.2.2 softPvc (soft PVC) + +softPvc MANAGED OBJECT CLASS +DERIVED FROM "Rec. X.721| ISO/IEC 10165-2": top; +CHARACTERIZED BY +"ITU-T M.3100": attributeValueChangeNotificationPackage, +"ITU-T M.3100": stateChangeNotificationPackage, +"ITU-T M.3100": createDeleteNotificationsPackage, +softPvcPkg PACKAGE +BEHAVIOUR softPvcBeh; +ATTRIBUTES +softPvcId +GET +SET-BY-CREATE, +"Rec. X.721|ISO/IEC-10165-2": administrativeState +GET-REPLACE, +"Rec. X.721|ISO/IEC-10165-2": operationalState +GET +SET-BY-CREATE, +calledPartyNumber +GET +SET-BY-CREATE, +calledPartySelectionType +GET +SET-BY-CREATE, +softPvcCause +GET;;; +CONDITIONAL PACKAGES +atmTrafficDescriptorPtrPkg +PRESENT IF "supplied by the managing system", + +``` + +uniAccessPtrPkg + PRESENT IF "instance is associated with a 'uniAccess' object instance", +callingPartyVpciPkg + PRESENT IF "supplied by the managing system", +callingPartyNumberPtrPkg + PRESENT IF "supplied by the managing system", +calledPartyVpciPkg + PRESENT IF "supplied by the managing system", +retryPkg + PRESENT IF "supplied by the managing system"; +REGISTERED AS {q824-7ManagedObjectClass 2}; + +``` + +###### **softPvcBeh BEHAVIOUR** + +###### **DEFINED AS** + +"The 'softPvc' object class (SPVC = Soft Permanent Virtual Connection) is a class of managed objects that delimit virtual channel (VC) or virtual path (VP) connections. + +The softPvc class is not instantiated, but serves as a superclass from which specialized subclasses are derived and instantiated. These represent either VC or VP connections. + +Management operations are limited to the network element where the originating side of the SPVC is located. + +For the 'administrativeState' attribute only the values locked and unlocked shall be used. + +If the attribute 'calledPartySelectionType' has the value requiredValue, then the package 'calledPartyVpciPkg' must be present. + +The calling party number at the originating UNI shall be one of the directory numbers assigned to this access, that is the object referenced by the callingPartyDirectoryNumberPtr must be associated with the object referenced by the uniAccessPtr. + +The administrative state attribute may be used to establish ('unlocked') and release ('locked') the soft PVC." + +##### **5.1.2.3 softPvcc (soft PVCC)** + +###### **softPvcc MANAGED OBJECT CLASS** + +###### **DERIVED FROM softPvc;** + +###### **CHARACTERIZED BY** + +###### **softPvccPkg PACKAGE** + +###### **BEHAVIOUR softPvccBeh;;;** + +###### **CONDITIONAL PACKAGES** + +###### **callingPartyVciPkg** + +PRESENT IF "supplied by the managing system", + +###### **calledPartyVciPkg** + +PRESENT IF "supplied by the managing system"; + +REGISTERED AS {q824-7ManagedObjectClass 3}; + +###### **softPvccBeh BEHAVIOUR** + +###### **DEFINED AS** + +"The 'softPvcc' object class is an instantiable subclass of the 'softPvc' managed object class that delimits virtual channel (VC) connections. + +If the attribute 'calledPartySelectionType' has the value requiredValue, then the package 'calledPartyVciPkg' must be present. + +The VPCI used by the soft PVCC at the originating UNI shall be one of the VPCIs assigned to this access, that is the callingPartyVpci has to be one of the VPCIs assigned to the associated uniAccess (referenced by the uniAccessPtr) in its tpAndVpciSigPtrList attribute." + +##### **5.1.2.4 softPvpc (soft PVPC)** + +###### **softPvpc MANAGED OBJECT CLASS** + +###### **DERIVED FROM softPvc;** + +###### **CHARACTERIZED BY** + +###### **softPvpcPkg PACKAGE** + +###### **BEHAVIOUR softPvpcBeh;;;** + +REGISTERED AS {q824-7ManagedObjectClass 4}; + +softPvpcBeh BEHAVIOUR + +DEFINED AS + +"The 'softPvpc' object class is an instantiable subclass of the 'softPvc' managed object class that delimits virtual path (VP) connections. + +The VPCI used by the soft PVPC at the originating UNI shall be one of the VPCIs assigned to this access, that is the callingPartyVpci has to be one of the VPCIs assigned to the associated uniAccessR1 (referenced by the uniAccessPtr) in its vpPoolAndVpciPtrList attribute."; + +##### 5.1.2.5 uniAccessR1 (UNI access revision 1) + +uniAccessR1 MANAGED OBJECT CLASS + +DERIVED FROM "ITU-T Q.824.6":uniAccess; + +CHARACTERIZED BY + +uniAccessR1Pkg PACKAGE + +BEHAVIOUR uniAccessR1Beh; + +ATTRIBUTES + +vpPoolAndVpciPtrList + +GET-REPLACE ADD-REMOVE;;; + +REGISTERED AS {q824-7ManagedObjectClass 5}; + +uniAccessR1Beh BEHAVIOUR + +DEFINED AS + +"This subclass of uniAccess represents a UNI access which supports VP switching. + +The vpPoolAndVpciPtrList attribute identifies the VPCI ranges that may be used at this uniAccessR1. A VPCI range is associated with each VPI range. Within a uniAccessR1, VPCIs and VPCI ranges assigned through the tpAndVpciSigPtrList and vpPoolAndVpciPtrList attributes must not overlap. + +Associated signalling does not apply when supporting switched virtual paths. Thus for instances of this class that support VP switching the signallingChannelPtrPkg (inherited from uniAccess) must be present and the sigChannel components of the tpAndVpciSigPtrList attribute (inherited from uniAccess) must be empty."; + +##### 5.1.2.6 virtualPathGroupR1 (virtual path group revision 1) + +virtualPathGroupR1 MANAGED OBJECT CLASS + +DERIVED FROM "ITU-T Q.824.6":virtualPathGroup; + +CHARACTERIZED BY + +virtualPathGroupR1Pkg PACKAGE + +BEHAVIOUR virtualPathGroupR1Beh; + +ATTRIBUTES + +vpPoolAndVpciPtrList + +GET-REPLACE ADD-REMOVE;;; + +REGISTERED AS {q824-7ManagedObjectClass 6}; + +virtualPathGroupR1Beh BEHAVIOUR + +DEFINED AS + +"This subclass of virtualPathGroup represents a virtual path group which supports VP switching."; + +##### 5.1.2.7 vpPool (VP pool) + +vpPool MANAGED OBJECT CLASS + +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2":top; + +CHARACTERIZED BY + +"ITU-T M.3100": attributeValueChangeNotificationPackage, + +"ITU-T M.3100": stateChangeNotificationPackage, + +"ITU-T M.3100": createDeleteNotificationsPackage, + +"Rec. X.721|ISO/IEC 10165-2":administrativeStatePackage, + +vpPoolPkg PACKAGE + +BEHAVIOUR vpPoolBeh; + +ATTRIBUTES + +vpPoolId + +GET + +SET-BY-CREATE, + +vpiRange + +GET-REPLACE, + +``` + +egressBandwidth + GET-REPLACE, +ingressBandwidth + GET-REPLACE;; +CONDITIONAL PACKAGES + "ITU-T Q.824.6": blockedForMaintenancePkg + PRESENT IF "supplied by the managing system", + "ITU-T Q.824.6": maintenanceSignallingRunningPkg + PRESENT IF "supplied by the managing system", + "ITU-T Q.824.6": propagationDelayPkg + PRESENT IF "supplied by the managing system", + "ITU-T Q.824.6": remoteBlockingPkg + PRESENT IF "supplied by the managing system"; +REGISTERED AS {q824-7ManagedObjectClass 7}; + +``` + +###### vpPoolBeh BEHAVIOUR + +###### DEFINED AS + +"This managed object represents a pool of bandwidth and VPI values available for VP switching. + +The vpiRange attribute reserves a range of VPIs for switched VPs at an interface. This range of VPIs must not overlap with ranges reserved for switched VPs by other vpPool instances within the same tcAdaptorTTPBidirectional, and it must not contain a VPI used by a vpCTPBidirectional for a VP established by management within the same tcAdaptorTTPBidirectional. + +The egress and ingress bandwidth attributes are used to reserve bandwidth that may be used exclusively for switched VPs within the pool (i.e. using the VPIs within this pool). + +The attributeValueChangeNotification need not be sent for the maintenanceSignallingRunning attribute."; + +##### 5.1.2.8 vpSwitchingInd (VP switching independent) + +###### vpSwitchingInd MANAGED OBJECT CLASS + +DERIVED FROM "ITU-T Q.824.6":supplementaryServiceIndBb; + +###### CHARACTERIZED BY + +vpSwitchingIndPkg PACKAGE + +BEHAVIOUR vpSwitchingIndBeh;; + +REGISTERED AS {q824-7ManagedObjectClass 8}; + +###### vpSwitchingIndBeh BEHAVIOUR + +###### DEFINED AS + +"This subscription option enables VP switching for a user. + +Only one object of this class shall be contained within the superior managed object. "; + +### 5.2 Name bindings + +#### 5.2.1 softPvc-managedElementR1 + +##### softPvc-managedElementR1 NAME BINDING + +SUBORDINATE OBJECT CLASS + +softPvc AND SUBCLASSES; + +NAMED BY SUPERIOR OBJECT CLASS + +"ITU-T M.3100": managedElementR1 AND SUBCLASSES; + +WITH ATTRIBUTE softPvcId; + +##### CREATE + +WITH-AUTOMATIC-INSTANCE-NAMING; + +##### DELETE + +ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {q824-7NameBinding 1}; + +#### 5.2.2 vpPool-tcAdaptorTTPBidirectional + +##### vpPool-tcAdaptorTTPBidirectional NAME BINDING + +SUBORDINATE OBJECT CLASS vpPool + +AND SUBCLASSES; + +NAMED BY SUPERIOR OBJECT CLASS "ITU-T Rec. I.751":tcAdaptorTTPBidirectional +AND SUBCLASSES; +WITH ATTRIBUTE vpPoolId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {q824-7NameBinding 2}; + +### **5.3 Definition of packages** + +#### **5.3.1 atmTrafficDescriptorPtrPkg (ATM traffic descriptor pointer package)** + +atmTrafficDescriptorPtrPkg PACKAGE +ATTRIBUTES +atmTrafficDescriptorPtr +GET-REPLACE; +REGISTERED AS {q824-7Package 1}; + +#### **5.3.2 calledPartyVciPkg (called party VCI package)** + +calledPartyVciPkg PACKAGE +ATTRIBUTES +calledPartyVci +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 2}; + +#### **5.3.3 calledPartyVpciPkg (called party VPCI package)** + +calledPartyVpciPkg PACKAGE +ATTRIBUTES +calledPartyVpci +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 3}; + +#### **5.3.4 callingPartyNumberPtrPkg (calling party number pointer package)** + +callingPartyNumberPtrPkg PACKAGE +ATTRIBUTES +callingPartyDirectoryNumberPtr +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 4}; + +#### **5.3.5 callingPartyVciPkg (calling party VCI package)** + +callingPartyVciPkg PACKAGE +ATTRIBUTES +callingPartyVci +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 5}; + +#### **5.3.6 callingPartyVpciPkg (calling party VPCI package)** + +callingPartyVpciPkg PACKAGE +ATTRIBUTES +callingPartyVpci +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 6}; + +#### **5.3.7 retryPkg (retry package)** + +retryPkg PACKAGE +ATTRIBUTES +retryLimit +GET +SET-BY-CREATE, +retryInterval +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 7}; + +#### **5.3.8 uniAccessPtrPkg (uni access pointer package)** + +uniAccessPtrPkg PACKAGE +ATTRIBUTES +uniAccessPtr +GET +SET-BY-CREATE; +REGISTERED AS {q824-7Package 8}; + +### **5.4 Definition of attributes** + +#### **5.4.1 atmTrafficDescriptorPtr (ATM traffic descriptor pointer)** + +atmTrafficDescriptorPtr ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.PointerOrNull; +MATCHES FOR EQUALITY; +BEHAVIOUR atmTrafficDescriptorPtrBeh; +REGISTERED AS {q824-7Attribute 1}; + +atmTrafficDescriptorPtrBeh BEHAVIOUR +DEFINED AS + +"This attribute is used as a pointer to an instance of the traffic descriptor managed object class."; + +#### **5.4.2 calledPartyNumber (called party number)** + +calledPartyNumber ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.DirectoryNumber; +MATCHES FOR EQUALITY; +BEHAVIOUR calledPartyNumberBeh; +REGISTERED AS {q824-7Attribute 2}; + +calledPartyNumberBeh BEHAVIOUR +DEFINED AS + +"This attribute specifies the directory number of the called party."; + +#### **5.4.3 calledPartySelectionType (called party selection type)** + +calledPartySelectionType ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.CalledPartySelectionType; +MATCHES FOR EQUALITY; +BEHAVIOUR calledPartySelectionTypeBeh; +REGISTERED AS {q824-7Attribute 3}; + +calledPartySelectionTypeBeh BEHAVIOUR +DEFINED AS + +"This attribute indicates whether the VPCI (if applicable also the VCI) for the called party have to be used at the destination. In case of 'anyValue' the destination switch will choose VPCI (if applicable also VCI) values. In case of 'requiredValue', the VPCI (if applicable also VCI) values supplied by the managing system will be used." +"; + +#### **5.4.4 calledPartyVci (called party VCI)** + +calledPartyVci ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.VciValue; +MATCHES FOR EQUALITY; +BEHAVIOUR calledPartyVciBeh; +REGISTERED AS {q824-7Attribute 4}; + +calledPartyVciBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the VCI for the called party."; + +#### **5.4.5 calledPartyVpci (called party VPCI)** + +calledPartyVpci ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.VpciValue; +MATCHES FOR EQUALITY; +BEHAVIOUR calledPartyVpciBeh; +REGISTERED AS {q824-7Attribute 5}; + +calledPartyVpciBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the VPCI for the called party."; + +#### **5.4.6 callingPartyDirectoryNumberPtr (calling party directory number pointer)** + +callingPartyDirectoryNumberPtr ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR callingPartyDirectoryNumberPtrBeh; +REGISTERED AS {q824-7Attribute 6}; + +callingPartyDirectoryNumberPtrBeh BEHAVIOUR +DEFINED AS +"This attribute is used as a pointer to an instance of a subclass of the 'directoryNumber' managed object class which pertains to the calling party."; + +#### **5.4.7 callingPartyVci (calling party VCI)** + +callingPartyVci ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.VciValue; +MATCHES FOR EQUALITY; +BEHAVIOUR callingPartyVciBeh; +REGISTERED AS {q824-7Attribute 7}; + +callingPartyVciBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the VCI for the calling party."; + +#### **5.4.8 callingPartyVpci (calling party VPCI)** + +callingPartyVpci ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.VpciValue; +MATCHES FOR EQUALITY; +BEHAVIOUR callingPartyVpciBeh; +REGISTERED AS {q824-7Attribute 8}; + +callingPartyVpciBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the VPCI for the calling party."; + +#### **5.4.9 egressBandwidth (egress bandwidth)** + +egressBandwidth ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.EgressBandwidth ; +BEHAVIOUR egressBandwidthBeh; +REGISTERED AS {q824-7Attribute 9}; + +egressBandwidthBeh BEHAVIOUR +DEFINED AS +"This attribute describes the egress bandwidth reserved for the VP pool."; + +#### **5.4.10 ingressBandwidth (ingress bandwidth)** + +ingressBandwidth ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.IngressBandwidth ; +BEHAVIOUR ingressBandwidthBeh; +REGISTERED AS {q824-7Attribute 10}; + +ingressBandwidthBeh BEHAVIOUR +DEFINED AS +"This attribute describes the ingress bandwidth reserved for the VP pool."; + +#### **5.4.11 retryInterval (retry interval)** + +retryInterval ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.RetryInterval; +MATCHES FOR EQUALITY; +BEHAVIOUR retryIntervalBeh; +REGISTERED AS {q824-7Attribute 11}; + +retryIntervalBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the time (in sec) between two attempts to re-establish an SPVC automatically."; + +#### **5.4.12 retryLimit (retry limit)** + +retryLimit ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.RetryLimit; +MATCHES FOR EQUALITY; +BEHAVIOUR retryLimitBeh; +REGISTERED AS {q824-7Attribute 12}; + +retryLimitBeh BEHAVIOUR +DEFINED AS +"This attribute specifies the maximal number of attempts to re-establish an SPVC automatically. After this number is reached no more re-establishment efforts will be made. However a value of zero indicates that an infinite number of call attempts will be made."; + +#### **5.4.13 softPvcCause (soft PVC cause)** + +softPvcCause ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.SoftPvcCause; +MATCHES FOR EQUALITY; +BEHAVIOUR softPvcCauseBeh; +REGISTERED AS {q824-7Attribute 13}; + +softPvcCauseBeh BEHAVIOUR +DEFINED AS +"This attribute is used to inform the operator of problems with SPVC establishment after receiving an 'attributeValueChange' notification that contains this attribute in the component 'attributeIdentifierList' of its information syntax. Possible cause values contained in this attribute are identical to those specified in ITU-T Recommendations Q.850, Q.2610 and Q.2767.1."; + +#### **5.4.14 softPvcId (soft PVC identifier)** + +softPvcId ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.NameType ; +MATCHES FOR EQUALITY; +BEHAVIOUR softPvcIdBeh; +REGISTERED AS {q824-7Attribute 14}; + +softPvcIdBeh BEHAVIOUR +DEFINED AS +"This is the naming attribute of the object class 'softPvc' and subclasses." ; + +#### **5.4.15 switchingModes (switching modes)** + +switchingModes ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.SwitchingModes; +MATCHES FOR EQUALITY; +BEHAVIOUR switchingModesBeh; +REGISTERED AS {q824-7Attribute 15}; + +switchingModesBeh BEHAVIOUR +DEFINED AS +"This attribute specifies if the managed object may be used for channel switching and/or path switching. At least one of the two modes (channelSwitching, pathSwitching) must have value TRUE."; + +#### **5.4.16 uniAccessPtr (uni access pointer)** + +uniAccessPtr ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR uniAccessPtrBeh; +REGISTERED AS {q824-7Attribute 16}; + +uniAccessPtrBeh BEHAVIOUR +DEFINED AS +"This attribute is used as a pointer to an instance of the 'uniAccess' managed object class or a subclass."; + +#### **5.4.17 vpiRange (VPI range)** + +vpiRange ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.VpiRange ; +BEHAVIOUR vpiRangeBeh; +REGISTERED AS {q824-7Attribute 17}; + +vpiRangeBeh BEHAVIOUR +DEFINED AS +"This attribute describes the range of VPI values belonging to the VP pool."; + +#### **5.4.18 vpPoolAndVpciPtrList (VP pool and VPCI pointer list)** + +vpPoolAndVpciPtrList ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.VpPoolAndVpciPtrList ; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR vpPoolAndVpciPtrListBeh; +REGISTERED AS {q824-7Attribute 18}; + +vpPoolAndVpciPtrListBeh BEHAVIOUR +DEFINED AS +"This is a set-valued attribute whose value(s) point to instances of the vpPool managed object class or its subclasses. The bandwidth and VPIs represented by the vpPool instances are available for VP switching at the concerned access. A VPCI value is related to every pointer. This VPCI value determines the lower limit of the VPCI range for the VP pool. The upper limit is calculated from the lower limit and the VPI range of the pool."; + +#### 5.4.19 vpPoolId (VP pool identifier) + +vpPoolId ATTRIBUTE +WITH ATTRIBUTE SYNTAX Q824-7Asn1Module.NameType ; +MATCHES FOR EQUALITY; +BEHAVIOUR vpPoolIdBeh; +REGISTERED AS {q824-7Attribute 19}; + +vpPoolIdBeh BEHAVIOUR +DEFINED AS +"This entity describes the object identifier attribute of the object class 'vpPool'." ; + +## 6 Type definitions + +``` +Q824-7Asn1Module { + itu-t(0) recommendation (0) q(17) ca(824) dot(127) ebs(7) + q824-7informationModel(0) asn1Modules(2) +asn1DefinedTypesModule(0)} + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN +-- EXPORTS everything + +IMPORTS + ObjectInstance + FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)} + + VciValue + FROM AtmMIBMod {itu-t(0) recommendation(0) i(9) atmm(751) + informationModel(0) asn1Module(2) atm(0)} + + NameType, + PointerOrNull + FROM ASN1DefinedTypesModule {ccitt recommendation m 3100 + informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0)} + + DirectoryNumber, + VpciValue + FROM ASN1DefinedTypesModule {itu-t(0) recommendation(0) + q(17) 824(824) dot(127) bsm(6) + informationModel(0) asn1Module(2) asn1TypeModule(0)}--Q.824.6 + +; -- end of imports + +-- start of object identifier definitions + +q824-7InformationModel + OBJECT IDENTIFIER ::= {itu-t(0) recommendation (0) q(17) ca(824) dot(127) + ebs(7) q824-7InformationModel(0)} +q824-7StandardSpecificExtension + OBJECT IDENTIFIER ::= {q824-7informationModel + q824-7StandardSpecificExtension(0)} +q824-7ManagedObjectClass + OBJECT IDENTIFIER ::= {q824-7informationModel q824-7ManagedObjectClass(3)} +q824-7Package + OBJECT IDENTIFIER ::= {q824-7informationModel q824-7Package(4)} +q824-7NameBinding + OBJECT IDENTIFIER ::= {q824-7informationModel q824-7NameBinding(6)} +q824-7Attribute + OBJECT IDENTIFIER ::= {q824-7informationModel q824-7Attribute(7)} +q824-7Action + OBJECT IDENTIFIER ::= {q824-7informationModel q824-7Action(9)} +``` + +``` + +q824-7Notification +OBJECT IDENTIFIER ::= {q824-7informationModel q824-7Notification(10)} + +-- end of object identifier definitions + +-- other ASN1 definitions in alphabetical order + +CalledPartySelectionType ::= ENUMERATED { + anyValue (0), + requiredValue (1) } + +EgressBandwidth ::= INTEGER + +IngressBandwidth ::= INTEGER + +RetryInterval ::= INTEGER(0..3600) + +RetryLimit ::= INTEGER + +SoftPvcCause ::= SEQUENCE { + softPvcCauseIndication [0] SoftPvcCauseIndication, + softPvcCauseValue [1] SoftPvcCauseValue } + +SoftPvcCauseIndication ::= ENUMERATED { + noCause (0), -- no failure detected + firstCause (1), -- failure detected, trying to re-establish + lastCause (2), -- not or no longer attempting to re-establish +} + +SoftPvcCauseValue ::= INTEGER (0..127) + +SwitchingModes ::= SEQUENCE { + channelSwitching BOOLEAN, + pathSwitching BOOLEAN } + +switchingModesDefault SwitchingModes ::= { + channelSwitching TRUE, + pathSwitching FALSE } + +VpiRange ::= SEQUENCE { + lowerLimit INTEGER, + upperLimit INTEGER } + +VpPoolAndVpciPtrList ::= SET OF SEQUENCE { + vpPool ObjectInstance, + lowerVpciLimit VpciValue } + +END -- of Q824-7Asn1Module + +``` + +# 7 Protocol stacks + +The protocol stacks specified in ITU-T Q.811, Q.812, G.773 and the SDH digital cross-connect part of ITU-T G.784 can be used as part of the protocol stack for this Recommendation. The following ITU-T Recommendations should be used to extend these stacks to include TM: + +- Q.2811 Broadband Q3 and X interfaces – Lower Layer Protocols. +- Q.2812 Broadband Q3 and X interfaces – Upper Layer Protocols. + +# Management requirements + +## A.1 Management requirements for switched virtual paths + +#### *VP pools* + +To support VP switching at a physical interface, a part of the bandwidth of the interface and one or more VPI ranges need to be reserved for switched VPs. A range of VPIs together with a bandwidth reserved for switched VPs using these VPIs is called a VP pool. + +#### *VPC pools* + +Before VP switching can take place, VP pools need to be associated with signalling interfaces and VPCIs need to be assigned to the VPI values. From a management perspective, a VPC Pool is a VP Pool which is associated with a signalling access and which has a VPCI range assigned to the VPI range. See ITU-T Q.2766.1 [8] for VPC Pools. + +#### *Propagation delay* + +The accumulation of propagation delay needs to be supported. The expected propagation delay should be provided for each VP Pool. + +#### *Blocking procedures* + +The blocking procedures described in 4.3/Q.2766.1 [8] need to be supported at the management interface. It shall be possible to block and unblock VPC pools, to identify remotely blocked VPs and to identify whether maintenance signalling is running. + +#### *Subscription option* + +According to ITU-T Q.2934 [11] VP switching is a subscription option. + +#### *Routing criterium* + +The support of switched VPs may be one of the criteria used to configure the selection of a route. + +## A.2 Management requirements for user-to-user soft PVCs + +![Diagram of Soft PVC Configuration (Figure A.1/Q.824.7). The diagram shows a User connected to a 'soft PVC calling endpoint' (Q3). This endpoint is connected via a 'VP or VC' link to a central node. Above this link is a dashed arc labeled 'NNI Signalling'. The central node is connected via another 'VP or VC' link to a second central node, also with an 'NNI Signalling' arc above it. The second central node is connected via a third 'VP or VC' link to a 'soft PVC called endpoint', which is then connected to another User. The diagram is labeled T0412920-99.](ced309874aec0546651b0976d5030a42_img.jpg) + +Diagram of Soft PVC Configuration (Figure A.1/Q.824.7). The diagram shows a User connected to a 'soft PVC calling endpoint' (Q3). This endpoint is connected via a 'VP or VC' link to a central node. Above this link is a dashed arc labeled 'NNI Signalling'. The central node is connected via another 'VP or VC' link to a second central node, also with an 'NNI Signalling' arc above it. The second central node is connected via a third 'VP or VC' link to a 'soft PVC called endpoint', which is then connected to another User. The diagram is labeled T0412920-99. + +**Figure A.1/Q.824.7 – Soft PVC Configuration** + +Two types of soft PVC are supported: + +- soft permanent virtual path connection (PVPC); and +- soft permanent virtual channel connection (PVCC). + +A user-to-user soft PVC is configured and established by management at the calling endpoint. There is no need for management action at the called endpoint. + +For each soft PVC the following types of information need to be provided via the Q3 interface of the "calling endpoint" network element: information related to the calling party, information related to the called party, traffic descriptors, and information to support the re-establishment of soft PVCs. + +#### *Calling Party* + +The calling party is identified by the calling party number. In addition calling party VPCI and calling party VCI (for soft PVCCs only) need to be provided. As VPCIs are defined per signalling access, the signalling access needs to be identified. + +#### *Called party* + +The called party is identified by the called party number. Optionally called party VPCI and called party VCI (for soft PVCCs only) may be provided. The called party selection type determines the selection of VPCI (and VCI) at the soft PVC called endpoint, see ITU-T Q.2767.1 [9]. + +#### *Traffic descriptors* + +The traffic descriptors for the connection need to be provided via the Q3 interface. + +#### *Re-establishment of soft PVCs* + +To support the re-establishment of soft PVCs as described in 6.5.1 and Annex 1/Q.2767.1 [9], configuration of retry limit and retry interval needs to be supported at the Q3 interface. + +The decision whether or not the network element attempts to re-establish the soft PVCs depends on the cause value, i.e. on the reason of the failure. It is a fault management requirement that this information is available at the Q3 interface. + +# APPENDIX I + +## **Bibliography** + +- ITU-T Recommendation G.773 (1993), *Protocol suites for Q-interfaces for management of transmission systems*. +- ITU-T Recommendation G.774 (1992), *Synchronous digital hierarchy (SDH) management information model for the network element view*. +- ITU-T Recommendation G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH)*. +- ITU-T Recommendation I.211 (1993), *B-ISDN service aspects*. +- ITU-T Recommendation I.327 (1993), *B-ISDN functional architecture*. +- ITU-T Recommendation I.356 (2000), *B-ISDN ATM layer cell transfer performance*. +- ITU-T Recommendation I.371 (2000), *Traffic control and congestion control in B-ISDN*. +- ITU-T Recommendation I.371.1 (1997), *Traffic control and congestion control in B-ISDN: Conformance definitions for ABT and ABR*. +- ITU-T Recommendation I.413 (1993), *B-ISDN user-network interface*. +- ITU-T Recommendations I.432.x, *B-ISDN user-network interface – Physical layer specification*. +- ITU-T Recommendation I.580 (1995), *General arrangements for interworking between B-ISDN and 64 kbit/s based ISDN*. + +- ITU-T Recommendation M.3010 (2000), *Principles for a Telecommunications management network*. +- ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. +- ITU-T Recommendation M.3400 (2000), *TMN management functions*. +- ITU-T Recommendation Q.822 (1994), *Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management*. +- ITU-T Recommendation X.208 (1988), *Specification of Abstract Syntax Notification One (ASN.1)*. +- ITU-T Recommendation X.701 (1997) | ISO/IEC 10040:1998, *Information technology – Open Systems Interconnection – System management overview*. +- ITU-T Recommendation X.722 (1992) | ISO/IEC 10165-4:1992, *Information technology – Open Systems Interconnection – Structure of Management Information: Guidelines for the definition of managed objects*. +- ITU-T Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function*. +- ITU-T Recommendation X.734 (1992) | ISO/IEC 10164-5:1992, *Information technology – Open Systems Interconnection – Systems Management: Event report management function*. +- ITU-T Recommendation X.735 (1992) | ISO/IEC 10164-6:1992, *Information technology – Open Systems Interconnection – Systems Management: Log control function*. +- ITU-T Recommendation X.737 (1995) | ISO/IEC 10164-14:1993, *Information technology – Open Systems Interconnection – Systems management: Confidence and diagnostic test categories*. +- ITU-T Recommendation X.738 (1993) | ISO/IEC 10164-13:1993, *Information technology – Open Systems Interconnection – Systems management: Summarization function*. +- ITU-T Recommendation X.739 (1993) | ISO/IEC 10164-11:1993, *Information technology – Open Systems Interconnection – Systems Management: Metric objects and attributes*. +- ITU-T Recommendation X.745 (1993) | ISO/IEC 10164-12:1993, *Information technology – Open Systems Interconnection – Systems Management: Test management function*. +- ITU-T Recommendation X.746 (2000) | ISO/IEC 10164-15:1993, *Information technology – Open Systems Interconnection – Systems management: Scheduling function*. +- ATM Forum Specification af-nm-0020.001 (1998), *M4 Interface Requirements and Logical MIB: ATM Network Element View, Version 2*. +- ATM Forum Specification af-nm-0027.001 (1999), *CMIP Specification for the M4 Interface: ATM Network Element View, Version 2*. +- ATM Forum Specification af-pnni-0066.000 (1996), *Private Network-Network Interface Specification Version 1.0 Addendum (Soft PVC MIB)*. +- ATM Forum Specification af-sig-0061.000 (1996), *ATM User-Network Interface (UNI) Signalling Specification, Version 4.0*. +- ATM Forum Specification af-uni-0010.002 (1994), *ATM User-Network Interface Specification, Version 3.1*. + +# APPENDIX II + +## Instantiation examples for switched VPs + +### Conventions + +The following conventions are used in the example (see Figure II.1): + +![Figure II.1/Q.824.7 – Conventions. The diagram illustrates two conventions for object relationships. The top part shows a large rectangle labeled 'A' containing a smaller rectangle labeled 'B', with text to the right stating 'Object A contains object B' and 'Object A points to object B'. The bottom part shows a rectangle labeled 'A' with an arrow pointing to a rectangle labeled 'B', with the text 'T0412930-99' below the arrow.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +A + +Object A contains object B + +Object A points to object B + +B + +A + +B + +T0412930-99 + +Figure II.1/Q.824.7 – Conventions. The diagram illustrates two conventions for object relationships. The top part shows a large rectangle labeled 'A' containing a smaller rectangle labeled 'B', with text to the right stating 'Object A contains object B' and 'Object A points to object B'. The bottom part shows a rectangle labeled 'A' with an arrow pointing to a rectangle labeled 'B', with the text 'T0412930-99' below the arrow. + +**Figure II.1/Q.824.7 – Conventions** + +Object instances are labelled by their class name, followed by #, followed by their RDN. Pointers are labelled by their attribute names. + +### Instantiation Example of Managed Objects (Switched VPs at UNI) + +In this example a user at a UNI has two permanent VPs (VPI = 0, VPI = 1) provided by management, while the vpPool object reserves bandwidth and a range of VPIs (not including 0 and 1) for VP switching. The vpPool is associated with the signalling access (uniAccess). See Figure II.2. + +![Diagram illustrating the instantiation example for ITU-T Q.824.7. It shows a hierarchy of network objects. At the top, 'uniAccessR1 #1' is connected to 'vpPool #1' via 'vpPoolAndVpciPtrList' and to 'vpCTPBidirectional #1' via 'tpAndVpciSigPtrList'. 'uniAccessR1 #1' also has a 'signallingChannelPtr' pointing to 'vcTTPBidirectional #1'. 'tcAdaptorTTPBidirectional #1' contains 'vpPool #1', 'vpCTPBidirectional #1', and 'vpCTPBidirectional #0'. 'vpCTPBidirectional #1' is connected to 'vpTTPBidirectional #1' with a '1' multiplicity. 'vpCTPBidirectional #0' is connected to 'vpTTPBidirectional #2' with a '1' multiplicity. 'vpTTPBidirectional #2' contains 'vcCTPBidirectional #5'. 'vcCTPBidirectional #5' is connected to 'vcTTPBidirectional #1' with a '1' multiplicity. 'uni #1' is connected to 'tcAdaptorTTPBidirectional #1' via 'underlyingTTPPointer'. A label 'T0412940-99' is present near the bottom right. A note at the bottom left states '1 upstream/downstream Connectivity Pointers'.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +classDiagram + uniAccessR1_1["uniAccessR1 #1"] --> vpPool_1["vpPool #1"] : vpPoolAndVpciPtrList + uniAccessR1_1 --> vpCTPBidirectional_1["vpCTPBidirectional #1"] : tpAndVpciSigPtrList + uniAccessR1_1 --> vcTTPBidirectional_1["vcTTPBidirectional #1"] : signallingChannelPtr + tcAdaptorTTPBidirectional_1["tcAdaptorTTPBidirectional #1"] --> uni_1["uni #1"] : underlyingTTPPointer + vpCTPBidirectional_1 --> vpTTPBidirectional_1["vpTTPBidirectional #1"] : 1 + vpCTPBidirectional_0["vpCTPBidirectional #0"] --> vpTTPBidirectional_2["vpTTPBidirectional #2"] : 1 + vpTTPBidirectional_2 --> vcCTPBidirectional_5["vcCTPBidirectional #5"] + vcCTPBidirectional_5 --> vcTTPBidirectional_1 : 1 + +``` + +Diagram illustrating the instantiation example for ITU-T Q.824.7. It shows a hierarchy of network objects. At the top, 'uniAccessR1 #1' is connected to 'vpPool #1' via 'vpPoolAndVpciPtrList' and to 'vpCTPBidirectional #1' via 'tpAndVpciSigPtrList'. 'uniAccessR1 #1' also has a 'signallingChannelPtr' pointing to 'vcTTPBidirectional #1'. 'tcAdaptorTTPBidirectional #1' contains 'vpPool #1', 'vpCTPBidirectional #1', and 'vpCTPBidirectional #0'. 'vpCTPBidirectional #1' is connected to 'vpTTPBidirectional #1' with a '1' multiplicity. 'vpCTPBidirectional #0' is connected to 'vpTTPBidirectional #2' with a '1' multiplicity. 'vpTTPBidirectional #2' contains 'vcCTPBidirectional #5'. 'vcCTPBidirectional #5' is connected to 'vcTTPBidirectional #1' with a '1' multiplicity. 'uni #1' is connected to 'tcAdaptorTTPBidirectional #1' via 'underlyingTTPPointer'. A label 'T0412940-99' is present near the bottom right. A note at the bottom left states '1 upstream/downstream Connectivity Pointers'. + +NOTE 1 – The use of #0 for the signalling VP and #5 for the signalling VC is deliberate so that the RDNs match the signalling VPI and VCI. + +NOTE 2 – Not all (possible) managed objects are shown, e.g. the atmAccessProfile and the object classes for customer administration are not shown. + +**Figure II.2/Q.824.7 – Instantiation example** + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eed8fb54a12ce6a0c2c7d288e355ade1f2c6d7de --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa16608cb5058033403399466b3ef4cc1b0dfad68daa829373036df63aa75b0 +size 10805 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/031de8ea6c5568a02faffd59b5c337f7_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/031de8ea6c5568a02faffd59b5c337f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..447025be1a2bf1718bfbb91a7807a9ac553b1372 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/031de8ea6c5568a02faffd59b5c337f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8b14a2929fa507ab2ad89541ccb0b107d1c14261dc73e8321ed50e486094fe9 +size 115094 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20ee670e117bfa1797eefabeb1dc4a875110df87 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5199a4a80372105233528188831927e03ba88fcbdbdcec8bd42168eaa62c17 +size 109086 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce0a015cca7a45d2072c8ef684257303556d1921 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b928019563530a27fe3172a1ae50690c865ec93059875b4c92858bee40d52d7 +size 160062 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b752ef8641669fb5a57e196360ef8da0a56ada1 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d5f077064bdbc99dc3fced7d54a51b520e7de1355d84c7d7c492b5546d5f820 +size 114744 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8313c01f50469a7f36e1e8f6b55f6f07983988b0 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c1448b7911867d394504632f40a7b76b37abc71eb9b6341ee1d22b8be2ff1e4 +size 108947 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f6a58a2086ddaae0141c959013b98071682d9a6 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:253c0f458857c2d4a4a3a84af1455d0adb62d65f4e686fd29e4e8fb11c52c9dd +size 94534 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/1c20b988e3792ded6d601aca944792a9_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/1c20b988e3792ded6d601aca944792a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2995af38e6a935acb330c5cd683492216d586fcc --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/1c20b988e3792ded6d601aca944792a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13c690d0437484a3c1172a3a0bd1f4a5c6d97b7fa55a89ad4e125f0048daf492 +size 213734 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/207817524fe964425718e1723d5b7d9e_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/207817524fe964425718e1723d5b7d9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9713a73667cb5d4afc2abf14e666f92ec03667ca --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/207817524fe964425718e1723d5b7d9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e71a40b720e07e45c5621e0adc6d76473b58cf22645c5114052528bdbdae15d7 +size 268767 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8ff00a23beb6fd6bd1e3297563abe4d64bb2e8a --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f23bb5cf2e3ec28c0942c7f764c254924c5a129f91fd26bb807ccd0f62a3c594 +size 132361 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1404fc82e532a9199c1c1a64bf6529f1c049d10c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab8d8f4eec0892247b17df567faca85670f78ce39021aa421809cba4fe291891 +size 100819 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/2c4c90917583576b27072e2083d75906_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/2c4c90917583576b27072e2083d75906_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e6e31ddbf8a74147bc01cd04fb5b660e57b7e31 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/2c4c90917583576b27072e2083d75906_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:540a0effc4fa76e93319dd71993304b2564d1a450089bed8ee399e90ee9293b0 +size 159783 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f11c277cf18a2a3bca2b104bbdcfd75a167eefb5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ee9f1a7716c7f20186a73dbbeabbbd1cfff558402bad718b9a1907caf9ca930 +size 110987 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faf8e30a2b61af5eb81ff7b31b9b29ec1ce18146 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edc8a99b4e9fa7cbe0a95b60baea8cbb519db7a2f133e1eb2adc3ed7ba165c92 +size 123438 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba10bd52829fe24f30acdd977ec83e2640787ef3 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d17bd6a8bbb57c58b4f068eb5b35243bd155c9a4b95af263c5772ab98eac51cb +size 92964 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9bd74d6639bed8f85ae754c292ddf900c31f94d --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6034609b61344a3496c8738b808d7efc764ff27772406fe8f9c5094bcf38b04f +size 100194 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6caffcda9eea78ec1e94878f01f0baa09b9a2838 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e222133471396d0c822d381460962b8c405cc52576e2e089ba8f89923db5e39 +size 129506 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce33b32ff740e9d55d4967d6f0d7fcf0e9f2efca --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:564b4c7e434178c6406f7a259106ce3f2c8bb67f41884c6bbee2f13afe77445e +size 97703 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c32ed5b5043e983ab6363718113737c35c0300d6 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ae9a140c2210cb740bf54133ab49cdf89955aef769660712bdb057c64a0e6b6 +size 137318 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..feda0482a6a396a3ce642e61326bcbd4c1ef307c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2287e9badcf5b6cb3c2e78e04264f8c85c1003ac427bc76f3c866675f536305 +size 83876 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3cc3e151a522f889d549619837350731680afbc --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b444e81b7aee13b7787a714b0cea47676481971afa0a3e9fb74adcea1e170096 +size 126084 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc51a5835d79f2e57fd52af5ae60c03385f093fe --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3254de30b9dcbedb0566f000787463e90fccf5890009d5128f632925bc326f5 +size 155769 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9dfb47b763867fe21a955eb32c725a209a07541 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da1969dbe86484c9e7a72aa325fc84bd9827720d93746981d96ca62e9f0d94ba +size 88191 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70ba6b9f9b22b9972086693f52314eb032ac901f --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d2455db4807972ab29b81060b5cdb2d7d7823703096b3a9ac023227a4e4731c +size 143913 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ea2d323b6d5aafe55c1b3f2de76e73d126148de --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b42d763852876ab3be6fd5c89f0b6f81285450ec64c4cca76e789d64a0ade13 +size 106931 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a9d9f053703d13d0f7f0a7b3bd3ff85127cd484 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0950a67b4d86d205b4e21f200ae82fde285fd99dce359aaa775c6bf4ebc57e08 +size 85953 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/43f7b6b61db9a2f3e3920740a9527d97_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/43f7b6b61db9a2f3e3920740a9527d97_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ae6f637b48449f3a19c06e2d432d96edd360b18 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/43f7b6b61db9a2f3e3920740a9527d97_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:585eeedeb3167f51fde77609388463a63064c33dc025d787dea6ffef21a1e015 +size 80682 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e31c88f216b84c4d03872f8e66c6d5d432b0397 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de1f29194cf21a0e4d530c43d8cdbbc9682626ec73fcced62724be90f182a209 +size 84964 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7969088361cdcd917f228e9835e690c30d4a72f --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9324ab08e1dd365d2d6e2a960618b3fcf342caf5a680da0aca255cd75fc69f68 +size 162730 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c140e0edc0119c7459b2d51224708630e836582 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13d6f8bb42737ab7d44f7f2c1a099b75fa6dfbd3c432ceddb61ce44cc5188b2b +size 126319 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49c935e9e59d0aedb0d30151b58906f043e1c1ba --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7d820cbddaf104b5d5951c8b28ccd5b779fb7555a0e6d1b050417798a022831 +size 9785 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..826fb0ced5480dfb2f98d6062a9fc6acee0322ce --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ba999546944dddb2a8dae7de8a72443ed663430a49ab99c5299cbf61eb311cd +size 64925 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4af0b353c75b7e2e9f65ddcc6866a56299337147 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c5ca74d3c9cec41607738c6a4bea39e54bca74550ec1cf81596a447dea1994d +size 91907 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47e646946409704ce19ad82038cd6d339df3f2e6 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07673bad3fce42f063070b3505ffd877d74fecfce842f602a56dc455dd5862e2 +size 85597 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/69d00e8adf9811292427fb2ce6712e39_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/69d00e8adf9811292427fb2ce6712e39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a166a2ad829381bb8f816ac50d76dd0a4e50a7 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/69d00e8adf9811292427fb2ce6712e39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6353ec92da7326672d8df52669d4029ebb44afcfb31a1cda627a37dc8368fad +size 137355 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..668514b74fb6bacceb176786700d4d95cabb77f1 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f4006c3d33ebf1681fb78f4bb7ee363018e2b0a4d5a3afc46476c3659648d09 +size 105478 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36420dc78eadfc29edf1cd88a7c6c33c8f4eff6a --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:577d3338e4e1d2ef8567d5ae9a07ec2b4d9b5e4cac3db0f5c70534806cb7e0aa +size 89745 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19c2d4ace9e33020af2860bbc41fe94fb190a04c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b54033e56aad311f6b42a7a8d8f9b0a99ff794b9a9e80f89f5c68dce2e2d6c +size 64878 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f39336ad9baeec776579fcf1c6b60edde1a6b8bd --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4d747498df8cbfdfd13cde307b20e222abc85cbb844e12aae1fe113247ebd65 +size 46565 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2781031d9da6cf777c2c6dc8da1eb7e285712eef --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a84ad4396106ce95f37077296666e23095757d3ba1303ac29e1e18c2c8b9184 +size 114842 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b408e4d0a306fd99d3e979f6ee36577d8bd4f48 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4571b7677a113dd7f3618c8ffe873c669169320d2475c4a1c6b420fc5707a830 +size 100833 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9819eba3403fa21a23ca640e480136362f4e17d5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:551195d927778e59f6a8139285ff44fdc02b7bba866eab0401e00a8ff6441cce +size 90217 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75cff665b586439e5c7cd7087356fca0770635ec --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f9d9ee61b8f6aefe888ec93d914b0610e48eb9ef0b117159a00553f2f743cbb +size 92195 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82d73705a506af961f4e0067a439bf970c44f5db --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcd0c55e5145dea356ee93a2a3b3c00420b94c2299c9cbda8b3638b9f3643b25 +size 94700 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8327f2fc29207dd0c03bc5f570b8f463728ebec1 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d45562a49d5066f422a71980c9151ffa66de4b48ddc54ee501d22357d997846d +size 78428 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1aa22d5cd453d015584aafe321835269f33668a --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14438bea405184cac35dbb116d2fed3db9f1175c36e0d7104a2b2b3e845e2eaf +size 69716 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/92e26d86c5a582766cb9afdbd2c1aee7_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/92e26d86c5a582766cb9afdbd2c1aee7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1178c7677972c9c243500fdf83e208cab121fc7 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/92e26d86c5a582766cb9afdbd2c1aee7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ebfc70a816152efac3978babf35be973d45683ff126b065de206e8b6aa861ee +size 114486 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/95be50ec094942200786128aa936cfae_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/95be50ec094942200786128aa936cfae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d147c65d4ed8fc8b1422da5a9455073e0aa581bb --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/95be50ec094942200786128aa936cfae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6c2d0b7c270fe4ed931ca6d955b5b1657fb00227d74e121c0191b5a7601827 +size 103007 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b4cc0b977d92233b351ae62c197e1d496e8a1f9 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e05efbd81a71b1763a60518399be5a2d7051171aa23fab4e3bb314db2f9fa75 +size 138658 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d641e8df7140aeca05af695ae7c72035283fe5f --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4878abc24bd49df4d5afb5ccf45e33effd7b8b8a209ccef6f3c654838c22bfa9 +size 76991 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f00870493775100cc9ae32133685f61fd5d4f09f --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc9f632cf6bb580347abbc917c878d8543776ab34e039bd4db3fc407396e4fc +size 85808 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad83db07d1b07efaabbb65ea78d8bc637d3299be --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9d47fe89bc71acebde670ea760ee6ffb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:857e7304563c55ceb0147e6c5230afd9fd18133374094b9c3a5fd593d89ab154 +size 129159 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0999b10481f41a81649c27be7a4bb10a523e67b --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c95f996a075b59e8faeeb66aeb74391cec8713e178d4e8d48ad2d58d61cbc9d0 +size 108062 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..048d67ceb5bf0e98e4c9c1f20f74614ff882a807 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdc873bd73ba79403f7b4062e219397b64653f7efe38b9649dd58a6a0fd4e8f6 +size 49610 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f5987b8d82206705722e14dc24f9bcea1bc12eb --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dea1c475783304a96c03769ba7af9476203e1a838978f84b005895686eac1a4e +size 117287 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..442edadb7900fca2cfa3935d1b993fc3dbf0b928 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d11de83c388595641fa9bbb5c59c33eaa65ed8a36f1ae7c57d8256e34a249b8a +size 50064 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4470449970fc7c655f0d3522300f20d749d0adc5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d82840edceb58903e509909be91261781f6928cc785da5d2466eb1c3576f4ba5 +size 99946 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0facc4208b2ce1c4fcfa1403244e24d2d51f694 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a16a26fd6acdc541fc56214c6865c3190455a176a8c8f1429fff44529d4ec78 +size 115202 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a98f3ef00da8508d2468334c6867f90f_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a98f3ef00da8508d2468334c6867f90f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f866e240fbbf733d8d59888c6b8aae38c94ad1 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/a98f3ef00da8508d2468334c6867f90f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68255b5870519a0d1ae54e2d1b011b22c835372357352f7d671dd54c587cb1a5 +size 173795 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c0db2dfb3e938c68acafafac85e130f647d0a5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aed79d181db67b606deeabe8c78a7141663c1d6b3d988931f7ea04709e12d0c5 +size 85966 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a1f23a883dc6e639ffa72a93a58e0c09f6460ab --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:356ccc3f3391346a12805152c0d74fd22bc7df27c31a4b8557907099400690b6 +size 95173 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18dd2a5084d2daf8e18c4f900e2707899f80321b --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b004786d5cf0f3ec0dc085f126c0f7cb7222e0c314cda2820cad72f76c52c860 +size 27187 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c0725bd91b769b9c4ebc3fbd8d59042789f6f37 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20d403571d497523aac6ea288b2b679daaa989eb9acd7b4b6ba4443a62fa50db +size 115911 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9868d515e0b269509fa71c15c373baf404d1d92 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:600f169a5c0656bbf4b8b0421aa5deec75be6762172488a20ab911c737aa65f6 +size 87632 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31b8a757ca620b95a001acfec581063af4416642 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc212aac514de4835fcd981160a33f4ef8be06cfccb4e3a85da46e63e1f8a68c +size 108251 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8283e84bea96b16be1e9935e23190f9bd1336959 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87f0b86ea417169f850d0bd46daf51f5293aa9e524fc2e9024994eca847e872d +size 119049 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b99ddca16383b6f00fc70050d695a235_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b99ddca16383b6f00fc70050d695a235_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35dd5088edbd09e42a60074474bd80ae710ce37a --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/b99ddca16383b6f00fc70050d695a235_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b8953c9b3cd07f03820104c22f3306bfc5b89cdac1f555edc129a437317dfaa +size 154468 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d40b8d6038c913ac97498192d0790ae28a524a5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba5c5525472b66e2b94a263cb406ac7d8b944d3c72ef1149df01462199af8212 +size 13099 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fbdfee9a800fa3c72f4ca4dd40def8e31fdf8b5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b9a01ee92210ff27db917239bd8b12956ba2a4c04bcb8bd730e826ebf719301 +size 143218 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d78e4bcba8aa13819d0f611169abf22cea6b27a5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7e6d8c60bf30f4bdf6d6dace5fd158f175af5521fb44897904baa9f19171ba8 +size 85675 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c355b8056bdd4728357d7d5ed18792ca_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c355b8056bdd4728357d7d5ed18792ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37d521eac4b8d7af9f84cbe5bf2eca46aca3bd08 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c355b8056bdd4728357d7d5ed18792ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75554541b6943e482096c39b5710003cbc878538477040a6f6adafa25d3d75ad +size 179411 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e36733099d970404eb775ed2a73140a2de0d318e --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6834466bb5c055b0bf266a1eb26e3a65afdd23d81f2f7b9043fb601283608b93 +size 93172 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c30d14dccddeb2f58ec0c8e6915868626c7f793f --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54ba7fc6695c53e0a4a4795b8a5300e5040184d558a033cc3cfbc677cd030e87 +size 33321 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dab41d3450fcbc7c816f006c4836e18560c4a6a --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1d975b760271363a2d557752152fc78feee40665c30451c846d7d3e6348334b +size 96828 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14f4f2d4c0df9745713fd2a56520d248f81aeaf5 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f7792fc7b4bb02a15ef85e1e5c5a40c36a9765cd74ea8c0e414bfd13d331b39 +size 64044 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/cc91bf9aed46f8b219ebceaee276d195_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/cc91bf9aed46f8b219ebceaee276d195_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e46103c329edcd13a2c5187759e9fbc9d359b5e7 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/cc91bf9aed46f8b219ebceaee276d195_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad6576e477fd9257d8756bc33d0eb53a130602d600974c09a12f66ec9994362f +size 103392 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dadda3babcd77864f09121a0ba72704ec5b757b --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5c78280ea3371c7d3e88e7e518d11efcffc5b76f7f7dfd3fa15a41233c3b6f8 +size 102377 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f44ec700355c07aae038b49c3d84de03e18624dd --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bcd936bb2840a9b21cf863a6f349cc4d787d0cc2ecbfc049d8f4169fb76f1e0 +size 83004 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd201a8cf7212ae4262f33ab7d0a57a8b920d1bf --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ec3aef552461b0bf69d1a026826d429076f18eb695a5d6350cc0dafc2cb63e6 +size 84167 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df4c50c31e74cdd1c87e3fc45945792073648f9c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e831774635b1ca8031fc7d7c3eddde62ab86d723a4bef5bfe7bb778d6acef2e3 +size 47300 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d2bc1cba85f328264c2ce310139606b70835ba6 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38e7963ea2a4534eaecf21bf3440428a8c97bbe48d006421575d5601b4245e3c +size 103236 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..493bb190770fedfbcf0c7715f238406ee8f786e0 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bbf73b45c798540f92d2a483f35fbe434a8a7884767ed7cfc4b6c39aee52530 +size 100156 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e47d450f315d0b633906c03cc91f90ef_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e47d450f315d0b633906c03cc91f90ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67360803c59bec0eee8600c9f119bb42f8a25763 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e47d450f315d0b633906c03cc91f90ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edb7e68f32b5d38271d50c10e4ddef3c82aa9446ffb41058e3e8869692033421 +size 67566 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05fbf860e18f910e2535ed6f06a324c0396f227b --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10f58ddc792eb02f68dcb42707ca3026611a0316fc770e5007039a6ec72f7796 +size 102074 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5743fddf0dd40beea02454e224e199cf0057784d --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87e0e238639f4d4ce4a693635bd9eb82887c3acd62ef28a2046c4da756d42cbd +size 54762 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e6dd03518dd0d86b0745aafcd4c6f348a48219c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04bb931f05efc9a8b8c6aede4545c96f677cda4e51c1fcec1e1ea2833ec947da +size 91121 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/eca6a6c6546af8ac124c207445901964_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/eca6a6c6546af8ac124c207445901964_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..818e68a8089abda8e7faa0ddf5aadb3b19dbdf6e --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/eca6a6c6546af8ac124c207445901964_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1981ca6816aa55dc17286a4f95a802540095fe7f43c335404df887a0fb4ebb7 +size 152649 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab5e354224cdd5b73fb621f45e8ee9f6f0bcd606 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1abddf6431a633c3f9e317297329b9038a32ecf79a08512b488cc0df0dc3503 +size 113177 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6962b43ef7710e121d8d06e3eb050ab2130e26af --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0502f435125092a3f231558c071f71ce59d62716d5e70a4d4b614b2828c2a25f +size 86038 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c40214086a419693869a451670c0770629c352c --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6855b1604e8b777792ea7332711dec6b7fbc44a37fd8021872c45991204b6ebb +size 109896 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..118250cef5cfc54bd4a989b5da01918789b268de --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4e314f1d7085c6b3d8c27f8703469798e8d8153019192ad7a3d71e9c0553114 +size 61015 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51df37c761bbfbe79057f7225587ba231a8e2711 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a34cb5a6a37a32c6284c3ca7c8c43d451f14bd5f8adb28d498a068b0d26dc28d +size 91736 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..231a81767860488c0a16d3174952738a2594db30 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f3270568998ef8433534330863678f315a06e3c1e0f24a646e1cddec0fd5b5d +size 87161 diff --git a/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..42fbf2d5ee5d1e689b3d7ebc3e9d8cdf5f582857 --- /dev/null +++ b/marked/Q/T-REC-Q.834.3-200406-I_PDF-E/raw.md @@ -0,0 +1,8149 @@ + + +I n t e r n a t i o n a l   T e l e c o m m u n i c a t i o n   U n i o n + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.834.3 + +(06/2004) + +SERIES Q: SWITCHING AND SIGNALLING + +Q3 interface + +# --- **A UML description for management interface requirements for Broadband Passive Optical Networks** + +ITU-T Recommendation Q.834.3 + +## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation Q.834.3** + +# **A UML description for management interface requirements for Broadband Passive Optical Networks** + +## **Summary** + +This Recommendation provides a UML description for the management interface between a supplier management system and an operator management system. This work defines part of the management aspects for network resources defined by the G.983-series of Recommendations for Broadband Passive Optical Network (BPON) equipment. + +Generally speaking, the supplier management system is an element management system (EMS) and the operator management system is a network management system (NMS). However, the supplier management system is required to present a "network view" of connection management to the operator management system. Therefore, it was deemed necessary for the sake of clarity to use the terminology adopted in naming the systems involved. + +## **Source** + +ITU-T Recommendation Q.834.3 was approved on 13 June 2004 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +APON, BPON, UML. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined in [ITU-T M.3010] ..... | 2 | +| 3.2 Terms defined in [b-OMG 99-06-01]..... | 2 | +| 3.3 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations and acronyms ..... | 4 | +| 5 Conventions ..... | 5 | +| 6 GDMI template..... | 6 | +| 6.1 Scope ..... | 6 | +| 6.2 Requirements..... | 7 | +| 6.3 Analysis ..... | 45 | +| Appendix I – Additional UML diagrams ..... | 144 | +| I.1 Process incoming NE events and log event records ..... | 144 | +| I.2 Root cause alarm analysis ..... | 146 | +| I.3 Autodiscover NEs and plug-in units..... | 148 | +| I.4 Collect history data..... | 152 | +| Appendix II – High level summary class diagrams ..... | 154 | +| II.1 Event handling..... | 154 | +| II.2 Software and configuration data management ..... | 156 | +| II.3 Installation ..... | 157 | +| II.4 Provisioning..... | 158 | +| II.5 Archiving and bulk transfer ..... | 159 | +| Bibliography..... | 160 | + + + +# ITU-T Recommendation Q.834.3 + +# A UML description for management interface requirements for Broadband Passive Optical Networks + +# 1 Scope + +This Recommendation provides a UML description of a management interface between a supplier management system, provided to manage network resources conforming to specifications found in the G.983-series of Recommendations, and a network owner operation management system. It follows the process proposed in ITU-T Rec. M.3020 with alternations in order of presentation of material. Behaviour for real time and non-real time interfacing is addressed. All aspects of TMN management functional areas are addressed except for accounting management since usage data collection is outside the scope of the BPON equipment reference architecture. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.983.1] ITU-T Recommendation G.983.1 (1998), *Broadband optical access systems based on Passive Optical Networks (PON)*. +- [ITU-T G.983.2] ITU-T Recommendation G.983.2 (2002), *ONT management and control interface specification for B-PON*. +- [ITU-T G.983.3] ITU-T Recommendation G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation*. +- [ITU-T G.983.4] ITU-T Recommendation G.983.4 (2001), *A broadband optical access system with increased service capability using dynamic bandwidth assignment*. +- [ITU-T G.983.5] ITU-T Recommendation G.983.5 (2002), *A broadband optical access system with enhanced survivability*. +- [ITU-T G.983.6] ITU-T Recommendation G.983.6 (2002), *ONT management and control interface specifications for B-PON system with protection features*. +- [ITU-T G.983.7] ITU-T Recommendation G.983.7 (2001), *ONT management and control interface specification for Dynamic Bandwidth Assignment (DBA) B-PON system*. +- [ITU-T M.2140] ITU-T Recommendation M.2140 (2000), *Transport network event correlation*. +- [ITU-T M.3010] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3200] ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. +- [ITU-T M.3400] ITU-T Recommendation M.3400 (2000), *TMN management functions*. +- [ITU-T Q.816.1] ITU-T Recommendation Q.816.1 (2001), *CORBA-based TMN services: Extensions to support coarse-grained interfaces*. + +- [ITU-T Q.834.1] ITU-T Recommendation Q.834.1 (2004), *ATM-PON requirements and managed entities for the network and network element view.* +- [ITU-T Q.834.2] ITU-T Recommendation Q.834.2 (2001), *ATM-PON requirements and managed entities for the network view.* +- [ITU-T X.720] ITU-T Recommendation X.720 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Management information model.* +- [ITU-T X.722] ITU-T Recommendation X.722 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects.* +- [ITU-T X.734] ITU-T Recommendation X.734 (1992), *Information technology – Open Systems Interconnection – Systems Management: Event report management function.* +- [ITU-T X.735] ITU-T Recommendation X.735 (1992), *Information technology – Open Systems Interconnection – Systems Management: Log control function.* +- [ITU-T X.741] ITU-T Recommendation X.741 (1995), *Information technology – Open Systems Interconnection – Systems Management: Objects and attributes for access control.* +- [ITU-T X.744] ITU-T Recommendation X.744 (1996), *Information technology – Open Systems Interconnection – Systems Management: Software management function.* +- [ITU-T X.745] ITU-T Recommendation X.745 (1993), *Information technology – Open Systems Interconnection – Systems Management: Test management function.* +- [ITU-T X.746] ITU-T Recommendation X.746 (2000), *Information technology – Open Systems Interconnection – Systems Management: Scheduling function.* +- [ITU-T X.780.1] ITU-T Recommendation X.780.1 (2001), *TMN guidelines for defining coarse-grained CORBA managed object interfaces.* + +# 3 Definitions + +This Recommendation uses the following terms: + +## 3.1 Terms defined in [ITU-T M.3010] + +- user +- TMN management service +- TMN management function set + +## 3.2 Terms defined in [b-OMG 99-06-01] + +- activity diagram +- actor +- class +- class diagram +- collaboration diagram +- sequence diagram +- state diagram + +- stereotype +- use case + +## 3.3 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.3.1 activate:** Execute installed software. Normally implies the switch of installed software from being secondary to primary. + +**3.3.2 assign:** The outcome of service provisioning. + +**3.3.3 autodiscovery:** The autonomous messaging to an OMS of creation or deletion notifications for equipment inventory data. + +**3.3.4 BPON resource:** BPON network resources that need to be managed. These resources can be physical and logical. + +**3.3.5 build:** The construction of a fragment of a management model based on containment rules and defined relationships, i.e., the provisioning of the parameters of a BPON managed resource, resulting from a discovery or autodiscovery process of installed equipment or through a pre-provisioning process prior to physical installation. + +**3.3.6 data warehouse:** Long-term archival system, normally implemented as a database management system. + +**3.3.7 dispatch:** To send personnel to a particular location where telecommunications equipment or facilities are or will be installed. + +**3.3.8 factory:** Functionality that manufactures and deletes managed entities. + +**3.3.9 filtering:** Criteria used for selection purposes. + +**3.3.10 includes:** An include relationship from use case A to use case B indicates that an instance of the use case A will also contain the behaviour as specified by use case B (see [ITU-T M.3400]). + +**3.3.11 install:** Physical placement of equipment. This means that shelves have been installed and powered. All common equipment is inserted. Management communication has been established. Interface cards may be inserted. + +**3.3.12 management model:** Formal description of managed entities and relationships between them. + +**3.3.13 range:** Ranging is a function used to measure the round-trip delay between the OLT and each ONU or ONT in order to determine the transmission timing for the subtending ONT or ONU. The process also involves establishing of security mechanisms (churning key algorithm) and the embedded operations channel. Ranging may be initiated manually by supplying the OLT with the serial number of the ONT or ONU. If supported by the implementation, ranging can also be initiated automatically by the OLT. + +**3.3.14 register:** The process used to bring a network resource into the management jurisdiction of the supplier management system. The management communication link is established to a physically installed NE, and the NE is included in the management domain for the supplier management system. + +**3.3.15 reserve:** The setting aside of network resources before provisioning of service. + +**3.3.16 service instance:** A service instance is a connection between a UNI endpoint on an ONT or NT and an NNI endpoint at an OLT, or between UNI endpoints on two ONTs or NTs. + +**3.3.17 transfer function:** This function implies the use of a non-real time protocol. + +**3.3.18 user label:** Indicates an identifier that is created and provided by the operator or operator management system to associate with a managed resource by the supplier management system. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|---------------------------------------------------------| +| AAL | ATM Adaptation Layer | +| APON | ATM Passive Optical Network | +| ATM | Asynchronous Transfer Mode | +| BICI | Broadband Inter-Carrier Interface | +| BISSI | Broadband Inter-Switching System Interface | +| BPON | Broadband Passive Optical Network | +| CAC | Call Admission Control | +| CES | Circuit Emulation Service | +| CORBA | Common Object Request Broker Architecture | +| CTP | Connection Termination Point | +| DCN | Data Communications Network | +| DSx | Digital Signal x | +| EM-OSF | Element Management Layer Operations System Function | +| EMS | Element Management System | +| EOC | Embedded Operations Channel | +| Ex | European digital signal x | +| FSAN | Full Service Access Network | +| GDMI | Guidelines for the Definition of Management Information | +| GUI | Graphical User Interface | +| IP | Internet Protocol | +| ME | Managed Entity | +| MIB | Management Information Base | +| NE | Network Element | +| NM-OSF | Network Management layer Operations System Function | +| NMS | Network Management System | +| NT | Network Terminal | +| ODN | Optical Distribution Network | +| OLT | Optical Line Terminal | +| OMG | Object Management Group | +| OMS | Operator Management System | +| ONT | Optical Network Terminal | +| ONU | Optical Network Unit | + +| | | +|--------|-----------------------------------------------------| +| OS | Operations System | +| OSF | Operations System Function | +| PON | Passive Optical Network | +| PVC | Permanent Virtual Circuit | +| QoS | Quality of Service | +| RCAA | Root Cause Alarm Analysis | +| RCIA | Root Cause Impairment Analysis | +| SM-OSF | Service Management layer Operations System Function | +| TCA | Threshold Crossing Alert | +| TMN | Telecommunication Management Network | +| TP | Termination Point | +| TTP | Trail Termination Point | +| UML | Unified Modelling Language | +| UNI | User Network Interface | +| VC | Virtual Channel | +| VCC | Virtual Channel Connection | +| VCI | Virtual Channel Identifier | +| VCL | Virtual channel link | +| VDSL | Very high speed Digital Subscriber Line | +| VP | Virtual Path | +| VPC | Virtual Path Connection | +| VPI | Virtual Path Identifier | +| VPL | Virtual Path Link | + +# 5 Conventions + +Any "communicates" association between an actor and use case in the requirements clause (see clause 6.2), refers to the Q interface addressed in this Recommendation when the actor is any one of the following: OMS, privileged user, external event channel, profile object repository, data warehouse or secure file server. Figure 5-1 illustrates this diagrammatic reference. + +![Figure 5-1: A UML diagram showing an actor (stick figure) connected to a use case (yellow oval) with the label 'communicates' above the association line. The actor is labeled 'Actor' and the use case is labeled 'Use Case Name'.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +graph LR + Actor[Actor] --- communicates[communicates] --- UseCase((Use Case Name)) + +``` + +Figure 5-1: A UML diagram showing an actor (stick figure) connected to a use case (yellow oval) with the label 'communicates' above the association line. The actor is labeled 'Actor' and the use case is labeled 'Use Case Name'. + +**Figure 5-1 – Q interface reference in use case diagram** + +Any association between an actor and an object class in the analysis clause (see clause 6.3) refers to the Q interface addressed in this Recommendation when the actor is any one of the following: OMS, privileged user, external event channel, profile object repository, data warehouse or secure file server. Figure 5-2 illustrates this diagrammatic reference. + +![UML class diagram showing an association between an Actor and a Class.](007b053fe94a8348f75128a584503fd0_img.jpg) + +The diagram shows a stick figure labeled 'Actor' with the text '(from Use Case View)' below it. A horizontal line connects the actor to a rectangular box labeled 'Class'. The line is labeled 'association name' above it. The 'Class' box has a header section with the word 'Class' and a body section below it. + +UML class diagram showing an association between an Actor and a Class. + +**Figure 5-2 – Q interface reference in class diagram** + +All other associations, as well as other object classes not possessing such an association to these actors in the analysis clause are provided in this clause in order to complete the description of expected behaviour of the supplier management system and the BPON NEs within its management jurisdiction when fulfilling the TMN management needs of the operator and operator management systems. In general, it is not required that the supplier management system explicitly implement these associations, or object classes, provided that the implementation possesses the same behaviour. However, when an object class appears in the Analysis clause, and this class is one of the managed entities of [ITU-T Q.834.1] or [ITU-T Q.834.2], the class shall be implemented within the supplier management system as part of its logical schema. In general, the managed entities of [ITU-T Q.834.1] and [ITU-T Q.834.2] provide management data that is present on the mechanized interface. + +# **6 GDMI template** + +## **6.1 Scope** + +The scope of this Recommendation includes management aspects for a BPON system as described by the G.983-series of Recommendations. The BPON system can be classified as an access and terminal equipment network [ITU-T G.983.1]. The management services covered by this Recommendation include aspects of network and service provisioning management, network performance management, traffic management, maintenance management and security administration. Figure 6-1 below shows the Q interface addressed in this Recommendation. + +![Figure 6-1 – Reference interface diagram showing a vertical hierarchy of three boxes. The top box is 'Operator Management System(s)'. A vertical line connects it to the middle box, 'BPON Supplier Management System (E-OSF, N-OSF, S-OSF)', with a horizontal tick mark and the letter 'Q' on the line. The middle box is connected to the bottom box, 'BPON Network Element(s)', by another vertical line.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +graph TD + A[Operator Management System(s)] ---|Q| B[BPON Supplier Management System +(E-OSF, N-OSF, S-OSF)] + B --- C[BPON Network Element(s)] + +``` + +Figure 6-1 – Reference interface diagram showing a vertical hierarchy of three boxes. The top box is 'Operator Management System(s)'. A vertical line connects it to the middle box, 'BPON Supplier Management System (E-OSF, N-OSF, S-OSF)', with a horizontal tick mark and the letter 'Q' on the line. The middle box is connected to the bottom box, 'BPON Network Element(s)', by another vertical line. + +**Figure 6-1 – Reference interface** + +## **6.2 Requirements** + +### **6.2.1 Business level requirements** + +Major business requirements concerning the functionality of the supplier management system are documented in [ITU-T Q.834.1]. Services performed by the supplier management system on behalf of the operator management system(s) and operator users are controlled by the interfaces supported by the supplier management and described by the requirements provided in [ITU-T Q.834.1]. + +#### **6.2.1.1 Actor roles** + +There are several actors mentioned in the high-level use case diagrams provided in clause 6.2.1.3. These actors include the following: operator, privileged user, operator management system (OMS), external event channel, white pages, data warehouse, BPON NE, profile object repository and secure file server. Figure 6-2 provides a brief definition of the roles that these actors play. + +| Actor | Roles | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Operator | User interacting with the supplier management system via a graphical user interface. | +| Privileged user | User with administrative access to the supplier management system. Can be a system or operator. | +| Operator management system (OMS) | Separate management systems supporting operator TMN management requirements. | +| External event channel | Consumer of BPON events supplied by the supplier management system. This channel acts as a conduit of event information to interested client applications. | +| White pages | Directory service for resolving names of objects referenced by interface method invocations. | +| Data warehouse | Long-term archive of records maintained by the operator. | +| BPON NE | Equipment that is a network element. | +| Profile object repository | External OMS where profile objects reside. | +| Secure file server | Secure and centralized repository of network element configuration data and software generics. | + +**Figure 6-2 – Actors and roles** + +#### 6.2.1.2 Telecommunications resources + +Figure 6-3 illustrates the BPON system architecture. The operation system linked to the OLT in this figure is the supplier management system. This system is provided, along with the equipment, to a network owner operator. There is no specification concerning the management communications interface between the OLT and the supplier management system. Consequently, both the supplier management system and the managed BPON equipment are viewed as relevant telecommunications resources in this Recommendation. + +The optical line terminal (OLT) is a head-end digital terminal commonly located in the central office or some controlled environment structure. The optical distribution network (ODN) is a point-to-multipoint fibre infrastructure employing a passive splitter or coupler device for the fan out. The ONU provides the access network line termination function and the ATM multiplexing and de-multiplexing function. The NT provides the user network interface line termination function. The reference point, indicated by the term UNI, denotes the user network interface. It is used in the most abstract sense and is meant to indicate any type of service interface. The ONT combines the functions of the ONU and NT in one piece of equipment. In some cases, the UNIs from one ONT may belong to different users. + +![Figure 6-3 – BPON system architecture diagram. The diagram shows a Supplier Management System (oval) connected to an OLT (rectangle) within a dashed box labeled 'EPON Network Elements'. The OLT is connected to an ODN (oval), which then branches to multiple ONUs (rectangles) and ONTs (rectangles). Each ONU is connected to an NT (rectangle), which is then connected to a UNI (rectangle). The OLT has external interfaces labeled EICI, EISI, and NNI. The ONT has a UNI interface. A legend below the diagram defines the abbreviations: EICI (Broadband Inter-Carrier Interface), EISI (Broadband Inter-Switching System Interface), EPON (Broadband Passive Optical Network), NNI (Network-to-Network Interface), NT (Network Terminal), OLT (Optical Line Terminal), ODN (Optical Distribution Network), ONT (Optical Network Terminal), ONU (Optical Network Unit), and UNI (User/Network Interface).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +| | | +|------|--------------------------------------------| +| EICI | Broadband Inter-Carrier Interface | +| EISI | Broadband Inter-Switching System Interface | +| EPON | Broadband Passive Optical Network | +| NNI | Network-to-Network Interface | +| NT | Network Terminal | +| OLT | Optical Line Terminal | +| ODN | Optical Distribution Network | +| ONT | Optical Network Terminal | +| ONU | Optical Network Unit | +| UNI | User/Network Interface | + +Figure 6-3 – BPON system architecture diagram. The diagram shows a Supplier Management System (oval) connected to an OLT (rectangle) within a dashed box labeled 'EPON Network Elements'. The OLT is connected to an ODN (oval), which then branches to multiple ONUs (rectangles) and ONTs (rectangles). Each ONU is connected to an NT (rectangle), which is then connected to a UNI (rectangle). The OLT has external interfaces labeled EICI, EISI, and NNI. The ONT has a UNI interface. A legend below the diagram defines the abbreviations: EICI (Broadband Inter-Carrier Interface), EISI (Broadband Inter-Switching System Interface), EPON (Broadband Passive Optical Network), NNI (Network-to-Network Interface), NT (Network Terminal), OLT (Optical Line Terminal), ODN (Optical Distribution Network), ONT (Optical Network Terminal), ONU (Optical Network Unit), and UNI (User/Network Interface). + +Figure 6-3 – BPON system architecture + +#### 6.2.1.3 High-level use case diagrams + +This clause contains high-level use case diagrams that summarize the functionality and interfaces of the supplier management system. Use cases are shown in these diagrams even when they do not have a "communicates" association to an external actor. The internal functionality described by these use cases serves an important purpose in that the behaviour of the supplier management system would be incompletely characterized without it. In some cases there are specific use cases mentioned on more than one high-level diagram. Again, the reason for this duplication is to aid in completing the characterization of behaviour and functionality. Use case descriptions are provided for every use case pictured in these high-level diagrams. + +The interfacing to BPON technology domain objects through a façade object or through a fine-grain mechanism is defined and described in ITU-T Rec. X.780 and [ITU-T X.780.1] with key services defined in ITU-T Rec. Q.816 and [ITU-T Q.816.1]. + +The first overview use case diagram shows the interactions involved administering user access to the supplier management system. + +![Use case diagram for access control showing a Privileged User communicating with Administer User Privileges.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +``` +graph LR; A[Privileged User] ---|communicates| B([Administer User Privileges]) +``` + +A use case diagram illustrating access control. It features a stick figure actor labeled "Privileged User" on the left and a yellow oval use case labeled "Administer User Privileges" on the right. A line connects them, with the label "communicates" written above the line. + +Use case diagram for access control showing a Privileged User communicating with Administer User Privileges. + +**Figure 6-4 – Access control** + +The second overview use case diagram shows the external interactions involved in event handling activities of the supplier management system. It includes both real time and non-real time activities. + +![Use case diagram for event handling showing interactions between BPON NE, External Event Channel, and OMS/Operator with various event processing use cases.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` +graph TD; A[BPON NE] ---|communicates| B([Process Incoming NE Events]); C[External Event Channel] ---|communicates| D([Publish Events]); E[Log Events]; F([Root Cause Alarm Analysis]); G([Root Cause Impairment Analysis]); H[OMS/Operator] ---|communicates| G +``` + +A use case diagram illustrating event handling activities. It includes several actors and use cases. On the left, a stick figure actor "BPON NE" is connected by a line labeled "communicates" to a yellow oval use case "Process Incoming NE Events". On the right, a stick figure actor "External Event Channel" is connected by a line labeled "communicates" to a yellow oval use case "Publish Events". Below these are two more yellow oval use cases: "Log Events" and "Root Cause Alarm Analysis". At the bottom left, a stick figure actor "OMS/Operator" is connected by a line labeled "communicates" to a yellow oval use case "Root Cause Impairment Analysis". + +Use case diagram for event handling showing interactions between BPON NE, External Event Channel, and OMS/Operator with various event processing use cases. + +**Figure 6-5 – Event handling** + +The third overview use case diagram covers the external interactions involving software and configuration data management by the supplier management system. + +![UML Use Case Diagram for Software and configuration data management](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +``` + + graph TD + SCS[Secure Config Server] + BPN[BPON NE] + S[Scheduler] + NSVC[NE Software Version Control] + BRNE[Backup and Restore NE] + OMS[OMS/Operator] + DASNE[Download and Activate NE Software] + + SCS ---|communicates| BPN + SCS ---|communicates| BRNE + BPN ---|communicates| S + BPN ---|communicates| BRNE + S ---|includes| BRNE + BRNE ---|communicates| OMS + OMS ---|communicates| NSVC + OMS ---|communicates| DASNE + NSVC ---|communicates| BRNE + DASNE ---|communicates| OMS + SCS ---|communicates| DASNE + +``` + +The diagram illustrates the interactions for software and configuration data management. It features several actors (stick figures) and use cases (ovals). The actors are Secure Config Server, BPON NE, Scheduler, Backup and Restore NE, OMS/Operator, and Download and Activate NE Software. The use cases are NE Software Version Control and Scheduler. The relationships are as follows: Secure Config Server communicates with BPON NE, Backup and Restore NE, and Download and Activate NE Software. BPON NE communicates with Scheduler and Backup and Restore NE. Scheduler includes Backup and Restore NE. Backup and Restore NE communicates with OMS/Operator. OMS/Operator communicates with NE Software Version Control, Download and Activate NE Software, and Backup and Restore NE. NE Software Version Control communicates with Backup and Restore NE. Download and Activate NE Software communicates with OMS/Operator. + +UML Use Case Diagram for Software and configuration data management + +**Figure 6-6 – Software and configuration data management1** + +1 Backup and restore NE use case only communicates with the actor Secure Config Server when the MIB data is stewarded by the EMS. + +The fourth overview use case diagram shows the interactions for testing functionality through the support of the supplier management system. + +![UML Use Case Diagram for Testing](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg) + +``` +graph TD + BPON_NE[BPON NE] ---|communicates| UC1(( )) + UC1 -->|includes| UC2(( )) + UC2 ---|communicates| UC3(( )) + UC3 ---|communicates| OMS_Operator[OMS/Operator] +``` + +The diagram is a UML Use Case Diagram illustrating the testing process. It features three use cases, each represented by a yellow oval, and two actors represented by stick figures. The actors are labeled 'BPON NE' and 'OMS/Operator'. The use cases are labeled 'Conduct Test, Report Results' and 'Scheduler'. The relationships are as follows: 'BPON NE' communicates with the first use case. The first use case includes the 'Scheduler' use case. The 'Scheduler' use case communicates with 'OMS/Operator'. Finally, the first use case also communicates directly with 'OMS/Operator'. + +UML Use Case Diagram for Testing + +**Figure 6-7 – Testing** + +The fifth overview use case diagram presents the internal functionality and external interactions of the supplier management system associated with the installation of BPON equipment. + +![UML Use Case Diagram for BPON Installation](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +``` + + usecaseDiagram + actor BPON_NE as BPON NE + actor Privileged_User as Privileged User + actor OMS_Operator as OMS/Operator + actor External_Event_Channel as External Event Channel + + usecase UC1[Process Incoming NE Events] + usecase UC2[Provide Current Event Listings] + usecase UC3[Synchronise NE] + usecase UC4[Register OLT] + usecase UC5[Range ONT or ONU] + usecase UC6[Autodiscover NEs and Plug-in Units] + usecase UC7[Publish Events] + usecase UC8[Scheduler] + + BPON_NE --> UC1 : communicates + BPON_NE --> UC2 : communicates + BPON_NE --> UC3 : communicates + BPON_NE --> UC4 : communicates + BPON_NE --> UC5 : communicates + BPON_NE --> UC6 : communicates + + Privileged_User --> UC2 : communicates + Privileged_User --> UC3 : includes + Privileged_User --> UC8 : communicates + + OMS_Operator --> UC4 : communicates + OMS_Operator --> UC5 : communicates + + External_Event_Channel --> UC7 : communicates + + UC3 --> UC2 : includes + UC3 --> UC8 : includes + UC6 --> UC7 : includes + +``` + +The diagram illustrates the internal functionality and external interactions of the supplier management system for BPON equipment installation. It features several actors and use cases connected by relationships. + +- Actors:** + - BPON NE:** The primary actor, represented by a stick figure, which communicates with multiple use cases. + - Privileged User:** Represented by a stick figure, interacting with 'Provide Current Event Listings', 'Synchronise NE', and 'Scheduler'. + - OMS/Operator:** Represented by a stick figure, interacting with 'Register OLT' and 'Range ONT or ONU'. + - External Event Channel:** Represented by a stick figure, interacting with 'Publish Events'. +- Use Cases (Yellow Ovals):** + - Process Incoming NE Events** + - Provide Current Event Listings** + - Synchronise NE** + - Register OLT** + - Range ONT or ONU** + - Autodiscover NEs and Plug-in Units** + - Publish Events** + - Scheduler** +- Relationships:** + - Communicates:** Indicated by solid lines with open arrowheads. BPON NE communicates with 'Process Incoming NE Events', 'Provide Current Event Listings', 'Synchronise NE', 'Register OLT', 'Range ONT or ONU', and 'Autodiscover NEs and Plug-in Units'. Privileged User communicates with 'Provide Current Event Listings', 'Scheduler', and 'Synchronise NE'. OMS/Operator communicates with 'Register OLT' and 'Range ONT or ONU'. External Event Channel communicates with 'Publish Events'. + - Includes:** Indicated by solid lines with hollow block arrowheads. 'Synchronise NE' includes 'Provide Current Event Listings' and 'Scheduler'. 'Autodiscover NEs and Plug-in Units' includes 'Publish Events'. + +UML Use Case Diagram for BPON Installation + +**Figure 6-8 – Installation** + +The sixth overview use case diagram presents the internal functionality and external interactions of the supplier management system associated with provisioning of BPON network elements and BPON services. + +![UML Use Case Diagram for Provisioning](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +``` + + usecaseDiagram + actor BPON_NE as BPON NE + actor OMS_Operator as OMS/Operator + actor Profile_Repository as Profile Object Repository + actor External_Channel as External Event Channel + + usecase Provision_Installed_NEs as Provision Installed NEs + usecase Synchronise_NE as Synchronise NE + usecase Build_Logical_Managed_Entities as Build Logical Managed Entities + usecase Provision_Service as Provision Service + usecase Reserve_Resources as Reserve Resources + usecase Manage_Profile_Objects as Manage Profile Objects + + BPON_NE -- communicates --> Provision_Installed_NEs + BPON_NE -- communicates --> Synchronise_NE + BPON_NE -- communicates --> Build_Logical_Managed_Entities + BPON_NE -- communicates --> Provision_Service + BPON_NE -- communicates --> Reserve_Resources + BPON_NE -- communicates --> Manage_Profile_Objects + + Provision_Installed_NEs -- includes --> Build_Logical_Managed_Entities + Synchronise_NE -- includes --> Build_Logical_Managed_Entities + + OMS_Operator -- communicates --> Provision_Installed_NEs + OMS_Operator -- communicates --> Build_Logical_Managed_Entities + OMS_Operator -- communicates --> Provision_Service + OMS_Operator -- communicates --> Reserve_Resources + OMS_Operator -- communicates --> Manage_Profile_Objects + + Profile_Repository -- communicates --> Provision_Service + Profile_Repository -- communicates --> Reserve_Resources + Profile_Repository -- communicates --> Manage_Profile_Objects + + External_Channel -- communicates --> Reserve_Resources + External_Channel -- communicates --> Manage_Profile_Objects + +``` + +The diagram illustrates the provisioning process for BPON network elements and services. It features several actors and use cases. The 'BPON NE' actor communicates with 'Provision Installed NEs', 'Synchronise NE', 'Build Logical Managed Entities', 'Provision Service', 'Reserve Resources', and 'Manage Profile Objects'. 'Provision Installed NEs' and 'Synchronise NE' both include 'Build Logical Managed Entities'. The 'OMS/Operator' actor communicates with 'Provision Installed NEs', 'Build Logical Managed Entities', 'Provision Service', 'Reserve Resources', and 'Manage Profile Objects'. The 'Profile Object Repository' actor communicates with 'Provision Service', 'Reserve Resources', and 'Manage Profile Objects'. Finally, the 'External Event Channel' actor communicates with 'Reserve Resources' and 'Manage Profile Objects'. + +UML Use Case Diagram for Provisioning + +**Figure 6-9 – Provisioning** + +The seventh and final overview use case diagram presents the external interactions of the supplier management system associated with collection of statistics and bulk transfer of large amounts of data stored in short-term archives within the supplier management system. + +![UML Use Case Diagram for Archiving and Bulk Transfer](83852ec55d4802521a727926336bedab_img.jpg) + +``` + + graph TD + BPON_NE[BPON NE] -- communicates --> Collect_NE[Collect NE Statistics] + Privileged_User[Privileged User] -- communicates --> Control_Archives[Control Archives] + Log_Events[Log Events] -- includes --> Collect_NE + Control_Archives -- includes --> View_Records[View Records] + View_Records -- includes --> Report_Outages[Report Service Outages] + Collect_NE -- includes --> Scheduler[Scheduler] + Performance_Traffic[Performance and Traffic Monitoring Reporting Control] -- communicates --> Scheduler + Scheduler -- communicates --> OMS_Operator[OMS/Operator] + OMS_Operator -- communicates --> Bulk_Transfer[Bulk Transfer] + Bulk_Transfer -- communicates --> Data_Warehouse[Data Warehouse] + +``` + +The diagram illustrates the external interactions of the supplier management system. It features several actors (stick figures) and use cases (ovals). The actors are BPON NE, Privileged User, OMS/Operator, and Data Warehouse. The use cases are Collect NE Statistics, Control Archives, Log Events, Performance and Traffic Monitoring Reporting Control, Scheduler, View Records, Report Service Outages, and Bulk Transfer. The relationships are as follows: BPON NE communicates with Collect NE Statistics; Privileged User communicates with Control Archives; Log Events includes Collect NE Statistics; Control Archives includes View Records; View Records includes Report Service Outages; Collect NE Statistics includes Scheduler; Performance and Traffic Monitoring Reporting Control communicates with Scheduler; Scheduler communicates with OMS/Operator; OMS/Operator communicates with Bulk Transfer; and Bulk Transfer communicates with Data Warehouse. + +UML Use Case Diagram for Archiving and Bulk Transfer + +**Figure 6-10 – Archiving and bulk transfer** + +### 6.2.2 Specification level requirements + +This clause contains textual details for each of the use cases shown in the high-level use case diagrams of the previous clause. The details are provided to clarify the roles of external actors and telecommunications resources, to establish the basis for interactive diagrams in the analysis clause, and to refine the previous high level use case diagrams to a specification level. Use case details include the following components: + +- Summary: Short summary of use case functionality referencing TMN functionality as needed. +- Assumptions: Listing of requirements surrounding the use case that would affect the design of the application code of the supplier management system. +- Actors: Actors are listed as shown in Figure 6-2 followed by parenthetical role characteristic as needed. +- Preconditions: Identifies the trigger for the use case commencement. + +- Description: Detailed textual rendition of the functionality of the use case including stops where exceptions can occur. +- Exceptions: Identifies unsuccessful completion circumstances for the use case. +- Post-conditions: Identifies the conditions that will hold if the use case ends successfully. + +The use case details are listed alphabetically by the use case title shown in the diagrams of the previous clause. + +#### 6.2.2.1 Administer user privileges + +**Summary:** This use case describes functionality for creating, deleting, assigning and using access control information for users of the supplier management system.2 + +**Assumptions:** Authentication is accomplished through use of an external authentication service for operator or OMS access and this function is outside the scope of the use case. The supplier management system has authenticated the requesting operator or OMS. Control of human user access to the supplier management system via the OMS is controlled by the OMS and is outside the scope of this use case. Access to the supplier management system via an OMS by any human user of the OMS is viewed to have the same privileges as the OMS. The supplier management system supports an administrative privileged user. Default logins and passwords have been provided to this user for initial login. Target activities are defined previously and known to the supplier management system. + +**Actors:** Privileged user. + +**Preconditions:** The supplier management system has been installed. Connectivity between the supplier management application, OMSs, and all required GUI client applications has been provided. + +**Description:** This use case begins when the supplier management system is first installed and the privileged user is required to establish access permission for any users of the supplier management system. The privileged user retrieves the default password policy of the supplier management system and determines whether or not to change the settings. If changes are needed, the privileged user makes them. Next, the privileged user checks the target activities and permission levels for any system-provided user group and determines whether or not these user groups will meet operational needs [unknown user group]. The privileged user will create new user groups if necessary based on this analysis [duplicate user group, unknown targets]. + +With a list of current operators in hand, the privileged user then creates new users and assigns them to user groups or establishes special target activities on an individual case basis [unknown user group, duplicate user Id, unknown targets, user login policy violation]. Settings for activity level for each activity for each user Id or group of users have values including "monitor only", "allowed to execute" or "no-access", to designate allowable operations on an individual activity basis. + +As operator assignments change, the privileged user maintains access control for these changes by any of the following means: + +- adding new operators to existing user groups [unknown user group]; +- retrieving the permission listing for any existing user [unknown user Id], and making modifications to the listing according to operational needs either through membership to different user groups or by individual assignment [unknown targets, unknown user Id, unknown user group]; +- deleting users who have left the company or whose assignments have changed so as to no longer require access to the supplier management system [unknown user Id]. + +--- + +2 This use case description makes use of management functionality described in [ITU-T X.741]. + +Additionally, as high-level network administrative changes occur, the privileged user can re-define the management scope of groups of users. The privileged user can examine existing operator assignments to specific user groups or can examine the access limitations established for the user group [unknown user group]. The privileged user can perform broad reassignments as well as make modifications to the access limitations defined. This includes adding, deleting or modifying the level of accessibility to any activity [unknown user group, duplicate user group, unknown targets]. It may also include the elimination of existing user groups [unknown user group, user group not empty]. + +Subsequently, operators attempting to log onto the supplier management system experience the following verification process. The access control manager of the supplier management system verifies the user Id and password of the operator and grants the operator GUI access to the functionality allowed in the permission list. At any time after establishing access permission levels, the user may forget their password. The user Id – password relationship can be re-established by the privileged user [user login policy violation, unknown user Id]. + +This use case ends when the privileged user has updated permissions as needed. + +**Exceptions:** Unknown user Id, unknown targets, duplicate user Id, unknown user group, duplicate user group, user group not empty. + +**Post-conditions:** Operator access to the supplier management system is restricted to the activities and items that are allowed by permission and privilege listings. As the supplier management system software is upgraded, operator access control settings are preserved. + +#### 6.2.2.2 Autodiscover NEs and plug-in units + +**Summary:** The supplier management system publishes changes in inventory management information to the operator or OMS. Changes in inventory management information are discovered by the supplier management system as a result of establishing management communications to an installed NE, or through the insertion or removal of a plug-in unit. + +**Assumptions:** Communications between the supplier management system and the OLT are in place. Inventory data modelled in the supplier management system for an NE (including contained equipment holders) and plug-in units may be overwritten based on discovered data. The "to be discovered" equipment is in a stable condition. Embedded NE software is able to detect actual plug-in units present and act accordingly (in the case of the ONT or ONU, this implies that the default setting for any slot must be "plug and play"). Inventory management data refers to the type of information normally tracked by a capital asset system concerning physically installed equipment. + +**Actors:** No external actors. + +**Preconditions:** An OLT is installed. + +**Description:** This use case begins when any one of the following events takes place: + +- an OLT is registered; +- an ONT or ONU is ranged; +- an NT is installed and connected to a port of the ONU; +- a plug-in unit is installed in or removed from a slot of an installed NE having an available management communications channel to the supplier management system. + +Registration of an OLT is an event triggering the synchronization of provisioned or modelled inventory management data for the OLT with the same inventory properties discovered through direct communications with the OLT. The supplier management system uses a set of managed entity creation records to format information about discovered properties of the OLT, the shelves contained within the OLT (equipmentHolderF), the slots within the shelves (equipmentHolderF), + +and the plug-in units inserted in the slots (plugInUnitF), including information concerning embedded software for the OLT or plug-in unit. + +The ranging of an ONU or ONT, whether on demand by the supplier management system or through the automatic ranging function described by [ITU-T G.983.1] for a newly installed ONT or ONU, is an event that also triggers the synchronization of provisioned or modelled inventory management data for the ONU or ONT with the same inventory properties discovered through direct communications with the ONU or ONT. The supplier management system uses a set of managed entity creation records to format information about discovered properties of the ONU or ONT, the shelves contained within the ONU or ONT (equipmentHolderF), the slots within the shelves (equipmentHolderF), the plug-in units inserted in the slots (plugInUnitF), and the embedded software for the ONU or ONT or of any plug-in unit present. + +If any port of the ONT is integrated to the ONT (meaning not the port of a plug-in unit), then this port relationship is known through recognition of the hardware version of the ONT. + +The installation of an NT with connection to a port on the ONU is an event that triggers the synchronization of provisioned or modelled inventory management data for the NT with the same inventory properties discovered through supplier management system discovery of this network element. The supplier management system uses a set of managed entity creation records to format information about the discovered properties of the NT, the slots of the NT if any (equipmentHolderF), and any plug-in units that may be inserted in the slots (plugInUnitF) including information concerning embedded software loads for the NT or plug-in units. + +The manipulation of a plug-in unit in a slot is an event that triggers either the formatting of a managed entity creation record for the plug-in unit in the case of insertion, or the formatting of a managed entity deletion record for the plug-in unit in the case of removal. Embedded software of the plug-in unit is also discovered. + +If any of these synchronization activities indicates a difference between what had been planned and what is actually present, then the supplier management system will form an alarm event record indicating the mismatch. + +This use case ends when the supplier management system formats the inventory change and/or provisioned versus installed alarm information into a form appropriate for publication to the external event channel. + +**Exceptions:** None specified since this use case does not describe an IF1 communications mechanism. + +**Post-conditions:** The newly discovered data is made available to the OMS and operators responsible for inventory management. + +#### 6.2.2.3 Backup and restore NE + +**Summary:** The supplier management system provides the operator with capabilities for backing up and subsequent restoring of BPON system configuration data in the case of catastrophic failure of the OLT. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. Stewardship of the OLT system MIB3 may be in the OLT, may be in the supplier management system or may be spread between the two. OLT system refers to the OLT and all its subtending BPON NEs. The OLT has the current copy of MIB data for its subtending BPON NEs. When required, the restoring of system configuration data to the OLT and its return to normal functioning + +--- + +3 Here system MIB (or Management Information Base) is used generally to mean all configuration data held within the system. + +must be accomplished as soon as possible. Backup versions of the OLT system MIB information are available on a secure file server. + +Before the restore or backup processes can start, DCN communications between the OLT and supplier management system and between the OLT and the secure file server must be available. Before the restore process begins, the OLT equipment must be repaired. + +**Actors:** Operator, OMS, BPON NE (OLT), secure file server. + +**Preconditions:** The BPON OLT is installed, registered and not experiencing a catastrophic failure. + +**Description:** This user case begins when an operator or OMS wishes to establish the routine backup of system configuration data found in a newly installed BPON system. The operator or OMS formulates a request that identifies the OLT system, provides the DCN address for the destination server and user Id and password to access the destination server, gives the full directory location for the backup file and a flag indicates whether the backup should overwrite the existing file or not, and specifies a schedule to be followed when backing up the configuration data [unknown destination server, unknown scheduler, invalid scheduler, unknown NE]. + +The supplier management system returns a tracking object Id to the request that can be used to cancel, abort, monitor the progress of, or change the schedule for, the back up activities [unknown backup process, unknown scheduler, invalid scheduler, comm failure, equipment failure]. Subsequently, the scheduling utility launches the actual backup activity according to a time trigger. + +The master of the OLT system MIB data may be the supplier management system, may be the OLT, or the responsibility may be shared between the two. As a result, OLT system MIB data may have to be uploaded from several locations at the same time. If the information comes from two locations (OLT and supplier management system) the backup data must be held in the same destination server directory. + +The server retains multiple versions of backup data. If need be, this server uses tape device backup itself to archive sufficient versions for operator requirements of security and reliability. The supplier management system maintains a log of successful and unsuccessful backups. + +Occasionally, due to DCN communications failures, NE software upgrade safeguards or other factors, it may be necessary to request a backup on-demand. In this case, the OMS or operator formulates a backup request specifying the OLT, the DCN address for the destination server, the user Id and password to access the destination server, the full directory location for the backup file and a flag indicates whether the backup should overwrite the existing file [unknown destination server, comm failure, equipment failure, unknown NE]. + +If an OLT needs to be restored, maintenance activities may be required (including replacement of plug-in units) before the operator can request a restore of the OLT system. The operator accesses the log of successful uploads and chooses a version to use to restore the OLT. The operator forms a restore request. This request includes the identity of the OLT and the version of archived MIB data to be used, as well as the location of the archived file and user Id and password for supplier management system access to the archived file. The operator may also let the supplier management system make the "best possible" version choice. + +The supplier management system checks the requested version against current equipment and software versions and determines if the version can be downloaded for the purposes of restoring the NE [software load hardware mismatch, unknown NE, denied access, unknown source file, unknown source server, comm failure, equipment failure]. In the case that the OLT is the master of the data, the supplier management system causes the OLT to pull the correct MIB version from the server. In the case that the supplier management system is the master of the data, the supplier management system pulls the version of MIB data from the server. In both cases, the configuration data eventually is downloaded and installed in the OLT. + +The operator may monitor the progress of the restore activity [unknown restore process]. The operator may also view the final disposition of the activity by examining a log reporting on the success or failure of the restore process. + +The use case ends when the restored OLT establishes management communication with the supplier management system. + +**Exceptions:** Unknown NE, software load hardware mismatch, unknown destination server, unknown scheduler, comm failure, equipment failure, unknown backup process, unknown restore process, unknown source server, unknown source file. + +**Post-conditions:** The successful download of MIB data triggers an NE synchronization process between the NE and the supplier management system. + +#### **6.2.2.4 Build logical managed entities** + +**Summary:** The supplier management system builds and/or modifies management model groupings for planned or installed BPON equipment on request of an OMS or operator, or builds management model groupings as a result of discovery. The constructed resources (consisting potentially of many managed entities) include but are not limited to NEs, plug-in units and logical resources such as TCONTs and MACBridges. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The OLT must be registered with the supplier management system if discovery triggers this use case. If the OLT is already registered, the DCN connection between the supplier management system and the OLT must be available to build subtending managed entities. The DCN connection between the supplier management system and the operator or provisioning OMS is available. The supplier management system is responsible for providing unique identifiers for managed entities that are contained within the context of an OLT system that are created by execution of this use case. As result of some external process outside the scope of this use case, the OMS or operator will have knowledge of the equipment hierarchy and naming conventions of the supplier management system. + +**Actors:** OMS, operator. + +**Preconditions:** The supplier management system is installed. + +**Description:** This use case begins when the operator plans for the installation of all or part of the BPON equipment, needs to modify parameters that have been automatically applied to newly installed BPON equipment, or needs to provision infrastructure aspects of BPON equipment that are not automatically established by installation of the equipment. + +When the operator plans for the installation of an NE, the operator or OMS formulates a request identifying the type of node, indicating versions of hardware and software, providing various configuration profiles to be associated with the node, and supplying several operator labels. A similar request is formulated for construction of plug-in units that also includes slot assignment [unrecognized version, invalid serial num syntax, duplicate serial number, unknown profiles, parameter violation, unknown managed entity, duplicate user label, invalid external time, unknown system timing source, profile suspended, unknown NE, invalid equipment code, slot already assigned, unknown slot, invalid slot assignment list]. + +The build process within the supplier management system follows containment relationships and other obvious restrictions (e.g., a plug-in unit is not built until the containing node has been constructed, or a protection grouping of ports is not built until the ports exist, or the construction of a subtending ONT or ONU is not possible unless the serving PON interface card port on the OLT exists). The construction of all managed entities within the supplier management system that is the consequence of a single request follows the schema for configuration managed entities described in [ITU-T Q.834.1]. The supplier management system follows the equipment hierarchy rules for the + +supplier's equipment, assigning identifiers to the managed entities it builds. The supplier management system returns with a unique identifier for the constructed item. + +The operator proceeds with provisioning activities such as modifications to port attributes, construction of protection groupings of ports, construction of MACBridges (if required), and construction of TCONTs. In each case, a request is formulated that identifies previously built managed entities, supplying configuration profiles and parameters, providing operator labels and, in some cases providing some control logic [unknown NE, insufficient PON BW, unsupported TCONT type, duplicate user label, unknown managed entity, unknown profiles, parameter violation, profile suspended, invalid protection scheme, interface speed not changeable]. As before, the logical schema for configuration managed entities described in [ITU-T Q.834.1] is followed. These activities can occur before or after the equipment is installed. The provisioning request results in configuration changes in any installed NE. The supplier management system returns with a unique identifier for any constructed item. + +If NEs and plug-in units are installed prior to operator or OMS provisioning activities, then the supplier management system shall support the augmentation of discovered equipment configuration information with profile assignments and user label assignments. In this case, the operator or OMS will formulate configuration requests identifying managed entities whose existence and identity have been provided to the OMS through installation notification reports, supplying configuration profiles and parameters, providing operator labels and, in some cases, providing some control logic [unknown NE, insufficient PON BW, unsupported TCONT type, duplicate user label, unknown managed entity, unknown profiles, parameter violation, profile suspended, invalid protection scheme, interface speed not changeable, invalid slot assignment list, invalid external time]. As before, the logical schema for configuration managed entities described in [ITU-T Q.834.1] is followed. The provisioning request results in configuration changes in the installed NE. + +Eventually it may become necessary to remove a BPON network resource. In this case, the operator or OMS requests that the administrative state of the resource be locked and then that it be deleted [unknown NE, remaining contained managed entities, remaining reservations, remaining subnetwork connections, unknown managed entity]. + +This use case ends when infrastructure provisioning information has been successfully conveyed to the supplier management system and transfer to any pertinent installed BPON NE. + +**Exceptions:** Unknown managed entity, unknown NE, unknown system timing source, unknown profiles, unknown slot, unrecognized version, remaining contained managed entities, remaining reservations, remaining subnetwork connections, duplicate user label, duplicate serial number, invalid parameter value, invalid slot assignment list, invalid external time, invalid equipment code, invalid user label syntax, invalid protection scheme, profile suspended, invalid serial number syntax, interface speed not changeable, slot already assigned, insufficient PONBW, profile suspended. + +**Post-conditions:** The resource is built within the supplier management system management model and is available for activities such as service provisioning. + +#### **6.2.2.5 Bulk transfer** + +**Summary:** Based on a timer (scheduler) or explicit request, the supplier management system transfers archived data through non-real time transfer mechanisms to a separate server known as a data warehouse. Archived data includes the contents of logs or record sets of statistics. This functionality includes monitoring and tracking of the transfer procedure. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. A communication link exists and is available between the operator or OMS and the supplier management system when making an explicit request. A communication link exists between the data warehouse and the supplier management system exists and is available. The supplier + +management system has authenticated the requesting operator or OMS. Archived data is accessible to the supplier management system. The data warehouse is able to store the new files (no obvious memory limitations). The supplier management system supports a scheduling function. Every record transferred in a single execution of bulk transfer function shall have the same data structure. After export, all exported data may or may not be deleted from the source location. If deletion of log records is expected, operator requested export should be possible only for special operator groups (authenticated) and this is handled by the OMS. If a scheduled transfer is desired, a schedule to be used in conjunction with the transfer has been established. Details of the file format are outside the scope of this use case. + +**Actors:** Data warehouse, operator, BPON NE, OMS. + +**Preconditions:** Archives have been established within the supplier management system and data has been stored in the archives. + +**Description:** This use case begins when the operator or OMS schedules the routine retrieval of archived data within the supplier management system on the BPON NE. The request includes reference to a previously determined schedule, identifies the archive and provides security credentials to the data warehouse and a file name to be used when the supplier management system transfers the data within the archive [unknown record set, unknown scheduler, unknown destination server, invalid scheduler]. At the trigger of the clock, the file transfer process is initiated. + +The operator or OMS may also make a request for the immediate file transfer of records within an archive of the supplier management system supplying the same reference material as before but without mention of the schedule [unknown record set, unknown destination server]. + +The supplier management system performs the following sequence of activities as part of the file transfer process: + +- The data records are grouped together into a file following a data transfer format pre-defined by operator and supplier agreement. The format conventions cover the use of delimiters, file header structure, file trailer structure. If the transfer data is found within a BPON NE, this step is accomplished within the BPON NE by request of the supplier management system. This file is created at the time trigger, whether or not this time trigger is derived from a schedule or on-demand by the OMS. +- The supplier management system uses file transfer protocol mechanisms to establish a connection with the data warehouse using the supplied security credentials. +- The supplier management system then writes the file to the file name provided [comm failure]. +- The supplier management system determines when the transfer is complete. It relies on file transfer protocol mechanisms to confirm that the transfer was successful. +- Throughout, the supplier management system records the status of the transfer process by providing updates to the transfer tracking object that was created within the supplier management system with the original transfer request. +- The supplier management system forms an activity completion record and logs the success or failure of the transfer in an activity completion log. + +At any time before completion of this process, the operator or OMS may check on the status of the transfer [unknown transfer process]. It is also possible for the operator or OMS to investigate the history of all file transfer requested or scheduled. + +Later, the OMS or operator may modify the schedule for the transfer of data from a particular archive. The OMS or operator formulates a request including reference to the existing scheduled activity and the new schedule to be applied [unknown transfer process, unknown scheduler, invalid scheduler]. The OMS or operator may also cancel the routine transfer of data from an archive + +[unknown transfer process]. If the activity is in progress, it shall be allowed to complete prior to cancelling of subsequent file transfer from that archive. The transfer tracking object is deleted from the supplier management system automatically upon cancellation of the scheduled process or with completion of an on-demand file transfer. + +This use case ends when all immediate file transfers have been completed and the OMS or operator has cancelled all scheduled file transfers. + +**Exceptions:** Unknown record set, unknown scheduler, unknown destination server, unknown transfer process, invalid scheduler. + +**Post-conditions:** The supplier management system no longer routinely transfers archived data to the data warehouse and no transfer tracking objects exist within the supplier management system. + +#### **6.2.2.6 Collect NE statistics** + +**Summary:** The supplier management system shall provide for the collection of history data records from the BPON NEs, including both performance and traffic monitoring statistics. This collection shall be timely and occur before requested records can be over-written by the BPON NE. This function supports OMS or operator data collection from the supplier management system. + +**Assumptions:** Performance or traffic monitoring and reporting has been activated by the operator or OMS for at least one monitoring point on a BPON NE within the management jurisdiction of the supplier management system. Monitoring on the BPON NE is accomplished through a register for every monitoring point. All registers for the same interval are initialized at the same time throughout the BPON NE (intervals may be 5 minutes, 15 minutes or 24 hours in length). + +Each type of collectable history data record is defined by the operator and associated with a specific monitoring interval length and monitoring point. Interval start times are determined by the supplier management system. A statistics archive has been created and initialized by the operator (or via supplier management system default setting) to hold each type of collectable history data record. Archives are constructed to only accept records of the same type (e.g., DS1PMHistoryData or DS3PMHistoryData) involving the same monitoring window length. + +If performance reporting has been requested by the operator for a particular monitoring point (via the use case called "performance and traffic monitoring reporting control"), a record showing the values for the counters or gauges is created at the end of the monitoring interval in the BPON NE and is available for collection. + +If the collection of history data records is triggered by a customer complaint, then the supplier management system executes the retrieval of pertinent history data records as a separate process in order to tag each record with the service instance Id. + +**Actors:** BPON NE. + +**Preconditions:** All required history data records have been formed on the BPON NE. + +**Description:** This use case begins when the clock indicates that another collection interval has been begun. The supplier management system systematically communicates with each BPON NE and retrieves all available history data records for the monitoring points and time interval specified by the operator or OMS. In the case of collection triggered by a customer complaint, the service instance Id is added to the history data records collected because of the customer complaint. + +If the communication channel between the supplier management system and the BPON NE is interrupted, the supplier management system attempts several times to re-establish communications and complete the retrieval of all history data records [comm failure]. The supplier management system classifies and stores the records in the short-term archive that holds the same record type. The supplier management system forms an activity completion record and logs the success or failure of the transfer in an activity completion log. + +This use case ends when the scheduled collection interval is ended. + +**Exceptions:** Comm failure. + +**Post-conditions:** BPON NE historical performance information is available for subsequent viewing by the operator and for bulk transfer to other file servers. The supplier management system archives the resulting information with other records of the same type awaiting the bulk transfer to the operator data warehouse. + +#### 6.2.2.7 Conduct test and report results + +**Summary:** The supplier management system shall participate as required in any operator or OMS directed testing procedure including, but not limited to, ATM OAM cell loopback testing, interface loopback set-up on subscriber cards or OLT network interface cards, self test, metallic drop test, MAC layer test, draw dialtone break dialtone, and ATM continuity checks. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The supplier management system communications channel to the NE is working. The supplier management system is ready to receive commands from an operator or OMS. Supplier management system communications channel to operator or OMS is working. The test performer or test device of the NE is working. Tests are sequential. The NE has capabilities to conduct the test. This use case can conduct tests to assess hardware functioning. This use case can also conduct test scenarios in order to address customer complaints of service failures. The OMS or operator constructs various test sequences to address diagnostics for specific detected or reported failure conditions. + +**Actors:** Operator, BPON NE, OMS. + +**Preconditions:** BPON network resources tested by this functionality have been installed and provisioned. In the case of service level testing, service has been provisioned and activated as well. + +**Description:** This use case begins when an operator or OMS receives a customer complaint or detects the failure of a BPON network resource. The operator or OMS constructs a test request. Types of tests requested include physical level tests, logical level tests and service level tests. + +Physical level tests include the following: voice frequency, quality of data transmission, multimeter test, signalling test, loop test, wideband test, power on self-test and on demand self-test. Logical level tests include the following: ATM cell continuity check and ATM cell loop back. Service level tests include protocol tests, MAC layer test, metallic drop test, draw dialtone break dialtone test and service level loopback. + +The supplier management system executes the following steps: + +- identifies the tests requested [unknown test, invalid test operations, invalid timeout period]; +- identifies the BPON resource to be tested and ancillary BPON resources that must participate in the test [unknown NE, unknown managed entity, not available for test, unknown service instance]; +- prepares the resources for the test (engages the test performer or device of the NE); +- executes the test sequence in collaboration with the NEs [comm failure, invalid test operations, invalid start time, invalid stop time, invalid direction, invalid location Id, invalid timeout period]; +- collects the results of the test; and +- reports the results of the testing promptly to the requester. + +If the test is of sufficient duration (e.g., interface port loopback tests) and the test is viewed to be controlled, the supplier management system supports test interruption from the requesting party and reporting of interim test results [unknown test]. + +Tests may be triggered by the clock as a scheduled activity [unknown scheduler, invalid scheduler, invalid timeout period, invalid test operations]. In this case, the test reporting process retains test results, grouping it with other test results and logged for viewing by the operator at a later date. The OMS may modify the schedule for a test or even cancel a regularly scheduled test on a managed resource [unknown scheduler, invalid scheduler, unknown test, uncontrolled test in progress]. + +If the supplier management system receives test requests to occur on the same managed resource at about the same time, the first scheduled or requested test is executed and the others generate a conflict report that is logged [not available for test]. + +This use case ends when the test completes execution and results are reported to the requesting OMS and logged in an activity completion log. Operators can retrieve historical test result by managed entity or service instance [unknown managed entity, access denied, unknown test, unknown service instance]. + +**Exceptions:** Access denied, comm failure, invalid test operations, invalid start time, invalid stop time, invalid direction, invalid location Id, invalid scheduler, not available for test, unknown managed entity, unknown NE, unknown test, invalid timeout period, uncontrolled test in progress, unknown scheduler, unknown service instance, unknown test, invalid timeout period. + +**Post-conditions:** An operator or OMS has more information with which to resolve the complaint of a customer or to support a maintenance activity. + +#### 6.2.2.8 Control archives + +**Summary:** The supplier management system provides the functionality to manage logs for specific groups of events. The privileged user can create, initialize, suspend, resume, purge and remove event logs. The supplier management system also provides the functionality to query the status of a log. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The supplier management system supports logs and short-term statistics archives. Only a privileged user has permission to create, initialize, suspend or resume archiving. Access control for the user has been verified prior to this use case. There are memory resources available on the server hardware supporting the supplier management system. The supplier management system tracks the status of logs and archives and provides a notification if a threshold related to the fill status of the log or archive is crossed. A communication link exists between the privileged user and the supplier management system. + +**Actors:** Privileged user. + +**Preconditions:** The privileged user is authenticated and a working session is established with the supplier management system. + +**Description:** This use case begins when the privileged user initiates a request to create a log or short-term archive that is not one of the standard archives installed with the supplier management system application. + +In case of log creation, the creation request identifies a filter defining the entrance criterion for an event in the log, log maximum size, full action (wrap or stop recording), a threshold to determine log full condition and action to be performed in case of log full [record set exists, duplicate user label, access denied]. + +In the case of performance or traffic statistics recording, the creation request identifies the type of history data record, the maximum size (in terms of record count), and a user label for identification [archive exists, duplicate user label]. + +After the creation of the log or statistics archive record set, the operator can change the user label of the record set or query its status [unknown record set]. The user can also suspend recording of new + +records into a particular record set or resume recording that had been previously suspended [unknown record set]. At any time the privileged user can purge an archive [unknown record set]. The privileged user can also delete any record set that was not automatically installed with the supplier management system application [unknown record set]. + +This use case ends when an archive is created, modified or deleted. + +**Exceptions:** Record set exists, unknown record set, duplicate user label. + +**Post-conditions:** A record set is created, re-named or deleted. Recording to the record set may be active or suspended. + +#### **6.2.2.9 Download and activate NE software** + +**Summary:** The supplier management system provides for the download, distribution, installation (commit) and activation of software generic programs, software upgrades and software maintenance changes (patches) to BPON NEs based on request of the operator or OMS. The supplier management system can accept requests for one or multiple BPON NEs at once. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The destination within the BPON NE for software download is free to accept downloaded software (e.g., no backup in progress). There are no outstanding alarms on BPON NE components involved in software download (e.g., control card operational or other NE components involved in software propagation). Supplier management system supports software version control. The communication between supplier management system and OLT is functional at the beginning of the use case. The communication channel between the OLT and the secure software file server is functional at the beginning of the use case. Before establishing an NE software download activity, it is assumed that the software set is available and tested. + +Until software is successfully loaded, propagated and activated, the formerly "active" version stays active. Software version control functionality is available. The supplier management system shall be able to support requests for software download, commitment and activation for a single instance and/or all instances of ONTs, ONUs or NTs subtending from one or all PON interfaces on one or more OLTs. The supplier management system shall be able to support requests for software download, commitment, and activation for a single instance and/or all instances of a particular card type for one or more OLTs. The activation of software on the OLT and ONU shall not be service affecting. If the activation of software on the ONT or NT is service affecting, the activation period is expected to last less than a few seconds. + +**Actors:** Operator, OMS, BPON NEs, secure file server. + +**Preconditions:** The software set is loaded onto the secure file server. + +**Description:** This use case begins when the operator or OMS makes a request to the supplier management system to load (and eventually activate) new software for the BPON NEs. The request includes a reference to the location of the software set to be downloaded and the target destination(s) of the download. The target destination can be specified at the BPON NE group level, the BPON NE level or at the circuit pack level depending on supplier implementation and operator agreement. The request can include a reference to a start time for download and/or activation if the intent of the OMS or operator is to plan the NE software activity. The supplier management system verifies the use of the software through software version control [unrecognized target, insufficient memory, software load HW mismatch, unknown software load, timeout, invalid start time]. Any request for downloading software generics is accompanied by security credentials whereby the supplier management system is allowed to communicate with the source server. + +The supplier management system then coordinates OLT access to the new software to be loaded, consulting the schedule or via on-demand request. The OLT downloads the software from the secure file server, applies the software to the target destination(s) and verifies that the delivery + +process has not introduced any errors to the software load [source unreachable, comm failure, insufficient memory, timeout, denied access, equipment failure]. + +The supplier management system returns a tracking object Id to the request that can be used to commit, activate, revert, get status, cancel and retrieve a list of software administration activities. The lifecycle of tracking object must extend until all associated activities are completed successfully or unsuccessfully. The object is only deleted after a pre-defined retention period and the length of time of the retention period is agreed outside the scope of this interface. The retention period for the tracking object should be generous enough to include any revert activity desired. If the tracking object has been automatically deleted by the supplier management system, then revert activity is viewed as download activity of a previous software load. The OMS can also delete this tracking object before its automatic termination if desired [unknown software download tracking object, software tracking object in use]. + +The software is not initially loaded to an active segment of the target destination. The software is then committed, i.e., made executable [installation failure, unknown software download tracking object, unrecognized target]. Then the software is activated by the operator or OMS [unknown software download tracking object, software not yet installed, activation failure, unrecognized target]. The supplier management system shall support both manual and automatic commitment and activation of successfully downloaded software. + +At each step of the NE software download process, the supplier management system shall update the status information associated with the tracking object. The supplier management system shall also provide a real-time notification as well as log the success or failure of these procedures in an activity completion log. Whether the download is successful or not, the supplier management system supports operator and OMS queries concerning the status of the download, distribution, commitment and activation process. + +The operator (or OMS) shall be able to cancel NE software download activities prior to their initiation [unknown software download tracking object, activity completed, activity in progress]. + +**Exceptions:** Software load/hardware mismatch, installation failure, activation failure, unknown software load, source unreachable, unrecognized target, comm failure, equipment failure, software not yet installed, insufficient memory, activity completed, timeout, activity in progress, denied access, unknown software download tracking object, invalid start time, software tracking object in use. + +**Post-conditions:** The BPON NE shall function using its new software load. + +#### 6.2.2.10 Log events + +**Summary:** The supplier management system stores event information in a log based on the filter defining the log. It makes the contents of a log available to a transfer function for scheduled bulk transfer. + +**Assumptions:** It is possible to construct filters to describe the contents of logs within the supplier management system. Operator can create these filters, modify the filters when needed and delete them when they are no longer needed. A set of default filters is attached to the individual log file and, when not defined, the default is no filtering. Log maintenance is handled by other use cases (control archiving and bulk transfer). In other words, logs are created, initialized, and cleared via other supplier management functionality. Only privileged users are allowed to create filters that define logs archived within the supplier management system. + +**Actors:** There are no external actors. + +**Preconditions:** An event has been processed by the supplier management system and a record formatted as result of that processing. + +**Description:** This use case begins when the supplier management system has processed an incoming event and formatted the resulting event record. Important events include but are not limited to the following: alarms, alarm clearings, threshold-crossing alerts, protection switching events, circuit pack removals and insertions, creation or deletion of managed entities, changes to key state and status variables, and scheduled or time-consuming activity completions. + +The processed event record is examined to see whether or not the record data matches any of the filter constructs defining the contents of any of the logs created and initialized for the supplier management system [event flood] (the filters determine which events are to be added to specific event logs). If the event record does not match any filter, the event information is discarded. If the event record does match a specific construct, the event record is stored in the relevant event log. If the log is not full, the event record is written at the end of the log. If the log has been configured as a "wrap around" log, and the log is full, the event record overwrites the oldest record in the log. If the writing of the event record causes a logFull condition, then a notification is prepared for forwarding to an external event channel [out of memory]. + +**Exceptions:** Out of memory, event flood. + +**Post-conditions:** The log is available for viewing by the OMS or operator. The contents of the log are available for bulk transfer to another file server called a data warehouse. + +#### 6.2.2.11 Manage profile objects + +**Summary:** Once a profile object has been created in the profile object repository, the supplier management system can process event information stating this fact and make the profile object settings available for use by any use case of the supplier management system. This functionality includes the ageing out and deletion of these profile settings. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The supplier management system maintains information on the syntax and permitted range of values for parameters for each profile type that it recognizes. Supplier management systems participating in this use case are instances of the same supplier application. The operator has determined which supplier management systems are interested consumers for event information. This assumes that the profile object type can be referenced and employed by the supplier management system. As required, management communications network links exist to support the publishing of profile object creation/deletion messages to the external event channel. Through an external specification process beyond the scope of this use case, the profile object repository is knowledgeable about valid values for profile object attributes. One or more profile object repositories may exist. + +**Actors:** OMS, operator, external event channel, BPON NEs. + +**Preconditions:** A supplier management system is installed and has registered as a consumer of profile object creation and deletion notifications.4 + +**Description:** This use case begins when a profile object is created in the profile object repository and published to the notification channel on external event channel. The message from the notification channel is consumed by the supplier management system. The message includes the name and type of the profile. It also includes the attribute value listing for the specific values of the profile object instance. The supplier management system stores the profile name and attribute values. In some circumstances, this may mean that the supplier management system writes this + +--- + +4 If creation of the profile object occurs prior to the instantiation of the supplier management system, then the supplier management system obtains its attribute values by query to the profile object repository [unknown profiles]. The supplier management system writes this profile name and attribute values to the NEs within its management jurisdiction. The profile object settings are now available for use by an operator or OMS when interfacing with supplier management system. + +profile name and attribute values to the NEs within its management jurisdiction. The profile object settings are now available for use by an operator or OMS when interfacing with supplier management system. + +The supplier management system supports the inquiry by an operator or OMS if a particular profile is in use in the management model under the jurisdiction of the supplier management system. The query includes the name of the profile object [unknown profiles]. The supplier management system supports the re-naming of any known profile [unknown profiles]. The supplier management system also supports the ageing out of use of a particular profile object by request of an operator or OMS [unknown profiles]. In this case, the supplier management system prevents subsequent use of the named profile object by any external or internal interaction. The operator or OMS can also request the resumption of use of a profile object [unknown profiles]. + +The supplier management system also supports deletion of all references to a particular profile object instance. A deletion request includes the name of the profile object [unknown profiles]. The supplier management system verifies that no use of the profile object is being made by any managed entity within its domain of management [profile in use]. This verification is accomplished by checking the management model. The supplier management system deletes all reference to the profile object within its application and on the network resources it is managing. + +This use case ends when the profile object parameters have been created, aged out or deleted in the supplier management system. + +**Exceptions:** Duplicate profile name, unknown profiles, profile in use. + +**Post-conditions:** At the end of its lifecycle, the profile object is unavailable for use by any supplier management system. Prior to that point, the profile object is available for use by an operator or OMS when interfacing with the supplier management system provided it has not been discontinued from use by an ageing out request of the operator or OMS. + +#### 6.2.2.12 NE software version control + +**Summary:** The supplier management system tracks the version and update status of BPON NE software and records this information in a repository accessible by the operator or NML system. The software version control validates the to-be-downloaded software version against the saved version number, and raises exception for invalid to-be-downloaded software version. The operator can view the software version information in the repository. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The supplier management system has a repository set up to store BPON NE software version information. The supplier management system has built-in algorithms, or rules for version control. The repository is large enough to hold hardware and software version information for all BPON NEs within its engineered management domain. + +**Actors:** Operator, OMS and BPON NE. + +**Preconditions:** A new version of NE software is due to be downloaded or a new BPON NE has been installed and registered with the supplier management system or a new plug-in unit has been inserted. + +**Description:** This use case begins when an NE software download is requested or when a new BPON NE has been installed in the network and autodiscovery has taken place. In each case, the supplier management system retrieves the current software and hardware version information from the BPON NE and updates (if necessary) the information within the software control repository for the NE memory area(s) [comm failure]. It determines if the version of software in the download request matches the rules or algorithmic checks implemented within the supplier management system for the corresponding hardware version. It provides notification of mismatch or match to the + +requesting internal process. As the NE software download process continues, the supplier management system continues to update the software hardware version information in its inventory. + +In the case of newly installed BPON hardware, the supplier management system determines if the current software load of newly installed hardware can be upgraded to the release being used throughout the administrative domain and automatically upgrades the new hardware with the current release and, again, updates its version release inventory. + +In all cases the supplier management system can respond to OMS or operator queries concerning the current release of software installed on a BPON network resource as well as whether or not a specific BPON network resource can support a particular software release [unknown managed entity, unknown NE]. + +This use case ends when hardware and software release information has been updated in the supplier management system inventory. + +**Exceptions:** Unknown managed entity, unknown NE, comm failure. + +**Post-conditions:** The version information of BPON NE software is updated and accessible to the operator and OMS. + +#### **6.2.2.13 Performance and traffic monitoring reporting control** + +**Summary:** The supplier management system shall provide for the activation and deactivation of performance data or traffic measurements collection on individual termination points contained in the BPON NEs as required by the operator or OMS. This use case also includes the setting of threshold values and describes automatic reporting of performance measurements when thresholds have been crossed. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. Hardware and software support for monitoring of all performance and traffic parameters defined in the current data and history data managed entities of [ITU-T Q.834.1] is available. Current data is not directly controlled by OMS. Hardware and firmware support for performance and/or traffic monitoring at all BPON NE monitoring points have been initialized and activated and counters and gauges are operational. The communications channels between the BPON NE and supplier management system and between the supplier management system and the operator or OMS are working. The supplier management system has verified that the operator or OMS has permission to establish threshold values and/or to request the collection of statistics from the BPON NEs. + +The supplier management system can hold up to one week of history data records collected from the BPON NEs within its management domain. The BPON NE can retain historical parameter values for at least one collection period beyond the recording of the data. The ultimate short-term archiving capability for performance and traffic records in the BPON NE is a matter for determination through explicit operator requirements and is not in the scope of this use case. Performance monitoring points of BPON NEs support the raising of threshold crossings alerts based on the setting of threshold values. + +**Actors:** Operator, OMS and BPON NE. + +**Preconditions:** Based on customer complaints or other trouble-shooting or maintenance needs, the operator decides to change the setting of threshold data values or wishes to collect performance and traffic measurements from BPON NEs. + +**Description:** This use case begins when the operator or OMS establishes or modifies values for thresholds for monitored performance or traffic measurements for certain termination points within a BPON NE. The operator or OMS sends a request to the supplier management system indicating the monitoring point(s) of the BPON NE, identification of the monitored parameters, and associated threshold values to be used in the detection of threshold crossing event [unknown NE, unknown managed entity, unknown profiles, invalid association, comm failure, profile suspended]. The + +supplier management system transfers each of the threshold values to the identified BPON NE for use at the associated monitoring point. The request process includes the opportunity for the operator to make a default setting assignment for a system-wide threshold value for each monitored parameter type within an entire BPON subnetwork [unknown NE, unknown managed entity, unknown profiles, invalid association, comm failure, profile suspended, unknown monitoring point types]. + +The BPON NE continues its constant monitoring of performance at each monitoring point for each counter, resetting each measurement to zero at the end of the monitoring interval associated with the counter. There can be 5-minute, 15-minute and 24-hour counters in the BPON NE. Monitoring intervals are automatically established and applied on a uniform basis across all monitoring points of the BPON NEs within the management domain of the supplier management system as each BPON NE is added to the management domain of the supplier management system. + +The BPON NE uses the threshold value to autonomously alert the supplier management system whenever the counter associated with the performance parameter falls out of the acceptable performance range indicated by the threshold value. TCA event processing by the supplier management system triggers (in part) the automatic retrieval of the history data record associated with the TCA event by the supplier management system. The history data record is archived with other records of the same type associated with TCA events and awaits the bulk transfer to the operator data warehouse. + +Based on a customer complaint, the operator or OMS can request the collection of history data records for a selection of monitoring points for limited periods of time. The request includes the identification of the BPON NE and monitoring points, the history data records to be collected, the start time for collection, the collection window length and the service instance Id associated with the complaint [unknown managed entity, collection period past, unknown service instance Id, unknown NE]. The supplier management system notes the monitoring points and monitoring collection intervals and collaborates with the containing BPON NE to enable the subsequent reporting of performance parameter values for each of the collection intervals for each monitoring point [collection limitation]. + +The operator or OMS may also request the routine collection of certain history data records from BPON NEs or may request the termination of routine collection. The request made to the supplier management system identifies the monitoring point type and history data type [unknown history data type, invalid association, unknown scheduler, invalid scheduler, unknown NE]. The supplier management system notes the monitoring points and collaborates with the containing BPON NE to enable the subsequent reporting of performance parameter values for every collection interval for each monitoring point, or to disable the subsequent reporting [collection limitation]. + +Based on trend analysis or traffic monitoring needs, the operator or OMS can also request the routine auditing (i.e., collection) of history data records. The request made to the supplier management system includes the BPON NE, monitoring point instance, history data record type and schedule to apply to the collection of the history data record identified [unknown managed entity, collection period past, unknown NE]. The supplier management system notes the monitoring points and monitoring collection intervals and collaborates with the containing BPON NE to enable the subsequent reporting of performance parameter values for each of the collection intervals for each monitoring point. In this case, reporting of zeroes is not suppressed [collection limitation]. + +The operator or OMS may query the supplier management system at any time to obtain a listing of reporting monitoring points and reporting intervals for each BPON NE. + +This use case ends when threshold values have been established, modified or removed for all or selected monitoring points or when performance data collection schedules are established, modified or cancelled according to maintenance needs and service level agreement policies. + +**Exceptions:** Collection limitation, unknown monitoring point, collection period past, unknown type, comm failure, unknown threshold data, invalid threshold data, unknown service instance Id, unknown BPON NE, reporting exists, unknown scheduler. + +**Post-conditions:** The operator has set threshold data values for monitored parameters on the BPON NE and the NE will respond with a TCA if an impairment is detected. If the operator request involves the collection of history data records in the supplier management system, then these record sets are available for retrieval by the OMS or operator, or for bulk transfer to the data warehouses. + +#### **6.2.2.14 Process incoming NE events** + +**Summary:** The supplier management system processes event notifications from the BPON NEs within its management jurisdiction. The supplier management system identifies the event type and source, transforms and augments the data into an event record structure of potential benefit to upstream systems and users, and transfers the record into an internal repository accessible to other supplier management system functions. + +**Assumptions:** The communications channels between the supplier management system and the NEs are working. The supplier management system is able to accept notification of all events from the BPON NEs within its domain of management. Events are time-stamped by the NEs with a consistent timing source. The supplier management system coordinates the time stamp mechanism between NEs. + +**Actors:** BPON NE. + +**Preconditions:** An event is detected by an installed BPON NE. + +**Description:** This use case begins when an event notification arrives from a BPON NE at the supplier management system event channel. Upon receiving an NE event the supplier management system uses a soak period to screen event transients (e.g., toggling alarms). This is distinct from the soak period used by the NE to determine that the situation should be reported as an alarm. The supplier management system perceives the event (i.e., it screens the source of the event and verifies that it is interested in the event) [corrupted event data, incomplete event data, unauthorized source]. The supplier management system shall discard any event according to a set of business rules including, but not limited to, the elimination of "toggling" events and congestion conditions on the input event buffer (persistence analysis on the event may also have occurred on the NE). The supplier management system further identifies the event. The list of event types consists of alarms (including threshold crossing alerts), attribute value changes (including protection switching events and state changes), and network resource creation and deletion notifications. + +The supplier management system may add data to the NE event information according to business requirements provided by the network operator [unable to add required enhancements]. For example, in the case of alarm events, the supplier management system may correlate alarm information to service instances supported by the managed entity in failure condition and add the identification of affected services to the event notification. The addition of the data could involve consultation with the management model in the supplier management system in order to determine if a service outage has occurred and the assignment of alarm severity, if this characteristic has not already been provided by the NE. + +This use case ends when the supplier management system makes the enhanced information accessible to other internal functions by putting it in an event queue. + +**Exceptions:** Corrupted event data, incomplete event data, unauthorized source, unable to add required enhancements. + +**Post-conditions:** The functions "autodiscover NE and plug in units", "root cause alarm analysis", "root cause impairment analysis", "provide current event summary listings", "maintain management model" and "log events" are able to consume properly formatted event records. + +#### 6.2.2.15 Provide current event listings + +**Summary:** The supplier management system will provide access to information showing the current value of key status and state parameters and group this information in a listing for perusal by the operator. The listings are continuously and autonomously updated by the supplier management system based upon ongoing events within the BPON NEs. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. Lists are limited to information concerning failure conditions and trouble-shooting within the BPON NEs. This functionality includes, but is not limited to the following: current alarm summaries, listing of successful and unsuccessful protection switching events where the protected unit is no longer the active one, service instances currently experiencing a service outage, termination points in loopback mode, or managed entities whose administrative state is "locked". + +The supplier management system can process incoming BPON NE and GUI interaction events. The supplier management system can correlate events and service information, can conclude that a service outage exists for a particular failure condition (considering all affecting conditions like protection switching events and that a service has indeed been provisioned), and can correlate protection group provisioning information with protection switching events. Events can come from BPON NEs or operator interaction. It is a matter for supplier implementation and operator requirements which current event listings are supported. + +**Actors:** Operator, BPON NE, privileged user. + +**Preconditions:** Current listings and event queues have been initialized as part of the installation of the supplier management system. + +**Description:** This use case begins when events of interest are detected at the BPON NE and event information is set to the supplier management system. The supplier management system examines events indicating changes in state and status. If the variable is one tracked for a current summary event listing, the listing is consulted. If the event indicates the start of a tracked condition, information concerning the managed entity associated with the event and attribute is added to the listing along with a timestamp of the event, provided the condition is not outstanding already. If the event indicates the end of a tracked condition, the listing is consulted and the most recent listing entry concerning the start of the condition is removed. Listings summarize conditions on a BPON system basis. + +The listing is always accessible to view by the operator through a graphical user interface. Changes to the listing happen autonomously without the need for operator refreshing of the screen. Desired modes of presentation of the listing are determined via operator system requirements. + +Operators with privileged status are allowed to resynchronize current summary event listings. Based on operator request, the supplier management system retrieves the current value of the state, status or management attribute tracked by the current summary event listing for the BPON system for any managed entity contained in the system that possesses the characteristic attribute [comm failure, DCN timeout, unknown NE, equipment failure, timeout]. If the BPON system retrieval process shows that the listing is not up-to-date with the current conditions of the system, then the listing is modified (through deletion of an entry or insertion of a new entry) in order to correct the listing. + +Listing entries are correlated with information retrieved from the system via the identifier of the managed entity. Deletion of an entry can occur if a listed managed entity no longer exists contained within the BPON system, or if a failure condition or test has ended and the system has reverted to normal functioning. If either of these situations occur, all entries concerning the same managed entity are removed from the listing. Insertion can occur when no listing entry exists for a managed entity now indicating a change in functioning. + +This use case ends when the listing has been properly updated. + +**Exceptions:** Comm failure, DCN timeout, unknown NE, equipment failure, timeout. + +**Post-conditions:** Accurate current event list information is accessible to the operator and OMS. + +#### 6.2.2.16 Provision installed NEs + +**Summary:** Installed BPON resources are provisioned with configuration settings in anticipation of service provisioning. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. Management communications between the supplier management system and the installed BPON resource is operational. In the case of the OLT, this means that the OLT has been registered. In the case of an ONT or ONU, this means that the ONT or ONU has been ranged. In the case of an NT, this means that the upstream ONU has been ranged and that management communications exists between the NT and ONU. Configuration settings may (or may not) have been previously supplied to the supplier management system. + +**Actors:** BPON NE, operator or OMS. + +**Preconditions:** A BPON NE has been installed and is under the management jurisdiction of the supplier management system. + +**Description:** This use case begins when the operator or OMS undertakes to provision the installed BPON network resource. BPON resources include BPON NEs (OLT, ONT, ONU, NT) and/or plug-in units. The autodiscovery function provides the supplier management system with inventory data describing the type of equipment installed. The supplier management system automatically "builds" the BPON resource in the management model. + +If the information constructed in the management model matches inventory data supplied previously to the supplier management system (through a set of "pre-provisioning" build transactions from the operator or OMS), the supplier management system automatically applies to the installed resource any additional configuration settings supplied via the previous transactions. If the information constructed in the management model does not match inventory data supplied previously to the supplier management system, the supplier management system prepares one or more event records to notify interested consumers of the mismatch. + +If no previous "pre-provisioning" build transactions have taken place, the operator or provisioning OMS formulates a set of provisioning build requests identifying the discovered BPON resource and providing configuration settings necessary to prepare the BPON resource for use in service provisioning.5 The supplier management system applies these settings to the identified BPON resource and updates the management model appropriately. + +This use case ends when provisioning information has been transferred (as needed) to the pertinent network resources by the supplier management system. + +**Exceptions:** See clause 6.2.2.4 exceptions. + +**Post-conditions:** The installed BPON resource is available for service provisioning and activation management operations. + +#### 6.2.2.17 Provision service + +**Summary:** The supplier management system selects ports, facilities and bandwidth from BPON resources determined to be available in order to complete the design, selection and assignment process associated with a set of services for a particular customer. Activation of network resources occurs simultaneously provided immediate activation is required. A service is + +--- + +5 Details covered in clause 6.2.2.4. + +defined as a connection between an UNI endpoint on an ONT and an NNI endpoint at an OLT, or between UNI endpoints on two ONTs subtending from the same OLT. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The OLT is registered with the supplier management system. The PON interface plug-in unit on the OLT may or may not be installed. In any case, the PON port has been provisioned. The ONT may or may not be installed. ONT resources have been provisioned if not installed. An operator or provisioning OMS selects the endpoints. The provisioning OMS or operator have access to the valid/permissible range of VPI/VCI values for the NNI and UNI interfaces. The communications channel between the supplier management system and OLT is up at the start of the use case. Resources may or may not have been reserved prior to this use case for the service connection. + +**Actors:** OMS, operator, BPON NEs. + +**Preconditions:** A service request has triggered the need for a connection between an UNI endpoint on an ONT or NT and an NNI endpoint on an OLT or between two UNI endpoints of ONTs subtending from the same OLT. + +**Description:** This use case begins when the OMS or operator sends a service connection set up request to the supplier management system. The request includes a service instance identifier, identifiers and characteristics for the endpoints (i.e., VPI and VCI values for ATM endpoints), a reservation Id (if relevant), administrative state value, and profile pointers that characterize the service connection desired. The supplier management system validates existence of the end points, identifiers and profiles [unknown NE, unknown profiles, unknown port, profile suspended, connection already exists]. It checks to see if the VPI/VCI values are in use and are valid [parameter violation]. It checks to see if resources have already been reserved [unknown reservation Id]. The supplier management system also validates that required network resources exist to provision this service if resources have not been reserved and applies appropriate configuration requests to the BPON NEs if they are already installed [insufficient BW, connection count exceeded, comm failure, equipment failure, insufficient PON BW]. Whether or not the BPON NEs are installed, the supplier management system updates its own management information model following rules derived from [ITU-T Q.834.1]. The supplier management system generates a subnetwork connection Id to describe the service connection and returns this value to the OMS or operator. + +At some later point, it might be necessary to modify the traffic or service characteristics describing the connection. In this case, a modification request is made from the operator or OMS to the supplier management system that includes the subnetwork connection Id [unknown connection], port A Id [unknown port] and a listing of service profile names and new network profile names [unknown profiles, profile suspended]. The supplier management system validates that required network resources exist to provision this service change (e.g., bandwidth over the PON and on the designated network interface) [insufficient BW] and applies the new traffic profile characteristics to the service connection [unknown profiles, profile suspended]. + +Based on customer request (extended absence) or failure to pay service charges, the OMS or operator may request the suspension of an existing service connection. In this case, the OMS or operator formulates a request including the service instance Id and the suspension time interval that is sent to the supplier management system for execution [unknown service instance, invalid start time, invalid stop time]. The supplier management system also supports the resumption of service based on the request of the OMS or operator if this is desired prior to the stop time of suspension or if the original connection request had administrative state set to the "locked" value [unknown service instance]. + +The operator or OMS may request the removal of a service connection. In this case, the deletion request includes the subnetwork connection Id. The supplier management system changes the configuration data on the BPON NEs [unknown connection, comm failure, equipment failure] as well as within its own management information model. The supplier management system also + +makes resources formerly assigned to the service available for use by any subsequent connection request, modifying managed entities tracking these resource values. + +This use case ends when the service creation, modification, suspend, resume or disconnect request completes and relevant service provisioning information has been transferred to the pertinent NE(s) as they are installed. + +**Exceptions:** Insufficient bandwidth, insufficient PON bandwidth, unknown port, unknown profiles, profile suspended, comm failure, equipment failure, unknown NE, connection already exists, connection count exceeded, parameter violation, invalid start time, invalid stop time, unknown service instance, unknown reservation Id. + +**Post-conditions:** Connection information is available to be applied to installed BPON network resources, thus creating service availability for the requesting customer. + +#### **6.2.2.18 Publish event** + +**Summary:** On receipt of processed configuration, performance, or fault event information provided by other use cases within the supplier management system and based on rules concerning publication, the supplier management system queues and channels event information to all interested consumers. + +**Assumptions:** Management communications channels are available between the supplier management system and interested consumers (users and systems) allowing the transfer of event information. The actual notification mechanisms are dependent on the communications protocol and can range from publishing, to specific event channels, to directing of event messages to individual consumers based on a discriminator construct filter. Details of the autonomous mechanisms are outside the scope of the use case. Operator business rules have been implemented in the supplier management system describing the event data that should be immediately transferred to upstream OMS(s) or operators. Relationships between event type and suitable notification channels have also been implemented. + +**Actors:** External event channel. + +**Preconditions:** The supplier management system is installed and is managing at least one BPON NE. + +**Description:** This use case begins when, as part of its installation, the supplier management system establishes management communications mechanisms for the purpose of forwarding event information using agreed upon protocols [already connected]. Then the supplier management system becomes aware of the creation of an event record from an internal process. Event records can be created because of managed entity creation, managed entity deletion, alarms, threshold crossing alerts in performance monitoring, and attribute value changes, including, but not limited to, changes in state and status variables, circuit pack removal from slots, and protection switching occurrences. + +The supplier management system applies business rules provided by operator requirements to determine whether or not the event record is of interest to any consumers. If the event record is not of interest to any consumers, it is discarded. If the event record is qualified for immediate transfer, the supplier management system provides the event record information to the notification forwarding mechanism implemented on the supplier management system that is specific to the communications protocol in use between the supplier management system and any interested event consumer [disconnected]. In some cases there may be multiple notification channels, in which case the supplier management system will also determine the channels to be used [invalid event type]. + +This use case ends when the event record has been successfully transferred to an external event channel. + +**Exceptions:** Disconnected, already connected, invalid event type. + +**Post-conditions:** The event information is available for use by the operator or OMS. + +#### 6.2.2.19 Range ONT or ONU + +**Summary:** The supplier management system directs the OLT to range a subtending ONT or ONU. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The OLT has been installed and is equipped with a provisioned PON interface card. The DCN is working between the supplier management system and OLT. The OLT supports ranging as described in [ITU-T G.983.1]. The ONT or ONU has been installed and is equipped with power. There is an ODN connection between the OLT PON interface port and the ONT (or ONU). Ranging can be accomplished without required use of service demand information. The supplier's manufacturing process control prevents the possibility of duplicate serial numbers. The supplier management system may support rules concerning serial number syntax and the maximum number of subtending ONT or ONUs on any OLT PON interface card port. + +**Actors:** Operator, OMS, BPON NE (OLT). + +**Preconditions:** An ONT or ONU has been installed. + +**Description:** This use case begins when the supplier management system obtains the serial number for a newly installed ONT or ONU. The serial number may be provided by a field installation technician or through an automatic protocol detection mechanism. If the serial number is provided by a technician, a ranging request for the ONT or ONU is formulated including identification of the OLT, the OLT PON port, the user label of the ONT or ONU, and the serial number itself. The supplier management system directs the OLT to range the new subtending ONT or ONU based on its serial number [comm failure, equipment failure, unknown NE, unknown port, max subtending nodes exceeded, insufficient PON BW, invalid serial num syntax, APON layer failure, duplicate user label, invalid user label syntax, backup in progress, synch in progress]. + +This ranging activity calculates the optical distance between the OLT and ONT/ONU, establishes security mechanisms, sets up the upstream time slot for the ONT/ONU, assigns an index number for the ONT/ONU, and establishes the VCC for the embedded operations channel between the OLT and ONT/ONU. The latter action establishes management communication between the supplier management system and the ONT/ONU. The supplier management system associates the ONT (or ONU) with an index number and returns the managed entity Id for the ONT. It also associates the user label supplied on the request with the index number and the ONT (or ONU) managed entity Id. + +If the serial number is supplied through automatic ranging protocol mechanisms through the autodiscovery function of the supplier management system, then the OMS or operator either requests the association of pre-provisioned data to the freshly discovered ONT/ONU [unknown managed entity] or builds the ONT/ONU and then requests the association of provisioned data to the freshly discovered ONT/ONU [unknown managed entity]. In either case, the supplier management system associates the ONT (or ONU) with an index number, the user label, and the managed entity Id as before. + +In case the ONT or ONU becomes defective, the supplier management system supports requests for replacement of ONTs/ONUs. In this case, the OMS or operator forms a request including the managed entity Id of the original NE, the new serial number for the replacement NE, and the new user label. The supplier management system processes the request, ranges the new ONT or ONU from the same PON port of the OLT, and applies existing service configuration data to the new ONT/ONU [comm failure, unknown NE, invalid serial num syntax, APON layer failure, equipment failure, invalid user label syntax, HW services mismatch, duplicate user label, backup in progress, synch in progress]. + +In case the service demand at the ONT or ONU location exceeds the capabilities of the existing NE, the supplier management system supports requests for the upgrading of the ONT or ONU. In this case, the OMS or operator forms a request including the managed entity Id of the original NE, a + +reference to pre-provisioning information for the new services, the new serial number for the replacement NE, and the new user label. The supplier management system processes the request, ranges the new ONT or ONU from the same PON port of the OLT, and applies existing and new service configuration data to the upgraded ONT/ONU [comm failure, unknown NE, invalid serial num syntax, APON layer failure, equipment failure, invalid user label syntax, HW services mismatch, duplicate user label, backup in progress, synch in progress, insufficient PON BW]. + +In case the service demand on a PON port reaches a threshold, then the supplier management system also supports requests for moving of the ONT/ONU from one PON port to another one. In this case, the OMS or operator forms a request including the managed entity Id of the original NE and the new PON port Id. The supplier management system processes the request, ranges the existing ONT or ONU from the new PON port of the OLT, and retains existing service configuration data associated with the ONT/ONU [comm failure, unknown NE, unknown port, APON layer failure, equipment failure, insufficient PON BW, backup in progress, synch in progress]. + +This use case ends when the ONT or ONU has been ranged successfully and all pertinent managed entities have been built in the supplier management system. + +**Exceptions:** Comm failure, unknown NE, invalid serial num syntax, APON layer failure, equipment failure, invalid user label syntax, HW services mismatch, duplicate user label, backup in progress, synch in progress, insufficient PON BW, unknown port. + +**Post-conditions:** The ONT or ONU is ready for further provisioning activities. + +#### 6.2.2.20 Register OLT + +**Summary:** The management communications channel between the supplier management system and OLT is verified and the OLT is registered for management by the supplier management system. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The OLT is installed. The power supply is working. An operator-defined name (OLT user label) and DCN address (e.g., IP address) have been configured on the installed OLT via local craft interface or some factory provisioning mechanisms. Registration takes less than one minute. The DCN connection has been installed and configured. A check of DCN connectivity times-out from the supplier management system if no response from the remote end is received within 10 seconds. If privileged user status is required for the provisioner, access control mechanisms have been verified in advance of this use case. + +**Actors:** Operator, OMS, BPON NE (OLT). + +**Preconditions:** An OLT is installed, but not yet managed by the supplier management system. + +**Description:** This use case begins when the OMS or operator requests that a supplier management system build a new OLT within its management domain. The request includes the DCN address associated with the OLT and an OLT user label. The request may also include references to operator administration domains. The supplier management system processes the request [duplicate user label, too many NEs, invalid user label syntax]. Invalid DCN address stores the address and label information and checks the DCN connection between itself and the OLT [DCN timeout, invalid DCN address]. The supplier management system establishes application layer to application layer communications between itself and the OLT and verifies this communication by retrieving the OLT user label [denied access, address label mismatch]. The supplier management system then assigns a globally unique OLTid (managed entity Id) to the OLT, thus exercising its role as manager of the OLT, and returns this assignment to the requesting OMS or operator. + +Upon request of the OMS or operator, the supplier management system can change the DCN address of an OLT belonging to its management domain. In this situation, the request includes the managed entity Id for the OLT and the new DCN address. The supplier management system verifies + +the old DCN address, checks the DCN connection between itself and the OLT using the new DCN address, and verifies management capabilities by retrieving the OLT user label [denied access, address label mismatch, DCN timeout, comm failure, unknown NE, invalid DCN address, backup in progress]. + +It is also possible to remove an OLT from management jurisdiction of the supplier management system by making such a request [unknown NE]. + +This use case ends when the supplier management system has added the OLT to its domain of management and has established a management application association with the OLT. + +**Exceptions:** Denied access, address label mismatch, DCN timeout, comm failure, unknown NE, invalid DCN address, backup in progress, duplicate user label, too many NEs, invalid user label syntax. + +**Post-conditions:** As long as the OLT is registered with the supplier management system it is available for management by the OMS or operator through the supplier management system. + +#### 6.2.2.21 Report service outages + +**Summary:** When a network outage occurs, the supplier management system should be able to detect it based on incoming alarms and events, identify affected services and BPON resources, generate service outage records and report the outage to the OMS or operator. + +**Assumptions:** The supplier management system establishes a proper channel to receive incoming alarms/events. It also establishes the proper channel to the OMS to report possible outages. The supplier management system has the necessary information about the services and BPON resources that it manages. It also contains proper logic to detect outage and affected service/resources based on incoming alarms/events. + +**Actors:** BPON NE. + +**Preconditions:** The supplier management system is installed and maintains relationship information between network resources and service assignments. + +**Description:** This use case begins when the supplier management system receives NE event information reflecting a possible network outage. The supplier management system proceeds with root cause analysis in an attempt to determine the fundamental cause of the failure. It also accesses events from the alarm event queue and protection switching event queue for the affected BPON NE in order to determine whether or not the failure condition is service affecting. If so, the supplier management system consults with the management model in order to identify the service instances that have been affected by the network outage and creates a service outage event record for each instance affected. Each service outage record shall include identification of the affected service, values of relevant state attributes, cause of outage, outage start time. The supplier management system posts the outage event record to a current event listing for such service outages. The OMS and operator can retrieve this information via an explicit request. + +Later, when event information indicating the clearing of the network outage is received and processed by the supplier management system, the supplier management system removes the outage event information from the current listing, appends the outage stop time to the record, and records the enhanced record in a log on the supplier management system. + +This use case ends when expanded outage record has been posted to the log. + +**Exceptions:** None specified. + +**Post-conditions:** Service outage records are available for retrieval by the OMS from the log. + +#### 6.2.2.22 Reserve resources + +**Summary:** The supplier management system supports reservation of bandwidth pending installation of an ONT, ONU, NT or subscriber port in the ONT or NT for a particular OLT prior to the dispatch of personnel to the ONT, ONU or NT installation location. This function includes cancel and modification of resource reservation. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The supplier management system may support rules concerning the maximum number of subtending ONT on any OLT PON interface card port for the OLT. The supplier management system has an accurate view of current network resources for a specific OLT, including installed, assigned and reserved resources. CAC calculation capability is supported either by an installed OLT or by the supplier management system. Slot assignments do not change within this use case. + +Appropriate DCN communications between the supplier management system, upstream OMS(s), and OLT are available as needed at the start of the use case. Reservation of bandwidth is supported on a per service instance basis (implying the eventual creation of a subnetwork connection). + +**Actors:** Operator, OMS, BPON NE (OLT). + +**Preconditions:** The OLT has been provisioned as well as the relevant PON interface slot and NNI slot and the OLT is under the management jurisdiction of the supplier management system. + +**Description:** This use case begins when an operator or OMS receives a work order to install a new service where there is new ONT, a new ONU, a new NT or a new subscriber line card in an existing NT or ONT. The operator or OMS formulates a reservation of bandwidth request. The request includes a service instance identifier, identifiers and characteristics for the endpoints (i.e., VPI and VCI values for ATM endpoints), and profile pointers that characterize the service connection desired. The supplier management system validates existence of the end points, identifiers and profiles [unknown NE, unknown profiles, unknown port, profile suspended, connection already exists]. It checks to see if the VPI/VCI values are in use and are valid [parameter violation]. The supplier management system processes the information provided on the request and performs the following: + +- accesses a CAC calculation mechanism to determine whether there is sufficient bandwidth in the OLT to admit the service [insufficient bandwidth]; +- uses connection counts, grant bandwidth metrics and port line bit rate information to determine whether there is sufficient capacity on the OLT (includes ODN limitations) and on the prospective interfaces of the OLT to satisfy the service demand [max subtending nodes exceeded, connection count exceeded]; +- reserves bandwidth, capacity and connections [comm failure] on the provisioned NEs; +- makes association of reserved resources to service instance Id; +- provides the reservation Id to the requesting operator (or provisioning system) as identification for the reserved resources. + +The operator or OMS makes requests until reservation of all resources in the OLT required for the installation of services for the specific customer served by the ONT, NT or port/circuit pack is finished. + +The supplier management system shall also support requests by the operator provisioning OMS to cancel reserved resources. The operator or OS references the reservation Id with the cancel request [unknown reservation Id]. The supplier management system releases all network resources whose reservation is tagged by the reservation Id. + +The supplier management system shall also support retrieval of a reservation Id given a service instance Id value or the retrieval of a service instance Id given a reservation Id originally provided + +with a successfully completed reservation request [unknown service instance, unknown reservation Id]. + +The supplier management system can report on reserved, assigned and available bandwidth per port on request of the OMS or operator [unknown NE, comm failure]. The supplier management system can also report on the amount of bandwidth reserved for a particular reservation [unknown reservation Id]. + +This use case ends when reservation of bandwidth, connections and other capacity metrics is completed and reservation information has been transferred as needed to the pertinent NE(s). + +**Exceptions:** Unknown NE, insufficient bandwidth, max subtending nodes exceeded, connection count exceeded, duplicate service instance Id, unknown service instance, unknown reservation Id, comm failure, unknown profiles, profile suspended. + +**Post-conditions:** Bandwidth, connections and capacity are marked as "reserved" in any subsequent capacity inventory reporting and dedicated for future provisioning activities for the identified service instance. + +#### 6.2.2.23 Root cause alarm analysis + +**Summary:** When there is an occurrence of a set of alarms associated with a single failure condition, the supplier management system shall analyse and correlate the alarm events within its domain to the best of its ability and determine the underlying root cause of the problem. It prepares an alarm record for the root cause failure condition for forwarding to OMS(s) and operators. If root cause is not determined, the supplier management system prepares a set of alarm records for publication to OMSs and operators.6 + +**Assumptions:** One failure condition in a BPON network resource may result in many alarm events from multiple managed entities. Multiple alarm events occurred at approximately the same time. These events were already evaluated and validated by the supplier management system ("process incoming NE events") and shown to possess enough information for alarm analysis purposes. The supplier management system maintains a management model containing (in part) dependency relationships between managed resources including unmonitored resources. Redundant alarm events are eliminated. + +**Actors:** No external actors. + +**Preconditions:** Multiple failure conditions have been detected by a BPON NE within a short period of time. + +**Description:** This use case begins when multiple incoming alarm events have been processed by the supplier management system within a small period of time. The supplier management system groups together related alarm events into an event set for direct comparison or patterning. Event sets are created via rules determined by managed entity dependency relationships. The supplier management system engages in an event comparison process with the goal of finding one active, underlying, independent event for the event set. The process starts with the first alarm event in the event set and compares the next event to see if one of them may be eliminated through rules of event correlation. The process continues until all events in the event set have been processed. If the comparison process detects an event that cannot supersede or be superseded by a previous event, it will be combined with remaining previous events. The result of this comparison process is either determination of a single root cause failure condition or a filtered set of alarm events. + +Dependencies are relationships between equipment components and/or transmission media determined by the topology of the network, client-server associations and cross connections. + +--- + +6 This use case description makes significant use of management functionality described in [ITU-T M.2140]. + +Patterning may be done recursively to infer trouble with a resource such as a conduit or power supply from indications in many indirectly supported resources. State change information also plays a role in alarm event correlation. There are several types of failure conditions: equipment failures, communications failures, processing errors, environmental concerns and security violations. There can be dependencies and causality relationships between different types of failure conditions. + +Communication alarms may be triggered by an equipment fault. Therefore, if an equipment alarm is received, all communication alarms for termination points contained by the equipment component should be superseded. That is, communication alarms are only considered when they occur without related equipment alarms. If no equipment alarms related to the trail are received, but communication alarms are received, then the cause of the fault might be outside of the supplier management system management domain, might be due to some unmonitored equipment component within its domain, or might arise from the transmission medium that carries the characteristic signal between the BPON NEs. In this case, the upstream communication alarm might be considered the best root cause information within the supplier management system domain. + +Environmental alarms should be given high priority in searching for root cause since they point to problems for entire BPON nodes or all NEs at a given location (i.e., they relate to many equipment components and many trails). State changes can also serve as a backup method of detecting faults. Administrative and operational state changes should be treated as equipment alarms, since they always indicate a change in the ability of a resource to fulfil its function. The details of alarm event correlation are left up to the individual supplier management system. + +This use case ends when a root cause has been determined, or when an event set has been filtered to the greatest extent possible. The alarm information is formatted in records and made available to interested consumers. + +**Exceptions:** None specified. + +**Post-conditions:** Root cause alarm information has been formatted and these alarms can be raised to external event channels. + +#### **6.2.2.24 Root cause impairment analysis** + +**Summary:** When there is an occurrence of a set of threshold crossing alerts associated with a single performance degradation condition, the supplier management system shall analyse and correlate the alert events within its domain to the best of its ability, determine the underlying root cause of the problem, and store this information in a log. If several occurrences of the same root cause impairment are detected within a period of time, the supplier management system shall prepare a QoS alarm record for publication by any interested consumer (operator or OMS). + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. One impairment condition in a BPON network resource may result in the notification of multiple TCA events associated with multiple managed entities. Multiple TCA events occurred at approximately the same time. These events were already evaluated and validated by the supplier management system ("process incoming NE events") and shown to possess enough information for impairment analysis purposes. The supplier management system maintains a management model containing (in part) dependency relationships between managed resources including unmonitored resources. Redundant TCA events are eliminated. The supplier management system shall support the collection of performance monitored parameters including, but not limited to, those listed as history data managed entities. + +**Actors:** Operator or OMS. + +**Preconditions:** Multiple impairments have been detected on a BPON NE within a short time window. + +**Description:** This use case begins when multiple incoming TCA events have been processed by the supplier management system within a small period of time. The supplier management system groups together related TCA events into an event set for direct comparison or patterning. Event sets are created via rules determined by managed entity dependency relationships. The supplier management system engages in an event comparison process with the goal of determining one active, underlying and independent priority impairment for the event set. + +The process starts with the first TCA event in the event set and compares the next event to see if one of them may be eliminated through rules of event correlation (see below for some filtering rules). The process continues until all events in the event set have been processed. If the comparison process detects an event that cannot supersede, or be superseded by, a previous event, it will be combined with remaining previous events. The result of this comparison process is either determination of a single root cause impairment condition or a filtered set of TCAs. + +Dependencies are relationships between equipment components and/or transmission media determined by the topology of the network, client-server associations, and cross connections. With the exception of physical interface termination points on the subscriber plug-ins, the supplier management system shall collect only near-end performance monitored parameters. The supplier management system shall suppress the processing and reporting of TCA on trails when the trails have an active failure condition. For each TCA, the supplier management system shall filter out any downstream near-end and far-end TCAs relating to the same direction of transmission for lower level trails served by the trail generating the TCA. For a set of TCAs involving the same parameter for the same trail, the supplier management system shall filter out all but the first TCA received during the interval of collection. TCAs may be further filtered according to precedence within each history data parameter category. + +At the end of the precedence and comparison filtering process, the supplier management system shall support tagging of the remaining TCAs. If a particular TCA persists for X intervals within a window of Y collection intervals (where X and Y are settable), the TCA will be called a persistent root cause impairment. The supplier management system shall notify all interested clients of any such persistent filtered root cause impairments using a quality of service alarm and providing the necessary information including managed entity Id, performance parameter, threshold value and observed value. + +The supplier management system also allows the setting of sliding window parameters (i.e., X TCAs within Y consecutive collection intervals) per monitored parameter type. [unknown NE, unknown parameters, interval count too large, comm failure, unknown managed entity, equipment failure]. The supplier management system also supports administrative functions of retrieval concerning settings of sliding window parameters [unknown managed entity, unknown NE, unknown parameters]. + +This use case ends when root cause impairment information has been logged and any suitable quality of service alarm notification has been prepared. + +**Exceptions:** Unknown NE, unknown parameters, interval count too large, comm failure, unknown managed entity, equipment failure. + +**Post-conditions:** Root cause impairment data is available for retrieval from the supplier management system and quality of service alarms can be raised to an external event channel. + +#### **6.2.2.25 Scheduler** + +**Summary:** The supplier management system provides a scheduler function for activities to be carried out at a later date. The operator or OMS can create a new schedule, suspend/resume a schedule, view a schedule and delete or modify an existing schedule if it is not in use. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. A communication link exists between the operator or OMS and the supplier management system. + +The supplier management system has authenticated the operator or OMS to access the scheduling function. + +**Actors:** Operator or OMS. + +**Preconditions:** The supplier management system is installed. + +**Description:** This use case begins when the OMS or operator initiates a request to create a new schedule. To create a new schedule, the following parameters are included: schedule name, start and stop times for when the schedule can be applied, schedule trigger point times matrix, and the periodicity of the schedule [duplicate user label, matrix scheduler type mismatch, invalid start time, invalid stop time, invalid trigger]. + +Once the schedule is created, the OMS or operator can schedule an activity such as NE MIB uploading, bulk transfer, testing or synchronization activity simply by referencing the schedule name. The scheduled activity is in pending mode prior to the trigger time, and in progress mode until it is successfully (or unsuccessfully) completed. + +The operator or OMS can retrieve information on the schedule. The returned information includes scheduler name, start time, stop time, trigger point times, matrix, operational state and administrative state [unknown scheduler]. The supplier management system also supports the operator's need to suspend or resume activities via reference to the schedule. The supplier management system is able to suspend/resume a scheduled activity by locking/unlocking the administrative state of the associated schedule [unknown scheduler]. The operator can also delete or modify an existing schedule that is not in use [unknown scheduler, schedule in use, invalid start time, invalid stop time, matrix scheduler type mismatch, invalid trigger, duplicate user label]. + +This use case ends when a schedule has been created, modified or deleted. + +**Exceptions:** Unknown scheduler, schedule in use, duplicate user label, matrix scheduler type mismatch, invalid start time, invalid stop time, invalid trigger. + +**Post-conditions:** Invocation of routine management activities can be supported by the supplier management system based on any established active schedulers. + +#### 6.2.2.26 Synchronize NE + +**Summary:** The supplier management system is responsible for providing synchronization and consistency between all physical and logical BPON network resource data. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. The management communications channel between the BPON resource is available. The supplier management system maintains an information model that captures the configuration data in a BPON system. This information model should reflect the current provisioned state of the BPON system. As provisioning changes are made in the network the information model is updated to reflect the latest changes. These changes may occur by the operator provisioning something through the supplier management system, or through a craftsperson provisioning changes in the field. + +**Actors:** BPON NEs, privileged user. + +**Preconditions:** The supplier management system is installed and is designed to normally remain in synch with the configuration of the BPON NEs within its management jurisdiction. + +**Description:** This use case begins when the privileged user suspects that the supplier management system and BPON NE are out of synch with each other. The privileged user formulates a request for synchronization naming the BPON NE. The supplier management system responds to the request by updating its management information with the latest information obtained by retrieving all configuration data from the BPON NE [comm failure, unknown NE, equipment failure, backup in progress, synch in progress]. While this process is active it is assumed that other management activities involving the BPON NE are blocked. + +If the synchronization proves to be disruptive to management operations (taking too long), then it is possible for the privileged user to abort the synchronization process. Any inconsistencies between the supplier management system and the NE that have been resolved before the abort are retained. + +Similar functionality is invoked automatically whenever there is an event denoting a DCN connection establishment or recovery, a remote reset of a BPON NE, an ONT or ONU ranging, or a resynchronization of a current event listing. When an ONT is ranged, it is assumed that the OLT will automatically update its local ONT configuration to reflect the state of the ONT. This means that the supplier management system will use the range event to trigger an upload of the ONT data from the OLT. + +Each time the process is initiated, an NE will be selected for synchronization. The process will initiate an upload of data from the NE. This will be a vendor-specific implementation. + +The next step in the sequence is to reconcile the data retrieved from the NE with the current state of the information model. If there is any difference in any data stewarded by the NE, then the model will be updated and (if business rules apply) attribute value change information will be formatted and made available as published notifications to any interested operator or OMS. As updates are made to the information model, events will also be generated in the system. If there is any difference in any data stewarded by the supplier management system, then the supplier management system issues configuration change requests to the NE. + +The process will conclude by returning a value to the initiator (internal procedure) that indicates that the synchronization process was successfully completed, and the information model was updated. + +A privileged user can also request routine resynchronization of NE and supplier management system management information. The request includes the identification of the BPON NE and reference to the schedule [unknown NE, unknown scheduler, invalid scheduler]. The privileged user can modify the scheduled activity as well as cancel it [unknown NE, unknown scheduler, invalid scheduler]. + +This user case ends when supplier management system and the BPON NE are in synch. + +**Exceptions:** Comm failure, unknown scheduler, unknown NE, equipment failure, backup in progress, synch in progress. + +**Post-conditions:** Management information resident in installed BPON NEs is consistent with the same information resident in the supplier management system. + +#### **6.2.2.27 View records** + +**Summary:** The supplier management system will provide means to view all logged events or other records archived temporarily at the supplier management system. It will also provide a way to retrieve a subset of records on behalf of an OMS. + +**Assumptions:** The supplier management system has authenticated the requesting operator or OMS. Selection filters have been specified and implemented. + +**Actors:** Operator and OMS. + +**Preconditions:** The supplier management system has been archiving performance and traffic measurements and recording event notifications in logs. + +**Description:** This use case begins when the operator or OMS initiates a request to select records from a particular record set for further evaluation. The request identifies the record set and provides selection criteria. The selection criteria may include such parameters as: + +- Managed entity Id. +- Time interval. +- Record type. + +The supplier management system will process the retrieval request and find the records contained in the record set that meet the selection criterion. The listing of records will be returned to the requestor [unknown record set, timeout, no such records, too many records]. + +The OMS may query for the size of any existing record set [unknown record set]. + +This use case ends when the records or status of a record set information has been provided to the requesting operator or OMS. + +**Exceptions:** Unknown record set, timeout, no such records, too many records. + +**Post-conditions:** The records are available for reviewing by the operator, or for processing by the OMS. + +## 6.3 Analysis + +Detailed class, sequence and state change diagrams will be offered only for those situations where an interface to an external actor exists, or for those cases that these details are necessary to explain behaviour. Each section of the analysis begins with a high-level view of the classes involved in the high-level use case diagrams of clause 6.2.1.3 with details of specific use cases following this summary. This is followed by references to any managed entities (the management information data structures from [ITU-T Q.834.1] and [ITU-T Q.834.2]) that may be involved in the use case. In some cases, the references to managed entities is followed by a listing to "management support entities" referring to familiar entities from existing ITU-T Recommendations. Next follows signatures for any real time operations between an external actor and the supplier management system. This information is accompanied by a brief description of each exception raised by the operations listed. Finally, users of this Recommendation may assume that every operation is atomic except where indicated as "best effort". + +### 6.3.1 Access control + +The following class diagram show interactions between actors and classes internal to the supplier management system when administering user access to the supplier management system. + +#### 6.3.1.1 Administer user privileges + +![UML class diagram for Administer user privileges showing AccessControlMgr, UserGroup, User, and Factory classes with their attributes, methods, and relationships.](3c6151f296d5800335472b7dc00ce423_img.jpg) + +``` +classDiagram + class PrivilegedUser { + <> + } + class AccessControlMgr { + +UserList + +UserGroupList + +PasswordPolicy + +setPasswordPolicy() + +passwordPolicyGet() + +userListGet() + +userGroupListGet() + +userGet() + +userGroupGet() + +createUserGroup() + +modifyUserGroup() + +deleteUserGroup() + +addUsersToGroup() + +deleteUsersFromGroup() + +getPermissionList() + +modifyPermissionList() + +createUser() + +deleteUser() + +resetPassword() + } + class UserGroup { + +MemberUserIds + +addMember() + +deleteMember() + +retrieveMembers() + +create() + +modifyTargetActivities() + +delete() + } + class User { + +UserId + +TargetActivities + +GroupMembership + +Password + +create() + +modifyUserTargets() + +retrieveGroupIds() + +retrieveUserTargetActivities() + +delete() + +resetPassword() + +modifyUserGroupMembership() + } + class Factory { + +create() + +delete() + } + PrivilegedUser --> AccessControlMgr : controls GUI user access + AccessControlMgr --> UserGroup : administers + AccessControlMgr --> Factory : commissions + UserGroup --> User : belongs to +``` + +The diagram illustrates the classes and relationships for administering user privileges. It includes a stick figure actor, three class boxes, and one factory box. + +- Privileged User** (Actor): Interacts with **AccessControlMgr** via the relationship "controls GUI user access". +- AccessControlMgr** (Class): + - Attributes: `UserList`, `UserGroupList`, `PasswordPolicy`. + - Methods: `setPasswordPolicy()`, `passwordPolicyGet()`, `userListGet()`, `userGroupListGet()`, `userGet()`, `userGroupGet()`, `createUserGroup()`, `modifyUserGroup()`, `deleteUserGroup()`, `addUsersToGroup()`, `deleteUsersFromGroup()`, `getPermissionList()`, `modifyPermissionList()`, `createUser()`, `deleteUser()`, `resetPassword()`. +- UserGroup** (Class): + - Attribute: `MemberUserIds`. + - Methods: `addMember()`, `deleteMember()`, `retrieveMembers()`, `create()`, `modifyTargetActivities()`, `delete()`. +- User** (Class): + - Attributes: `UserId`, `TargetActivities`, `GroupMembership`, `Password`. + - Methods: `create()`, `modifyUserTargets()`, `retrieveGroupIds()`, `retrieveUserTargetActivities()`, `delete()`, `resetPassword()`, `modifyUserGroupMembership()`. +- Factory** (Class): + - Methods: `create()`, `delete()`. + +Relationships: + +- AccessControlMgr** *administers* **UserGroup**. +- AccessControlMgr** *commissions* **Factory**. +- UserGroup** *belongs to* **User**. + +UML class diagram for Administer user privileges showing AccessControlMgr, UserGroup, User, and Factory classes with their attributes, methods, and relationships. + +Figure 6-11 – Administer user privileges class diagram + +![UML sequence diagram for creating a user and user group. The diagram shows interactions between a Privileged User, AccessControlMgr, User, UserGroup, User:Factory, and UserGroup:Factory. The process includes password policy management, user creation, password reset, user group creation, target activity modification, and group membership management.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +``` + +sequenceDiagram + actor PU as : Privileged User + participant ACM as : AccessControlMgr + participant U as : User + participant UG as : UserGroup + participant UF as User : Factory + participant UGF as User Group : Factory + + PU->>ACM: passwordPolicyGet() + activate ACM + deactivate ACM + PU->>ACM: setPasswordPolicy() + activate ACM + deactivate ACM + PU->>ACM: createUser() + activate ACM + ACM->>UF: create() + activate UF + deactivate UF + ACM->>U: resetPassword() + activate U + deactivate U + deactivate ACM + PU->>ACM: createUserGroup() + activate ACM + ACM->>UGF: create() + activate UGF + deactivate UGF + ACM->>UG: modifyTargetActivities() + activate UG + deactivate UG + deactivate ACM + PU->>ACM: addUsersToGroup() + activate ACM + ACM->>UG: addMember() + activate UG + UG->>UGF: modifyUserGroupMembership() + activate UGF + UGF->>U: modifyUserTargets() + activate U + deactivate U + deactivate UGF + deactivate UG + deactivate ACM + +``` + +UML sequence diagram for creating a user and user group. The diagram shows interactions between a Privileged User, AccessControlMgr, User, UserGroup, User:Factory, and UserGroup:Factory. The process includes password policy management, user creation, password reset, user group creation, target activity modification, and group membership management. + +Figure 6-12 – Create user and user group sequence diagram + +![UML sequence diagram for 'Modify user permissions' involving actors and objects: Privileged User, AccessControlMgr, User, and UserGroup. The diagram shows two main paths: one for modifying permissions by group and another for modifying permissions individually. The 'Modify by group' path includes calls to userGet(), userGroupGet(), modifyUserGroup(), modifyTargetPermissions(), and modifyUserTargets(). The 'Modify individually' path includes calls to getPermissions(), reIssueUserTargetActivities(), modifyPermissions(), and modifyUserTargets(). The 'Modify by group membership' path includes calls to addUsersToGroup(), addMember(), modifyUserGroupMembership(), and modifyUserTargets().](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +``` + +sequenceDiagram + actor PU as : Privileged User + participant ACM as : AccessControlMgr + participant U as : User + participant UG as : UserGroup + + PU->>ACM: userGet() + activate ACM + ACM->>U: reIssueGroupIds() + activate U + U->>ACM: reIssueUserTargetActivities() + deactivate U + ACM->>U: reIssueGroupIds() + deactivate ACM + deactivate U + + PU->>ACM: userGroupGet() + activate ACM + ACM->>U: reIssueGroupIds() + activate U + U->>ACM: reIssueGroupIds() + deactivate U + ACM->>U: reIssueGroupIds() + deactivate ACM + deactivate U + + Note left of PU: Modify by Group permissions modification. + PU->>ACM: modifyUserGroup() + activate ACM + ACM->>U: modifyTargetPermissions() + activate U + U->>UG: modifyUserTargets() + activate UG + UG->>U: modifyUserTargets() + deactivate UG + U->>ACM: modifyUserTargets() + deactivate U + ACM->>U: modifyUserTargets() + deactivate ACM + deactivate U + + Note left of PU: Modify Individually. + PU->>ACM: getPermissions() + activate ACM + ACM->>U: reIssueUserTargetActivities() + activate U + U->>ACM: reIssueUserTargetActivities() + deactivate U + ACM->>U: reIssueUserTargetActivities() + deactivate ACM + deactivate U + + PU->>ACM: modifyPermissions() + activate ACM + ACM->>U: modifyUserTargets() + activate U + U->>ACM: modifyUserTargets() + deactivate U + ACM->>U: modifyUserTargets() + deactivate ACM + deactivate U + + Note left of PU: Modify by group membership. + PU->>ACM: addUsersToGroup() + activate ACM + ACM->>U: addMember() + activate U + U->>UG: modifyUserGroupMembership() + activate UG + UG->>U: modifyUserTargets() + activate U + U->>ACM: modifyUserTargets() + deactivate U + ACM->>U: modifyUserTargets() + deactivate ACM + deactivate U + deactivate UG + deactivate U + deactivate ACM + +``` + +UML sequence diagram for 'Modify user permissions' involving actors and objects: Privileged User, AccessControlMgr, User, and UserGroup. The diagram shows two main paths: one for modifying permissions by group and another for modifying permissions individually. The 'Modify by group' path includes calls to userGet(), userGroupGet(), modifyUserGroup(), modifyTargetPermissions(), and modifyUserTargets(). The 'Modify individually' path includes calls to getPermissions(), reIssueUserTargetActivities(), modifyPermissions(), and modifyUserTargets(). The 'Modify by group membership' path includes calls to addUsersToGroup(), addMember(), modifyUserGroupMembership(), and modifyUserTargets(). + +Figure 6-13 – Modify user permissions sequence diagram + +![Sequence diagram for deleting users and user groups. The diagram shows interactions between a Privileged User, AccessControlMgr, User, UserGroup, User Factory, and User Group Factory. The Privileged User initiates deleteUser() and deleteUserGroup(). AccessControlMgr handles these by calling modifyUserGroupMembership() and deleteMember() on User, and delete() on UserGroup and User Factory. It also calls userGroupGet() on User Group Factory.](89f8aefc01866631793087542316cef2_img.jpg) + +``` + +sequenceDiagram + actor PU as Privileged User + participant ACM as : AccessControlMgr + participant U as : User + participant UG as : UserGroup + participant UF as User : Factory + participant UGF as User Group : Factory + + PU->>ACM: deleteUser() + activate ACM + ACM->>U: modifyUserGroupMembership() + activate U + U->>UG: deleteMember() + activate UG + UG->>UF: delete() + deactivate UG + ACM->>UGF: delete() + deactivate U + deactivate UG + deactivate UF + deactivate ACM + + PU->>ACM: userGroupGet() + activate ACM + ACM->>UGF: userGroupGet() + activate UGF + deactivate ACM + + PU->>ACM: deleteUserGroup() + activate ACM + ACM->>UGF: delete() + activate UGF + deactivate ACM + deactivate UGF + +``` + +Sequence diagram for deleting users and user groups. The diagram shows interactions between a Privileged User, AccessControlMgr, User, UserGroup, User Factory, and User Group Factory. The Privileged User initiates deleteUser() and deleteUserGroup(). AccessControlMgr handles these by calling modifyUserGroupMembership() and deleteMember() on User, and delete() on UserGroup and User Factory. It also calls userGroupGet() on User Group Factory. + +**Figure 6-14 – Delete users and user groups sequence diagram** + +##### Operations + +| Operation name | Operation purpose | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) setPasswordPolicy | This operation allows the privileged users to manage the password policy. | +| 2) passwordPolicyGet | This operation allows the privileged users to retrieve the policy concerning the syntax of data exchanged and timers used when logging into the supplier management system. | +| 3) userListGet | This operation allows the privileged users to retrieve the list of user Ids having some form of access to the supplier management system as well as their target activities and group memberships. | +| 4) userGroupListGet | This operation allows the privileged users to retrieve the user groups having access to the supplier management system with the members of the group and target activities identified. | +| 5) userGet | This operation allows the privileged users to retrieve the user's group membership and target activities. | +| 6) userGroupGet | This operation allows the privileged users to retrieve the member users of the group and their allowed target activities. | +| 7) createUserGroup | This operation allows the privileged users to create a new user group. | +| 8) modifyUserGroup | This operation allows the privileged users to add/delete the target activities of a user group. | +| 9) deleteUserGroup | This operation allows the privileged users to delete an existing user group. | +| 10) addUsersToGroup | This operation allows the privileged user to add new users to an existing user group. | +| 11) deleteUsersFromGroup | This operation allows the privileged users to delete users from a user group. | +| 12) getPermissionList | This operation allows the privileged users to obtain the list of the activities allowed to a specified user. | +| 13) modifyPermissionList | This operation allows the privileged users to modify the list of the activities allowed to a user. | +| 14) createUser | This operation allows the privileged users to create a new user. | +| 15) deleteUser | This operation allows the privileged users to delete an existing user. | +| 16) resetPassword | This operation allows the privileged users to reset the password for a user. | + +**Figure 6-15 – Access control manager operations** + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|--------------------------|-------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------------------| +| 1) setPasswordPolicy | PasswordPolicyType | void | AccessDenied | +| 2) passwordPolicyGet | | PasswordPolicyType | AccessDenied | +| 3) userListGet | | UserSeqType | AccessDenied | +| 4) userGroupListGet | | UserGroupSeqType | AccessDenied | +| 5) userGet | UserIdType | UserType | AccessDenied,
UnknownUserIds | +| 6) userGroupGet | UserLabelType | UserGroupType | AccessDenied,
UnknownUserGroupId | +| 7) createUserGroup | UserLabelType,
TargetActivitySeqType | void | DuplicateUserGroupId,
UnknownTargets,
AccessDenied | +| 8) modifyUserGroup | UserLabelType,
TargetActivitySeqType,
TargetActivitySeqType | TargetActivitySeqType | UnknownUserGroupId,
UnknownTargets,
AccessDenied | +| 9) deleteUserGroup | UserLabelType | void | AccessDenied,
UserGroupNotEmpty,
UnknownUserGroupId | +| 10) addUsersToGroup | UserLabelType | void | AccessDenied,
UnknownUserGroupId | +| 11) deleteUsersFromGroup | UserLabelType,
UserIdSeqType | void | AccessDenied,
UnknownUserGroupId,
UnknownUserIds | +| 12) getPermissionList | UserIdType | TargetActivitySeqType | UnknownUserIds,
AccessDenied | +| 13) modifyPermissionList | UserIdType,
TargetActivitySeqType,
TargetActivitySeqType | TargetActivitySeqType | UnknownUserIds,
UnknownTargets,
AccessDenied | +| 14) createUser | UserIdType,
PasswordType,
TargetActivitySeqType | void | DuplicateUserId,
UnknownTargets,
AccessDenied,
UserLoginPolicyViolation | +| 15) deleteUser | UserIdType | void | UnknownUserIds,
AccessDenied | +| 16) resetPassword | UserIdType,
PasswordType | void | UnknownUserIds,
UserLoginPolicyViolation,
AccessDenied | + +**Figure 6-16 – Access control manager signatures** + +##### Exceptions + +| Exception raised | Description | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| DuplicateUserGroupId | The Id is already used for another user group. | +| DuplicateUserId | Access control profile has already been established for this user Id. | +| UnknownTargets | List of unknown target activities. | +| UnknownUserGroupId | User group is unknown to the supplier management system. | +| UnknownUserIds | This exception is raised when any user Id is unrecognized. | +| UserLoginPolicyViolation | The specified assignment of a new password to a user violates the user login policy currently enforced by the supplier management system. | +| UserGroupNotEmpty | Non-empty user group cannot be deleted. | + +**Figure 6-17 – Access control manager exceptions** + +### 6.3.2 Event handling + +The following two clauses provide the analysis for the two use cases in Figure 6-5, having interactions with external actors provided by the operator or network owner. + +#### 6.3.2.1 Publish event + +![UML Class Diagram for Publish Event](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` +classDiagram + class NotificationAdmin { + +updateChannels() + +updateFilters() + +updateConnections() + } + class EventForwarder { + +SupplierFilterMatrix + +notifyEventSupplier() + +processAnnouncement() + +updateSupplierFilterMatrix() + } + class EventSupplier { + +subscriptionChange() + +disconnectSupplier() + +pushEvent() + } + class ExternalEventChannel { + +push() + +getSupplierAdmin() + +connectSupplier() + +obtainSubscription() + } + class WhitePages { + +resolve() + } + + NotificationAdmin --> EventForwarder : updates event supplier info + EventForwarder --> EventSupplier : pushes events + EventSupplier --> NotificationAdmin : updates external forwarding + EventSupplier --> ExternalEventChannel : pushes events + EventSupplier --> WhitePages : looks up name +``` + +The diagram illustrates the 'Publish event' process with the following components and interactions: + +- NotificationAdmin**: Contains methods `updateChannels()`, `updateFilters()`, and `updateConnections()`. It sends the message *updates event supplier info* to **EventForwarder**. +- EventForwarder**: Contains a `SupplierFilterMatrix` object and methods `notifyEventSupplier()`, `processAnnouncement()`, and `updateSupplierFilterMatrix()`. It sends the message *pushes events* to **EventSupplier**. +- EventSupplier**: Contains methods `subscriptionChange()`, `disconnectSupplier()`, and `pushEvent()`. It sends the message *updates external forwarding* to **NotificationAdmin** and *pushes events* to **External Event Channel**. It also sends the message *looks up name* to **White Pages**. +- External Event Channel**: Contains methods `push()`, `getSupplierAdmin()`, `connectSupplier()`, and `obtainSubscription()`. +- White Pages**: Contains the method `resolve()`. + +UML Class Diagram for Publish Event + +Figure 6-18 – Publish event class diagram + +![UML sequence diagram for 'Publish event' showing interactions between White Pages, External Event Channel, Event Supplier, Event Forwarder, and Notification Admin.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +``` + +sequenceDiagram + participant WP as : White Pages + participant EEC as : External Event Channel + participant ES as : Event Supplier + participant EF as : Event Forwarder + participant NA as : Notification Admin + + WP->>EEC: resolve() + activate EEC + EEC->>ES: updateChannels() + activate ES + ES->>EEC: obtainSubscription() + deactivate ES + activate EEC + EEC->>ES: getSupplierAdmin() + activate ES + ES->>NA: updateFilters() + deactivate ES + activate NA + NA->>EEC: connectSupplier() + deactivate NA + activate EEC + EEC->>ES: updateConnections() + activate ES + ES->>EF: updateSupplierFilterMatrix() + deactivate ES + activate EF + EF->>NA: processAnnouncement() + deactivate EF + activate NA + NA->>EF: + deactivate NA + EF->>ES: pushEvent() + activate EF + EF->>EEC: push() + deactivate EF + deactivate ES + deactivate EEC + EEC->>ES: disconnectSupplier() + activate EEC + activate ES + ES->>EF: updateConnections() + deactivate ES + activate EF + EF->>NA: updateSupplierFilterMatrix() + deactivate EF + activate NA + NA->>EF: processAnnouncement() + deactivate NA + EF->>EF: + deactivate EF + deactivate ES + deactivate EEC + +``` + +The diagram illustrates the sequence of operations for publishing an event. It involves five participants: **: White Pages**, **: External Event Channel**, **: Event Supplier**, **: Event Forwarder**, and **: Notification Admin**. The process begins with **: White Pages** calling **resolve()** on **: External Event Channel**. This triggers a series of updates and connections: **: External Event Channel** calls **updateChannels()** on **: Event Supplier**, which then calls **obtainSubscription()** back on **: External Event Channel**. Next, **: External Event Channel** calls **getSupplierAdmin()** on **: Event Supplier**, which calls **updateFilters()** on **: Notification Admin**. **: Notification Admin** then calls **connectSupplier()** on **: External Event Channel**, which calls **updateConnections()** on **: Event Supplier**. **: Event Supplier** calls **updateSupplierFilterMatrix()** on **: Event Forwarder**, which calls **processAnnouncement()** on **: Notification Admin**. **: Notification Admin** returns to **: Event Forwarder**, which then calls **pushEvent()** on **: Event Supplier**. **: Event Supplier** calls **push()** on **: External Event Channel**. **: External Event Channel** then calls **disconnectSupplier()** on **: Event Supplier**, which calls **updateConnections()** on **: Event Forwarder**. **: Event Forwarder** calls **updateSupplierFilterMatrix()** on **: Notification Admin**, which calls **processAnnouncement()** on **: Event Forwarder**. Two notes are present: one stating "As announcements arrive, events are pushed." pointing to the **pushEvent()** call, and another stating "If communications are to be suppressed." pointing to the **disconnectSupplier()** call. + +UML sequence diagram for 'Publish event' showing interactions between White Pages, External Event Channel, Event Supplier, Event Forwarder, and Notification Admin. + +Figure 6-19 – Publish event sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------| +| 1) obtainConsumers | This operation allows the supplier management system to determine the names of the OMSs that consume event notifications. | +| 2) connectSupplier | This operation allows the supplier management system to connect to the external event channel. | +| 3) push | This operation allows the supplier management system to push an event notification to the external event channel. | +| 4) obtainSubscription | This operation allows the supplier management system to determine the type of events to be pushed on the external event channel. | +| 5) disconnectSupplier | This operation allows the supplier management system to be disconnected from the external event channel. | +| 6) getSupplierAdmin | This operation allows the supplier management system to administer its event supplier function. | + +**Figure 6-20 – Event publisher operations** + +| Operation name | Input parameters | Return value | Exceptions | +|-----------------------|---------------------|------------------------|--------------------------------| +| 1) obtainConsumers | | NameType | AccessDenied | +| 2) connectSupplier | NameType | | AccessDenied, AlreadyConnected | +| 3) push | StructuredEventType | void | Disconnected, AccessDenied | +| 4) obtainSubscription | | StructuredEventSeqType | AccessDenied | +| 5) disconnectSupplier | NameType | void | AccessDenied | +| 6) getSupplierAdmin | | sequence of long | AccessDenied | + +**Figure 6-21 – Event publisher signatures** + +##### Exceptions + +| Exception raised | Description | +|------------------|---------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| AlreadyConnected | The communicating object is already connected to the event channel. | +| Disconnected | The object was disconnected from the event channel. | +| InvalidEventType | The subscription change identified an invalid event type. | + +**Figure 6-22 – Event publisher exceptions** + +#### 6.3.2.2 Root cause impairment analysis + +![UML Class Diagram for Root cause impairment analysis. The diagram shows the interactions between various components including Profile Object Repository, BPON NE, Impairment Persistence, Event Set Manager, Event Correlator, Event Queue, Event Set, QoS Log, and Event Forwarder. It details methods like retrieve(), setThreshold(), and processAnnouncement() and their relationships.](0ccaa59b5bc46884777e728ee3dadaa7_img.jpg) + +``` + +classDiagram + class ProfileObjectRepository { + retrieve() + } + class BPONNE { + setValues() + getValues() + } + class ImpairmentPersistence { + setSlidingWindowParameters() + setSpecificSlidingWindowParameters() + getSpecificSlidingWindowParameters() + setThreshold() + setThresholds() + getThresholdValues() + getSystemThresholdsSetting() + getSystemSWSettings() + } + class EventSetManager { + Scheduler + notify() + deleteEventSet() + } + class EventCorrelator { + supersedeFilterings() + addDependencyRelationshipInfo() + groupWithSameDependentResource() + removeGroupRedundancy() + patternToSupportingResource() + } + class EventQueue { + addEvents() + selectEvents() + } + class EventSet { + EventSetId + RetrievalCriteria + TimeWindow + setAttributes() + fillWithNewEvents() + create() + delete() + purge() + completeEventRecord() + } + class QoSLog { + Scheduler + XYMatrix + storeRecord() + calcPersistence() + addRemoveMatrixRow() + clockTrigger() + getXYMatrixRows() + } + class EventForwarder { + processAnnouncement() + } + class Clock + class ManagementModelMaintainer + + ProfileObjectRepository --> ImpairmentPersistence : retrieves Threshold Data + ImpairmentPersistence --> ProfileObjectRepository : provisions thresholds + ImpairmentPersistence --> OMSOperator : sets threshold parameters + ImpairmentPersistence --> ManagementModelMaintainer : modify properties of monitoring points + ImpairmentPersistence --> QoSLog : set counter parameters + BPONNE --> EventScreening : sends TCA event + class EventScreening { + readEvents() + validates() + } + EventScreening --> EventSetManager : notifies + EventSetManager --> EventSet : creates + EventScreening --> EventQueue : queues to + EventSet --> EventQueue : extracts from + EventSet --> EventCorrelator : obtains correlation + EventSet --> QoSLog : logs root cause TCAs + Clock --> QoSLog : periodically triggers + QoSLog --> EventForwarder : announce QoS alarm + +``` + +The diagram illustrates the root cause impairment analysis process. Key components and their interactions are as follows: + +- Profile Object Repository** and **BPON NE** interact with **Impairment Persistence** for threshold data retrieval and provisioning. +- Impairment Persistence** manages threshold parameters and interacts with **OMS/Operator** and **Management Model Maintainer**. +- BPON NE** sends TCA events to the **Event Screening** component. +- Event Screening** notifies the **Event Set Manager** and queues events to the **Event Queue**. +- The **Event Set Manager** creates **Event Set** objects. +- The **Event Set** extracts events from the **Event Queue** and obtains correlation from the **Event Correlator**. +- The **Event Set** logs root cause TCAs into the **QoS Log**. +- The **QoS Log** is periodically triggered by the **Clock** and announces QoS alarms to the **Event Forwarder**. + +UML Class Diagram for Root cause impairment analysis. The diagram shows the interactions between various components including Profile Object Repository, BPON NE, Impairment Persistence, Event Set Manager, Event Correlator, Event Queue, Event Set, QoS Log, and Event Forwarder. It details methods like retrieve(), setThreshold(), and processAnnouncement() and their relationships. + +Figure 6-23 – Root cause impairment analysis class diagram + +![UML sequence diagram for 'Setting of parameters' involving OMS/Operator, ImpairmentPersistence, BPON NE, and QoSLog.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant IP as : ImpairmentPersistence + participant BPN as : BPON NE + participant QSL as : QoSLog + + OMS->>IP: setThresholds() + activate IP + IP->>BPN: setValues() + deactivate IP + BPN-->>QSL: + Note right of QSL: As many times... + OMS->>IP: setSlidingWindowParameters() + activate IP + IP->>QSL: addRemoveMatrixRow() + deactivate IP + OMS->>IP: getSystemThresholdsSetting() + activate IP + deactivate IP + OMS->>IP: getSystemSWSettings() + activate IP + deactivate IP + OMS->>IP: setThreshold() + activate IP + IP->>BPN: setValues() + deactivate IP + BPN-->>QSL: + Note right of QSL: For all monitoring points of specific type. + OMS->>IP: getThresholdValues() + activate IP + IP->>BPN: getValues() + deactivate IP + BPN-->>QSL: + Note right of QSL: For all monitoring points monitoring the specific parameter. + OMS->>IP: getSpecificSlidingWindowParameters() + activate IP + IP->>QSL: getXYMatrixRows() + deactivate IP + +``` + +The diagram illustrates the sequence of operations for setting parameters. It involves four participants: : OMS/Operator (Actor), : ImpairmentPersistence (Boundary), : BPON NE (Entity), and : QoSLog (Control). The sequence begins with the OMS/Operator sending a `setThresholds()` message to ImpairmentPersistence. ImpairmentPersistence then sends a `setValues()` message to BPON NE. A dashed arrow from BPON NE to QoSLog is annotated with a note: "As many times...". Next, the OMS/Operator sends `setSlidingWindowParameters()` to ImpairmentPersistence, which sends `addRemoveMatrixRow()` to QoSLog. This is followed by two self-call messages from the OMS/Operator to ImpairmentPersistence: `getSystemThresholdsSetting()` and `getSystemSWSettings()`. Then, the OMS/Operator sends `setThreshold()` to ImpairmentPersistence, which sends `setValues()` to BPON NE. A dashed arrow from BPON NE to QoSLog is annotated with a note: "For all monitoring points of specific type.". The OMS/Operator then sends `getThresholdValues()` to ImpairmentPersistence, which sends `getValues()` to BPON NE. Another dashed arrow from BPON NE to QoSLog is annotated with a note: "For all monitoring points monitoring the specific parameter.". Finally, the OMS/Operator sends `getSpecificSlidingWindowParameters()` to ImpairmentPersistence, which sends `getXYMatrixRows()` to QoSLog. + +UML sequence diagram for 'Setting of parameters' involving OMS/Operator, ImpairmentPersistence, BPON NE, and QoSLog. + +Figure 6-24 – Setting of parameters sequence diagram + +![Sequence diagram for RCIA showing interactions between ImpairmentPers..., BPON NE, Event Screener, EventDelete, EventSet Manager, EventSet, Event Correlator, QoSLog, EventForwarder, and Clock. The diagram illustrates the flow of events and data processing, including operations like readEvents(TCA), addEvents(), notify(), create(), selectEvents(), addDependencyRelationship(), groupWithSameDependencyResource(), removeGroupDependency(), supersedeFilterings(), patternToSupportingResource(), completeEventRecord(), storeRecord(), deleteEventSet(), purge(), delete(), clockTrigger(), calcPersistence(), and processAnnouncement().](7e14467740b2570a44379b347a697921_img.jpg) + +``` + +sequenceDiagram + participant ImpairmentPers... as :ImpairmentPers... + participant BPON NE as :BPON NE + participant Event Screener as :Event Screener + participant EventDelete as :EventDelete + participant EventSet Manager as :EventSet Manager + participant EventSet as :EventSet + participant Event Correlator as :Event Correlator + participant QoSLog as :QoSLog + participant EventForwarder as :EventForwarder + participant Clock as :Clock + + ImpairmentPers...->>BPON NE: setValues() + activate BPON NE + BPON NE->>Event Screener: readEvents(TCA) + activate Event Screener + Event Screener->>EventDelete: addEvents() + activate EventDelete + EventDelete->>EventSet Manager: notify() + activate EventSet Manager + EventSet Manager->>EventSet: create() + activate EventSet + EventSet->>Event Correlator: selectEvents() + activate Event Correlator + Event Correlator->>Event Correlator: addDependencyRelationship() + Event Correlator->>Event Correlator: groupWithSameDependencyResource() + Event Correlator->>Event Correlator: removeGroupDependency() + Event Correlator->>Event Correlator: supersedeFilterings() + Event Correlator->>Event Correlator: patternToSupportingResource() + Event Correlator->>Event Correlator: completeEventRecord() + Event Correlator->>QoSLog: storeRecord() + deactivate Event Correlator + Event Correlator->>EventSet Manager: deleteEventSet() + activate EventSet Manager + EventSet Manager->>EventSet: purge() + deactivate EventSet Manager + EventSet->>EventSet: delete() + deactivate EventSet + Event Correlator->>Clock: clockTrigger() + activate Clock + Clock->>EventForwarder: calcPersistence() + activate EventForwarder + EventForwarder->>EventForwarder: processAnnouncement() + deactivate EventForwarder + deactivate Clock + +``` + +Sequence diagram for RCIA showing interactions between ImpairmentPers..., BPON NE, Event Screener, EventDelete, EventSet Manager, EventSet, Event Correlator, QoSLog, EventForwarder, and Clock. The diagram illustrates the flow of events and data processing, including operations like readEvents(TCA), addEvents(), notify(), create(), selectEvents(), addDependencyRelationship(), groupWithSameDependencyResource(), removeGroupDependency(), supersedeFilterings(), patternToSupportingResource(), completeEventRecord(), storeRecord(), deleteEventSet(), purge(), delete(), clockTrigger(), calcPersistence(), and processAnnouncement(). + +Figure 6-25 – RCIA sequence diagram + +##### Operations + +| Operation name | Input parameters | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) setSlidingWindowParameters | This operation sets the sliding window parameters for one, some or all monitored parameters in an NE. | +| 2) setSpecificSlidingWindowParameters | This operation is similar to the operation setSlidingWindowParameters except the scope of assignment of settings is limited to a specific monitoring point identified in the operation. | +| 3) getSpecificSlidingWindowParameters | This operation provides a listing of monitoring points and their sliding window settings for a specified parameter. | +| 4) setThreshold | This operation sets the threshold value identified by a profile to a monitoring point in a network element. | +| 5) setThresholds | This operation allows the setting of a collection of threshold value, monitoringPointType pairs on a particular NE. | +| 6) getThresholdValues | This operation provides a listing of monitoring points and their threshold data setting names for a specified monitoring point type. | +| 7) getSystemThresholdsSetting | This operation retrieves the system default values for threshold data. | +| 8) getSystemSWSettings | This operation retrieves the system default sliding window settings. | + +Figure 6-26(a) – Impairment persistence operations + +##### Operation signatures7 + +| Operation name | Input parameters | Return value | Exceptions | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 1) setSlidingWindowParameters | ManagedEntityType (NE),
MonitoredParameterSeqType,
short (total consecutive intervals),
short (minimum persistence) | void | UnknownNE,
UnknownParameters,
IntervalCountTooLarge,
AccessDenied,
CommFailure | +| 2) setSpecificSlidingWindowParameters | ManagedEntityType (NE),
ManagedEntityType (Monitoring Point),
MonitoredParameterSeqType,
short (total consecutive intervals),
short (minimum persistence) | void | UnknownNE,
UnknownParameters,
IntervalCountTooLarge,
AccessDenied,
UnknownManagedEntity,
CommFailure,
EquipmentFailure | +| 3) getSpecificSlidingWindowParameters | ManagedEntityType (NE),
MonitoredParameterType | SWPValueSeqType | UnknownNE,
UnknownParameters,
CommFailure | +| 4) setThreshold | ManagedEntityType (NE),
ManagedEntityType (monitoring point),
NameType (threshold data profile) | void | UnknownNE,
AccessDenied,
UnknownManagedEntity,
UnknownProfiles,
InvalidAssociation,
CommFailure,
ProfileSuspended | +| 5) setThresholds | ManagedEntityType (NE),
boolean (system scope),
ThresholdsSeqType | void | UnknownNE,
UnknownProfiles,
AccessDenied,
UnknownMonitoringPoint Types,
InvalidAssociation,
CommFailure,
ProfileSuspended | +| 6) getThresholdValues | ManagedEntityType (NE),
MonitoringKindType | MonitoringPoint ThresholdsSeqType | UnknownNE,
UnknownMonitoringPoint Types,
CommFailure | +| 7) getSystemThresholdsSetting | ManagedEntityType (NE) | ThresholdsSeqType | AccessDenied,
UnknownManagedEntity | +| 8) getSystemSWSettings | ManagedEntityType (NE) | ParameterSetting SeqType | AccessDenied,
UnknownManagedEntity | + +**Figure 6-26(b) – Impairment persistence signatures** + +7 The "set" operations listed above modify (overwrite) an existing X,Y sliding window specification. If no such specification exists for the monitored parameter, then the "set" operations are viewed to be additional specifications. + +##### Exceptions + +| Exception raised | Description | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| EquipmentFailure | The NE currently has a failure condition preventing the requested transaction from being completed. | +| IntervalCountTooLarge | The exception is raised when the requested intervals exceeds the maximum supported by the supplier management system. The exception indicates the maximum allowed monitoring intervals supported by the supplier management system. | +| InvalidAssociation | The given profile cannot be applied to a monitoring point. | +| ProfileSuspended | This exception is raised if the profile name provided is unknown to the supplier management system and cannot be retrieved from the profile object repository. | +| UnknownManagedEntity | The specified managed entity is unknown to the supplier management system. | +| UnknownMonitoringPointTypes | The monitoring point instance provided on the request is unknown to the supplier management system. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownParameters | The given monitored parameter is unknown in the supplier management system. | +| UnknownProfiles | System is not granted access to this interface object. | + +**Figure 6-27 – Impairment persistence exceptions** + +### 6.3.3 Software and configuration data + +#### 6.3.3.1 Download and activate NE software + +![UML class diagram for Distribute NE software. The diagram shows classes: RecordSetMgr, Log, DownloadLogRecord, DownloadMgr, Event Supplier, Event Forwarder, Clock, Factory, Version Repository, and actors: OMS/Operator, BPON NE, and Secure File Server. Relationships include: RecordSetMgr obtains records from Log and selects records; Log stores, finds, displays by key, and displays records; DownloadMgr updates Log, views Log, plans NE software loading, and acts as a coordinator for BPON NE; BPON NE delivers to DownloadMgr; DownloadMgr announces to Event Forwarder, triggers Clock, commissions Factory, and designates software set source to Secure File Server; Event Forwarder pushes event notification to Event Supplier, which then pushes to External Event Channel; Version Repository validates version from DownloadMgr and has methods for update, retrieve, validate NE, and validate PlugIn.](3ce04f1c7128814978c6b34d654a25cc_img.jpg) + +``` +classDiagram + class RecordSetMgr { + +selectRecords() + } + class Log { + +storeRecord() + +findRecords() + +displayByKey() + +displayRecords() + } + class DownloadLogRecord + class DownloadMgr { + +Scheduled Software Download Tracking Object List + +On Demand Software Download Tracking Object List + +Software Load Target Mapping + +deliverDistSWGlobal() + +deliverDistSWSpecific() + +deleteSoftwareDownloadTrackingObject() + +commit() + +activate() + +revert() + +getStatus() + +scheduleDeliverDist() + +scheduleCommit() + +scheduleActivate() + +cancelScheduledSoftwareActivity() + +scheduledSoftwareDownloadTrackingObjectListGet() + +onDemandSoftwareDownloadTrackingObjectListGet() + } + class EventSupplier { + +pushEvent() + } + class EventForwarder { + +processAnnouncement() + } + class Clock + class Factory { + +create() + +delete() + } + class VersionRepository { + +updateSWVersion() + +retrieveVersions() + +validateNEVersion() + +validatePlugInVersion() + } + class OMSOperator[OMS/Operator] + class BPONNE[BPON NE] + class SecureFileServer[Secure File Server] + + RecordSetMgr --> Log : obtains records + RecordSetMgr --> RecordSetMgr : selectRecords() + Log --> DownloadLogRecord : updates + Log --> DownloadMgr : views + DownloadMgr --> Log : plans NE software loading + DownloadMgr --> BPONNE : +coordinator + BPONNE --> DownloadMgr : delivers to + DownloadMgr --> EventForwarder : announces + DownloadMgr --> Clock : triggers + DownloadMgr --> Factory : commissions + DownloadMgr --> SecureFileServer : designates software set source + EventForwarder --> EventSupplier : pushes event notification + EventSupplier --> ExternalEventChannel[External Event Channel] : push() + VersionRepository --> DownloadMgr : validates version + VersionRepository --> VersionRepository : updateSWVersion() + VersionRepository --> VersionRepository : retrieveVersions() + VersionRepository --> VersionRepository : validateNEVersion() + VersionRepository --> VersionRepository : validatePlugInVersion() +``` + +UML class diagram for Distribute NE software. The diagram shows classes: RecordSetMgr, Log, DownloadLogRecord, DownloadMgr, Event Supplier, Event Forwarder, Clock, Factory, Version Repository, and actors: OMS/Operator, BPON NE, and Secure File Server. Relationships include: RecordSetMgr obtains records from Log and selects records; Log stores, finds, displays by key, and displays records; DownloadMgr updates Log, views Log, plans NE software loading, and acts as a coordinator for BPON NE; BPON NE delivers to DownloadMgr; DownloadMgr announces to Event Forwarder, triggers Clock, commissions Factory, and designates software set source to Secure File Server; Event Forwarder pushes event notification to Event Supplier, which then pushes to External Event Channel; Version Repository validates version from DownloadMgr and has methods for update, retrieve, validate NE, and validate PlugIn. + +Figure 6-28 – Distribute NE software class diagram + +![UML sequence diagram for Immediate NE software delivery. The diagram shows interactions between OMSOperator, DownloadMgr, VersionRepository, OLT:BPON NE, Secure File Server, Target:BPON NE, ActivityCompletion:Log, TrackingObject:Factory, ExternalBeetChannel, BeetForwarder, and BeetSupplier. Key steps include validation, software download, distribution to targets, and final status updates.](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator + participant DownloadMgr as :DownloadMgr + participant VersionRepository as :VersionRepository + participant OLT as OLT:BPON NE + participant SFS as :Secure File Server + participant Target as Target:BPON NE + participant Log as ActivityCompletion:Log + participant Factory as TrackingObject:Factory + participant Channel as :ExternalBeetChannel + participant Forwarder as :BeetForwarder + participant Supplier as :BeetSupplier + + OMSOperator->>DownloadMgr: deliverDISTINGGlobal() + activate DownloadMgr + DownloadMgr->>VersionRepository: validateNEVersions() + activate VersionRepository + VersionRepository->>DownloadMgr: validatePluginVersion() + deactivate VersionRepository + Note over DownloadMgr: For every system. + DownloadMgr->>Factory: create() + activate Factory + Factory->>DownloadMgr: downloadSoftware() + deactivate Factory + DownloadMgr->>OLT: login() + activate OLT + OLT->>SFS: establishFileTransfer() + activate SFS + SFS->>OLT: checkDownload() + deactivate SFS + OLT->>Target: endConnection() + activate Target + Target->>OLT: removeLoad() + deactivate Target + Note over OLT: For every target within system. + OLT->>Target: distributeSoftware() + activate Target + Target->>Target: checkDownload() + deactivate Target + OLT->>Log: storeRecord() + deactivate OLT + DownloadMgr->>Log: processAnnouncement() + activate Log + Log->>Channel: postBeet() + activate Channel + Channel->>Forwarder: postBeet() + activate Forwarder + Forwarder->>Supplier: postBeet() + activate Supplier + Supplier->>Forwarder: post() + deactivate Supplier + Forwarder->>Channel: post() + deactivate Forwarder + Channel->>Log: post() + deactivate Channel + Log->>DownloadMgr: + deactivate Log + deactivate DownloadMgr + +``` + +UML sequence diagram for Immediate NE software delivery. The diagram shows interactions between OMSOperator, DownloadMgr, VersionRepository, OLT:BPON NE, Secure File Server, Target:BPON NE, ActivityCompletion:Log, TrackingObject:Factory, ExternalBeetChannel, BeetForwarder, and BeetSupplier. Key steps include validation, software download, distribution to targets, and final status updates. + +Figure 6-29 – Immediate NE software delivery sequence diagram + +![UML sequence diagram for Immediate specific NE software delivery. The diagram shows interactions between an OMS Operator, Download Manager, Version Repository, OLT: BRON NE, Secure File Server, Target: BPON NE, Activity Completion Log, Tracking Object Factory, External Beut Channel, BeutForwarder, and BeutSupplier. The process starts with the OMS Operator requesting software status and details, followed by validation of NE version and plug-in version. A loop 'For each missed system / target type' leads to creating a tracking object and downloading software. The software is then distributed through the OLT and Target, with various status checks and connection management. Finally, records are stored and announcements are processed, leading to a push event and a push response.](1b23b78336d8bd286c653cbdb38428dd_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant DownloadMgr as :DownloadMgr + participant VersionRepository as :VersionRepository + participant OLT as OLT: BRON NE + participant SecureFileServer as :Secure File Server + participant Target as Target: BPON NE + participant ActivityCompletionLog as :ActivityCompletion Log + participant TrackingObjectFactory as :Tracking Object Factory + participant ExternalBeutChannel as :External Beut Channel + participant BeutForwarder as :BeutForwarder + participant BeutSupplier as :BeutSupplier + + OMSOperator->>DownloadMgr: getStatus() + activate DownloadMgr + DownloadMgr->>VersionRepository: getNEDetails() + activate VersionRepository + VersionRepository->>DownloadMgr: validateNEVersion() + deactivate VersionRepository + DownloadMgr->>VersionRepository: validatePlugInVersion() + activate VersionRepository + VersionRepository->>DownloadMgr: validatePlugInVersion() + deactivate VersionRepository + Note left of DownloadMgr: For each missed system / target type. + DownloadMgr->>TrackingObjectFactory: create() + activate TrackingObjectFactory + TrackingObjectFactory->>DownloadMgr: downloadSoftware() + deactivate TrackingObjectFactory + DownloadMgr->>OLT: login() + activate OLT + OLT->>SecureFileServer: establishFileTransfer() + activate SecureFileServer + SecureFileServer->>OLT: checkDownload() + deactivate SecureFileServer + OLT->>Target: endConnection() + activate Target + Target->>OLT: removeLoad() + deactivate Target + OLT->>Target: distributeSoftware() + activate Target + Target->>Target: checkDownload() + deactivate Target + OLT->>ActivityCompletionLog: storeRecord() + deactivate OLT + ActivityCompletionLog->>BeutForwarder: processAnnouncement() + activate BeutForwarder + BeutForwarder->>BeutSupplier: pushEvent() + activate BeutSupplier + BeutSupplier->>BeutForwarder: push() + deactivate BeutSupplier + BeutForwarder->>ExternalBeutChannel: push() + deactivate BeutForwarder + deactivate ActivityCompletionLog + +``` + +UML sequence diagram for Immediate specific NE software delivery. The diagram shows interactions between an OMS Operator, Download Manager, Version Repository, OLT: BRON NE, Secure File Server, Target: BPON NE, Activity Completion Log, Tracking Object Factory, External Beut Channel, BeutForwarder, and BeutSupplier. The process starts with the OMS Operator requesting software status and details, followed by validation of NE version and plug-in version. A loop 'For each missed system / target type' leads to creating a tracking object and downloading software. The software is then distributed through the OLT and Target, with various status checks and connection management. Finally, records are stored and announcements are processed, leading to a push event and a push response. + +Figure 6-30 – Immediate specific NE software delivery sequence diagram + +![Sequence diagram for Immediate NE software commit, activate or revert sequence. The diagram shows interactions between OMS Operator, DownloadMgt, Target: EPON NE, ActivityCompletion: Log, Version Repository, and External Event Channel. The process is divided into three main sections: commit, activate, and revert. Each section involves sending messages to the Target, updating the Version Repository, and pushing notifications to the External Event Channel. Notes indicate that these actions are performed for each successful delivery or commit target.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant DownloadMgt as :DownloadMgt + participant Target as Target: EPON NE + participant Log as ActivityCompletion: Log + participant Repository as :Version Repository + participant Channel as :External Event Channel + + Note over Target: For each successful delivery target. + OMSOperator->>DownloadMgt: getStatus() + DownloadMgt->>Target: commit() + Target->>Target: sem&SyncCheck() + Target->>Target: removeLoad() + DownloadMgt->>Repository: updateSWVersion() + DownloadMgt->>Log: storeRecord() + DownloadMgt->>Channel: pushNotification() + + Note over Target: For each successful commit target. + OMSOperator->>DownloadMgt: activate() + DownloadMgt->>Target: switchPrimarySecondary() + Target->>Target: reset() + DownloadMgt->>Repository: updateSWVersion() + DownloadMgt->>Log: storeRecord() + DownloadMgt->>Channel: pushNotification() + + Note over Target: For undesirable software loads. + OMSOperator->>DownloadMgt: revert() + DownloadMgt->>Target: switchPrimarySecondary() + Target->>Target: reset() + DownloadMgt->>Repository: updateSWVersion() + DownloadMgt->>Log: storeRecord() + DownloadMgt->>Channel: pushNotification() + +``` + +Sequence diagram for Immediate NE software commit, activate or revert sequence. The diagram shows interactions between OMS Operator, DownloadMgt, Target: EPON NE, ActivityCompletion: Log, Version Repository, and External Event Channel. The process is divided into three main sections: commit, activate, and revert. Each section involves sending messages to the Target, updating the Version Repository, and pushing notifications to the External Event Channel. Notes indicate that these actions are performed for each successful delivery or commit target. + +**Figure 6-31 – Immediate NE software commit, activate or revert sequence diagram (for successful software delivery targets)8** + +8 In this figure and subsequent software activity sequences diagrams, "pushes notification" to the external event channel refers to the same notification process that is detailed out in Figures 6-29 and 6-30 for on demand software delivery and distribution. + +![UML sequence diagram for Scheduled NE software download. The diagram shows interactions between :OMS Operator, :DownloadMgr, :VersionRepository, OLT: BPON NE, :Secure File Server, Target: BPON NE, :EventForwarder, Activity Completion Log, Tracking Object Factory, and :External Event Channel. The process starts with a scheduled delivery, followed by validation, software download to OLTs, distribution to targets, and final status reporting.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +``` + +sequenceDiagram + actor OMS as :OMS Operator + participant DM as :DownloadMgr + participant VR as :VersionRepository + participant OLT as OLT: BPON NE + participant SFS as :Secure File Server + participant Target as Target: BPON NE + participant EF as :EventForwarder + participant ACL as Activity Completion Log + participant TOF as Tracking Object Factory + participant EEC as :External Event Channel + + OMS->>DM: scheduleDelivery() + activate DM + DM->>VR: validateNEVersions() + activate VR + VR->>DM: validateNEVersions() + deactivate VR + DM->>TOF: create() + activate TOF + TOF->>DM: + deactivate TOF + DM->>OLT: downloadSoftware() + activate OLT + OLT->>SFS: login() + activate SFS + SFS->>OLT: establishFileTransfer() + activate SFS + SFS->>OLT: checkDownload() + activate SFS + SFS->>OLT: endConnection() + deactivate SFS + OLT->>DM: removeLoad() + deactivate OLT + Note over OLT: To all appropriate targets. + OLT->>Target: distributeSoftware() + activate Target + Target->>Target: checkDownload() + deactivate Target + Note over Target: For each specific target. + DM->>DM: storeRecord() + activate DM + DM->>ACL: persistNotification() + activate ACL + ACL->>DM: + deactivate ACL + DM->>EEC: + activate EEC + EEC->>DM: + deactivate EEC + DM->>DM: getStatus() + deactivate DM + OMS->>DM: getStatus() + activate DM + DM->>DM: getStatus() + deactivate DM + +``` + +UML sequence diagram for Scheduled NE software download. The diagram shows interactions between :OMS Operator, :DownloadMgr, :VersionRepository, OLT: BPON NE, :Secure File Server, Target: BPON NE, :EventForwarder, Activity Completion Log, Tracking Object Factory, and :External Event Channel. The process starts with a scheduled delivery, followed by validation, software download to OLTs, distribution to targets, and final status reporting. + +Figure 6-32 – Scheduled NE software download sequence diagram + +![UML sequence diagram for 'Scheduled NE software commit or activate' showing interactions between OMS Operator, DownloadMgr, BPGN NE, Version Repository, Log, EventForwarder, Tracking Object Factory, and External Event Channel.](6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMS Operator + participant DownloadMgr as :DownloadMgr + actor BPGNNE as :BPGN NE + participant VersionRepository as :Version Repository + participant Log as :Log + participant EventForwarder as :EventForwarder + participant TrackingObjectFactory as :Tracking Object Factory + actor ExternalEventChannel as :External Event Channel + + OMSOperator->>DownloadMgr: scheduleCommit() + activate DownloadMgr + DownloadMgr->>BPGNNE: getStatus() + activate BPGNNE + BPGNNE->>DownloadMgr: + deactivate BPGNNE + DownloadMgr->>BPGNNE: writeToSecondary() + activate BPGNNE + BPGNNE->>DownloadMgr: sendSyncCheck() + activate DownloadMgr + DownloadMgr->>BPGNNE: removeLoad() + activate BPGNNE + BPGNNE->>DownloadMgr: + deactivate BPGNNE + DownloadMgr->>VersionRepository: updateSVNVersion() + activate VersionRepository + VersionRepository->>DownloadMgr: + deactivate VersionRepository + DownloadMgr->>EventForwarder: postEventNotification() + activate EventForwarder + EventForwarder->>DownloadMgr: + deactivate EventForwarder + DownloadMgr->>TrackingObjectFactory: storeRecord() + activate TrackingObjectFactory + TrackingObjectFactory->>DownloadMgr: + deactivate TrackingObjectFactory + DownloadMgr->>VersionRepository: updateSVNVersion() + activate VersionRepository + VersionRepository->>DownloadMgr: + deactivate VersionRepository + OMSOperator->>DownloadMgr: scheduleActivate() + activate DownloadMgr + DownloadMgr->>BPGNNE: switchPrimarySecondary() + activate BPGNNE + BPGNNE->>DownloadMgr: reset() + activate DownloadMgr + DownloadMgr->>BPGNNE: + deactivate BPGNNE + DownloadMgr->>VersionRepository: updateSVNVersion() + activate VersionRepository + VersionRepository->>DownloadMgr: + deactivate VersionRepository + DownloadMgr->>EventForwarder: postEventNotification() + activate EventForwarder + EventForwarder->>DownloadMgr: + deactivate EventForwarder + DownloadMgr->>TrackingObjectFactory: storeRecord() + activate TrackingObjectFactory + TrackingObjectFactory->>DownloadMgr: + deactivate TrackingObjectFactory + DownloadMgr->>VersionRepository: updateSVNVersion() + activate VersionRepository + VersionRepository->>DownloadMgr: + deactivate VersionRepository + DownloadMgr->>ExternalEventChannel: delete() + activate ExternalEventChannel + ExternalEventChannel->>DownloadMgr: + deactivate ExternalEventChannel + deactivate DownloadMgr + +``` + +The diagram illustrates the sequence of operations for scheduling a software commit or activation. It involves the following components and their interactions: + +- Participants:** :OMS Operator (Actor), :DownloadMgr (Boundary), :BPGN NE (Actor), :Version Repository (Boundary), :Log (Boundary), :EventForwarder (Boundary), :Tracking Object Factory (Boundary), and :External Event Channel (Actor). +- Sequence of Operations:** + - scheduleCommit():** Initiated by :OMS Operator to :DownloadMgr. + - :DownloadMgr calls `getStatus()` on :BPGN NE. + - :BPGN NE returns to :DownloadMgr. + - :DownloadMgr calls `writeToSecondary()` on :BPGN NE. + - :BPGN NE calls `sendSyncCheck()` on :DownloadMgr. + - :DownloadMgr calls `removeLoad()` on :BPGN NE. + - :BPGN NE returns to :DownloadMgr. + - :DownloadMgr calls `updateSVNVersion()` on :Version Repository. + - :Version Repository returns to :DownloadMgr. + - :DownloadMgr calls `postEventNotification()` on :EventForwarder. + - :EventForwarder returns to :DownloadMgr. + - :DownloadMgr calls `storeRecord()` on :Tracking Object Factory. + - :Tracking Object Factory returns to :DownloadMgr. + - :DownloadMgr calls `updateSVNVersion()` on :Version Repository. + - :Version Repository returns to :DownloadMgr. + - scheduleActivate():** Initiated by :OMS Operator to :DownloadMgr. + - :DownloadMgr calls `switchPrimarySecondary()` on :BPGN NE. + - :BPGN NE calls `reset()` on :DownloadMgr. + - :DownloadMgr returns to :BPGN NE. + - :DownloadMgr calls `updateSVNVersion()` on :Version Repository. + - :Version Repository returns to :DownloadMgr. + - :DownloadMgr calls `postEventNotification()` on :EventForwarder. + - :EventForwarder returns to :DownloadMgr. + - :DownloadMgr calls `storeRecord()` on :Tracking Object Factory. + - :Tracking Object Factory returns to :DownloadMgr. + - :DownloadMgr calls `updateSVNVersion()` on :Version Repository. + - :Version Repository returns to :DownloadMgr. + - :DownloadMgr calls `delete()` on :External Event Channel. + - :External Event Channel returns to :DownloadMgr. + +A note indicates: "For all specific targets at start time." This applies to the `postEventNotification()` and `storeRecord()` calls to the EventForwarder and Tracking Object Factory respectively. + +UML sequence diagram for 'Scheduled NE software commit or activate' showing interactions between OMS Operator, DownloadMgr, BPGN NE, Version Repository, Log, EventForwarder, Tracking Object Factory, and External Event Channel. + +Figure 6-33 – Scheduled NE software commit or activate sequence diagram + +![UML sequence diagram for 'Cancel scheduled NE software delivery'. The diagram involves three lifelines: :OMSOperator (actor), :DownloadMgr, and :VersionRepository. The process starts with a note: 'Assume software has been distributed via schedule successfully. Software download tracking object is automatically deleted.' The sequence of messages is: 1. :OMSOperator->>:DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet(). 2. :DownloadMgr->>:VersionRepository: getStats(). 3. :VersionRepository-->>:DownloadMgr: (return). 4. :OMSOperator->>:DownloadMgr: scheduleCommit(). 5. :OMSOperator->>:DownloadMgr: scheduleActivate(). 6. :OMSOperator->>:DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet(). 7. :OMSOperator->>:DownloadMgr: cancelScheduledSoftwareActivity(). 8. :DownloadMgr->>:VersionRepository: validateNEVersion(). 9. :DownloadMgr->>:VersionRepository: validatePluginVersion(). 10. :VersionRepository-->>:DownloadMgr: (return). 11. :OMSOperator->>:DownloadMgr: cancelScheduledSoftwareActivity(). 12. :OMSOperator->>:DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet(). Annotations include: 'Shows more.' pointing to the first call to getStats(); 'For same target.' pointing to the return of getStats(); 'Shows two activities.' pointing to the first call to scheduledSoftwareDownloadTrackingObjectLinkGet(); 'For each scheduled activity.' pointing to the first call to cancelScheduledSoftwareActivity(); and another 'Shows more.' pointing to the second call to scheduledSoftwareDownloadTrackingObjectLinkGet().](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant DownloadMgr as :DownloadMgr + participant VersionRepository as :VersionRepository + + Note over OMSOperator, DownloadMgr: Assume software has been distributed via +schedule successfully. Software download +tracking object is automatically deleted. + + OMSOperator->>DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet() + DownloadMgr->>VersionRepository: getStats() + VersionRepository-->>DownloadMgr: + Note over VersionRepository: Shows more. + + OMSOperator->>DownloadMgr: scheduleCommit() + OMSOperator->>DownloadMgr: scheduleActivate() + OMSOperator->>DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet() + Note over VersionRepository: For same target. + + OMSOperator->>DownloadMgr: cancelScheduledSoftwareActivity() + Note over VersionRepository: Shows two activities. + + DownloadMgr->>VersionRepository: validateNEVersion() + DownloadMgr->>VersionRepository: validatePluginVersion() + VersionRepository-->>DownloadMgr: + Note over VersionRepository: For each scheduled activity. + + OMSOperator->>DownloadMgr: cancelScheduledSoftwareActivity() + OMSOperator->>DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet() + Note over VersionRepository: Shows more. + +``` + +UML sequence diagram for 'Cancel scheduled NE software delivery'. The diagram involves three lifelines: :OMSOperator (actor), :DownloadMgr, and :VersionRepository. The process starts with a note: 'Assume software has been distributed via schedule successfully. Software download tracking object is automatically deleted.' The sequence of messages is: 1. :OMSOperator->>:DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet(). 2. :DownloadMgr->>:VersionRepository: getStats(). 3. :VersionRepository-->>:DownloadMgr: (return). 4. :OMSOperator->>:DownloadMgr: scheduleCommit(). 5. :OMSOperator->>:DownloadMgr: scheduleActivate(). 6. :OMSOperator->>:DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet(). 7. :OMSOperator->>:DownloadMgr: cancelScheduledSoftwareActivity(). 8. :DownloadMgr->>:VersionRepository: validateNEVersion(). 9. :DownloadMgr->>:VersionRepository: validatePluginVersion(). 10. :VersionRepository-->>:DownloadMgr: (return). 11. :OMSOperator->>:DownloadMgr: cancelScheduledSoftwareActivity(). 12. :OMSOperator->>:DownloadMgr: scheduledSoftwareDownloadTrackingObjectLinkGet(). Annotations include: 'Shows more.' pointing to the first call to getStats(); 'For same target.' pointing to the return of getStats(); 'Shows two activities.' pointing to the first call to scheduledSoftwareDownloadTrackingObjectLinkGet(); 'For each scheduled activity.' pointing to the first call to cancelScheduledSoftwareActivity(); and another 'Shows more.' pointing to the second call to scheduledSoftwareDownloadTrackingObjectLinkGet(). + +Figure 6-34 – Cancel scheduled NE software delivery sequence diagram + +![UML sequence diagram for Tracking object maintenance. Lifelines: : OMS/Operator (Actor), : DownloadMgr (Object), Tracking Object : Factory (Object). Messages: 1. : OMS/Operator to : DownloadMgr: scheduledSoftwareDownloadTrackingObjectListGet(). 2. : OMS/Operator to : DownloadMgr: onDemandSoftwareDownloadTrackingObjectListGet(). 3. : OMS/Operator to : DownloadMgr: getStatus(). 4. : OMS/Operator to : DownloadMgr: deleteSoftwareDownloadTrackingObject(). 5. : DownloadMgr to Tracking Object : Factory: delete().](a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg) + +``` + +sequenceDiagram + actor Operator as : OMS/Operator + participant DownloadMgr as : DownloadMgr + participant Factory as Tracking Object : Factory + + Operator->>DownloadMgr: scheduledSoftwareDownloadTrackingObjectListGet() + activate DownloadMgr + deactivate DownloadMgr + + Operator->>DownloadMgr: onDemandSoftwareDownloadTrackingObjectListGet() + activate DownloadMgr + deactivate DownloadMgr + + Operator->>DownloadMgr: getStatus() + activate DownloadMgr + deactivate DownloadMgr + + Operator->>DownloadMgr: deleteSoftwareDownloadTrackingObject() + activate DownloadMgr + DownloadMgr->>Factory: delete() + activate Factory + deactivate Factory + deactivate DownloadMgr + +``` + +UML sequence diagram for Tracking object maintenance. Lifelines: : OMS/Operator (Actor), : DownloadMgr (Object), Tracking Object : Factory (Object). Messages: 1. : OMS/Operator to : DownloadMgr: scheduledSoftwareDownloadTrackingObjectListGet(). 2. : OMS/Operator to : DownloadMgr: onDemandSoftwareDownloadTrackingObjectListGet(). 3. : OMS/Operator to : DownloadMgr: getStatus(). 4. : OMS/Operator to : DownloadMgr: deleteSoftwareDownloadTrackingObject(). 5. : DownloadMgr to Tracking Object : Factory: delete(). + +**Figure 6-35 – Tracking object maintenance sequence diagram** + +##### Operations + +| Operation name | Operation purpose | +|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) deliverDistSWGloabal | This operation requests the supplier management system to download software generics from software source machine for the purpose of software upgrades and software maintenance changes (patches) to NEs. | +| 2) deliverDistSWSpecific | This operation is same as deliverDistSWGloabal except the scope is within a single NE/PlugInUnit/slot as described in the input parameter distributionTarget. | +| 3) deleteSoftwareDownloadTrackingObject | This operation allows the OMS to notify the supplier management system that the software tracking object specified is no longer needed. | +| 4) commit | This operation requests the supplier management system to install (commit) the downloaded software to target locations. | +| 5) activate | This operation activates installed software at target locations. | +| 6) revert | This operation activates older installed software at target locations. | +| 7) getStatus | This operation requests the status of software activities. | +| 8) scheduleDeliverDist | This operation schedules the delivery and distribution of software to specified targets. | +| 9) scheduleCommit | This operation schedules the installation (commit) of software to predetermined targets. | +| 10) scheduleActivate | This operation schedules the activation of software to predetermined targets. | +| 11) cancelScheduledSoftwareActivity | This operation cancels all subsequently scheduled software download activities associated with this tracking object. | +| 12) scheduledSoftwareDownloadTrackingObjectListGet | This operation retrieves the list of outstanding scheduled activities for software download. | +| 13) onDemandSoftwareDownloadTrackingObjectListGet | This operation retrieves the list of outstanding non-scheduled activities for software download. | + +**Figure 6-36 – Download manager operations** + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) deliverDistSWGloab | FilenameSeqType,
DCNAddressType,
UserIdType,
PasswordType,
ManagedEntityIdSeqType | SoftwareDownload
TrackingObjectId
Type | CommFailure,
UnrecognisedTarget,
InsufficientMemory,
SoftwareLoadHWMismatch,
SourceUnreachable,
UnknownSoftwareLoad,
Timeout,
AccessDenied,
DeniedAccess | +| 2) deliverDistSWSpecific | FilenameSeqType,
DCNAddressType,
UserIdType,
PasswordType,
TargetType | SoftwareDownload
TrackingObjectId
Type | CommFailure,
UnrecognisedTarget,
InsufficientMemory,
SoftwareLoadHWMismatch,
SourceUnreachable,
UnknownSoftwareLoad,
Timeout,
AccessDenied,
DeniedAccess | +| 3) deleteSoftwareDownload
TrackingObject | SoftwareDownloadTracking
ObjectIdType | void | UnknownSoftwareDownload
TrackingObject,
AccessDenied,
SoftwareTrackingObjectInUse | +| 4) commit | SoftwareDownloadTracking
ObjectIdType,
TargetType | void | InstallationFailure,
UnknownSoftwareDownload
TrackingObject,
AccessDenied,
UnrecognisedTarget | +| 5) activate | SoftwareDownloadTracking
ObjectIdType,
TargetType | void | UnknownSoftwareDownload
TrackingObject,
SoftwareNotYetInstalled,
ActivationFailure,
AccessDenied,
UnrecognisedTarget | +| 6) revert | SoftwareDownloadTracking
ObjectIdType,
TargetType | void | UnknownSoftwareDownload
TrackingObject,
SoftwareNotYetInstalled,
ActivationFailure,
AccessDenied,
UnrecognisedTarget,
InvalidSoftwareTrackingObject | +| 7) getStatus | SoftwareDownloadTracking
ObjectIdType | DownloadStatusSeq
Type | UnknownSoftwareDownload
TrackingObject,
AccessDenied | +| 8) scheduleDeliverDist | FilenameSeqType
DCNAddressType
UserIdType
PasswordType
ManagedEntityIdSeqType
GeneralizedTimeType | SoftwareDownload
TrackingObjectId
Type | SoftwareLoadHWMismatch,
AccessDenied,
InvalidStartTime | +| 9) scheduleCommit | SoftwareDownloadTracking
ObjectIdType,
GeneralizedTimeType | void | UnknownSoftwareDownload
TrackingObject,
SoftwareNotYetInstalled,
AccessDenied,
InvalidStartTime | +| 10) scheduleActivate | SoftwareDownloadTracking
ObjectIdType,
GeneralizedTimeType | void | UnknownSoftwareDownload
TrackingObject,
SoftwareNotYetInstalled,
AccessDenied,
InvalidStartTime | + +| Operation name | Input parameters | Return value | Exceptions | +|----------------------------------------------------|--------------------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------| +| 11) cancelScheduledSoftwareActivity | SoftwareDownloadTrackingObjectIdType | void | UnknownSoftwareDownloadTrackingObject, ActivityCompleted, ActivityInProgress, AccessDenied | +| 12) scheduledSoftwareDownloadTrackingObjectListGet | | SoftwareDownloadTrackingObjectIdSeqType | AccessDenied | +| 13) onDemandSoftwareDownloadTrackingObjectListGet | | SoftwareDownloadTrackingObjectIdSeqType | AccessDenied | + +**Figure 6-37 – Download manager signatures** + +##### Exceptions + +| Exception raised | Description | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| ActivationFailure | This exception is raised if the software activation process failed. | +| ActivityCompleted | The software activity has been executed and cannot be cancelled. | +| ActivityInProgress | This exception is raised when the software activity has been initiated and cannot be cancelled. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| DeniedAccess | System is not granted access to the NE. | +| InstallationFailure | Software installation process failed. | +| InsufficientMemory | There is insufficient memory on the NE to load the software unit. | +| InvalidSoftwareTrackingObject | The referenced software tracking object is not the most recent associated with the installation of a software load on the NE. | +| InvalidStartTime | The start time is inconsistent with the current time, the current trigger time matrix or the new stop time. | +| SoftwareLoadHWMismatch | The designated software may not be loaded onto the equipment hardware since the version of the hardware cannot accept the software load. | +| SoftwareNotYetInstalled | The software may not be activated since it has not been installed yet. | +| SoftwareTrackingObjectInUse | Indicates that software download has been completed so that the process cannot be cancelled. | +| SourceUnreachable | The server holding the software load to be downloaded could not be reached by the OLT. | +| Timeout | The process duration reached a system-defined timeout before the process could complete. | +| UnknownSoftwareLoad | The specified software unit cannot be found. | +| UnknownSoftwareDownloadTrackingObject | The named software activity is unknown to the supplier management system. | +| UnrecognisedTarget | The designated software in the secure file server is unknown to the supplier management system. | + +**Figure 6-38 – Download manager exceptions** + +#### 6.3.3.2 Backup and restore NE + +![UML class diagram for NE data backup and restore. The diagram shows the interactions between various components including Log, BackupRestoreLogRecord, MIBMover, Scheduler, Transfer Mgr, Factory, Management Model Maintainer, BPON NE, OMS/Operator, and Secure File Server. It includes method lists for each class and detailed annotations for the relationships.](b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg) + +``` + +classDiagram + class Log { + +storeRecord() + +findRecords() + +displayByKey() + +displayRecords() + } + class BackupRestoreLogRecord { + } + class MIBMover { + +TransferTrackingObjectList + +startBackup() + +cancelScheduledBackup() + +getBackupStatus() + +startRestore() + +getRestoreStatus() + +scheduleBackup() + +modifyBackupSchedule() + +abortBackup() + +transferTrackingObjectListGet() + } + class Scheduler { + } + class TransferMgr[Transfer Mgr] { + } + class Factory { + +create() + +delete() + } + class ManagementModelMaintainer[Management Model Maintainer] { + } + class BPON_NE[BPON NE] + class OMS_Operator[OMS/Operator] + class Secure_File_Server[Secure File Server] + class OLTSysMIB[OLTSysMIB] + + Log ..> BackupRestoreLogRecord + MIBMover --> Log : updates + MIBMover --> Scheduler : triggers + Scheduler --> MIBMover : loading + MIBMover --> TransferMgr : commissions + TransferMgr --> Factory : commissions + MIBMover --> ManagementModelMaintainer : consults + BPON_NE --> MIBMover : extracts and applies MIB data + OMS_Operator --> MIBMover : schedules backup and initiates restore + OMS_Operator --> Scheduler + OLTSysMIB --> TransferMgr : loading + TransferMgr --> Secure_File_Server : delivers to + Factory --> TransferMgr + +``` + +The diagram illustrates the class structure and interactions for Network Element (NE) data backup and restore. + +- MIBMover** is the central class, managing operations like `startBackup()`, `startRestore()`, and `scheduleBackup()`. It maintains a `TransferTrackingObjectList`. +- OMS/Operator** (actor) interacts with **MIBMover** to schedule backups and initiate restores, and also interacts with the **Scheduler**. +- BPON NE** (actor) interacts with **MIBMover** to extract and apply MIB data. +- MIBMover** updates the **Log** (which contains **BackupRestoreLogRecord**), triggers the **Scheduler**, commissions the **Transfer Mgr**, and consults the **Management Model Maintainer**. +- Scheduler** is responsible for loading **MIBMover**. A note indicates: "Details found in 'Scheduler' Analysis." +- Transfer Mgr** is commissioned by **MIBMover** and also commissions the **Factory** (which has `create()` and `delete()` methods). It loads data from **OLTSysMIB** and delivers it to the **Secure File Server** (actor). A note indicates: "Details found in 'File Transfer' Analysis." + +UML class diagram for NE data backup and restore. The diagram shows the interactions between various components including Log, BackupRestoreLogRecord, MIBMover, Scheduler, Transfer Mgr, Factory, Management Model Maintainer, BPON NE, OMS/Operator, and Secure File Server. It includes method lists for each class and detailed annotations for the relationships. + +Figure 6-39 – NE data backup and restore class diagram + +![UML sequence diagram for Immediate NE backup sequence. Lifelines: :OMSOperator, :MIBMover, :Secure File Server, OLT: BRON NE, Tracking_Object: Factory, :Transfer Mgr, Transfer Tracking Object: Factory, Activity Completion: Log. Messages: startBackup(), checkPermissions(), snapshotMIB(), create(), prepareFile(), getBackupStatus(), fileTransfer(), transferFile(), create(), delete(), storeRecord(), delete(). Includes a 'Raises exception.' note.](3bf1696c3034743b5ab07a0b5e398347_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant MIBMover as :MIBMover + participant SecureFileServer as :Secure File Server + participant OLT as OLT: BRON NE + participant TrackingObjectFactory as Tracking_Object: Factory + participant TransferMgr as :Transfer Mgr + participant TransferTrackingObjectFactory as Transfer Tracking Object: Factory + participant ActivityCompletionLog as Activity Completion: Log + + OMSOperator->>MIBMover: startBackup() + activate MIBMover + MIBMover->>SecureFileServer: checkPermissions() + activate SecureFileServer + SecureFileServer->>OLT: snapshotMIB() + activate OLT + OLT->>TrackingObjectFactory: create() + activate TrackingObjectFactory + TrackingObjectFactory->>MIBMover: prepareFile() + deactivate TrackingObjectFactory + MIBMover->>OLT: prepareFile() + deactivate MIBMover + OLT->>MIBMover: getBackupStatus() + deactivate OLT + activate MIBMover + MIBMover->>TransferMgr: fileTransfer() + activate TransferMgr + TransferMgr->>TransferTrackingObjectFactory: create() + activate TransferTrackingObjectFactory + TransferTrackingObjectFactory->>TransferMgr: delete() + deactivate TransferTrackingObjectFactory + TransferMgr->>SecureFileServer: transferFile() + activate SecureFileServer + SecureFileServer->>OLT: login + activate OLT + OLT->>SecureFileServer: establishFileTransfer + activate SecureFileServer + SecureFileServer->>OLT: readConnection + deactivate SecureFileServer + OLT->>TransferMgr: storeRecord() + deactivate OLT + TransferMgr->>ActivityCompletionLog: delete() + deactivate TransferMgr + MIBMover->>TrackingObjectFactory: delete() + deactivate MIBMover + MIBMover->>MIBMover: getBackupStatus() + deactivate MIBMover + MIBMover-->>MIBMover: Raises exception. + +``` + +UML sequence diagram for Immediate NE backup sequence. Lifelines: :OMSOperator, :MIBMover, :Secure File Server, OLT: BRON NE, Tracking\_Object: Factory, :Transfer Mgr, Transfer Tracking Object: Factory, Activity Completion: Log. Messages: startBackup(), checkPermissions(), snapshotMIB(), create(), prepareFile(), getBackupStatus(), fileTransfer(), transferFile(), create(), delete(), storeRecord(), delete(). Includes a 'Raises exception.' note. + +Figure 6-40 – Immediate NE backup sequence diagram9 + +9 If the MIB is stewarded within the supplier management system, then the MIB snapshot, file creation and file transfer is accomplished within the supplier management system and not the OLT. + +![UML sequence diagram for Scheduled NE backup process. Lifelines: :OMSOperator, :MIB Mgr, :Secure File Server, Tracking Object : Factory, OLT : BRON NE, :Scheduler, :Transfer Mgr, Transfer Tracking Object : Factory, Activity Completion : Log. Messages: 1. :OMSOperator->>:MIB Mgr: schedule Backup(). 2. :MIB Mgr->>:Secure File Server: checkPermission(). 3. :MIB Mgr->>Tracking Object : Factory: create(). 4. :MIB Mgr->>:Scheduler: addAssociatedActivity(). 5. :Scheduler->>:MIB Mgr: startBackup(). 6. :MIB Mgr->>:Secure File Server: checkPermission(). 7. :MIB Mgr->>OLT : BRON NE: snapshotMIB(). 8. :MIB Mgr->>OLT : BRON NE: prepareFile(). 9. :MIB Mgr->>:Transfer Mgr: fileTransfer(). 10. :Transfer Mgr->>Transfer Tracking Object : Factory: create(). 11. :Transfer Mgr->>OLT : BRON NE: transferFile(). 12. :Transfer Mgr->>Transfer Tracking Object : Factory: delete(). 13. :Transfer Mgr->>Activity Completion : Log: storeRecord(). 14. :MIB Mgr->>:Transfer Mgr: log(). 15. :Transfer Mgr->>:Secure File Server: establishFileTransfer(). 16. :Transfer Mgr->>:Secure File Server: endConnection(). 17. :MIB Mgr->>:MIB Mgr: getBackupStatus(). 18. :MIB Mgr->>:MIB Mgr: getBackupStatus().](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +``` + +sequenceDiagram + participant OMSOperator as :OMSOperator + participant MIBMgr as :MIB Mgr + participant SecureFileServer as :Secure File Server + participant TrackingObjectFactory as Tracking Object : Factory + participant OLT as OLT : BRON NE + participant Scheduler as :Scheduler + participant TransferMgr as :Transfer Mgr + participant TransferTrackingObjectFactory as Transfer Tracking Object : Factory + participant ActivityCompletionLog as Activity Completion : Log + + OMSOperator->>MIBMgr: schedule Backup() + activate MIBMgr + MIBMgr->>SecureFileServer: checkPermission() + activate SecureFileServer + deactivate SecureFileServer + MIBMgr->>TrackingObjectFactory: create() + activate TrackingObjectFactory + deactivate TrackingObjectFactory + MIBMgr->>Scheduler: addAssociatedActivity() + activate Scheduler + Scheduler->>MIBMgr: startBackup() + deactivate Scheduler + activate MIBMgr + MIBMgr->>SecureFileServer: checkPermission() + activate SecureFileServer + deactivate SecureFileServer + MIBMgr->>OLT: snapshotMIB() + activate OLT + deactivate OLT + MIBMgr->>OLT: prepareFile() + activate OLT + deactivate OLT + MIBMgr->>TransferMgr: fileTransfer() + activate TransferMgr + TransferMgr->>TransferTrackingObjectFactory: create() + activate TransferTrackingObjectFactory + deactivate TransferTrackingObjectFactory + TransferMgr->>OLT: transferFile() + activate OLT + deactivate OLT + TransferMgr->>TransferTrackingObjectFactory: delete() + activate TransferTrackingObjectFactory + deactivate TransferTrackingObjectFactory + TransferMgr->>ActivityCompletionLog: storeRecord() + activate ActivityCompletionLog + deactivate ActivityCompletionLog + TransferMgr->>SecureFileServer: log() + activate SecureFileServer + deactivate SecureFileServer + TransferMgr->>SecureFileServer: establishFileTransfer() + activate SecureFileServer + deactivate SecureFileServer + TransferMgr->>SecureFileServer: endConnection() + activate SecureFileServer + deactivate SecureFileServer + deactivate TransferMgr + MIBMgr->>MIBMgr: getBackupStatus() + deactivate MIBMgr + activate MIBMgr + MIBMgr->>MIBMgr: getBackupStatus() + deactivate MIBMgr + +``` + +UML sequence diagram for Scheduled NE backup process. Lifelines: :OMSOperator, :MIB Mgr, :Secure File Server, Tracking Object : Factory, OLT : BRON NE, :Scheduler, :Transfer Mgr, Transfer Tracking Object : Factory, Activity Completion : Log. Messages: 1. :OMSOperator->>:MIB Mgr: schedule Backup(). 2. :MIB Mgr->>:Secure File Server: checkPermission(). 3. :MIB Mgr->>Tracking Object : Factory: create(). 4. :MIB Mgr->>:Scheduler: addAssociatedActivity(). 5. :Scheduler->>:MIB Mgr: startBackup(). 6. :MIB Mgr->>:Secure File Server: checkPermission(). 7. :MIB Mgr->>OLT : BRON NE: snapshotMIB(). 8. :MIB Mgr->>OLT : BRON NE: prepareFile(). 9. :MIB Mgr->>:Transfer Mgr: fileTransfer(). 10. :Transfer Mgr->>Transfer Tracking Object : Factory: create(). 11. :Transfer Mgr->>OLT : BRON NE: transferFile(). 12. :Transfer Mgr->>Transfer Tracking Object : Factory: delete(). 13. :Transfer Mgr->>Activity Completion : Log: storeRecord(). 14. :MIB Mgr->>:Transfer Mgr: log(). 15. :Transfer Mgr->>:Secure File Server: establishFileTransfer(). 16. :Transfer Mgr->>:Secure File Server: endConnection(). 17. :MIB Mgr->>:MIB Mgr: getBackupStatus(). 18. :MIB Mgr->>:MIB Mgr: getBackupStatus(). + +Figure 6-41 – Scheduled NE backup sequence diagram10 + +10 If the MIB is stewarded within the supplier management system, then the MIB snapshot, file creation and file transfer is accomplished within the supplier management system and not the OLT. + +![UML sequence diagram for Cancel scheduled NE backup. Lifelines: :OMSOperator, :MIB Mover, :Secure File Server, Tracking Object Factory, :Scheduler, OLT: BRON NE. The diagram shows a sequence of operations including scheduling, canceling, starting, aborting, and deleting backups, with error handling for exceptions.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant MIBMover as :MIB Mover + participant SecureFileServer as :Secure File Server + participant TOF as Tracking Object Factory + participant Scheduler as :Scheduler + participant OLT as OLT: BRON NE + + OMSOperator->>MIBMover: scheduleBackup() + activate MIBMover + MIBMover->>SecureFileServer: checkPermissions() + activate SecureFileServer + SecureFileServer->>TOF: create() + activate TOF + TOF->>Scheduler: addAssociatedActivity() + activate Scheduler + Scheduler->>MIBMover: + deactivate Scheduler + MIBMover->>MIBMover: + deactivate MIBMover + + OMSOperator->>MIBMover: cancelScheduledBackup() + activate MIBMover + MIBMover->>SecureFileServer: delete() + activate SecureFileServer + SecureFileServer->>Scheduler: removeAssociatedActivity() + activate Scheduler + Scheduler->>MIBMover: + deactivate Scheduler + MIBMover->>MIBMover: + deactivate MIBMover + + OMSOperator->>MIBMover: cancelScheduledBackup() + activate MIBMover + MIBMover->>MIBMover: Raises exception. + deactivate MIBMover + + OMSOperator->>MIBMover: scheduleBackup() + activate MIBMover + MIBMover->>SecureFileServer: checkPermissions() + activate SecureFileServer + SecureFileServer->>TOF: create() + activate TOF + TOF->>Scheduler: addAssociatedActivity() + activate Scheduler + Scheduler->>MIBMover: + deactivate Scheduler + MIBMover->>MIBMover: Raises exception. + deactivate MIBMover + + OMSOperator->>MIBMover: startBackup() + activate MIBMover + MIBMover->>SecureFileServer: checkPermissions() + activate SecureFileServer + SecureFileServer->>Scheduler: startBackup() + activate Scheduler + Scheduler->>MIBMover: + deactivate Scheduler + MIBMover->>MIBMover: + deactivate MIBMover + + OMSOperator->>MIBMover: cancelScheduledBackup() + activate MIBMover + MIBMover->>OLT: stopMIB + activate OLT + OLT->>MIBMover: prepareFile + deactivate OLT + MIBMover->>MIBMover: + deactivate MIBMover + + OMSOperator->>MIBMover: abortBackup() + activate MIBMover + MIBMover->>MIBMover: + deactivate MIBMover + + OMSOperator->>MIBMover: getBackupStatus() + activate MIBMover + MIBMover->>MIBMover: Shows abort termination. + deactivate MIBMover + + OMSOperator->>MIBMover: cancelScheduledBackup() + activate MIBMover + MIBMover->>SecureFileServer: delete() + activate SecureFileServer + SecureFileServer->>Scheduler: removeAssociatedActivity() + activate Scheduler + Scheduler->>MIBMover: + deactivate Scheduler + MIBMover->>MIBMover: + deactivate MIBMover + +``` + +UML sequence diagram for Cancel scheduled NE backup. Lifelines: :OMSOperator, :MIB Mover, :Secure File Server, Tracking Object Factory, :Scheduler, OLT: BRON NE. The diagram shows a sequence of operations including scheduling, canceling, starting, aborting, and deleting backups, with error handling for exceptions. + +Figure 6-42 – Cancel scheduled NE backup sequence diagram + +![UML sequence diagram for the Restore NE process. The diagram shows interactions between several lifelines: :OMSOperator, :MIB Mover, :Sect's File Server, :Transfer Mgr, :BPC N NE, Transfer Tracking Object: Factory, :Management Model Maintainer, and :Factory. The process starts with :OMSOperator selecting records and getting backup status. Then, :MIB Mover starts a restore, checks permissions, and checks SW/HW match. It then creates a Transfer Tracking Object and calls fileTransfer() on :Transfer Mgr. :Transfer Mgr checks permissions, creates a Transfer Tracking Object, logs in, establishes a file transfer, and ends the connection. :BPC N NE then applies MIB and resets. :MIB Mover gets restore status, notifies :Factory to delete, and stores records. Finally, :MIB Mover gets restore status again and selects records.](f78d2e126f00fcc5d8d9797ca410cc09_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant MIBMover as :MIB Mover + participant SectFileServer as :Sect's File Server + participant TransferMgr as :Transfer Mgr + participant BPCNNE as :BPC N NE + participant TransferTrackingObjectFactory as Transfer Tracking Object: Factory + participant ManagementModelMaintainer as :Management Model Maintainer + participant Factory as :Factory + + OMSOperator->>MIBMover: selectRecords() + activate MIBMover + MIBMover->>MIBMover: getBackupStatus() + deactivate MIBMover + OMSOperator->>MIBMover: startRestore() + activate MIBMover + MIBMover->>SectFileServer: checkPermissions() + activate SectFileServer + deactivate SectFileServer + MIBMover->>ManagementModelMaintainer: checkSW/HWMatch() + activate ManagementModelMaintainer + deactivate ManagementModelMaintainer + MIBMover->>TransferTrackingObjectFactory: create() + activate TransferTrackingObjectFactory + deactivate TransferTrackingObjectFactory + MIBMover->>TransferMgr: fileTransfer() + activate TransferMgr + TransferMgr->>SectFileServer: checkPermissions() + activate SectFileServer + deactivate SectFileServer + TransferMgr->>TransferTrackingObjectFactory: create() + activate TransferTrackingObjectFactory + deactivate TransferTrackingObjectFactory + TransferMgr->>BPCNNE: login + activate BPCNNE + deactivate BPCNNE + TransferMgr->>BPCNNE: establishFileTransfer + activate BPCNNE + deactivate BPCNNE + TransferMgr->>SectFileServer: endConnection + activate SectFileServer + deactivate SectFileServer + BPCNNE->>TransferTrackingObjectFactory: applyMIB + activate TransferTrackingObjectFactory + deactivate TransferTrackingObjectFactory + BPCNNE->>TransferTrackingObjectFactory: reset + activate TransferTrackingObjectFactory + deactivate TransferTrackingObjectFactory + MIBMover->>MIBMover: getRestoreStatus() + deactivate MIBMover + OMSOperator->>MIBMover: getRestoreStatus() + activate MIBMover + MIBMover->>Factory: notify delete() + activate Factory + deactivate Factory + MIBMover->>MIBMover: storeRecord() + deactivate MIBMover + MIBMover->>Factory: delete() + activate Factory + deactivate Factory + OMSOperator->>MIBMover: getRestoreStatus() + activate MIBMover + deactivate MIBMover + OMSOperator->>MIBMover: selectRecords() + activate MIBMover + deactivate MIBMover + +``` + +UML sequence diagram for the Restore NE process. The diagram shows interactions between several lifelines: :OMSOperator, :MIB Mover, :Sect's File Server, :Transfer Mgr, :BPC N NE, Transfer Tracking Object: Factory, :Management Model Maintainer, and :Factory. The process starts with :OMSOperator selecting records and getting backup status. Then, :MIB Mover starts a restore, checks permissions, and checks SW/HW match. It then creates a Transfer Tracking Object and calls fileTransfer() on :Transfer Mgr. :Transfer Mgr checks permissions, creates a Transfer Tracking Object, logs in, establishes a file transfer, and ends the connection. :BPC N NE then applies MIB and resets. :MIB Mover gets restore status, notifies :Factory to delete, and stores records. Finally, :MIB Mover gets restore status again and selects records. + +Figure 6-43 – Restore NE sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) startBackup | This operation initiates an immediate backup of system configuration data from a system and/or supplier management system to a backup server destination. | +| 2) getBackupStatus | This operation provides the capability to retrieve the status of a backup process. | +| 3) scheduleBackup | This operation cancels all subsequent backup processes for a system based on a scheduler. This operation will not interrupt a backup process in progress. | +| 4) modifyBackupSchedule | This operation cancels all subsequent backup processes for a system based on a scheduler. | +| 5) cancelScheduledBackup | This operation aborts a backup process in progress whether scheduled or not. Subsequent scheduled backup process are not affected by this operation. | +| 6) abortBackup | This operation aborts a backup process in progress whether scheduled or not. Subsequent scheduled backup process are not affected by this operation. | +| 7) startRestore | This operation provides functionality to restore a system based on a backed up copy of configuration data. | +| 8) getRestoreStatus | This operation provides the status of a restoral process. | +| 9) transferTrackingObjectIdListGet | This operation retrieves the list of outstanding system MIB transfers, both backup and restore. | + +Figure 6-44 – MIB mover operations + +##### Operation signatures11 + +| Operation name | Input parameters | Return value | Exceptions | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| 1) startBackup | ManagedEntityIdType (NE),
DCNAddressType,
UserIdType,
PasswordType,
FilenameType,
boolean (overwrite file?) | TransferTrackingObjectIdType | UnknownNE,
UnknownDestinationServer,
CommFailure,
EquipmentFailure,
DeniedAccess,
AccessDenied | +| 2) getBackupStatus | TransferTrackingObjectIdType | StatusAttributeSeqType | UnknownBackupProcess,
AccessDenied | +| 3) scheduleBackup | ManagedEntityIdType (NE),
UserIdType,
PasswordType,
UserLabelType,
DCNAddressType,
FilenameType,
boolean (overwrite file?) | TransferTrackingObjectIdType | UnknownNE,
UnknownDestinationServer,
UnknownScheduler,
InvalidScheduler,
AccessDenied | +| 4) modifyBackupSchedule | TransferTrackingObjectIdType,
UserLabelType | void | UnknownBackupProcess,
AccessDenied,
UnknownScheduler,
InvalidScheduler | +| 5) cancelScheduledBackup | TransferTrackingObjectIdType, | void | UnknownBackupProcess,
AccessDenied | +| 6) abortBackup | TransferTrackingObjectIdType, | void | UnknownBackupProcess,
CommFailure,
EquipmentFailure,
AccessDenied | +| 7) startRestore | ManagedEntityIdType (NE),
DCNAddressType,
UserIdType,
PasswordType,
FilenameType | TransferTrackingObjectIdType | UnknownNE,
CommFailure,
EquipmentFailure,
UnknownSourceServer,
DeniedAccess,
SoftwareLoadHardwareMismatch,
AccessDenied | +| 8) getRestoreStatus | TransferTrackingObjectIdType | StatusAttributeSeqType | UnknownRestoreProcess,
AccessDenied | +| 9) transferTrackingObjectIdListGet | | TransferTrackingObjectIdSeqType | AccessDenied | + +**Figure 6-45 – MIB mover signatures** + +11 The operation "overWriteBackup" has the same behaviour as "startBackup" except that the named destination file (the target) may be non-empty. + +##### Exceptions + +| Exception raised | Description | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| DeniedAccess | System is not granted access to the NE. | +| EquipmentFailure | The NE currently has a failure condition preventing the requested transaction from being completed. | +| InvalidScheduler | The scheduler parameters values are outside defined scope. | +| SoftwareLoadHardwareMismatch | The former NE configuration data could not be downloaded to the NE because there were changes made to the NE hardware that caused an incapability. | +| UnknownBackupProcess | The named transfer-tracking object identifying the file transfer process is unknown to the supplier management system. | +| UnknownDestinationServer | The identified destination server cannot be accessed by the transfer agent. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownRestoreProcess | The name restore activity is unknown to the supplier management system. | +| UnknownScheduler | The named scheduler is unknown to the supplier management system. | +| UnknownSourceServer | The supplier management system and/or OLT cannot communicate with the source server. The DCN address is unknown or access is blocked. | + +Figure 6-46 – MIB mover exceptions + +#### 6.3.3.3 NE software version control + +![UML class diagram for NE software version control. The diagram shows three main classes: Download Mgr, Version Repository, and Discoverer. Download Mgr has a dashed association to a note 'Details in "Download Manager" Analysis'. Version Repository has two methods: retrieveVersions() and validateNEVersion(). Discoverer has a dashed association to a note 'More details in "NE Synchroniser" Analysis'. The relationships are: Download Mgr confirms and updates Version Repository; Version Repository updates through Discoverer; Discoverer queries BPON NE; and OMS/Operator verifies version information from Version Repository.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +``` + +classDiagram + class DownloadMgr { + } + class VersionRepository { + retrieveVersions() + validateNEVersion() + validatePluginVersion() + } + class Discoverer { + } + class BPONNE["BPON NE"] + class OMSOperator["OMS/Operator"] + + DownloadMgr ..> Note1["Details in "Download Manager" Analysis"] + DownloadMgr --> VersionRepository : confirms and updates + VersionRepository --> Discoverer : updates through + Discoverer ..> Note2["More details in "NE Synchroniser" Analysis"] + Discoverer --> BPONNE : queries + OMSOperator --> VersionRepository : verifies version information + +``` + +UML class diagram for NE software version control. The diagram shows three main classes: Download Mgr, Version Repository, and Discoverer. Download Mgr has a dashed association to a note 'Details in "Download Manager" Analysis'. Version Repository has two methods: retrieveVersions() and validateNEVersion(). Discoverer has a dashed association to a note 'More details in "NE Synchroniser" Analysis'. The relationships are: Download Mgr confirms and updates Version Repository; Version Repository updates through Discoverer; Discoverer queries BPON NE; and OMS/Operator verifies version information from Version Repository. + +Figure 6-47 – NE software version control class diagram + +![Sequence diagram for NE software version control. Lifelines: : OMS/Operator, : Download Mgr, : Version Repository, NE Synchroniser, : Discoverer, : BPGN NE. Messages: retrieveVersions(), getEquipmentVersion(), getSoftwareVersions(), get, updateSWVersion(), updateHWVersion(), deliverDistSWGGlobal (or deliverDistSWGGlobal or scheduleDeliverDist), validateNEVersion(), validatePlugInVersion(), commit (or activate or scheduleCommit or scheduleActivate), updateSWVersion. Notes: 'Show updating triggered by NE synchronisation activities.', 'Details found in "Distribute Software" Analysis.', 'Followed by many steps.', 'Preceded by many steps.'](0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant DM as : Download Mgr + participant VR as : Version Repository + participant NS as NE Synchroniser + participant D as : Discoverer + actor BPGN as : BPGN NE + + OMS->>DM: retrieveVersions() + activate DM + DM->>VR: getEquipmentVersion() + activate VR + VR->>NS: getSoftwareVersions() + activate NS + NS->>BPGN: get + activate BPGN + BPGN-->>NS: + deactivate BPGN + NS-->>VR: + deactivate NS + VR->>DM: updateSWVersion() + activate DM + Note left of DM: Show updating triggered by NE synchronisation activities. + VR->>DM: updateHWVersion() + deactivate DM + activate DM + DM->>DM: deliverDistSWGGlobal (or deliverDistSWGGlobal or scheduleDeliverDist) + activate DM + DM->>VR: validateNEVersion() + activate VR + Note right of VR: Details found in "Distribute Software" Analysis. + DM->>VR: validatePlugInVersion() + activate VR + Note left of VR: Followed by many steps. + VR-->>DM: + deactivate VR + activate DM + DM->>DM: commit (or activate or scheduleCommit or scheduleActivate) + Note left of DM: Preceded by many steps. + activate DM + DM->>VR: updateSWVersion + activate VR + VR-->>DM: + deactivate VR + deactivate DM + +``` + +Sequence diagram for NE software version control. Lifelines: : OMS/Operator, : Download Mgr, : Version Repository, NE Synchroniser, : Discoverer, : BPGN NE. Messages: retrieveVersions(), getEquipmentVersion(), getSoftwareVersions(), get, updateSWVersion(), updateHWVersion(), deliverDistSWGGlobal (or deliverDistSWGGlobal or scheduleDeliverDist), validateNEVersion(), validatePlugInVersion(), commit (or activate or scheduleCommit or scheduleActivate), updateSWVersion. Notes: 'Show updating triggered by NE synchronisation activities.', 'Details found in "Distribute Software" Analysis.', 'Followed by many steps.', 'Preceded by many steps.' + +Figure 6-48 – NE software version control sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| 1) retrieveVersions | This operation retrieves all version information (both software and hardware) for a network resource. | +| 2) validateNEVersion | This operation requests the supplier management system to validate if the proposed software is compatible with the the NE. | +| 3) validatePlugInVersion | This operation requests the supplier management system to validate if the proposed software is compatible with the plugInUnit. | + +Figure 6-49 – Version repository operations + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|--------------------------|----------------------------------|------------------|-------------------------------------------------| +| 1) retrieveVersions | ManagedEntityIdType | VersionsSeqType | CommFailure, UnknownManagedEntity, AccessDenied | +| 2) validateNEVersion | ManagedEntityIdType, VersionType | boolean (valid?) | UnknownNE, AccessDenied | +| 3) validatePlugInVersion | ManagedEntityIdType, VersionType | boolean (valid?) | UnknownManagedEntity, AccessDenied | + +Figure 6-50 – Version repository signatures + +##### Exceptions + +| Exception raised | Description | +|----------------------|---------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| UnknownManagedEntity | The specified managed entity is unknown to the supplier management system. | + +Figure 6-51 – Version repository exceptions + +#### 6.3.3.4 Scheduler + +![UML Class Diagram for Scheduler Management](afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg) + +``` + +classDiagram + class SchedulerMgr { + SchedulerList + SchedulerIdUserLabelListing + makeScheduler() + suspendScheduler() + resumeScheduler() + modifyTime() + changeSchedulerName() + modifyTriggerTimes() + removeScheduler() + retrieveScheduler() + schedulerListGet() + } + class Factory { + create() + delete() + } + class Scheduler { + SchedulerId + AdministrativeState + StartTime + StopTime + UserLabel + AssociatedActivityPointerList + lockAdministrativeState() + unlockAdministrativeState() + setTime() + getTime() + setUserLabel() + getUserLabel() + setByCreate() + terminate() + getAll() + modifyTriggerTimes() + } + class DailyScheduler { + TriggerTimeListing + } + class HourlyScheduler { + minuteTriggerTimeMatrix + } + class WeeklyScheduler { + weekdayTriggerTimeMatrix + } + class MonthlyScheduler { + monthdayTriggerTimeMatrix + } + SchedulerMgr --> Factory : commissions + SchedulerMgr --> Scheduler : controls + Factory --> Scheduler : creates + SchedulerMgr --> Scheduler : manipulates scheduling + Scheduler <|-- DailyScheduler + Scheduler <|-- HourlyScheduler + Scheduler <|-- WeeklyScheduler + Scheduler <|-- MonthlyScheduler + +``` + +The diagram illustrates the Scheduler management class structure. The **Scheduler Mgr** class is the central interface, containing methods for managing schedulers and a list of scheduler objects. It interacts with a **Factory** to create and delete schedulers, and it controls the **Scheduler** interface. The **Scheduler** interface defines the common methods and attributes for all scheduler types, including administrative state management, time setting, and retrieval. Four concrete scheduler classes are shown: **DailyScheduler**, **HourlyScheduler**, **WeeklyScheduler**, and **MonthlyScheduler**, each with its own specific trigger time matrix or listing. An **OMS/Operator** actor is shown manipulating the scheduling process through the **Scheduler Mgr**. + +UML Class Diagram for Scheduler Management + +Figure 6-52 – Scheduler management class diagram + +![UML sequence diagram for Scheduler control. Lifelines: : OMS/Operator (Actor), : Scheduler Mgr, Scheduler: Factory, and : Scheduler. Messages: 1. makeScheduler() from OMS/Operator to Scheduler Mgr, then create() to Scheduler: Factory, then setByCreate() to Scheduler. 2. suspendScheduler() from OMS/Operator to Scheduler Mgr, then lockAdministrativeState() to Scheduler. 3. resumeScheduler() from OMS/Operator to Scheduler Mgr, then unlockAdministrativeState() to Scheduler. 4. changeSchedulerName() from OMS/Operator to Scheduler Mgr, then setUserLabel() to Scheduler. 5. retrieveScheduler() from OMS/Operator to Scheduler Mgr. 6. schedulerListGet() from OMS/Operator to Scheduler Mgr. 7. retrieveScheduler() from OMS/Operator to Scheduler Mgr, then getAll() to Scheduler.](caeb1637753f79f4cd005eda3768d1d5_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant Mgr as : Scheduler Mgr + participant Factory as Scheduler: Factory + participant Scheduler as : Scheduler + + OMS->>Mgr: makeScheduler() + activate Mgr + Mgr->>Factory: create() + activate Factory + Factory->>Scheduler: setByCreate() + activate Scheduler + Scheduler-->>Factory: + deactivate Scheduler + Factory-->>Mgr: + deactivate Factory + Mgr-->>Oms: + deactivate Mgr + + OMS->>Mgr: suspendScheduler() + activate Mgr + Mgr->>Scheduler: lockAdministrativeState() + activate Scheduler + Scheduler-->>Mgr: + deactivate Scheduler + Mgr-->>Oms: + deactivate Mgr + + OMS->>Mgr: resumeScheduler() + activate Mgr + Mgr->>Scheduler: unlockAdministrativeState() + activate Scheduler + Scheduler-->>Mgr: + deactivate Scheduler + Mgr-->>Oms: + deactivate Mgr + + OMS->>Mgr: changeSchedulerName() + activate Mgr + Mgr->>Scheduler: setUserLabel() + activate Scheduler + Scheduler-->>Mgr: + deactivate Scheduler + Mgr-->>Oms: + deactivate Mgr + + OMS->>Mgr: retrieveScheduler() + activate Mgr + Mgr-->>Oms: + deactivate Mgr + + OMS->>Mgr: schedulerListGet() + activate Mgr + Mgr-->>Oms: + deactivate Mgr + + OMS->>Mgr: retrieveScheduler() + activate Mgr + Mgr->>Scheduler: getAll() + activate Scheduler + Scheduler-->>Mgr: + deactivate Scheduler + Mgr-->>Oms: + deactivate Mgr + +``` + +UML sequence diagram for Scheduler control. Lifelines: : OMS/Operator (Actor), : Scheduler Mgr, Scheduler: Factory, and : Scheduler. Messages: 1. makeScheduler() from OMS/Operator to Scheduler Mgr, then create() to Scheduler: Factory, then setByCreate() to Scheduler. 2. suspendScheduler() from OMS/Operator to Scheduler Mgr, then lockAdministrativeState() to Scheduler. 3. resumeScheduler() from OMS/Operator to Scheduler Mgr, then unlockAdministrativeState() to Scheduler. 4. changeSchedulerName() from OMS/Operator to Scheduler Mgr, then setUserLabel() to Scheduler. 5. retrieveScheduler() from OMS/Operator to Scheduler Mgr. 6. schedulerListGet() from OMS/Operator to Scheduler Mgr. 7. retrieveScheduler() from OMS/Operator to Scheduler Mgr, then getAll() to Scheduler. + +Figure 6-53 – Scheduler control sequence diagram + +![Sequence diagram for Scheduler modifications. Lifelines: : OMS/Operator, : Scheduler Mgr, Scheduler: Factory, : Scheduler, : MIBMover. Messages: 1. modifyTime() from OMS/Operator to Scheduler Mgr. 2. setTime() from Scheduler Mgr to Scheduler. 3. startBackup() from Scheduler to MIBMover. 4. modifyTriggerTimes() from OMS/Operator to Scheduler Mgr. 5. modifyTriggerTimes() from Scheduler Mgr to Scheduler. 6. startBackup() from Scheduler to MIBMover. 7. removeScheduler() from OMS/Operator to Scheduler Mgr. 8. delete() from Scheduler Mgr to Scheduler: Factory. 9. terminate() from Scheduler: Factory to Scheduler. 10. cancelScheduledBackup() from Scheduler to MIBMover. Notes: - Note 1: 'Modifies the start or stop time for the periodic activity (e.g., daily activity starts on Tuesday, rather than Monday).' - Note 2: 'Scheduled activity begins one hour earlier.' - Note 3: 'When a scheduler is removed, all associated activities are cancelled.'](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant Mgr as : Scheduler Mgr + participant Factory as Scheduler: Factory + participant Scheduler as : Scheduler + participant MIBMover as : MIBMover + + OMS->>Mgr: modifyTime() + activate Mgr + Mgr->>Scheduler: setTime() + deactivate Mgr + activate Scheduler + Scheduler->>MIBMover: startBackup() + deactivate Scheduler + activate MIBMover + Note right of MIBMover: Modifies the start or stop time for the periodic activity (e.g., daily activity starts on Tuesday, rather than Monday). + deactivate MIBMover + + OMS->>Mgr: modifyTriggerTimes() + activate Mgr + Mgr->>Scheduler: modifyTriggerTimes() + deactivate Mgr + activate Scheduler + Scheduler->>MIBMover: startBackup() + deactivate Scheduler + activate MIBMover + Note right of MIBMover: Scheduled activity begins one hour earlier. + deactivate MIBMover + + OMS->>Mgr: removeScheduler() + activate Mgr + Mgr->>Factory: delete() + deactivate Mgr + activate Factory + Factory->>Scheduler: terminate() + deactivate Factory + activate Scheduler + Scheduler->>MIBMover: cancelScheduledBackup() + deactivate Scheduler + activate MIBMover + Note right of MIBMover: When a scheduler is removed, all associated activities are cancelled. + deactivate MIBMover + deactivate Scheduler + deactivate Factory + deactivate Mgr + +``` + +Sequence diagram for Scheduler modifications. Lifelines: : OMS/Operator, : Scheduler Mgr, Scheduler: Factory, : Scheduler, : MIBMover. Messages: 1. modifyTime() from OMS/Operator to Scheduler Mgr. 2. setTime() from Scheduler Mgr to Scheduler. 3. startBackup() from Scheduler to MIBMover. 4. modifyTriggerTimes() from OMS/Operator to Scheduler Mgr. 5. modifyTriggerTimes() from Scheduler Mgr to Scheduler. 6. startBackup() from Scheduler to MIBMover. 7. removeScheduler() from OMS/Operator to Scheduler Mgr. 8. delete() from Scheduler Mgr to Scheduler: Factory. 9. terminate() from Scheduler: Factory to Scheduler. 10. cancelScheduledBackup() from Scheduler to MIBMover. Notes: - Note 1: 'Modifies the start or stop time for the periodic activity (e.g., daily activity starts on Tuesday, rather than Monday).' - Note 2: 'Scheduled activity begins one hour earlier.' - Note 3: 'When a scheduler is removed, all associated activities are cancelled.' + +Figure 6-54 – Scheduler modifications sequence diagram12 + +##### Operations + +| Operation name | Operation purpose | +|------------------------|---------------------------------------------------------------------------------------------------------------------| +| 1) makeScheduler | This operation creates a new scheduler object. | +| 2) suspendScheduler | This operation is used to suspend a schedule. | +| 3) resumeScheduler | This operation is used to resume a suspended schedule. | +| 4) modifyTime | This operation is used in order to change the startTime and stopTime of a schedule. | +| 5) changeSchedulerName | This operation is used to change the name of the scheduler object. | +| 6) modifyTriggerTimes | This operation is used by the OMS to specify new trigger times and iteration for a scheduler. | +| 7) removeScheduler | This operation is used to delete a scheduler. | +| 8) retrieveScheduler | This operation is used to retrieve information on the schedule. | +| 9) schedulerListGet | This operation is used to retrieve the names of all existing schedulers defined for the supplier management system. | + +Figure 6-55 – Scheduler operations + +12 This sequence diagram uses an associated scheduled activity of MIB backup as an example. There can be others, and more than one associated with a given scheduler. + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------| +| 1) makeScheduler | UserLabelType,
GeneralizedTimeType (start time),
GeneralizedTimeType (stop time),
HourlyDailyWeeklyMonthlyIndType,
TriggerTimeMatrixSeqType | void | InvalidStartTime,
InvalidStopTime,
DuplicateUserLabel,
MatrixSchedulerType
Mismatch, AccessDenied,
InvalidTrigger | +| 2) suspendScheduler | UserLabelType | void | UnknownScheduler,
AccessDenied | +| 3) resumeScheduler | UserLabelType | void | UnknownScheduler,
AccessDenied | +| 4) modifyTime | UserLabelType,
GeneralizedTimeType (start time),
GeneralizedTimeType (stop time) | void | InvalidStartTime,
InvalidStopTime,
UnknownScheduler,
AccessDenied | +| 5) changeSchedulerName | UserLabelType (old name),
UserLabelType (new name) | void | UnknownScheduler,
DuplicateUserLabel,
AccessDenied | +| 6) modifyTriggerTimes | UserLabelType,
HourlyDailyWeeklyMonthlyIndType,
TriggerTimeMatrixSeqType | void | UnknownScheduler,
MatrixSchedulerType
Mismatch, InvalidTrigger,
AccessDenied | +| 7) removeScheduler | UserLabelType | void | UnknownScheduler,
AccessDenied,
ScheduleInUse | +| 8) retrieveScheduler | UserLabelType | SchedulerType | UnknownScheduler,
AccessDenied | +| 9) schedulerListGet | | SchedulerSeqType | AccessDenied | + +**Figure 6-56 – Scheduler signatures** + +##### Exceptions + +| Exception raised | Description | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| DuplicateUserLabel | The user label provided in the request has been used to label another scheduler. | +| InvalidStartTime | The new start time is inconsistent with the current time, the current trigger time matrix or the new stop time. | +| InvalidStopTime | The new stop time is inconsistent with the current time, the current trigger time matrix or the new start time. | +| InvalidTrigger | The specified trigger has values that cannot be interpreted by the scheduler. | +| MatrixSchedulerTypeMismatch | The syntax for the trigger time matrix is mismatched with the type of scheduler named. | +| ScheduleInUse | There are still activities scheduled by the named scheduler. | +| UnknownScheduler | The named scheduler is unknown to the supplier management system. | + +**Figure 6-57 – Scheduler exceptions** + +### 6.3.4 Testing + +#### 6.3.4.1 Conduct tests + +![UML Class Diagram for Conduct tests and report results](3b11cc18f8ee769d0076c139dbf81ba3_img.jpg) + +This UML Class Diagram illustrates the architecture for conducting tests and reporting results. The diagram includes the following classes and their interactions: + +- Log**: Contains methods `storeRecord()`, `findRecords()`, `displayByKey()`, and `displayRecords()`. It is updated by **TestHistoryRecord** and viewed by **RecordSetMgr**. +- RecordSetMgr**: Contains `selectRecords()`. It retrieves data from **OMSOperator** and obtains records from **Log**. +- OMSOperator**: Interacts with **RecordSetMgr** and **TestActionPerformer**. It requests tests and processes results from **TestActionPerformer**. +- TestIDInbome**: A data structure that triggers **TestActionPerformer**. +- TestRequestInb**: A data structure that triggers **TestActionPerformer**. +- Scheduler**: Triggers **TestActionPerformer**. +- TestActionPerformer**: The central class for test execution. It contains: + - Attributes: `ScheduledTestNEList`, `SupportedTestList`. + - Methods: `getTTLLoopback()`, `initiateLoopback()`, `terminateLoopback()`, `initiateContinuityCheck()`, `terminateContinuityCheck()`, `scheduledResourceSetTest()`, `modifyTestSchedule()`, `cancelScheduledTest()`, `conductResourceSetTest()`, `terminateResourceSetTest()`, `getLoopbackInb()`, `getLoopbackInbByNE()`, `getTestStatus()`, `scheduledTestNEListGet()`, `TestHistoryByManagedEntity()`, `TestHistoryBySequenceInstance()`, `metallicDropTest()`, `scheduledMetallicDropTest()`, `MACLayerTest()`, `scheduledMACLayerTest()`, `drawDialtoneDropBreakTest()`, and `scheduledDrawDialtoneBreakTest()`. +- TestHistoryRecord**: Updates the **Log**. +- BPONE**: Performs tests. It has methods `doTest()`, `loopUp()`, `loopDown()`, `getTestResults()`, `stopTest()`, and `testSetup()`. It receives test requests from **TestActionPerformer**. +- TestObject**: Contains: + - Attributes: `TestObjectID`, `InitializationSchedule`, `OperationalState`, `ProceduralStatus`, `TestInvocationID`, `AvailabilityStatus`, `ActualStart`, `ActualStop`, `TerminationCriteria`, `AssociatedObjectsList`, `ResourceObjectsUnderTest`, `TimeonPeriod`, and `TestOperations`. + - Methods: `terminate()`, `setCrateDetails()`, `setActualTime()`, `monitorTesting()`, `getProceduralStatus()`, `getOperationalState()`, `getTestResults()`, and `setTestResults()`. +- Factory**: Contains `create()` and `delete()`. It creates **TestTrackInbObject** and **TestObject**. +- TestTrackInbObject**: Created by the **Factory**. + +Key interactions include: **TestActionPerformer** performing tests on **BPONE**, setting actual times for controlled tests on **TestObject**, and creating **TestObject** instances via the **Factory**. The **OMSOperator** manages the flow of test requests and result processing between the **RecordSetMgr** and **TestActionPerformer**. + +UML Class Diagram for Conduct tests and report results + +Figure 6-58 – Conduct tests and report results class diagram + +![UML sequence diagram for conducting uncontrolled tests. The diagram shows four test scenarios: aTMLoopback(), metallicDropTest(), mACLayerTest(), and drawDialtoneDropBreakTest(). Each scenario involves an OMS/Operator initiating a test, the Test Action Performer executing the test and preparing the outcome, the BPON NE performing the test, and the Test History Log storing the record.](ec96d99a16edb981eb7defe41a79b57f_img.jpg) + +``` + +sequenceDiagram + actor OMS as OMS/Operator + participant TAP as : Test Action Performer + actor BPON as : BPON NE + participant THL as Test History : Log + + OMS->>TAP: aTMLoopback() + TAP->>BPON: doTest() + BPON->>THL: storeRecord() + BPON-->>TAP: prepareTestOutcome() + TAP-->>TAP: prepareTestOutcome() + + OMS->>TAP: metallicDropTest() + TAP->>BPON: doTest() + BPON->>THL: storeRecord() + BPON-->>TAP: prepareTestOutcome() + TAP-->>TAP: prepareTestOutcome() + + OMS->>TAP: mACLayerTest() + TAP->>BPON: doTest() + BPON->>THL: storeRecord() + BPON-->>TAP: prepareTestOutcome() + TAP-->>TAP: prepareTestOutcome() + + OMS->>TAP: drawDialtoneDropBreakTest() + TAP->>BPON: doTest() + BPON->>THL: storeRecord() + BPON-->>TAP: prepareTestOutcome() + TAP-->>TAP: prepareTestOutcome() + +``` + +UML sequence diagram for conducting uncontrolled tests. The diagram shows four test scenarios: aTMLoopback(), metallicDropTest(), mACLayerTest(), and drawDialtoneDropBreakTest(). Each scenario involves an OMS/Operator initiating a test, the Test Action Performer executing the test and preparing the outcome, the BPON NE performing the test, and the Test History Log storing the record. + +**Figure 6-59 – Conduct uncontrolled tests sequence diagram** + +![UML sequence diagram for Test set up showing interactions between OMS Operator, Test Action Performer, Test Tracking Object Factory, BPON NE, and Test History Log.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant TestActionPerformer as :TestAction Performer + participant TestTrackingObjectFactory as TestTracking Object: Factory + actor BPONNE as :BPON NE + participant TestHistoryLog as TestHistory: Log + + OMSOperator->>TestActionPerformer: Initiate Loopback() + activate TestActionPerformer + TestActionPerformer->>BPONNE: loopUp() + activate BPONNE + BPONNE->>TestActionPerformer: + deactivate BPONNE + TestActionPerformer->>TestTrackingObjectFactory: create() + activate TestTrackingObjectFactory + TestTrackingObjectFactory->>TestActionPerformer: + deactivate TestTrackingObjectFactory + TestActionPerformer->>TestHistoryLog: store Record() + activate TestHistoryLog + TestHistoryLog->>TestActionPerformer: + deactivate TestHistoryLog + TestActionPerformer->>OMSOperator: getLoopbackInfo() + deactivate TestActionPerformer + OMSOperator->>TestActionPerformer: + activate TestActionPerformer + TestActionPerformer->>TestTrackingObjectFactory: getLoopbackInfoByNE() + activate TestTrackingObjectFactory + TestTrackingObjectFactory->>TestActionPerformer: + deactivate TestTrackingObjectFactory + TestActionPerformer->>OMSOperator: terminate Loopback() + deactivate TestActionPerformer + OMSOperator->>TestActionPerformer: + activate TestActionPerformer + TestActionPerformer->>BPONNE: loopDown() + activate BPONNE + BPONNE->>TestActionPerformer: + deactivate BPONNE + TestActionPerformer->>TestTrackingObjectFactory: delete() + activate TestTrackingObjectFactory + TestTrackingObjectFactory->>TestActionPerformer: + deactivate TestTrackingObjectFactory + TestActionPerformer->>TestHistoryLog: store Record() + activate TestHistoryLog + TestHistoryLog->>TestActionPerformer: + deactivate TestHistoryLog + TestActionPerformer->>OMSOperator: InitializeContinue Check() + deactivate TestActionPerformer + OMSOperator->>TestActionPerformer: + activate TestActionPerformer + TestActionPerformer->>BPONNE: testSetup() + activate BPONNE + BPONNE->>TestActionPerformer: + deactivate BPONNE + TestActionPerformer->>TestTrackingObjectFactory: create() + activate TestTrackingObjectFactory + TestTrackingObjectFactory->>TestActionPerformer: + deactivate TestTrackingObjectFactory + TestActionPerformer->>TestHistoryLog: store Record() + activate TestHistoryLog + TestHistoryLog->>TestActionPerformer: + deactivate TestHistoryLog + TestActionPerformer->>OMSOperator: terminateContinue Check() + deactivate TestActionPerformer + OMSOperator->>TestActionPerformer: + activate TestActionPerformer + TestActionPerformer->>BPONNE: testSetup() + activate BPONNE + BPONNE->>TestActionPerformer: + deactivate BPONNE + TestActionPerformer->>TestTrackingObjectFactory: delete() + activate TestTrackingObjectFactory + TestTrackingObjectFactory->>TestActionPerformer: + deactivate TestTrackingObjectFactory + TestActionPerformer->>TestHistoryLog: store Record() + activate TestHistoryLog + TestHistoryLog->>TestActionPerformer: + deactivate TestHistoryLog + TestActionPerformer->>OMSOperator: + deactivate TestActionPerformer + +``` + +The diagram illustrates the sequence of operations for test setup and teardown. It involves five main components: the OMS Operator (actor), the Test Action Performer (participant), the Test Tracking Object Factory (participant), the BPON NE (actor), and the Test History Log (participant). The process begins with the OMS Operator initiating a loopback, followed by the Test Action Performer performing loopup, creating a record, and storing it. Subsequent steps include retrieving loopback information and terminating the loopback. The process then repeats for a continue check, involving test setup, record creation, and storage, followed by another termination and record storage. Two yellow notes provide additional context: 'Shows loopback initiated about.' and 'Shows at least loopback initiated about.' + +UML sequence diagram for Test set up showing interactions between OMS Operator, Test Action Performer, Test Tracking Object Factory, BPON NE, and Test History Log. + +Figure 6-60 – Test set up sequence diagram + +![UML sequence diagram for a controlled test sequence. Lifelines include : OMS/Operator, : Test Action Performer, : BPON NE, Test Tracking Object : Factory, Test Object : Factory, : TestObject, and : Log. The sequence involves conducting a resource self-test, creating objects, setting defaults, performing tests, and storing results, with an exception handling path.](811d62d08ce934a2a7e5bd877abff7ad_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant TAP as : Test Action Performer + participant BPON as : BPON NE + participant TTOF as Test Tracking Object : Factory + participant TOF as Test Object : Factory + participant TO as : TestObject + participant Log as : Log + + OMS->>TAP: conductResourceSelfTest() + activate TAP + TAP->>TTOF: create() + activate TTOF + TAP->>TOF: setCreateDefault() + activate TOF + TAP->>TO: setActualTime() + activate TO + TAP->>BPON: doTest() + activate BPON + TAP->>TTOF: create() + activate TTOF + TAP->>TO: getTestStatus() + activate TO + deactivate TO + TAP->>TAP: terminateResourceSelfTest() + activate TAP + TAP->>BPON: getInterimResults() + activate BPON + deactivate BPON + TAP->>TO: setTestResults() + activate TO + deactivate TO + TAP->>TTOF: delete() + activate TTOF + deactivate TTOF + TAP->>Log: storeRecord() + activate Log + deactivate Log + TAP->>TO: getTestStatus() + activate TO + TO-->>TAP: Raises exception. + deactivate TO + deactivate TAP + +``` + +UML sequence diagram for a controlled test sequence. Lifelines include : OMS/Operator, : Test Action Performer, : BPON NE, Test Tracking Object : Factory, Test Object : Factory, : TestObject, and : Log. The sequence involves conducting a resource self-test, creating objects, setting defaults, performing tests, and storing results, with an exception handling path. + +Figure 6-61 – Controlled test sequence diagram + +![UML sequence diagram for 'Schedule test and view status' showing interactions between OMS Operator, TestAction Performer, TestTracking Object: Factory, Scheduler, BPQNE, TestHistory: Log, and RecordSetter.](401f020d9ab5904f584424eabb596d2c_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant TestActionPerformer as :TestAction Performer + participant TestTracking as TestTracking Object: Factory + participant Scheduler as :Scheduler + actor BPQNE as :BPQNE + participant TestHistory as TestHistory: Log + participant RecordSetter as :RecordSetter + + OMSOperator->>TestActionPerformer: scheduleMetallicDropTest() + activate TestActionPerformer + TestActionPerformer->>TestTracking: create() + activate TestTracking + TestTracking->>Scheduler: addAssociatedActivity() + deactivate TestTracking + TestActionPerformer->>TestTracking: scheduledTestNEListGet() + activate TestTracking + Note over TestTracking: Includes new scheduled test. + TestTracking->>TestActionPerformer: metallicDropTest() + deactivate TestTracking + activate TestActionPerformer + TestActionPerformer->>BPQNE: doTest() + activate BPQNE + BPQNE->>RecordSetter: storeRecord() + activate RecordSetter + RecordSetter-->>TestHistory: findRecords() + activate TestHistory + TestHistory-->>RecordSetter: + deactivate TestHistory + RecordSetter-->>BPQNE: + deactivate RecordSetter + BPQNE-->>TestActionPerformer: metallicDropTest() + deactivate BPQNE + deactivate TestActionPerformer + TestActionPerformer->>TestTracking: metallicDropTest() + activate TestTracking + TestTracking->>TestActionPerformer: doTest() + deactivate TestTracking + activate TestActionPerformer + TestActionPerformer->>BPQNE: storeRecord() + activate BPQNE + BPQNE->>RecordSetter: storeRecord() + activate RecordSetter + RecordSetter-->>TestHistory: + deactivate RecordSetter + BPQNE-->>TestActionPerformer: + deactivate BPQNE + deactivate TestActionPerformer + Note over TestTracking: Shows previous test completion. + TestActionPerformer->>TestTracking: getTestStatus() + activate TestTracking + TestTracking-->>TestActionPerformer: + deactivate TestTracking + deactivate TestActionPerformer + OMSOperator->>TestActionPerformer: selectRecords() + activate TestActionPerformer + TestActionPerformer->>RecordSetter: selectRecords() + activate RecordSetter + RecordSetter->>TestHistory: findRecords() + activate TestHistory + TestHistory-->>RecordSetter: + deactivate TestHistory + RecordSetter-->>TestActionPerformer: + deactivate RecordSetter + deactivate TestActionPerformer + Note over TestTracking: Shows all previous test completions. + TestActionPerformer->>TestTracking: cancelScheduledTest() + activate TestTracking + TestTracking->>TestActionPerformer: delete() + deactivate TestTracking + activate TestActionPerformer + TestActionPerformer->>Scheduler: removeAssociatedActivity() + activate Scheduler + Scheduler-->>TestActionPerformer: + deactivate Scheduler + deactivate TestActionPerformer + TestActionPerformer->>TestTracking: getTestStatus() + activate TestTracking + Note over TestTracking: Raises exception. + TestTracking-->>TestActionPerformer: + deactivate TestTracking + deactivate TestActionPerformer + OMSOperator->>TestActionPerformer: scheduledTestNEListGet() + activate TestActionPerformer + Note over TestTracking: Does n't include previously scheduled metallic drop test. + TestActionPerformer->>TestTracking: + deactivate TestActionPerformer + deactivate TestTracking + +``` + +UML sequence diagram for 'Schedule test and view status' showing interactions between OMS Operator, TestAction Performer, TestTracking Object: Factory, Scheduler, BPQNE, TestHistory: Log, and RecordSetter. + +Figure 6-62 – Schedule test and view status sequence diagram13 + +13 Using MetallicDropTest as one example. All other scheduled tests would have similar behavioural characteristics. + +##### Operations + +| Operation name | Operation purpose | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) aTMLoopback | This operation is used to invoke an ATM OAM loopback test. | +| 2) initializeContinuityCheck | This operation is used to prepare for an ATM continuity check. | +| 3) terminateContinuityCheck | This operation is used to take down the ATM continuity test environment. | +| 4) scheduleResourceSelfTest | This operation is used to schedule a resource self test. | +| 5) modifyTestSchedule | This operation is used to modify the schedule for a regularly conducted test. | +| 6) cancelScheduledTest | This operation is used to cancel a regularly scheduled test. | +| 7) conductResourceSelfTest | This operation is used to initiate a resource self test following the identification of a system fault or a subscriber service complaint. | +| 8) terminateResourceSelfTest | This operation terminates a resource self test in progress. | +| 9) initiateLoopback | This operation is used to initiate a loopback for a service. | +| 10) terminateLoopback | This operation is used to cancel a running loopback. | +| 11) getLoopbackInfo | This operation is used to retrieve the loopback information of a particular connection termination point. | +| 12) getLoopbackInfoByNE | This operation is used to retrieve the location and details of every connection point in an NE that are in loopback mode. | +| 13) getTestStatus | This operation is used to retrieve the status of a loopback in progress. | +| 14) scheduledTestNEListGet | This operation is used to retrieve the list of all scheduled NE testing. | +| 15) testHistoryByManagedEntity | This operation is used to retrieve the test history associated with a managed entity. | +| 16) testHistoryByServiceInstance | This operation is used to retrieve the test history associated with a service instance. | +| 17) metallicDropTest | This operation is used to conduct a metallic drop test following the identification of a system fault or a subscriber service complaint. | +| 18) scheduleMetallicDropTest | This operation is used to schedule a metallic drop test. | +| 19) mACLAYERTest | This operation is used to conduct a MAC layer test following the identification of a system fault or a subscriber service complaint. | +| 20) scheduleMACTest | This operation is used to schedule a MAC layer test. | +| 21) drawDialToneBreakTest | This operation is used to conduct a telephony service related test following the identification of a system fault or a subscriber service complaint. | +| 22) scheduleDrawDialToneBreakTest | This operation is used by the OMS to set up draw dialtone/break dialtone testing for telephony service ports to be executed at a regular basis. | + +**Figure 6-63 – Test action performer operations** + +##### Operation signatures14 + +| Operation name | Input parameters | Return value | Exceptions | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 1) aTMLoopback | UserIdType,
ManagedEntityType (TP),
ATMLoopbackInfoType,
TestIterationNumType,
ServiceInstanceIdType | AggregateATM
LoopbackResult
SeqType | AccessDenied,
CommFailure,
UnknownManagedEntity,
NotAvailableForTest,
InvalidLocationId,
InvalidDirection | +| 2) initializeContinuityCheck | UserIdType,
ManagedEntityType (TP),
ATMContinuityCheckInfoType,
GeneralizedTimeType,
ServiceInstanceIdType | CCSetUpIdType | AccessDenied,
CommFailure,
UnknownManagedEntity,
NotAvailableForTest,
InvalidStartTime,
InvalidStopTime,
InvalidDirection | +| 3) terminateContinuityCheck | CCSetUpIdType | void | AccessDenied,
CommFailure,
UnknownTest | +| 4) scheduleResourceSelfTest | UserIdType,
ManagedEntityType (NE),
unsigned long (timeout),
ResourceSelfTestInfoSeqType,
UserLabelType (scheduler) | TestTrackingObject
IdType | AccessDenied,
UnknownNE,
UnknownScheduler,
InvalidScheduler,
InvalidTimeoutPeriod,
InvalidTestOperations | +| 5) modifyTestSchedule | TestTrackingObjectIdType,
UserLabelType (new scheduler) | TestTrackingObject
IdType | UnknownTest,
UnknownScheduler,
InvalidScheduler,
AccessDenied | +| 6) cancelScheduledTest | TestTrackingObjectIdType | void | UnknownTest,
UncontrolledTestInProgress,
AccessDenied | +| 7) conductResourceSelfTest | UserIdType,
ManagedEntityType (NE),
unsigned long (timeout),
ResourceSelfTestInfoType | TestTracking
ObjectId | AccessDenied,
CommFailure,
UnknownNE,
InvalidTimeoutPeriod,
InvalidTestOperations | +| 8) terminateResourceSelfTest | TestTrackingObjectIdType | ResourceSelfTest
ResultSeqType | UnknownTest,
UncontrolledTestInProgress,
AccessDenied | +| 9) initiateLoopback | UserIdType,
ManagedEntityType (TP),
long (duration),
DirectionalityType,
LoopbackTestType,
ServiceInstanceIdType | LoopbackTracking
ObjectIdType | AccessDenied,
CommFailure,
UnknownManagedEntity,
NotAvailableForTest | +| 10) terminateLoopback | LoopbackTrackingObjectId | void | UnknownTest,
AccessDenied | +| 11) getLoopbackInfo | ManagedEntityType (TP) | LoopbackInfoType | UnknownManagedEntity,
AccessDenied | +| 12) getLoopbackInfoByNE | ManagedEntityType (NE) | LoopbackInfo
SeqType | UnknownManagedEntity,
AccessDenied | +| 13) getTestStatus | LoopbackTrackingObjectIdType | StatusValueType | UnknownTest,
AccessDenied | +| 14) scheduledTestNEListGet | | ScheduledTestNE
SeqType | AccessDenied | +| 15) testHistoryByManagedEntity | ManagedEntityType | TestHistorySeqType | AccessDenied,
UnknownManagedEntity | + +14 At the moment, controlled testing is not required for BPON network resources. However, for the sake of completeness, two operations called "requestControlledTest" and "requestScheduledControlledTest" have been included and shown in the sequence diagrams. Scheduled tests can be periodic. + +| Operation name | Input parameters | Return value | Exceptions | +|---------------------------------------|---------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------| +| 16) testHistoryByServiceInstance | ServiceInstanceIdType | TestHistorySeqType | AccessDenied,
UnknownServiceInstance | +| 17) metallicDropTest | UserIdType,
ManagedEntityIdType (port),
ServiceInstanceIdType | DropTestResultsType | AccessDenied,
CommFailure,
UnknownManagedEntity | +| 18) scheduleMetallicDropTest | UserIdType,
ManagedEntityIdType (port),
ServiceInstanceIdType,
UserLabelType (scheduler) | TestTrackingObject
IdType | AccessDenied,
UnknownManagedEntity,
UnknownScheduler,
InvalidScheduler | +| 19) mACLAYERTest | UserIdType,
ManagedEntityIdType (port),
ServiceInstanceIdType | short | AccessDenied,
CommFailure,
UnknownManagedEntity | +| 20) scheduleMACTest | UserIdType,
ManagedEntityIdType (port),
ServiceInstanceIdType,
UserLabelType (scheduler) | TestTrackingObject
IdType | AccessDenied,
UnknownManagedEntity,
UnknownScheduler,
InvalidScheduler | +| 21) drawDialToneBreakTest | UserIdType, ManagedEntityId
Type (port),
ServiceInstanceIdType | boolean | AccessDenied,
CommFailure,
UnknownManagedEntity | +| 22) scheduleDrawDialToneBreak
Test | UserIdType,
ManagedEntityIdType (port),
ServiceInstanceIdType,
UserLabelType (scheduler) | TestTrackingObject
IdType | AccessDenied,
UnknownManagedEntity,
UnknownScheduler,
InvalidScheduler | + +**Figure 6-64 – Test action performer signatures** + +##### Exceptions + +| Exception raised | Description | +|----------------------------|------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| InvalidDirection | Identified test operations unknown to the supplier management system. | +| InvalidLocationId | The LLID specified is not valid. | +| InvalidScheduler | The scheduler parameters values are outside defined scope. | +| InvalidStartTime | The new start time is inconsistent with the current trigger time matrix or the new stop time. | +| InvalidStopTime | The new stop time is inconsistent with the current trigger time matrix or the new start time. | +| InvalidTestOperations | The requested self test operation is not valid. | +| InvalidTimeoutPeriod | Designated timeout period violates definition of valid values. | +| NotAvailableForTest | The specified CTP is not available for this test. | +| UncontrolledTestInProgress | The scheduled test cannot be cancelled because of an uncontrolled test in progress. | +| UnknownManagedEntity | The specified managed entity is unknown to the supplier management system. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownScheduler | The named scheduler is unknown to the supplier management system. | +| UnknownServiceInstance | The service instance is unknown to the supplier management system. | +| UnknownTest | The test specified by the TestTrackingObjectId is not known in the supplier management system. | + +**Figure 6-65 – Test action performer exceptions** + +### 6.3.5 Installation + +#### 6.3.5.1 Synchronize NE and current event listing + +![Figure 6-66 – NE synchronization class diagram](487c58c79e44e6cf98b6368b6667b9c6_img.jpg) + +``` + +classDiagram + class ManagementInformationMaintainer["Management Information Maintainer"] + class Scheduler + class Factory { + +create() + +delete() + } + class NESynchroniser["NESynchroniser\nScheduledSynchNEList"] { + +synchNE() + +scheduleSynchNE() + +abortSynchNE() + +modifyNESynchSchedule() + +cancelScheduledSynchNE() + +synchCurrentEventListings() + +scheduledSynchNEListGet() + } + class Discoverer { + +getConfigurationData() + +getStatusData() + +getStateData() + } + class EventScreener["Event Screener"] + class EventQueue["Event Queue"] + class EventSetManager["Event Set Manager"] + class EventSet["Event Set"] + class Log { + +storeRecord() + +findRecords() + +displayByKey() + +displayRecords() + } + class CurrentEventListing["Current Event Listing"] { + +writeRecord() + +deleteRecord() + } + + class PrivilegedUser["Privileged User"] + class OMSOperator["OMS/Operator"] + class BPONNE["BPON NE"] { + +get() + } + + Scheduler --> NESynchroniser : triggers + ManagementInformationMaintainer --> NESynchroniser : consults + PrivilegedUser --> NESynchroniser : requests synchronization + Factory --> NESynchroniser : commissions + NESynchroniser --> Discoverer : gets details + Discoverer --> BPONNE : queries + BPONNE --> EventScreener : sends events + NESynchroniser --> EventScreener : sends discovery event + EventScreener --> EventQueue : queues to + EventQueue --> EventSetManager : extracts from + EventSetManager --> EventSet : creates + EventSet --> Log : logs event + EventScreener --> Log : updates + NESynchroniser --> Log : synchs + Log --> CurrentEventListing : writes to + OMSOperator --> CurrentEventListing : views + EventScreener --> EventSetManager : notifies + +``` + +Figure 6-66 – NE synchronization class diagram + +**Figure 6-66 – NE synchronization class diagram** + +90 + +ITU-T Rec. Q.834.3 (06/2004) + +![UML sequence diagram for NE synchronization requested by a privileged user. The diagram shows interactions between a Privileged User, NESynchroniser, Discoverer, Management Information Maintainer, BPQN NE, Managed Entity Factory, and Event Screener. Key steps include configuration data retrieval, entity creation/deletion, discovery event preparation, status/state data retrieval, and event listing preparation.](2dd10dd89365981b6b6154de6390a602_img.jpg) + +``` + +sequenceDiagram + actor User as : Privileged User + participant NESynchroniser as : NESynchroniser + participant Discoverer as : Discoverer + participant MIIM as : Management Information Maintainer + actor BPQN as : BPQN NE + participant MEF as : Managed Entity Factory + participant ES as : Event Screener + + User->>NESynchroniser: synchNE() + activate NESynchroniser + NESynchroniser->>Discoverer: getConfigurationData() + activate Discoverer + Discoverer->>BPQN: get() + activate BPQN + BPQN-->>NESynchroniser: + deactivate BPQN + NESynchroniser->>Discoverer: compare and update + activate Discoverer + Discoverer-->>MIIM: create() + activate MIIM + MIIM-->>Discoverer: + deactivate MIIM + Discoverer-->>MEF: delete() + activate MEF + MEF-->>Discoverer: + deactivate MEF + Discoverer->>NESynchroniser: prepareDiscoveryEvent + activate NESynchroniser + NESynchroniser-->>ES: readEvent() + activate ES + ES-->>NESynchroniser: + deactivate ES + NESynchroniser-->>User: + deactivate NESynchroniser + Note left of NESynchroniser: For all inventory data changes. + NESynchroniser->>Discoverer: getStatusData() + activate Discoverer + Discoverer->>BPQN: get() + activate BPQN + BPQN-->>Discoverer: + deactivate BPQN + Discoverer->>Discoverer: + deactivate Discoverer + NESynchroniser->>Discoverer: getStateData() + activate Discoverer + Discoverer->>BPQN: get() + activate BPQN + BPQN-->>Discoverer: + deactivate BPQN + Discoverer->>Discoverer: + deactivate Discoverer + NESynchroniser->>Discoverer: compare and update + activate Discoverer + Discoverer-->>MIIM: + deactivate Discoverer + NESynchroniser->>NESynchroniser: prepareEvent + activate NESynchroniser + NESynchroniser-->>ES: readEvent() + activate ES + ES-->>NESynchroniser: + deactivate ES + NESynchroniser-->>User: + deactivate NESynchroniser + Note left of NESynchroniser: For all current event listings. + +``` + +UML sequence diagram for NE synchronization requested by a privileged user. The diagram shows interactions between a Privileged User, NESynchroniser, Discoverer, Management Information Maintainer, BPQN NE, Managed Entity Factory, and Event Screener. Key steps include configuration data retrieval, entity creation/deletion, discovery event preparation, status/state data retrieval, and event listing preparation. + +Figure 6-67 – NE synchronization requested by privileged user sequence diagram + +![Sequence diagram for Synchronize current event listing. The diagram shows interactions between a Privileged User, NESynchroniser, Discoverer, BPON NE, Management Information Maintainer, Current Event Log, Event Screener, and CurrentEventListing. The process involves getting status and state data, comparing and updating, preparing an event, reading the event, and then writing or deleting records based on conditions.](b3335932702b8668e62791e9fd12c9ff_img.jpg) + +``` + +sequenceDiagram + actor User as Privileged User + participant NESynchroniser as :NESynchroniser + participant Discoverer as :Discoverer + participant BPON_NE as :BPON NE + participant MI_M as :Management Information Maintainer + participant CEL as Current Event Log + participant ES as :Event Screener + participant CEL_obj as :CurrentEventListing + + User->>NESynchroniser: synchCurrentEventListings() + activate NESynchroniser + NESynchroniser->>Discoverer: getStatusData() + activate Discoverer + Discoverer->>BPON_NE: get() + activate BPON_NE + BPON_NE-->>Discoverer: + deactivate BPON_NE + NESynchroniser->>Discoverer: getStateData() + activate Discoverer + Discoverer->>BPON_NE: get() + activate BPON_NE + BPON_NE-->>Discoverer: + deactivate BPON_NE + NESynchroniser->>MI_M: compare and update + activate MI_M + MI_M-->>NESynchroniser: + deactivate MI_M + NESynchroniser->>MI_M: prepareEvent + activate MI_M + MI_M-->>NESynchroniser: + deactivate MI_M + NESynchroniser->>ES: readEvent() + activate ES + ES->>CEL_obj: writeRecord() + activate CEL_obj + CEL_obj-->>ES: + deactivate CEL_obj + ES->>CEL_obj: deleteRecord() + activate CEL_obj + CEL_obj-->>ES: + deactivate CEL_obj + ES-->>NESynchroniser: + deactivate ES + NESynchroniser-->>User: + deactivate NESynchroniser + + Note left of NESynchroniser: For all changed conditions. + Note right of ES: Proceed with event processing as described in Appendix A. + Note right of CEL_obj: For new outstanding conditions. + Note left of CEL_obj: For return to normal conditions. + +``` + +Sequence diagram for Synchronize current event listing. The diagram shows interactions between a Privileged User, NESynchroniser, Discoverer, BPON NE, Management Information Maintainer, Current Event Log, Event Screener, and CurrentEventListing. The process involves getting status and state data, comparing and updating, preparing an event, reading the event, and then writing or deleting records based on conditions. + +Figure 6-68 – Synchronize current event listing sequence diagram + +![UML sequence diagram for Scheduled synchronization. Lifelines: :Privileged User, :NESynchronizer, :Scheduler, :Discoverer, :BPCON NE, :Management Information Maintainer, :Managed Entity Factory, :Event Screener, :Scheduler. Operations: scheduleSynchNEListGet(), scheduleSynchNE(), addAssociatedActivity(), scheduleSynchNEListGet() (with note: Shows additional scheduled synchronizations.), abortSynchNE() (with note: Raises exception.), synchNE(), getConfigurationData(), get(), compare and update, create(), delete(), prepareDiscoverEvent(), readEvent(), abortSynchNE(), scheduleSynchNEListGet() (with note: Shows same scheduled synchronizations.), modifyNESynchSchedule(), removeAssociatedActivity(), addAssociatedActivity(), cancelScheduledSynchNE(), deleteAssociatedActivity(), scheduleSynchNEListGet() (with note: Shows same as at the top.).](a37adbbe12ec735a20ead2466363d07a_img.jpg) + +UML sequence diagram for Scheduled synchronization. Lifelines: :Privileged User, :NESynchronizer, :Scheduler, :Discoverer, :BPCON NE, :Management Information Maintainer, :Managed Entity Factory, :Event Screener, :Scheduler. Operations: scheduleSynchNEListGet(), scheduleSynchNE(), addAssociatedActivity(), scheduleSynchNEListGet() (with note: Shows additional scheduled synchronizations.), abortSynchNE() (with note: Raises exception.), synchNE(), getConfigurationData(), get(), compare and update, create(), delete(), prepareDiscoverEvent(), readEvent(), abortSynchNE(), scheduleSynchNEListGet() (with note: Shows same scheduled synchronizations.), modifyNESynchSchedule(), removeAssociatedActivity(), addAssociatedActivity(), cancelScheduledSynchNE(), deleteAssociatedActivity(), scheduleSynchNEListGet() (with note: Shows same as at the top.). + +Figure 6-69 – Scheduled synchronization sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) synchNE 15 | This operation initiates a synchronization process between the supplier management system and a specific NE. | +| 2) abortSynchNE | This operation aborts a synchronization process in progress between the supplier management system and a specific NE. | +| 3) scheduleSynchNE | This operation schedules a synchronization process between the supplier management system and a specific NE. | +| 4) modifyNESynchSchedule | This operation modifies the schedule for NE synchronization. | +| 5) cancelScheduledSynchNE | This operation cancels all subsequent scheduled synchronization processes for this NE. | +| 6) synchCurrentEventListings | The operation initiates synchronization between the supplier management system and specified NE for items in particular current event listings. | +| 7) scheduledSynchNEListGet | This operation is used to retrieve the names of all NEs with synchronization schedules. | + +Figure 6-70 – NE synchronizer operations + +15 The "synch" operation is a best effort attempt. If the results are suspect as detected by the supplier management system, then the suspect flag is set to TRUE. + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|------------------------------|------------------------------------------------------------|-----------------------------|----------------------------------------------------------------------------------------------------------| +| 1) synchNE | ManagedEntityIdType (NE) | void | AccessDenied,
CommFailure,
UnknownNE,
EquipmentFailure,
BackupInProgress,
SynchInProgress | +| 2) abortSynchNE | ManagedEntityIdType (NE) | void | AccessDenied,
CommFailure,
UnknownNE,
EquipmentFailure,
NoSynchInProgress | +| 3) scheduleSynchNE | ManagedEntityIdType (NE),
UserLabelType (scheduler) | void | AccessDenied,
UnknownNE,
UnknownScheduler,
InvalidScheduler | +| 4) modifyNESynchSchedule | ManagedEntityIdType (NE),
UserLabelType (new scheduler) | void | AccessDenied,
UnknownNE,
UnknownScheduler,
InvalidScheduler,
SynchNotScheduled | +| 5) cancelScheduledSynchNE | ManagedEntityIdType (NE) | void | AccessDenied,
UnknownNE | +| 6) synchCurrentEventListings | ManagedEntityIdType,
CurrentListingSeqType | void | AccessDenied,
CommFailure,
DCNTimeout,
UnknownNE,
EquipmentFailure,
Timeout | +| 7) scheduledSynchNEListGet | | ScheduledSynchNE
SeqType | AccessDenied | + +**Figure 6-71 – NE synchronizer signatures** + +##### Exceptions + +| Exception raised | Description | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| BackupInProgress | This exception is raised when the request is issued while the backup is in progress. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| DCNTimeout | The DCN communications link between at least one of the NEs and the supplier management system is so congested that current state or status information cannot be transferred within a system-defined synch time. | +| EquipmentFailure | The NE currently has a failure condition preventing the requested transaction from being completed. | +| InvalidScheduler | The scheduler parameter's values are outside defined scope. | +| NoSynchInProgress | The exception is raised if there is no synchronization process is in progress. | +| SynchInProgress | An operation is requested while the supplier management system is in the process of synchronizing with the NE, which prohibits the execution of the operation requested. | +| Timeout | The process duration reached a system-defined timeout before the process could complete. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownScheduler | The named scheduler is unknown to the supplier management system. | +| SynchNotScheduled | This exception is raised when the schedule modification references an NE for which no synchronization schedule has previously been established. | + +**Figure 6-72 – NE synchronizer exceptions** + +#### 6.3.5.2 Range ONT or ONU and register OLT + +![Registration class diagram showing the interactions between various components for registering an ONT or ONU and registering an OLT.](48adb97a6a4a14b039450192f25cc1e0_img.jpg) + +``` + +classDiagram + class EventScreener + class NERegistrar { + +SerialNumberList + +OLTDCNAddressList + +rangeReplacementNE() + +rangeONTorONU() + +registerNE() + +modifyNEDCNAddress() + +rangeUpgradeNE() + +moveONTorONU() + +getSubstendingNEList() + +nEListGet() + +deRegisterNE() + +associateNE() + } + class RecordSetMgr + class Log + class Discoverer { + +getConfigurationData() + +getStatusData() + +getStateData() + } + class OLTCommunicator { + +sendKeepAliveMessage() + +raiseCommAlarm() + +terminateKeepAliveMessage() + } + class BPONNE { + +get() + +range() + +set() + } + class ManagementModelMaintainer + class Builder + class Factory { + +create() + +delete() + } + class APONLink + class OLT + class APONLinkConnection + class APONLogicalLinkEnd + class APONCTP + class APONTTP + class APONTrail + class vpLinkConnectionF + class vpTopologicalLinkF + class pluginUnitF + class equipmentHolderF + class FSANNE + class toAdaptorF + class TPF + class CTPF + class TTPF + + EventScreener --> NERegistrar : notifies + NERegistrar --> RecordSetMgr : selects discovery record + RecordSetMgr --> Log : finds + NERegistrar --> Discoverer : gets details + Discoverer --> NERegistrar : enrolls + NERegistrar --> OLTCommunicator : DCN Validation + OLTCommunicator --> NERegistrar : +Comm Agent + NERegistrar --> BPONNE : constructs + BPONNE --> NERegistrar : checks DCN + NERegistrar --> ManagementModelMaintainer : consults and updates + ManagementModelMaintainer --> APONLink : updates + ManagementModelMaintainer --> OLT : updates substending list + ManagementModelMaintainer --> Builder : modifies + Builder --> Factory : commissions + Factory --> pluginUnitF : creates + Factory --> equipmentHolderF : creates + Factory --> FSANNE : creates all types + Factory --> toAdaptorF : creates at ONT PON port + Factory --> TPF : creates TPs at ports + Factory --> Port : creates + Factory --> APONLinkConnection : creates EOC + Factory --> APONLogicalLinkEnd : creates by ranging + Factory --> APONCTP : creates to describe capacity on ONT PON port + Factory --> APONTTP : creates + Factory --> vpLinkConnectionF : creates + Factory --> vpTopologicalLinkF : creates + APONLinkConnection --> APONLogicalLinkEnd + APONCTP --> APONTTP + TPF --> CTPF + TPF --> TTPF + +``` + +The diagram illustrates the registration process for an ONT or ONU and the registration of an OLT. Key components and their interactions include: + +- Event Screener** notifies the **NERegistrar**. +- NERegistrar** (containing `SerialNumberList` and `OLTDCNAddressList`) interacts with **RecordSetMgr** (selects discovery record) and **Log** (finds). +- NERegistrar** gets details from **Discoverer** and enrolls it. +- NERegistrar** performs DCN Validation with **OLT Communicator**, which acts as a `+Comm Agent`. +- NERegistrar** constructs **BPON NE**, which checks DCN. +- NERegistrar** consults and updates the **Management Model Maintainer**. +- Management Model Maintainer** updates **APONLink** and updates the substending list for **OLT**. +- Management Model Maintainer** modifies the **Builder**. +- Builder** commissions the **Factory**. +- Factory** (with `create()` and `delete()`) creates various components: + - `pluginUnitF`, `equipmentHolderF`, `FSANNE` (creates all types), `toAdaptorF` (creates at ONT PON port), `TPF` (creates TPs at ports), `Port`. + - `APONLinkConnection` (creates EOC), `APONLogicalLinkEnd` (creates by ranging), `APONCTP` (creates to describe capacity on ONT PON port), `APONTTP`. + - `vpLinkConnectionF` and `vpTopologicalLinkF`. +- Factory** also creates **APONTrail**. +- APONLinkConnection** is associated with **APONLogicalLinkEnd**. +- APONCTP** is associated with **APONTTP**. +- TPF** is associated with **CTPF** and **TTPF**. + +Registration class diagram showing the interactions between various components for registering an ONT or ONU and registering an OLT. + +Figure 6-73 – Registration class diagram + +![UML sequence diagram for Register NE. Lifelines: :OMS/Operator, :NERegistrar, :OLT Communicator, OLT: BPON NE, :Discoverer, :Builder, Managed Entity : Factory, : Management Model Maintainer. Messages: registerNE(), sendKeepAliveMessage(), get(), getConfigurationData(), checkUserLabel, getStatusData(), getStateData(), buildNode(), buildPlugInUnit(), modifyPort(), create(), update(), nEListGet(). Notes: 'Periodically performed.', 'As required based on discovery.', 'Includes new OLT.'](3a006a7c9c9934695f0fc731344eff8a_img.jpg) + +``` + +sequenceDiagram + actor OMS as :OMS/Operator + participant NERegistrar as :NERegistrar + participant OLTComm as :OLT Communicator + participant OLT as OLT: BPON NE + participant Discoverer as :Discoverer + participant Builder as :Builder + participant Factory as Managed Entity : Factory + participant Maintainer as : Management Model Maintainer + + OMS->>NERegistrar: registerNE() + NERegistrar->>OLTComm: sendKeepAliveMessage() + OLTComm->>OLT: get() + Note over OLTComm: Periodically performed. + OLTComm->>Discoverer: getConfigurationData() + Discoverer->>OLTComm: get() + OLTComm->>NERegistrar: checkUserLabel + NERegistrar->>Discoverer: getStatusData() + Discoverer->>OLTComm: get() + NERegistrar->>Discoverer: getStateData() + Discoverer->>OLTComm: get() + NERegistrar->>Builder: buildNode() + Builder->>Factory: create() + Note over NERegistrar: As required based on discovery. + NERegistrar->>Builder: buildPlugInUnit() + Builder->>Factory: create() + NERegistrar->>Builder: modifyPort() + Builder->>Maintainer: update() + OMS->>NERegistrar: nEListGet() + Note over NERegistrar: Includes new OLT. + +``` + +UML sequence diagram for Register NE. Lifelines: :OMS/Operator, :NERegistrar, :OLT Communicator, OLT: BPON NE, :Discoverer, :Builder, Managed Entity : Factory, : Management Model Maintainer. Messages: registerNE(), sendKeepAliveMessage(), get(), getConfigurationData(), checkUserLabel, getStatusData(), getStateData(), buildNode(), buildPlugInUnit(), modifyPort(), create(), update(), nEListGet(). Notes: 'Periodically performed.', 'As required based on discovery.', 'Includes new OLT.' + +Figure 6-74 – Register NE sequence diagram16 + +16 Applies only to OLT. + + + +![Sequence diagram for Deregister NE. The diagram shows the interaction between :OMS/Operator, :NERRegistrar, :BPON NE, :Management Model Maintainer, :OLT Communicator, Managed Entity Factory, and :Builder. The process starts with :OMS/Operator calling deRegisterNE() on :NERRegistrar. :NERRegistrar then calls narrowByContainment() on :BPON NE. :NERRegistrar calls modifyPort() on :Management Model Maintainer, which then calls update() on :Builder. :NERRegistrar calls modifyNode() on :Management Model Maintainer, which then calls update() on :Builder. :NERRegistrar calls deletePlugInUnit() on :Management Model Maintainer, which then calls delete() on :Builder. :NERRegistrar calls deleteNode() on :Management Model Maintainer, which then calls delete() on :Builder. Finally, :NERRegistrar calls terminateKeepAliveMessage() on :OLT Communicator. A note indicates that the update and delete calls are 'As required based on existing management information fragment.'](df803281854ce2cbde7019b5aeefd8cd_img.jpg) + +``` + +sequenceDiagram + actor OMS as :OMS/Operator + participant NER as :NERRegistrar + participant BPON as :BPON NE + participant MM as :Management Model Maintainer + participant OLT as :OLT Communicator + participant MEF as Managed Entity Factory + participant Builder as :Builder + + OMS->>NER: deRegisterNE() + activate NER + NER->>BPON: narrowByContainment() + activate BPON + BPON->>MM: modifyPort() + activate MM + MM->>Builder: update() + activate Builder + Builder->>MM: + deactivate Builder + MM->>BPON: + deactivate MM + NER->>MM: modifyNode() + activate MM + MM->>Builder: update() + activate Builder + Builder->>MM: + deactivate Builder + MM->>BPON: + deactivate MM + NER->>MM: deletePlugInUnit() + activate MM + MM->>Builder: delete() + activate Builder + Builder->>MM: + deactivate Builder + MM->>BPON: + deactivate MM + NER->>MM: deleteNode() + activate MM + MM->>Builder: delete() + activate Builder + Builder->>MM: + deactivate Builder + MM->>BPON: + deactivate MM + NER->>OLT: terminateKeepAliveMessage() + activate OLT + OLT->>OLT: + deactivate OLT + deactivate NER + +``` + +As required based on existing management information fragment. + +Sequence diagram for Deregister NE. The diagram shows the interaction between :OMS/Operator, :NERRegistrar, :BPON NE, :Management Model Maintainer, :OLT Communicator, Managed Entity Factory, and :Builder. The process starts with :OMS/Operator calling deRegisterNE() on :NERRegistrar. :NERRegistrar then calls narrowByContainment() on :BPON NE. :NERRegistrar calls modifyPort() on :Management Model Maintainer, which then calls update() on :Builder. :NERRegistrar calls modifyNode() on :Management Model Maintainer, which then calls update() on :Builder. :NERRegistrar calls deletePlugInUnit() on :Management Model Maintainer, which then calls delete() on :Builder. :NERRegistrar calls deleteNode() on :Management Model Maintainer, which then calls delete() on :Builder. Finally, :NERRegistrar calls terminateKeepAliveMessage() on :OLT Communicator. A note indicates that the update and delete calls are 'As required based on existing management information fragment.' + +Figure 6-76 – Deregister NE sequence diagram + + + +![UML sequence diagram for 'Move ONT or ONU' showing interactions between OMS Operator, NE Registrar, OLT A, BPON NEOLT B, BPON NEONT or ONU, Builder, Management Model Maintainer, Managed Entity Factory, and Discoverer. The diagram includes various messages like getSubtreeIncludingNELink(), get(), modifyNode(), range(), getConfigData(), getStateData(), deletePlugInUnit(), deleteNode(), and delete(). It also contains several notes explaining specific actions and conditions.](9687bd5e8b62cadba093b0d1b70536cd_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant NERegistrar as :NERegistrar + participant OLTAB as OLT A : BPON NEOLT B + participant BPONNE as BPON NEONT or ONU : BPON NE + participant Builder as :Builder + participant ManagementModel as :Management Model Maintainer + participant ManagedEntityFactory as Managed Entity : Factory + participant Discoverer as :Discoverer + + OMSOperator->>NERegistrar: getSubtreeIncludingNELink() + NERegistrar->>OLTAB: get() + Note over OLTAB: Shows ONT or ONU to be moved. + OMSOperator->>NERegistrar: moveONTorONU() + Note over OMSOperator: Includes all the subsequent behaviour and classes found in rangeONTorONU. + OMSOperator->>Builder: modifyNode() + Note over Builder: To avoid unnecessary alarms. + Builder->>ManagementModel: update() + OMSOperator->>OLTAB: range() + OLTAB->>BPONNE: range() + OMSOperator->>Discoverer: getConfigData() + Discoverer->>OLTAB: get() + OMSOperator->>Discoverer: getStateData() + Discoverer->>OLTAB: get() + OMSOperator->>Discoverer: getStateData() + Discoverer->>OLTAB: get() + OMSOperator->>Discoverer: getStateData() + Discoverer->>OLTAB: get() + Note over OMSOperator: Associate ONT with OLT B. + OMSOperator->>ManagementModel: update() + OMSOperator->>ManagementModel: narrowByConstraint() + OMSOperator->>Builder: deletePlugInUnit() + Note over Builder: As needed. + Builder->>ManagementModel: deleteNode() + ManagementModel->>ManagedEntityFactory: delete() + Note over ManagedEntityFactory: As needed based on management information fragment. + ManagedEntityFactory->>Discoverer: update() + Discoverer->>ManagementModel: delete() + ManagementModel->>ManagedEntityFactory: delete() + ManagedEntityFactory->>Discoverer: update() + OMSOperator->>NERegistrar: getSubtreeIncludingNELink() + NERegistrar->>OLTAB: get() + Note over OLTAB: Includes new ONT or ONU. + OMSOperator->>NERegistrar: getSubtreeIncludingNELink() + NERegistrar->>OLTAB: get() + Note over OLTAB: Doesn't show ONT or ONU. + +``` + +UML sequence diagram for 'Move ONT or ONU' showing interactions between OMS Operator, NE Registrar, OLT A, BPON NEOLT B, BPON NEONT or ONU, Builder, Management Model Maintainer, Managed Entity Factory, and Discoverer. The diagram includes various messages like getSubtreeIncludingNELink(), get(), modifyNode(), range(), getConfigData(), getStateData(), deletePlugInUnit(), deleteNode(), and delete(). It also contains several notes explaining specific actions and conditions. + +Figure 6-78 – Move ONT or ONU sequence diagram + +![UML sequence diagram for upgrading an ONT or ONU. The diagram shows interactions between an OMS Operator, a Builder, a Service Provider, a NE Registrar, and three ONT/ONU entities (OLT, ONT A, ONT B). The process involves building nodes, modifying ports, provisioning connections, upgrading NEs, associating services, and deleting old nodes.](301f4a188198a15b1415d54545b07e0d_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant Builder as :Builder + participant ServiceProvider as :Service Provider + participant NERegistrar as :NERegistrar + participant OLT as OLT : BPON NE + participant ONTA as ONT A : BPON NE + participant ONTB as ONT B : BPON NE + participant Builder2 as :Builder + participant ManagementModel as :Management Model Maintainer + participant ManagedEntity as Managed Entity : Factory + + OMSOperator->>Builder: buildNode() + Note over Builder: As required by new hardware type and including all install classes and behaviour for strict construction. + OMSOperator->>Builder: buildPlugInUnit() + OMSOperator->>Builder: modifyPort() + Note over Builder: As required for new desired services and including all install classes and behaviour for strict construction. + OMSOperator->>Builder: provisionConnection() + Note over Builder: Proceeds as in rangeONTorONU with associated classes and behaviour. + OMSOperator->>NERegistrar: rangeUpgradeNE() + NERegistrar->>Builder2: modifyNode(ONT A) + Builder2->>ManagementModel: update() + NERegistrar->>OLT: range() + OLT->>ONTA: range() + NERegistrar->>ONTA: associateNE() + Note over NERegistrar: Associates new desired services. + NERegistrar->>ONTA: set() + Note over NERegistrar: Associates existing desired services. + NERegistrar->>ONTA: deleteNode(ONT A) + Note over NERegistrar: Doesn't show any change unless MEd changes. + NERegistrar->>Builder2: deleteNode(ONT A) + Builder2->>ManagementModel: delete() + ManagementModel->>ManagedEntity: update() + OMSOperator->>NERegistrar: NEListGet() + Note over NERegistrar: Does not show any change unless MEd changes. + OMSOperator->>NERegistrar: getSubordinateNEList() + NERegistrar->>OLT: get() + +``` + +UML sequence diagram for upgrading an ONT or ONU. The diagram shows interactions between an OMS Operator, a Builder, a Service Provider, a NE Registrar, and three ONT/ONU entities (OLT, ONT A, ONT B). The process involves building nodes, modifying ports, provisioning connections, upgrading NEs, associating services, and deleting old nodes. + +Figure 6-79 – Upgrade ONT or ONU sequence diagram + +![Sequence diagram for Automatic ranging showing interactions between OMS/Operator, Builder, Service Provisioner, Event Screener, NERegistrar, Event Forwarder, Event Supplier, External Event Channel, NESynchroniser, and BPON NE. The diagram includes messages like buildNede(), buildPlugInUnit(), modifyPort(), provisionConnection(), nEListGet(), notify, processAnnouncement, pushEvent(), push(), synchNE(), get(), consumeEvent(), and associateNE(), along with several explanatory notes.](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as OMS/Operator + participant Builder + participant ServiceProvisioner + participant EventScreener + participant NERegistrar + participant EventForwarder + participant EventSupplier + participant ExternalEventChannel as External Event Channel + participant NESynchroniser + participant BPONNE as BPON NE + + OMSOperator->>Builder: buildNede() + OMSOperator->>Builder: buildPlugInUnit() + Note over Builder: As required by new hardware and including all usual classes and behaviour for such construction. + OMSOperator->>Builder: modifyPort() + Note over Builder: As required for new desired services and including all usual classes and behaviour for such construction. + OMSOperator->>ServiceProvisioner: provisionConnection() + OMSOperator->>NERegistrar: nEListGet() + Note over NERegistrar: Shows no change. + NERegistrar->>EventForwarder: notify + Note over EventForwarder: Autodiscovery based on automatic ranging. + EventForwarder->>EventSupplier: pushEvent() + EventSupplier->>ExternalEventChannel: push() + ExternalEventChannel->>NESynchroniser: synchNE() + Note over NESynchroniser: Synch of Supplier Management System db and NE db shown only at a high-level. + NESynchroniser->>BPONNE: get() + BPONNE->>NERegistrar: consumeEvent() + NERegistrar->>Builder: associateNE() + OMSOperator->>NERegistrar: nEListGet() + Note over NERegistrar: Shows new ONT or ONU. + +``` + +Sequence diagram for Automatic ranging showing interactions between OMS/Operator, Builder, Service Provisioner, Event Screener, NERegistrar, Event Forwarder, Event Supplier, External Event Channel, NESynchroniser, and BPON NE. The diagram includes messages like buildNede(), buildPlugInUnit(), modifyPort(), provisionConnection(), nEListGet(), notify, processAnnouncement, pushEvent(), push(), synchNE(), get(), consumeEvent(), and associateNE(), along with several explanatory notes. + +**Figure 6-80 – Automatic ranging sequence diagram** + +##### Operations + +| Operations name | Operation purpose | +|------------------------|---------------------------------------------------------------------------------------------------------------------------| +| 1) registerNE | This operation registers an NE with a particular instance of supplier management system. | +| 2) modifyNEDCNAddress | This operation changes the DCN address of a registered NE. | +| 3) rangeONTorONU | This operation ranges an ONT or ONU using the serial number of the PON interface of the NE. | +| 4) rangeReplacementNE | This operation ranges a replacement ONT or ONU using the serial number of the replacement equipment. | +| 5) rangeUpgradeNE | This operation ranges a replacement NE for the purposes of upgrading the hardware. | +| 6) moveONTorONU | This operation is used to move an ONT or ONU from one PON to another and also move all of the associated services. | +| 7) getSubtendingNEList | This operation returns all subtending NEs of a particular NE. | +| 8) nEListGet | This operation retrieves the network elements under the management jurisdiction of the supplier management system. | +| 9) deRegisterNE | This operation removes the network element from the management jurisdiction of the supplier management system. | +| 10) associateNE | This operation associates pre-provisioning information with a network element that has been installed and autodiscovered. | + +**Figure 6-81 – NE registrar operations** + +##### Operation signatures17 + +| Operations name | Input parameters | Return value | Exceptions | +|-----------------------|------------------------------------------------------------------------------------------------------------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) registerNE | DCNAddressType,
UserLabelType,
AdministrationDomainType | ManagedEntityIdType | AccessDenied,
DCNTimeout,
AddressLabelMismatch,
DuplicateUserLabel,
TooManyNEs,
InvalidDCNAddress,
DeniedAccess,
InvalidUserLabelSyntax | +| 2) modifyNEDCNAddress | ManagedEntityIdType,
DCNAddressType | void | AccessDenied,
DeniedAccess,
AddressLabelMismatch,
DCNTimeout,
CommFailure,
UnknownNE,
InvalidDCNAddress,
BackupInProgress | +| 3) rangeONTorONU | ManagedEntityIdType (OLT),
UserLabelType,
SerialNumType,
ManagedEntityIdType (port) | void | AccessDenied,
CommFailure,
EquipmentFailure,
UnknownNE,
UnknownPort,
MaxSubtendingNodesExceeded,
InsufficientPONBW,
InvalidSerialNumSyntax,
APONLayerFailure,
DuplicateUserLabel,
InvalidUserLabelSyntax,
BackupInProgress,
SynchInProgress | +| 4) rangeReplacementNE | ManagedEntityIdType (old NE),
UserLabelType,
SerialNumType | ManagedEntityIdType | AccessDenied,
CommFailure,
UnknownNE,
InvalidSerialNumSyntax,
APONLayerFailure,
EquipmentFailure,
InvalidUserLabelSyntax,
HWServicesMismatch,
DuplicateUserLabel,
BackupInProgress,
SynchInProgress | +| 5) rangeUpgradeNE | ManagedEntityIdType (old NE),
ManagedEntityIdType
(pre-provisioned NE),
UserLabelType,
SerialNumType | ManagedEntityIdType | AccessDenied,
CommFailure,
APONLayerFailure,
EquipmentFailure,
InvalidUserLabelSyntax,
DuplicateUserLabel,
UnknownNE,
HWServicesMismatch,
InsufficientPONBW,
BackupInProgress,
SynchInProgress | + +17 The operation "rangeNewONU" has the same behaviour as "rangeNewONT" so there was no apparent need to show another sequence diagram. + +| Operations name | Input parameters | Return value | Exceptions | +|------------------------|------------------------------------------------------------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6) moveONTorONU | ManagedEntityType (old NE),
ManagedEntityType (new port) | ManagedEntityType | AccessDenied,
CommFailure,
UnknownNE,
UnknownPort,
APONLayerFailure,
EquipmentFailure,
InsufficientPONBW,
BackupInProgress,
SynchInProgress | +| 7) getSubtendingNEList | ManagedEntityType (subtended NE) | ManagedEntityIdSeqType | UnknownNE,
AccessDenied | +| 8) nEListGet | | ManagedEntityIdSeqType | AccessDenied | +| 9) deRegisterNE | ManagedEntityType | void | AccessDenied | +| 10) associateNE | ManagedEntityType (pre-provisioned NE),
ManagedEntityType (discovered NE) | ManagedEntityType | AccessDenied,
UnknownManagedEntity | + +**Figure 6-82 – NE registrar signatures** + +##### Exceptions + +| Exception raised | Description | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| AddressLabelMismatch | The identified NE does not have the current DCN address provided in the request. | +| APONLayerFailure | There was an APON protocol ranging failure between the OLT and the designed subtending node. | +| BackupInProgress | This exception is raised when the request is issued while the backup is in progress. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| DCNTimeout | The DCN communications link between at least one of the NEs and the supplier management system is so congested that current state or status information cannot be transferred within a system-defined synch time. | +| DeniedAccess | System is not granted access to the NE. | +| DuplicateUserLabel | The user label provided in the request has been used to label another archive, i.e., one that is defined by a different set of creation request parameters. | +| EquipmentFailure | The NE currently has a failure condition preventing the requested transaction from being completed. | +| HWServicesMismatch | The replacement NE cannot perform the provisioned services. | +| InsufficientPONBW | The ONT or ONU cannot be ranged due to insufficient bandwidth on the APONLink. | +| InvalidDCNAddress | The specified DCN address is not valid. | +| InvalidSerialNumSyntax | Syntax of the serial number provided does not match definition rules. | +| InvalidUserLabelSyntax | The specified user label does not follow established rules for user label. | +| MaxSubtendingNodesExceeded | The maximum engineered number of subtending nodes for the identified PON interface has been exceeded with this request for service provisioning. | +| SynchInProgress | An operation is requested while the supplier management system is in the process of synchronizing with the NE that prohibits the execution of the operation requested. | +| TooManyNEs | The supplier management system cannot manage one more OLT. | +| UnknownManagedEntity | The specified managed entity is unknown to the supplier management system. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownPort | The identified port is unknown to the supplier management system. | + +**Figure 6-83 – NE registrar exceptions** + +### 6.3.6 Provisioning + +#### 6.3.6.1 Build BPON resources + +This clause shows the construction of management infrastructure to support the management of an OLT, an ONT or ONU, and of a port. In each case, a class diagram is followed by the associated sequence diagram. + +![UML Class Diagram for Build BPON resources](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +The diagram illustrates the Build BPON resources class diagram. It features the following components and relationships: + +- internal use case**: A rectangular box with a double-line border. +- Builder**: A central class containing: + - Attributes: `CreatedNodesList`, `ManagedEntityFragments`. + - Operations: `buildNode()`, `modifyNode()`, `deleteNode()`, `modifyPort()`, `buildPlugInUnit()`, `modifyPlugInUnit()`, `deletePlugInUnit()`, `assignUserLabelsToNE()`, `buildProtectionGrouping()`, `modifyProtectionParameters()`, `modifyProtectionUnitList()`, `deleteProtectionGrouping()`, `buildBridge()`, `deleteBridge()`, `modifyBridgePortList()`, `modifyBridgeProfile()`, `buildVPNetworkCTP()`, `deleteVPNetworkCTP()`, `buildTCONT()`, `deleteTCONT()`, `modifyTCONTParameters()`, and `createdNodesGet()`. +- Management Model Maintainer**: A class containing operations `update()` and `scopeFilter()`. +- Profile Object Repository**: A class containing the operation `retrieve()`. +- Factory**: A class containing operations `create()` and `delete()`. +- Actors**: `OMS/Operator` (represented by a stick figure) and `Profile Object Repository` (represented by a stick figure). + +Relationships and Messages: + +- internal use case** to **Builder**: `constructs entity` (solid arrow). +- OMS/Operator** to **Builder**: `constructs entity` (solid arrow). +- Builder** to **Management Model Maintainer**: `consults and updates` (solid arrow). +- Builder** to **Profile Object Repository**: `retrieves Profile values` (solid arrow). A note "Only if Profile is unknown." is attached to this message. +- Builder** to **Factory**: `commissions` (solid arrow). +- Profile Object Repository** to **Builder**: `retrieve()` (solid arrow). + +UML Class Diagram for Build BPON resources + +Figure 6-84 – Build class diagram + +![UML sequence diagram showing interactions between OMS/Operator, Builder, Managed Entity Factory, and Management Model Maintainer for build, modify, and delete operations.](0f007a07756791edf7be50672cb010a4_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant Builder as : Builder + participant Factory as Managed Entity : Factory + participant Maintainer as : Management Model Maintainer + + OMS->>Builder: buildNode() + activate Builder + Builder->>Factory: create() + activate Factory + Factory-->>Maintainer: + deactivate Factory + Note right of Maintainer: Create all managed entities in management information fragment for node entity. + Builder->>Builder: deactivate + OMS->>Builder: modifyNode() + activate Builder + Builder->>Maintainer: updates() + activate Maintainer + Note right of Maintainer: Assigns new values to relevant management information fragment managed entities. + Maintainer-->>Builder: + deactivate Maintainer + Builder->>Builder: deactivate + OMS->>Builder: assignUserLabelsToNE() + activate Builder + Builder->>Maintainer: updates() + activate Maintainer + Note right of Maintainer: Raises exception if there are remaining subnetwork connections or reservations. + Maintainer-->>Builder: + deactivate Maintainer + Builder->>Builder: deactivate + OMS->>Builder: deleteNode() + activate Builder + Builder->>Maintainer: scopeFilter() + activate Maintainer + Note right of Maintainer: + Maintainer->>Factory: delete() + activate Factory + Factory-->>Maintainer: + deactivate Factory + Maintainer-->>Builder: + deactivate Maintainer + Note right of Maintainer: Delete all managed entities in management information fragment for node entity. + Builder->>Builder: deactivate + +``` + +The diagram illustrates the sequence of operations for building, modifying, and deleting a node entity. The participants involved are the OMS/Operator (Actor), the Builder (Boundary), the Managed Entity Factory (Control), and the Management Model Maintainer (Control). The process begins with the OMS/Operator sending a `buildNode()` message to the Builder. The Builder then sends a `create()` message to the Managed Entity Factory, which in turn interacts with the Management Model Maintainer. A note specifies: "Create all managed entities in management information fragment for node entity." Next, the OMS/Operator sends a `modifyNode()` message to the Builder, which sends an `updates()` message to the Management Model Maintainer. A note states: "Assigns new values to relevant management information fragment managed entities." This is followed by the OMS/Operator sending an `assignUserLabelsToNE()` message to the Builder, which again sends an `updates()` message to the Management Model Maintainer. A note indicates: "Raises exception if there are remaining subnetwork connections or reservations." Finally, the OMS/Operator sends a `deleteNode()` message to the Builder, which sends a `scopeFilter()` message to the Management Model Maintainer. The Maintainer then sends a `delete()` message to the Managed Entity Factory. A final note states: "Delete all managed entities in management information fragment for node entity." + +UML sequence diagram showing interactions between OMS/Operator, Builder, Managed Entity Factory, and Management Model Maintainer for build, modify, and delete operations. + +**Figure 6-85 – Build, modify and delete sequence diagram18** + +18 This example concerns the "node" entity (for BPON technology this would be an OLT, ONT, ONU or NT), but the behaviour described applies to all the other entities in this interface including the following: Port, ProtectionGrouping, TCONT, PlugInUnit, MACBridge or VPNetworkCTP. + +##### Operations + +| Operation name | Operation purpose | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 1) buildNode | This operation builds an NE in the supplier management system. | +| 2) assignUserLabelsToNE | This operation assigns operator administrative designations to NEs. | +| 3) modifyNode | The operation initiates reconfiguration and update of specific parameters associated with an NE. | +| 4) deleteNode | This operation deletes the NE from the supplier management system and cancels a previous pre-provisioning request. | +| 5) modifyPort | The operation modifies parameters of the designated port identified by physicalPathTPId. | +| 6) buildPlugInUnit | This operation builds a plug-in unit in the supplier management system as part of the pre-provisioning activities. | +| 7) modifyPlugInUnit | This operation modifies attributes of the plug-in unit in the supplier management system. | +| 8) deletePlugInUnit | This operation deletes a plug-in unit from the supplier management system. | +| 9) buildProtectionGrouping | This operation builds a protectionGrouping in the supplier management system. | +| 10) modifyProtectionParameters | This operation modifies the protection schema for the identified protection grouping. | +| 11) modifyProtectionUnitList | This operation either adds to or removes from the list of protected and protecting ports for the identified protection grouping. | +| 12) deleteProtectionGrouping | This operation deletes a protection grouping of ports from the supplier management system. | +| 13) buildBridge | This operation builds a MAC bridge in the supplier management system. | +| 14) modifyBridgeProfile | This operation modifies the characteristics of the bridging function by changing the MAC bridge service profile associated with the bridge. | +| 15) modifyBridgePortList | This operation either adds to or removes from the list of UNI ports belonging to the bridge grouping. | +| 16) deleteBridge | This operation deletes a bridge provisioning from the supplier management system. | +| 17) buildVPNNetworkCTP | This operation builds a VP network CTP in the supplier management system. | +| 18) deleteVPNNetworkCTP | This operation deletes a VP network CTP provisioning from the supplier management system. | +| 19) createdNodesGet | This operation retrieves the list of network elements that have been constructed through invocation of this interface. | +| 20) buildTCONT | This operation builds a TCONT in the supplier management system. | +| 21) modifyTCONTParameters | This operation modifies the parameters associated with an existing TCONT in the supplier management system. | +| 22) deleteTCONT | This operation deletes a TCONT provisioning from the supplier management system. | + +**Figure 6-86 – Builder operations** + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) buildNode | NEKindType,
string (supplier name),
string (location),
VersionType (hardware version),
SerialNumType,
string (registration Id)
NameSeqType (alarm severity profile),
NameSeqType (threshold data profile),
SlotAssignmentSeqType,
ManagedEntityIdType (port),
string (equipment code)
UserLabelType,
ExternalTimeType,
SystemTimingType,
RegistrationIdType,
boolean (status reporting indicator)
AdministrationDomainType | ManagedEntity
IdType | UnrecognisedVersion,
InvalidSerialNumSyntax,
DuplicateSerialNumber,
UnknownProfiles,
UnknownManagedEntity,
DuplicateUserLabel,
AccessDenied,
InvalidExternalTime,
UnknownSystemTimingSource,
ProfileSuspended | +| 2) assignUserLabelsToNE | SerialNumType,
string (registration Id),
UserLabelType,
RegistrationIdType
AdministrationDomainType | void | InvalidSerialNumSyntax,
DuplicateSerialNumber,
DuplicateUserLabel,
AccessDenied | +| 3) modifyNode | ManagedEntityIdType,
SlotAssignmentSeqType,
NameSeqType (alarm severity profile),
NameSeqType (threshold data profile),
string (registration Id),
UserLabelType,
ExternalTimeType,
RegistrationIdType,
boolean (status reporting indicator)
AdministrationDomainType | void | UnknownManagedEntity,
UnknownNE,
InvalidSlotAssignmentList,
UnknownProfiles,
DuplicateUserLabel,
AccessDenied,
InvalidExternalTime,
ProfileSuspended | +| 4) deleteNode | ManagedEntityIdType | void | UnknownNE,
RemainingContainedManaged
Entities,
AccessDenied,
RemainingReservations,
RemainingSubnetworkConnections | +| 5) modifyPort | ManagedEntityIdType,
NameSeqType (alarm severity profile),
NameSeqType (threshold data profile),
NameSeqType (port profiles),
string,
AdministrativeStateType,
OpticalWaveLengthArraySeqType,
LoopbackLocationIdSeqType,
unsigned long (interface speed),
unsigned long (ARC timer) | void | UnknownManagedEntity,
UnknownProfiles,
AccessDenied,
InterfaceSpeedNotChangeable,
ProfileSuspended | +| 6) buildPlugInUnit | ManagedEntityIdType,
NameSeqType (alarm severity profile),
UserLabelType,
string (equipment code),
AdministrativeStateType,
ManagedEntityIdType (slot) | ManagedEntity
IdType | UnknownNE,
DuplicateUserLabel,
AccessDenied,
UnknownManagedEntity,
InvalidEquipmentCode,
SlotAlreadyAssigned,
UnknownSlot,
InvalidSlotAssignmentList,
UnknownProfiles,
ProfileSuspended | + +| Operation name | Input parameters | Return value | Exceptions | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7) modifyPlugInUnit | ManagedEntityType,
NameType (alarm severity profile),
string (equipment code),
ManagedEntityType,
UserLabelType,
AdministrativeStateType | ManagedEntity
IdType | UnknownManagedEntity,
UnknownProfiles,
AccessDenied,
InvalidEquipmentCode,
SlotAlreadyAssigned,
UnknownSlot,
InvalidSlotAssignmentList,
InvalidUserLabelSyntax,
ProfileSuspended | +| 8) deletePlugInUnit | ManagedEntityType | void | UnknownManagedEntity,
RemainingSubnetworkConnections,
AccessDenied,
RemainingReservations | +| 9) buildProtection
Grouping | ProtectionParameterType,
ProtectionUnitSeqType | ManagedEntity
IdType | InvalidProtectionScheme,
AccessDenied | +| 10) modifyProtection
Parameters | ManagedEntityType,
ProtectionParameterType | void | UnknownManagedEntity,
InvalidProtectionScheme,
AccessDenied | +| 11) modifyProtection
UnitList | ManagedEntityType,
ProtectionUnitSeqType,
boolean (add delete indication) | void | UnknownManagedEntity,
InvalidProtectionScheme,
AccessDenied | +| 12) deleteProtection
Grouping | ManagedEntityType | void | UnknownManagedEntity,
AccessDenied | +| 13) buildBridge | NameType (MAC bridge profile),
ManagedEntityType (port),
ManagedEntityIdSeqType (UNI ports) | ManagedEntity
IdType | UnknownProfiles,
AccessDenied,
UnknownManagedEntity,
ProfileSuspended | +| 14) modifyBridgeProfile | ManagedEntityType,
NameType (MAC bridge profile) | void | UnknownManagedEntity,
UnknownProfiles,
AccessDenied,
ProfileSuspended | +| 15) modifyBridgePortList | ManagedEntityType,
ManagedEntityIdSeqType (delta UNI
ports),
boolean (add delete indication) | void | UnknownManagedEntity,
RemainingSubnetworkConnections,
AccessDenied | +| 16) deleteBridge | ManagedEntityType | void | UnknownManagedEntity,
AccessDenied,
RemainingSubnetworkConnections | +| 17) buildVPNNetworkCTP | ManagedEntityType (port),
short (VPI),
NameType(traffic descriptor profile)
ATMOverbookingFactorType,
UserLabelType,
SegmentEndpointIdType | ManagedEntity
IdType | UnknownProfiles,
AccessDenied,
UnknownManagedEntity,
ParameterViolation,
ProfileSuspended | +| 18) deleteVPNNetwork
CTP | ManagedEntityType | void | UnknownManagedEntity,
AccessDenied | +| 19) createdNodesGet | | ManagedEntity
IdSeqType | AccessDenied | +| 20) buildTCONT | ManagedEntityType (ONT or ONU),
TCONTType,
BWType (maxBW),
BWType (fixedBW),
BWType (guaranteedBW),
UserLabelType | ManagedEntity
IdType | UnknownNE,
AccessDenied,
InsufficientPONBW,
UnsupportedTCONTType,
DuplicateUserLabel | +| 21) modifyTCONT
Parameters | ManagedEntityType (TCONT),
BWType (maxBW),
BWType (fixedBW),
BWType (guaranteedBW),
UserLabelType | void | UnknownManagedEntity,
AccessDenied,
InsufficientPONBW,
DuplicateUserLabel | +| 22) deleteTCONT | ManagedEntityType (TCONT) | void | UnknownManagedEntity,
AccessDenied,
RemainingSubnetworkConnections | + +**Figure 6-87 – Builder signatures** + +##### Exceptions + +| Exception raised | Description | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| DuplicateSerialNumber | There exists other equipment of the same type with this serial number. | +| DuplicateUserLabel | The user label provided in the request has been used to label another archive, i.e., one that is defined by a different set of creation request parameters. | +| InterfaceSpeedNotChangeable | The physical port cannot support the new interface speed or the speed is not configurable. | +| InvalidEquipmentCode | The equipment code does not conform to syntax. | +| InvalidExternalTime | External time specified is not valid. | +| InvalidProtectionScheme | The network resource does not support the protection parameters specified in context with the port listing or if the protection units are ports of dissimilar physical path characteristic. | +| InvalidSerialNumSyntax | Syntax of the serial number provided does not match definition rules. | +| InvalidSlotAssignmentList | Expected slot provisioning rules are violated by slot assignment provided. | +| InvalidUserLabelSyntax | The specified UserLabel does not follow established rules for UserLabel. | +| ParameterViolation | This exception is raised when the endpoint parameters do not match the protocol characteristics of the port, or when the values are out of range or invalid duplicates. | +| ProfileSuspended | The named profile(s) in the invocation have been suspended for use within the supplier management system by the OMS or operator. | +| RemainingContainedManagedEntities | Contained circuit packs or equipment holders have not been deleted yet. | +| RemainingReservations | The node cannot be deleted as resource reservations still exist. | +| RemainingSubnetworkConnections | The node or plug-in unit cannot be deleted as there are remaining subnetwork connections. | +| SlotAlreadyAssigned | The requested slot is already provisioned. | +| UnknownManagedEntity | The specified managed entity is unknown to the supplier management system. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownProfiles | This exception is raised if the profile name provided is unknown to the supplier management system and cannot be retrieved from the profile object repository. | +| UnknownSlot | The requested slot is unknown in the NE. | +| UnknownSystemTimingSource | External time source unknown to the supplier management system. | +| UnrecognisedVersion | Equipment version provided does not match known values. | + +**Figure 6-88 – Builder exceptions** + +#### 6.3.6.2 Profile object management + +![UML class diagram for Profile object management showing entities like Profile Object Repository, OMS Operator, Management Model Maintainer, Profile Usage Mgr, Profile Object Consumer, Factory, and various profile classes like ATM Network Access Profile F, Tires hold Data F, AAL2 PVC Profile, CES Service Profile, Traffic Descriptor Profile F, etc.](207817524fe964425718e1723d5b7d9e_img.jpg) + +``` + +classDiagram + class ProfileObjectRepository { + +retrieve() + +createProfileObject() + } + class OMSOperator { + +obtainsParameterValues() + +managesProfileUsage() + } + class ManagementModelMaintainer { + +consultsAndUpdatesUsageCapability() + } + class ProfileUsageMgr { + +KnownProfileList + +isUse() + +suspendUse() + +deleteProfile() + +lookup() + +setName() + +resetUse() + +matchKnownProfile() + } + class ProfileObjectConsumer { + +subscribeToChannel() + +consumeProfileObjectCreation() + } + class InternalProcess { + } + class Factory { + +create() + +delete() + } + class ExternalEventChannel { + +push() + } + class ATMNetworkAccessProfileF { + +Name + +ManagedEntityId + +LocalMaxNmVPCSupportable + +LocalMaxNmVCCSupportable + +LocalMaxNmAllocatedVPIBts + +LocalMaxNmAllocatedVCIBts + +TotalEgressBandwidth + +TotalIngressBandwidth + +UPC/NPCId + +Suspended + } + class TiresHoldDataF { + +Name + +ManagedEntityId + +PMTType + +PerformParamTiresHoldValueList + } + class AAL2PVCProfile { + +Name + +ManagedEntityId + +AppId + +MaxNmNmCba + +MinNmNmCbaIdVal + +MaxNmNmCbaIdVal + +MaxPCSPDULEn + +TimeRCULEn + } + class CESServiceProfile { + +Name + +CESBInterDCDVTolerance + +ChannelAssociatedSignalling + +CableGaugeLength + } + class TrafficDescriptorProfileF { + +Name + +ManagedEntityId + +ServiceCategory + +ConformanceDefinition + +PeakCellRate - Ingress and Egress + +CellDelayVariationTolerancePCR - Ingress and Egress + +CellDelayVariationToleranceSCR - Ingress and Egress + +SustainableCellRate - Ingress and Egress + +MaximumBurstSize - Ingress and Egress + +MFS - Ingress and Egress + +MinimumCellRate - Ingress and Egress + +RateIncreaseFactor - Ingress and Egress + +FixedRoundTripTime + +InitialCellRate - Ingress and Egress + +TransitBufferExposure - Ingress and Egress + +RateDecreaseFactor - Ingress and Egress + +Nrm - Ingress and Egress + +Ttm - Ingress and Egress + +CDF - Ingress and Egress + +ADTF - Ingress and Egress + } + class VoiceServiceProfileAAL1 { + +Name + +ManagedEntityId + +AnnouncementType + } + class MACBridgeServiceProfile { + +Name + +ManagedEntityId + +SpanningTreeId + +LearnIngId + +MaxAge + +HelloTime + +ForwardDelay + } + class EthernetProfile { + +Name + +ManagedEntityId + +DuplexId + +AutoDetectionId + +DataRate + +MaxFrameSize + +DTEorDCEId + +BridgePortId + } + class VoiceServiceProfileAAL2 { + +Name + +ManagedEntityId + +AnnouncementType + +JitterTarget + +JitterBurstMax + +TimingReference + } + class SSCSPParameterProfile1 { + +Name + +ManagedEntityId + +SegmentLength + +RASTimer + +MaxSSARSDUlen + +SSTEDId + +SSADTId + } + class SSCSPParameterProfile2 { + +Name + +ManagedEntityId + +ServiceCategory + +EncStrType + +EncProfileIndex + +AudioSequenced + +PCMEncType + +CMDataId + +CMMultipleNrm + +FIMDataId + +FIMMaxFrameLen + +CASId + +DTMFId + +MFRFId + +RateControlId + +SyncCableLength + } + class LESServiceProfile { + +Name + +ManagedEntityId + +ELCId + +POTS signalling + +BRI signalling + +MaxNmCIDs + +MaxPacketLength + +ChannelSSCSPParameterPtrList + } + class UNINbF { + +Name + +LocalMaxNmVPCSupportable + +LocalMaxNmVCCSupportable + +LocalMaxNmAllocatedVPIBts + +LocalMaxNmAllocatedVCIBts + +LoopbackLocationCode + } + class AAL1ProfileF { + +Name + +ManagedEntityId + +SubType + +CBRRate + +ClockRecoveryType + +ForwardErrorCorrectionType + +StructuredDataTransfer + +PartiallyFilledCells + +CellLossIntegrationPeriod + } + class AAL2P1P1P { + +Name + +ManagedEntityId + +DetailSSCSPParameterProfile1Ptr + +DetailSSCSPParameterProfile2Ptr + } + class VGCESServiceProfile { + +Name + +ManagedEntityId + +CESBInterDCDVTolerance + +ChannelAssociatedSignalling + } + class AALSPProfileF { + +Name + +ManagedEntityId + +MaxPCSPDULen + +SSCSType + } + + ProfileObjectRepository --> ProfileUsageMgr : retrieve() + ProfileObjectRepository --> ProfileUsageMgr : createProfileObject() + OMSOperator --> ProfileUsageMgr : obtainsParameterValues() + OMSOperator --> ProfileUsageMgr : managesProfileUsage() + ManagementModelMaintainer --> ProfileUsageMgr : consultsAndUpdatesUsageCapability() + ProfileUsageMgr --> ProfileObjectConsumer : matches + ProfileUsageMgr --> InternalProcess : matches + InternalProcess --> Factory : commissions + ProfileObjectConsumer --> Factory : commissions + ProfileObjectConsumer --> ExternalEventChannel : consumesEventsFrom + Factory --> ProfileUsageMgr : createsAndDeletesProfilesWithinSupplierManagementSystem + Factory --> ProfileUsageMgr : delete() + Factory --> ProfileUsageMgr : create() + +``` + +UML class diagram for Profile object management showing entities like Profile Object Repository, OMS Operator, Management Model Maintainer, Profile Usage Mgr, Profile Object Consumer, Factory, and various profile classes like ATM Network Access Profile F, Tires hold Data F, AAL2 PVC Profile, CES Service Profile, Traffic Descriptor Profile F, etc. + +Figure 6-89 – Profile object management class diagram + +![UML sequence diagram for Profile object management. Lifelines include Profile Object Consumer, Profile Object Repository, Operator, External Event Channel, Management Model Maintainer, Managed Entity: Factory, Profile Usage Mgr, Internal Process, and OMS Operator. The diagram shows the flow of creating, matching, updating, and managing profile objects with various annotations like 'Response is negative' and 'Response is positive'.](9dc88fb2c48bc64047fc3e79814f1d47_img.jpg) + +``` + +sequenceDiagram + participant POConsumer as :Profile Object Consumer + participant POR as :Profile Object Repository + participant Operator as :Operator + participant EEC as :External Event Channel + participant MMT as :Management Model Maintainer + participant MEF as Managed Entity: +Factory + participant PUM as :Profile Usage Mgr + participant IP as Internal Process + participant OMSOperator as :OMS Operator + + POConsumer->>POR: subscribeToChannel() + activate POR + Operator->>POR: createProfileObject(ProfileA) + activate POR + POR->>EEC: post() + deactivate POR + activate EEC + EEC->>POConsumer: post() + deactivate EEC + POConsumer->>MMT: matchKnownProfile(ProfileA) + activate MMT + MMT-->>PUM: If not +known. + deactivate MMT + POConsumer->>MEF: create(ProfileA) + activate MEF + Note right of PUM: Response is +negative. + PUM->>OMSOperator: In Use(ProfileA) + activate OMSOperator + OMSOperator->>PUM: matchKnownProfile(ProfileA) + deactivate OMSOperator + PUM->>MMT: getProfile(ProfileA) + activate MMT + MMT->>MEF: updateProfilePtr(ProfileA) + Note left of MMT: The profile is being "used" to +configure another managed entity. + Note right of MMT: Response is +positive. + MEF-->>PUM: + deactivate MEF + PUM->>OMSOperator: In Use(ProfileA) + activate OMSOperator + OMSOperator->>PUM: suspendUse(ProfileA) + deactivate OMSOperator + PUM->>MMT: matchKnownProfile(ProfileA) + activate MMT + Note left of MMT: Raises +exception. + MMT->>MEF: getProfile(ProfileA) + activate MEF + MEF-->>PUM: + deactivate MMT + deactivate MEF + +``` + +UML sequence diagram for Profile object management. Lifelines include Profile Object Consumer, Profile Object Repository, Operator, External Event Channel, Management Model Maintainer, Managed Entity: Factory, Profile Usage Mgr, Internal Process, and OMS Operator. The diagram shows the flow of creating, matching, updating, and managing profile objects with various annotations like 'Response is negative' and 'Response is positive'. + +Figure 6-90 – Profile object management sequence diagram + +![UML sequence diagram for Profile object management. Lifelines: InternalProcess, Profile Usage Mgr, Profile Object Repository, Managed Entity Factory, Management Model Maintainer, OMS Operator, Profile Object Consumer, External Event Channel. The diagram shows interactions for creating, updating, deleting, and managing profiles, with notes indicating error handling like 'Profile is in use by another managed entity' and 'Raises exception'.](95be50ec094942200786128aa936cfae_img.jpg) + +``` + +sequenceDiagram + participant IP as :InternalProcess + participant PUM as :Profile Usage Mgr + participant POR as :Profile Object Repository + participant MEF as :Managed Entity Factory + participant MMM as :Management Model Maintainer + participant OMS as :OMS Operator + participant POC as :Profile Object Consumer + participant EEC as :External Event Channel + + IP->>PUM: matchKnownProfile (Profile B) + PUM->>POR: lookUp() + Note left of PUM: Response is no. + PUM->>POR: retrieve() + Note right of POR: Profile is in use by another managed entity. + PUM->>MEF: create (Profile B) + PUM->>MMM: getProfile (Profile B) + PUM->>MMM: updateProfilePrf (Profile B) + PUM->>POR: resumeUse (Profile A) + POC->>POR: matchKnownProfile (Profile C) + POC->>MEF: create (Profile C) + POC->>POC: consumeProfileObjCreation (Profile C) + POC->>POR: deleteProfile (Profile C) + POC->>MEF: delete (Profile C) + POC->>MMM: reName (Profile C) + Note left of POR: Raises exception. + +``` + +UML sequence diagram for Profile object management. Lifelines: InternalProcess, Profile Usage Mgr, Profile Object Repository, Managed Entity Factory, Management Model Maintainer, OMS Operator, Profile Object Consumer, External Event Channel. The diagram shows interactions for creating, updating, deleting, and managing profiles, with notes indicating error handling like 'Profile is in use by another managed entity' and 'Raises exception'. + +**Figure 6-91 – Profile object management – New supplier management system sequence diagram** + +##### Operations + +| Operation name | Operation purpose | +|---------------------------|-----------------------------------------------------------------------------------------------| +| 1) reName | This operation provides the capability to rename a profile. | +| 2) inUse | This operation returns a boolean value to tell if the profile is in use. | +| 3) suspendUse | This operation suspends the use of a profile. | +| 4) resumeUse | This operation resumes the use of a named profile. | +| 5) deleteProfile | This operation deleteProfile provides the capability to remove a profile which is not in use. | +| 6) retrieve 19 | This operation provides the capability to retrieve a profile attribute values. | + +**Figure 6-92 – Profile usage manager and profile retriever operations** + +19 The operation "retrieve()" is the only one associated with the interface object profile retriever. + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|---------------------------|-------------------------------------------------------------|--------------------------------|-----------------------------------------------------------| +| 1) reName | NameType (old profile name),
NameType (new profile name) | void | UnknownProfiles,
AccessDenied,
DuplicateProfileName | +| 2) inUse | NameType (profile name) | boolean (indication of in use) | UnknownProfiles,
AccessDenied | +| 3) suspendUse | NameType (profile name) | void | UnknownProfiles,
AccessDenied | +| 4) resumeUse | NameType (profile name) | void | UnknownProfiles,
AccessDenied | +| 5) deleteProfile | NameType (profile name) | void | UnknownProfiles,
AccessDenied,
ProfileInUse | +| 6) retrieve 20 | NameType (profile name) | ProfileInfoType | UnknownProfiles | + +**Figure 6-93 – Profile usage manager and profile retriever signatures** + +##### Exceptions + +| Exception raised | Description | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| DuplicateProfileName | This exception is raised when the new profile name duplicates an existing profile name. | +| ProfileInUse | This exception is raised when the profile may not be deleted because it is still being used to characterize managed entities within the management jurisdiction of the supplier management system. | +| UnknownProfiles | This exception is raised if the profile name provided is unknown to the supplier management system and cannot be retrieved from the profile object repository. | + +**Figure 6-94 – Profile usage manager and profile retriever exceptions** + +--- + +20 The operation "retrieve()" is the only one associated with the interface object profile retriever. It is instantiated by the profile object repository. + +#### 6.3.6.3 Provision installed BPON resources + +![UML Class Diagram for Provision installed BPON resources. The diagram shows the relationships between various components including EventScreener, EventQueue, NotificationAdmin, EventForwarder, EventSupplier, Discoverer, Synchronizer, NERegister, Builder, ManagementModelMaintainer, Factory, InventoryData, ExternalEventChannel, Small_FSANNE, NEFSAN, Large_FSANNE, equipmentHolderF, Port, OLT, ONT, ONU, PlugInUnitF, and ProfileObjectRepository. It also includes actors like BPON NE, OMS Operator, and External Event Channel, and several notes about event analysis and profile retrieval.](b99ddca16383b6f00fc70050d695a235_img.jpg) + +``` + +classDiagram + class EventScreener { + +getConfigurationData() + +getStatusData() + +getStateData() + } + class EventQueue + class NotificationAdmin + class EventForwarder { + +processAnnouncement() + } + class EventSupplier + class Discoverer { + +getConfigurationData() + +getStatusData() + +getStateData() + } + class Synchronizer { + +NECommunicationsList + +getCompare() + +formatDataRecord() + +notify() + } + class NERegister + class Builder { + +CreatedNodesList + +ManagedEntityFragments + } + class ManagementModelMaintainer + class Factory { + +create() + +delete() + } + class InventoryData + class ExternalEventChannel + class Small_FSANNE + class NEFSAN + class Large_FSANNE + class equipmentHolderF + class Port + class OLT + class ONT + class ONU + class PlugInUnitF + class ProfileObjectRepository + + BPON_NE[BPON NE] --> EventScreener : sends events + BPON_NE --> Discoverer : queries + BPON_NE --> Synchronizer : triggers + BPON_NE --> NERegister : provides NE database + OMS_Operator[OMS Operator] --> Builder : registers or reconfigures + OMS_Operator --> Builder : provisions + OMS_Operator --> ProfileObjectRepository : consults and discovers (event) + ProfileObjectRepository --> Builder : retrieves Profile values + Note for EventScreener: Details found in "Process Incoming NE Events" Analysis. + Note for EventForwarder: Details found in "Publish BPON Event Analysis". + EventScreener --> EventQueue : queues to + EventScreener --> Synchronizer : notifies + Synchronizer --> EventQueue : extracts from + Synchronizer --> EventForwarder : announces discovery events + EventForwarder --> EventSupplier : pushes event + EventSupplier --> ExternalEventChannel : publishes event + Synchronizer --> Factory : commissions + Factory --> InventoryData : creates + InventoryData --> ExternalEventChannel : contains hardware and software inventory + ExternalEventChannel --> NEFSAN + NEFSAN --> Large_FSANNE + Large_FSANNE --> equipmentHolderF + equipmentHolderF --> Port + Port --> OLT + OLT --> ONT + ONT --> ONU + ONU --> equipmentHolderF + equipmentHolderF --> PlugInUnitF + PlugInUnitF --> equipmentHolderF + Note for PlugInUnitF: Only if Profile is unknown. + +``` + +UML Class Diagram for Provision installed BPON resources. The diagram shows the relationships between various components including EventScreener, EventQueue, NotificationAdmin, EventForwarder, EventSupplier, Discoverer, Synchronizer, NERegister, Builder, ManagementModelMaintainer, Factory, InventoryData, ExternalEventChannel, Small\_FSANNE, NEFSAN, Large\_FSANNE, equipmentHolderF, Port, OLT, ONT, ONU, PlugInUnitF, and ProfileObjectRepository. It also includes actors like BPON NE, OMS Operator, and External Event Channel, and several notes about event analysis and profile retrieval. + +Figure 6-95 – Provision installed BPON resources class diagram + +![UML sequence diagram for provisioning installed BPON resources with pre-provisioning. The diagram shows interactions between :OMSOperator, :Builder, :BPON NE, :Event Screener, :Event Queue, :Synchroniser, :Managed Entity Factory, :Discoverer, :NERegistrar, and :Port. Key actions include building nodes, ports, and protection groups, reading events, and associating NEs. Annotations specify that objects are created as required based on management information fragments and that the node is installed and registered or raised.](33cbd34b2ff74e39d12fae4db73f5b41_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant Builder as :Builder + participant BPON_NE as :BPON NE + participant Event_Screener as :Event Screener + participant Event_Queue as :Event Queue + participant Synchroniser as :Synchroniser + participant Managed_Entity_Factory as :Managed Entity Factory + participant Discoverer as :Discoverer + participant NE_Registrar as :NERegistrar + participant Port as :Port + + OMSOperator->>Builder: buildNode() + Builder-->>Managed_Entity_Factory: create() + Note right of Managed_Entity_Factory: As required based on management information fragment. + OMSOperator->>Builder: buildPort() + Builder-->>Managed_Entity_Factory: create() + Note right of Managed_Entity_Factory: As required based on management information fragment. + OMSOperator->>Builder: modifyPort() + Note left of Builder: As desired and as many as desired. + Builder->>Port: setAttribute() + OMSOperator->>Builder: buildProtectionGroup() + Builder-->>Managed_Entity_Factory: create() + OMSOperator->>Builder: readEvent() + Note left of Builder: The node is installed and registered or raised. + Builder->>Event_Screener: readEvent() + Event_Screener->>Event_Queue: notify() + OMSOperator->>Builder: associateNE() + Builder->>NE_Registrar: set() + Note right of NE_Registrar: Set all configuration values with pre-provisioned settings. + +``` + +UML sequence diagram for provisioning installed BPON resources with pre-provisioning. The diagram shows interactions between :OMSOperator, :Builder, :BPON NE, :Event Screener, :Event Queue, :Synchroniser, :Managed Entity Factory, :Discoverer, :NERegistrar, and :Port. Key actions include building nodes, ports, and protection groups, reading events, and associating NEs. Annotations specify that objects are created as required based on management information fragments and that the node is installed and registered or raised. + +Figure 6-96 – Provision installed BPON resources sequence diagram with pre-provisioning + +![Sequence diagram for provisioning installed BPON resources. The diagram shows interactions between OMS/Operator, Builder, Management Model Maintainer, Managed Entity Factory, External Event Channel, and BPON NE. The process starts with an external event being consumed by the OMS/Operator, which then triggers a series of modify and build actions on the Builder. The Builder then updates the Management Model Maintainer, which in turn sets values on the Managed Entity Factory. Finally, the Managed Entity Factory creates and sets values on the BPON NE. A note indicates that some build functions may not be required depending on the autodiscovered network resource.](49d7bfbc65a92a7e1bd61777326a212d_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant Builder as : Builder + participant MM as : Management Model Maintainer + participant ME as Managed Entity : Factory + actor ExtEvent as : External Event Channel + participant BPON as : BPON NE + + ExtEvent->>OMS: consumes autodiscovery event() + activate OMS + OMS->>Builder: modifyNode() + activate Builder + Builder-->>MM: update + deactivate Builder + Builder->>ME: set() + deactivate Builder + OMS->>Builder: modifyPlugInUnit() + activate Builder + Builder-->>MM: update + deactivate Builder + Builder->>ME: set() + deactivate Builder + OMS->>Builder: modifyPort() + activate Builder + Builder-->>MM: update + deactivate Builder + Builder->>ME: set() + deactivate Builder + OMS->>Builder: buildProtectionGrouping() + activate Builder + Builder->>ME: create() + deactivate Builder + ME->>BPON: set() + deactivate ME + OMS->>Builder: buildBridge() + activate Builder + Builder->>ME: create() + deactivate Builder + ME->>BPON: set() + deactivate ME + OMS->>Builder: buildTCONT() + activate Builder + Builder->>ME: create() + deactivate Builder + ME->>BPON: set() + deactivate ME + deactivate OMS + +``` + +According to Management Information fragment rules. Depending on the autodiscovered network resource, some of the build functions are not required. + +Sequence diagram for provisioning installed BPON resources. The diagram shows interactions between OMS/Operator, Builder, Management Model Maintainer, Managed Entity Factory, External Event Channel, and BPON NE. The process starts with an external event being consumed by the OMS/Operator, which then triggers a series of modify and build actions on the Builder. The Builder then updates the Management Model Maintainer, which in turn sets values on the Managed Entity Factory. Finally, the Managed Entity Factory creates and sets values on the BPON NE. A note indicates that some build functions may not be required depending on the autodiscovered network resource. + +Figure 6-97 – Provision installed BPON resources sequence diagram – No pre-provisioning + +#### 6.3.6.4 Provision service + +![UML Class Diagram for Provision Service](1c20b988e3792ded6d601aca944792a9_img.jpg) + +``` + +classDiagram + class ServiceProvider { + +provisionConnection() + +provisionReservation() + +deleteConnection() + +modifyConnection() + +suspendService() + +resumeService() + } + class BPONE + class OMSOperator + class Factory { + +create() + +delete() + } + class ProfileUsageMgr { + } + class ResourceAllocator { + +ServiceInstanceReservationIdListing + +ReservationIdReservedResourcesListing + +CACAlgorithms + +reserveForService() + +cancelReservation() + +getReservationId() + +reportReservedResources() + +getReservations() + +cancelAllRemainingReservations() + +getReservation() + +getAvailableSocBandwidth() + +assignForService() + +makeUnassigned() + } + class ATMPortResource + class EthernetPortResource + class TDMPortResource + class ManagementModelMaintainer { + } + class DetailAboutProfileObjectManagementAnalysis + class AAL2PvCPProfile + class AAL5ProfileF + class AAL2ProfileF + class DS1PProfile + class E3PProfile + class UNItoF + class AAL1PProfileF + class DS3PProfile + class E1PProfile + class SSCSPParameterProfile2 + class BridgedLANServiceProfile + class TrafficDescriptorProfileF + class IDLCCallProcessingProfile + class CESServiceProfile + class VoiceServiceProfileAAL1 + class BridgedLANServiceProfile + class VoiceServiceProfileAAL2 + class MACBridgeServiceProfile + class EthernetProfile + class ATMNetworkAccessProfileF + class LESServiceProfile + class VoiceServiceProfileAAL2 + + ServiceProvider --> BPONE : updates + ServiceProvider --> OMSOperator : provisions service + ServiceProvider --> ProfileUsageMgr : employs + ServiceProvider --> Factory : commissions + ProfileUsageMgr --> ResourceAllocator : employs + ProfileUsageMgr --> ManagementModelMaintainer : verifies capacity + ResourceAllocator --> ATMPortResource : adjusts + ResourceAllocator --> EthernetPortResource : adjusts + ResourceAllocator --> TDMPortResource : adjusts + ManagementModelMaintainer --> ResourceAllocator : consults + DetailAboutProfileObjectManagementAnalysis --> AAL2PvCPProfile + DetailAboutProfileObjectManagementAnalysis --> AAL5ProfileF + DetailAboutProfileObjectManagementAnalysis --> AAL2ProfileF + DetailAboutProfileObjectManagementAnalysis --> DS1PProfile + DetailAboutProfileObjectManagementAnalysis --> E3PProfile + DetailAboutProfileObjectManagementAnalysis --> UNItoF + DetailAboutProfileObjectManagementAnalysis --> AAL1PProfileF + DetailAboutProfileObjectManagementAnalysis --> DS3PProfile + DetailAboutProfileObjectManagementAnalysis --> E1PProfile + DetailAboutProfileObjectManagementAnalysis --> SSCSPParameterProfile2 + DetailAboutProfileObjectManagementAnalysis --> BridgedLANServiceProfile + DetailAboutProfileObjectManagementAnalysis --> TrafficDescriptorProfileF + DetailAboutProfileObjectManagementAnalysis --> IDLCCallProcessingProfile + DetailAboutProfileObjectManagementAnalysis --> CESServiceProfile + DetailAboutProfileObjectManagementAnalysis --> VoiceServiceProfileAAL1 + DetailAboutProfileObjectManagementAnalysis --> BridgedLANServiceProfile + DetailAboutProfileObjectManagementAnalysis --> VoiceServiceProfileAAL2 + DetailAboutProfileObjectManagementAnalysis --> MACBridgeServiceProfile + DetailAboutProfileObjectManagementAnalysis --> EthernetProfile + DetailAboutProfileObjectManagementAnalysis --> ATMNetworkAccessProfileF + DetailAboutProfileObjectManagementAnalysis --> LESServiceProfile + DetailAboutProfileObjectManagementAnalysis --> VoiceServiceProfileAAL2 + + Note for DetailAboutProfileObjectManagementAnalysis "Details about 'Profile Object Management' Analysis." + Note for ProfileUsageMgr "Profile Usage Manager" + Note for ResourceAllocator "Resource Allocator" + Note for ManagementModelMaintainer "Management Model Maintainer" + Note for AAL2PvCPProfile "AAL2PvCP Profile" + Note for AAL5ProfileF "AAL5 Profile F" + Note for AAL2ProfileF "AAL2 Profile F" + Note for DS1PProfile "DS1P Profile" + Note for E3PProfile "E3P Profile" + Note for UNItoF "UNI to F" + Note for AAL1PProfileF "AAL1P Profile F" + Note for DS3PProfile "DS3P Profile" + Note for E1PProfile "E1P Profile" + Note for SSCSPParameterProfile2 "SSCSP Parameter Profile 2" + Note for BridgedLANServiceProfile "BridgedLAN Service Profile" + Note for TrafficDescriptorProfileF "Traffic Descriptor Profile F" + Note for IDLCCallProcessingProfile "IDLCCall Processing Profile" + Note for CESServiceProfile "CES Service Profile" + Note for VoiceServiceProfileAAL1 "Voice Service Profile AAL1" + Note for BridgedLANServiceProfile "BridgedLAN Service Profile" + Note for VoiceServiceProfileAAL2 "Voice Service Profile AAL2" + Note for MACBridgeServiceProfile "MAC Bridge Service Profile" + Note for EthernetProfile "Ethernet Profile" + Note for ATMNetworkAccessProfileF "ATM Network Access Profile F" + Note for LESServiceProfile "LES Service Profile" + Note for VoiceServiceProfileAAL2 "Voice Service Profile AAL2" + + Note for ProfileUsageMgr "Only if P profile is unknown." + +``` + +The diagram illustrates the Provision service architecture. Key components include: + +- Service Provider**: Manages connections and reservations, interacting with BPONE and OMSOperator. +- Factory**: Creates and deletes resources, commissioned by the Service Provider. +- Profile Usage Manager**: Manages profiles, employing the Resource Allocator and verifying capacity with the Management Model Maintainer. +- Resource Allocator**: Allocates resources (ATM, Ethernet, TDM) and manages reservations. +- Management Model Maintainer**: Consults the Resource Allocator for capacity management. +- Profile Objects**: A collection of specific profiles such as AAL2PvCP, AAL5, AAL2, DS1P, E3P, UNItoF, AAL1P, DS3P, E1P, SSCSP, BridgedLAN, TrafficDescriptor, IDLCCallProcessing, CES, VoiceService (AAL1, AAL2), MAC Bridge, Ethernet, ATM Network Access, LES, and VoiceService (AAL2). + +UML Class Diagram for Provision Service + +Figure 6-98 – Provision service class diagram + +![Sequence diagram for Provision service and reservation connection. The diagram shows interactions between OMS Operator, Service Provisioner, Resource Allocator, and various network resource objects (OLT PON, ONT PON, OLT NNI, ONT UNI, Managed Entity). Key actions include bandwidth checks, connection and reservation requests, metric updates, and resource creation. Two callouts provide context: one for creating network components and another for adjusting gauges and counters.](3d46409f8d0190e611a910ff27f8ec07_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as OMS Operator + participant ServiceProvisioner as Service Provisioner + participant ResourceAllocator as Resource Allocator + participant OLT_PON as OLT PON : ATM Port Resource + participant ONT_PON as ONT PON : ATM Port Resource + participant OLT_NNI as OLT NNI : ATM Port Resource + participant ONT_UNI as ONT UNI : TDM Port Resource + participant ManagedEntity as Managed Entity : Factory + + OMSOperator->>ServiceProvisioner: getAvailableSysBandwidth() + activate ServiceProvisioner + ServiceProvisioner->>ResourceAllocator: provisionConnection() reserveForService() + activate ResourceAllocator + ResourceAllocator->>OLT_PON: update "reserved" and "available" metrics + activate OLT_PON + OLT_PON->>ONT_PON: update "reserved" and "available" metrics + activate ONT_PON + ONT_PON->>OLT_NNI: update "reserved" and "available" metrics + activate OLT_NNI + OLT_NNI->>ONT_UNI: update "reserved" and "available" metrics + activate ONT_UNI + ResourceAllocator-->>ManagedEntity: create() + activate ManagedEntity + Note over ManagedEntity: Creates all necessary NetworkCTPs, NetworkTTPs, CTPs, TTPs, and subnetwork and link connections, according to the designation of endpoints. + ManagedEntity-->>ResourceAllocator: + deactivate ManagedEntity + ResourceAllocator->>ServiceProvisioner: assignForService() + activate ServiceProvisioner + ServiceProvisioner->>OLT_PON: update "assigned" and "reserved" metrics + activate OLT_PON + OLT_PON->>ONT_PON: update "assigned" and "reserved" metrics + activate ONT_PON + ONT_PON->>OLT_NNI: update "assigned" and "reserved" metrics + activate OLT_NNI + OLT_NNI->>ONT_UNI: update "assigned" and "reserved" metrics + activate ONT_UNI + Note over ONT_UNI: Shows adjustments in gauges and counters. + ONT_UNI-->>ServiceProvisioner: + deactivate ONT_UNI + deactivate OLT_NNI + deactivate ONT_PON + deactivate OLT_PON + ServiceProvisioner->>ResourceAllocator: getAvailableSysBandwidth() + activate ResourceAllocator + ResourceAllocator->>ServiceProvisioner: provisionReservation() + activate ServiceProvisioner + ServiceProvisioner->>ResourceAllocator: getReservation() + activate ResourceAllocator + ResourceAllocator->>ManagedEntity: create() + activate ManagedEntity + ManagedEntity->>ServiceProvisioner: assignForService() + activate ServiceProvisioner + ServiceProvisioner->>OLT_PON: update "assigned" and "reserved" metrics + activate OLT_PON + OLT_PON->>ONT_PON: update "assigned" and "reserved" metrics + activate ONT_PON + ONT_PON->>OLT_NNI: update "assigned" and "reserved" metrics + activate OLT_NNI + OLT_NNI->>ONT_UNI: update "assigned" and "reserved" metrics + activate ONT_UNI + ONT_UNI-->>ServiceProvisioner: + deactivate ONT_UNI + deactivate OLT_NNI + deactivate ONT_PON + deactivate OLT_PON + ServiceProvisioner->>ResourceAllocator: getAvailableSysBandwidth() + activate ResourceAllocator + deactivate ResourceAllocator + deactivate ServiceProvisioner + +``` + +Sequence diagram for Provision service and reservation connection. The diagram shows interactions between OMS Operator, Service Provisioner, Resource Allocator, and various network resource objects (OLT PON, ONT PON, OLT NNI, ONT UNI, Managed Entity). Key actions include bandwidth checks, connection and reservation requests, metric updates, and resource creation. Two callouts provide context: one for creating network components and another for adjusting gauges and counters. + +Figure 6-99 – Provision service and reservation connection sequence diagram + +![Sequence diagram for suspend, resume, and delete connection operations. The diagram shows interactions between OMSOperator, ServiceProvisioner, ManagementModelMaintainer, ONT:BPON NE, ResourceAllocator, ManagedEntityFactory, and various resource objects (OLT PON, ONT PON, OLT NNI, ONT UNI). Key actions include suspendService(), resumeService(), deleteConnection(), and bandwidth management updates. Notes indicate 'No change', 'Change administrative state of UNI port', 'Provides bandwidth values', and 'All previously created managed entities for the service connection'.](92e26d86c5a582766cb9afdbd2c1aee7_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator + participant ServiceProvisioner + participant ManagementModelMaintainer + participant ONT as ONT:BPON NE + participant ResourceAllocator + participant ManagedEntityFactory + participant OLT_PON as OLT PON: ATMPortResource + participant ONT_PON as ONT PON: ATMPortResource + participant OLT_NNI as OLT NNI: ATMPortResource + participant ONT_UNI as ONT UNI: TDMPortResource + + OMSOperator->>ServiceProvisioner: suspendService() + activate ServiceProvisioner + ServiceProvisioner->>ManagementModelMaintainer: set() + activate ManagementModelMaintainer + ManagementModelMaintainer->>ONT: update + deactivate ManagementModelMaintainer + Note over ManagementModelMaintainer: Change administrative state of UNI port + ServiceProvisioner->>ResourceAllocator: getAvailableSysBandwidth() + activate ResourceAllocator + Note over ResourceAllocator: No change + ResourceAllocator->>ServiceProvisioner: + deactivate ResourceAllocator + OMSOperator->>ServiceProvisioner: resumeService() + activate ServiceProvisioner + ServiceProvisioner->>ManagementModelMaintainer: set() + activate ManagementModelMaintainer + ManagementModelMaintainer->>ONT: update + deactivate ManagementModelMaintainer + ServiceProvisioner->>ResourceAllocator: getAvailableSysBandwidth() + activate ResourceAllocator + Note over ResourceAllocator: Provides bandwidth values + ResourceAllocator->>ServiceProvisioner: + deactivate ResourceAllocator + OMSOperator->>ServiceProvisioner: deleteConnection() + activate ServiceProvisioner + ServiceProvisioner->>ManagementModelMaintainer: getReservationId() + activate ManagementModelMaintainer + ManagementModelMaintainer->>ResourceAllocator: getReservation() + activate ResourceAllocator + ResourceAllocator->>ManagedEntityFactory: delete() + deactivate ResourceAllocator + Note over ManagedEntityFactory: All previously created managed entities for the service connection + ServiceProvisioner->>ResourceAllocator: makeUnassigned() + activate ResourceAllocator + ResourceAllocator->>OLT_PON: update "available" and "assigned" metrics + activate OLT_PON + OLT_PON->>ONT_PON: update "available" and "assigned" metrics + activate ONT_PON + ONT_PON->>OLT_NNI: update "available" and "assigned" metrics + activate OLT_NNI + OLT_NNI->>ONT_UNI: update "available" and "assigned" metrics + deactivate OLT_NNI + deactivate ONT_PON + deactivate OLT_PON + ResourceAllocator->>ServiceProvisioner: + deactivate ResourceAllocator + ServiceProvisioner->>ResourceAllocator: getAvailableSysBandwidth() + activate ResourceAllocator + Note over ResourceAllocator: Shows adjustments + ResourceAllocator->>ServiceProvisioner: + deactivate ResourceAllocator + deactivate ServiceProvisioner + +``` + +Sequence diagram for suspend, resume, and delete connection operations. The diagram shows interactions between OMSOperator, ServiceProvisioner, ManagementModelMaintainer, ONT:BPON NE, ResourceAllocator, ManagedEntityFactory, and various resource objects (OLT PON, ONT PON, OLT NNI, ONT UNI). Key actions include suspendService(), resumeService(), deleteConnection(), and bandwidth management updates. Notes indicate 'No change', 'Change administrative state of UNI port', 'Provides bandwidth values', and 'All previously created managed entities for the service connection'. + +Figure 6-100 – Suspend, resume and delete connection sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| 1) provisionConnection | This operation provisions a connection between any two endpoints of a BPON fibre access system. | +| 2) provisionReservation | This operation provisions service between the NNI of an OLT and the UNI of an ONT or between two UNIs based on an outstanding reservation. | +| 3) deleteConnection | The operation tears down the existing service and connections. | +| 4) modifyConnection | This operation provides the capability to modify the existing service. | +| 5) suspendService | This operation disables the flow of user traffic through the service subnetwork connection. | +| 6) resumeService | This operation enables the flow of user traffic through the service subnetwork connection. | + +Figure 6-101 – Service provisioner operations + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) provisionConnection | EndpointType (endpoint A),
EndpointType (endpoint Z),
NameSeqType (network profiles),
ServiceInstanceType,
RegistrationIdType,
AdministrativeStateType | ManagedEntityIdType | UnknownNE,
UnknownProfiles,
UnknownPort,
InsufficientBW,
ConnectionCountExceeded,
CommFailure,
EquipmentFailure,
ParameterViolation,
AccessDenied,
InsufficientPONBW,
ProfileSuspended,
ConnectionAlreadyExists | +| 2) provisionReservation | ReservationIdType,
AdministrativeStateType | ManagedEntityIdType | UnknownReservationId,
AccessDenied | +| 3) deleteConnection | ManagedEntityIdType | void | UnknownConnection,
CommFailure,
EquipmentFailure,
AccessDenied | +| 4) modifyConnection | ManagedEntityIdType,
ManagedEntityIdType (port A),
NameSeqType (new network
profiles),
NameSeqType (new service
profiles) | ManagedEntityIdType | UnknownConnection,
UnknownProfiles,
InsufficientBW,
UnknownPort,
AccessDenied,
ProfileSuspended | +| 5) suspendService | ServiceInstanceType,
GeneralizedTimeType (start time),
GeneralizedTimeType (stop time) | void | UnknownServiceInstance,
AccessDenied,
InvalidStartTime,
InvalidStopTime | +| 6) resumeService | ServiceInstanceType | void | UnknownServiceInstance,
AccessDenied | + +**Figure 6-102 – Service provisioner signatures** + +##### Exceptions + +| Exception raised | Description | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| ConnectionAlreadyExists | There already exists a subnetwork connection with the same endpoints. | +| ConnectionCountExceeded | The maximum number of connections for the OLT or PON port has been exceeded with this request for service provisioning. | +| EquipmentFailure | The NE currently has a failure condition preventing the requested transaction from being completed. | +| InsufficientPONBW | The ONT or ONU cannot be ranged or the service connection cannot be provisioned due to insufficient bandwidth on the APONLink. | +| InsufficientBW | The CAC algorithm indicates that requested service requires too much bandwidth for the OLT. | +| InvalidStartTime | The new start time is inconsistent with the current trigger time matrix or the new stop time. | +| InvalidStopTime | The new stop time is inconsistent with the current trigger time matrix or the new start time. | +| ParameterViolation | This exception is raised when the endpoint parameters do not match the protocol characteristics of the port, or when the values are out of range or invalid duplicates. | +| ProfileSuspended | The named profile(s) in the invocation have been suspended for use within the supplier management system by the OMS or operator. | +| UnknownConnection | The subnetwork connection is not known by the supplier management system. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownPort | The identified port is unknown to the supplier management system. | +| UnknownProfiles | This exception is raised if the profile name provided is unknown to the supplier management system and cannot be retrieved from the profile object repository. | +| UnknownReservationId | The supplier management system does not recognize this reservation Id. | +| UnknownServiceInstance | The service instance is unknown to the supplier management system. | + +**Figure 6-103 – Service provisioner exceptions** + +#### 6.3.6.5 Reserve resources + +![UML class diagram for Reserve resources. The diagram shows the interactions between Profile Usage Mgr, Resource Allocator, and various profile and resource classes.](be9225da20b1fa284d0ed4b44fd633a3_img.jpg) + +``` + +classDiagram + class Profile_Object_Repository { + <> + retrieve() + } + class Profile_Usage_Mgr { + <> + obtain_profile_parameters() + } + class Resource_Allocator { + <> + Get_Service_Instance_Id_Reservations_Listing() + Get_Reservation_Id_Reserved_Resources_Listing() + CAC_Algorithms() + reserve_For_Service() + cancel_Reservation() + get_Reservation_Id() + report_Reserved_Resources() + get_Reservations() + cancel_All_Remaining_Reservations() + get_Reservation() + get_Available_Sys_Bandwidth() + assign_For_Service() + make_Unassigned() + } + class Management_Model_Maintainer { + <> + } + class ATM_Port_Resource { + <> + } + class Ethernet_Port_Resource { + <> + } + class TDM_Port_Resource { + <> + } + class Profile_Object_Management_Analysis { + <> + } + class AAL2PVC_Profile { + <> + } + class AAL2P_Profile_F { + <> + } + class AAL2P_Profile_F_2 { + <> + } + class DS1P_Profile { + <> + } + class E3P_Profile { + <> + } + class UNIMbf { + <> + } + class AAL1P_Profile_F { + <> + } + class DS3P_Profile { + <> + } + class E1P_Profile { + <> + } + class SSC_Parameter_Profile_2 { + <> + } + class Bridged_LAN_Service_Profile { + <> + } + class Traffic_Descriptor_Profile_F { + <> + } + class IDUC_Call_Processing_Profile { + <> + } + class CES_Service_Profile { + <> + } + class Voice_Service_Profile_AAL1 { + <> + } + class Bridged_LAN_Service_Profile_2 { + <> + } + class SSC_Parameter_Profile_1 { + <> + } + class Voice_Service_Profile_AAL2 { + <> + } + class Ethernet_Profile { + <> + } + class ATM_Network_Access_Profile_F { + <> + } + class LES_Service_Profile { + <> + } + class Voice_Service_Profile_AAL2_2 { + <> + } + class MAC_Bridge_Service_Profile { + <> + } + class Management_Model_Maintainer { + <> + } + + Profile_Object_Repository --> Profile_Usage_Mgr : retrieve() + Profile_Usage_Mgr --> Profile_Object_Repository : obtain_profile_parameters() + Profile_Usage_Mgr --> Resource_Allocator : lookup + Resource_Allocator --> Profile_Usage_Mgr : + Resource_Allocator --> Management_Model_Maintainer : consists + Resource_Allocator --> ATM_Port_Resource : adjusts + Resource_Allocator --> Ethernet_Port_Resource : adjusts + Resource_Allocator --> TDM_Port_Resource : adjusts + Profile_Object_Management_Analysis --> Profile_Usage_Mgr + Profile_Object_Management_Analysis --> Resource_Allocator + Profile_Object_Management_Analysis --> Management_Model_Maintainer + Profile_Object_Management_Analysis --> AAL2PVC_Profile + Profile_Object_Management_Analysis --> AAL2P_Profile_F + Profile_Object_Management_Analysis --> AAL2P_Profile_F_2 + Profile_Object_Management_Analysis --> DS1P_Profile + Profile_Object_Management_Analysis --> E3P_Profile + Profile_Object_Management_Analysis --> UNIMbf + Profile_Object_Management_Analysis --> AAL1P_Profile_F + Profile_Object_Management_Analysis --> DS3P_Profile + Profile_Object_Management_Analysis --> E1P_Profile + Profile_Object_Management_Analysis --> SSC_Parameter_Profile_2 + Profile_Object_Management_Analysis --> Bridged_LAN_Service_Profile + Profile_Object_Management_Analysis --> Traffic_Descriptor_Profile_F + Profile_Object_Management_Analysis --> IDUC_Call_Processing_Profile + Profile_Object_Management_Analysis --> CES_Service_Profile + Profile_Object_Management_Analysis --> Voice_Service_Profile_AAL1 + Profile_Object_Management_Analysis --> Bridged_LAN_Service_Profile_2 + Profile_Object_Management_Analysis --> SSC_Parameter_Profile_1 + Profile_Object_Management_Analysis --> Voice_Service_Profile_AAL2 + Profile_Object_Management_Analysis --> Ethernet_Profile + Profile_Object_Management_Analysis --> ATM_Network_Access_Profile_F + Profile_Object_Management_Analysis --> LES_Service_Profile + Profile_Object_Management_Analysis --> Voice_Service_Profile_AAL2_2 + Profile_Object_Management_Analysis --> MAC_Bridge_Service_Profile + +``` + +The diagram illustrates the Reserve resources class diagram. It features several key components and their interactions: + +- Profile\_Object\_Repository** (Boundary) interacts with **Profile\_Usage\_Mgr** (Control) via `retrieve()` and `obtain_profile_parameters()`. +- Profile\_Usage\_Mgr** (Control) interacts with **Resource\_Allocator** (Control) via `lookup`. +- Resource\_Allocator** (Control) interacts with **Management\_Model\_Maintainer** (Control) via `consists`. +- Resource\_Allocator** (Control) interacts with **ATM\_Port\_Resource** (Entity) via `adjusts`. +- Resource\_Allocator** (Control) interacts with **Ethernet\_Port\_Resource** (Entity) via `adjusts`. +- Resource\_Allocator** (Control) interacts with **TDM\_Port\_Resource** (Entity) via `adjusts`. +- Profile\_Object\_Management\_Analysis** (Note) is associated with **Profile\_Usage\_Mgr**, **Resource\_Allocator**, **Management\_Model\_Maintainer**, and various profile classes. + +The **Resource\_Allocator** class includes the following methods: + +- `Get_Service_Instance_Id_Reservations_Listing()` +- `Get_Reservation_Id_Reserved_Resources_Listing()` +- `CAC_Algorithms()` +- `reserve_For_Service()` +- `cancel_Reservation()` +- `get_Reservation_Id()` +- `report_Reserved_Resources()` +- `get_Reservations()` +- `cancel_All_Remaining_Reservations()` +- `get_Reservation()` +- `get_Available_Sys_Bandwidth()` +- `assign_For_Service()` +- `make_Unassigned()` + +The **Profile\_Usage\_Mgr** class includes the following method: + +- `obtain_profile_parameters()` + +The **Management\_Model\_Maintainer** class is an empty control class. + +The **ATM\_Port\_Resource**, **Ethernet\_Port\_Resource**, and **TDM\_Port\_Resource** classes are empty entity classes. + +The **Profile\_Object\_Management\_Analysis** is a note box containing a list of profile classes: AAL2PVC\_Profile, AAL2P\_Profile\_F, AAL2P\_Profile\_F\_2, DS1P\_Profile, E3P\_Profile, UNIMbf, AAL1P\_Profile\_F, DS3P\_Profile, E1P\_Profile, SSC\_Parameter\_Profile\_2, Bridged\_LAN\_Service\_Profile, Traffic\_Descriptor\_Profile\_F, IDUC\_Call\_Processing\_Profile, CES\_Service\_Profile, Voice\_Service\_Profile\_AAL1, Bridged\_LAN\_Service\_Profile\_2, SSC\_Parameter\_Profile\_1, Voice\_Service\_Profile\_AAL2, Ethernet\_Profile, ATM\_Network\_Access\_Profile\_F, LES\_Service\_Profile, Voice\_Service\_Profile\_AAL2\_2, and MAC\_Bridge\_Service\_Profile. + +UML class diagram for Reserve resources. The diagram shows the interactions between Profile Usage Mgr, Resource Allocator, and various profile and resource classes. + +Figure 6-104 – Reserve resources class diagram + +![Sequence diagram for Reserve and cancel reservation. The diagram shows interactions between an OMS Operator and five system components: Resource Allocator, OLT PON: ATMPortResource, ONT PON: ATMPortResource, OLT NNI: ATMPortResource, and ONT UNI: TDMPortResource. The process includes getting available system bandwidth, reserving for a service, updating metrics across all components, getting reservation details, canceling the reservation, and getting reservation IDs. Annotations explain the purpose of various steps, such as updating gauges and counters, showing input data, and handling exceptions.](26d6d8d333f84acff82b7a9f9b303da6_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant RA as Resource Allocator + participant OLT_PON as OLT PON : ATMPortResource + participant ONT_PON as ONT PON : ATMPortResource + participant OLT_NNI as OLT NNI : ATMPortResource + participant ONT_UNI as ONT UNI : TDMPortResource + + OMSOperator->>RA: getAvailableSysBandwidth() + activate RA + RA->>OMSOperator: + deactivate RA + + OMSOperator->>RA: reserveForService() + activate RA + RA->>OLT_PON: update "reserved" and "available" metrics + activate OLT_PON + OLT_PON->>RA: + deactivate OLT_PON + + RA->>ONT_PON: update "reserved" and "available" metrics + activate ONT_PON + ONT_PON->>RA: + deactivate ONT_PON + + RA->>OLT_NNI: update "reserved" and "available" metrics + activate OLT_NNI + OLT_NNI->>RA: + deactivate OLT_NNI + + RA->>ONT_UNI: update "reserved" and "available" metrics + activate ONT_UNI + ONT_UNI->>RA: + deactivate ONT_UNI + + RA->>OMSOperator: + deactivate RA + + Note over RA: Shows adjustments in gauges and counters. + OMSOperator->>RA: getAvailableSysBandwidth() + activate RA + RA->>OMSOperator: + deactivate RA + + Note over RA: Shows all input data and bandwidth associated with reservation request. + OMSOperator->>RA: getReservation() + activate RA + RA->>OMSOperator: + deactivate RA + + OMSOperator->>RA: cancelReservation() + activate RA + RA->>OLT_PON: update "reserved" and "available" metrics + activate OLT_PON + OLT_PON->>RA: + deactivate OLT_PON + + RA->>ONT_PON: update "reserved" and "available" metrics + activate ONT_PON + ONT_PON->>RA: + deactivate ONT_PON + + RA->>OLT_NNI: update "reserved" and "available" metrics + activate OLT_NNI + OLT_NNI->>RA: + deactivate OLT_NNI + + RA->>ONT_UNI: update "reserved" and "available" metrics + activate ONT_UNI + ONT_UNI->>RA: + deactivate ONT_UNI + + RA->>OMSOperator: + deactivate RA + + Note over RA: Makes exception. + OMSOperator->>RA: getReservationId() + activate RA + RA->>OMSOperator: + deactivate RA + + Note over RA: Shows original data. + OMSOperator->>RA: getAvailableSysBandwidth() + activate RA + RA->>OMSOperator: + deactivate RA + +``` + +Sequence diagram for Reserve and cancel reservation. The diagram shows interactions between an OMS Operator and five system components: Resource Allocator, OLT PON: ATMPortResource, ONT PON: ATMPortResource, OLT NNI: ATMPortResource, and ONT UNI: TDMPortResource. The process includes getting available system bandwidth, reserving for a service, updating metrics across all components, getting reservation details, canceling the reservation, and getting reservation IDs. Annotations explain the purpose of various steps, such as updating gauges and counters, showing input data, and handling exceptions. + +Figure 6-105 – Reserve and cancel reservation sequence diagram + +![Sequence diagram for Reserve resources showing interactions between OMS Operator, Resource Allocator, and various network elements (OLT PON, ONT PON, OLT NNI, ONT UNI). The diagram illustrates the process of reserving resources, reporting reserved resources, and canceling reservations.](f431b5db0c635c95318cff1adbe10c05_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant RA as ResourceAllocator + participant OLT_PON as OLT PON : ATMPortResource + participant ONT_PON as ONT PON : ATMPortResource + participant OLT_NNI as OLT NNI : ATMPortResource + participant ONT_UNI as ONT UNI : TDMPortResource + + OMSOperator->>RA: getAvailableSysBandwidth() + RA->>RA: update "reserved" and "available" metrics + RA->>OLT_PON: update "reserved" and "available" metrics + RA->>ONT_PON: update "reserved" and "available" metrics + RA->>OLT_NNI: update "reserved" and "available" metrics + RA->>ONT_UNI: update "reserved" and "available" metrics + RA->>OMSOperator: reportReservedResources() + Note over OLT_PON: Shows reserved resources. + Note over ONT_UNI: For same service connection type. + OMSOperator->>RA: reserveForService() + RA->>RA: update "reserved" and "available" metrics + RA->>OLT_PON: update "reserved" and "available" metrics + RA->>ONT_PON: update "reserved" and "available" metrics + RA->>OLT_NNI: update "reserved" and "available" metrics + RA->>ONT_UNI: update "reserved" and "available" metrics + RA->>OMSOperator: reportReservedResources() + Note over OLT_PON: Shows double reservation. + OMSOperator->>RA: cancelReservation() + Note over OLT_PON: Reduced by half. + RA->>OMSOperator: reportReservedResources() + OMSOperator->>RA: cancelAllRemainingReservations() + Note over OLT_PON: Shows none. + RA->>OMSOperator: reportReservedResources() + +``` + +Sequence diagram for Reserve resources showing interactions between OMS Operator, Resource Allocator, and various network elements (OLT PON, ONT PON, OLT NNI, ONT UNI). The diagram illustrates the process of reserving resources, reporting reserved resources, and canceling reservations. + +**Figure 6-106 – Reserve resources sequence diagram** + +##### Operations + +| Operation name | Operation purpose | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 1) reserveForService | This operation reserves bandwidth for a network resource such as ONT, ONU or NT whose installation is pending. | +| 2) cancelReservation | This operation is used to delete the reservation and release the resources from the reserved system capacity. | +| 3) getReservationId | This operation is used to display the reservation Id associated with the service instance Id that is assigned for the reserved bandwidth. | +| 4) reportReservedResources | This operation is used by the OMS to display the current reserved bandwidth in the specific headend NE (in this case the OLT). | +| 5) getReservations | This operation is used by OMS to retrieve all the reservations associated with the given NE. | +| 6) cancelAllRemainingReservations | This operation is used to delete all the remaining reservations against capacity associated with a given network element. | +| 7) getReservation | This operation is used to investigate the origins of a reservation of capacity within an NE. | +| 8) getAvailableSysBandwidth | This operation is used to determine the amount of capacity remaining for service connection reservation or assignment for a network element. | + +**Figure 6-107 – Resource allocator operations** + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) reserveForService | EndPointType (endpoint A),
EndPointType (endpoint Z),
NameSeqType (network profiles),
ServiceInstanceIdType | ReservationBandwidthType | UnknownNE,
UnknownPort,
UnknownProfiles,
InsufficientBW,
MaxSubtendingNodes Exceeded,
ConnectionCountExceeded,
CommFailure,
AccessDenied,
ProfileSuspended | +| 2) cancelReservation | ReservationIdType | AvailableSysBandwidthSeqType | UnknownReservationId,
CommFailure,
AccessDenied | +| 3) getReservationId | ServiceInstanceIdType | ReservationIdType | UnknownServiceInstance,
AccessDenied | +| 4) reportReservedResources | ManagedEntityIdType | ReservedBandwidthSeqType | UnknownNE,
AccessDenied | +| 5) getReservations | ManagedEntityIdType (NE) | ReservationIdSeqType | UnknownNE,
AccessDenied | +| 6) cancelAllRemaining Reservations | ManagedEntityIdType (NE) | AvailableSysBandwidthSeqType | UnknownNE,
CommFailure,
AccessDenied | +| 7) getReservation | ReservationIdType | ReservationInfoType | UnknownReservationId,
AccessDenied | +| 8) getAvailableSys Bandwidth | ManagedEntityIdType (NE) | AvailableSysBandwidthSeqType | UnknownNE,
CommFailure,
AccessDenied | + +**Figure 6-108 – Resource allocator signatures** + +##### Exceptions + +| Exception raised | Description | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| ConnectionCountExceeded | The maximum number of connections for the OLT or PON port has been exceeded with this request for service provisioning. | +| InsufficientBW | The CAC algorithm indicates that requested service requires too much bandwidth for the OLT. | +| MaxSubtendingNodesExceeded | The maximum engineered number of subtending nodes for the identified PON interface has been exceeded with this request for service provisioning or reservation. | +| ProfileSuspended | The named profile(s) in the invocation have been suspended for use within the supplier management system by the OMS or operator. | +| UnknownNE | Identified NE is unknown to the supplier management system. | +| UnknownPort | The identified port is unknown to the supplier management system. | +| UnknownProfiles | This exception is raised if the profile name provided is unknown to the supplier management system and cannot be retrieved from the profile object repository. | +| UnknownReservationId | The supplier management system does not recognize this reservation Id. | +| UnknownServiceInstance | The service instance is unknown to the supplier management system. | + +**Figure 6-109 – Resource allocator exceptions** + +### 6.3.7 Archiving and bulk transfer + +#### 6.3.7.1 Bulk transfer + +![Bulk transfer class diagram showing interactions between OMS/Operator, RecordSetMgr, Transfer Mgr, Log, Scheduler, Schedule Mgr, TransferLogRecord, Data Warehouse, Factory, and TransferTrackingObject.](24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg) + +``` +classDiagram + actor OMSOperator as OMS/Operator + class RecordSetMgr { + +RecordSetNameToldListing + } + class TransferMgr { + +RecordSetNameToldListing + +fileTransfer() + +scheduleFileTransfer() + +createFile() + +scheduledFileTransferListGet() + +fileTransferHistoryListGet() + +cancelScheduledFileTransfer() + +getStatus() + +modifyFileTransferSchedule() + } + class Log { + +Records + +storeRecord() + +findRecords() + +displayRecords() + +displayByKey() + } + class Scheduler { + } + class ScheduleMgr { + } + class TransferLogRecord { + } + class DataWarehouse as Data Warehouse + class Factory { + +create() + +delete() + } + class TransferTrackingObject { + +TransferObjectId + +InitialisationSchedule + +OperationalState + +ProceduralStatus + +TransferInvocationId + +AvailabilityStatus + +ActualStart + +ActualStop + +TerminationCriteria + +RecordSetId + +terminate() + +setCreateDefaults() + +setActualTime() + +getProceduralStatus() + +getOperationalState() + } + class RecordSet { + } + + OMSOperator --> RecordSetMgr : selects records + OMSOperator --> TransferMgr : requests file transfer + RecordSetMgr --> TransferMgr : obtain records + OMSOperator --> Log : views + OMSOperator --> ScheduleMgr : schedules activity + TransferMgr --> DataWarehouse : delivers to + Scheduler --> TransferMgr : triggers + TransferMgr --> Factory : commissions + Factory --> TransferTrackingObject : creates + TransferMgr --> TransferTrackingObject : record's progress + TransferLogRecord ..> Log : writes + RecordSet ..> TransferMgr : record set full + ScheduleMgr ..> RecordSetMgr : Details are found in "Scheduler" Analysis + RecordSet ..> RecordSetMgr : Details are found in "Control Archiving" Analysis +``` + +The diagram illustrates the bulk transfer process. An OMS/Operator interacts with RecordSetMgr (selects records) and TransferMgr (requests file transfer). RecordSetMgr obtains records from TransferMgr. The OMS/Operator also views Log and schedules activity with Schedule Mgr. TransferMgr delivers data to Data Warehouse, is triggered by Scheduler, and commissions Factory. Factory creates TransferTrackingObject, which TransferMgr tracks progress. TransferLogRecord writes to Log. RecordSet is notified of a full record set. Notes indicate that Scheduler and Control Archiving details are found in specific analysis documents. + +Bulk transfer class diagram showing interactions between OMS/Operator, RecordSetMgr, Transfer Mgr, Log, Scheduler, Schedule Mgr, TransferLogRecord, Data Warehouse, Factory, and TransferTrackingObject. + +Figure 6-110 – Bulk transfer class diagram + +![UML sequence diagram for Immediate bulk transfer. Lifelines: :Operator or OMS, :TransferMgr, TransferTrackingObject:Factory, :TransferTrackingObject, :RecordSet, :DataWareHouse, ActivityCompletion:Log, :RecordSetMgr. Messages: fileTransfer(), create(TransferTrackingObject), sendCreateDetails(), gatherAllRecords(), createFile(), establishFileTransfer(), getStatus(), getProceduralStatus(), setActualTime(), putFile(), setActualTime(), storeRecord(), delete(TransferTrackingObject), terminate(), selectRecords(), findRecords(), fileTransferHistoryGet(). Annotations: 'Can occur anytime before termination of the transfer object.', 'Attempt file transfer as many times as allowed by Data Ware house.', 'Shows requested file transfer.', 'Shows disposition of requested transfer.'](792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg) + +``` + +sequenceDiagram + actor Operator as :Operator or OMS + participant TransferMgr as :TransferMgr + participant Factory as TransferTrackingObject:Factory + participant TransferObj as :TransferTrackingObject + participant RecordSet as :RecordSet + actor DataWareHouse as :DataWareHouse + participant Log as ActivityCompletion:Log + participant RecordMgr as :RecordSetMgr + + Operator->>TransferMgr: fileTransfer() + activate TransferMgr + TransferMgr->>Factory: create(TransferTrackingObject) + activate Factory + Factory->>TransferObj: sendCreateDetails() + deactivate Factory + TransferMgr->>RecordSet: gatherAllRecords() + activate RecordSet + RecordSet->>TransferMgr: + deactivate RecordSet + TransferMgr->>TransferObj: createFile() + activate TransferObj + TransferObj->>DataWareHouse: establishFileTransfer() + activate DataWareHouse + DataWareHouse->>TransferMgr: + deactivate DataWareHouse + TransferMgr->>TransferObj: getStatus() + activate TransferObj + TransferObj->>TransferMgr: + deactivate TransferObj + TransferMgr->>TransferObj: getProceduralStatus() + activate TransferObj + TransferObj->>TransferMgr: + deactivate TransferObj + TransferMgr->>TransferObj: setActualTime() + activate TransferObj + TransferObj->>TransferMgr: + deactivate TransferObj + TransferMgr->>TransferObj: putFile() + activate TransferObj + TransferObj->>DataWareHouse: + activate DataWareHouse + DataWareHouse-->>TransferObj: + deactivate DataWareHouse + TransferObj->>TransferMgr: + deactivate TransferObj + TransferMgr->>TransferObj: setActualTime() + activate TransferObj + TransferObj->>TransferMgr: + deactivate TransferObj + TransferMgr->>Log: storeRecord() + activate Log + Log->>RecordMgr: + deactivate Log + TransferMgr->>TransferObj: delete(TransferTrackingObject) + activate TransferObj + TransferObj->>TransferMgr: terminate() + deactivate TransferObj + TransferMgr->>RecordSet: selectRecords() + activate RecordSet + RecordSet->>RecordMgr: findRecords() + activate RecordMgr + RecordMgr->>RecordSet: + deactivate RecordMgr + RecordSet->>RecordMgr: + deactivate RecordSet + TransferMgr->>RecordMgr: fileTransferHistoryGet() + activate RecordMgr + RecordMgr->>RecordSet: + deactivate RecordMgr + deactivate TransferMgr + +``` + +Can occur anytime before termination of the transfer object. + +Attempt file transfer as many times as allowed by Data Ware house. + +Shows requested file transfer. + +Shows disposition of requested transfer. + +UML sequence diagram for Immediate bulk transfer. Lifelines: :Operator or OMS, :TransferMgr, TransferTrackingObject:Factory, :TransferTrackingObject, :RecordSet, :DataWareHouse, ActivityCompletion:Log, :RecordSetMgr. Messages: fileTransfer(), create(TransferTrackingObject), sendCreateDetails(), gatherAllRecords(), createFile(), establishFileTransfer(), getStatus(), getProceduralStatus(), setActualTime(), putFile(), setActualTime(), storeRecord(), delete(TransferTrackingObject), terminate(), selectRecords(), findRecords(), fileTransferHistoryGet(). Annotations: 'Can occur anytime before termination of the transfer object.', 'Attempt file transfer as many times as allowed by Data Ware house.', 'Shows requested file transfer.', 'Shows disposition of requested transfer.' + +Figure 6-111 – Immediate bulk transfer sequence diagram + +![UML sequence diagram for Bulk transfer failure. Lifelines: : OMS/Operator, : Transfer Mgr, Transfer Tracking Object : Factory, : TransferTrackingObject, : Record Set, : Data Warehouse, Activity Completion : Log. Sequence: 1. : OMS/Operator calls fileTransfer() on : Transfer Mgr. 2. : Transfer Mgr calls create() on Transfer Tracking Object : Factory. 3. Transfer Tracking Object : Factory calls setCreateDefaults() on : TransferTrackingObject. 4. : Transfer Tracking Object : Factory calls gatherAllRecords() on : Record Set. 5. : Transfer Mgr calls createFile on : Transfer Tracking Object : Factory. 6. : Transfer Tracking Object : Factory calls establishFileTransfer on : Data Warehouse. 7. : Transfer Mgr calls setActualTime() on : TransferTrackingObject. 8. : Transfer Mgr calls pushFile on : Transfer Tracking Object : Factory. 9. : Transfer Tracking Object : Factory calls prepareRecord on : Transfer Tracking Object : Factory. 10. : Transfer Tracking Object : Factory calls storeRecord(Failure) on Activity Completion : Log. A note 'DCN fails.' points to the pushFile call.](e47d450f315d0b633906c03cc91f90ef_img.jpg) + +``` + +sequenceDiagram + actor Operator as : OMS/Operator + participant TM as : Transfer Mgr + participant Factory as Transfer Tracking Object : Factory + participant TTO as : TransferTrackingObject + participant RS as : Record Set + actor DW as : Data Warehouse + participant ACL as Activity Completion : Log + + Operator->>TM: fileTransfer() + activate TM + TM->>Factory: create() + activate Factory + Factory->>TTO: setCreateDefaults() + activate TTO + TTO->>RS: gatherAllRecords() + activate RS + RS-->>Factory: + deactivate RS + Factory->>TM: createFile + deactivate Factory + TM->>DW: establishFileTransfer + activate DW + DW-->>TM: + deactivate DW + TM->>TTO: setActualTime() + activate TTO + TTO-->>TM: + deactivate TTO + TM->>Factory: pushFile + activate Factory + Note over Factory: DCN fails. + Factory->>Factory: prepareRecord + activate Factory + Factory->>ACL: storeRecord(Failure) + activate ACL + ACL-->>Factory: + deactivate ACL + Factory-->>TM: + deactivate Factory + deactivate TM + +``` + +UML sequence diagram for Bulk transfer failure. Lifelines: : OMS/Operator, : Transfer Mgr, Transfer Tracking Object : Factory, : TransferTrackingObject, : Record Set, : Data Warehouse, Activity Completion : Log. Sequence: 1. : OMS/Operator calls fileTransfer() on : Transfer Mgr. 2. : Transfer Mgr calls create() on Transfer Tracking Object : Factory. 3. Transfer Tracking Object : Factory calls setCreateDefaults() on : TransferTrackingObject. 4. : Transfer Tracking Object : Factory calls gatherAllRecords() on : Record Set. 5. : Transfer Mgr calls createFile on : Transfer Tracking Object : Factory. 6. : Transfer Tracking Object : Factory calls establishFileTransfer on : Data Warehouse. 7. : Transfer Mgr calls setActualTime() on : TransferTrackingObject. 8. : Transfer Mgr calls pushFile on : Transfer Tracking Object : Factory. 9. : Transfer Tracking Object : Factory calls prepareRecord on : Transfer Tracking Object : Factory. 10. : Transfer Tracking Object : Factory calls storeRecord(Failure) on Activity Completion : Log. A note 'DCN fails.' points to the pushFile call. + +**Figure 6-112 – Bulk transfer failure sequence diagram** + +![UML sequence diagram for Scheduled bulk transfer. Lifelines: :OMSOperator, :Transfer Mgr, :Transfer Tracking Object Factory, :Transfer Tracking Object, :Record Set, :Scheduler, :Data Warehouse, :Activity Completion Log, :Scheduler. The diagram shows the process of scheduling, executing, and managing file transfers, including creating objects, setting parameters, performing transfers, and logging completion.](031de8ea6c5568a02faffd59b5c337f7_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant TransferMgr as :Transfer Mgr + participant TransferTrackingObjectFactory as :Transfer Tracking Object Factory + participant TransferTrackingObject as :Transfer Tracking Object + participant RecordSet as :Record Set + participant Scheduler as :Scheduler + participant DataWarehouse as :Data Warehouse + participant ActivityCompletionLog as :Activity Completion Log + participant Scheduler2 as :Scheduler + + OMSOperator->>TransferMgr: scheduleFileTransfer() + TransferMgr->>TransferTrackingObjectFactory: create() + TransferTrackingObjectFactory->>TransferTrackingObject: setCreateDetails() + TransferMgr->>Scheduler: addAssociatedActivity() + TransferMgr->>TransferTrackingObject: fileTransfer() + TransferMgr->>TransferTrackingObject: setProcedureStatus() + TransferMgr->>RecordSet: gatherAllRecords() + TransferMgr->>TransferTrackingObject: createFile() + TransferMgr->>DataWarehouse: establishFileTransfer() + TransferMgr->>TransferTrackingObject: setActualTime() + TransferMgr->>TransferTrackingObject: pushFile() + TransferMgr->>DataWarehouse: disconnect + TransferMgr->>TransferTrackingObject: setProcedureStatus() + TransferMgr->>ActivityCompletionLog: storeRecord() + Scheduler->>TransferMgr: scheduledFileTransferListGet() + Note over TransferMgr: Shows this periodic scheduled activity. + TransferMgr->>TransferMgr: modifyFileTransferSchedule() + TransferMgr->>Scheduler: removeAssociatedActivity() + TransferMgr->>Scheduler: addAssociatedActivity() + TransferMgr->>Scheduler: cancelScheduledFileTransfer() + TransferMgr->>Scheduler: removeAssociatedActivity() + TransferMgr->>TransferMgr: scheduledFileTransferListGet() + Note over TransferMgr: Shows none. + +``` + +UML sequence diagram for Scheduled bulk transfer. Lifelines: :OMSOperator, :Transfer Mgr, :Transfer Tracking Object Factory, :Transfer Tracking Object, :Record Set, :Scheduler, :Data Warehouse, :Activity Completion Log, :Scheduler. The diagram shows the process of scheduling, executing, and managing file transfers, including creating objects, setting parameters, performing transfers, and logging completion. + +Figure 6-113 – Scheduled bulk transfer sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 1) fileTransfer | The file transfer is initiated immediately by this operation. | +| 2) scheduleFileTransfer | The file transfer is scheduled for future initiation by this operation. | +| 3) modifyFileTransferSchedule | The file transfer schedule is modified by this operation. | +| 4) cancelScheduledFileTransfer | The scheduled file transfer is cancelled. | +| 5) getStatus | This operation allows the client to check the status of a transfer before its completion. | +| 6) fileTransferHistoryListGet | This operation is used to retrieve the list of all completed file transfers for the supplier management system. | +| 7) scheduledFileTransferListGet | This operation is used to retrieve the names of all existing scheduled file transfers defined for the supplier management system. | + +Figure 6-114 – Transfer manager operations + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------| +| 1) fileTransfer | ManagedEntityType,
DCNAddressType,
UserIdType,
PasswordType,
FilenameType,
boolean (overwrite?) | TransferTrackingObject
IdType | AccessDenied,
CommFailure,
UnknownRecordSet,
UnknownDestinationServer | +| 2) scheduleFileTransfer | ManagedEntityType,
DCNAddressType,
UserIdType,
PasswordType,
FilenameType,
boolean (overwrite?),
UserLabelType (scheduler
name) | TransferTrackingObject
IdType | AccessDenied,
UnknownRecordSet,
UnknownDestinationServer,
UnknownScheduler,
InvalidScheduler | +| 3) modifyFileTransferSchedule | TransferTrackingObjectIdType,
UserLabelType (scheduler
name) | void | AccessDenied,
UnknownTransferProcess,
UnknownScheduler,
InvalidScheduler | +| 4) cancelScheduledFileTransfer | TransferTrackingObjectIdType | void | AccessDenied,
UnknownTransferProcess | +| 5) getStatus | TransferTrackingObjectIdType | StatusValueType | AccessDenied,
UnknownTransferProcess | +| 6) fileTransferHistoryListGet | | FileTransferHistorySeq
Type | AccessDenied | +| 7) scheduledFileTransferListGet | | ScheduledFileTransfer
SeqType | AccessDenied | + +**Figure 6-115 – Transfer manager signatures** + +##### Exceptions + +| Exception raised | Description | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| InvalidScheduler | The scheduler parameters' values are outside defined scope. | +| UnknownDestinationServer | The identified destination server cannot be accessed by the transfer agent. | +| UnknownRecordSet | Record set identified in the request is unknown to the supplier management system. | +| UnknownScheduler | The named scheduler is unknown to the supplier management system. | +| UnknownTransferProcess | The status of the identified transfer process could not be checked because it is unknown to the supplier management system. | + +**Figure 6-116 – Transfer manager exceptions** + +#### 6.3.7.2 Control archives + +![UML Class Diagram for Control Archiving System](69d00e8adf9811292427fb2ce6712e39_img.jpg) + +``` + +classDiagram + class RecordSet { + RecordSetId + CurrentSize + OperationalState + MaximumSize + RecentClearTime + SizeThreshold + EntranceFilter + FullAction + SuspendStatus + Records + AdministrativeState + RecordType + UserLabel + storeRecord() + gatherAllRecords() + displayRecords() + findRecords() + getStatusAttributes() + setMaximumSize() + setSizeThreshold() + setFullAction() + setByCreation() + purge() + setAdministrativeState() + displayByKey() + getCurrentSize() + setUserLabel() + } + class RecordSetMgr { + RecordSetList + createArchive() + deleteArchive() + createLog() + getStatusAttributes() + suspendArchive() + resumeArchive() + purgeArchive() + selectRecords() + recordSetListGet() + changeUserLabel() + } + class Factory { + create() + delete() + } + class StatisticsCollector { + } + class EventScreen { + } + class EventQueue { + } + class EventSet { + } + class EventCorrelator { + } + class BPON_NE + class PrivilegedUser + class OMS_Operator + + RecordSet --> RecordSetMgr : enters record + RecordSetMgr --> Factory : commissions + RecordSetMgr --> RecordSet : controls recording + RecordSetMgr --> EventSet : suspends, resumes archiving or purges + RecordSetMgr --> EventSet : selects records + RecordSetMgr --> EventSet : logs event record + RecordSetMgr --> EventCorrelator : obtains correlation + Factory --> RecordSetMgr : commissions + StatisticsCollector --> RecordSetMgr : collects from + StatisticsCollector --> BPON_NE : collects from + BPON_NE --> EventScreen : sends event + PrivilegedUser --> RecordSetMgr : manipulates storage + PrivilegedUser --> EventScreen : notifies + EventScreen --> EventQueue : queues to + EventScreen --> EventSet : extracts from + EventQueue --> EventSet : extracts from + EventSet --> EventCorrelator : obtains correlation + EventCorrelator --> EventSet : obtains correlation + OMS_Operator --> EventSet : obtains correlation + OMS_Operator --> RecordSet : logs event record + +``` + +**Record Set** + +- RecordSetId +- CurrentSize +- OperationalState +- MaximumSize +- RecentClearTime +- SizeThreshold +- EntranceFilter +- FullAction +- SuspendStatus +- Records +- AdministrativeState +- RecordType +- UserLabel +- storeRecord() +- gatherAllRecords() +- displayRecords() +- findRecords() +- getStatusAttributes() +- setMaximumSize() +- setSizeThreshold() +- setFullAction() +- setByCreation() +- purge() +- setAdministrativeState() +- displayByKey() +- getCurrentSize() +- setUserLabel() + +**RecordSetMgr** + +- RecordSetList +- createArchive() +- deleteArchive() +- createLog() +- getStatusAttributes() +- suspendArchive() +- resumeArchive() +- purgeArchive() +- selectRecords() +- recordSetListGet() +- changeUserLabel() + +**Factory** + +- create() +- delete() + +**Statistics Collector** + +**Event Screen** + +**Event Queue** + +**Event Set** + +**Event Correlator** + +**Actors:** BPON NE, Privileged User (from Use Case View), OMS/Operator + +**Associations and Messages:** + +- Record Set** enters record to **RecordSetMgr**. +- RecordSetMgr** commissions **Factory**. +- RecordSetMgr** controls recording to **Record Set**. +- RecordSetMgr** suspends, resumes archiving or purges to **Event Set**. +- RecordSetMgr** selects records to **Event Set**. +- RecordSetMgr** logs event record to **Event Set**. +- RecordSetMgr** obtains correlation to **Event Correlator**. +- Factory** commissions **RecordSetMgr**. +- Statistics Collector** collects from **RecordSetMgr**. +- Statistics Collector** collects from **BPON NE**. +- BPON NE** sends event to **Event Screen**. +- Privileged User** manipulates storage to **RecordSetMgr**. +- Privileged User** notifies **Event Screen**. +- Event Screen** queues to **Event Queue**. +- Event Screen** extracts from **Event Set**. +- Event Queue** extracts from **Event Set**. +- Event Set** obtains correlation to **Event Correlator**. +- Event Correlator** obtains correlation to **Event Set**. +- OMS/Operator** obtains correlation to **Event Set**. +- OMS/Operator** logs event record to **Record Set**. + +**Notes:** + +- Details found in "Collect History Data" Analysis. +- Details explained in Appendix A. + +UML Class Diagram for Control Archiving System + +Figure 6-117 – Control archiving class diagram + +![UML sequence diagram for 'Create log' showing interactions between Privileged User, RecordSetMgr, EventSet, BPON NE, Event Screener, Record Set, and Log Factory.](9b6977f95ef47e2c87cd4979c09a7edb_img.jpg) + +``` + +sequenceDiagram + actor User as : Privileged User + participant RSM as : RecordSetMgr + participant ES as : EventSet + actor BPON as : BPON NE + participant EScreener as : Event Screener + participant RS as : Record Set + participant LF as Log : Factory + + User->>RSM: createLog() + activate RSM + RSM->>ES: modifyFilterLogListing() + activate ES + deactivate ES + deactivate RSM + + User->>RSM: resumeArchive() + activate RSM + RSM->>EScreener: setAdministrativeState() + activate EScreener + deactivate EScreener + deactivate RSM + + BPON->>EScreener: create() + activate EScreener + EScreener->>LF: setFullAction() + activate LF + deactivate LF + EScreener->>LF: setMaximumSize() + activate LF + deactivate LF + EScreener->>LF: setSizeThreshold() + activate LF + deactivate LF + deactivate EScreener + + EScreener->>ES: processEvent() + activate ES + ES->>EScreener: consumesRecord() + deactivate ES + activate EScreener + EScreener->>ES: matchToFilters() + activate ES + deactivate ES + EScreener->>RS: storeRecord() + activate RS + deactivate RS + deactivate EScreener + + User->>RS: getStatusAttributes() + activate RS + deactivate RS + deactivate User + +``` + +The diagram illustrates the 'Create log' sequence. It involves a Privileged User, RecordSetMgr, EventSet, BPON NE, Event Screener, Record Set, and Log Factory. The sequence begins with the Privileged User calling createLog() on RecordSetMgr. RecordSetMgr then calls modifyFilterLogListing() on EventSet. The Privileged User calls resumeArchive() on RecordSetMgr, which then calls setAdministrativeState() on Event Screener. BPON NE calls create() on Event Screener, which in turn calls setFullAction(), setMaximumSize(), and setSizeThreshold() on Log Factory. Event Screener then calls processEvent() on EventSet, which returns consumesRecord() to Event Screener. Event Screener then calls matchToFilters() on EventSet, which returns to Event Screener. Event Screener then calls storeRecord() on Record Set. Finally, the Privileged User calls getStatusAttributes() on Record Set. + +UML sequence diagram for 'Create log' showing interactions between Privileged User, RecordSetMgr, EventSet, BPON NE, Event Screener, Record Set, and Log Factory. + +Figure 6-118 – Create log sequence diagram + +![UML sequence diagram for Control log sequence diagram showing interactions between Privileged User, EventSet, EventScreen, RecordSet, RecordSetMgr, and LogFactory.](e492fe1061d82aa76cbf7114f57eb90c_img.jpg) + +``` + +sequenceDiagram + actor User as : Privileged User + participant EventSet as : EventSet + participant EventScreen as : EventScreen + participant RecordSet as Log : Record Set + participant RecordSetMgr as : RecordSetMgr + participant LogFactory as Log : Factory + + User->>EventSet: suspendArchive() + EventSet->>RecordSetMgr: getAdminIsrativeState() + RecordSetMgr->>RecordSet: + EventScreen->>EventSet: processEvent() + EventSet->>EventScreen: constructRecord() + EventScreen->>EventSet: matchToFilters() + EventSet->>RecordSetMgr: processEvent() + EventSet->>EventScreen: constructRecord() + EventScreen->>EventSet: matchToFilters() + User->>RecordSet: getStatusAttributes() + User->>RecordSetMgr: resumeArchive() + RecordSetMgr->>RecordSet: getAdminIsrativeState() + EventScreen->>EventSet: processEvent() + EventSet->>EventScreen: constructRecord() + EventScreen->>EventSet: matchToFilters() + EventSet->>RecordSet: storeRecord() + User->>RecordSetMgr: purgeArchive() + RecordSetMgr->>RecordSet: purge() + User->>RecordSetMgr: deleteArchive() + RecordSetMgr->>RecordSet: purge() + RecordSetMgr->>LogFactory: delete() + +``` + +The diagram illustrates the control log sequence. It involves a Privileged User, an EventSet object, an EventScreen object, a RecordSet object, a RecordSetMgr object, and a LogFactory object. The sequence begins with the Privileged User suspending the archive, followed by a series of interactions between EventSet and RecordSetMgr to manage the archive's state and process events. The Privileged User then resumes the archive, and the RecordSetMgr interacts with the RecordSet to purge and delete the archive. Finally, the RecordSetMgr deletes the archive from the LogFactory. + +UML sequence diagram for Control log sequence diagram showing interactions between Privileged User, EventSet, EventScreen, RecordSet, RecordSetMgr, and LogFactory. + +Figure 6-119 – Control log sequence diagram + +![UML sequence diagram for Control statistics archiving. Lifelines: :Privileged User, :RecordSetMgr, :Record Set, :BPNONE, :Statistics Collector, :Scheduler, :OMSOperator. Interactions include: createArchive() from User to Mgr; setCreation(), setSizeThreshold(), setMaximumSize(), setFullAction() from Mgr to Set; a loop 'Repeats for all records over a period of time' where Scheduler calls getHistoryData() on Collector, Collector calls getHistoryData() on BPNONE, BPNONE calls storeRecords() on Set, and Scheduler calls pmHistoryDataRecords() on Collector; Mgr calls getStatusAttributes() on Set; OMSOperator calls selectRecords() on Mgr; Mgr calls findRecords() on Set; User calls recordSetListGet() on Mgr; User calls changeUserLabel() on Mgr, which then calls setUserLabel() on Set.](3ce6b213ec556257e32ff7451182369d_img.jpg) + +``` + +sequenceDiagram + actor User as :Privileged User + participant Mgr as :RecordSetMgr + participant Set as :Record Set + participant BPNONE as :BPNONE + participant Collector as :Statistics Collector + participant Scheduler as :Scheduler + participant OMSOperator as :OMSOperator + + User->>Mgr: createArchive() + activate Mgr + Mgr->>Set: setCreation() + Mgr->>Set: setSizeThreshold() + Mgr->>Set: setMaximumSize() + Mgr->>Set: setFullAction() + deactivate Mgr + activate Set + + Scheduler->>Collector: pmHistoryDataRecords() + activate Collector + Collector->>BPNONE: getHistoryData() + activate BPNONE + BPNONE->>Set: storeRecords() + deactivate BPNONE + deactivate Set + deactivate Collector + + Scheduler-->>Collector: Repeats for all records over a period of time. + Scheduler-->>Collector: pmHistoryDataRecords() + Collector-->>BPNONE: getHistoryData() + BPNONE-->>Set: storeRecords() + deactivate BPNONE + deactivate Set + deactivate Collector + + Mgr->>Set: getStatusAttributes() + activate Mgr + activate Set + deactivate Set + deactivate Mgr + + OMSOperator->>Mgr: selectRecords() + activate OMSOperator + activate Mgr + Mgr->>Set: findRecords() + activate Mgr + activate Set + deactivate Set + deactivate Mgr + deactivate OMSOperator + + User->>Mgr: recordSetListGet() + activate User + activate Mgr + deactivate Mgr + deactivate User + + User->>Mgr: changeUserLabel() + activate User + activate Mgr + Mgr->>Set: setUserLabel() + activate Mgr + activate Set + deactivate Set + deactivate Mgr + deactivate User + +``` + +UML sequence diagram for Control statistics archiving. Lifelines: :Privileged User, :RecordSetMgr, :Record Set, :BPNONE, :Statistics Collector, :Scheduler, :OMSOperator. Interactions include: createArchive() from User to Mgr; setCreation(), setSizeThreshold(), setMaximumSize(), setFullAction() from Mgr to Set; a loop 'Repeats for all records over a period of time' where Scheduler calls getHistoryData() on Collector, Collector calls getHistoryData() on BPNONE, BPNONE calls storeRecords() on Set, and Scheduler calls pmHistoryDataRecords() on Collector; Mgr calls getStatusAttributes() on Set; OMSOperator calls selectRecords() on Mgr; Mgr calls findRecords() on Set; User calls recordSetListGet() on Mgr; User calls changeUserLabel() on Mgr, which then calls setUserLabel() on Set. + +Figure 6-120 – Control statistics archiving sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) createLog | This operation is used to create a record set in the supplier management system for the purposes of archiving event information. | +| 2) createArchive | This operation is used to create a record set for storing data. | +| 3) getStatusAttributes | At any time the operator or OMS can view the current status of an archive through this operation. | +| 4) suspendArchive | Once the short-term archive has been created and initialized for use, the OMS can suspend its use by invoking this operation. | +| 5) resumeArchive | This operation resumes recording in an archive or initializes the recording within a record set that has been constructed in a locked state. | +| 6) deleteArchive | This operation deletes an archive from the supplier management system. | +| 7) purgeArchive | This operation removes the information contained within a specified archive. However, the archive continues its recording. | +| 8) selectRecords | After the creation of an archive, this operation allows the selection of some (or all) of the records found within it. The selection is based on a filter. | +| 9) recordSetListGet | This operation allows an OMS to get a complete listings of record sets managed by the supplier management system. | +| 10) changeUserLabel | After the creation of a short-term archive, the OMS can change the user label assigned to the archive. | + +Figure 6-121 – Record set manager operations + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------------------------------------------------------------| +| 1) createLog | UserLabelType,
AdministrativeStateType
NameType (selection filter),
FullActionType,
MaxSizeType,
SizeThresholdType | ManagedEntityIdType | RecordSetExists,
DuplicateUserLabel,
AccessDenied | +| 2) createArchive | UserLabelType,
AdministrativeStateType,
RecordKindType,
MaxSizeType | ManagedEntityIdType | RecordSetExists,
DuplicateUserLabel,
AccessDenied | +| 3) getStatusAttributes | ManagedEntityIdType | RecordSetStatusType | AccessDenied,
UnknownRecordSet | +| 4) suspendArchive | ManagedEntityIdType | void | AccessDenied,
UnknownRecordSet | +| 5) resumeArchive | ManagedEntityIdType | void | AccessDenied,
UnknownRecordSet | +| 6) deleteArchive | ManagedEntityIdType | void | AccessDenied,
UnknownRecordSet | +| 7) purgeArchive | ManagedEntityIdType | void | AccessDenied,
UnknownRecordSet | +| 8) selectRecords | FilterType,
ManagedEntityIdType | RecordSeqType | UnknownRecordSet,
Timeout,
NoSuchRecords,
AccessDenied,
TooManyRecords | +| 9) recordSetListGet | CreationModeType | ManagedEntityIdSeqType | AccessDenied | +| 10) changeUserLabel | ManagedEntityIdType,
UserLabelType | void | UnknownRecordSet,
AccessDenied,
DuplicateUserLabel | + +**Figure 6-122 – Record set manager signatures** + +##### Exceptions + +| Exception raised | Description | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| DuplicateUserLabel | The user label provided in the request has been used to label another archive, i.e., one that is defined by a different set of creation request parameters. | +| NoSuchRecords | No records among the designated record sets matches the selection criteria. | +| RecordSetExists | The record set defined by the parameters of the creation request already exists in the supplier management system. | +| Timeout | The process duration reached a system-defined timeout before the process could complete. | +| TooManyRecords | The number of records selected for retrieval produces a response to the request that exceeds a predetermined size. | +| UnknownRecordSet | Record set identified in the request is unknown to the supplier management system. | + +**Figure 6-123 – Record set manager exceptions** + +#### 6.3.7.3 Performance and traffic monitoring reporting control + +![UML Class Diagram for Performance and traffic monitoring reporting control. The diagram shows the interactions between various components including BPON NE, Event Screenshot, Event Queue, TCAS Collector, Statistics Collector, Report Controller, and Record Set. It includes a list of methods for each class and a note about details provided in a specific case.](2c4c90917583576b27072e2083d75906_img.jpg) + +Details provided in "Process Incoming NE Events" use case. + +``` + +classDiagram + class BPON_NE { + <> + } + class Event_Screenshot { + } + class Event_Queue { + } + class TCAS_Collector { + CollectionInterval + NextTimeToMonitorList + +addMonitoringPoint() + +pullHistoryDataRecords() + +removeInactiveMonitoringPoints() + } + class Statistics_Collector { + CollectionInterval + NextTimeToMonitorList + MonitoringPointsScheduleList + +addMonitoringPointsSchedule() + +removeMonitoringPoint() + +pullHistoryDataRecords() + +removeInactiveMonitoringPoints() + +lowMonitoringPointsScheduleList() + +modifyMonitoringPointsSchedule() + } + class Report_Controller { + +displayActiveReporting() + +addNewMonitoringReporting() + +addCustomerMonitoringReporting() + +removeCustomerMonitoringReporting() + +selectByServiceInstance() + +selectByMonitoringPoint() + +createReportingSchedule() + +modifyReportingSchedule() + +cancelReportingSchedule() + } + class Record_Set { + RecordSetId + CurrentSize + OperationalState + MaximumSize + RecordKeepTime + SizeThreshold + EntranceFilter + ExitAction + SuspendedStatus + Records + RecordType + AdminIsWritableState + UserLabel + +storeRecord() + +retrieveAllRecords() + +displayRecords() + +findRecords() + +getStatisticsAttributes() + +setMaximumSize() + +setSizeThreshold() + +setExitAction() + +setEntryAction() + +storeRecords() + +displayByKey() + +prune() + +setAdminIsWritableState() + +getCurrentSize() + +setUserLabel() + } + class DailyScheduler { + } + class Implementation_Instance { + } + class CustomerComplaintStatisticsCollector { + ServiceInstanceTypeMonitoringPointsReference + +addServiceInstanceIds() + } + + BPON_NE --> Event_Screenshot : sends events + Event_Screenshot --> Event_Queue : queues to + Event_Queue --> TCAS_Collector : triggers collection + TCAS_Collector --> BPON_NE : collects from + TCAS_Collector --> Statistics_Collector : triggers + Statistics_Collector --> Record_Set : enters record + Report_Controller --> Statistics_Collector : schedules collection + Report_Controller --> BPON_NE : set threshold values + Report_Controller --> BPON_NE : controls reporting + Implementation_Instance --> BPON_NE : set + Implementation_Instance --> BPON_NE : collects from + CustomerComplaintStatisticsCollector <|-- Statistics_Collector + +``` + +**BPON NE** (Actor) Methods: + +- getTNTTrafficLoad() +- getUPCNPCKragreement() +- getVAL1PM() +- getVAL2PM() +- getVALSPM() +- getDS1PM() +- getDS3PM() +- getE1PM() +- getE3PM() +- getPVCPM() +- getEthernetPM() +- getMACBridgePM() +- getMACBridgePortPM() +- getVoicePM() +- setThresholdValues() +- RecordHistoryData() + +**Event Screenshot** Methods: + +- None + +**Event Queue** Methods: + +- None + +**TCAS Collector** Methods: + +- CollectionInterval +- NextTimeToMonitorList +- +addMonitoringPoint() +- +pullHistoryDataRecords() +- +removeInactiveMonitoringPoints() + +**Statistics Collector** Methods: + +- CollectionInterval +- NextTimeToMonitorList +- MonitoringPointsScheduleList +- +addMonitoringPointsSchedule() +- +removeMonitoringPoint() +- +pullHistoryDataRecords() +- +removeInactiveMonitoringPoints() +- +lowMonitoringPointsScheduleList() +- +modifyMonitoringPointsSchedule() + +**Report Controller** Methods: + +- +displayActiveReporting() +- +addNewMonitoringReporting() +- +addCustomerMonitoringReporting() +- +removeCustomerMonitoringReporting() +- +selectByServiceInstance() +- +selectByMonitoringPoint() +- +createReportingSchedule() +- +modifyReportingSchedule() +- +cancelReportingSchedule() + +**Record Set** Methods: + +- RecordSetId +- CurrentSize +- OperationalState +- MaximumSize +- RecordKeepTime +- SizeThreshold +- EntranceFilter +- ExitAction +- SuspendedStatus +- Records +- RecordType +- AdminIsWritableState +- UserLabel +- +storeRecord() +- +retrieveAllRecords() +- +displayRecords() +- +findRecords() +- +getStatisticsAttributes() +- +setMaximumSize() +- +setSizeThreshold() +- +setExitAction() +- +setEntryAction() +- +storeRecords() +- +displayByKey() +- +prune() +- +setAdminIsWritableState() +- +getCurrentSize() +- +setUserLabel() + +**Daily Scheduler** Methods: + +- None + +**Implementation Instance** Methods: + +- None + +**Customer Complaint Statistics Collector** Methods: + +- ServiceInstanceTypeMonitoringPointsReference +- +addServiceInstanceIds() + +UML Class Diagram for Performance and traffic monitoring reporting control. The diagram shows the interactions between various components including BPON NE, Event Screenshot, Event Queue, TCAS Collector, Statistics Collector, Report Controller, and Record Set. It includes a list of methods for each class and a note about details provided in a specific case. + +Figure 6-124 – Performance and traffic monitoring reporting control class diagram + +![UML sequence diagram for performance and traffic monitoring reporting (scheduled) - AAL1PM example. The diagram shows interactions between OMS/Operator, ReportController, BPON NE, Statistics Collector, Daily Scheduler, and AAL1PM Record Set.](5ee80a63ec53c60d7306b5a44984afcf_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant RC as : ReportController + actor BPON as : BPON NE + participant SC as : Statistics Collector + participant DS as : Daily Scheduler + participant AAL1PM as : AAL1PM Record Set + + OMS->>RC: createReportingSchedule() + activate RC + RC->>SC: addMonitoringPoint&Schedule() + activate SC + SC->>BPON: recordHistoryData() + activate BPON + BPON-->>SC: + deactivate BPON + RC->>SC: modifyMonitoringPointSchedule() + deactivate SC + RC->>RC: modifyReportingSchedule() + deactivate RC + + DS->>SC: refreshNextIntervalMonitoringList() + activate SC + SC->>SC: pullHistoryDataRecords() + activate SC + SC->>BPON: getAAL1PM() + activate BPON + BPON-->>SC: + deactivate BPON + SC->>AAL1PM: storeRecords() + activate AAL1PM + AAL1PM-->>SC: + deactivate AAL1PM + deactivate SC + deactivate DS + + OMS->>RC: selectByMonitoringPoint() + activate RC + RC-->>RC: + deactivate RC + deactivate OMS + +``` + +The sequence diagram illustrates the process of performance and traffic monitoring reporting (scheduled) for AAL1PM. It involves the following participants and interactions: + +- : OMS/Operator** (Actor) initiates the process by calling `createReportingSchedule()` on **: ReportController**. +- : ReportController** (Boundary) calls `addMonitoringPoint&Schedule()` on **: Statistics Collector**. +- : Statistics Collector** (Control) calls `recordHistoryData()` on **: BPON NE**. +- : BPON NE** (Actor) returns control to **: Statistics Collector**. +- : ReportController** calls `modifyMonitoringPointSchedule()` on **: Statistics Collector**. +- : ReportController** performs a self-call `modifyReportingSchedule()`. +- : Daily Scheduler** (Control) calls `refreshNextIntervalMonitoringList()` on **: Statistics Collector**. +- : Statistics Collector** performs a self-call `pullHistoryDataRecords()`. +- : Statistics Collector** calls `getAAL1PM()` on **: BPON NE**. +- : BPON NE** returns control to **: Statistics Collector**. +- : Statistics Collector** calls `storeRecords()` on **: AAL1PM Record Set**. +- : AAL1PM Record Set** (Entity) returns control to **: Statistics Collector**. +- : OMS/Operator** calls `selectByMonitoringPoint()` on **: ReportController**. +- : ReportController** performs a self-call. + +UML sequence diagram for performance and traffic monitoring reporting (scheduled) - AAL1PM example. The diagram shows interactions between OMS/Operator, ReportController, BPON NE, Statistics Collector, Daily Scheduler, and AAL1PM Record Set. + +**Figure 6-125 – Performance and traffic monitoring reporting (scheduled) sequence diagram – AAL1PM example** + +![UML sequence diagram for performance monitoring reporting (TCA triggered) sequence diagram – AAL1PM example. The diagram shows interactions between OMS/Operator, Impairment Persistence, Daily Scheduler, TCAStatsCollector, BPON NE, Event Screener, TCA EventQueue, and TCA AAL1PM Record Set.](d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as OMS/Operator + participant ImpairmentPersistence as : Impairment Persistence + participant DailyScheduler as : Daily Scheduler + participant TCAStatsCollector as : TCAStatsCollector + actor BPONNE as : BPON NE + participant EventScreener as : Event Screener + participant TCAEventQueue as TCA : EventQueue + participant TCAAAL1PMRecordSet as TCA AAL1PM : Record Set + + OMSOperator->>ImpairmentPersistence: setAllThresholds() + ImpairmentPersistence->>BPONNE: setThresholdValues() + OMSOperator->>ImpairmentPersistence: setThresholds() + ImpairmentPersistence->>BPONNE: setThresholdValues() + BPONNE->>EventScreener: readEvent() + EventScreener->>EventScreener: identifySource() + EventScreener->>EventScreener: identifyEventType() + EventScreener->>EventScreener: checkComplete() + EventScreener->>EventScreener: checkEventLogic() + EventScreener->>EventScreener: doPersistenceAnalysisProcess() + EventScreener->>TCAAAL1PMRecordSet: addMonitoringPoint() + EventScreener->>TCAAAL1PMRecordSet: addEvent() + TCAAAL1PMRecordSet->>TCAEventQueue: Showing TCA for AAL1PM example. + TCAAAL1PMRecordSet->>TCAEventQueue: pullHistoryDataRecords() + TCAAAL1PMRecordSet->>TCAEventQueue: getAAL1PM() + TCAAAL1PMRecordSet->>TCAAAL1PMRecordSet: storeRecord() + TCAAAL1PMRecordSet->>TCAAAL1PMRecordSet: refreshNextIntervalMonitoringList() + +``` + +UML sequence diagram for performance monitoring reporting (TCA triggered) sequence diagram – AAL1PM example. The diagram shows interactions between OMS/Operator, Impairment Persistence, Daily Scheduler, TCAStatsCollector, BPON NE, Event Screener, TCA EventQueue, and TCA AAL1PM Record Set. + +**Figure 6-126 – Performance monitoring reporting (TCA triggered) sequence diagram – AAL1PM example** + +![UML sequence diagram for performance and traffic monitoring reporting (customer complaint).](c93353297f7ed04bc9173ac1f224d406_img.jpg) + +``` + +sequenceDiagram + actor OMSOperator as :OMSOperator + participant ReportController as :ReportController + actor BPCN_NE as :BPCN_NE + participant CSC as :Customer Complaint Statistics Collector + participant DS as :Daily Scheduler + participant RS as :Record Set + + OMSOperator->>ReportController: displayActiveReporting() + ReportController->>CSC: showCustomerMonitoringPointsAndSchedule() + BPCN_NE->>CSC: modifyCustomerMonitoringPointsSchedule() + ReportController->>CSC: modifySchedule() + OMSOperator->>ReportController: addCustomerMonitoringReporting() + ReportController->>CSC: addCustomerMonitoringPoints&Schedule() + CSC->>BPCN_NE: recordHistoryData() + CSC->>DS: refreshNextTimeNextMonitoringList() + CSC->>DS: putCustomerHistoryDataRecords() + DS->>CSC: addServiceInstanceIds() + DS->>RS: storeRecord() + DS->>CSC: removeInactiveCustomerMonitoringPoints() + CSC->>BPCN_NE: getVALIPM() + CSC->>BPCN_NE: getDSIPM() + CSC->>BPCN_NE: getPVCPM() + OMSOperator->>ReportController: selectServiceInstance() + +``` + +The diagram illustrates the sequence of operations for performance and traffic monitoring reporting in a customer complaint scenario. The participants involved are the OMS Operator, Report Controller, BPCN\_NE, Customer Complaint Statistics Collector, Daily Scheduler, and Record Set. The process begins with the OMS Operator displaying active reporting, followed by the Report Controller showing monitoring points and schedules to the CSC. The BPCN\_NE and Report Controller then modify the schedule. The OMS Operator adds monitoring reporting, which the Report Controller passes to the CSC. The CSC records history data from BPCN\_NE and refreshes the monitoring list with the Daily Scheduler. The scheduler adds service instance IDs, stores records in the Record Set, and removes inactive monitoring points. Finally, the CSC retrieves VALIPM, DSIPM, and PVCPM data from BPCN\_NE, and the OMS Operator selects a service instance. + +UML sequence diagram for performance and traffic monitoring reporting (customer complaint). + +Figure 6-127 – Performance and traffic monitoring reporting (customer complaint) sequence diagram + +##### Operations + +| Operation name | Operation purpose | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) addCustomerMonitoringReporting | This operation causes performance monitoring at specific monitoring point(s) in response to a customer complaint. | +| 2) removeCustomerMonitoringReporting | This operation removes all performance monitoring statistics collection on behalf of a supplied service instance. | +| 3) selectByServiceInstance | This operation retrieves all the performance monitoring statistics available in the supplier management system associated with a given service instance Id. | +| 4) displayActiveReporting | This operation retrieves all the monitoring points for which performance monitoring statistics are currently being collected for a given service instance Id. | +| 5) addNewMonitoringReporting | This operation causes performance monitoring at specific monitoring point(s). | +| 6) selectByMonitoringPoint | This operation gets all the performance statistic records available in the supplier management system associated with the given monitoring point. | +| 7) createReportingSchedule | This operation adds a scheduled collection of performance monitoring statistics for a specific monitoring point. | +| 8) modifyReportingSchedule | This operation modifies the scheduled collection of performance monitoring statistics for a specific monitoring point. | +| 9) cancelReportingSchedule | This operation cancels subsequent scheduled collection of performance monitoring statistics where the scheduled reporting was requested by the operator previously. | + +**Figure 6-128 – Report controller operations** + +##### Operation signatures + +| Operation name | Input parameters | Return value | Exceptions | +|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) addCustomerMonitoringReporting | ManagedEntityType (NE),
ServiceInstanceIdType,
ManagedEntityType (monitoring point),
GeneralizedTimeType (stop time),
HistoryDataType,
short (granularity period) | void | UnknownServiceInstance,
AccessDenied,
UnknownNE,
UnknownManagedEntity,
CollectionPeriodPast,
CollectionLimitation,
InvalidAssociation,
UnknownHistoryDataType,
CommFailure | +| 2) removeCustomerMonitoringReporting | ServiceInstanceIdType | void | UnknownServiceInstance,
AccessDenied,
CollectionPeriodPast,
CommFailure | +| 3) selectByServiceInstance | ServiceInstanceIdType,
GeneralizedTimeType (start time),
GeneralizedTimeType (stop time), | RecordsSeqType | UnknownServiceInstance,
AccessDenied | +| 4) displayActiveReporting | ServiceInstanceIdType | MonitoringPointSeqType | UnknownServiceInstance,
AccessDenied | +| 5) addNewMonitoringReporting | ManagedEntityType (NE),
ManagedEntityType (monitoring point),
GeneralizedTimeType (stop time),
HistoryDataType,
short (granularity period) | void | AccessDenied,
UnknownNE,
UnknownManagedEntity,
CollectionPeriodPast,
CollectionLimitation,
InvalidAssociation,
UnknownHistoryDataType,
CommFailure | +| 6) selectByMonitoringPoint | ManagedEntityType (monitoring point),
GeneralizedTimeType (start time),
GeneralizedTimeType (stop time) | RecordsSeqType | UnknownManagedEntity,
AccessDenied | +| 7) createReportingSchedule | ManagedEntityType (NE),
ManagedEntityType (monitoring point),
HistoryDataType,
ServiceInstanceIdType,
short (granularity period),
UserLabelType (scheduler name) | void | AccessDenied,
UnknownNE,
UnknownManagedEntity,
CollectionLimitation,
UnknownScheduler,
InvalidAssociation,
UnknownHistoryDataType,
InvalidScheduler | +| 8) modifyReportingSchedule | ManagedEntityType (NE),
ManagedEntityType (monitoring point),
HistoryDataType,
ServiceInstanceIdType,
UserLabelType (scheduler name) | void | AccessDenied,
UnknownNE,
UnknownManagedEntity,
CollectionLimitation,
UnknownScheduler,
InvalidAssociation,
UnknownHistoryDataType,
InvalidScheduler | +| 9) cancelReportingSchedule | ManagedEntityType (NE),
ManagedEntityType (monitoring point),
HistoryDataType,
ServiceInstanceIdType,
UserLabelType (scheduler name) | void | AccessDenied,
UnknownNE,
UnknownManagedEntity,
UnknownScheduler,
InvalidAssociation,
UnknownHistoryDataType | + +**Figure 6-129 – Report controller signatures** + +##### Exceptions + +| Exception raised | Description | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| CollectionLimitation | The supplier management system cannot collect data for the given time duration and granularity period due to implementation restrictions. | +| CollectionPeriodPast | When the period end-time is less than or equal to the current time. | +| CommFailure | There was a DCN link failure between the NE and the supplier management system. | +| InvalidAssociation | The given profile cannot be applied to a monitoring point. | +| InvalidScheduler | The Scheduler parameters values are outside defined scope. | +| UnknownHistoryDataType | The history data type is unknown in the supplier management system. | +| UnknownManagedEntity | The specified managed entity is unknown to the supplier management system. | +| UnknownNE | The identified NE is unknown to the supplier management system. | +| UnknownScheduler | The named scheduler is unknown to the supplier management system. | +| UnknownServiceInstance | The service instance is unknown to the supplier management system. | + +**Figure 6-130 – Report controller exceptions** + +# Appendix I + +## Additional UML diagrams + +(This appendix does not form an integral part of this Recommendation) + +The following class and sequence diagrams are provided as non-normative information with the intention of completing a description of the behaviour within the supplier management system associated with use cases of clause 6 not directly involving the interface shown in Figure 6-1. + +## I.1 Process incoming NE events and log event records + +![UML class diagram for processing incoming NE events and logging event records.](9d47fe89bc71acebde670ea760ee6ffb_img.jpg) + +``` +classDiagram + actor BPON_NE as BPON NE + class Event_Screener { + +QueueList + +identifySource() + +doPersistenceAnalysisProcess() + +identifyEventType() + +checkComplete() + +checkEventLogic() + +readEvent() + } + class Event_Set { + +EventSetId + +RetrievalCriteria + +TimeWindow + +setAttributes() + +fillWithNewEvents() + +create() + +delete() + +purge() + +completesEventRecord() + } + class Event_Queue { + +EventType + +QueueId + +EventListing + +addEvent() + +selectEvents() + } + class Event_Correlator { + +obtainsCorrelation() + } + class Management_Model_Maintainer { + +consults() + } + class Record_Set { + +RecordSetId + +CurrentSize + +OperationalState + +MaximumSize + +RecentClearTime + +SizeThreshold + +EntranceFilter + +FullAction + +SuspendStatus + +Records + +RecordType + +AdministrativeState + +UserLabel + +storeRecord() + +gatherAllRecords() + +displayRecords() + +findRecords() + +getStatusAttributes() + +setMaximumSize() + +setSizeThreshold() + +setFullAction() + +setByCreation() + +purge() + +setAdministrativeState() + +getCurrentSize() + +displayByKey() + } + + BPON_NE --> Event_Screener : sends events + Event_Screener --> Event_Queue : queues to + Event_Set --> Event_Queue : extracts from + Event_Set --> Record_Set : logs event record + Event_Set --> Event_Correlator : obtains correlation + Event_Set --> Management_Model_Maintainer : consults +``` + +The diagram illustrates the process of handling incoming NE events and logging them. It features several classes and their interactions: + +- BPON NE** (Actor): Sends events to the **Event Screener**. +- Event Screener**: Contains a **QueueList** and methods for identifying sources, persistence analysis, event types, completion checks, logic checks, and reading events. It queues events to the **Event Queue**. +- Event Queue**: Contains attributes for event type, queue ID, and event listing, along with methods for adding and selecting events. It extracts data from the **Event Set**. +- Event Set**: Contains attributes for event set ID, retrieval criteria, and time window, and methods for setting attributes, filling with new events, creating, deleting, purging, and completing event records. It logs event records to the **Record Set**, obtains correlations from the **Event Correlator**, and consults the **Management Model Maintainer**. +- Event Correlator**: Provides correlation information to the **Event Set**. +- Management Model Maintainer**: Consulted by the **Event Set** for model-related operations. +- Record Set**: A comprehensive class containing numerous attributes (e.g., RecordSetId, CurrentSize, OperationalState, MaximumSize, RecentClearTime, SizeThreshold, EntranceFilter, FullAction, SuspendStatus, Records, RecordType, AdministrativeState, UserLabel) and methods for storing, gathering, displaying, finding, and managing records. + +UML class diagram for processing incoming NE events and logging event records. + +Figure I.1 – Incoming event class diagram + +![Sequence diagram for processing an incoming event. Lifelines: :BPON NE (actor), :Event Screener, :EventQueue. Messages: readEvent, identifySource(), identifyEventType(), checkComplete(), checkEventLogic(), doPersistenceAnalysisProcess(), addEvent(). A note indicates the first five messages are equivalent to 'validates' in an RCIA diagram.](fc7c83167c4e9e614f40e52b39ef735d_img.jpg) + +``` + +sequenceDiagram + actor BPON_NE as :BPON NE + participant Event_Screener as :Event Screener + participant Event_Queue as :EventQueue + + BPON_NE->>Event_Screener: readEvent + activate Event_Screener + Event_Screener->>Event_Screener: identifySource() + Event_Screener->>Event_Screener: identifyEventType() + Event_Screener->>Event_Screener: checkComplete() + Event_Screener->>Event_Screener: checkEventLogic() + Event_Screener->>Event_Screener: doPersistenceAnalysisProcess() + deactivate Event_Screener + Event_Screener->>Event_Queue: addEvent() + activate Event_Queue + deactivate Event_Queue + +``` + +Equivalent to "validates" in RCIA Sequence diagram. + +Sequence diagram for processing an incoming event. Lifelines: :BPON NE (actor), :Event Screener, :EventQueue. Messages: readEvent, identifySource(), identifyEventType(), checkComplete(), checkEventLogic(), doPersistenceAnalysisProcess(), addEvent(). A note indicates the first five messages are equivalent to 'validates' in an RCIA diagram. + +**Figure I.2 – Process incoming event sequence diagram** + +![Sequence diagram for logging an event. Lifelines: :EventQueue, :EventSet, :Event Correlator, :Management Model Maintainer, :Record Set. Messages: selectEvents(), obtainsCorrelation(), consults(), completesEventRecord(), storeRecord().](d7896dd2d38adf224c3b76cd22d29c10_img.jpg) + +``` + +sequenceDiagram + participant Event_Queue as :EventQueue + participant Event_Set as :EventSet + participant Event_Correlator as :Event Correlator + participant Management_Model_Maintainer as :Management Model Maintainer + participant Record_Set as :Record Set + + Event_Set->>Event_Queue: selectEvents() + activate Event_Queue + Event_Queue->>Event_Correlator: obtainsCorrelation() + activate Event_Correlator + deactivate Event_Correlator + Event_Queue->>Management_Model_Maintainer: consults() + activate Management_Model_Maintainer + deactivate Management_Model_Maintainer + Event_Queue->>Event_Set: completesEventRecord() + deactivate Event_Queue + Event_Set->>Record_Set: storeRecord() + activate Record_Set + deactivate Record_Set + +``` + +Sequence diagram for logging an event. Lifelines: :EventQueue, :EventSet, :Event Correlator, :Management Model Maintainer, :Record Set. Messages: selectEvents(), obtainsCorrelation(), consults(), completesEventRecord(), storeRecord(). + +**Figure I.3 – Log event sequence diagram** + +## I.2 Root cause alarm analysis + +![UML Class Diagram for Root cause alarm analysis showing actors, classes, and their interactions.](a98f3ef00da8508d2468334c6867f90f_img.jpg) + +``` + +classDiagram + actor BPON_NE + actor OMS_Operator + class Builder + class Management_Model_Maintainer + class Event_Screener { + +setValues() + +getValues() + } + class Event_Set_Manager { + +Scheduler + +notify() + +deleteEventSet() + } + class Event_Correlator { + +supersedeFilterings() + +addDependencyRelationshipInfo() + +groupWithSameDependentResource() + +removeGroupRedundancy() + +patternToSupportingResource() + } + class Alarm_Log { + +RecordSetId + +CurrentSize + +OperationalState + +MaximumSize + +RecentClearTime + +SizeThreshold + +EntranceFilter + +FullAction + +SuspendStatus + +Records + +RecordType + +AdministrativeState + +UserLabel + +storeRecord() + +gatherAllRecords() + +displayRecords() + +findRecords() + +getStatusAttributes() + +setMaximumSize() + +setSizeThreshold() + +setFullAction() + +setByCreation() + +purge() + +setAdministrativeState() + +getCurrentSize() + +displayByKey() + } + class Event_Set { + +EventSetId + +RetrievalCriteria + +TimeWindow + +setAttributes() + +fillWithNewEvents() + +create() + +delete() + +purge() + +completeEventRecord() + } + class Event_Queue { + +addEvents() + +selectEvents() + } + class Event_Forwarder { + +processAnnouncement() + } + + BPON_NE --> Builder : assigns severity + OMS_Operator --> Builder : provisions alarm severity + Builder --> Management_Model_Maintainer : updates + BPON_NE --> Event_Screener : sends alarm event + Event_Screener --> Event_Set_Manager : notifies + Event_Screener --> Event_Queue : queues to + Event_Set_Manager --> Event_Set : creates + Event_Set --> Event_Correlator : obtains correlation + Event_Set --> Event_Queue : extracts from + Event_Set --> Alarm_Log : writes root cause alarms + Event_Set --> Event_Forwarder : announces root cause alarms + Event_Correlator --> Event_Set : consults + +``` + +The diagram illustrates the root cause alarm analysis process. It involves several actors and classes: + +- Actors:** BPON NE and OMS/Operator. +- Classes:** Builder, Management Model Maintainer, Event Screener, Event Set Manager, Event Correlator, Alarm Log, Event Set, Event Queue, and Event Forwarder. + +**Interactions:** + +- BPON NE** assigns severity to the **Builder**. +- OMS/Operator** provisions alarm severity to the **Builder**. +- The **Builder** updates the **Management Model Maintainer**. +- BPON NE** sends an alarm event to the **Event Screener**. +- The **Event Screener** notifies the **Event Set Manager** and queues events to the **Event Queue**. +- The **Event Set Manager** creates an **Event Set**. +- The **Event Set** obtains correlation from the **Event Correlator** and consults it. +- The **Event Set** extracts events from the **Event Queue**. +- The **Event Set** writes root cause alarms to the **Alarm Log**. +- The **Event Set** announces root cause alarms to the **Event Forwarder**. + +**Event Set Manager Class Details:** + +- Attributes: Scheduler +- Operations: notify(), deleteEventSet() + +**Event Correlator Class Details:** + +- Operations: supersedeFilterings(), addDependencyRelationshipInfo(), groupWithSameDependentResource(), removeGroupRedundancy(), patternToSupportingResource() + +**Alarm Log Class Details:** + +- Attributes: RecordSetId, CurrentSize, OperationalState, MaximumSize, RecentClearTime, SizeThreshold, EntranceFilter, FullAction, SuspendStatus, Records, RecordType, AdministrativeState, UserLabel +- Operations: storeRecord(), gatherAllRecords(), displayRecords(), findRecords(), getStatusAttributes(), setMaximumSize(), setSizeThreshold(), setFullAction(), setByCreation(), purge(), setAdministrativeState(), getCurrentSize(), displayByKey() + +**Event Set Class Details:** + +- Attributes: EventSetId, RetrievalCriteria, TimeWindow +- Operations: setAttributes(), fillWithNewEvents(), create(), delete(), purge(), completeEventRecord() + +**Event Queue Class Details:** + +- Operations: addEvents(), selectEvents() + +**Event Forwarder Class Details:** + +- Operations: processAnnouncement() + +UML Class Diagram for Root cause alarm analysis showing actors, classes, and their interactions. + +Figure I.4 – Root cause alarm analysis class diagram + +![UML sequence diagram for Root cause alarm analysis. Lifelines: :BPON NE, :Event Screener, :EventDelete, :EventSet Manager, :EventSet, :Event Correlator, :Alarm Log, :EventForwarder. Messages: readEvents(), validate(), addEvent(), notify(), create(), selectEvents(), addDependencyRelationship(), groupWithSameDependencyResource(), removeGroupRedundancy(), suppressFilterings(), patternToSupportingResource(), completeEventRecord(), storeRecord(), processAnnouncement(), purge(), deleteEventSet(), delete().](f512ae9c630f2fb53197fa77a1bda0e8_img.jpg) + +``` + +sequenceDiagram + actor BPON_NE as :BPON NE + participant Event_Screener as :Event Screener + participant Event_Delete as :EventDelete + participant Event_Set_Manager as :EventSet Manager + participant Event_Set as :EventSet + participant Event_Correlator as :Event Correlator + participant Alarm_Log as :Alarm Log + participant Event_Forwarder as :EventForwarder + + BPON_NE->>Event_Screener: readEvents() + activate Event_Screener + Event_Screener->>Event_Screener: validate() + Event_Screener->>Event_Delete: addEvent() + activate Event_Delete + Event_Delete->>Event_Set_Manager: notify() + deactivate Event_Delete + activate Event_Set_Manager + Event_Set_Manager->>Event_Set: create() + activate Event_Set + Event_Set->>Event_Delete: selectEvents() + deactivate Event_Set + activate Event_Delete + Event_Delete->>Event_Correlator: addDependencyRelationship() + activate Event_Correlator + Event_Correlator->>Event_Set: groupWithSameDependencyResource() + activate Event_Set + Event_Set->>Event_Correlator: removeGroupRedundancy() + deactivate Event_Set + activate Event_Correlator + Event_Correlator->>Event_Set: suppressFilterings() + activate Event_Set + Event_Set->>Event_Correlator: patternToSupportingResource() + deactivate Event_Set + activate Event_Correlator + Event_Correlator->>Event_Set: completeEventRecord() + deactivate Event_Correlator + activate Event_Set + Event_Set->>Event_Set_Manager: storeRecord() + deactivate Event_Set + activate Event_Set_Manager + Event_Set_Manager->>Alarm_Log: processAnnouncement() + deactivate Event_Set_Manager + activate Alarm_Log + Alarm_Log->>Event_Forwarder: purge() + deactivate Alarm_Log + activate Event_Forwarder + Event_Forwarder->>Event_Set_Manager: deleteEventSet() + deactivate Event_Forwarder + activate Event_Set_Manager + Event_Set_Manager->>Event_Set: delete() + deactivate Event_Set_Manager + deactivate Event_Set + +``` + +UML sequence diagram for Root cause alarm analysis. Lifelines: :BPON NE, :Event Screener, :EventDelete, :EventSet Manager, :EventSet, :Event Correlator, :Alarm Log, :EventForwarder. Messages: readEvents(), validate(), addEvent(), notify(), create(), selectEvents(), addDependencyRelationship(), groupWithSameDependencyResource(), removeGroupRedundancy(), suppressFilterings(), patternToSupportingResource(), completeEventRecord(), storeRecord(), processAnnouncement(), purge(), deleteEventSet(), delete(). + +Figure I.5 – Root cause alarm analysis sequence diagram + + + +![UML sequence diagram for New NE event sequence. Lifelines: :BPQN NE, :Event Screener, :Event Queue, :Synchroniser, :Discoverer, :Event Forwarder, :Inventory Data. Messages: readEvents(new node), validates, addEvents(), notify(), selectEvents(), getNodeDetails(), getValues(), getEquipmentHolderList(), getPlugInUnits(), getPrevious(), formatInvDataRecord(), updates(), processAnnouncement(). Notes: 'Polling if event information is insufficient.' and 'For all new plug-in units and the node.'](defe20e5056d0c3552de2d50ce88c5cb_img.jpg) + +``` + +sequenceDiagram + actor BPQN_NE as :BPQN NE + participant Event_Screener as :Event Screener + participant Event_Queue as :Event Queue + participant Synchroniser as :Synchroniser + participant Discoverer as :Discoverer + participant Event_Forwarder as :Event Forwarder + participant Inventory_Data as :Inventory Data + + BPQN_NE->>Event_Screener: readEvents(new node) + activate Event_Screener + Event_Screener->>Event_Screener: validates + Event_Screener->>Event_Queue: addEvents() + deactivate Event_Screener + activate Event_Queue + Event_Queue->>Synchroniser: notify() + deactivate Event_Queue + activate Synchroniser + Synchroniser->>Event_Queue: selectEvents() + deactivate Synchroniser + activate Event_Queue + Event_Queue->>Discoverer: getNodeDetails() + deactivate Event_Queue + activate Discoverer + Discoverer->>BPQN_NE: getValues() + deactivate Discoverer + activate BPQN_NE + Note right of Discoverer: Polling if event information is insufficient. + Discoverer->>Discoverer: getEquipmentHolderList() + deactivate Discoverer + activate BPQN_NE + BPQN_NE->>Discoverer: getValues() + deactivate BPQN_NE + activate Discoverer + Discoverer->>Discoverer: getPlugInUnits() + deactivate Discoverer + activate BPQN_NE + BPQN_NE->>Discoverer: getValues() + deactivate BPQN_NE + activate Discoverer + Discoverer->>Inventory_Data: getPrevious() + deactivate Discoverer + activate Inventory_Data + deactivate Inventory_Data + Discoverer->>Discoverer: formatInvDataRecord() + deactivate Discoverer + Note left of Discoverer: For all new plug-in units and the node. + Discoverer->>Inventory_Data: updates() + deactivate Discoverer + activate Inventory_Data + deactivate Inventory_Data + Discoverer->>Event_Forwarder: processAnnouncement() + deactivate Discoverer + activate Event_Forwarder + deactivate Event_Forwarder + +``` + +UML sequence diagram for New NE event sequence. Lifelines: :BPQN NE, :Event Screener, :Event Queue, :Synchroniser, :Discoverer, :Event Forwarder, :Inventory Data. Messages: readEvents(new node), validates, addEvents(), notify(), selectEvents(), getNodeDetails(), getValues(), getEquipmentHolderList(), getPlugInUnits(), getPrevious(), formatInvDataRecord(), updates(), processAnnouncement(). Notes: 'Polling if event information is insufficient.' and 'For all new plug-in units and the node.' + +**Figure I.7 – New NE event sequence diagram** + +![UML sequence diagram for Register OLT and autodiscovery. Lifelines: : OMS/Operator, : NE Registrar, : Synchroniser, : Discoverer, : BPON NE, : Management Model Maintainer, : Event Forwarder. Messages: registerNE(OLT), get&compare(), getNodeDetails(), getValues(), getEquipmentHolderList(), getValues(), getPlugInUnits(), getValues(), consults(), formatInvDataRecord(), processAnnouncement(). A note indicates: 'For all new plug-in units and the OLT.'](af4f213abb5ad1891a43425e0d758021_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant NE as : NE Registrar + participant Syn as : Synchroniser + participant Disc as : Discoverer + participant BPON as : BPON NE + participant MM as : Management Model Maintainer + participant EF as : Event Forwarder + + OMS->>NE: registerNE(OLT) + activate NE + NE->>Syn: get&compare() + activate Syn + Syn->>Disc: getNodeDetails() + activate Disc + Disc->>BPON: getValues() + activate BPON + BPON-->>Disc: + deactivate BPON + Disc->>Syn: getEquipmentHolderList() + activate Syn + Syn->>BPON: getValues() + activate BPON + BPON-->>Syn: + deactivate BPON + Syn->>Disc: getPlugInUnits() + activate Disc + Disc->>BPON: getValues() + activate BPON + BPON-->>Disc: + deactivate BPON + Disc->>MM: consults() + activate MM + MM-->>Disc: + deactivate MM + Disc->>Disc: formatInvDataRecord() + activate Disc + Note left of Disc: For all new plug-in units and the OLT. + Disc->>EF: processAnnouncement() + activate EF + EF-->>Disc: + deactivate EF + deactivate Disc + deactivate Syn + deactivate NE + deactivate OMS + +``` + +UML sequence diagram for Register OLT and autodiscovery. Lifelines: : OMS/Operator, : NE Registrar, : Synchroniser, : Discoverer, : BPON NE, : Management Model Maintainer, : Event Forwarder. Messages: registerNE(OLT), get&compare(), getNodeDetails(), getValues(), getEquipmentHolderList(), getValues(), getPlugInUnits(), getValues(), consults(), formatInvDataRecord(), processAnnouncement(). A note indicates: 'For all new plug-in units and the OLT.' + +Figure I.8 – Register OLT and autodiscovery sequence diagram + +![UML sequence diagram for Equipment removal process involving OMS/Operator, Builder, BPDN NE, Event Screener, Event Queue, Synchroniser, Management Model Maintainer, and Event Forwarder.](43f7b6b61db9a2f3e3920740a9527d97_img.jpg) + +``` + +sequenceDiagram + actor OMS as : OMS/Operator + participant Builder as : Builder + participant BPDN as : BPDN NE + participant EventS as : Event Screener + participant EventQ as : Event Queue + participant Synchroniser as : Synchroniser + participant MM as : Management Model Maintainer + participant EventF as : Event Forwarder + + OMS->>Builder: modifyNode(administrative state) + activate Builder + Builder->>BPDN: setValues() + activate BPDN + BPDN->>EventS: readEvents(node removed) + activate EventS + EventS->>EventS: validates() + EventS->>EventQ: addEvents() + activate EventQ + EventQ->>Synchroniser: notify() + activate Synchroniser + Synchroniser->>EventQ: selectEvents() + deactivate Synchroniser + Synchroniser->>MM: consults() + activate MM + MM->>EventF: processAnnouncement() + activate EventF + EventF->>MM: formalInvDataRecord() + deactivate EventF + deactivate MM + Synchroniser->>Builder: deleteNode() + deactivate Synchroniser + deactivate EventQ + deactivate EventS + deactivate BPDN + deactivate Builder + +``` + +The sequence diagram illustrates the equipment removal process. It begins with the **: OMS/Operator** actor sending a **modifyNode(administrative state)** message to the **: Builder** participant. The **: Builder** then sends **setValues()** to the **: BPDN NE** participant. The **: BPDN NE** participant sends **readEvents(node removed)** to the **: Event Screener** participant. The **: Event Screener** performs a self-call **validates()**, then sends **addEvents()** to the **: Event Queue** participant. The **: Event Queue** participant sends **notify()** to the **: Synchroniser** participant. The **: Synchroniser** participant sends **selectEvents()** back to the **: Event Queue** participant. The **: Synchroniser** then sends **consults()** to the **: Management Model Maintainer** participant. The **: Management Model Maintainer** sends **processAnnouncement()** to the **: Event Forwarder** participant. The **: Event Forwarder** sends **formalInvDataRecord()** back to the **: Management Model Maintainer** participant. Finally, the **: Synchroniser** sends **deleteNode()** back to the **: Builder** participant, which then returns the control to the **: OMS/Operator** actor. + +UML sequence diagram for Equipment removal process involving OMS/Operator, Builder, BPDN NE, Event Screener, Event Queue, Synchroniser, Management Model Maintainer, and Event Forwarder. + +Figure I.9 – Equipment removal sequence diagram + +## I.4 Collect history data + +Figure I.10 provides the class diagram associated with history data collection triggered by routine needs for performance monitoring as well as by customer complaint or detection of threshold crossing alerts for a monitored performance parameter. Figure I.11 provides a sequence diagram that shows separate processes for history data collection triggered by customer complaint and history data collection triggered by all other mechanisms. + +![UML Class Diagram for Collect history data](cc91bf9aed46f8b219ebceaee276d195_img.jpg) + +``` +classDiagram + class ReportController + class DailyScheduler + class EventScreener + class StatisticsCollector { + +CollectionInterval + +MonitoringPointSchedulerList + +NextIntervalMonitoringList + +addMonitoringPoint&Schedule() + +removeMonitoringPoint() + +pullHistoryDataRecords() + +refreshNextIntervalMonitoringList() + +removeInactiveMonitoringPoints() + } + class CustomerComplaintStatisticsCollector { + +ServiceInstanceTypeMonitoringPointsReference + +addServiceInstanceIds() + } + class RecordSet + class BPON_NE { + +getATMTrafficLoad() + +getUPCNPCDisagreement() + +getAAL1PM() + +getAAL2PM() + +getAAL5PM() + +getDS1PM() + +getAPONPM() + +getDS3PM() + +getE1PM() + +getE3PM() + +getVPVCPM() + +getEthernetPM() + +getMACBridgePM() + +getMACBridgePortPM() + +getVoicePM() + } + + ReportController --> StatisticsCollector : modifies scheduled monitoring points + DailyScheduler --> StatisticsCollector : triggers + EventScreener --> StatisticsCollector : TCA triggers + StatisticsCollector <|-- CustomerComplaintStatisticsCollector + StatisticsCollector --> RecordSet : enters record + BPON_NE --> StatisticsCollector : collects from +``` + +The diagram illustrates the classes and interactions for collecting history data. The **Statistics Collector** class is central, containing attributes *CollectionInterval*, *MonitoringPointSchedulerList*, and *NextIntervalMonitoringList*, and methods *addMonitoringPoint&Schedule()*, *removeMonitoringPoint()*, *pullHistoryDataRecords()*, *refreshNextIntervalMonitoringList()*, and *removeInactiveMonitoringPoints()*. It is triggered by **Daily Scheduler** and **Event Screener** (via TCA triggers), and its monitoring points are modified by **ReportController**. A **Customer Complaint Statistics Collector** inherits from **Statistics Collector**, adding *ServiceInstanceTypeMonitoringPointsReference* and *addServiceInstanceIds()*. The **Statistics Collector** enters records into a **Record Set**, which is detailed in a note about "Control Archiving" Analysis. The **BPON NE** actor (from the Use Case View) collects data from the **Statistics Collector**, with a list of methods including *getATMTrafficLoad()*, *getUPCNPCDisagreement()*, *getAAL1PM()*, *getAAL2PM()*, *getAAL5PM()*, *getDS1PM()*, *getAPONPM()*, *getDS3PM()*, *getE1PM()*, *getE3PM()*, *getVPVCPM()*, *getEthernetPM()*, *getMACBridgePM()*, *getMACBridgePortPM()*, and *getVoicePM()*. + +UML Class Diagram for Collect history data + +Figure I.10 – Collect history data class diagram + +![UML sequence diagram for 'Collect history data' involving components like Daily Scheduler, Report Controller, Statistics Collector, BPON NE, and various Record Sets. The diagram shows a loop for processing monitoring points, with notes indicating repetition for all identified points and each type of 15-minute register.](ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg) + +``` + +sequenceDiagram + participant DS as :Daily Scheduler + participant RC as :Report Controller + participant SC as :Statistics Collector + participant BPON_NE as :BPON NE + participant AAL1PM_RS as 15 Minutes AAL1PM : Record Set + participant CCS as :Customer Complaint Statistics Collector + participant AAL1PM_CRS as 15 Minutes Cost AAL1PM : Record Set + participant TCA_BS as TCA : Best Screener + + DS->>RC: addMonitoringPointSchedule() + RC->>SC: addMonitoringPointSchedule() + SC->>BPON_NE: pullHistoryDataRecords() + BPON_NE->>SC: removeInactiveMonitoringPoints() + SC->>SC: refreshNextTimeMailMonitoringList() + SC->>AAL1PM_RS: getVAL1PM() + SC->>AAL1PM_RS: storeRecords() + Note over AAL1PM_RS: Repeating for all identified monitoring points and each type of 15 minute register. + SC->>CCS: addMonitoringPointSchedule() + RC->>CCS: pullHistoryDataRecords() + CCS->>SC: removeInactiveMonitoringPoints() + CCS->>SC: refreshNextTimeMailMonitoringList() + CCS->>BPON_NE: getVAL1PM() + CCS->>AAL1PM_CRS: addServiceInstanceIds() + CCS->>AAL1PM_CRS: storeRecords() + Note over AAL1PM_CRS: Repeating for all identified monitoring points and each type of 15 minute register with a selected monitoring point. + +``` + +UML sequence diagram for 'Collect history data' involving components like Daily Scheduler, Report Controller, Statistics Collector, BPON NE, and various Record Sets. The diagram shows a loop for processing monitoring points, with notes indicating repetition for all identified points and each type of 15-minute register. + +Figure I.11 – Collect history data sequence diagram + +# **Appendix II** + +## **High level summary class diagrams** + +(This appendix does not form an integral part of this Recommendation) + +The following class diagrams are provided as non-normative information with the intention of completing a description of the behaviour within the supplier management system. Object classes, actors and associations are identified for the use case diagrams of clause 6.2.1.3 where more than one use case is present. The purpose of providing this information is to show how use cases within the supplier management system addressing similar management functionality might employ the same internal object classes. Since these diagrams show primarily internal associations, the diagrams are for information only. + +## **II.1 Event handling** + +The following simplified class diagram, Figure II.1, shows interactions between external actors and classes internal to the supplier management system when events are processed in the supplier management system. This diagram serves to consolidate and provide consistency to diagrams found within clause 6.3.2. The analysis for the interactions called "provisions service", and "selects records" and "views" involving the actor called "OMS/Operator" in Figure II.1 are found in clauses 6.3.5 and 6.3.6, respectively. + +![High-level event handling class diagram showing interactions between various components like OMS/Operator, Service Provisioner, Event Set Manager, and Event Forwarder.](eca6a6c6546af8ac124c207445901964_img.jpg) + +``` + +classDiagram + actor OMSOperator as OMS/Operator + actor BPONNE as BPON NE + actor ExternalEventChannel as External Event Channel + class CurrentEventListing + class RecordSetMgr + class ImpairmentPersistence + class EventCorrelator + class ManagementModelMaintainer + class ServiceAffectingDeterminer + class EventForwarder + class NotificationAdmin + class EventSupplier + class EventQueue + class EventSetManager + class EventScreener + class Log + class Clock + class ManagedEntityFactory + class ServiceProvisioner + + OMSOperator --> CurrentEventListing : views + OMSOperator --> ServiceProvisioner : provisions service + OMSOperator --> RecordSetMgr : selects records + OMSOperator --> ImpairmentPersistence : sets threshold parameters + OMSOperator --> ManagedEntityFactory : updates containment relationships + OMSOperator --> ManagementModelMaintainer : modify properties of monitoring points + BPONNE --> EventScreener : sends events + EventScreener --> EventQueue : queues to + EventScreener --> EventSetManager : notifies + EventQueue --> EventSetManager : extracts from + EventSetManager --> EventSet : creates + EventSet --> CurrentEventListing : adds to current outage list + EventSet --> Log : logs event records + EventSet --> ImpairmentPersistence : writes not impairments to + EventSet --> EventCorrelator : obtains correlation + EventSet --> ManagementModelMaintainer : retrieves service tags + EventSet --> ServiceAffectingDeterminer : determines + EventSet --> EventForwarder : announces event + EventSet --> EventForwarder : announces QoS Alarm + EventForwarder --> NotificationAdmin : updates event supplier info + NotificationAdmin --> EventSupplier : updates external forwarding + EventSupplier --> EventForwarder : pushes event + EventSupplier --> ExternalEventChannel : pushes event + ExternalEventChannel --> EventSupplier : pushes event + CurrentEventListing --> RecordSetMgr : updates + RecordSetMgr --> ImpairmentPersistence : manages + ImpairmentPersistence --> EventCorrelator : consults + EventCorrelator --> ManagementModelMaintainer : consults + ManagementModelMaintainer --> ServiceAffectingDeterminer : consults + ServiceAffectingDeterminer --> ManagementModelMaintainer : consults + ServiceProvisioner --> ManagedEntityFactory : commissions + ManagedEntityFactory --> ManagementModelMaintainer : updates + Clock --> Log : triggers periodically + Log --> CurrentEventListing : provisions thresholds + +``` + +The diagram illustrates the high-level event handling process. It involves several actors and classes. The **OMS/Operator** actor interacts with **Current Event Listing**, **Service Provisioner**, **Record Set Mgr**, **Impairment Persistence**, **Managed Entity Factory**, and **Management Model Maintainer**. The **BPON NE** actor sends events to the **Event Screener**, which queues them to the **Event Queue** and notifies the **Event Set Manager**. The **Event Queue** extracts from the **Event Set**, which is created by the **Event Set Manager**. The **Event Set** then triggers various actions: it adds to the current outage list, logs event records, writes not impairments to **Impairment Persistence**, obtains correlation from **Event Correlator**, retrieves service tags from **Management Model Maintainer**, determines service affecting determiners, and announces events and QoS alarms to the **Event Forwarder**. The **Event Forwarder** updates event supplier info for the **Notification Admin**, which in turn updates external forwarding for the **Event Supplier**. The **Event Supplier** pushes events to the **Event Forwarder** and the **External Event Channel**, which also pushes events to the **Event Supplier**. The **Current Event Listing** updates the **Record Set Mgr**, which manages **Impairment Persistence**. The **Impairment Persistence** consults the **Event Correlator**, which consults the **Management Model Maintainer**, which in turn consults the **Service Affecting Determiner**. The **Service Provisioner** commissions the **Managed Entity Factory**, which updates the **Management Model Maintainer**. The **Clock** triggers periodically the **Log**, which provisions thresholds to the **Current Event Listing**. + +High-level event handling class diagram showing interactions between various components like OMS/Operator, Service Provisioner, Event Set Manager, and Event Forwarder. + +Figure II.1 – High-level event handling class diagram + +### II.2 Software and configuration data management + +The following simplified class diagram show interactions between external actors and classes internal to the supplier management system when software and NE configuration data is managed with the supplier management system. This diagram serves to consolidate and provide consistency to the subsequent diagrams found within clause 6.3.3. + +![Figure II.2 – High-level software and configuration data class diagram](a76fa39f5daf6a026e032495262ed0f6_img.jpg) + +A high-level UML class diagram showing the relationships between various management components and external actors. Key actors include OMS Operator, BPON NE, Secure File Server, OLT: BPON NE, and Operator or OMS. Core classes include Scheduler, Download Mgr, Transfer Mgr, MIB Mover, and Version Repository. Relationships are labeled with actions such as 'manipulates scheduling', 'obtains records', 'updates', 'commissions', 'triggers', 'delivers to', and 'extracts and applies MIB data'. + +Figure II.2 – High-level software and configuration data class diagram + +**Figure II.2 – High-level software and configuration data class diagram** + +156 ITU-T Rec. Q.834.3 (06/2004) + + + +## II.4 Provisioning + +Figure II.4 shows interactions between external actors and classes internal to the supplier management system when BPON equipment and services are being provisioned. This diagram serves to consolidate and provide consistency to the subsequent diagrams found within clause 6.3.6. + +![Figure II.4 – Provisioning class diagram. This is a complex UML class diagram showing the interactions for provisioning BPON equipment and services. It includes numerous classes such as Inventory Data, Management Model Interfaces, Profiles, BPON NE Registration, Event Clauses, NE Synchronism, Discovery, Event Supplies, External Communications, and various protocol-specific classes like ATM, MPLS, and GPRS. External actors like OMS Operator and BPON NE are also shown. Relationships include associations, generalizations, and specific interactions like 'build physical inventory', 'provision service', and 'update'.](c355b8056bdd4728357d7d5ed18792ca_img.jpg) + +The diagram illustrates the provisioning process within a supplier management system. Key components and interactions include: + +- External Actors:** OMS Operator, BPON NE, and an unnamed actor at the top left. +- Core Classes:** + - Inventory Data**: Interacts with **Management Model Interfaces** and **Profiles**. + - Management Model Interfaces**: Central hub for data management. + - Profiles**: Includes **Profile Object Consumer**, **Profile Object Repository**, and various **Profile** subclasses (e.g., **ATMNetConnProfile**, **MPLSProfile**, **GPRSProfile**). + - BPON NE Registration**: Manages **Event Clauses** and **NE Synchronism**. + - Event Clauses** and **NE Synchronism**: Handle event-driven logic and synchronization. + - Discovery** and **Event Supplies**: Manage discovery processes and event supply details. + - External Communications**: Facilitates communication with external systems. + - Notification Administration**: Manages system notifications. +- Internal Logic and Data:** + - Build** and **BuildLogical**: Core logic for building and logical representation of profiles. + - OLP** (Operation Logical Profile): A central class for logical operations. + - ATMConnConnProfile**, **MPLSConnConnProfile**, **GPRSConnConnProfile**: Specific connection profiles. + - Equipment** and **Physical** classes: Represent hardware components and their physical attributes. + - Service Provisioning**: The core process for provisioning services. +- Interactions:** + - Inventory Data** is *maintained by* **External Event Channel**. + - Management Model Interfaces** *publishes to* **Profile Object Consumer** and *provides access* to **Build**. + - Build** *builds physical inventory* for **BPON NE Registration**. + - BPON NE Registration** *registers* **Event Clauses** and *updates* **NE Synchronism**. + - Event Clauses** *publishes to* **Event Supplies**. + - Event Supplies** *publishes to* **External Communications**. + - External Communications** *publishes to* **Notification Administration**. + - Notification Administration** *updates* **Inventory Data**. + - Profiles** are *managed* and *provisioned* through various internal classes like **OLP** and **Service Provisioning**. + +Figure II.4 – Provisioning class diagram. This is a complex UML class diagram showing the interactions for provisioning BPON equipment and services. It includes numerous classes such as Inventory Data, Management Model Interfaces, Profiles, BPON NE Registration, Event Clauses, NE Synchronism, Discovery, Event Supplies, External Communications, and various protocol-specific classes like ATM, MPLS, and GPRS. External actors like OMS Operator and BPON NE are also shown. Relationships include associations, generalizations, and specific interactions like 'build physical inventory', 'provision service', and 'update'. + +Figure II.4 – Provisioning class diagram + +## II.5 Archiving and bulk transfer + +Figure II.5 shows interactions between external actors and classes internal to the supplier management system when statistics are archived for short periods of time in the supplier management system and eventually transferred, via a file transfer protocol, to long-term archives within an operator data warehouse. This diagram serves to consolidate and provide consistency to the subsequent diagrams found within clause 6.3.7. + +![UML Class Diagram for Archiving and Bulk Transfer](3429a2cee05dee88538d8b6816a5a877_img.jpg) + +``` + +classDiagram + actor BPON_NE + actor OperatorOrOMS as Operator or OMS + actor PrivilegedUser + class EventScreener + class EventQueue + class TCASStatsCollector + class DailyScheduler + class StatisticsCollector + class CustomerComplaintStatisticsCollector + class ReportController + class TransferRequestInfo + class TransferMgr + class Scheduler + class Factory + class ActivityCompletionLog + class TransferLogRecord + class RecordSet + class TransferTrackingObject + class RecordSetMgr + + BPON_NE --> EventScreener : sends events + BPON_NE --> TCASStatsCollector : collects from + BPON_NE --> StatisticsCollector : collects from + BPON_NE --> ReportController : sets thresholds & History Data recording + ReportController --> StatisticsCollector : reads scheduled monitoring points + OperatorOrOMS --> ReportController : sets thresholds and reporting + OperatorOrOMS --> TransferMgr : requests transfer + OperatorOrOMS --> ActivityCompletionLog : views + OperatorOrOMS --> RecordSetMgr : retrieves records + PrivilegedUser --> RecordSetMgr : suspends and resumes recording + + EventScreener --> EventQueue : queues to + EventScreener --> EventSet : sends record to + EventQueue --> EventSet : obtains correlation + EventSet --> EventCorrelator + EventScreener --> StatisticsCollector : triggers + DailyScheduler --> StatisticsCollector : triggers + DailyScheduler --> EventSet : triggers collection + StatisticsCollector --|> CustomerComplaintStatisticsCollector + StatisticsCollector --> TransferMgr : enters record + StatisticsCollector --> RecordSet : logs event record + TransferRequestInfo ..> TransferMgr : requests transfer + TransferMgr --> Scheduler : triggers + TransferMgr --> Factory : commissions + TransferMgr --> Factory : creates + TransferMgr --> RecordSet : reports progress + TransferMgr --> RecordSet : record set full + TransferMgr --> TransferLogRecord : writes + TransferMgr --> RecordSet : inventories + TransferMgr --> TransferTrackingObject + TransferLogRecord ..> RecordSet : inventories + RecordSetMgr --> RecordSet + +``` + +The diagram illustrates the interactions for archiving and bulk transfer. Key components include: + +- Actors:** BPON\_NE, Operator or OMS, Privileged User, and Data Warehouse. +- Classes:** EventScreener, EventQueue, TCASStatsCollector, DailyScheduler, StatisticsCollector, CustomerComplaintStatisticsCollector, ReportController, TransferRequestInfo, TransferMgr, Scheduler, Factory, ActivityCompletionLog, TransferLogRecord, RecordSet, TransferTrackingObject, and RecordSetMgr. +- Interactions:** + - BPON\_NE sends events to EventScreener and collects data from TCASStatsCollector and StatisticsCollector. + - Operator or OMS sets thresholds and reporting for ReportController and requests transfers from TransferMgr. + - ReportController reads scheduled monitoring points from StatisticsCollector. + - EventScreener queues events to EventQueue and sends records to EventSet. + - DailyScheduler triggers StatisticsCollector and EventSet. + - StatisticsCollector inherits from CustomerComplaintStatisticsCollector and logs event records to RecordSet. + - TransferMgr commissions and creates objects from a Factory, reports progress to RecordSet, and writes TransferLogRecords. + - RecordSetMgr manages RecordSet and is controlled by a Privileged User. + +UML Class Diagram for Archiving and Bulk Transfer + +Figure II.5 – Archiving and bulk transfer class diagram + +# Bibliography + +[b-OMG 99-06-01]    OMG Document formal/99-06-01, *OMG Modeling Book* (section 1). + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.86.4-199706-I_PDF-E/raw.md b/marked/Q/T-REC-Q.86.4-199706-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..16a4a3f948a741c19cbfd777ba8cd04d23fd9932 --- /dev/null +++ b/marked/Q/T-REC-Q.86.4-199706-I_PDF-E/raw.md @@ -0,0 +1,819 @@ + + +![ITU logo: a globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.86.4 + +(06/97) + +SERIES Q: SWITCHING AND SIGNALLING + +Functions and information flows for services in the ISDN – +Supplementary services + +--- + +**Stage 2 description for charging supplementary +services: International Freephone Service (IFS)** + +ITU-T Recommendation Q.86.4 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| Methodology | Q.60–Q.67 | +| Basic services | Q.68–Q.79 | +| Supplementary services | Q.80–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION Q.86.4** + +### **STAGE 2 DESCRIPTION FOR CHARGING SUPPLEMENTARY SERVICES: INTERNATIONAL FREEPHONE SERVICE (IFS)** + +## **Summary** + +Consistent with Recommendation E.152, International Freephone Service (IFS) Stage 1, this Recommendation constitutes the Stage 2 description for the service, including the functional architecture, Intelligent Network-based descriptions for normal IFS and optional features, and allocation of functional entities to physical locations. This Recommendation also provides Q.1200-Series references for information flows, SDL diagrams, and functional entity actions. + +### **Source** + +ITU-T Recommendation Q.86.4 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th of June 1997. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------------|-------------| +| 4 International Freephone Service (IFS)..... | 1 | +| 4.1 Scope..... | 1 | +| 4.2 References..... | 1 | +| 4.3 Definitions ..... | 2 | +| 4.4 Symbols and abbreviations ..... | 2 | +| 4.5 Description..... | 2 | +| 4.6 Derivation of the functional model..... | 3 | +| 4.6.1 Functional model description ..... | 3 | +| 4.6.2 Description of functional entities ..... | 3 | +| 4.6.3 Relationship with basic service ..... | 4 | +| 4.7 IN SIB-based service feature definitions ..... | 4 | +| 4.7.1 Announcement for caller ..... | 6 | +| 4.7.2 Geographical zone call routing..... | 7 | +| 4.7.3 Variable call routing ..... | 8 | +| 4.7.4 Additional customer service statistics/real-time information..... | 15 | +| 4.8 Information flows..... | 15 | +| 4.9 SDL diagrams for functional entities..... | 15 | +| 4.10 Functional entity actions..... | 15 | +| 4.11 Allocation of functional entities to physical locations..... | 16 | + + + +## Recommendation Q.86.4 + +### STAGE 2 DESCRIPTION FOR CHARGING SUPPLEMENTARY SERVICES: INTERNATIONAL FREEPHONE SERVICE (IFS) + +(Geneva, 1997) + +## 4 International Freephone Service (IFS) + +### 4.1 Scope + +This Recommendation defines the stage 2 service description for the call handling aspects of the international freephone service on the international Public Switched Telephone Network (PSTN). It is also applicable to IFS callers located on ISDNs or private networks directing calls towards IFS customers on the PSTN. It may be applicable to some degree to called IFS customers on ISDNs or private networks. + +This Recommendation is specified according to the methodology defined in Recommendation Q.65 (1997). + +This Recommendation does not formally describe the relationship between this supplementary service and basic call. Where possible, this information is included for guidance. + +"The **international freephone service (IFS)** enables a customer in one country to be assigned one or more special telephone numbers in another country(ies) which allow callers in those countries to call the customer free of charge. All service and call-related charges are paid by the customer. " (4.1/E.152.) + +This Recommendation is applicable to the stage 3 Recommendation for the IFS service. The term "stage 3" is also defined in Recommendation I.130. Where the text indicates the status of a requirement (i.e. as strict command or prohibition, as authorization leaving freedom, or as a capability or possibility), this shall be reflected in the text of the relevant stage 3 Recommendations. + +Conformance to this Recommendation is met by conforming to the stage 3 Recommendations with the field of application appropriate to the equipment being implemented. Therefore no method of testing is provided for this Recommendation. + +### 4.2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation E.152 (1996), *International freephone service*. +- ITU-T Recommendation Q.1213 (1995), *Global functional plane for intelligent network CS-1*. +- ITU-T Recommendation Q.1214 (1995), *Distributed functional plane for intelligent network CS-1*. + +- ITU-T Recommendation Q.1215 (1995), *Physical plane for intelligent network CS-1*. +- ITU-T Recommendation Q.65 (1997), *The unified functional methodology for the characterization of services and network capabilities*. + +### 4.3 Definitions + +This Recommendation defines the following terms. + +**4.3.1 IFS customer:** The individual or entity who (or which) obtains an international freephone service from an IFS service provider, and is responsible for payment of all charges due to that IFS service provider. + +**4.3.2 IFS caller:** The person who places a call to an IFS number. + +These definitions are extracted from clause 3/E.152. + +### 4.4 Symbols and abbreviations + +This Recommendation uses the following symbols and abbreviations: + +| | | +|-------|----------------------------------------| +| CCAF | Call Control Agent Function | +| CCF | Call Control Function | +| CID | Call Instance Data | +| CIDFP | Call Instance Data Field Pointer | +| CLI | Calling Line Identity | +| FE | Functional Entity | +| FIFO | First-In-First-Out | +| IFS | International Freephone Service | +| IN | Intelligent Network | +| ISDN | Integrated Services Digital Network | +| LE | Local Exchange | +| PNX | Private Network Exchange | +| PSTN | Public Switched Telephone Network | +| SCF | Service Control Function | +| SDF | Service Data Function | +| SDL | Specification and Description Language | +| SIB | Service Independent Building Block | +| SRF | Specialized Resource Function | +| SSF | Service Switching Function | +| TE | Terminal Equipment | +| TR | Transit Exchange | + +### 4.5 Description + +Not applicable. + +### 4.6 Derivation of the functional model + +International freephone service and its optional customer features are characterized in terms of SIBs in the IN context. The applicable functional model is that of the intelligent network as defined in Recommendation Q.1214, modified to show explicitly that initiating and terminating end treatment are required. + +### 4.6.1 Functional model description + +The functional model defining the supplementary service aspects of IFS is shown in Figure 4-1. + +![Figure 4-1/Q.86.4 – IFS functional model diagram showing two network architectures. The left architecture shows a vertical stack of SDF (FE4) connected to SCF (FE3), which is connected to SSF (FE1). SCF (FE3) is also connected to SRF (FE2). The right architecture shows a vertical stack of SDF (FE8) connected to SCF (FE6), which is connected to SSF (FE5). SCF (FE6) is also connected to SRF (FE7).](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +The diagram illustrates two functional models for IFS. Both models consist of a vertical stack of three functional entities (FEs): SDF (Service Data Function) at the top, SCF (Service Control Function) in the middle, and SSF (Service Switching Function) at the bottom. In the left model, SDF is labeled FE4, SCF is FE3, and SSF is FE1. SCF (FE3) is also connected to SRF (Service Resource Function, FE2) on the left. In the right model, SDF is labeled FE8, SCF is FE6, and SSF is FE5. SCF (FE6) is also connected to SRF (FE7) on the right. The label T1180820-96 is located at the bottom right of the diagram. + +Figure 4-1/Q.86.4 – IFS functional model diagram showing two network architectures. The left architecture shows a vertical stack of SDF (FE4) connected to SCF (FE3), which is connected to SSF (FE1). SCF (FE3) is also connected to SRF (FE2). The right architecture shows a vertical stack of SDF (FE8) connected to SCF (FE6), which is connected to SSF (FE5). SCF (FE6) is also connected to SRF (FE7). + +**Figure 4-1/Q.86.4 – IFS functional model** + +### 4.6.2 Description of functional entities + +The Functional Entities (FEs) required by IFS above those of basic call are as follows: + +- FE1: Originating service switching function. +- FE2: Originating side specialized resource function. +- FE3: Originating side service control function. +- FE4: Originating side service data function. +- FE5: Terminating side service switching function. +- FE6: Terminating side service control function. +- FE7: Terminating side specialized resource function. +- FE8: Terminating side service data function. + +The following table shows the functional entities spanned by each SIB used in this Recommendation, and the subclauses of Recommendation Q.1213 corresponding to the SIBs. + +| SIB | CCF/SSF | SCF | SDF | SRF | Q.1213 subclause | +|----------------------|---------|-----|-----|-----|------------------| +| Translate | | X | X | | 5.14 | +| Log call information | X | X | X | | 5.9 | +| User interaction | X | X | | X | 5.15 | +| Screen | | X | X | | 5.11 | +| Compare | | X | | | 5.6 | +| Queue | X | X | | X | 5.10 | + +#### 4.6.3 Relationship with basic service + +The relationship of the IFS functional model to basic service is shown in Figure 4-2. + +NOTE – The basic call model for this Recommendation is defined in Recommendation Q.1214. + +![Figure 4-2/Q.86.4 – Relationship of IFS functional model to basic service. The diagram shows two symmetrical functional models connected by a central CCF entity. Each model consists of a vertical stack of SDF, SCF, and SSF/CCF, with SRF and CCAF branching off. Functional entities are labeled FE1 through FE8.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +``` + +graph TD + subgraph Left_Model [Left Functional Model] + SDF4(SDF FE4) --- SCF3(SCF FE3) + SCF3 --- SRF2(SRF FE2) + SCF3 --- SSF1(SSF FE1) + SSF1 --- CCF1(CCF FE1) + CCF1 --- CCAF1(CCAF) + end + subgraph Right_Model [Right Functional Model] + SDF8(SDF FE8) --- SCF6(SCF FE6) + SCF6 --- SRF7(SRF FE7) + SCF6 --- SSF5(SSF FE5) + SSF5 --- CCF5(CCF FE5) + CCF5 --- CCAF2(CCAF) + end + CCF1 --- CCF5 + +``` + +CCF Call Control Function +CCAF Call Control Agent Function + +T1180830-96 + +Figure 4-2/Q.86.4 – Relationship of IFS functional model to basic service. The diagram shows two symmetrical functional models connected by a central CCF entity. Each model consists of a vertical stack of SDF, SCF, and SSF/CCF, with SRF and CCAF branching off. Functional entities are labeled FE1 through FE8. + +**Figure 4-2/Q.86.4 – Relationship of IFS functional model to basic service** + +### 4.7 IN SIB-based service feature definitions + +These global service logic and SIB diagrams conform to the semantics and syntax of Recommendations Q.1203 and Q.1213 (revised), with the exception that SIB error outputs are not shown or terminated. It is expected that error handling will be implementation-specific and is not covered in this Recommendation. + +With no additional customer service features, the SIB-based network support for the IFS service is shown in Figure 4-3. + +![Flowchart of the Normal IFS service process. It starts with 'Address analysed' pointing to a circle labeled 'Translate SIB'. Above this circle is the text 'Translate dialled # to destination network #'. An arrow points from 'Translate SIB' to another circle labeled 'Log call SIB'. Above this circle is the text 'Log to billing file for charging to account #'. An arrow points from 'Log call SIB' to a downward-pointing triangle labeled 'Proceed with new data'. To the right of this triangle is the text 'T1180840-96'.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +``` + +graph TD + Start([Address analysed]) --> TranslateSIB((Translate SIB)) + TranslateSIB --> LogCallSIB((Log call SIB)) + LogCallSIB --> End([Proceed with new data]) + +``` + +Translate dialled # to destination network # + +Log to billing file for charging to account # + +Address analysed + +Proceed with new data + +T1180840-96 + +Flowchart of the Normal IFS service process. It starts with 'Address analysed' pointing to a circle labeled 'Translate SIB'. Above this circle is the text 'Translate dialled # to destination network #'. An arrow points from 'Translate SIB' to another circle labeled 'Log call SIB'. Above this circle is the text 'Log to billing file for charging to account #'. An arrow points from 'Log call SIB' to a downward-pointing triangle labeled 'Proceed with new data'. To the right of this triangle is the text 'T1180840-96'. + +**Figure 4-3/Q.86.4 – Normal IFS service** + +The service support data for this service is shown in the following tables: + +| Translate SIB | | +|----------------------|-------------------------------| +| Service support data | Values | +| Object name | IFS number translation list | +| Translate filter | Originally dialled IFS number | +| Translated attribute | Network routing number | +| CIDFP-info | Originally dialled IFS number | +| CIDFP-translated | Network routing number | + +| Log call information SIB | | +|--------------------------|----------------------------------| +| Service support data | Values | +| CIDFP-log | IFS number and call attempt time | + +NOTE – While this Recommendation does not show all possible combinations of IFS and its options, combinations consistent with the requirements of the stage 1 service description can be readily formulated using IN techniques. + +### 4.7.1 Announcement for caller + +See Figure 4.4. + +![Flowchart for 'No-charge announcement to caller' showing a user interaction SIB with two paths: 'Prepared to complete call' and 'Continue with existing data'.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +``` +graph TD; Start([Prepared to complete call]) --> SIB((User interaction SIB)); SIB --> End1([Confirm no-charge nature of call to caller]); SIB --> End2([Continue with existing data]); +``` + +The diagram is a flowchart centered around a circle labeled "User interaction SIB". An arrow points from a triangle labeled "Prepared to complete call" to the circle. From the circle, two arrows point outwards. The top arrow points to the text "Confirm no-charge nature of call to caller". The bottom arrow points to a triangle labeled "Continue with existing data", with the reference "T1180850-96" placed next to it. + +Flowchart for 'No-charge announcement to caller' showing a user interaction SIB with two paths: 'Prepared to complete call' and 'Continue with existing data'. + +**Figure 4-4/Q.86.4 – No-charge announcement to caller** + +The service support data for this service feature is shown in the following table: + +| User interaction SIB | | +|--------------------------|------------------------------------------------| +| Service support data | Values | +| Announcement ID | Pointer to "confirmation of no-charge" message | +| Repetition requested | No | +| Collect information/type | Null (i.e. no collection of user input) | +| CIDFP-call_party | Caller | + +This terminating call treatment is in addition to the translation/logging for billing purposes at the initiating end for normal IFS. + +This feature can also be provided by the originating network by incorporating the user interaction SIB into normal IFS service (see 4.7, Figure 4-3), as shown in Figure 4-5. + +![Flowchart for Figure 4-5/Q.86.4: IFS with originating no-charge announcement. The process starts with 'Address analysed' leading to 'Translate SIB' (with function 'Translate dialled # to destination network #'). This leads to 'User interaction SIB' (with function 'Confirm no-charge nature of call to caller'), which then leads to 'Log call SIB' (with function 'Log to billing file for charging to account #'). The process ends with 'Proceed with new data' (with code 'T1180860-96').](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +graph TD + Start([Address analysed]) --> SIB1((Translate SIB)) + SIB1 --> SIB2((User interaction SIB)) + SIB2 --> SIB3((Log call SIB)) + SIB3 --> End([Proceed with new data]) + +``` + +Translate dialled # to destination network # + +Confirm no-charge nature of call to caller + +Log to billing file for charging to account # + +Address analysed + +Proceed with new data + +T1180860-96 + +Flowchart for Figure 4-5/Q.86.4: IFS with originating no-charge announcement. The process starts with 'Address analysed' leading to 'Translate SIB' (with function 'Translate dialled # to destination network #'). This leads to 'User interaction SIB' (with function 'Confirm no-charge nature of call to caller'), which then leads to 'Log call SIB' (with function 'Log to billing file for charging to account #'). The process ends with 'Proceed with new data' (with code 'T1180860-96'). + +**Figure 4-5/Q.86.4 – IFS with originating no-charge announcement** + +### 4.7.2 Geographical zone call routing + +See Figure 4-6. + +![Flowchart for Figure 4-6/Q.86.4: Geographical zone call routing. The process starts with 'Address analysed' leading to 'Screen SIB' (with function 'Check calling line identity against allowed zone list'). From 'Screen SIB', a 'Match' path leads to 'Translate SIB' (with function 'Translate dialled # to destination network #'), which then leads to 'Log call SIB' (with function 'Log to billing file for charging to account #'). A 'No match' path from 'Screen SIB' leads to 'User interaction SIB' (with function 'Inform caller: e.g. IFS calling from zone not supported'), which then leads to 'Clear call'. The process ends with 'Proceed with new data' (with code 'T1180870-96') from 'Log call SIB'.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` + +graph TD + Start([Address analysed]) --> SIB1((Screen SIB)) + SIB1 -- Match --> SIB2((Translate SIB)) + SIB1 -- No match --> SIB3((User interaction SIB)) + SIB2 --> SIB4((Log call SIB)) + SIB3 --> End1([Clear call]) + SIB4 --> End2([Proceed with new data]) + +``` + +Check calling line identity against allowed zone list + +Translate dialled # to destination network # + +Log to billing file for charging to account # + +Address analysed + +Clear call + +Proceed with new data + +T1180870-96 + +Match + +No match + +Inform caller: e.g. IFS calling from zone not supported + +Flowchart for Figure 4-6/Q.86.4: Geographical zone call routing. The process starts with 'Address analysed' leading to 'Screen SIB' (with function 'Check calling line identity against allowed zone list'). From 'Screen SIB', a 'Match' path leads to 'Translate SIB' (with function 'Translate dialled # to destination network #'), which then leads to 'Log call SIB' (with function 'Log to billing file for charging to account #'). A 'No match' path from 'Screen SIB' leads to 'User interaction SIB' (with function 'Inform caller: e.g. IFS calling from zone not supported'), which then leads to 'Clear call'. The process ends with 'Proceed with new data' (with code 'T1180870-96') from 'Log call SIB'. + +**Figure 4-6/Q.86.4 – Geographical zone call routing** + +The service support data for this service feature is shown in the following tables: + +| Screen SIB | | +|----------------------|--------------------------| +| Service support data | Values | +| Screen list name | Acceptable zone CLI list | +| Screen list filter | Calling line identity | +| CIDFP-screen | Calling line identity | + +| User Interaction SIB | | +|--------------------------|------------------------------------------------------| +| Service support data | Values | +| Announcement ID | Pointer to "call not allowed from your zone" message | +| Repetition requested | No | +| Collect information/type | Null (i.e. no collection of user input) | +| CIDFP-call_party | Caller | + +The service support data for the translate and log SIBs is the same as in 4.6. + +### 4.7.3 Variable call routing + +Variable call routing consists of a number of service features: + +#### 4.7.3.1 Point of origin call routing + +See Figure 4-7. + +![Flowchart of Point of origin call routing showing the sequence from Address analysed to Translate SIB, then to Log call SIB, and finally to Proceed with new data.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` + +graph TD + A[Address analysed] --> B((Translate SIB)) + B --> C((Log call SIB)) + C --> D[Proceed with new data] + +``` + +The diagram illustrates the process of point of origin call routing. It begins with 'Address analysed' (represented by a triangle symbol), which leads to the 'Translate SIB' (represented by a circle). Above the 'Translate SIB' circle, the text 'Translate dialled # and calling line id to destination network #' is written. An arrow points from 'Translate SIB' to the 'Log call SIB' (represented by a circle). Above the 'Log call SIB' circle, the text 'Log to billing file for charging to account #' is written. Finally, an arrow points from 'Log call SIB' to 'Proceed with new data' (represented by an inverted triangle symbol). The reference 'T1180880-96' is located near the 'Proceed with new data' symbol. + +Flowchart of Point of origin call routing showing the sequence from Address analysed to Translate SIB, then to Log call SIB, and finally to Proceed with new data. + +**Figure 4-7/Q.86.4 – Point of origin call routing** + +The service support data for this service feature is shown in the following table: + +| Translate SIB | | +|----------------------|---------------------------------------------| +| Service support data | Values | +| Object name | IFS point of origin number translation list | +| Translate filter | Originally dialled IFS number and CLI | +| Translated attribute | Network routing number | +| CIDFP-info | Originally dialled IFS number, CLI | +| CIDFP-translated | Network routing number | + +The service support data for the log SIB is the same as in 4.6. + +This feature can also be provided by the terminating network (in addition to normal originating treatment) as shown in Figure 4-8. + +![Flowchart for Point of origin call routing (destination). The process starts with 'Translate dialled # and calling line id to destination network #', leading to a circle labeled 'Translate SIB'. From this circle, two paths emerge: one leading to a triangle labeled 'Prepared to complete call', and another leading to a triangle labeled 'Handle as transit' with the reference 'T1180890-96'.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +graph TD + A[Translate dialled # +and calling line id +to destination +network #] --> B((Translate SIB)) + B --> C[Prepared to +complete call] + B --> D[Handle as transit +T1180890-96] + +``` + +Flowchart for Point of origin call routing (destination). The process starts with 'Translate dialled # and calling line id to destination network #', leading to a circle labeled 'Translate SIB'. From this circle, two paths emerge: one leading to a triangle labeled 'Prepared to complete call', and another leading to a triangle labeled 'Handle as transit' with the reference 'T1180890-96'. + +**Figure 4-8/Q.86.4 – Point of origin call routing (destination)** + +#### 4.7.3.2 Time-dependent call routing + +##### 4.7.3.2.1 Time-dependent routing to alternative destinations + +This feature is illustrated by an example using a different translation during the lunch period (1200 to 1400 hours). The parameters and the structure may vary from IFS customer-to-IFS customer. See Figure 4-9. + +![Flowchart illustrating time-dependent call routing logic. The process starts with 'Prepared to complete call' leading to a 'Compare SIB' block. This block compares the time of day against a 1400 hours limit. If the time is greater than 1400 hours (indicated by '>'), it proceeds to a 'Translate SIB' block for 'Non-lunch time translation, dialled # to destination network #'. If the time is less than or equal to 1400 hours (indicated by '<='), it proceeds to another 'Compare SIB' block. This second 'Compare SIB' block compares the time of day against a 1200 hours limit. If the time is greater than 1200 hours (indicated by '>'), it proceeds to a 'Translate SIB' block for 'Lunch time translation, dialled # to destination network #'. If the time is less than or equal to 1200 hours (indicated by '<='), it proceeds to a third 'Translate SIB' block. All three 'Translate SIB' blocks lead to a final 'Handle as transit' block, which is associated with the code 'T1180900-96'.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + Start([Prepared to complete call]) --> C1((Compare SIB)) + C1 -- ">" --> T1((Translate SIB)) + C1 -- "<=" --> C2((Compare SIB)) + C2 -- ">" --> T2((Translate SIB)) + C2 -- "<=" --> T3((Translate SIB)) + T1 --> End([Handle as transit]) + T2 --> End + T3 --> End + End --- Code[T1180900-96] + +``` + +Compare time of day against 1400 hours limit + +Non-lunch time translation, dialled # to destination network # + +Translate SIB + +Compare SIB + +Compare time of day against 1200 hours limit + +Lunch time translation, dialled # to destination network # + +Translate SIB + +Handle as transit + +T1180900-96 + +Flowchart illustrating time-dependent call routing logic. The process starts with 'Prepared to complete call' leading to a 'Compare SIB' block. This block compares the time of day against a 1400 hours limit. If the time is greater than 1400 hours (indicated by '>'), it proceeds to a 'Translate SIB' block for 'Non-lunch time translation, dialled # to destination network #'. If the time is less than or equal to 1400 hours (indicated by '<='), it proceeds to another 'Compare SIB' block. This second 'Compare SIB' block compares the time of day against a 1200 hours limit. If the time is greater than 1200 hours (indicated by '>'), it proceeds to a 'Translate SIB' block for 'Lunch time translation, dialled # to destination network #'. If the time is less than or equal to 1200 hours (indicated by '<='), it proceeds to a third 'Translate SIB' block. All three 'Translate SIB' blocks lead to a final 'Handle as transit' block, which is associated with the code 'T1180900-96'. + +**Figure 4-9/Q.86.4 – Time-dependent call routing** + +The service support data for this service feature is shown in the following tables: + +| Compare SIB | | +|----------------------|-------------------------------------------------------| +| Service support data | Values | +| Comparison type | Time, day or date, per customer requirements | +| CIDFP-compare | Time, day or date, per customer requirements | +| Reference value | Value of time, day or date, per customer requirements | + +| Translate SIB | | +|----------------------|---------------------------------------------------------------------------| +| Service support data | Values | +| Object name | Customer-specific IFS translation list corresponding to service logic leg | +| Translate filter | Originally dialled IFS number | +| Translated attribute | Network routing number | +| CIDFP-info | Originally dialled IFS number, CLI | +| CIDFP-translated | Network routing number | + +This terminating call treatment is in addition to the translation/logging for billing purposes at the initiating end for normal IFS. + +###### 4.7.3.2.2 Time-dependent routing to alternative destinations or announcement + +As a second example, the call can be routed to a destination or an announcement. See Figure 4-10. + +![Flowchart illustrating time-dependent routing logic. It starts with 'Prepared to complete call' leading to a 'Compare SIB' node. This node compares the time of day against a 1400 hours limit. If the time is greater than 1400 (>), it goes to a 'Translate SIB' node. If the time is equal to 1400 (=), it goes to another 'Compare SIB' node. If the time is less than 1400 (<), it goes to a 'User interaction SIB' node. The 'Translate SIB' node performs 'Non-lunch time translation, dialled # to destination network #' and leads to 'Handle as transit'. The second 'Compare SIB' node compares the time of day against a 1200 hours limit. If the time is greater than 1200 (>), it goes to the 'User interaction SIB' node. If the time is equal to 1200 (=), it loops back to itself. If the time is less than 1200 (<), it goes to the 'User interaction SIB' node. The 'User interaction SIB' node displays a 'Lunch time message, e.g. sorry, no service until 1400 hours' and leads to 'Clear call'.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +``` + +graph TD + Start([Prepared to complete call]) --> C1((Compare SIB)) + C1 -- ">" --> T1((Translate SIB)) + C1 -- "=" --> C2((Compare SIB)) + C1 -- "<" --> UI((User interaction SIB)) + T1 -->|Non-lunch time translation, dialled # to destination network #| H1([Handle as transit]) + C2 -- ">" --> UI + C2 -- "=" --> C2 + C2 -- "<" --> UI + UI -->|Lunch time message, e.g. sorry, no service until 1400 hours| C3([Clear call]) + +``` + +Flowchart illustrating time-dependent routing logic. It starts with 'Prepared to complete call' leading to a 'Compare SIB' node. This node compares the time of day against a 1400 hours limit. If the time is greater than 1400 (>), it goes to a 'Translate SIB' node. If the time is equal to 1400 (=), it goes to another 'Compare SIB' node. If the time is less than 1400 (<), it goes to a 'User interaction SIB' node. The 'Translate SIB' node performs 'Non-lunch time translation, dialled # to destination network #' and leads to 'Handle as transit'. The second 'Compare SIB' node compares the time of day against a 1200 hours limit. If the time is greater than 1200 (>), it goes to the 'User interaction SIB' node. If the time is equal to 1200 (=), it loops back to itself. If the time is less than 1200 (<), it goes to the 'User interaction SIB' node. The 'User interaction SIB' node displays a 'Lunch time message, e.g. sorry, no service until 1400 hours' and leads to 'Clear call'. + +**Figure 4-10/Q.86.4 – Time-dependent routing to destination or announcement** + +The additional service support data for this service feature is shown in the following table: + +| User interaction SIB | | +|--------------------------|--------------------------------------------| +| Service support data | Values | +| Announcement ID | Pointer to "no lunch-time service" message | +| Repetition requested | No | +| Collect information/type | Null (i.e. no collection of user input) | +| CIDFP-call_party | Caller | + +This terminating call treatment is in addition to the translation/logging for billing purposes at the initiating end for normal IFS. + +#### 4.7.3.3 Date-dependent call routing + +This feature is illustrated by an example using a different translation for Bastille Day, 14 July. The parameters and the structure may vary from IFS customer-to-IFS customer. See Figure 4-11. + +![Flowchart for Date-dependent call routing. The process starts with 'Prepared to complete' leading to 'Compare SIB'. From 'Compare SIB', a decision is made: if the date is greater than the 14 July limit (>), it goes to 'Translate SIB' (14 July translation); if equal (==), it goes to 'Translate SIB' (Non-14 July translation); if less than (<), it goes to 'Handle as transit'. Both 'Translate SIB' blocks lead to 'Handle as transit', which is associated with T1180920-96.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + Start([Prepared to complete]) --> CompareSIB((Compare SIB)) + CompareSIB -- "> Compare date against 14 July limit" --> TranslateSIB1((Translate SIB)) + TranslateSIB1 -- "14 July translation +dialled # to destination +network #" --> HandleTransit + CompareSIB -- "==" --> TranslateSIB2((Translate SIB)) + TranslateSIB2 -- "Non-14 July translation +dialled # to destination +network #" --> HandleTransit + CompareSIB -- "<" --> HandleTransit + HandleTransit --> End([Handle as transit]) + End --- T1180920-96 + +``` + +Flowchart for Date-dependent call routing. The process starts with 'Prepared to complete' leading to 'Compare SIB'. From 'Compare SIB', a decision is made: if the date is greater than the 14 July limit (>), it goes to 'Translate SIB' (14 July translation); if equal (==), it goes to 'Translate SIB' (Non-14 July translation); if less than (<), it goes to 'Handle as transit'. Both 'Translate SIB' blocks lead to 'Handle as transit', which is associated with T1180920-96. + +**Figure 4-11/Q.86.4 – Date-dependent call routing** + +The service support data for the translate SIB is the same as in 4.7.3.2. This terminating call treatment is in addition to the translation/logging for billing purposes at the initiating end for normal IFS. + +#### **4.7.3.4 Variable (follow-me) call routing** + +This is a service management feature and not part of call control. As such, it is beyond the scope of the stage 2 Recommendation. + +#### **4.7.3.5 Call completion on busy (traffic dependent) call routing** + +This terminating call treatment consists of the following three sub-options and is in addition to the translation/logging for billing purposes at the initiating end for normal IFS: + +- Diversion of calls to alternative destinations. +- Queueing of calls. +- Recorded announcements. + +##### 4.7.3.5.1 Diversion of calls to alternative destinations + +See Figure 4-12. + +![Flowchart for 'Diversion on busy' showing a 'Translate SIB' process box with two outgoing paths: one to a 'Busy' state and another to 'Handle as transit' with reference T1180930-96.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +Translate current destination # to forwarded-to # + +``` +graph TD; A[Translate SIB] --> B[Busy]; A --> C[Handle as transit]; +``` + +The diagram illustrates a process flow for call diversion. A central circular process box labeled "Translate SIB" receives an input from above with the instruction "Translate current destination # to forwarded-to #". From this box, two output paths emerge: one leads to a state represented by an upward-pointing triangle labeled "Busy", and the other leads to a state represented by a downward-pointing triangle labeled "Handle as transit". The reference "T1180930-96" is positioned next to the "Handle as transit" state. + +Flowchart for 'Diversion on busy' showing a 'Translate SIB' process box with two outgoing paths: one to a 'Busy' state and another to 'Handle as transit' with reference T1180930-96. + +**Figure 4-12/Q.86.4 – Diversion on busy** + +The service support data for this service feature is shown in the following table: + +| Translate SIB | | +|----------------------|------------------------------------| +| Service support data | Values | +| Object name | Forwarding number translation list | +| Translate filter | Destination number | +| Translated attribute | Forwarding number | +| CIDFP-info | Destination number | +| CIDFP-translated | Forwarding number | + +###### 4.7.3.5.2 Queueing of calls/recorded announcements + +See Figure 4-13. + +![Sequence diagram for Queueing of calls/recorded announcements. The diagram shows the interaction between a caller, a QUEUE SIB, and a UI SIB. The caller sends a 'Message to caller while in queue' to the QUEUE SIB. The QUEUE SIB sends 'Resource available' to the caller, 'Call abandon' to the UI SIB, 'Timer expiry' to the UI SIB, and 'Queue full' to the UI SIB. The UI SIB sends 'Message to caller that call cannot be completed because queue is full' to the caller. The UI SIB also sends 'Message to caller that allowed time in queue has expired and call will be cleared' to the caller. The caller then sends 'Prepared to complete call' to the QUEUE SIB. The QUEUE SIB sends 'Clear call' to the caller and 'Continue with existing data' to the UI SIB. The diagram is labeled T1182410-96.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant Caller + participant QUEUE_SIB as QUEUE SIB + participant UI_SIB as UI SIB + + Caller->>QUEUE_SIB: Message to caller while in queue + QUEUE_SIB->>Caller: Resource available + QUEUE_SIB->>UI_SIB: Call abandon + QUEUE_SIB->>UI_SIB: Timer expiry + QUEUE_SIB->>UI_SIB: Queue full + UI_SIB-->>Caller: Message to caller that call cannot be completed because queue is full + UI_SIB-->>Caller: Message to caller that allowed time in queue has expired and call will be cleared + Caller->>QUEUE_SIB: Prepared to complete call + QUEUE_SIB->>Caller: Clear call + QUEUE_SIB->>UI_SIB: Continue with existing data + +``` + +T1182410-96 + +Sequence diagram for Queueing of calls/recorded announcements. The diagram shows the interaction between a caller, a QUEUE SIB, and a UI SIB. The caller sends a 'Message to caller while in queue' to the QUEUE SIB. The QUEUE SIB sends 'Resource available' to the caller, 'Call abandon' to the UI SIB, 'Timer expiry' to the UI SIB, and 'Queue full' to the UI SIB. The UI SIB sends 'Message to caller that call cannot be completed because queue is full' to the caller. The UI SIB also sends 'Message to caller that allowed time in queue has expired and call will be cleared' to the caller. The caller then sends 'Prepared to complete call' to the QUEUE SIB. The QUEUE SIB sends 'Clear call' to the caller and 'Continue with existing data' to the UI SIB. The diagram is labeled T1182410-96. + +**Figure 4-13/Q.86.4 – Queueing of calls/recorded announcements** + +The service support data for this service feature is shown in the following tables: + +| Queue SIB | | +|------------------------------|----------------------------------------------------------------------| +| Service support data | Values | +| Max active | Maximum number of simultaneous calls supported at the IFS subscriber | +| Max number | Maximum number of calls allowed in the queue | +| Max time | Maximum time a call is allowed to remain in a queue | +| Announcement ID | Pointer to "an attendant will be with you shortly" message | +| Repetition requested | Customer specified | +| Repetition interval | Customer specified | +| Maximum repetitions repeated | Customer specified | +| CIDFP-call_party | Caller | + +| User interaction SIB | | +|--------------------------|---------------------------------------------------| +| Service support data | Values | +| Announcement ID | Pointer to "queue full" or "timer expiry" message | +| Repetition requested | No | +| Collect information/type | Null (i.e. no collection of user input) | +| CIDFP-call_party | Caller | + +### 4.7.4 Additional customer service statistics/real-time information + +As a national option, the network should provide by suitable means, to the extent possible, the called and calling number, from which the customer can deduce the origin of the call and the charging related to the call. + +### 4.8 Information flows + +International freephone service and its optional customer features are characterized in terms of SIBs. The information flows for these SIBs are defined in Recommendation Q.1214 as shown in the following table. + +| SIB information flows | Q.1214 subclause | +|-----------------------|------------------| +| Translate | 5.2.11.2 | +| Log call information | 5.2.6.2 | +| User interaction | 5.2.12.2 | +| Screen | 5.2.8.2 | +| Compare | 5.2.3.2 | +| Queue | 5.2.7.2 | + +NOTE – No new information flows are required between the CCAF $\leftrightarrow$ CCF ( $r_1$ and $r_3$ ) or CCF $\leftrightarrow$ CCF ( $r_2$ ). + +### 4.9 SDL diagrams for functional entities + +International freephone service and its optional customer features are characterized in terms of SIBs. The SDL diagrams for these SIBs are defined in Recommendation Q.1214 as shown in the following table. + +| SIB SDLs | Q.1214 subclause | +|----------------------|------------------| +| Translate | 5.2.11.3 | +| Log call information | 5.2.6.3 | +| User interaction | 5.2.12.3 | +| Screen | 5.2.8.3 | +| Compare | 5.2.3.3 | +| Queue | 5.2.7.3 | + +### 4.10 Functional entity actions + +International freephone service and its optional customer features are characterized in terms of SIBs. The functional entity actions for these SIBs are defined in Recommendation Q.1214 as shown in the following table. + +| SIB functional entity actions | Q.1214 subclause | +|--------------------------------------|-------------------------| +| Translate | 5.2.11.4 | +| Log call information | 5.2.6.4 | +| User interaction | 5.2.12.4 | +| Screen | 5.2.8.4 | +| Compare | 5.2.3.4 | +| Queue | 5.2.7.4 | + +### **4.11 Allocation of functional entities to physical locations** + +International freephone service and its optional customer features are characterized in terms of SIBs and the IN functional model. The allocation options for IN functional entities to IN generic physical entities are defined in Recommendation Q.1215. Such allocation is shown in Figure 1/Q.1215. These options include the collapsing of various combinations of FEs into single PEs, if desired. + +The allocation options of SSF FEs to specific network physical entities is shown in the following table: + +| | FE1 | FE5 | +|--------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------| +| Scenario 1 | Originating LE | Destination LE (Note) | +| Scenario 2 | Originating TR | Destination LE (Note) | +| Scenario 3 | Originating international gateway | Destination LE (Note) | +| Scenario 4 | Originating LE | Destination PNx | +| Scenario 5 | Originating TR | Destination PNx | +| Scenario 6 | Originating international gateway | Destination PNx | +| NOTE – The called user's TE shall be directly attached to the destination LE in these scenarios. | | | + +## ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.930-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.930-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..39e0a065612701559626ee703a374b0ed4a4c7f1 --- /dev/null +++ b/marked/Q/T-REC-Q.930-199303-I_PDF-E/raw.md @@ -0,0 +1,151 @@ + + +![ITU logo: a globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.930 + +(03/93) + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 NETWORK LAYER** --- + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1) – ISDN USER-NETWORK INTERFACE LAYER 3 – GENERAL ASPECTS** + +## **ITU-T Recommendation Q.930** + +(Previously “CCITT Recommendation”) + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.930 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +## --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms “CCITT, CCIR or IFRB” or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +*Page* + +| | | | +|---|---------------------------------------------------------|---| +| 1 | General ..... | 1 | +| 2 | Structure of layer 3 Recommendations ..... | 2 | +| 3 | Interface between layer 3 and the adjacent layers ..... | 2 | + + + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1) – ISDN USER-NETWORK INTERFACE LAYER 3 – GENERAL ASPECTS** + +*(Málaga-Torremolinos, 1984; modified at Helsinki, 1993)* + +## **1 General** + +### **1.1 Introduction** + +This Recommendation describes in general terms the D-channel layer 3 functions and protocol employed across an ISDN user-network interface. Details are provided in Recommendations in the Q.930-Series and in the Q.950-Series. + +The term “layer 3” is a general term used in these Recommendations to refer to the procedures described in Recommendation Q.931 [1] and in Recommendation Q.932 [2]. The term “layer 3” does not correspond to layer 3 of the OSI protocol reference model or to layer 3 of the control plane of the ISDN protocol reference model. + +The layer 3 protocol provides the means to establish, maintain and terminate network connections across an ISDN between communicating application entities. In addition, it provides generic procedures which may be used for the invocation and operation of supplementary services. The detailed description of the layer 3 protocol in Recommendation Q.931, Recommendation Q.932 and Recommendation Q.933 [3] make use of the definition and terminology concepts of the ISDN protocol reference model given in Recommendation I.320 [4]. + +Procedures for basic call, to support a range of bearer services and teleservices are described. Recommendation Q.931 contains procedures for circuit-mode and packet-mode bearer capabilities. Recommendation Q.933 contains procedures for frame-mode bearer capabilities. Recommendation Q.939 [5] contains a detailed description of the coding of the compatibility information elements required to identify the various bearer services and teleservices. + +Recommendation Q.932 contains a number of generic protocols for the provision of supplementary services. + +The application of the functional protocol of Recommendation Q.932 to the detailed operation of each individual supplementary service will be the subject for the Recommendations in the Q.950-Series. + +### **1.2 Connection control by the user of an ISDN requires:** + +- a) application of layer 3 protocol for control of circuit-switched connections, packet-switched and/or frame-mode connections, in combination with; +- b) application of an appropriate data link layer service (supported by an appropriate physical layer service). + +Layer 3 provides to the user the functions associated with the establishment and operation of a network connection. Layer 3 makes invisible to the user how it utilizes underlying resources such as data link connections to provide a network connection. + +### **1.3 Services provided by the data link layer** + +Layer 3 utilizes functions and services provided by the data link as defined in Recommendations Q.920 [6] and Q.921 [7]. These services are summarized below: + +- a) establishment of data link connections; +- b) error-protected transmission of data; +- c) re-establishment of data link connection (indicating loss of information). + +### 1.4 Symmetry of the layer 3 protocol + +It is intended that the layer 3 protocol is fully symmetrical to enable direct user-to-user communication. + +In order to achieve this objective, several options are incorporated in Recommendation Q.931. They are described in Annex D/Q.931. + +## 2 Structure of layer 3 Recommendations + +The following is the structure of the layer 3 Recommendations: + +Q.930 – ISDN user-network interface layer 3 – General aspects + +Q.931 – ISDN user-network interface layer 3 specification for basic call control + +Q.932 – Generic procedures for the control of ISDN supplementary services + +Q.933 – Specification for frame-mode basic call control + +Q.939 – Typical DSS 1 service indicator codings for ISDN telecommunications services + +Q.950 – Supplementary service protocols – Structure and general principles + +Further supplementary service Recommendations are described in Recommendation Q.950 [8]. + +## 3 Interface between layer 3 and the adjacent layers + +### 3.1 Interface between layer 3 and data link layer + +Overview of the interface between ISDN user-network interface layer 3 and the data link layer from the view point of the data link layer is given in 2/Q.920. Primitives and primitive procedures for this interface are specified in 4/Q.921. + +### 3.2 Interface to call control + +Both basic call and supplementary service protocols interface to call control. A general view of this structure is given in Figure 1. + +![Figure 1/Q.930: Modelling of basic and supplementary services. The diagram shows two symmetrical architectures for Terminal and Exchange Call Processing. Each architecture consists of a top-level oval (Terminal/Exchange Call Processing) connected to two parallel boxes (Basic Service Protocol (Q.931) and Supp. Svc. Protocol (Facility)). These boxes connect to a horizontal bar (Q.931 Messages), which then connects to a vertical stack of two boxes (LAPD and I.430/I.431). A horizontal line at the bottom connects the I.430/I.431 boxes of both architectures.](a9ed452e3e099e1505f7b9ad182a11e9_img.jpg) + +The diagram illustrates the modelling of basic and supplementary services in two symmetrical architectures: Terminal Call Processing and Exchange Call Processing. Each architecture is represented by a vertical stack of components. At the top is an oval labeled 'Terminal Call Processing' (left) or 'Exchange Call Processing' (right). Below this oval are two rectangular boxes: 'Basic Service Protocol (Q.931)' and 'Supp. Svc. Protocol (Facility)'. These two boxes are connected to a horizontal bar labeled 'Q.931 Messages'. Below the 'Q.931 Messages' bar is a rectangular box labeled 'LAPD'. At the bottom is a rectangular box labeled 'I.430/I.431'. A horizontal line at the very bottom connects the 'I.430/I.431' boxes of both architectures, indicating a shared interface or connection. + +Figure 1/Q.930: Modelling of basic and supplementary services. The diagram shows two symmetrical architectures for Terminal and Exchange Call Processing. Each architecture consists of a top-level oval (Terminal/Exchange Call Processing) connected to two parallel boxes (Basic Service Protocol (Q.931) and Supp. Svc. Protocol (Facility)). These boxes connect to a horizontal bar (Q.931 Messages), which then connects to a vertical stack of two boxes (LAPD and I.430/I.431). A horizontal line at the bottom connects the I.430/I.431 boxes of both architectures. + +T1143260-92/d01 + +FIGURE 1/Q.930 + +Modelling of basic and supplementary services + +### 3.3 Abbreviations used in Recommendations Q.930(I.450) and Q.931(I.451) + +See list at the end of Recommendation Q.931. + +## References + +- [1] CCITT Recommendation *ISDN user-network interface layer 3 specification for basic call control*, Rec. Q.931(I.451). +- [2] CCITT Recommendation *Generic procedures for the control of ISDN supplementary services*, Rec. Q.932(I.452). +- [3] CCITT Recommendation *Digital subscriber Signalling System No. 1 (DSS 1) – Signalling specification for frame mode basic call control*, Rec. Q.933. +- [4] CCITT Recommendation *ISDN protocol reference model*, Rec. I.320. +- [5] CCITT Recommendation *Typical DSS 1 service indicator codings for ISDN telecommunications services*, Rec. Q.939. +- [6] CCITT Recommendation *ISDN user-network interface data link layer – General aspects*, Rec. Q.920(I.440). +- [7] CCITT Recommendation *ISDN user-network interface data link layer specification*, Rec. Q.921(I.441). +- [8] CCITT Recommendation *Supplementary services protocols – Structure and general principles*, Rec. Q.950. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.941-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.941-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8d25d862104396c112202f4084bd9790bf0b4bbf --- /dev/null +++ b/marked/Q/T-REC-Q.941-199303-I_PDF-E/raw.md @@ -0,0 +1,432 @@ + + +![ITU logo: a globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.941** + +(03/93) + +**DIGITAL SUBSCRIBER SIGNALLING +SYSTEM No. 1 (DSS 1)** + +--- + +**DIGITAL SUBSCRIBER SIGNALLING +SYSTEM No. 1 (DSS 1) – ISDN USER- +NETWORK INTERFACE PROTOCOL +PROFILE FOR MANAGEMENT** + +**ITU-T Recommendation Q.941** + +(Previously “CCITT Recommendation”) + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.941 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +# --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms “CCITT, CCIR or IFRB” or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|-----------------------------------------------------------------|-------------| +| 1 General ..... | 1 | +| 1.1 Scope ..... | 1 | +| 1.2 Abbreviations and symbols..... | 2 | +| 1.3 Terms ..... | 2 | +| 2 ISDN user-network management profile: overview..... | 2 | +| 3 Physical layer profile..... | 2 | +| 3.1 Basic rate physical layer ..... | 2 | +| 3.2 Primary rate physical layer ..... | 2 | +| 4 Data link layer profile ..... | 3 | +| 5 Network layer profile ..... | 3 | +| 5.1 Use of the extended facility information element..... | 4 | +| 5.2 Call independent management procedures ..... | 4 | +| 5.3 Call associated management procedures..... | 4 | +| 6 Convergence function ..... | 4 | +| 6.1 Mapping..... | 5 | +| 7 Application layer ..... | 5 | +| 7.1 Association control ..... | 6 | +| 7.2 Remote operations ..... | 6 | +| 7.3 Common management information service ..... | 7 | +| 7.4 System management application service element (SMASE)..... | 7 | +| 7.5 Syntax and encoding..... | 7 | +| 8 Conformance ..... | 7 | +| Annex A – Example of APDU mapping to Q.931/Q.932 messages ..... | 8 | +| References ..... | 8 | + + + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1) – ISDN USER-NETWORK INTERFACE PROTOCOL PROFILE FOR MANAGEMENT** + +*(Melbourne, 1988; modified at Helsinki, 1993)* + +# **1 General** + +This Recommendation is one of a series of Recommendations describing the model, protocol profile and the communications capabilities in support of management and maintenance functions to be provided at the ISDN user-network interface. + +This Recommendation describes the protocol profile employed in providing management information transfer capabilities at the ISDN user-network interface. The overall management architecture, communications paths and service requirements are specified in Recommendation Q.940 [1]. These protocols can be used on the D-channel of both the basic and primary rate interface structures and across both reference points S and T, and are based on the DSS 1 messages. Because these messages are transferred between a network node and the directly connected users, these protocols only have local significance at the user-network interface. If management information transfer is end-to-end between a user and a remote OS, mapping in the network node has to be provided. + +Other Recommendations in this series specify the procedures and protocol associated with specific management functions that are provided at the ISDN user-network interface. + +The protocols and procedures described in these Recommendations provide the means to support management functions at the ISDN user-network interface. In particular, these management functions “provided by the ISDN user-network interface” should “enable the network node or network user” to support the activities of the Telecommunications Management Network (TMN) and support specific requirements such as those expressed in the I.600-Series [2] Recommendations (Subscriber access and installation maintenance). These protocols make the local control of these management functions possible, e.g. the control of loopbacks and diagnostic tests, the initiation and termination of event reports, etc. + +NOTE – The means by which file transfer capability is to be provided on the ISDN primary rate access is for further study. + +## **1.1 Scope** + +This Recommendation specifies the application protocol and the use of the layer 1-3 protocols at the ISDN user-network interface in providing management capabilities. The protocols defined in this Recommendation are suitable for management interactions involving transaction type information exchanges. + +NOTE – The means of providing file transfer capabilities at the local access is for further study. + +Specifically, this Recommendation defines the following: + +- a) the layer services for layers 1-3 and the application layer; +- b) the protocols for layers 1-3 and the application layer; +- c) the convergence function required to allow the application layer to interface directly with layer 3; and +- d) the conformance requirements to be met by a system claiming to implement the management protocol profile for the ISDN user-network interface. + +This Recommendation does not: + +- a) define the structure or meaning of the management information that is transmitted by means of these protocols; +- b) specify the manner in which management is accomplished as a result of the protocol exchanges; + +- c) define the nature of any interactions which result in the use of the application layer protocol; and +- d) define the nature of any implementation intended to provide the ISDN management function. + +## **1.2 Abbreviations and symbols** + +### **1.2.1 Abbreviations** + +| | | +|-------|-----------------------------------------------| +| ACSE | Association Control Service Element | +| ASN.1 | Abstract Syntax Notation One | +| CMISE | Common Management Information Service Element | +| CMIP | Common Management Information Protocol | +| ROSE | Remote Operation Service Element | +| SMASE | System Management Application Service Element | + +## **1.3 Terms** + +To be provided. + +# **2 ISDN user-network management profile: overview** + +The ISDN user-network management profile is based on CCITT ISDN Recommendations for the D-channel layers 1-3 protocols and on ISO standards and CCITT Recommendations for the management application layer. To allow the management application layer to access the network layer interface a convergence function has been defined. The architecture of the resulting profile is shown in Figure 1. The ISDN user-network interface management protocols make use of the D-channel. + +# **3 Physical layer profile** + +The ISDN user-network management protocol utilizes the D-channel of either the primary or basic rate interface. + +## **3.1 Basic rate physical layer** + +Management information is transmitted on the 16 kbit D-channel of the basic rate interface. + +The service and protocol definition for the physical layer shall apply as defined in Recommendation I.430 [3]. + +The default values of all parameters shall be the values specified in Recommendation I.430. + +The interface connector shall comply with ISO 8877 [4]. + +## **3.2 Primary rate physical layer** + +Management information is transmitted on the 64 kbit D-channel of the primary rate interface. + +The service and protocol definition for the physical layer shall apply as defined in Recommendation I.431. + +The default values of all parameters shall be the values specified in Recommendation I.431 [5]. + +The interface connector and interface wiring shall comply with 6/I.431 and 7/I.431, respectively. + +![Diagram of the ISDN user-network interface management profile showing protocol layers and functions.](fc46871d72c65d3381d9201646d23439_img.jpg) + +``` + +graph TD + subgraph Management_Profile [Management Profile] + SMASE[SMASE] + ACSE[ACSE] + CMISE[CMISE] + ROSE[ROSE] + SMASE --- ACSE + SMASE --- CMISE + CMISE --- ROSE + end + + subgraph Network_Layers [Network Layers] + CF[Convergence function] + L3[Layer 3 +Q.931 and Q.932] + L2[Layer 2 +Q.921] + L1[Layer 1 +I.430 or I.431] + end + + Management_Profile --- CF + CF --- L3 + L3 --- L2 + L2 --- L1 + +``` + +The diagram illustrates the ISDN user-network interface management profile. It is structured into two main sections: a management profile at the top and network layers below. The management profile includes SMASE at the top, which connects to ACSE and CMISE. CMISE further connects to ROSE. Below this, the network layers are stacked: a Convergence function layer, followed by Layer 3 (Q.931 and Q.932), Layer 2 (Q.921), and Layer 1 (I.430 or I.431). + +Diagram of the ISDN user-network interface management profile showing protocol layers and functions. + +T1155600-93/d01 + +FIGURE 1/Q.941 +ISDN user-network interface management profile + +# 4 Data link layer profile + +Local management information shall be transmitted on the D-channel and shall use the same SAPI as for call control procedures, i.e. SAPI 0. + +The data link layer service and protocol definition shall apply as defined in Recommendation Q.921. + +Default values for all parameters shall be as specified in 5.9/Q.921 [6]. + +# 5 Network layer profile + +The network layer service and protocol definition shall be in accordance with Recommendations Q.931 [7] and Q.932 [8]. + +Default values for layer 3 parameters shall apply as defined in Table 9/Q.931. + +In addition to Q.931 messages, to support the management profile the ISDN access shall also support the following Q.932 messages: + +- FACILITY, +- REGISTER. + +In addition the ISDN access shall also support the extended facility information element specified in Recommendation Q.932, in these Q.931 and Q.932 messages as specified in those Recommendations. + +The extended facility information element may carry information with a length longer than 255 octets in its PDU field. Management services which utilize layer 3 messages with a length exceeding N201 (defined in Recommendation Q.921) shall support Annex H/Q.931, Message segmentation procedures. The default maximum number of message segments supported by Annex H/Q.931 is eight. Thus the maximum length of the application protocol data unit (APDU) which may be carried by an extended facility information element is approximately 2000 octets1). + +## 5.1 Use of the extended facility information element + +The extended facility information element is used to convey application protocol data units (APDUs). To indicate that a management service has been invoked the protocol profile is used with the following encoding: + +### Protocol profile + +| Bits | 5 | 4 | 3 | 2 | 1 | | +|------|---|---|---|---|---|-------------------| +| | 1 | 0 | 0 | 1 | 0 | for CMIP Protocol | +| | 1 | 0 | 0 | 1 | 1 | for ACSE Protocol | + +## 5.2 Call independent management procedures + +For management procedures invoked independent of an active call, once a data link connection has been established, the user or the network start the establishment of a signalling connection (and management association) by transferring a REGISTER message across the user-network interface. The signalling connection (and management association) is identified by the call reference allocated with the REGISTER message. The REGISTER message shall contain an extended facility information element which will carry the information for requesting to establish the management association. + +Management service requests are conveyed in the extended facility information elements in the FACILITY messages. + +The signalling connection (and management association) is released by means of a RELEASE COMPLETE message. The RELEASE COMPLETE message shall contain an extended facility information element which will carry the information for orderly release of the management association. + +If the protocol profile in the extended facility information element indicates “CMIP Protocol” or “ACSE Protocol” then the information in the extended facility information element is passed to the management entity for further processing. + +NOTE – The term “management entity” as used here refers to the convergence function and protocol entities that process management information. + +If an extended facility information element contains more than one PDU, these PDUs are treated as separate PDUs and no assumption can be made about the order in which they will be processed. + +## 5.3 Call associated management procedures + +When management information is exchanged in association with an existing call the management information may be carried in any Q.931 or Q.932 message that contains an extended facility information element. + +NOTE – Further study is required to determine the actions to be taken when either the call control process attempts to release the connection or when the management application process attempts to release the connection (e.g. due to attempted security violations or errors in the extended facility information element). + +# 6 Convergence function + +The convergence function is required to support the mapping service. + +1) The exact length is determined by $N201 \times 8$ – layer 3 headers. + +## **6.1 Mapping** + +The mapping service is required to map the P-DATA, P-CONNECT, P-RELEASE and P-U-ABORT services onto appropriate network services and Q.931/Q.932 messages. + +### **6.1.1 Mapping of the P-DATA service** + +P-DATA-requests issued by the management entity shall have their user data mapped into the PDU field of the extended facility information element of a message. The protocol profile shall be set to the value indicating CMIP Protocol. + +PDU received by the convergence function shall be mapped into the user data field of a P-DATA-indication. + +### **6.1.2 Mapping of the P-CONNECT service** + +P-CONNECT-requests issued by the management entity shall be mapped onto the REGISTER message. Only the user data parameter of the P-CONNECT-request is required. If any other parameters are present, they shall be ignored. For information on when the P-CONNECT-request is used see 7.1.3. + +The first response received shall be mapped onto the P-CONNECT-confirmation. Only the user data parameter of the P-CONNECT-confirmation is required. If any other parameters are present, they shall be ignored. A RELEASE COMPLETE message shall result in a negative indication and contain a negative AARE APDU in its user data field. A FACILITY message shall result in a positive confirmation containing a positive AARE APDU in its user data field. + +The protocol profile in the extended facility information element shall be set to the value indicating ACSE Protocol. + +### **6.1.3 Mapping of the P-RELEASE service** + +P-RELEASE-requests issued by the management entity shall be mapped onto a FACILITY message. For information on when the P-RELEASE-request is used see 7.1.3. + +A RELEASE COMPLETE message received by the convergence function shall be mapped onto a P-RELEASE-confirmation with a RLRE APDU in the user data. + +The protocol profile in the extended facility information element shall be set to the value indicating ACSE Protocol. + +### **6.1.4 Mapping of the P-U-ABORT service** + +P-U-ABORT-requests issued by the management entity shall be mapped onto a RELEASE COMPLETE message. A RELEASE COMPLETE message received by the convergence function shall be mapped onto a P-U-ABORT-indication with an ABRT APDU in the user data. + +The protocol profile in the extended facility information element shall be set to the value indicating ACSE Protocol. + +# **7 Application layer** + +The application layer provides transaction type management across the ISDN user-network interface. To provide this capability the following application service elements are used: + +ACSE Association Control Service Element + +CMISE Common Management Information Service Element + +ROSE Remote Operation Service Element + +## **7.1 Association control** + +Version 1 of the ACSE protocol shall be used. For ISDN local management, the Q.931 call reference value is used to identify the Q.931 connection and the management association, if any. Since the management association is identified, the following optional parameters in AARQ and AARE shall not be used: calling and called AP-titles, calling and called AP-invocations, calling and called AE-qualifiers, and calling and called AE-invocations: and responding AP-title, responding AP-invocation, responding AE-qualifier, and responding AE-invocation. + +### **7.1.1 Association control service** + +Association control services used shall comply with Recommendation X.217 [9]. All the A-ASSOCIATE parameters in Table 2/X.217 with a value of P with respect to request, indication, response and confirmation columns are not required in A-ASSOCIATE service primitives. If present, they shall be ignored. + +### **7.1.2 Association control service protocol** + +The association control protocol shall comply with Recommendation X.227 [10]. + +### **7.1.3 Use of Associations** + +To establish a new non-call associated management association, the A-ASSOCIATE-request is used. The request uses the P-CONNECT-request in the presentation layer. The association is established when the positive A-ASSOCIATE-confirmation is received. The confirmation uses the P-CONNECT-confirmation in the presentation layer. + +To exchange call associated management information on an existing connection, the A-ASSOCIATE-request shall not be used. Instead the appropriate CMISE operation shall be invoked. The SMISE services use the P-DATA in the presentation layer. + +When management information is exchanged in conjunction with Q.931 call establishment, the A-ASSOCIATE-request shall not be used. Instead the appropriate operation shall be conveyed in an extended facility information element contained in a SETUP message. + +To release a management association, the A-RELEASE-request is used if the association was established via an exchange of the A-ASSOCIATE-request and A-ASSOCIATE-confirmation. The A-RELEASE-request makes use of the P-RELEASE-request. The management association is orderly released when a positive A-RELEASE-confirmation is received. For a call associated management association, the management association will be cleared when the call reference is released. + +## **7.2 Remote operations** + +### **7.2.1 Remote operations service** + +The remote operations service element shall comply with Recommendation X.219 [11] with the exception that the BIND and UNBIND operations are not used in this profile. Operation Classes 2 and 5 shall be supported. Alternatively, Operation Class 1 may be supported instead of Operation Class 2. + +### **7.2.2 Remote operations protocol** + +The remote operations protocol shall comply with Recommendation X.229 [12]. In addition support of the correct origination and reception of the linked-id protocol element is required. + +ROSE association class 3 shall be supported. + +## **7.3 Common management information service** + +### **7.3.1 Common management service** + +For this interface a simplified subset of the CMIP protocol is used. The availability of the CMIP functional units cannot be negotiated when this profile is used and shall be statically supported as follows: + +- 1) the support of multiple object selection and filter functional units by the network for the requests from the user is mandatory for both the basic and primary rate interfaces; +- 2) the support of multiple object selection and filter functional units by the user for the requests from the network is mandatory for the primary rate interface and optional for the basic rate interface; +- 3) the support of a multiple reply functional unit by both the network and the user for both the basic and primary rate interfaces is mandatory; and +- 4) the cancel-get and extended service functional units shall not be used for this profile. + +The common management information service shall comply with Recommendation X.710 [13]. + +### **7.3.2 Common management protocol** + +The common management information protocol shall comply with Recommendation X.711 [14]. Version 2 of CMIP shall be used. + +### **7.3.3 Object naming** + +The Local Distinguished Name (LDN) shall be used. + +## **7.4 System management application service element (SMASE)** + +The SMASE provides services in support of specific management functions. The details are for further study. + +## **7.5 Syntax and encoding** + +The application layer protocol data units is described by using ASN.1 as defined in Recommendation X.208 [15] and is encoded in accordance with the Basic Encoding Rules for ASN.1 as defined in Recommendation X.209 [16]. + +The procedures for encoding/decoding the EXTERNAL type shall comply with 34.5/X.208. For encoding/decoding the two ASN.1 types: CMIPUserInfo and CMIPAbortInfo, the following object identifier value is assigned. An ASN.1 object identifier value + +**{ ccitt(0) recommendation(0) q(17) q941(941) abstractSyntax(0) }** + +is assigned in this Recommendation which is the combination of + +**{ joint-iso-ccittms(9)cmip(1)abstractSyntax(4) }** + +as the abstract syntax and the Basic Encoding Rules as the transfer syntax. + +The maximum value of an ASN.1 basic encoding tag shall be limited to 16,383. + +# **8 Conformance** + +For further study. + +# Annex A + +## Example of APDU mapping to Q.931/Q.932 messages + +(This annex forms an integral part of this Recommendation) + +An example is given below to illustrate the mapping of the APDUs to the Q.931/Q.932 messages in a time sequence for a call independent management association. + +![Sequence diagram showing the mapping of APDUs to Q.931/Q.932 messages. On the left, four right-pointing arrows represent outgoing APDUs: (AARQ) REGISTER, (CMIP/ROSE) FACILITY, (CMIP/ROSE) FACILITY, and (RLRQ) FACILITY. On the right, four left-pointing arrows represent incoming Q.931/Q.932 messages: FACILITY (AARE), FACILITY (CMIP/ROSE), and RELEASE COMPLETE (RLRE). The first two outgoing APDUs map to the first two incoming messages. The third outgoing APDU maps to the third incoming message. The fourth outgoing APDU maps to the fourth incoming message. The text 'T1155610-93/d02' is located at the bottom right of the diagram.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +(AARQ) REGISTER + +FACILITY (AARE) + +(CMIP/ROSE) FACILITY + +FACILITY (CMIP/ROSE) + +(CMIP/ROSE) FACILITY + +(RLRQ) FACILITY + +RELEASE COMPLETE (RLRE) + +T1155610-93/d02 + +Sequence diagram showing the mapping of APDUs to Q.931/Q.932 messages. On the left, four right-pointing arrows represent outgoing APDUs: (AARQ) REGISTER, (CMIP/ROSE) FACILITY, (CMIP/ROSE) FACILITY, and (RLRQ) FACILITY. On the right, four left-pointing arrows represent incoming Q.931/Q.932 messages: FACILITY (AARE), FACILITY (CMIP/ROSE), and RELEASE COMPLETE (RLRE). The first two outgoing APDUs map to the first two incoming messages. The third outgoing APDU maps to the third incoming message. The fourth outgoing APDU maps to the fourth incoming message. The text 'T1155610-93/d02' is located at the bottom right of the diagram. + +# References + +- [1] CCITT Recommendation Q.940 *ISDN User-Network Interface Protocol for Management – General Aspects*. +- [2] CCITT Recommendations I.600 Series *ISDN – Inter network Interfaces and Maintenance Principles*. +- [3] CCITT Recommendation I.430 *Basic User-Network Interface – Layer 1 Specification*. +- [4] ISO 8877 Interface Connector and Contact Assignments for ISDN Basic Interface Located at Reference Points S and T. +- [5] CCITT Recommendation I.431 *Primary Rate User-Network Interface – Layer 1 Specification*. +- [6] CCITT Recommendation Q.921 *ISDN User-Network Interface-Data Link Layer Specification*. +- [7] CCITT Recommendation Q.931 *ISDN User-Network Interface Layer 3 Specification for Basic Call Control*. +- [8] CCITT Recommendation Q.932 *Generic Procedures for the Control of ISDN Supplementary Services*. +- [9] CCITT Recommendation X.217 *Open Systems Interconnection – Service Definition for Association Control Service Elements* (see also ISO 8649). +- [10] CCITT Recommendation X.227 *Open Systems Interconnection – Protocol Specification for Association Control Service Element* (see also ISO 8650). + +- [11] CCITT Recommendation X.219 *Remote Operations: Model, Notation, and Service Definition*. +- [12] CCITT Recommendation X.229 *Remote Operations: Protocol Specification*. +- [13] CCITT Recommendation X.710 *Common Management Information Service Definition* (see also ISO 9595). +- [14] CCITT Recommendation X.711 *Common Management Information Protocol [Part 1:] Specification* (see also ISO 9596-1). +- [15] CCITT Recommendation X.208 *Specification of Abstract Syntax Notation One (ASN.1)* (see also ISO 8824). +- [16] CCITT Recommendation X.209 *Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)* (see also ISO 8825). \ No newline at end of file diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7268078d896f5bfca565184f09b88647a1cd364b --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0935f46b2119ed3ea372951a62df08ce7c6b9936db253d24760166e294d70c56 +size 82551 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c977f588b33e514b3c6289f1959cdf879b98477 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:443d11dc23c7613a2b3737e10657625f8adfba1bf5b287b638b5cce0513773b0 +size 52160 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a34da7d9efbdd7d852293445e38deb4065074027 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:038f53f616d222c8448aa9214e186460849d0166bfb0d657d5f34a29f23c3ce1 +size 8280 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf171b8f1b4fb7fdcca86ec8100fe3f427355b84 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22538145812bbf698c657d9c6b4ea924fe82ee3f53ea6979962d1e73e9d7ab20 +size 77653 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..628fe88dd86f07c25e95f238d6daa62d362fef96 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab9a9811006dc47541714584c9b56a4628f86f87b961255a10c8a4cba8c7bd79 +size 76479 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e94691d736789d41d921391d7c51bedcd308855f --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1b8a14c0b7b63ee77c1afcd128ecd604dbc7eb3e28c895391f8b9c21c01f13c +size 85003 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f672b216d9e0df1a992f076d02b4dd609f103366 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad7e1c8ab64c25ae856a9f3e9328eff95c650826340256ee2dfc942ea1c63084 +size 41882 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5553de6deec57863b97ec0654e84ab7b536bca6 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:723f07bf1d4551f90decd002eec912eb24a118c70e1b5cf026b135263898126a +size 72293 diff --git a/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44d4722486815e13b5c15b1bf4410dca8f9ee5b2 --- /dev/null +++ b/marked/Q/T-REC-Q.951.4-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f48f1511f565fdc5752458fd2ef635ea664ceae3c3eaac3a0cbfdf3898e8e657 +size 71032 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7268078d896f5bfca565184f09b88647a1cd364b --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0935f46b2119ed3ea372951a62df08ce7c6b9936db253d24760166e294d70c56 +size 82551 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c977f588b33e514b3c6289f1959cdf879b98477 --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:443d11dc23c7613a2b3737e10657625f8adfba1bf5b287b638b5cce0513773b0 +size 52160 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a34da7d9efbdd7d852293445e38deb4065074027 --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:038f53f616d222c8448aa9214e186460849d0166bfb0d657d5f34a29f23c3ce1 +size 8280 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf171b8f1b4fb7fdcca86ec8100fe3f427355b84 --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22538145812bbf698c657d9c6b4ea924fe82ee3f53ea6979962d1e73e9d7ab20 +size 77653 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..628fe88dd86f07c25e95f238d6daa62d362fef96 --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab9a9811006dc47541714584c9b56a4628f86f87b961255a10c8a4cba8c7bd79 +size 76479 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e94691d736789d41d921391d7c51bedcd308855f --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1b8a14c0b7b63ee77c1afcd128ecd604dbc7eb3e28c895391f8b9c21c01f13c +size 85003 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2ce526420dd23be25b04660fcf26514ffffd1db --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:122ed946ac3b47f074d959a4b5de1d4cbcdc77e079c0be788761df3327864ebb +size 41887 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9909963daba5f66f751cb921466c1c80ed220cb --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa6a037596081df4a16ee92d055fa86f01a1d94978a6f78aad7cf91152c3770b +size 72315 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44d4722486815e13b5c15b1bf4410dca8f9ee5b2 --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f48f1511f565fdc5752458fd2ef635ea664ceae3c3eaac3a0cbfdf3898e8e657 +size 71032 diff --git a/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..913794842215e1aad7eac0166505dadc5d6249a3 --- /dev/null +++ b/marked/Q/T-REC-Q.951.5-199303-I_PDF-E/raw.md @@ -0,0 +1,1712 @@ + + +![ITU logo: a globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.951 + +(03/93) + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 STAGE 3 DESCRIPTION FOR SUPPLEMENTARY SERVICES USING DSS 1** --- + +## **STAGE 3 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES USING DSS 1** + +**Clause 3 – Calling Line Identification Presentation (CLIP)** + +**Clause 4 – Calling Line Identification Restriction (CLIR)** + +**Clause 5 – Connected Line Identification Presentation (COLP)** + +**Clause 6 – Calling Line Identification Restriction (COLR)** + +## **ITU-T Recommendation Q.951** + +(Previously “CCITT Recommendation”) + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.951, clauses 3, 4, 5 and 6 was prepared by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +# --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms “CCITT, CCIR or IFRB” or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|--------------------------------------------------------------------------------------------------------|-------------| +| 3    Calling Line Identification Presentation (CLIP) ..... | 1 | +| 3.1    Definition..... | 1 | +| 3.2    Description..... | 1 | +| 3.3    Operational requirements..... | 2 | +| 3.4    Coding requirements..... | 2 | +| 3.5    Signalling requirements..... | 2 | +| 3.6    Interaction with other supplementary services ..... | 6 | +| 3.7    Interaction with other networks ..... | 8 | +| 3.8    Signalling flows ..... | 9 | +| 3.9    Parameter values (timers) ..... | 9 | +| 3.10    Dynamic description ..... | 9 | +| Annex A (referred to in clause 3) – Two Calling party number information elements delivery option..... | 12 | +| A.1    Scope ..... | 12 | +| A.2    Additional procedures at the destination network side ..... | 12 | +| A.3    Actions at the originating user ..... | 12 | +| A.4    Additional actions at the originating local exchange ..... | 12 | +| 4    Calling Line Identification Restriction (CLIR) ..... | 13 | +| 4.1    Definition..... | 13 | +| 4.2    Description..... | 13 | +| 4.3    Operational requirements..... | 14 | +| 4.4    Coding requirements..... | 14 | +| 4.5    Signalling requirements..... | 14 | +| 4.6    Interaction with other supplementary services ..... | 15 | +| 4.7    Interaction with other networks ..... | 17 | +| 4.8    Signalling flows ..... | 17 | +| 4.9    Parameter values (timers) ..... | 17 | +| 4.10    Dynamic description ..... | 17 | +| 5    Connected Line Identification Presentation (COLP) ..... | 17 | +| 5.1    Definition..... | 17 | +| 5.2    Description..... | 17 | +| 5.3    Operational requirements..... | 19 | +| 5.4    Coding requirements..... | 19 | +| 5.5    Signalling requirements..... | 21 | +| 5.6    Interaction with other supplementary services ..... | 25 | +| 5.7    Interaction with other networks ..... | 27 | +| 5.8    Signalling flows ..... | 27 | +| 5.9    Parameter values (timers) ..... | 27 | +| 5.10    Dynamic description ..... | 27 | +| 6    Connected Line Identification Restriction (COLR) ..... | 30 | +| 6.1    Definition..... | 30 | +| 6.2    Description..... | 30 | +| 6.3    Operational requirements..... | 30 | +| 6.4    Coding requirements..... | 31 | +| 6.5    Signalling requirements..... | 31 | +| 6.6    Interaction with other supplementary services ..... | 31 | +| 6.7    Interaction with other networks ..... | 33 | +| 6.8    Signalling flows ..... | 33 | +| 6.9    Parameter values (timers) ..... | 33 | +| 6.10    Dynamic description ..... | 33 | + + + +## STAGE 3 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES USING DSS 1 + +*(Helsinki, 1993)* + +# 3 Calling Line Identification Presentation (CLIP) + +## 3.1 Definition + +**calling line identification presentation (CLIP)** is a supplementary service offered to the called party which provides the calling party's ISDN number, possibly with sub-address information to the called party. + +## 3.2 Description + +#### 3.2.1 General description + +This supplementary service provides the ability of indicating the ISDN number of the calling line, with possible additional sub-address information (i.e. the Calling party sub-address information element), to the called party. + +The information provided to the called user consists of the ISDN number of the calling user in a form sufficient to allow the returning of the call (i.e. a subscriber number, a national number or an international number and optionally a sub-address if provided by the calling user). + +#### 3.2.2 Specific terminology + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the presentation of the calling line identification information in association with incoming calls. The served user is also known as the called user. + +A **calling user** is the user that initiated an incoming call at the served user. The calling user need not have subscribed to the Calling Line Identification Presentation supplementary service. + +An **ISDN number** is a number conforming to the numbering plan structure specified in Recommendation E.164. + +An **address** is the number of the calling user (normally ISDN number), and a sub-address if provided by that user. + +An **international number** is an ISDN number structured as specified in Recommendation E.164. + +A **national number; national significant number** is an ISDN number structured as specified in Recommendation E.164. + +A **subscriber number** is an ISDN number structured as specified in Recommendation E.164. + +A **default number** is an agreed number between the user at the calling side and the network provider. + +A **special arrangement** is an arrangement between a customer and a public network operator whereby customer supplied calling numbers are not screened by the public ISDN. + +CLIP     Calling Line Identification Presentation + +CLIR     Calling Line Identification Restriction + +#### **3.2.3 Qualification on the applicability to telecommunication services** + +See Recommendation I.251.3. + +#### **3.2.4 State definitions** + +No specific state definitions are required. + +## **3.3 Operational requirements** + +#### **3.3.1 Provision/withdrawal** + +See Recommendation I.251.3. + +NOTE – Annex A contains some additional procedures to support the two Calling party number information elements delivery option. This is a network option. + +#### **3.3.2 Requirements on the originating network side** + +All information pertaining to CLIP, shall be inserted in the SETUP message sent as part of the basic call procedures according to 5/Q.931. + +In the case where no information is provided by the calling user (as part of the basic call procedures) the network shall provide the default number associated with the user access (in which the call was generated) in the originating local exchange. + +When the calling party information is provided by the user, the network can only verify that the number is within the range allocated to that user. + +Where a special arrangement exists with the calling user, no screening of the calling number they supplied, shall be performed. + +#### **3.3.3 Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **3.3.4 Requirements on the destination network side** + +See 3.5.2.3. + +### **3.4 Coding requirements** + +All information pertaining to CLIP is inserted in the SETUP message. 4.5.10/Q.931 and 4.5.11/Q.931 give the coding for the Calling party number and Calling party sub-address information elements which are required to support this service. The purpose of the Calling party number information element is to identify the origin of a call. The purpose of the Calling party sub-address information element is to identify a sub-address associated with the origin of the call. + +## **3.5 Signalling requirements** + +#### **3.5.1 Activation/deactivation/registration** + +Not applicable. + +#### **3.5.2 Invocation and operation** + +##### **3.5.2.1 Actions at the originating local exchange** + +###### **3.5.2.1.1 Normal operation** + +###### **3.5.2.1.1.1 Actions at the originating user** + +These procedures shall be provided as part of the basic service and the calling user need not have subscribed to the CLIP supplementary service. + +The numbering plan identification, to be indicated with the Calling party number information element, sent by the calling user, shall be either “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”. + +NOTE – Either coding may be used and the treatment of both by the network is identical. + +Where the calling number included by the calling user is complete the type of number to be indicated within the Calling party number information element, sent by the calling user, shall be one of the following: + +- “*Subscriber number*” – In the case where the complete subscriber number is sent. +- “*National number*” – In the case where the complete national number is sent. +- “*International number*” – In the case where the complete international number is sent. + +Where a partial calling number is included by the calling user (e.g., to indicate digits specific to the Direct-Dialling-In or the Multiple Subscriber Number supplementary services) the user shall set the type of number to be indicated within the Calling party number information element to “unknown”. + +###### **3.5.2.1.1.2 Actions at the originating local exchange if a special arrangement does not apply** + +These procedures shall be provided as part of the basic service and the calling user need not have subscribed to the CLIP supplementary service. + +When a SETUP message is received from the calling user, the network shall check to see if the Calling party number and Calling party sub-address information elements are included. + +If the Calling party number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Calling party number information element and process the call as if that information was not received. + +The network shall set the value of the screening indicator based on the outcome of the screening of the calling number. The network shall disregard any value of the screening indicator, if received from the calling user. + +If the Calling party number information element is included, the network shall perform the screening function. + +NOTE 1 – Some networks may accept a full ISDN number in a Calling party number information element with the addition of a prefix or escape digits to the number digits field and the type of number field set to “unknown”. + +If the calling number received from the calling user is determined to be correct, the network shall set the screening indicator to “user-provided, verified and passed”. + +If the screening function fails the network shall note that the screening is failed and shall use a default number associated with the calling user. The network shall set the screening indicator to “network provided”. + +If the SETUP message does not contain the Calling party number information element the network shall use a default number associated with the calling user. The network shall set the screening indicator to “network provided”. + +In the case where the calling user provides only partial calling number information and the number is a valid digit sequence for the user access arrangement, the network shall complete the number as appropriate. The network shall set the screening indicator to “user-provided, verified and passed”. + +NOTE 2 – In some cases the network cannot guarantee that the completed number identifies an end user. + +The information determined by the procedures above, shall be forwarded to the destination local exchange, in association with the basic call request. + +The presentation indicator, as determined by the procedures of the CLIR supplementary service (see clause 4), shall be forwarded to the destination local exchange, in association with the basic call request. + +If the Calling party sub-address information element is available, it shall be passed transparently through the network. + +The actions at the originating local exchange when special arrangement does not apply are summarized in Table 3-1. + +TABLE 3-1/Q.951 + +###### **Information provided by the calling user and by the network when special arrangement does not apply** + +| Information provided by the calling user | | Information provided by the network to the called user | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------| +| Calling number received from the calling user (octet 4) | Type of number (octet 3) | Calling number forwarded (if CLIR is not activated) (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No calling party number information element is provided by the calling user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 7) | +| Valid part of the number not sufficient for returning the call (Note 2) | “Unknown” | Completion of the number (Note 3) | User-provided verified and passed (Note 4) | “International number” or “national number” (Notes 1, 7) | +| Correct complete calling party number (Note 5) | “Subscriber number” or “national number” or “international number” | Complete calling party number | User-provided verified and passed | “International number” or “national number” (Notes 1, 7) | +| Incorrect number (Note 6) | Any type of number | Default number stored at the network side sufficient for returning the call | Network-provided | “International number” or “national number” (Notes 1, 7) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network path where the destination is in a different country.

2 This assumes that the user's equipment provides that part of the number pertaining to its own (private) domain. This may be multiple subscriber number digits provided by a terminal equipment or an extension line number provided by a private ISDN. The network shall interpret the number digits and check if it is a valid digit sequence according to the agreements existing between the calling user and the network provider.

3 Completion means that the remaining part of the ISDN number associated with the appropriate access is added to the user provided part of the number.

4 The term “verified” implies matching the user provided number or part of this number with the range(s) of numbers stored at the network side and it implies at least a valid format of user provided number information.

5 The term “correct” implies, from the network point of view, matching the subscriber number provided by the user with one of the numbers in the set of numbers stored at the network side.

6 The number provided by the user is discarded.

7 As a network option the type of number forwarded to the called user may be coded “unknown” when a prefix is added to the number, in which case the number is organized according to the network dialling plan, i.e. prefixes or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +###### 3.5.2.1.1.3 Actions at the originating local exchange if a special arrangement applies + +These procedures shall be provided as part of the basic service and the calling user need not have subscribed to the CLIP supplementary service. + +When a SETUP message is received from the calling user, the network shall check to see if the Calling party number and Calling party sub-address information elements are included. + +If the Calling party number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Calling party number information element and process the call as if that information element was not received. + +If the Calling party number information element is received with the coding of the type of number field other than “national number” or “international number”, then the network shall discard the Calling party number information element and process the call as if that information element was not received. + +The network shall disregard any value of the screening indicator, if received from the calling user. + +If the SETUP message does not contain the Calling party number information element the network shall use a default number associated with the calling user. The network shall set the screening indicator to “network provided”. + +If the Calling party number information element is included the network shall set the screening indicator to “user-provided, not screened”. + +NOTE – For the above condition, the procedures of basic call will provide for another calling number to be transported through the network. This other calling number will contain the default number, with an associated screening indicator set to “network provided”. + +The information determined by the procedures above, shall be forwarded to the destination local exchange, in association with the basic call request. + +The presentation indicator, as determined by the procedures of the CLIR supplementary service (see clause 4) shall be forwarded to the destination local exchange, in association with the basic call request. + +If the Calling party sub-address information element is available, it shall be passed transparently through the network. + +The actions at the originating local exchange when special arrangement applies are summarized in Table 3-2. + +TABLE 3-2/Q.951 + +###### **Information provided by the calling user and by the network when special arrangement applies** + +| Information provided by the calling user | | Information provided by the network to the called user | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------|----------------------------------------------------------| +| Calling party number received from the calling user (octet 4) | Type of number (octet 3) | Calling party number forwarded (if CLIR is not activated) (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No calling party number information element is provided by the calling user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 2) | +| Any digit sequence conforming to E.164 | “National number” or “international number” | Number provided by the user (Note 1) | User-provided, not screened | “International number” or “national number” (Notes 1, 2) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network path where the destination is in a different country.

2 As a network option the type of number forwarded to the called user may be coded “unknown” when a prefix is added to the number, in which case the number is organized according to the network dialling plan, i.e. prefixes or the absence of prefixes, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +###### 3.5.2.1.2 Exceptional procedures + +Not applicable. + +#### **3.5.2.2 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **3.5.2.3 Actions at the destination local exchange** + +###### **3.5.2.3.1 Normal operation** + +When the network sends a SETUP message to the called user and if the called user is provided with the CLIP supplementary service, the network shall check to see if the calling number is available. + +If the calling number is available and presentation is allowed according to the presentation indicator supplied together with the calling number, the network shall include the Calling party number information element in the SETUP message sent to the called user. If provided, the network shall also include the Calling party sub-address information element in the SETUP message. The presentation and screening indicators associated with the calling number, and the calling sub-address, received at the destination exchange, shall be passed transparently to the called user. + +The numbering plan identification field shall be coded either “ISDN/telephony numbering plan” (see Recommendation E.164)” or “unknown”. + +If presentation is not allowed according to the presentation indicator supplied together with the calling number, the network shall include the Calling party number information element in the SETUP message sent to the called user. The presentation indicator in the Calling party number information element shall indicate “presentation restricted”. The network shall encode the screening indicator, numbering plan identification and the type of number according to one of the following options: + +- i) The screening indicator shall indicate “network provided”. The type of number and numbering plan identification shall be set to “unknown”. +- ii) The screening indicator, numbering plan identification and the type of number shall be as received at the destination network. + +The network shall not include digits field. The network shall not include the Calling party sub-address information element in the SETUP message. + +If neither the calling number nor an indication that presentation is restricted is available at the destination local exchange the network shall include the Calling party number information element in the SETUP message sent to the called user. The presentation indicator shall be set to “number not available due to interworking”, and the screening indicator shall be set to “network provided”, the type of number and the numbering plan identification shall be set to “unknown” and the number digits field shall not be included. The network shall not include the Calling party sub-address information element, if provided, in the SETUP message. + +If the called user is not provided with the CLIP supplementary service, then neither the Calling party number nor the Calling party sub-address information elements shall be included in the SETUP message sent to the called user. + +If presentation is restricted but as a national network option the called user has the “override” category (e.g., police or emergency service) marked in the destination local exchange, the network shall include the Calling party number information element, and Calling party sub-address information element if the sub-address was supplied by the calling party in the SETUP message. In this case, the presentation and screening indicators shall be passed transparently to the called user. + +NOTE – If the presentation indicator in the Calling party number information element received by the user is set to “number not available due to interworking” or “presentation restricted”, the remaining information in the Calling party number information element should be ignored by the user. + +###### **3.5.2.3.2 Exceptional procedures** + +Not applicable. + +### **3.6 Interaction with other supplementary services** + +#### **3.6.1 Call Waiting** + +No interaction. + +#### **3.6.2 Call Transfer** + +No interaction. + +#### **3.6.3 Connected Line Identification Presentation** + +No interaction. + +#### **3.6.4 Connected Line Identification Restriction** + +No interaction. + +#### **3.6.5 Calling Line Identification Presentation** + +No interaction. + +#### **3.6.6 Calling Line Identification Restriction** + +The calling line identification will not be presented if the calling user has an arrangement to inhibit the presentation of his number(s) to the called party (calling user subscribes to the supplementary service “Calling Line Identification Restriction”). The only occasion when a user subscribing to CLIP can take precedence over CLIR is when the CLIP served user has an override category. This is a national option. + +#### **3.6.7 Closed User Group** + +No interaction. + +#### **3.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **3.6.9 Direct-Dialling-In** + +No interaction. + +#### **3.6.10 Call diversion (call forwarding) services** + +##### **3.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **3.6.10.2 Call Forwarding No Reply** + +As specified in 3/Q.952. + +##### **3.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +##### **3.6.10.4 Call Deflection** + +As specified in 5/952. + +#### **3.6.11 Line Hunting** + +No interaction. + +#### **3.6.12 Three-Party Service** + +No interaction. + +#### **3.6.13 User-to-User Signalling** + +##### **3.6.13.1 Service 1** + +No interaction. + +##### **3.6.13.2 Service 2** + +No interaction. + +##### **3.6.13.3 Service 3** + +No interaction. + +#### **3.6.14 Multiple Subscriber Number** + +Upon call initiation, if the ISDN number indicated by the MSN user terminal is not subscribed to for the interface, or if no numbering information is indicated, a default number or a number unavailable indication is provided to the CLIP user. + +#### **3.6.15 Call Hold** + +No interaction. + +#### **3.6.16 Advice of charge** + +No interaction. + +#### **3.6.17 Sub-addressing** + +No interaction. + +#### **3.6.18 Terminal Portability** + +No interaction. + +#### **3.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **3.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **3.6.21 Reverse Charging** + +No interaction. + +#### **3.6.22 Multilevel Precedence and Preemption** + +No interaction. + +### **3.7 Interaction with other networks** + +#### **3.7.1 Interaction with non-ISDNs** + +On calls incoming from some non-ISDNs, the calling number may be delivered to the destination ISDN without an indication of calling line identity restriction. In this case a number of options exist and the selection of the following is according to the network rules and regulations: + +- The network shall send the Calling party number information element according to 3.5.2.3.1, sixth paragraph, and shall include no Calling party sub-address information element. +- The network shall send the Calling party number information element according to 3.5.2.3.1, fourth paragraph, and shall include no Calling party sub-address information element. +- The network shall send the Calling party number information element according to 3.5.2.3.1, second paragraph, and shall include the Calling party sub-address information element if the calling sub-address is available. + +For some other non-ISDNs, no complete calling number may be available to the ISDN and therefore the full number of the calling user cannot be given to the called user who has been provided with the CLIP supplementary service. In this case the network shall send the Calling party number information element according to 3.5.2.3.1, sixth paragraph, and shall include no Calling party sub-address information element. + +On calls incoming from some non-ISDNs, the calling number may be delivered to the destination ISDN with an indication of Calling Line Identity Restriction. In this case the network shall send the Calling party number information element according to 3.5.2.3.1, second paragraph, and shall include the Calling party sub-address information element if the calling sub-address is available. + +As a network option the originating network may restrict any address information identifying the calling user from being forwarded to another network. + +#### **3.7.2 Procedures for interworking with private ISDNs** + +The procedures specified in 3.5.2 shall be used. + +NOTE – The provision of the special arrangement where an access is used by a private network is especially appropriate. + +### **3.8 Signalling flows** + +The signalling flows are not included as they are an integral part of the basic call control procedures. + +### **3.9 Parameter values (timers)** + +No specific timers are required. + +### **3.10 Dynamic description** + +See Figures 3-1 and 3-2. + +![Flowchart for Originating network side dynamic description (FIGURE 3-1/Q.951). The process starts with a 'Null 0' terminal, followed by a 'SETUP' message. A decision diamond asks 'CPN IE provided by the calling user?'. If 'No', it goes to 'Default number set SI = 11'. If 'Yes', it goes to another decision diamond 'Special arrangement?'. If 'Yes' to 'Special arrangement?', it goes to 'Set SI = 00'. If 'No', it goes to a third decision diamond 'Verification of the number?'. If 'OK', it goes to 'Complete the number set SI = 01'. If 'Not OK', it goes to 'Default number set SI = 11'. All three paths (SI = 11, SI = 01, and SI = 00) merge at a junction, followed by 'CLIR Service', 'Set type of number and numbering plan', 'Setup indication', and finally 'Call initiated 1' terminal.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph TD + Start([Null 0]) --> Setup[SETUP] + Setup --> CPN{CPN IE provided by the calling user?} + CPN -- No --> SI11_1[Default number set SI = 11] + CPN -- Yes --> Special{Special arrangement?} + Special -- Yes --> SI00[Set SI = 00] + Special -- No --> Verification{Verification of the number?} + Verification -- OK --> SI01[Complete the number set SI = 01] + Verification -- Not OK --> SI11_2[Default number set SI = 11] + SI11_1 --> Merge(( )) + SI01 --> Merge + SI11_2 --> Merge + SI00 --> Merge + Merge --> CLIR[CLIR Service] + CLIR --> SetType[Set type of number and numbering plan] + SetType --> SetupInd[Setup indication] + SetupInd --> End([Call initiated 1]) + +``` + +T1158670-94/d01 + +Flowchart for Originating network side dynamic description (FIGURE 3-1/Q.951). The process starts with a 'Null 0' terminal, followed by a 'SETUP' message. A decision diamond asks 'CPN IE provided by the calling user?'. If 'No', it goes to 'Default number set SI = 11'. If 'Yes', it goes to another decision diamond 'Special arrangement?'. If 'Yes' to 'Special arrangement?', it goes to 'Set SI = 00'. If 'No', it goes to a third decision diamond 'Verification of the number?'. If 'OK', it goes to 'Complete the number set SI = 01'. If 'Not OK', it goes to 'Default number set SI = 11'. All three paths (SI = 11, SI = 01, and SI = 00) merge at a junction, followed by 'CLIR Service', 'Set type of number and numbering plan', 'Setup indication', and finally 'Call initiated 1' terminal. + +## NOTES + +- 1 This procedure operates independently from any CLIP subscription by the calling user and is provided as part of the basic service. +- 2 The screenings indicator encodings are: + SI = 11 Network provided + SI = 01 User provided verified and passed + SI = 00 User provided not screened. + +FIGURE 3-1/Q.951 +**Originating network side dynamic description** + +![Flowchart for Destination network side dynamic description (Recommendation Q.951). The process starts with a 'Null 0' start node, followed by a 'Setup request' input. A decision 'User subscribed to CLIP?' branches into 'No' (leading to 'No CPN IE is sent to the called user') and 'Yes' (leading to 'CPN IE available?'). 'CPN IE available?' branches into 'Yes' (leading to 'Presentation allowed?') and 'No' (leading to 'CPN IE without number digits (Note)'). 'Presentation allowed?' branches into 'No' (leading to 'Override?') and 'Yes' (leading to 'Send CPN IE as received'). 'Override?' branches into 'No' (leading to 'CPN IE without number digits') and 'Yes' (leading to 'Send CPN IE as received'). All four paths converge at a join point before the 'SETUP' output, which leads to a 'Call present 6' end node. The reference 'T1130140-91/d02' is at the bottom.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph TD + Start([Null +0]) --> SetupReq[/Setup +request/] + SetupReq --> UserSubscribed{User +subscribed +to CLIP?} + UserSubscribed -- No --> NoCPNIE[No CPN IE is sent +to the called user] + UserSubscribed -- Yes --> CPNIEAvailable{CPN IE +available?} + CPNIEAvailable -- Yes --> PresentationAllowed{Presentation +allowed?} + CPNIEAvailable -- No --> CPNIEWithoutDigitsNote[CPN IE without +number digits +(Note)] + PresentationAllowed -- No --> Override{Override?} + PresentationAllowed -- Yes --> SendCPNIE[Send CPN IE as +received] + Override -- No --> CPNIEWithoutDigits[CPN IE without +number digits] + Override -- Yes --> SendCPNIE + NoCPNIE --> Join(( )) + CPNIEWithoutDigits --> Join + SendCPNIE --> Join + CPNIEWithoutDigitsNote --> Join + Join --> SETUP[/SETUP/] + SETUP --> End([Call +present +6]) + +``` + +T1130140-91/d02 + +Flowchart for Destination network side dynamic description (Recommendation Q.951). The process starts with a 'Null 0' start node, followed by a 'Setup request' input. A decision 'User subscribed to CLIP?' branches into 'No' (leading to 'No CPN IE is sent to the called user') and 'Yes' (leading to 'CPN IE available?'). 'CPN IE available?' branches into 'Yes' (leading to 'Presentation allowed?') and 'No' (leading to 'CPN IE without number digits (Note)'). 'Presentation allowed?' branches into 'No' (leading to 'Override?') and 'Yes' (leading to 'Send CPN IE as received'). 'Override?' branches into 'No' (leading to 'CPN IE without number digits') and 'Yes' (leading to 'Send CPN IE as received'). All four paths converge at a join point before the 'SETUP' output, which leads to a 'Call present 6' end node. The reference 'T1130140-91/d02' is at the bottom. + +NOTE – In this case SI = 11 and PI = 10. + +FIGURE 3-2/Q.951 +Destination network side dynamic description + +## **Annex A** (referred to in clause 3) + +### **Two Calling party number information elements delivery option** + +### **A.1 Scope** + +This annex specifies additional procedures to be supported for the delivery of two Calling party number information elements to the served user. The support of these procedures (or of a part of these) is a network option. + +These additional features shall have no impact and shall place no requirement whatsoever on the provision and operation of the CLIP supplementary service defined in this Recommendation by public ISDNs that do not support these additional features, nor on the interchangeability of terminals. + +### **A.2 Additional procedures at the destination network side** + +The procedures described in this annex pertain to networks capable of delivering two numbers to the called user. + +#### **A.2.1 Normal operation** + +The procedures described in 3.5.2.3.1 apply in the following situations: + +- a) only a single number is available for delivery at the terminating exchange; +- b) presentation is restricted; +- c) the called user is not provided with the CLIP supplementary service; +- d) if the subscription option to two number delivery exists and the called user has not subscribed to two number delivery. + +When two numbers are available at the terminating exchange with screening indicators of one set to “network provided” and the other set to “user provided not screened”, the network shall deliver the information in two Calling party number information elements sent in a SETUP message to the called user. + +In addition, for some networks, when two numbers are available at the terminating exchange with screening indicators of one set to “network provided” and the other set to “user-provided, verified and failed”, the network shall deliver the information in two Calling party number information elements sent in a SETUP message to the called user. + +The order in which the Calling party number information elements appear in the SETUP message is a network option. + +If provided, the network shall also include the Calling party sub-address information element in the SETUP message. The presentation and screening indicators associated with the calling number, and the calling sub-address, received at the destination exchange, shall be passed transparently to the called user. + +#### **A.2.2 Exceptional procedures** + +Not applicable. + +### **A.3 Actions at the originating user** + +Actions at the originating user are as described in 3.5.2.1.1.1. + +### **A.4 Additional actions at the originating local exchange** + +The procedures of 3.5.2.1.1.2 shall apply except in the case where the screening function fails. + +When the screening function fails, the network shall set the screening indicator to “user-provided, verified and failed”. + +NOTE – For the above condition, the procedures of basic call will provide for another calling number to be transported through the network. This other calling number will contain the default number with an associated screening indicator set to “network provided”. + +The information determined by the procedures above shall be forwarded to the destination local exchange in association with the basic call request. + +The presentation indicator, as determined by the procedures of the CLIR supplementary service (see clause 4) shall be forwarded to the destination local exchange in association with the basic call request. + +If the Calling party sub-address information element is available, it shall be passed transparently through the network. + +The actions at the originating local exchange when screening fails are summarized in Table A.1. + +TABLE A-1/Q.951 + +#### **Information provided by the calling user and by the network when screening fails** + +| Information provided by the calling user | | Information provided by the network to the called user | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------|------------------------------------|----------------------------------------------------------------------------| +| Any digit sequence conforming to E.164 | “Unknown number”, “national number” or “international number” | Number provided by the user (Note 1) | User-provided, verified and failed | “Unknown number”, “international number” or “national number” (Notes 1, 2) | +| NOTES
1 A national number shall be converted to an international number at some point in the public network path where the destination is in a different country.
2 As a network option the type of number forwarded to the called user may be coded “unknown” when a prefix is added to the number, in which case the number is organized according to the network dialling plan, i.e. prefixes or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other. | | | | | + +## 4 Calling Line Identification Restriction (CLIR) + +### 4.1 Definition + +**calling line identification restriction (CLIR)** is a supplementary service offered to the calling party to restrict presentation of the calling party’s ISDN number and sub-address to the called party. + +### 4.2 Description + +#### 4.2.1 General description + +When CLIR is applicable and activated the originating network shall provide the destination network with an indication that the calling user’s ISDN number and sub-address (if provided by the calling user) are not allowed to be presented to the called user. In this case no calling user number and sub-address shall be included in the call offered to the called user. + +The presentation restriction function shall not influence the forwarding of the calling party number within the network as part of the basic service procedures. + +#### 4.2.2 Specific terminology + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the restriction of the calling line identification information (on a permanent or on a per-call basis) in association with outgoing calls. The served user is also known as the calling user. + +A **called user** is the receiver of a call, initiated by the served user, on which CLIR has been activated. + +An ISDN number is a number conforming to the numbering plan and structure specified in Recommendation E.164. + +CLIP     Calling Line Identification Presentation + +CLIR     Calling Line Identification Restriction + +#### **4.2.3     Qualification on the applicability to telecommunication services** + +See Recommendation I.251.4. + +#### **4.2.4     State definition** + +No specific states are required. + +### **4.3     Operational requirements** + +#### **4.3.1     Provision/withdrawal** + +See Recommendation I.251.4 + +#### **4.3.2     Requirements on the originating network side** + +All information pertaining to CLIR is inserted in the SETUP message sent as part of the basic call procedures according to Recommendation Q.931. + +#### **4.3.3     Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **4.3.4     Requirements on the destination network side** + +See 4.5.2.3. + +### **4.4     Coding requirements** + +The same as for 3.4. + +### **4.5     Signalling requirements** + +#### **4.5.1     Activation/deactivation/registration** + +Not applicable. + +#### **4.5.2     Invocation and operation** + +#### **4.5.2.1     Actions at the originating user** + +If the calling user wishes to override the default setting in the network, the SETUP message sent by the user shall contain the Calling party number information element with the presentation indicator set appropriately. + +#### **4.5.2.2     Actions at the originating local exchange** + +###### **4.5.2.2.1     Normal operation** + +If the calling user has subscribed to the Calling Line Identification Restriction supplementary service permanent mode, the presentation indicator received in the SETUP message will be ignored. The network shall set the presentation indicator to "presentation restricted". + +If the calling user has subscribed to the CLIR supplementary service on a per-call basis and requests to override the default setting, the originating network shall set the presentation indicator according to that in the received Calling party number information element. + +The number digits, if included, shall be treated according to Table 3-1 or Table 3-2, and 3.5.2.1.1. + +If the CLIR is requested by the user on a per-call basis, and no Calling party number information element is included in the SETUP message, the originating network shall set the presentation indicator according to the subscribed default value. + +The presentation indicator shall be forwarded to the destination in association with the basic call request. + +###### **4.5.2.2.2 Exceptional procedures** + +Not applicable. + +#### **4.5.2.3 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **4.5.2.4 Actions at the destination local exchange** + +###### **4.5.2.4.1 Normal operation** + +The actions to be performed at the destination local exchange are provided as part of the CLIP service, described in 3.5.2.3.1. + +###### **4.5.2.4.2 Exceptional procedures** + +Not applicable. + +### **4.6 Interaction with other supplementary services** + +#### **4.6.1 Call Waiting** + +No interaction. + +#### **4.6.2 Call Transfer** + +No interaction. + +#### **4.6.3 Connected Line Identification Presentation** + +No interaction. + +#### **4.6.4 Connected Line Identification Restriction** + +No interaction. + +#### **4.6.5 Calling Line Identification Presentation** + +CLIR takes precedence over CLIP. The only occasion when a user subscribing to CLIP can take precedence over CLIR is when the CLIP served user has an override category. This is a national option. + +#### **4.6.6 Calling Line Identification Restriction** + +No interaction. + +#### **4.6.7 Closed User Group** + +No interaction. + +#### **4.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **4.6.9 Direct-Dialling-In** + +No interaction. + +#### **4.6.10 Call diversion (call forwarding) services** + +##### **4.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **4.6.10.2 Call Forwarding No Reply** + +As specified in 3/Q.952. + +##### **4.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +#### **4.6.10.4 Call Deflection** + +As specified in 5/Q.952. + +#### **4.6.11 Line Hunting** + +No interaction. + +#### **4.6.12 Three-Party Service** + +No interaction. + +#### **4.6.13 User-to-User Signalling** + +##### **4.6.13.1 Service 1** + +No interaction. + +##### **4.6.13.2 Service 2** + +No interaction. + +##### **4.6.13.3 Service 3** + +No interaction. + +#### **4.6.14 Multiple Subscriber Number** + +No interaction. + +#### **4.6.15 Call Hold** + +No interaction. + +#### **4.6.16 Advice of Charge** + +No interaction. + +#### **4.6.17 Sub-addressing** + +No interaction. + +#### **4.6.18 Terminal Portability** + +No interaction. + +#### **4.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **4.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **4.6.21 Reverse Charging** + +No interaction. + +#### **4.6.22 Multi-level Precedence and Preemption** + +No interaction. + +### **4.7 Interaction with other networks** + +#### **4.7.1 Interaction with other networks** + +On calls to or via non-ISDNs, it cannot be assured that a restriction indication can be carried to the destination network. As a national network option the originating network shall have the possibility to restrict any information identifying the calling party being forwarded to the destination network when CLIR is applicable. If a destination network receives a calling party number without any indication of presentation allowed or restricted, the destination network (the host network) will act according to its rules and regulations. For further information see 3.7. + +#### **4.7.2 Procedures for interworking with private ISDNs** + +The procedures specified in 4.5 shall be used. + +### **4.8 Signalling flows** + +The signalling flows are not included as they form an integral part of the basic call control procedures. + +### **4.9 Parameter values (timers)** + +No specific timers are required. + +### **4.10 Dynamic description** + +See Figure 4-1. + +## **5 Connected Line Identification Presentation (COLP)** + +### **5.1 Definition** + +**connected line identification presentation (COLP)** is a supplementary service offered to the calling party which provides the connected party's ISDN number, with possible additional sub-address information, to the calling party. + +### **5.2 Description** + +#### **5.2.1 General description** + +This supplementary service is not a dialling check but an indication to the calling subscriber of the connected ISDN number. In a full ISDN environment, the connected line identity must include all the information necessary to unambiguously identify the connected line. + +Moreover, the information on the connected line identity may include additional sub-address information (i.e. the Connected sub-address information element) generated by the connected user and transparently transported by the network. The network is not responsible for the content of this additional sub-address information. + +Unless COLR has been subscribed by the connected user, the network delivers the connected line identity to the calling user regardless of the terminal capability to handle the information. + +![Flowchart for CLIR service logic. It starts with 'CLIR service' leading to a decision 'Calling usersubscribed to CLIR?'. If 'No', it leads to 'PI = 00 set by the network'. If 'Yes', it leads to a decision 'Subscription option'. If 'Permanent', it leads to 'PI = 01 set by the network'. If 'Temporary', it leads to a decision 'PI included in the CPN IE?'. If 'No', it leads to 'PI = default value'. If 'Yes', it leads to 'PI as received from the calling user'. All paths converge at a junction marked with a circle containing an 'X'.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +graph TD + Start([CLIR service]) --> D1{Calling usersubscribed to CLIR?} + D1 -- No --> P1[PI = 00 set by the network] + D1 -- Yes --> D2{Subscription option} + D2 -- Permanent --> P2[PI = 01 set by the network] + D2 -- Temporary --> D3{PI included in the CPN IE?} + D3 -- No --> P3[PI = default value] + D3 -- Yes --> P4[PI as received from the calling user] + P1 --> Join((X)) + P2 --> Join + P3 --> Join + P4 --> Join + +``` + +T1124580-90/d03 + +Flowchart for CLIR service logic. It starts with 'CLIR service' leading to a decision 'Calling usersubscribed to CLIR?'. If 'No', it leads to 'PI = 00 set by the network'. If 'Yes', it leads to a decision 'Subscription option'. If 'Permanent', it leads to 'PI = 01 set by the network'. If 'Temporary', it leads to a decision 'PI included in the CPN IE?'. If 'No', it leads to 'PI = default value'. If 'Yes', it leads to 'PI as received from the calling user'. All paths converge at a junction marked with a circle containing an 'X'. + +PI = 00 "presentation allowed" + PI = 01 "presentation restricted" + +FIGURE 4-1/Q.951 + Originating network side dynamic description + +#### 5.2.2 Specific terminology + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the presentation of the connected line identification information in association with outgoing calls. The served user is also known as the calling user. + +A **connected user** is the user that responded to the served user call request at the destination network and has been awarded the call by the network. The connected user need not have subscribed to the Connected Line Identification Presentation supplementary service. + +An ISDN number is a number conforming to the numbering plan structure specified in Recommendation E.164. + +An international number is an ISDN number structured as specified in Recommendation E.164. + +A national number or a national significant number is an ISDN number structured as specified in Recommendation E.164. + +A subscriber number is an ISDN number structured as specified in Recommendation E.164. + +An address is the number of the connected user (normally ISDN number), and a sub-address if provided by that user. + +A default number is an agreed number between the user at the connected side and the network provider. + +A special arrangement is an arrangement between a customer and a public network operator whereby customer supplied connected numbers are not screened by the public ISDN. + +COLP Connected Line Identification Presentation + +COLR Connected Line Identification Restriction + +#### **5.2.3 Qualification on the applicability to telecommunication services** + +See Recommendation I.251.5. + +#### **5.2.4 State definition** + +No specific states are required. + +### **5.3 Operational requirements** + +#### **5.3.1 Provision/withdrawal** + +See Recommendation I.251.5. + +#### **5.3.2 Requirements on the originating network side** + +See 5.5.2.1. + +#### **5.3.3 Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **5.3.4 Requirements on the destination network side** + +All information pertaining to COLP shall be inserted in the CONNECT message sent as part of the basic call procedures according to 5/Q.931. + +In the case where no information is provided by the connected user (as part of the basic call procedures), the network shall provide the default number associated with this user's access in the destination local exchange. When the connected number is provided by the connected user, the network can only verify that the number is within the set of numbers allocated to that user. Where a special arrangement exists with the connected user, no verification shall be performed. + +### **5.4 Coding requirements** + +The COLP supplementary service shall make use of the Connected number and Connected sub-address information elements inserted in the CONNECT message. + +All codesets used in this Recommendation are defined in codeset 0. + +TABLE 5-1/Q.951 +**CONNECT message content** + +Message type: CONNECT +Significance: local +Direction: both + +| Information element | Reference | Direction | Type | Length | +|--------------------------------------------------------------|-----------|-----------|------|--------| +| Protocol discriminator | 4.2/Q.931 | Both | M | 1 | +| Call reference | 4.3/Q.931 | Both | M | 2-* | +| Message type | 4.4/Q.931 | Both | M | 1 | +| Connected number | 5.4.1 | Both | O | 2-* | +| Connected sub-address | 5.4.1 | Both | O | 2-23 | +| NOTE – Other information elements as described in 3.1/Q.931. | | | | | + +#### 5.4.1 Connected number information element + +The purpose of the Connected number information element is to indicate which number is connected to a call. The connected number may be different from the called party number because of changes (e.g. call redirection, transfer) during the lifetime of a call. + +The Connected number information element is coded as shown in Figure 5-1. The maximum length of this information element is network dependent. + +![](171115f072e42b379238ed0dd438e9d7_img.jpg) + +| | | | | | | | | | | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---|---|-------------------------------|------------------------|---|-----|-----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 |
1001100

Connected number
Information element identifier

| | | | | | | | Octet 1 | +| | Length of connected number contents | | | | | | | | | +| 0/1
ext. | Type of number | | | | Numbering plan identification | | | | 3 | +| 1
ext. | Presentation
indicator |
000

Spare

| | | | Screening
indicator | | 3a* | | +| 0
Spare |

Number digits
(IA5 characters)

| | | | | | | | 4
etc. | + +FIGURE 5-1/Q.951 +**Connected number information element** + +#### 5.4.2 Connected sub-address information element + +The purpose of the Connected sub-address information element is to identify a sub-address associated with the connected number of a call. For the definition of sub-address, see Recommendation I.330. + +The Connected sub-address information element is coded as shown in Figure 5-2. Octets 3 and 4 are coded as in calling and Called party sub-address information elements in Recommendation Q.931. The maximum length of this information element is 23. + +![](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +| | | | | | | | | | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------|---|------------|---|---|-----------| +| bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| 0 |
Sub-address
1001101
Information element identifier
| | | | | | 1 | | +| Length of calling party sub-address contents | | | | | | | | 2 | +| 1
ext. | Type of sub-address | | Odd/Even
indicator | 0 | 0
Spare | 0 | | 3 | +| Sub-address information | | | | | | | | 4
etc. | + +FIGURE 5-2/Q.951 + +#### Connected sub-address information element + +### 5.5 Signalling requirements + +#### 5.5.1 Activation/deactivation/registration + +Not applicable. + +#### 5.5.2 Invocation and operation + +#### 5.5.2.1 Actions at the originating local exchange + +###### 5.5.2.1.1 Normal operation + +When the network sends a CONNECT message to the calling user and the calling user is provided with the COLP supplementary service, the network shall check to see if the connected number is available. + +If the connected number is available and presentation is allowed according to the presentation indicator supplied together with the connected number, the network shall include the Connected number information element in the CONNECT message sent to the calling user. If provided, the network shall also include the Connected sub-address information element in the CONNECT message. The presentation and screening indicators associated with the connected number and the connected sub-address received at the originating exchange shall be passed transparently to the calling user. + +The numbering plan identification field shall be coded either as “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”. + +If presentation is not allowed according to the presentation indicator supplied together with the connected number, the network shall include the Connected number information element in the CONNECT message sent to the calling user. The presentation indicator in the Connected number information element shall indicate “presentation restricted”. The network shall encode the screening indicator, numbering plan identification and the type of number according to one of the following options: + +- i) The screening indicator shall indicate “network provided”. The type of number and numbering plan identification shall be set to “unknown”. +- ii) The screening indicator, numbering plan identification and the type of number shall be passed as received at the destination network. + +The network shall not include number digits field. The network shall not include the Connected sub-address information element, in the CONNECT message. + +If neither the connected number nor an indication that presentation is restricted is available at the originating local exchange, the network shall include the Connected number information element in the CONNECT message sent to the calling user. The presentation indicator shall be set to “number not available due to interworking” and the screening indicator shall be set to “network provided”, the type of number and numbering plan identification shall be set to “unknown” and the number digits field shall not be included. The network shall not include the Connected sub-address information element, if provided, in the CONNECT message. + +If the calling user is not provided with the COLP supplementary service, then neither the Connected number nor the Connected sub-address information elements shall be included in the CONNECT message sent to the calling user. + +If presentation is restricted but as a national network option the calling user has the “override” category (e.g. police or emergency service) marked in the originating local exchange, the network shall include the Connected number information element and Connected sub-address information element if the sub-address was supplied by the connected user, in the CONNECT message. In this case, the presentation and screening indicators shall be passed transparently to the calling user. + +NOTE – If the presentation indicator in the Connected number information element received by the user is set to “number not available due to interworking” or “presentation restricted”, the remaining information in the Connected number information element should be ignored by the user. + +###### **5.5.2.1.2 Exceptional procedures** + +Not applicable. + +#### **5.5.2.2 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **5.5.2.3 Actions at the destination local exchange** + +###### **5.5.2.3.1 Normal operation** + +###### **5.5.2.3.1.1 Action at the destination user** + +These procedures shall be provided as part of the basic service and the connected user need not have subscribed to the COLP supplementary service. + +The numbering plan identification to be indicated within the Connected number information element, sent by the connected user shall be either “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”. + +NOTE – Either coding may be used and the treatment of both by the network is identical. + +Where the connected number included by the connected user is complete, the type of number to be indicated within the Connected number information element, sent by the connected user, shall be one of the following: + +- “*Subscriber number*” – In the case where the complete subscriber number is sent. +- “*National number*” – In the case where the complete national number is sent. +- “*International number*” – In the case where the complete international number is sent. + +Where a partial connected number is included by the connected user (e.g. to indicate digits specific to the Multiple Subscriber Number supplementary service) the user shall set the type of number to be indicated within the Connected number information element to “unknown”. + +###### **5.5.2.3.1.2 Actions at the destination local exchange if a special arrangement does not apply** + +These procedures shall be provided as part of the basic service and the connected user need not have subscribed to the COLP supplementary service. + +If multiple CONNECT messages are received from the called user, the network shall only perform the following procedures when it has decided which CONNECT message to acknowledge. + +Where a CONNECT message is received from the connected user, the network shall check to see if the Connected number and Connected sub-address information elements are included. + +If the Connected number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Connected number information element and process the call as if that information was not received. + +The network shall set the value of the screening indicator based on the outcome of the screening of the connected number. The network shall disregard any value of the screening indicator, if received from the connected user. + +If the Connected number information element is included, the network shall perform the screening function. + +NOTE 1 – Some networks may accept a full ISDN number with the addition of a prefix or escape digits to the number digits field and the type of number field set to “unknown”. + +If the connected number received from the connected user is determined to be correct, the network shall set the screening indicator to “user-provided, verified and passed”. + +If the screening function fails, the network shall note that the screening is failed and shall use a default number associated with the connected user. The network shall set the screening indicator to “network provided”. + +If the CONNECT message does not contain the Connected number information element, the network shall use a default number associated with the connected user. The network shall set the screening indicator to “network provided”. + +In the case where the connected user provides partial connected number information, and the number is a valid digit sequence for the user access arrangement, the network shall complete the number as appropriate. The network shall set the screening indicator to “user-provided, verified and passed”. + +NOTE 2 – In some cases the network cannot guarantee that the completed number identifies an end user. + +The information, as determined by the procedures above, shall be forwarded to the originating local exchange, in association with the basic call response. + +The presentation indicator, as determined by the procedures of the COLR supplementary service (see clause 6), shall be forwarded to the originating local exchange, in association with the basic call response. + +If the Connected sub-address information element is available, it shall be passed transparently through the network. + +The actions at the destination local exchange if a special arrangement does not apply are shown in Table 5-2. + +###### **5.5.2.3.1.3 Actions at the destination local exchange if a special arrangement applies** + +These procedures shall be provided as part of the basic service and the connected user need not have subscribed to the COLP supplementary service. + +If multiple CONNECT messages are received from the called user, the network shall only perform the following procedures when it has decided which CONNECT message to acknowledge. + +When a CONNECT message is received from the connected user, the network shall check to see if the Connected number and Connected sub-address information elements are included. + +If the Connected number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Connected number information element and process the call as if that information element was not received. + +If the Connected number information element is received with a coding of the type of number field other than “national number” or “international number”, then the network shall discard the Connected number information element and process the call as if that information element was not received. + +If the Connected number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony number plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Connected number information element and process the call as if that information element was not received. + +The network shall disregard any value of the screening indicator, if received from the connected user. + +TABLE 5-2/Q.951 + +###### **Information provided by the connected user and by the network when special arrangement does not apply** + +| Information provided by the connected user | | Information provided by the network to the calling user | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------| +| Connected number received from the connected user (octet 4) | Type of number (octet 3) | Connected number forwarded (if COLR is not activated) (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No connected number information element is provided by the connected user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 7) | +| Valid part of the number not sufficient for returning the call (Note 2) | “Unknown” | Completion of the number (Note 3) | User-provided verified and passed (Note 4) | “International number” or “national number” (Notes 1, 7) | +| Correct complete connected number (Note 5) | “Subscriber number” or “national number” or “international number” | Complete connected number | User-provided verified and passed | “International number” or “national number” (Notes 1, 7) | +| Incorrect number (Note 6) | Any type of number | Default number stored at the network side sufficient for returning the call | Network-provided | “International number” or “national number” (Notes 1, 7) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network where the origination is in a different country.

2 This assumes that the user's equipment provides that part of the number pertaining to its own (private) domain. This may be multiple subscriber number digits provided by a terminal equipment or an extension line number provided by a private ISDN. The network shall interpret the number digits and check if it is a valid digit sequence according to the agreements existing between the connected user and the network provider.

3 Completion means that the remaining part of the ISDN number associated with the appropriate access is added to the user provided part of the number.

4 The term “verified” implies matching the user provided number or part of this number(s) with the range(s) of numbers stored at the network side and it implies at least a valid format of user provided number information.

5 The term “correct” implies, from the network point of view, matching the subscriber number provided by the user with one of the range(s) of subscriber numbers stored at the network side.

6 The number provided by the user is discarded.

7 As a network option the type of number may be coded “unknown”, in which case, the number is organized according to the network dialling plan, i.e. prefixes, or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +If the CONNECT message does not contain the Connected number information element, the network shall use a default number associated with the connected user. The network shall set the screening indicator to “network provided”. + +The actions at the destination local exchange when special arrangement does not apply, are summarized in Table 5-2. + +The information, as determined by the procedures above, shall be forwarded to the origination local exchange, in association with the basic call response. + +If the Connected sub-address information element is available, it shall be passed transparently through the network. + +The presentation indicator, as determined by the procedures of the COLR supplementary service (see clause 6), shall be forwarded to the originating local exchange, in association with the basic call response. + +The actions at the destination local exchange when special arrangement applies are summarized in Table 5-3. + +If the Connected number information element is included, the network shall set the screening indicator forwarded to the calling user to “user-provided, not screened”. + +TABLE 5-3/Q.951 + +###### **Information provided by the connected user and by the network when special arrangement applies** + +| Information provided by the connected user | | Information provided by the network to the called user | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------|----------------------------------------------------------| +| Connected number received from the connected user (octet 4) | Type of number (octet 3) | Connected number forwarded if COLR is not activated (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No connected number information element is provided by the connected user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 2) | +| Any digit sequence conforming to Rec. E.164 | “National number” or “international number” | Number provided by the user (Note 1) | User-provided, not screened | “International number” or “national number” (Notes 1, 2) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network path where the origination is in a different country.

2 As a network option the type of number may be coded “unknown”, in which case, the number is organized according to the network dialling plan, i.e. prefixes, or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +###### 5.5.2.3.2 Exceptional procedures + +Not applicable. + +### 5.6 Interaction with other supplementary services + +#### 5.6.1 Call Waiting + +No interaction. + +#### 5.6.2 Call Transfer + +No interaction. + +#### 5.6.3 Connected Line Identification Presentation + +No interaction. + +#### 5.6.4 Connected Line Identification Restriction + +The connected line identification will not be presented to the calling user if the connected user has subscribed to COLR. The only occasion when a user subscribing to COLP can take precedence over COLR is when the COLP user has an override category. This is a national option. + +#### 5.6.5 Calling Line Identification Presentation + +No interaction. + +#### **5.6.6 Calling Line Identification Restriction** + +No interaction. + +#### **5.6.7 Closed User Group** + +No interaction. + +#### **5.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **5.6.9 Direct-Dialling-in** + +No interaction. + +#### **5.6.10 Call diversion (call forwarding) services** + +##### **5.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **5.6.10.2 Call Forwarding no Reply** + +As specified in 3/Q.952. + +##### **5.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +#### **5.6.10.4 Call Deflection** + +As specified in 5/Q.952. + +#### **5.6.11 Line Hunting** + +No interaction. + +#### **5.6.12 Three-Party Service** + +No interaction. + +#### **5.6.13 User-to-User Signalling** + +##### **5.6.13.1 Service 1** + +No interaction. + +##### **5.6.13.2 Service 2** + +No interaction. + +##### **5.6.13.3 Service 3** + +No interaction. + +#### **5.6.14 Multiple Subscriber Number** + +No interaction. + +#### **5.6.15 Call Hold** + +No interaction. + +#### **5.6.16 Advice of charge** + +No interaction. + +#### **5.6.17 Sub-addressing** + +No interaction. + +#### **5.6.18 Terminal Portability** + +No interaction. + +#### **5.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **5.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **5.6.21 Reverse Charging** + +No interaction. + +#### **5.6.22 Multilevel Precedence and Preemption** + +No interaction. + +### **5.7 Interaction with other networks** + +#### **5.7.1 Interaction with non-ISDNs** + +On calls destined for some non-ISDNs, the connected number may be delivered to the originating ISDN without an indication of connected line identity restriction. In this case a number of options exist and the selection of the following options is according to the network rules and regulations: + +- The network shall send the Connected number information element according to 5.5.2.1.1, sixth paragraph, and shall include no Connected sub-address information element. +- The network shall send the Connected number information element according to 5.5.2.1.1, fourth paragraph, and shall include no Connected sub-address information element. +- The network shall send the Connected number information element according to 5.5.2.1.1, second paragraph, and shall include the Connected sub-address information element if the connected sub-address is available. + +For some other non-ISDNs, no complete connected number may be available to the ISDN and therefore the full number of the connected user cannot be given to the calling user who has been provided with the COLP supplementary service. In this case the network shall send the Connected number information element according to 5.5.2.1.1, sixth paragraph, and shall include no Connected sub-address information element. + +On calls destined for some non-ISDNs, the connected number may be delivered to the originating ISDN with an indication of connected line identity restriction. In this case the network shall send the Connected number information element according to 5.5.2.1.1, second paragraph, and shall include the Connected sub-address information element if the connected sub-address is available. + +As a network option, the destination network may restrict any information identifying the connected user from being forwarded to another network. + +#### **5.7.2 Procedures for interworking with private ISDNs** + +These procedures specified in 5.5.2 shall be used. + +NOTE – The provision of the special arrangement where an access is used by a private network is especially appropriate. + +### **5.8 Signalling flows** + +The signalling flows are not included as they are an integral part of the basic call control procedures. + +### **5.9 Parameter values (timers)** + +No specific timers are required. + +### **5.10 Dynamic description** + +See Figures 5-3 and 5-4. + +![Flowchart for Destination network side dynamic description. The process starts with a call present, incoming call proceeding, and call received. It then connects and checks if CON IE is provided by the connected user. If yes, it checks for special arrangements. If yes, it sets SI = 00. If no, it verifies the number. If OK, it completes the number set (SI = 01). If not OK, it sets the default number set (SI = 11). If the user did not provide CON IE, it sets the default number set (SI = 11). All paths lead to COLR Service, setting the type of number and numbering plan, setup confirmation, and finally the connect request.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +graph TD + Start([Call present 6 +Incoming call proceeding 9 +Call received 7]) --> Connect[/CONNECT/] + Connect --> Decision1{CON IE +provided by +the connected +user?} + Decision1 -- No --> SI11_1[Default +number set +SI = 11] + Decision1 -- Yes --> Decision2{Special +arrangement?} + Decision2 -- Yes --> SI00[Set SI = 00] + Decision2 -- No --> Decision3{Verification +of the number?} + Decision3 -- OK --> SI01[Complete the +number set +SI = 01] + Decision3 -- Not OK --> SI11_2[Default +number set +SI = 11] + SI11_1 --> Merge(( )) + SI01 --> Merge + SI11_2 --> Merge + SI00 --> Merge + Merge --> COLR[COLR +Service] + COLR --> SetType[Set type of +number and +numbering plan] + SetType --> Setup[/Setup +confirmation/] + Setup --> End([Connect request 8]) + +``` + +T1158680-94/d04 + +Flowchart for Destination network side dynamic description. The process starts with a call present, incoming call proceeding, and call received. It then connects and checks if CON IE is provided by the connected user. If yes, it checks for special arrangements. If yes, it sets SI = 00. If no, it verifies the number. If OK, it completes the number set (SI = 01). If not OK, it sets the default number set (SI = 11). If the user did not provide CON IE, it sets the default number set (SI = 11). All paths lead to COLR Service, setting the type of number and numbering plan, setup confirmation, and finally the connect request. + +## NOTES + +- 1 This procedure operates independently from any COLP subscription by the connected user and is provided as part of the basic service. +- 2 The screening indicator encodings are: + - SI = 11 Network provided + - SI = 01 User provided verified and passed + - SI = 00 User provided verified not screened. + +FIGURE 5-3/Q.951 +Destination network side dynamic description + +![Flowchart for Originating network side dynamic description (Q.951). The process starts with 'Overlap sending 2 outgoing call proceeding 3 Call delivered 4', followed by 'Setup response'. A decision 'User subscribed to COLP?' branches into 'No' (leading to 'No CON IE is sent to the calling user') and 'Yes' (leading to 'CON IE available?'). 'CON IE available?' branches into 'Yes' (leading to 'Presentation allowed?') and 'No' (leading to 'CON IE without number digits (Note)'). 'Presentation allowed?' branches into 'No' (leading to 'Override?') and 'Yes' (leading to 'Send CON IE as received'). 'Override?' branches into 'No' (leading to 'CON IE without number digits') and 'Yes' (leading to 'Send CON IE as received'). All paths converge at a merge point before 'CONNECT', which leads to 'Active 10'.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +``` + +graph TD + Start([Overlap sending +2 outgoing call +proceeding 3 +Call delivered 4]) --> Setup[/Setup +response/] + Setup --> COLP{User +subscribed +to COLP?} + COLP -- No --> NoCONIE[No CON IE is sent +to the calling user] + COLP -- Yes --> CONIEAvail{CON IE +available?} + CONIEAvail -- Yes --> Presentation{Presentation +allowed?} + CONIEAvail -- No --> CONIENoDigitsNote[CON IE without +number digits +(Note)] + Presentation -- No --> Override{Override?} + Presentation -- Yes --> SendCONIE[Send CON IE as +received] + Override -- No --> CONIENoDigits[CON IE without +number digits] + Override -- Yes --> SendCONIE + NoCONIE --> Merge(( )) + CONIENoDigits --> Merge + SendCONIE --> Merge + CONIENoDigitsNote --> Merge + Merge --> CONNECT[/CONNECT/] + CONNECT --> Active10([Active 10]) + +``` + +T1130160-91/d05 + +Flowchart for Originating network side dynamic description (Q.951). The process starts with 'Overlap sending 2 outgoing call proceeding 3 Call delivered 4', followed by 'Setup response'. A decision 'User subscribed to COLP?' branches into 'No' (leading to 'No CON IE is sent to the calling user') and 'Yes' (leading to 'CON IE available?'). 'CON IE available?' branches into 'Yes' (leading to 'Presentation allowed?') and 'No' (leading to 'CON IE without number digits (Note)'). 'Presentation allowed?' branches into 'No' (leading to 'Override?') and 'Yes' (leading to 'Send CON IE as received'). 'Override?' branches into 'No' (leading to 'CON IE without number digits') and 'Yes' (leading to 'Send CON IE as received'). All paths converge at a merge point before 'CONNECT', which leads to 'Active 10'. + +NOTE – In this case SI=11 and PI=10. + +FIGURE 5-4/Q.951 +Originating network side dynamic description + +# **6 Connected Line Identification Restriction (COLR)** + +## **6.1 Definition** + +**connected line identification restriction (COLR)**fs is a supplementary service offered to the connected party to restrict presentation of the connected party's ISDN number and sub-address to the calling party. + +### **6.2 Description** + +#### **6.2.1 General description** + +When COLR is applicable and activated, the destination network shall provide the originating network with an indication that the connected user's ISDN number and sub-address information is (if provided by the connected user) are not allowed to be presented to the calling user. In this case no connected number and sub-address shall be included in the call connected information to the calling user. + +The presentation restriction function shall not influence the forwarding of the connected number within the network as part of the basic service procedures. + +#### **6.2.2 Specific terminology** + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the restriction of the connected line identification information (on a permanent or on a per-call basis) in association with incoming calls. The served user may also be known as the connected user. + +A **calling user** is the initiator of a call, received by the served user, on which COLR has been activated. + +An ISDN number is a number conforming to the numbering plan and structure specified in Recommendation E.164. + +COLP Connected Line Identification Presentation + +COLR Connected Line Identification Restriction + +#### **6.2.3 Qualification on the applicability to telecommunication services** + +See Recommendation I.251.6. + +#### **6.2.4 State definition** + +No specific states are required. + +### **6.3 Operational requirements** + +#### **6.3.1 Provision/withdrawal** + +See Recommendation I.251.6. + +#### **6.3.2 Requirements on the originating network side** + +See 6.5.2.1. + +#### **6.3.3 Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **6.3.4 Requirements on the destination network side** + +All information pertaining to COLR is inserted in the CONNECT message sent as part of the basic call procedures according to 5/Q.931. + +### **6.4 Coding requirements** + +The same as for 5.4. + +### **6.5 Signalling requirements** + +#### **6.5.1 Activation/deactivation/registration** + +Not applicable. + +#### **6.5.2 Invocation and operation** + +##### **6.5.2.1 Actions at the originating local exchange** + +###### **6.5.2.1.1 Normal operation** + +The actions to be performed at the originating local exchange are provided as part of the COLP supplementary service, described in 5.5.2.1.1. + +###### **6.5.2.1.2 Exceptional procedures** + +Not applicable. + +#### **6.5.2.2 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **6.5.2.3 Action at the destination user** + +If the connected user wishes to override the default setting in the network, the CONNECT message sent by the user shall contain the Connected number information element with the presentation indicator set appropriately. + +#### **6.5.2.4 Actions at the destination local exchange** + +###### **6.5.2.4.1 Normal operation** + +If the connected user has subscribed to the Connected Line Identification Restriction supplementary service permanent mode, the presentation indicator received in the CONNECT message will be ignored. The network shall set the presentation indicator to “presentation restricted”. + +If the connected user has subscribed to the COLR supplementary service on a per-call basis and requests to override the default setting, the destination network shall set the presentation indicator according to that in the received Connected number information element. + +The digits, if included, shall be treated according to Table 5-2 or Table 5-3, and 5.5.2.3.1. + +If COLR is requested by the user on a per-call basis, and no Connected number information element is included in the CONNECT message, the destination network shall set the presentation indicator according to the subscriber value. + +The presentation indicator shall be forwarded to the originating network in association with the basic call response. + +###### **6.5.2.4.2 Exceptional procedures** + +Not applicable. + +### **6.6 Interaction with other supplementary services** + +#### **6.6.1 Call Waiting** + +No interaction. + +#### **6.6.2 Call Transfer** + +No interaction. + +#### **6.6.3 Connected Line Identification Presentation** + +COLR will take precedence over COLP. The only occasion when a user subscribing to COLP can take precedence over COLR is when the user has an override category. This is a national option. + +#### **6.6.4 Connected Line Identification Restriction** + +No interaction. + +#### **6.6.5 Calling Line Identification Presentation** + +No interaction. + +#### **6.6.6 Calling Line Identification Restriction** + +No interaction. + +#### **6.6.7 Closed User Group** + +No interaction. + +#### **6.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **6.6.9 Direct-Dialling-In** + +No interaction. + +#### **6.6.10 Call diversion (call forwarding) services** + +##### **6.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **6.6.10.2 Call Forwarding no Reply** + +As specified in 3/Q.952. + +##### **6.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +##### **6.6.10.4 Call Deflection** + +As specified in 5/Q.952. + +#### **6.6.11 Line Hunting** + +No interaction. + +#### **6.6.12 Three-Party Service** + +No interaction. + +#### **6.6.13 User-to-User Signalling** + +##### **6.6.13.1 Service 1** + +No interaction. + +##### **6.6.13.2 Service 2** + +No interaction. + +##### **6.6.13.3 Service 3** + +No interaction. + +#### **6.6.14 Multiple Subscriber Number** + +No interaction. + +#### **6.6.15 Call Hold** + +No interaction. + +#### **6.6.16 Advice of Charge** + +No interaction. + +#### **6.6.17 Sub-addressing** + +No interaction. + +#### **6.6.18 Terminal Portability** + +No interaction. + +#### **6.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **6.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **6.6.21 Reverse Charging** + +No interaction. + +#### **6.6.22 Multilevel Precedence and Preemption** + +No interaction. + +### **6.7 Interaction with other networks** + +#### **6.7.1 Interaction with non-ISDNs** + +On calls to or via non-ISDNs, it cannot be assured that a restriction indication can be carried to the originating network. As a national network option the destination network shall have the possibility to restrict any information identifying the connected party from being returned to the originating network when COLR is applicable. If an originating network receives a connected party ISDN number without any indication of presentation allowed or restricted, the originating network (the host network) will act according to its rules and regulations. For further information see 5.7. + +#### **6.7.2 Procedures for interworking with private ISDNs** + +The procedures specified in 6.5 shall be used. + +### **6.8 Signalling flows** + +The signalling flows are not included as they form an integral part of the basic call control procedures. + +### **6.9 Parameter values (timers)** + +No specific timers are required. + +### **6.10 Dynamic description** + +See Figure 6-1. + +![Flowchart for Destination network side dynamic description. It starts with 'COLR service' leading to a decision 'Connected user subscribed to COLR?'. If 'No', PI = 00 set by the network. If 'Yes', it goes to 'Subscription option' (Permanent/Temporary). Permanent leads to PI = 01 set by the network. Temporary leads to 'PI included in the CON IE?'. If 'No', PI = default value. If 'Yes', PI as received from the connected user. All paths merge at a junction marked with a circle containing an X.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +graph TD + Start([COLR service]) --> Dec1{Connected user +subscribed to +COLR?} + Dec1 -- No --> PI00[PI = 00 set by +the network] + Dec1 -- Yes --> Dec2{Subscription +option} + Dec2 -- Permanent --> PI01[PI = 01 set by +the network] + Dec2 -- Temporary --> Dec3{PI included +in the CON IE?} + Dec3 -- No --> PIDefault[PI = default +value] + Dec3 -- Yes --> PIUser[PI as received +from the +connected user] + PI00 --> Merge((X)) + PI01 --> Merge + PIDefault --> Merge + PIUser --> Merge + +``` + +T1124610-90/d06 + +Flowchart for Destination network side dynamic description. It starts with 'COLR service' leading to a decision 'Connected user subscribed to COLR?'. If 'No', PI = 00 set by the network. If 'Yes', it goes to 'Subscription option' (Permanent/Temporary). Permanent leads to PI = 01 set by the network. Temporary leads to 'PI included in the CON IE?'. If 'No', PI = default value. If 'Yes', PI as received from the connected user. All paths merge at a junction marked with a circle containing an X. + +PI = 00 “presentation allowed” +PI = 01 “presentation restricted” + +FIGURE 6-1/Q.951 +**Destination network side dynamic description** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3492ba13104c1b23df1f843562f3a44bfb2f2c9 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c3b5263a414e8fc8439fed79252c47c4fa87561b287a62849e3421e8064d9d2 +size 38645 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fb0ad100987e7a486babf420232c8cff79e7979 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90a36647ab412616ae2ebeeb6c57fbdb78d180b3e91d5af55062638bb7386ed7 +size 60761 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36ad17a3ef915cae178c26dd1bc8a647a4dbbb80 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d58b2d3f801f4759843448c6f3163baa9947e05fd175b7f5314846a96e703eb +size 48455 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26442a15942cfbfa94ee13369391ac5855e83d97 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc3a8f1c6c09e069d8810b66ad377083c5440e611db6b90231d3df32c610838 +size 45238 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1dfa4d0c052bd5e90d18a3a242dc4c114a4db4d --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f34f770fd6d3986a538671d550d7eda63de9a11fdf9fba2c8391ab4f553fbe3 +size 18457 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7996f5b8beee3796ab3170c874a1f42ca0569b0e --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df113aae113a62a5160ec662f3356b0c85ba767b68fcf7ba99f0a8f07670484 +size 82934 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..660482f67c44ff6f3207939e71e8de295cd106ba --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9431be4b979467005c48eab2bef411813d145d8251dbad065f9a1472780d6f7 +size 8278 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edcc48e8cad98359a0034531d3b6fe31a43dc8cf --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f57e1d3f5bcfa63f9cf04c226400fec4a3a34d07eeb1d9a00903a8f9b0914e6b +size 55647 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..005bd8ca2639017b1d2df459c9ccc2427449f819 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57c86f920277a23776cd771bd81c89b972863a8c108a66880944c3c698b98052 +size 65292 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da744f67c459da472520051bd2f39b0c88c47546 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c9a474d01042d4ec8cfb4b61808136a9d271bf8bcbde37ae2d8bf7e8b37f253 +size 54554 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..098a31fe9214ebe786f9fead7d13f03f520a9321 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:446cb89d922a72c0ac90f0fb58f5eb9406d23e848bd6d61a46848c864091670b +size 40488 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2f9a76d816d468c0802a3c779f0a0ac174017bc --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62c07cfc3c51fa5563d31a3543d978402dcd782f45c70cc5ea3134259920fb02 +size 48677 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78fde414e464e810e254489a002d12a10edb25ad --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2118331203561cb623506c8527a1387b025714b9998ef65d1b9a453a6e5119e4 +size 89682 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bfec2ee37a2bc5198720ae0b2defd76df8e002c --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:195dc6f5790e25a95191605072b77db2643b243db4e577d45b5f9f5422fd973b +size 61292 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b45eb79b264dc809733c5234f12429798997a5a0 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e596bc2f1fe413072e7cc32b28010cc636936f39d46a93382f1ae96319d0f6bb +size 68540 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b17fa9ef3b8e28af1a50c83b40a946c2ac82df72 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50bc79ef71ee3711a58014f8d115b99f829f0b04912888df75cc293d34841964 +size 52288 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b7f6d593c4f8466e3089035880382ab9034d1ea --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deb1c558962a042276e889fd93ababa7c864e2248f2a34cd51047de0fe3dbb4e +size 88084 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63f65864ebea78b62b0146d4d38c48da6874e224 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9c1ab2f802cf8ff0ecec3dd002e8162847f308659913dda78048a685794a77e +size 85436 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c63d467914000e3c30106fe43aefcdd36a776ec --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:827675bf6e8b9879cb5b72fe42226779f622b01da915b7e69d366023234e7af0 +size 88637 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..877a5a0d5b6f2270a95de6267a1130275f084911 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc26b5cb28edd3184a9be076ccac97d6d1f152a2dc7f4406e165f06376b62129 +size 84018 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26fe2872ac943172e6a077f69eae4443e812ffb8 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca10e83984d59c59a503ef70e9522b44a639620920d8c192f2ab239b60e0d793 +size 112034 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f11cf5d37e22e08d12f790381076419e053f9beb --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c7635e91b1026f301cdc15c3eaafdb76ddaf31f253f8d3cc6e0505e8a3f9331 +size 41775 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b739af2dd64231fb77300051271da947dd5d7d4 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:653c0282235a26008949a05d08fe32e3760bcf63a58f087c2a16dc46725fddc5 +size 101275 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20f93899bc55aca1f33322fc5a9d6a30172553ce --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01213870b65f907af4a5f5312a0cb12bb364d0fa56f0c5b44e2a36c6f2f61b47 +size 100287 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11ee5155c91a50e7b775f0abefc53f7a8cd042c0 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a92ab7b15c8743e3888f263ecbaf2dbfae07ae015f5584d65eed2f3eafb69559 +size 131132 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f441452d24447eaabbf0d723b5ab9935f8ce238d --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fa9d56b7429443f2944dc1566138f9ee22e7c32c7cdbed79f6712e5f067898e +size 128011 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a32d92f58c78c01ef6c499e7ee1a92ec40d105fd --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bd6f13d0cd70b8b309bdcc94e0c4e6922295792d607a739daf04d85e104ee28 +size 35339 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a0c42790345f83db5905b13ef2204ca2fca3525 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caef803f8e61852a1c128a82918ae96c950ccd416db3ab888a27ff4cc133d0f8 +size 86020 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8024ff8a3dfdd1c945fd4f07485e720ed7aef85 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d1c7b92478548e2b54abd3757ca6fd5d6d5316ffe360478e4909269ad1e2fc8 +size 89269 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6fee8a2889d9ce5ffad831473cbc0f11505736e --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc2e0627f91b2572f3990b56da5ed0cb9a1570e6256f19479621139017edc584 +size 98215 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..045148baaad27b5187436d74e631e5789c6457b4 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c3cd3249fcfa379b9f0dbb8dfc01cf43d5881a13c4ffeb4ae1e4ba78d9d389d +size 87403 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bb41e4e587dcd9a9085638c52b1db38954bd3ba --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5797cadad6e8b897c51d838b332015e60cd3d1961efb9d954be18a35c6acbb8 +size 99376 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55be73aa53e02db978805e2ec97fd86022564773 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ac5f942a7f47be667f866c9a41f57497ca4eeacced7a7eb9de6e9b496487478 +size 92765 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2df445e80ccb3076e31391807fc59e439fc655c --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d67cfcd3a158ab7cf22069596c517b7b8528d9378faba07e36ac611d0b6ad9b +size 88224 diff --git a/marked/Q/T-REC-Q.952-199303-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.952-199303-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69705561c6cce32be76515a09994593bcff32435 --- /dev/null +++ b/marked/Q/T-REC-Q.952-199303-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eaaccff2510052f14762e17eb1500bf14df12c3852aee87833a2a8ac993d0c4e +size 18105 diff --git a/marked/Q/T-REC-Q.955.1-199202-I_PDF-E/raw.md b/marked/Q/T-REC-Q.955.1-199202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0bf960006ba370be016ea0b854d48737b0b6ca1e --- /dev/null +++ b/marked/Q/T-REC-Q.955.1-199202-I_PDF-E/raw.md @@ -0,0 +1,987 @@ + + +![ITU logo: a globe with the letters ITU inside, crossed by a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU inside, crossed by a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +# CCITT + +## Q.955 + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +# **STAGE 3 DESCRIPTION FOR SUPPLEMENTARY SERVICES USING DSS 1** --- + +# **STAGE 3 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES USING DSS 1** + +## **SECTION 1 – CLOSED USER GROUP** + +## **Recommendation Q.955** --- + +![CCITT logo: a globe with the letters CCITT inside.](84a1d09fb489061482111515543b60dc_img.jpg) + +CCITT logo: a globe with the letters CCITT inside. + +Geneva, 1992 + +## FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation Q.955, § 1 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 4th of February 1992. + +## --- CCITT NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. + +© ITU 1992 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# **STAGE 3 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES USING DSS 1** + +## **1 Closed User Group (CUG)** + +### **1.1 *Definition*** + +The supplementary service Closed User Group (CUG) enables users to form groups, to and from which access is restricted. A specific user may be a member of one or more CUGs. Members of a specific CUG can communicate among themselves but not, in general, with users outside the group. Specific CUG members can have additional capabilities that allow them to originate calls outside the group, and/or to receive calls from outside the group. Specific CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG, or from receiving calls from other members of the CUG. + +### **1.2 *Description*** + +#### **1.2.1 *General description*** + +Essentially normal call establishment procedures apply, but additionally, to provide CUG service, the network analyses the call request from the calling user in conjunction with the CUG attributes associated with both the calling and called users (as identified by their ISDN numbers). As a result of this analysis the call either fails for CUG reasons or is allowed to proceed. + +*Note* – In the case where a user has subscribed to the DDI supplementary service, attributes are associated with that part of the ISDN number which the network can recognize or with the default number valid for that access. + +The network provider may define the maximum number of CUGs of which a user can be a member. + +Since the fundamental purpose of the CUG service is to prevent certain connections, it is necessary to strictly control interactions with some other supplementary services to protect CUG integrity. + +#### **1.2.2 *Specific terminology*** + +##### **1.2.2.1 CUG manager** + +The CUG manager is the authority representing the interests of all the members of a CUG. By planning and controlling the membership and members' options, the manager can provide the overall CUG service expected by the members as a whole. + +The CUG manager need not be a CUG member and the concept has no signalling implications. + +##### **1.2.2.2 CUG index** + +The CUG index is a parameter used by the calling user to select a particular CUG when originating a call. The index is also used by the network to indicate to the called user the CUG from which an incoming call has originated. + +This index has only local significance, i.e. the index used by the calling user will, in general, be different from the index used by the called user to identify the same CUG. + +##### **1.2.2.3 CUG interlock code** + +This is a means of identifying CUG membership within the network. At the calling side, if a CUG match exists, the CUG index identifying a CUG maps to the CUG interlock code for that CUG. If a CUG match exists at the called side, the CUG interlock code identifying a CUG maps to the CUG index representing that CUG. + +CUG interlock code is not an access concept, but is used for clarity during the descriptions of signalling procedures and flows. + +##### 1.2.2.4 **preferential CUG** + +A CUG user subscribing to preferential CUG nominates a CUG index which the network uses to identify the required CUG in the absence of a CUG index being included in the outgoing call request. + +A preferential CUG applies to an ISDN number (or to an ISDN number/service – see § 1.3.1) and not to a specific CUG. + +##### 1.2.2.5 **CUG only service** + +A user with CUG only services is limited to making calls to, and receiving calls from, members of those CUGs of which the user is a member. + +##### 1.2.2.6 **outgoing calls barred within the CUG** + +This restriction means that a CUG user cannot make CUG calls to members of those CUGs of which the user is a member with the “outgoing calls” barring within the CUG option. + +##### 1.2.2.7 **outgoing access** + +Outgoing access allows a CUG user, in addition to the CUG only service (with or without outgoing calls barred within the CUG), to make calls to all other non-CUG users and also to those other CUG users that allow incoming access. + +An outgoing access arrangement applies to an ISDN number (or to an ISDN number/service – see § 1.3.1) and not to a specific CUG. + +##### 1.2.2.8 **incoming calls barred within the CUG** + +This restriction means that a CUG user cannot receive CUG calls from members of those CUGs of which the user is a member with the “incoming calls” barring within the CUG option. + +##### 1.2.2.9 *Incoming access* + +Incoming access allows a CUG user, in addition to the CUG only service (with or without incoming calls barred within the CUG), to receive calls from all other non-CUG users and also from those other CUG users that allow outgoing access. + +An incoming access arrangement applies to an ISDN number (or to an ISDN number/service – see § 1.3.1) and not to a specific CUG. + +#### 1.2.3 *Qualification on the applicability to telecommunication services* + +In general CUG service is defined independently of any basic service, i.e. it applies to an ISDN number. However, the service may be defined in relation to one, or a list of basic services. + +#### 1.2.4 *State definitions* + +No specifically defined states are required for the CUG service. + +### 1.3 *Operational requirements* + +#### 1.3.1 *Provision/withdrawal* + +The provision of the CUG service to a new member and also assignment of the various CUG service options (except preferential CUG) individually, require a prior arrangement between the (new) member and the network provider with the consent of the CUG manager for the CUG. + +The assignment of a CUG index value to be associated with the CUG and also the assignment of any preferential CUG requires prior arrangement between the (new) member and the network provider only. + +The CUG service is provided on a subscription basis. As a network provider option, CUG service can be offered with subscription options. The options can be divided into two groups: + +- a) The following options apply per ISDN number. The option values can be assigned individually for each basic service, or set of basic services, available at the ISDN number with CUG service: + +| Option | Values | +|---------------------|-------------------------------------------------------| +| 1) Preferential CUG | Default CUG index, or non designated | +| 2) Outgoing access | Allowed permanently, allowed per call, or not allowed | + +*Note* – The “allowed per call” outgoing access option is alternatively known as “outgoing access (explicit)” and the “allowed permanently” outgoing access option is alternatively known as “Outgoing access (implicit)”. + +| Option | Values | +|--------------------|-------------------------| +| 3) Incoming access | Allowed, or not allowed | + +If for a user with CUG service, a basic service, or set of basic services, is not included in at least one CUG, then: + +- preferential CUG must have the “none designated” option value; +- outgoing access will normally have the “allowed permanently” option value if outgoing calls using a basic service or set of basic services are required; +- incoming access will have the “allowed” option value if incoming calls using a basic service or set of basic services are required. + +- b) The following option applies per CUG. If the CUG includes more than one basic service, or set of basic services, the value of this option can be assigned individually for each basic service, or set of basic services, including: + +| Option | Values | +|---------------------------|-----------------------------------------| +| 1) Barring within the CUG | None, incoming calls, or outgoing calls | + +If for a particular basic service, or set of basic services, available to an ISDN number, a preferential CUG is nominated, then it shall not be possible to assign the “outgoing calls” barring within the CUG option to that basic service, or set of basic services, for the preferential CUG. + +The options assigned to a CUG member are stored in the network. + +*Note* – Whether or not the storage of these options for CUG are centralized or decentralized is beyond the scope of this Recommendation and is defined in the stage 2 of Recommendation of CUG (see Recommendation Q.85.1). + +#### 1.3.2 *Requirements on the originating network side* + +For correct interactions with other supplementary services, it is necessary for the originating network side to store, for the duration of the call, details of whether a non-CUG, CUG (without outgoing access) or CUG (with outgoing access) call was requested in the information sent to the destination network side. The CUG identity (if any) requested of the destination network side must also be retained. + +#### 1.3.3 *Requirements in the network* + +This section is not applicable to DSS 1. + +#### 1.3.4 Requirements on the terminating network side + +For correct interactions with other supplementary services, it is necessary for the destination network side to store, for the duration of the call, details of whether a non-CUG or CUG (with or without outgoing access) call request was passed to the user. The CUG identity (if any) requested must also be retained. + +### 1.4 Coding requirements + +#### 1.4.1 Messages + +The messages that will be used for the invocation and control of the CUG supplementary service follow: + +- a) DISCONNECT (see Note 1); +- b) RELEASE (see Note 1); +- c) RELEASE COMPLETE (see Note 1); +- d) SETUP (see Note 2). + +*Note 1* – The facility information element may be included in the network-to-user direction in the first call clearing message if the calling user explicitly requests CUG service, if the network cannot allow the call to proceed before returning CUG service acceptance to the calling user. In the user-to-network direction the facility information element may be included in the first call clearing message if the called user cannot allow the call to proceed before returning CUG service acceptance to the network. + +*Note 2* – In the user-to-network direction the facility information element will be included if the calling user explicitly requests CUG service. In the network-to-user direction facility information element will be included if a CUG call is required. + +#### 1.4.2 Operations (ASN.1) + +Closed-User-Group-Service-Operations {ccitt recommendation q 955 cug (1)} + +DEFINITIONS ::= + +BEGIN + +EXPORTS CUGCallOperationType ; + +IMPORTS OPERATION, ERROR Remote-Operation-Notation {joint-iso-ccitt remote-operations(4) notations(0)} +userNotSubscribed, basicServiceNotProvided FROM General-Error-List +{ccitt recommendation q 950 general-error-list}; + +CUGCallOperationType ::= -- invoked from calling user to originating +-- network side and from destination network +-- side to user. + +OPERATION + +ARGUMENT SEQUENCE { +outgoingAccessRequest [1] IMPLICIT BOOLEAN DEFAULT FALSE, +-- if outgoing access is requested then TRUE is set, and +-- if outgoing access is not requested then FALSE is set. +cUGIndex [2] IMPLICIT CUGindex OPTIONAL} +-- in SETUP message + +ERRORS { +userNotSubscribed, +basicServiceNotProvided, +invalidOrUnregisteredCUGIndex, +requestedBasicServiceViolatesCUGConstraints, +outgoingCallsBarredWithinCUG, + +``` + + incomingCallsBarredWithinCUG, + userNotMemberOfCUG, + inconsistencyInDesignatedFacilityAndSubscriberClass} + -- in first clearing message to calling user or network + +CUGCallOperation CUGCallOperationType ::= 2 + +CUGIndex ::= INTEGER (0..32767) + +-- Some networks may specify a max. value of the CUG index from 0 to 9999. + +invalidOrUnregisteredCUGIndex ERROR ::= 16 +requestedBasicServiceViolatesCUGConstraints ERROR ::= 17 +outgoingCallsBarredWithinCUG ERROR ::= 18 +incomingCallsBarredWithinCUG ERROR ::= 19 +userNotMemberOfCUG ERROR ::= 20 +inconsistencyInDesignatedFacilityAndSubscriberClass ERROR ::= 21 + +END -- of closed user group service operations + +``` + +### 1.5 *Signalling requirements* + +#### 1.5.1 *Activation/deactivation/registration* + +No signalling procedure is necessary for activation, deactivation and registration. + +#### 1.5.2 *Invocation and operation* + +The CUG service is invoked by: + +- a call originating from a user that has CUG service. The user can explicitly request CUG service, but in the absence of an explicit request the CUG service default procedures are automatically applied; +- a call terminating at a user that has CUG service. + +##### 1.5.2.1 *Normal operation* + +###### 1.5.2.1.1 *Actions at the originating local exchange* + +###### 1.5.2.1.1.1 *Call originating from a user with CUG service* + +###### 1.5.2.1.1.1.1 *Explicit request of CUG service* + +The calling user can explicitly request the CUG service by including in the outgoing SETUP message a facility information element containing a CUG call invoke component. + +To indicate outgoing access the user shall set the value of the Outgoing Access Request parameter to TRUE. + +The network performs internal checks appropriate to the originating network side based on the contents of the invoke component and the CUG attributes of the calling user. The outcome of these checks are defined in Table 1-1/Q.955 (including Notes). + +*Note* – The network might respond to the SETUP message with a SETUP ACKNOWLEDGE or CALL PROCEEDING message or the call might be cleared for some non-CUG service related reasons before the checks are completed. + +If the result of the checks relevant to the originating network side allow the call to proceed, then the network performs further internal checks based on the CUG attributes (if any) of the called user. The outcome of these checks are defined in Table 1-2/Q.955. + +If the call is successfully offered to the called user, an ALERTING or CONNECT message according to basic call control, shall be returned to the calling user. + +###### 1.5.2.1.1.1.2 *Implicit request of CUG service* + +The calling user with CUG service can request the CUG service without including an invoke component in the outgoing setup message (e.g. to make use of the preferential CUG facility). In this case the procedures of § 1.5.2.1.1.1.1 apply with the following exception: + +- the network performs internal checks appropriate to the originating network side only based on the CUG attributes of the calling user. + +###### 1.5.2.1.1.2 *Call originating from a user without CUG service* + +It is possible for a user without CUG service to make a call to a user with CUG service. If such a calling user does not include a CUG call invoke component in the outgoing SETUP message, Table 1-1/Q.955 shall apply. + +The network then performs further internal checks based on the CUG attributes (if any) of the called user. The outcome of these checks are defined in Table 1-2/Q.955. + +If the call is successfully offered to the called user, no return result component shall be returned to the calling user. + +###### 1.5.2.1.2 *Actions at the transit exchange* + +This section is not applicable to DSS 1. + +###### 1.5.2.1.3 *Actions at the destination local exchange* + +If the internal checks defined in Table 1-2/Q.955 result in a requirement for a CUG call (with or without outgoing access request) to the called user, then the incoming SETUP message shall include a facility information element containing a CUG call invoke component. + +If the call is successfully offered to the called user, no return result component shall be expected by the network. + +##### 1.5.2.2 *Exceptional procedures* + +###### 1.5.2.2.1 *Actions at the originating local exchange* + +###### 1.5.2.2.1.1 *Call originating from a user with CUG service* + +###### 1.5.2.2.1.1.1 *Explicit request of CUG service* + +If the network cannot allow the call to proceed for a CUG service related reason as a result of the checks relevant to either the originating or the destination network side, then the network shall fail the call attempt and include in the first clearing message returned to the calling user a facility information element containing a return error component with the appropriate indication as defined by Tables 1-1/Q.955 and 1-2/Q.955 (including Notes). + +The Q.931 cause in the clearing message conveying the return error component will be No. 29 “facility rejected”. + +If the call attempt fails for a non-CUG service related reason, then a facility information element containing a return error component indicating “basic service not provided” should be included in the first clearing message returned to the calling user. The Q.931 cause used will be determined by the event causing the failure. However, even if a facility information element containing a return error component will not be included in the first clearing message to the calling user, the terminal shall continue normal clearing and abandon the operation. + +The possibility of “simultaneous” failure for CUG and non-CUG service related reasons is not precluded. In this case the return error component will contain an indication as defined by Tables 1-1/Q.955 and 1-2/Q.955, but the Q.931 cause will be determined by the non-CUG service event causing call failure. + +TABLE 1-1/Q.955 + +###### **CUG check at the originating network side** + +This table is used to determine the type of call request sent to the destination network side and the type of rejection indications returned to the calling user. + +*Note* — The type of call request derived from this table determines the linkage to Table 1-2/Q.955 + +| CUG attributes of calling user for requested basic service | | CUG information received from calling user in SETUP | | | | | +|------------------------------------------------------------|---------|-----------------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|------------------------------------------------------| +| | | CUG call invoke received | | | | No CUG call invoke received | +| | | OA not requested CUG index | OA requested CUG index | OA not requested no CUG index | OA requested no CUG index | | +| O/access not allowed | Not OCB | CUG call
IC = spec CUG
(Note 1) | CUG call
IC = spec CUG
(Note 1) | Rejected
RE-VAL = No. 21
(Note 5) | Rejected
RE-VAL = No. 21
(Note 5) | Rejected
Rec. Q.931
CAUSE = No. 29
(Note 5) | +| | OCB | Rejected
RE-VAL = No. 18 | Rejected
RE-VAL = No. 18 | | | | +| O/access per call | Not OCB | CUG call
IC = spec CUG
(Note 1) | CUG + OA
IC = spec CUG
(Note 2) | Rejected
RE-VAL = No. 21
(Note 5) | Non-CUG call
(Note 5) | Rejected
Rec. Q.931
CAUSE = No. 29
(Note 5) | +| | OCB | Rejected
RE-VAL = No. 18 | Non-CUG call | | | | +| O/access permanent | Not OCB | CUG + OA
IC = spec CUG
(Note 1) | CUG + OA
IC = spec CUG
(Note 1) | Non-CUG call
(Note 5) | Non-CUG call
(Note 5) | Non-CUG call
(Note 5) | +| | OCB | Non-CUG call | Non-CUG call | | | | +| Preferential CUG nominated
O/access not allowed | Not OCB | CUG call
IC = spec CUG
(Note 3) | CUG call
IC = spec CUG
(Note 3) | CUG call
IC = preferential CUG | Rejected
RE-VAL = No. 21 | CUG call IC = preferential CUG | +| | OCB | Rejected
RE-VAL = No. 18
(Note 4) | Rejected
RE-VAL = No. 18
(Note 4) | Combination barred
(Note 6) | Combination barred
(Note 6) | Combination barred
(Note 6) | +| Preferential CUG nominated
O/access per call | Not OCB | CUG call
IC = spec CUG
(Note 3) | CUG + OA
IC = spec CUG
(Note 3) | CUG call
IC = preferential CUG | Non-CUG call | CUG call IC = preferential CUG | +| | OCB | Rejected
RE-VAL = No. 18
(Note 4) | Non-CUG call
(Note 4) | Combination barred
(Note 6) | Combination barred
(Note 6) | Combination barred
(Note 6) | +| Preferential CUG nominated
O/access permanent | Not OCB | CUG + OA
IC = spec CUG
(Note 3) | CUG + OA
IC = spec CUG
(Note 3) | (Note 8) | CUG + OA call IC = preferential CUG | (Note 8) | +| | OCB | Non-CUG call
(Note 4) | Non-CUG call
(Note 4) | Combination barred
(Note 6) | Combination barred
(Note 6) | Combination barred
(Note 6) | +| Not a CUG user | | Rejected
RE-VAL = No. 0 | Rejected
RE-VAL = No. 0 | Rejected
RE-VAL = No. 0 | Rejected
RE-VAL = No. 0 | Non-CUG call
(Note 7) | + +OA                      Outgoing access + OCB                    Outgoing call barred + IC                      CUG interlock code + RE                     Return error + RE-VAL                Return error value + +| | | +|-------------------------|-----------------------------------------------------------| +| RE-VAL No. 0 | User not subscribed | +| RE-VAL No. 16 | InvalidOrUnregisteredCUGIndex | +| RE-VAL No. 17 | Requested basic service violates CUG constraints | +| RE-VAL No. 18 | Outgoing calls barred within CUG | +| RE-VAL No. 21 | Inconsistency in designated facility and subscriber class | +| Rec. Q.931 CAUSE No. 29 | Facility rejected | + +*Note 1* — Assumes match between CUG index and IC exists for the requested basic service. If no match exists then: + +- if the CUG index exists but is not appropriate to the requested basic service the call is rejected with RE-VAL = No. 17; +- Note that this includes the case when the requested basic service is not included in any CUG; +- if the CUG index does not exist the call is rejected with RE-VAL = No. 16. + +*Note 2* — Assumes match between CUG index and IC exists for the requested basic service. If no match exists then: + +- if the CUG index exists but is not appropriate to the requested basic service the call proceeds as a non-CUG call. + +Note that this includes the case when the requested basic service is not included in any CUG; + +- if the CUG index does not exist the call is rejected with RE-VAL = No. 16. + +*Note 3* — Assumes match between CUG index and IC exists for the requested basic service. If no match exists then: + +- if the CUG index exists but is not appropriate to the requested basic service the call is rejected with RE-VAL = No. 17; +- if the CUG index does not exist the call is rejected with RE-VAL = No. 16. + +*Note 4* — If the CUG index identifies the preferential CUG then this combination is barred in the options data, i.e. the preferential CUG cannot be assigned the “outgoing calls” barring within the CUG option. + +*Note 5* — This includes the case when the requested basic service is not included in any CUG. + +*Note 6* — This combination is barred in the options data, i.e. the preferential CUG cannot be assigned the “outgoing calls” barring within the CUG option. + +*Note 7* — This represents the normal case of a user without CUG service making a non-CUG call. + +*Note 8* — Both “preferential CUG” and “allowed permanently” outgoing access options imply that either of them can be requested without including an invoke component in the outgoing SETUP message. When a user subscribes to both options, a network does not know which option the user is invoking in the outgoing SETUP message. + +Three ways of operating are recommended: + +- 1) the user has to indicate if a call is intended to be an outgoing access call. If no information (CUG request or outgoing call request) is given, the preferential CUG is assumed; +- 2) the combination of the options is not allowed, i.e. a user cannot have both options allocated at the same time; +- 3) the caller may make a call and the network will route the call with the preferential CUG and an outgoing access request. The call will therefore be connected if the called number is a member of the preferential CUG or is a member of a different CUG and has incoming access, or is a non-CUG user. + +In the case of option 1) the type of call request sent to the destination network side is “CUG (IC = pref.)”. + +In the case of option 2) the combination of the options is not allowed. + +In the case of option 3) the type of call request sent to the destination network side is “CUG + OA (IC = pref.)”. + +The choice from the above cases is a national option. + +TABLE 1-2/Q.955 + +###### **CUG checks at the destination network side** + +This table can be used to determine the type of call request sent to the destination user and the type of rejection indications returned to the calling user. + +| Type of CUG indication from the network | M or NM | CUG attributes of called user for requested basic service | | | | Not a CUG user | | +|-----------------------------------------|---------|-----------------------------------------------------------|-----------------------------|--------------------------------------|-----------------------------|-----------------------------|--| +| | | I/access not allowed | | Incoming access allowed | | | | +| | | Not ICB | ICB | Not ICB | ICB | | | +| CUG call with no O/access indication | M | CUG call | Rejected
RE-VAL = No. 19 | CUG call | Rejected
RE-VAL = No. 19 | Rejected
RE-VAL = No. 20 | | +| | NM | Rejected RE-VAL = No. 20
(Note 1) | | Rejected RE-VAL = No. 20
(Note 1) | | | | +| CUG call with O/access indication | M | CUG call with OA request | Rejected
RE-VAL = No. 19 | CUG call with OA request | Non-CUG call | Non-CUG call | | +| | NM | Rejected RE-VAL = No. 20
(Note 1) | | Non-CUG call (Note 2) | | | | +| Non-CUG call | — | Rejected RE-VAL = No. 20 (Note 2) | | Non-CUG call (Note 2) | | Non-CUG call
(Note 3) | | + +| | | +|---------------|--------------------------------------------------------------------------| +| ICB | Incoming call barred | +| M | Match between IC and CUG index exists for the requested basic service | +| NM | No match between IC and CUG index exists for the requested basic service | +| IC | CUG interlock code | +| RE | “Return error” component returned to calling user | +| RE-VAL | “Return error” value | +| RE-VAL No. 17 | Requested basic service violates CUG constraints | +| RE-VAL No. 19 | Incoming calls barred within CUG | +| RE-VAL No. 20 | User not member of CUG | + +###### *Key to cross points in table:* + +| | | +|--------------------------|---------------------------------------------------------------------------------------------| +| CUG call | Invoke component in SETUP message identifies CUG index but does not request outgoing access | +| CUG call with OA request | Invoke component in SETUP message identifies CUG index and requests outgoing access | +| Non-CUG call | No invoke component in SETUP message | + +*Note 1* — Assumes that the CUG match fails because the IC does not exist for the called user. If the IC exists but is not appropriate to the requested basic service, then the call is rejected with RE-VAL = No. 17. + +Note that this includes the case when the requested basic service is not included in any CUG. + +*Note 2* — This includes the case when the requested basic service is not included in any CUG. + +*Note 3* — This represents the normal case of a user without CUG service receiving a non-CUG call. + +###### 1.5.2.2.1.1.2 *Implicit request of CUG service* + +If the calling user with CUG service does not include an invoke component in the outgoing SETUP message (e.g. to make use of the preferential CUG facility) the procedures of § 1.5.2.2.1.1.1 apply with the following exceptions: + +- 1) if either the originating or destination network side cannot allow the call to proceed for a CUG service related reason, the network shall initiate call clearing using the following Q.931 causes: + - No. 87 “user not a member of CUG” if the corresponding return error value would be No. 20 “user not a member of CUG” using the explicit request procedures; + - No. 29 “facility rejected” in the case of all other CUG service related reasons, +- 2) when a call fails for a purely non-CUG service related reason, then no indication of “basic service not provided” is provided to the calling user. + +###### 1.5.2.2.1.2 *Call originating from a user without CUG service* + +If the calling user includes in the outgoing SETUP message a facility information element containing a CUG call invoke component, and the network can recognize that the calling user is requesting CUG service, then it shall include in the first CLEARING message returned to the calling user a facility information element containing a return error component with the appropriate indication as defined by Table 1-1/Q.955, i.e. “user not subscribed”. + +If the calling user does not include a facility information element, and the network cannot allow the call to proceed as a result of the checks relevant to the destination network side, then the network shall fail the call attempt and initiate clearing with Q.931 cause No. 87 “user not a member of CUG”. No CUG service related indication shall be conveyed to the calling user. + +If the call attempt fails for a non-CUG service related reason, then no CUG service related procedures apply. + +###### 1.5.2.2.2 *Actions at the transit exchange* + +This section is not applicable to DSS 1. + +###### 1.5.2.2.3 *Actions at the destination local exchange* + +If after transmitting the incoming SETUP message and before receiving an ALERTING message, the call attempt fails for a CUG or non-CUG service related reason, then the network expects a return error component with the appropriate indication in the first clearing message received from the called user. If the call attempt fails for a CUG service related reason, the Q.931 cause in the clearing message conveying the return error component will normally be No. 29 “facility rejected”. The indication in the return error component shall be sent back to the calling user. Absence of the return error component shall be regarded by the destination network side as a failure for non-CUG service related reasons. + +In the case of a SETUP message sent via the broadcast data link, the network may, as a network option, retain the return error component along with the Q.931 cause retained according to § 5.2.5.3 of Recommendation Q.931. If there are multiple clearing messages containing return error components, the indication in the return error component contained in the first clearing message will be sent back to the calling user. If any of the clearing messages with the highest Q.931 causes do not contain return error components and other clearing messages with Q.931 causes of lower priority do contain return error components, no indication in these return error components shall be sent back to the calling user. + +### 1.6 *Interaction with other supplementary services* + +#### 1.6.1 *Call Waiting* + +No interaction. + +#### 1.6.2 *Call Transfer* + +No applicable interaction at this time. + +#### 1.6.3 *Connected Line Identification Presentation* + +No interaction. + +#### 1.6.4 *Connected Line Identification Restriction* + +No interaction. + +#### 1.6.5 *Calling Line Identification Presentation* + +No interaction. + +#### 1.6.6 *Calling Line Identification Restriction* + +No interaction. + +#### 1.6.7 *Closed User Group* + +Not relevant. + +#### 1.6.8 *Conference Calling* + +No applicable interaction at this time. + +#### 1.6.9 *Direct-Dialling-in* + +When the user has also subscribed to the DDI supplementary service, the CUG supplementary service is provided on the basis of that part of the ISDN number which the network can recognize or with the default number valid for that access. However CUG membership shall not be available on a per DDI number basis, but instead shall be on the basis of the entire range of DDI members applicable at an access or group of accesses. + +#### 1.6.10 *Call diversion (call forwarding) services* + +##### 1.6.10.1 *Call Forwarding Busy* + +No interaction. + +##### 1.6.10.2 *Call Forwarding No Reply* + +No interaction. + +##### 1.6.10.3 *Call Forwarding Unconditional* + +No interaction. + +##### 1.6.10.4 *Call Deflection* + +No interaction. + +#### 1.6.11 *Line Hunting* + +Interaction is specified in Recommendation Q.952, § 6. + +#### 1.6.12 *Three-Party-Service* + +Interaction is specified in Recommendation Q.954, § 2. + +#### 1.6.13 *User-to-User Signalling* + +##### 1.6.13.1 *Service 1* + +No interaction + +##### 1.6.13.2 *Service 2* + +No interaction + +##### 1.6.13.3 *Service 3* + +No interaction + +#### 1.6.14 *Multiple Subscriber Number* + +It shall be possible to provide separate CUG services for each ISDN number both at the calling and called sides. + +If the calling terminal does not identify its MSN, then the CUG attributes assigned to the default number shall be applied by the originating network side. + +It is the CUG manager's responsibility to ensure that a passive bus does not compromise CUG integrity. + +#### 1.6.15 *Call Hold* + +No interaction. + +#### 1.6.16 *Advice of Charge* + +No interaction. + +#### 1.6.17 *Sub-addressing* + +No interaction. + +#### 1.6.18 *Terminal Portability* + +No interaction. + +#### 1.6.19 *Completion of Calls to Busy Subscriber* + +No applicable interaction at this time. + +#### 1.6.20 *Malicious Call Identification* + +No applicable interaction at this time. + +### 1.7 *Interaction with other networks* + +#### 1.7.1 *Interaction with public network* + +Where a CCITT Signalling System No. 7 link exists between two networks, bilateral agreement is required to allow a CUG interlock code to be unique across both networks. + +Note that part of the CUG interlock code already identifies the allocating country. + +When a CCITT Signalling System No. 7 network interworks with a network not supporting CUG service (e.g. an analogue network), the gateway allows non-CUG calls and CUG calls requesting outgoing access to proceed as normal calls. In the latter case the CUG interlock code is discarded and there is no CUG specific notification returned to the originating network side. + +In the case of CUG calls (without outgoing access request) the gateway rejects the call request. Within the return error component returned to the calling user, the indication shall be "user not member of CUG" and the Q.931 cause will normally be No. 29 "facility rejected". + +#### 1.7.2 *Interaction with private ISDN* + +When a public network CUG interacts with a private network CUG by way of an access, it is possible, by mapping between the two CUG domains in the gateway (e.g. PBX), to arrange for CUG users to perceive the concatenated CUG domains as a single CUG. + +Under these circumstances the access must behave as an internodal link for CUG purposes. + +If the private network with a private network CUG domain is the originating network, a public CUG index should be indicated in a SETUP message whenever CUG service is requested so that the private network can receive proper indications of public CUG failures or destination private CUG failures. + +Therefore when the private network anticipates interaction with a public CUG domain at the originating side, it shall use only the explicit request of CUG service. + +If the private network is the destination network, no special procedures are required. + +### 1.8 Signalling flows + +The following examples show only the messages which convey CUG information and their CUG related contents. Otherwise, basic call control applies. + +### 1.9 Parameter value (timers) + +### 1.10 Dynamic description (SDLs) + +The SDL description is shown in Figures 1-5/Q.955 and 1-6/Q.955. + +Figures 1-5/Q.955 and 1-6/Q.955 provide the SDL description of the CUG process at the originating and destination network sides respectively. + +The CUG process is modelled as an extension of the call control process. Information can pass between the call control and CUG processes by means of primitives. + +The call control process communicates certain call control events and parameters to the CUG process and then waits for instructions to proceed from the CUG process. The primitives from the CUG process fall into two categories: + +- a) *Continue*: The continue primitive prompts the call control process to proceed but does not change the course of call control in establishing or clearing the call attempt. It may provide additional instructions from the CUG process to call control, e.g.: + - *normal*: no additional instructions to call control; + - apply checks – call control required to perform the appropriate CUG checks and then proceed (note that the stage 2 description functional entities FE3 “outgoing CUG control” and FE5 “incoming CUG control” are not modelled as part of the stage 3 description “CUG process”); + - RE value – call control required to include a *CUG call* return error component with the indicated value in the first clearing message to the calling user; +- b) *Clear call*: The clear call primitive causes call control to move from call establishment to appropriate call clearing procedures using the additional information provided by the CUG process. + +![Sequence diagram showing call signalling flow between Calling user, Network, and Called user.](a7c51c18111139f9aca2805114108565_img.jpg) + +``` +sequenceDiagram + participant CU as Calling user + participant N as Network + participant CUS as Called user + + CU->>N: SETUP [FAC(CUG-CL-INV, OA, CI)] + N-->CU: CALL PROCEEDING + N->>CUS: SETUP [FAC(CUG-CL-INV, OA, CI)] + CUS-->N: ALERT + N-->CU: ALERT + CUS->>N: CONNECT + N-->CU: CONNECT + CUS->>N: CONNECT ACKNOWLEDGEMENT +``` + +The diagram illustrates the signalling flow for a successful call passing through both originating and destination network checks. It involves three entities: Calling user, Network, and Called user. The sequence of messages is as follows: 1. The Calling user sends a SETUP message to the Network, containing FAC(CUG-CL-INV, OA, CI). 2. The Network responds to the Calling user with a CALL PROCEEDING message. 3. The Network sends a SETUP message to the Called user, also containing FAC(CUG-CL-INV, OA, CI). 4. The Called user sends an ALERT message back to the Network. 5. The Network sends an ALERT message back to the Calling user. 6. The Called user sends a CONNECT message to the Network. 7. The Network sends a CONNECT message back to the Calling user. 8. The Called user sends a CONNECT ACKNOWLEDGEMENT message to the Network. + +Sequence diagram showing call signalling flow between Calling user, Network, and Called user. + +T1124750-90 + +FIGURE 1-1/Q.955 + +**Call passes both originating and destination network checks and is successful** + +![Sequence diagram for Figure 1-2/Q.955 showing a call failure scenario where the destination network side checks fail. The diagram involves three lifelines: Calling user, Network, and Called user. The sequence of messages is: Calling user sends SETUP [FAC(CUG-CL-INV, OA, CI)] to Network; Network sends CALL PROCEEDING to Calling user; Network sends DISCONNECT [FAC(RE)] to Calling user. The Called user lifeline is present but has no messages.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant CU as Calling user + participant N as Network + participant C as Called user + + CU->>N: SETUP [FAC(CUG-CL-INV, OA, CI)] + N-->>CU: CALL PROCEEDING + N-->>CU: DISCONNECT [FAC(RE)] + C + +``` + +T1124760-90 + +Sequence diagram for Figure 1-2/Q.955 showing a call failure scenario where the destination network side checks fail. The diagram involves three lifelines: Calling user, Network, and Called user. The sequence of messages is: Calling user sends SETUP [FAC(CUG-CL-INV, OA, CI)] to Network; Network sends CALL PROCEEDING to Calling user; Network sends DISCONNECT [FAC(RE)] to Calling user. The Called user lifeline is present but has no messages. + +FIGURE 1-2/Q.955 + +**Call fails destination network side checks** + +![Sequence diagram for Figure 1-3/Q.955 showing a call failure scenario where the origination network side checks fail. The diagram involves three lifelines: Calling user, Network, and Called user. The sequence of messages is: Calling user sends SETUP [FAC(CUG-CL-INV, OA, CI)] to Network; Network sends CALL PROCEEDING to Calling user; Network sends DISCONNECT [FAC(RE)] to Calling user. The Called user lifeline is present but has no messages.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant CU as Calling user + participant N as Network + participant C as Called user + + CU->>N: SETUP [FAC(CUG-CL-INV, OA, CI)] + N-->>CU: CALL PROCEEDING + N-->>CU: DISCONNECT [FAC(RE)] + C + +``` + +T1124770-90 + +Sequence diagram for Figure 1-3/Q.955 showing a call failure scenario where the origination network side checks fail. The diagram involves three lifelines: Calling user, Network, and Called user. The sequence of messages is: Calling user sends SETUP [FAC(CUG-CL-INV, OA, CI)] to Network; Network sends CALL PROCEEDING to Calling user; Network sends DISCONNECT [FAC(RE)] to Calling user. The Called user lifeline is present but has no messages. + +FIGURE 1-3/Q.955 + +**Call fails origination network side checks** + +![Sequence diagram showing a call setup and release between a Calling user and a Network. The Calling user sends a SETUP [FAC(CUG-CL-INV, OA, CI)] message to the Network, and the Network returns a RELEASE COMPLETE [FAC(RE)] message to the Calling user. A Called user is shown but has no messages.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant CU as Calling user + participant N as Network + participant C as Called user + CU->>N: SETUP [FAC(CUG-CL-INV, OA, CI)] + N-->>CU: RELEASE COMPLETE [FAC(RE)] + +``` + +Sequence diagram showing a call setup and release between a Calling user and a Network. The Calling user sends a SETUP [FAC(CUG-CL-INV, OA, CI)] message to the Network, and the Network returns a RELEASE COMPLETE [FAC(RE)] message to the Calling user. A Called user is shown but has no messages. + +![Sequence diagram showing a call setup, proceeding, and release between a Calling user, a Network, and a Called user. The Calling user sends a SETUP [FAC(CUG-CL-INV, OA, CI)] message to the Network. The Network returns a CALL PROCEEDING message to the Calling user. The Network then sends a SETUP [FAC(CUG-CL-INV, OA, CI)] message to the Called user. The Called user returns a RELEASE COMPLETE [FAC(RE)] message to the Network. The Network then returns a DISCONNECT [FAC(RE)] message to the Calling user.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg) + +``` + +sequenceDiagram + participant CU as Calling user + participant N as Network + participant C as Called user + CU->>N: SETUP [FAC(CUG-CL-INV, OA, CI)] + N-->>CU: CALL PROCEEDING + N->>C: SETUP [FAC(CUG-CL-INV, OA, CI)] + C-->>N: RELEASE COMPLETE [FAC(RE)] + N-->>CU: DISCONNECT [FAC(RE)] + +``` + +Sequence diagram showing a call setup, proceeding, and release between a Calling user, a Network, and a Called user. The Calling user sends a SETUP [FAC(CUG-CL-INV, OA, CI)] message to the Network. The Network returns a CALL PROCEEDING message to the Calling user. The Network then sends a SETUP [FAC(CUG-CL-INV, OA, CI)] message to the Called user. The Called user returns a RELEASE COMPLETE [FAC(RE)] message to the Network. The Network then returns a DISCONNECT [FAC(RE)] message to the Calling user. + +FAC Facility information element +CUG-CL-INV CUG call invoke +RE Return error +CI CUG index +OA Outgoing access + +T1124780-90 + +*Note* – Point-to-point configuration is assumed for the called user. + +FIGURE 1-4/Q.955 + +**Call passes both originating and destination network checks and fails at the called user side** + +![Flowchart of CUG process – Outgoing call (network side). The process starts with 'CUG idle' and branches into 'Outgoing SETUP', 'Call fail (reason)', 'Called party ALERTING', and 'Called party CONNECT'. It includes decision points for 'CUG? subscription?' and 'Explicit invocation?', leading to various 'Continue (normal)' and 'CUG idle' states, or error handling steps like 'Set error value = No. 0' and 'Clear call (RE value)'. A reference 'T1124790-90' and a circled '1' with a '2' are also present.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + Start([CUG idle]) --> Outgoing_SETUP[/Outgoing SETUP/] + Start --> Call_fail_1[/Call fail (reason)/] + Start --> Called_party_ALERTING_1[/Called party ALERTING/] + Start --> Called_party_CONNECT_1[/Called party CONNECT/] + + Outgoing_SETUP --> CUG_subscription{CUG? subscription?} + CUG_subscription -- Yes --> Continue_Apply_checks[/Continue (Apply checks)/] + Continue_Apply_checks --> Outgoing_CUG([Outgoing CUG]) + Outgoing_CUG --> Called_party_ALERTING_2[/Called party ALERTING/] + Called_party_ALERTING_2 --> Continue_Normal_1[/Continue (normal)/] + Continue_Normal_1 --> CUG_idle_1([CUG idle]) + + CUG_subscription -- No --> Explicit_invocation{Explicit invocation?} + Explicit_invocation -- Yes --> Set_error[Set error value = No. 0] + Set_error --> Clear_call[/Clear call (RE value)/] + Clear_call --> Called_party_CONNECT_2[/Called party CONNECT/] + Called_party_CONNECT_2 --> Continue_Normal_2[/Continue (normal)/] + Continue_Normal_2 --> CUG_idle_2([CUG idle]) + + Explicit_invocation -- No --> Continue_Normal_3[/Continue (normal)/] + Continue_Normal_3 --> CUG_idle_3([CUG idle]) + + Called_party_CONNECT_1 --> Continue_Normal_4[/Continue (normal)/] + Continue_Normal_4 --> CUG_idle_4([CUG idle]) + + Call_fail_1 --> CUG_idle_5([CUG idle]) + + Called_party_ALERTING_1 --> Continue_Normal_5[/Continue (normal)/] + Continue_Normal_5 --> CUG_idle_6([CUG idle]) + + Called_party_CONNECT_1 --> Call_fail_2[/Call fail (reason)/] + Call_fail_2 --> 1((1)) + 1 --> 2 + +``` + +T1124790-90 + +Flowchart of CUG process – Outgoing call (network side). The process starts with 'CUG idle' and branches into 'Outgoing SETUP', 'Call fail (reason)', 'Called party ALERTING', and 'Called party CONNECT'. It includes decision points for 'CUG? subscription?' and 'Explicit invocation?', leading to various 'Continue (normal)' and 'CUG idle' states, or error handling steps like 'Set error value = No. 0' and 'Clear call (RE value)'. A reference 'T1124790-90' and a circled '1' with a '2' are also present. + +FIGURE 1-5/Q.955 (sheet 1 of 2) +CUG process – Outgoing call (network side) + +![Flowchart for CUG process – Outgoing call (network side). The process starts with a start node (1) leading to a decision 'CUG related reason?'. If 'Yes', it goes to 'Map reason to error value'. If 'No', it goes to 'Set error value = No. 8'. Both paths merge and lead to a decision 'Explicit invocation?'. If 'Yes', it goes to 'Continue (RE value)'. If 'No', it goes to a decision 'Error value = No. 20'. If 'Yes', it goes to 'Continue (Cause = No. 87)'. If 'No', it goes to 'Continue (Normal)'. All three 'Continue' paths merge and lead to the final state 'CUG idle'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + Start((1)) --> CUGRelated{CUG related reason?} + CUGRelated -- Yes --> MapReason[Map reason to error value] + CUGRelated -- No --> SetError[Set error value = No. 8] + MapReason --> Explicit{Explicit invocation?} + SetError --> Explicit + Explicit -- Yes --> ContinueRE{{Continue (RE value)}} + Explicit -- No --> Error20{Error value = No. 20} + Error20 -- Yes --> Continue87{{Continue (Cause = No. 87)}} + Error20 -- No --> ContinueNormal{{Continue (Normal)}} + ContinueRE --> Merge(( )) + Continue87 --> Merge + ContinueNormal --> Merge + Merge --> CUGIdle{{CUG idle}} + +``` + +T1124800-90 + +Flowchart for CUG process – Outgoing call (network side). The process starts with a start node (1) leading to a decision 'CUG related reason?'. If 'Yes', it goes to 'Map reason to error value'. If 'No', it goes to 'Set error value = No. 8'. Both paths merge and lead to a decision 'Explicit invocation?'. If 'Yes', it goes to 'Continue (RE value)'. If 'No', it goes to a decision 'Error value = No. 20'. If 'Yes', it goes to 'Continue (Cause = No. 87)'. If 'No', it goes to 'Continue (Normal)'. All three 'Continue' paths merge and lead to the final state 'CUG idle'. + +FIGURE 1-5/Q.955 (sheet 2 of 2) + +#### **CUG process – Outgoing call (network side)** + +![Flowchart of CUG process – Incoming call (network side). The process starts with 'CUG idle' and branches into 'Incoming SETUP (Non-CUG)', 'Incoming SETUP (CUG)', and 'Incoming SETUP (CUG + OA)'. 'Non-CUG' leads to 'Continue (Normal)' and back to 'CUG idle'. 'CUG' and 'CUG + OA' lead to 'Continue (Apply checks)' and then to 'Incoming CUG'. 'Incoming CUG' branches into 'Called party ALERTING', 'Called party CONNECT', and 'Call fall (Reason)'. 'ALERTING' and 'CONNECT' lead to a junction point labeled '1' with a '2' below it. 'Call fall (Reason)' leads to a junction point labeled '2' with a '2' below it. A second set of boxes for 'Called party ALERTING', 'Called party CONNECT', and 'Call fall (Reason)' is shown below, with arrows from the first set pointing to them. 'Call fall (Reason)' also leads to 'Continue (Normal)' and back to 'CUG idle'. Reference T1124810-90 is noted.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +graph TD + CUG_idle1{{CUG idle}} + InSETUP_NonCUG[Incoming SETUP (Non-CUG)] + InSETUP_CUG[Incoming SETUP (CUG)] + InSETUP_CUG_OA[Incoming SETUP (CUG + OA)] + Called_ALERTING1[Called party ALERTING] + Called_CONNECT1[Called party CONNECT] + Call_fall1[Call fall (Reason)] + Continue_NonCUG[Continue (Normal)] + Continue_CUG[Continue (Apply checks)] + Continue_fall1[Continue (Normal)] + CUG_idle2{{CUG idle}} + InCUG{{Incoming CUG}} + Called_ALERTING2[Called party ALERTING] + Called_CONNECT2[Called party CONNECT] + Call_fall2[Call fall (Reason)] + Junction1((1)) + Junction2((2)) + + CUG_idle1 --- InSETUP_NonCUG + CUG_idle1 --- InSETUP_CUG + CUG_idle1 --- InSETUP_CUG_OA + CUG_idle1 --- Called_ALERTING1 + CUG_idle1 --- Called_CONNECT1 + CUG_idle1 --- Call_fall1 + + InSETUP_NonCUG --> Continue_NonCUG + Continue_NonCUG --> CUG_idle2 + + InSETUP_CUG --> Continue_CUG + InSETUP_CUG_OA --> Continue_CUG + Continue_CUG --> InCUG + + InCUG --> Called_ALERTING2 + InCUG --> Called_CONNECT2 + InCUG --> Call_fall2 + + Called_ALERTING1 --> Junction1 + Called_CONNECT1 --> Junction1 + Junction1 --> Called_ALERTING2 + Junction1 --> Called_CONNECT2 + + Call_fall1 --> Junction2 + Call_fall2 --> Junction2 + Junction2 --> Continue_fall1 + Continue_fall1 --> CUG_idle2 + + subgraph BottomRow [ ] + Called_ALERTING2 + Called_CONNECT2 + Call_fall2 + end + +``` + +T1124810-90 + +Flowchart of CUG process – Incoming call (network side). The process starts with 'CUG idle' and branches into 'Incoming SETUP (Non-CUG)', 'Incoming SETUP (CUG)', and 'Incoming SETUP (CUG + OA)'. 'Non-CUG' leads to 'Continue (Normal)' and back to 'CUG idle'. 'CUG' and 'CUG + OA' lead to 'Continue (Apply checks)' and then to 'Incoming CUG'. 'Incoming CUG' branches into 'Called party ALERTING', 'Called party CONNECT', and 'Call fall (Reason)'. 'ALERTING' and 'CONNECT' lead to a junction point labeled '1' with a '2' below it. 'Call fall (Reason)' leads to a junction point labeled '2' with a '2' below it. A second set of boxes for 'Called party ALERTING', 'Called party CONNECT', and 'Call fall (Reason)' is shown below, with arrows from the first set pointing to them. 'Call fall (Reason)' also leads to 'Continue (Normal)' and back to 'CUG idle'. Reference T1124810-90 is noted. + +FIGURE 1-6/Q.955 (sheet 1 of 2) + +**CUG process – Incoming call (network side)** + +![Flowchart of the CUG process – Incoming call (network side). The process starts with a start node (1) leading to a 'Continue (Normal)' block. This block leads to a decision diamond 'RE component included?'. If 'Yes', it goes to 'Map error to reason value', then to a 'Continue (Reason)' block, and finally to the 'CUG idle' end node. If 'No', it goes to another 'Continue (Normal)' block, which also leads to the 'CUG idle' end node. A reference 'T1124820-90' is noted at the bottom right of the flowchart.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + Start((1)) -- 1 --> ContinueNormal1[/Continue (Normal)/] + ContinueNormal1 --> Decision{RE component included?} + Decision -- Yes --> MapError[Map error to reason value] + MapError --> ContinueReason[/Continue (Reason)/] + ContinueReason --> End([CUG idle]) + Decision -- No --> ContinueNormal2[/Continue (Normal)/] + ContinueNormal2 --> End + +``` + +T1124820-90 + +Flowchart of the CUG process – Incoming call (network side). The process starts with a start node (1) leading to a 'Continue (Normal)' block. This block leads to a decision diamond 'RE component included?'. If 'Yes', it goes to 'Map error to reason value', then to a 'Continue (Reason)' block, and finally to the 'CUG idle' end node. If 'No', it goes to another 'Continue (Normal)' block, which also leads to the 'CUG idle' end node. A reference 'T1124820-90' is noted at the bottom right of the flowchart. + +FIGURE 1-6/Q.955 (sheet 2 of 2) + +#### **CUG process – Incoming call (network side)** + +## ANNEX A + +(to § 1 of Recommendation Q.955) + +### **Diagrammatic description of coding requirements** + +This annex gives examples on the detailed coding of the following components: + +- invoke component; +- Return error component. + +*Note* – The formal description of this component is defined in § 1.4 of this Recommendation which takes precedence over this annex in case of discrepancy. The structure and encoding is only one possible version and the full range of legal encodings is given in the formal definition in § 1.4. + +#### A.1.1 *Invoke component* + +| | | | +|----------------------------------|-----------------|----------------------------| +| Invoke component type | 1 0 1 0 0 0 0 1 | context-spec, const, 1 | +| Invoke component length | 0 0 0 0 1 1 1 1 | (for example) | +| Invoke component contents: | | | +| Invoke identifier type | 0 0 0 0 0 0 1 0 | univ, prim, 2 (INTEGER) | +| Invoke identifier length | 0 0 0 0 0 0 0 1 | | +| Invoke identifier contents | XXXXXXXX | invoke id value | +| | | | +| OPERATION type | 0 0 0 0 0 0 1 0 | univ, prim, 2 (INTEGER) | +| OPERATION length | 0 0 0 0 0 0 0 1 | | +| OPERATION contents | 0 0 0 0 0 0 1 0 | CUG Call | +| | | | +| SEQUENCE type | 0 0 1 1 0 0 0 0 | univ, const, 16 (SEQUENCE) | +| SEQUENCE length | 0 0 0 0 0 1 1 1 | (for example) | +| SEQUENCE contents: | | | +| Outgoing access request type | 1 0 0 0 0 0 0 1 | context-spec, prim, 1 | +| Outgoing access request length | 0 0 0 0 0 0 0 1 | | +| Outgoing access request contents | 1 1 1 1 1 1 1 1 | Error! | +| | 0 0 0 0 0 0 0 0 | (implied BOOLEAN) | +| | | | +| CUG index type | 1 0 0 0 0 0 1 0 | context-spec, prim, 2 | +| CUG index length | 0 0 0 0 0 0 1 0 | (for example) | +| CUG index contents | XXXXXXXX | (implied INTEGER) | +| CUG index contents | XXXXXXXX | | +| | | | + +#### A.1.2 Return error component + +| | | | +|-------------------------------|--------------------------------|----------------------------------------------------------------| +| Return error component type | 1 0 1 0 0 0 1 1 | context-spec, const, 3 | +| Return error component length | 0 0 0 0 0 1 1 0 | | +| Return error component cont: | | | +| Invoke identifier type | 0 0 0 0 0 0 1 0 | univ, prim, 2 (INTEGER) | +| Invoke identifier length | 0 0 0 0 0 0 0 1 | | +| Invoke identifier contents | XXXXXXXX | invoke id value | +| Error type | 0 0 0 0 0 0 1 0 | univ, prim, 2 (INTEGER) | +| Error length | 0 0 0 0 0 0 0 1 | | +| Error contents | 0 0 0 0 0 0 0 0 | (0) User not subscribed | +| | 0 0 0 0 1 0 0 0 | (8) Basic service not provided | +| | 0 0 0 1 0 0 0 0 | (16) Invalid or unregistered CUG index | +| | 0 0 0 1 0 0 0 1 | (17) Requested basic service violates CUG constraints | +| | 0 0 0 1 0 0 1 0 | (18) Outgoing calls barred within CUG | +| | 0 0 0 0 0 0 1 1 | (19) Incoming calls barred within CUG | +| | 0 0 0 1 0 1 0 0 | (20) User not member of CUG | +| | 0 0 0 1 0 1 0 1 | (21) Inconsistency in designated facility and subscriber class | +| | All other values are reserved. | | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.955.3-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.955.3-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..362050fb2ca224e525daa54705014a0b235a86dc --- /dev/null +++ b/marked/Q/T-REC-Q.955.3-199303-I_PDF-E/raw.md @@ -0,0 +1,2327 @@ + + +![ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.955** + +(03/93) + +**DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 +STAGE 3 DESCRIPTION FOR SUPPLEMENTARY +SERVICES USING DSS 1** + +--- + +**STAGE 3 DESCRIPTION FOR COMMUNITY +OF INTEREST SUPPLEMENTARY SERVICES +USING DSS 1 +CLAUSE 3 – MULTI-LEVEL PRECEDENCE +AND PREEMPTION (MLPP)** + +**ITU-T Recommendation Q.955** + +(Previously “CCITT Recommendation”) + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.955, clause 3, was prepared by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +# --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms “CCITT, CCIR or IFRB” or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|---------------------------------------------------------|-------------| +| 3 Multi-level precedence and preemption (MLPP)..... | 1 | +| 3.1 Definition..... | 1 | +| 3.2 Description..... | 1 | +| 3.3 Operational requirements..... | 2 | +| 3.4 Coding requirements..... | 4 | +| 3.5 Signalling requirements..... | 8 | +| 3.6 Interactions with other supplementary services..... | 16 | +| 3.7 Interactions with other networks..... | 20 | +| 3.8 Signalling flows..... | 25 | +| 3.9 Parameter values – timers..... | 29 | + + + +# STAGE 3 DESCRIPTION FOR “COMMUNITY OF INTEREST” SUPPLEMENTARY SERVICES, USING DSS 1 + +*(Helsinki 1993)* + +# 3 Multi-level precedence and preemption (MLPP) + +## 3.1 Definition + +The Multi-level Precedence and Preemption (MLPP) supplementary service provides prioritized call handling service. This supplementary service has two parts – precedence and preemption. Precedence involves assigning a priority level to a call. Preemption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resources. Users in networks that do not support this service will not be affected by this service. + +The stage 1 description of the MLPP supplementary service is contained in 3/I.255. + +The stage 2 description of the MLPP supplementary service is contained in 3/Q.85. + +## 3.2 Description + +### 3.2.1 General description + +The MLPP supplementary service is provided as a network provider's option to a domain of a network. The domain can be the whole network or a subset of the network. The MLPP supplementary service applies to all network resources in the domain that are in common use. The maximum precedence level of a subscriber is set at the subscription time by the service provider based on the subscriber's need. The subscriber may select a precedence level up to and including the maximum subscribed to precedence level on a per call basis. + +Precedence calls (calls using the MLPP supplementary service that have a higher precedence than the lowest level of precedence) that are not responded to by the called party (e.g. call unanswered and/or unacknowledged, called party busy with call of equal or higher precedence, or called party busy and non-preemptable) are diverted to a predetermined alternate party. This alternate party may be another subscriber or a network operating position. + +Preemption may take one of two forms. First, the called party may be busy with a lower precedence call which must be preempted in favor of completing the higher precedence call from the calling party. Second, the network resources may be busy with calls some of which are of lower precedence than the call requested by the calling party. One or more of these lower precedence calls must be preempted to complete the higher precedence call. There are three characteristics of preemption: + +- 1) Any party whose connection was terminated (whether that resource is reused or not) must receive a distinctive preemption notification. +- 2) Any called party of an active call that is being preempted by a higher precedence call should be required to acknowledge the preemption before being connected to the new calling party. +- 3) When there are no idle resources, preemption of the lowest lower level of precedence resources shall occur. + +A call can be preempted any time after the precedence level of the call has been established and before call clearing has begun. + +The MLPP supplementary service is not intended to provide preemption of users that do not subscribe to the MLPP supplementary service. The service provides for preemption of calls within the MLPP domain, which consists of the resources belonging to the users that subscribe to the MLPP supplementary service. In other words, calls that are originated by or made to non-MLPP users will not be preempted. Calls that are originated by MLPP subscribers may be preempted by calls of higher precedence only in networks that support this service. + +### 3.2.2 Specific terminology + +The following specific terminology is used in this Recommendation: + +*Precedence* is the priority associated with a call. + +A *precedence call* is a call using the MLPP supplementary service with precedence level higher than the lowest level of precedence. + +An *MLPP call* is a call using the MLPP supplementary service that has a precedence level established and is either being setup or is setup. In the DSS 1, an MLPP call is a call from an MLPP subscriber for which a SETUP has been sent but no DISCONNECT has been sent or received (i.e. call states U1 through U10). + +A *preempting call* is a call using the MLPP supplementary service with a precedence level higher than the lowest (i.e. ROUTINE) level of precedence, for which a call setup request has been received at the exchange. + +*User* is a DSS 1 protocol entity at the user side of the user-network interface. A *user* is identified by a terminal, which is addressed by its ISDN number. A *called user* is considered *busy* if he is on an active call (i.e. in call state U10). + +*Network* is a DSS 1 protocol entity at the network side of the user-network interface. + +A *preemptable circuit* is a circuit that is active with or reserved for an MLPP call: (1) within the same domain as the preempting call and (2) with a lower precedence than the preempting call. A busy or reserved circuit for which a precedence level has not been specified is not a preemptable circuit. + +A *preemption initiating exchange* is the exchange that is congested (i.e. no idle circuits) and has received a preempting call setup. + +*Congestion* has been encountered when it is determined that all circuits capable of routing the MLPP call are busy (i.e. no idle circuits.) + +*Response Timer $T_K$* is as defined in 3/Q.85. The length of this timer is in the range of 4-30 seconds. + +An *alternate party* is as defined in 3/Q.85. + +*OE (Originating Exchange)* is an exchange that is directly connected to a calling user. + +*DE (Destination Exchange)* is an exchange that is directly connected to a called user. + +The “*Invoke*”, “*Return Result*”, and “*Return Error*” components shall be as defined in 8.2.3.1.1/Q.932. + +### 3.2.3 Qualifications on the applicability to telecommunication services + +This supplementary service is considered meaningful when applied to the Telephony Teleservice, speech, 3.1 kHz audio, 7 kHz audio, and 64 kbit/s unrestricted bearer services. Furthermore, it may be meaningful when applied to other services. + +### 3.2.4 State definitions + +No additional call states, beyond those specified in Recommendations Q.931 and Q.932, are identified for the MLPP service. + +## 3.3 Operational requirements + +### 3.3.1 Provision/withdrawal + +For a given ISDN number, a maximum authorized precedence level may be subscribed to for each service or collectively for all services. + +#### 3.3.1.1 Terminal options + +A user, as identified by a terminal, has the following subscription options for the MLPP supplementary service: + +- 1) Maximum authorized precedence level (see Note 1): + - a) 0 (FLASH OVERRIDE – highest) + - b) 1 (FLASH) + - c) 2 (IMMEDIATE) + - d) 3 (PRIORITY) + - e) 4 (ROUTINE – lowest). +- 2) Alternate party: + - a) yes + - network operating position + - alternate party directory number + - b) no. +- 3) Access resources non-preemptable (see Note 2): + - a) yes + - b) no. + +###### NOTES + +1 A call of higher precedence level can preempt calls of lower precedence. For example, a FLASH call can preempt IMMEDIATE, PRIORITY, or ROUTINE calls. + +2 A user having this option will not experience preemption of calls by higher precedence calls, if the cause for preemption would be due to called party busy condition. However, the user may still experience preemption of calls due to a lack of network resources other than the user's own access resources. + +Terminal equipment invoking MLPP supplementary service should be able to indicate the precedence level of the call in the SETUP message and should support Cause values: #8, "preemption" and #46, "precedence call blocked". + +Terminal equipment that receive MLPP calls, including that of the alternate party, should support the Hold and Retrieve functions, as defined in 6.2.1/Q.932, Cause value: #8, "preemption". Terminal equipment receiving MLPP calls do not have to subscribe to the call hold supplementary service. + +#### 3.3.1.2 Network options + +As described in MLPP supplementary service Recommendations I.255.3 (for stage 1) and 3/Q.85 (for stage 2). + +### 3.3.2 Requirements on the originating network side + +Notification to the calling, called, and preempted users (as a result of preemption in the network or access) shall be conveyed in call control messages using Cause #8 and #46 in the Cause information element, as described in this Recommendation. + +Notification to the calling user of delay in call setup shall be conveyed in the NOTIFY message using notification description "0 0 0 1 0 0" in the Notification indicator information element, as described in this Recommendation. + +Notification to all conferees of served user preemption shall be conveyed in the NOTIFY message using notification description "1 0 0 1 1 1" in the Notification indicator information element, as described in this Recommendation. + +Notification to the remaining parties of a three way conversation that conference is disconnected as a result of preemption of one of the two calls, shall be conveyed in the NOTIFY or DISCONNECT message using notification description "1 0 0 1 1 0 0" in the Notification indicator information element, as described in this Recommendation. + +### 3.3.3 Requirements in the network + +This subclause is not applicable to DSS 1. + +### **3.3.4 Requirements on the terminating network side** + +Notification to the calling, called, and preempted users (as a result of preemption in the network or access) shall be conveyed in call control messages using Cause #s 8 and #46 in the Cause information element, as described in this Recommendation. + +## **3.4 Coding requirements** + +### **3.4.1 Messages** + +The following messages are applicable to the operation of the MLPP supplementary service: SETUP, ALERTING, NOTIFY, REGISTER, FACILITY, HOLD, HOLD ACKNOWLEDGE, HOLD REJECT, DISCONNECT, RELEASE, and RELEASE COMPLETE. + +The SETUP, ALERTING, NOTIFY, DISCONNECT, RELEASE, and RELEASE COMPLETE messages shall be as defined in 3.3.1/Q.931. For the SETUP, NOTIFY, and DISCONNECT messages the following changes are required. + +The SETUP message will contain the Facility information element. In addition, it shall contain the optional Calling party number, Called party number, and Channel identification information elements as mandatory information elements. The NOTIFY message shall contain the Notification indicator information element to indicate delay in call setup, as described in the MLPP procedure. The DISCONNECT message shall include the Cause information element, coded as described in this Recommendation. + +The FACILITY message shall contain the Return Result or Return Error components in its Facility information element when it is sent in response to the REGISTER message that shall be used to invoke an MLPP DSS 1 Look-ahead For Busy (LFB) query. The RELEASE COMPLETE message shall be used to terminate the signalling association created by the REGISTER message. + +The REGISTER, FACILITY, HOLD, HOLD ACKNOWLEDGE, and HOLD REJECT messages shall be as defined in 7.1/Q.932. The REGISTER message shall contain the Bearer capability, Calling party number, Called party number, and Channel identification information elements encapsulated within the Invoke component of the Facility information element. The HOLD message shall also contain the Cause information element, coded as appropriate to the MLPP procedure. + +### **3.4.2 Codesets** + +All information elements are in codeset 0. Cause values #8 and #46, contained in the Cause information element, are proposed codeset 0 values. + +### **3.4.3 Information elements** + +The following information elements are applicable. + +#### **3.4.3.1 Facility information element** + +For the functional protocol, the Facility information element, as described in 8.2.2/Q.932, shall be used for three MLPP operations, mLPPCallpreemption with operation value 26 (for management of the circuit occupied by the to be preempted call), mLPPCallrequest (for MLPP call) with operation value 25 and mLPPFBquery [for MLPP Look-ahead for Busy (LFB) query] with operation value 24. The MLPP operations and errors are defined in 3.4. + +#### **3.4.3.2 Cause Information Element** + +For indicating the preemption of the call in the network and in the access, the Cause information element, as described in 4.5.12/Q.931, shall be used with the two proposed codepoints for cause values described in Table 3-1. + +TABLE 3-1/Q.955 + +##### **Cause information element** + +| Number | Label | Meaning | +|--------|-------------------------|-----------------------------------------------------------------------------------------------| +| 8 | Preemption | No preemptable circuit or called user is busy with a call of equal or higher precedence level | +| 46 | Precedence call blocked | | + +#### **3.4.3.3 Notification indicator information element** + +For indicating call completion delay; conference disconnected, preemption; and for indicating conference floating, served user preempted, the Notification indicator information element, as described in 4.5.21/Q.931, shall be used with the notification descriptions, as described in Table 3-2. + +TABLE 3-2/Q.955 + +##### **Notification indicator information element** + +| Notification Description (Octet 3) | | +|------------------------------------|-------------------------------------------| +| Bits | | +| 7 6 5 4 3 2 1 | | +| 0 0 0 0 1 0 0 | Call completion delay | +| 1 0 0 1 1 1 1 | Conference floating served user preempted | +| 1 0 0 1 1 0 0 | Conference disconnected, preemption | + +### **3.4.4 Definition of operations and errors** + +The definition of operations and errors required for the MLPP supplementary service using the ASN.1, as specified in Recommendation X.208 and using the OPERATION and ERROR macros, as defined in Figure 4/X.219, is in Table 3-3. + +TABLE 3-3/Q.955 + +#### **Definition of operations and errors** + +| | | +|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| -- Begin MLPP-operations definitions | | +| MLPP-operations{ccitt recommendation q 955 mlpp (3) operations-and-errors(1)} | | +| DEFINITIONS | ::= | +| BEGIN | | +| EXPORTS | mLPPLFBquery, mLPPCallrequest, mLPPCallpreemption, unauthorizedPrecedenceLevel; | +| IMPORTS | OPERATIONS, ERRORS | +| | FROM Remote-Operation-Notation | +| | {joint-iso-ccitt remote-operations(4) notation(0)} | +| | userNotSubscribed, rejectedByNetwork | +| | FROM General-Error-List | +| | {ccitt recommendation q 950 general-error-list(1)} | +| | Q931InformationElement | +| | FROM Embedded-Q931-Types | +| | {ccitt recommendation q 932 embedded-q931-types(5)}; | + +TABLE 3-3/Q.955 (continued) + +#### Definition of operations and errors + +| | | | | +|----------------------------------------|---------------------------------------------|--------------------------------------------------------------------------|----------------------------------------------| +| -- Begin mLPPLFBquery operation | | | | +| MLPP_LFBquery | OPERATION | MLPP_LFB_arg | | +| | ARGUMENT | MLPP_LFB_resp | | +| | RESULT | | {userNotSubscribed,rejectedByNetwork} | +| | ERRORS | | | +| MLPP_LFB-arg | ::= SEQUENCE | {MLPP_params, IE_arg} | | +| MLPP_params | ::= SEQUENCE | {Prec_level, LFB_Indictn, MLPP_Svc_Domn} | | +| Prec_level | ::= ENUMERATED | { | | +| | | flashOverride(0), flash(1), immediate(2), priority(3), routine(4) | | +| | | } | | +| | | -- Prec_level identifies the precedence level of the MLPP call. | | +| LFB_Indictn | ::= ENUMERATED | { | | +| | | lfbAllowed(0), lfbNotAllowed(1), pathReserved(2) | | +| | | } | | +| | | -- LFB_Indictn is coded for values, as indicated. | | +| MLPP_Svc_Domn | ::= OCTET STRING (size(5)) | | | +| | | -- Initial two octets provide the International ID, while the | | +| | | -- following three octets provide the MLPP Domain | | +| | | -- identification. | | +| IE_arg | ::= Q931InformationElement | | | +| | | -- Bearer capability, Calling party number, Called party | | +| | | -- number, and Channel identification information elements in | | +| | | -- the IE_arg shall be as defined in Q.931. | | +| MLPP_LFB_resp | ::= SEQUENCE {StatusQuery, Location} | | | +| | | -- The MLPP DSS1 LFB query response contains two | | +| | | -- parameters, StatusQuery and Location. | | +| StatusQuery | ::= ENUMERATED | { | | +| | | success(1), | | +| | | -- Many cases as described in the optional MLPP LFB | | +| | | failure(2), | | +| | | -- Many cases as described in the MLPP procedure with LFB | | +| | | -- option. | | +| | | bearerCapabilityNotAuthorized(3), | | +| | | -- bearer capability check failure, not authorized | | +| | | bearerCapabilityNotImplemented(4), | | +| | | -- bearer capability check failure, not implemented | | +| | | bearerCapabilityNotAvailable(5), | | +| | | -- bearer capability check failure, not available | | +| | | pathReservationDenied(6) | | +| | | -- circuit cannot be reserved at the far end | | +| | | } | | + +TABLE 3-3/Q.955 (concluded) + +#### Definition of operations and errors + +| | | +|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | ::= Q931InformationElement
-- a bit string which conforms to Octect 3 of the Cause
-- information element as defined in Q.931, except that bit 8 is
-- marked as a spare.
-- End of mLPPLFBquery operation.
-- Begin mLPPCallrequest operation | +| MLPPCallrequest | OPERATION MLPP_params
ARGUMENT StatusRequest
RESULT {userNotSubscribed, rejectedByNetwork,
ERRORS unauthorizedPrecedenceLevel} | +| StatusRequest | ::= ENUMERATED
{
successCalledUserMLPPSubscriber(1) ,
-- Called user is an MLPP subscriber.
successCalledUserNotMLPPSubscriber(2) ,
-- Called user is not an MLPP subscriber.
failureCaseA(3) ,
-- MLPP call from the calling user is a precedence call and
-- cannot be completed.
failureCaseB(4) ,
-- MLPP call from the calling user or MLPP call between two
-- MLPP subscribers experiences preemption.
} | +| | -- End mLPPCallrequest operation.
-- Begin mLPPCallpreemption operation | +| MLPPCallpreemption | OPERATION
ARGUMENT Preempt_params
RESULT
ERRORS | +| Preempt_params | ::= ENUMERATED
{
circuitReservedForReuse(1) ,
-- Circuit of the to be preempted call is reserved for reuse
circuitNotReservedForReuse(2) ,
-- Circuit of the to be preempted call is not reserved for
-- reuse
} | +| | -- End mLPPCallpreemption operation | +| UnauthorizedPrecedenceLevel | ::= ERROR
-- An indication that the calling user has exceeded the authorized, maximum
-- precedence level. | +| mLPPLFBquery MLPLFBquery | ::= 24 | +| mLPPCallrequest MLPPCallrequest | ::= 25 | +| mLPPCallpreemption MLPPCallpreemption | ::= 26 | +| unauthorizedPrecedenceLevel UnauthorizedPrecedenceLevel | ::= 44 | +| END | -- End MLPP-operations. | + +## **3.5 Signalling requirements** + +### **3.5.1 Activation/deactivation/registration** + +Not applicable. + +### **3.5.2 Invocation and operation** + +Invocation and operation without an optional MLPP DSS 1 LFB query is illustrated in Figures 3-1 through 3-3 and described in 3.5.2.1. + +#### **3.5.2.1 MLPP DSS 1 procedure without LFB option** + +##### **3.5.2.1.1 Procedure at originating exchange/originating user side** + +###### **3.5.2.1.1.1 Normal operation** + +The calling user shall implicitly invoke the MLPP supplementary service by sending a SETUP message to the network. + +The calling user shall explicitly invoke the MLPP supplementary service by including the Facility information element in the SETUP message sent to the network. The Invoke component of the mLPPCallrequest operation within the Facility information element contains the precedence level (Prec\_level), LFB Indication (LFB\_Indictn), and MLPP Service Domain (MLPP\_Svc\_Domn). The precedence level inserted by the user may be up to and including the maximum subscribed to precedence level on a per call basis. The LFB Indication and MLPP Service Domain values are set according to user subscription options. + +Upon receipt of a SETUP message for an MLPP service call, the originating exchange shall do the following: + +- 1) If the Facility information element is not present in the SETUP message for a call invoking MLPP supplementary service (i.e. from an MLPP subscriber) and the calling user has subscribed to the MLPP supplementary service for the bearer capability in the SETUP message the originating exchange shall formulate a Facility information element with a precedence level equal to ROUTINE by coding Prec\_level to “routine”. +- 2) If the Facility information element is present in the SETUP message for a call invoking the MLPP supplementary service, it shall validate the precedence level to insure that it falls within the range that the calling user is authorized. + +In both cases in items 1) and 2) above, the originating exchange shall also set appropriate codes for LFB Indication (LFB\_Indictn) and MLPP Service Domain (MLPP\_Svc\_domn) in the Facility information element. If the LFB option is supported by the network and subscribed to for the precedence level in the SETUP message, the LFB\_Indictn is coded “lfbAllowed”. If the LFB option is not supported by the network or if the LFB option is supported by the network but not subscribed to for the precedence level in the SETUP message, LFB\_Indictn is coded “lfbNotAllowed”. + +- 3) Upon formulating the Facility information element with a precedence level equal to ROUTINE or receiving the Facility information element with a valid precedence level, the originating exchange shall mark the circuit busy with the precedence level and MLPP Service Domain of the outgoing MLPP call, send the CALL PROCEEDING message toward the calling user and a Setup Indication toward the network, and wait for the network response. Upon receipt of the CALL PROCEEDING message, the calling user shall mark the outgoing circuit busy with the precedence level and MLPP Service Domain of the outgoing MLPP call. Upon receiving an Alerting Indication that user alerting is initiated at the called user, the originating exchange shall check to determine if the called user is an MLPP subscriber or not. If the called user is not an MLPP subscriber, the originating exchange shall unmark the previously marked circuit for the MLPP call; if the called user is an MLPP subscriber, the originating exchange shall retain + +marking on the previously marked circuit for the MLPP call. Then, in both cases above, the MLPP call setup will continue, as described in 5.1/Q.931, except that upon receipt of the ALERTING message, the calling user shall unmark the previously marked circuit if the StatusRequest in the Return Result component of its Facility information element is coded to “successCalledUserNotMLPPSubscriber”. + +###### **3.5.2.1.1.2 Exceptional Procedures** + +- 1) Upon receipt of a SETUP message for an MLPP service call, the originating exchange shall check to determine if the network supports the invoked MLPP service. If this check is not satisfied, the Facility information element shall be ignored or not formulated and the MLPP call setup shall continue as if it were a basic call, as described in 5.1/Q.931, except that the first call control message shall contain the Return Error component of the mLPPCallrequest operation in its Facility information element, which is coded to “rejectedByNetwork”. +- 2) If the Facility information element is present in the SETUP message for a call invoking the MLPP supplementary service (i.e. from an MLPP subscriber) and if the calling user exceeds the maximum subscribed precedence level, the originating exchange shall return a RELEASE COMPLETE message toward the calling user, which contains the Return Error component of the mLPPCallrequest operation in its Facility information element with Error “unauthorizedPrecedenceLevel”. +- 3) If the Facility information element is not present in the SETUP message for a call invoking MLPP supplementary service (i.e. from an MLPP subscriber) and if the calling user has not subscribed to the MLPP supplementary service for the bearer capability in the SETUP message, the originating exchange shall reject the call by sending a RELEASE COMPLETE message toward the calling user, which contains the Return Error component of the mLPPCallrequest operation in its Facility information element with Error “userNotSubscribed”. +- 4) The precedence call may not be completed as a result of a network exchange being busy with calls of equal or higher precedence (on the path toward the called user) or no preemptable circuit at the called interface. In this case, upon receipt of the Release Indication with cause value #46, “precedence call blocked” from the network, the originating exchange shall return a DISCONNECT message toward the calling user with the same cause value to clear the call. The DISCONNECT message shall also contain the Return Result component of the mLPPCallrequest operation in its Facility information element with StatusRequest coded to “failureCaseA”, indicating call failure. +- 5) The precedence call may not be completed as a result of called user, who has not subscribed to alternate party, is busy with either: (a) a call of equal or higher precedence than the calling user and no call completion supplementary services (e.g. call waiting) or call offering supplementary services (e.g. call forwarding busy) are available or (b) non-preemptable access resources and no call completion supplementary services (e.g. call waiting) or call offering supplementary services (e.g. call forwarding busy) are available. In this case, upon receipt of the Release Indication with cause value #46, “precedence call blocked” from the network, the originating exchange shall return a DISCONNECT message toward the calling user with the same cause value to clear the call. The DISCONNECT message shall also contain the Return Result component of the mLPPCallrequest operation in its Facility information element with StatusRequest coded to “failureCaseA”, indicating call failure. +- 6) An MLPP call may be preempted as a result of preemption in the network or access. In this case, upon receipt of the Release Indication with cause value #8, “preemption” from the network, the originating exchange shall return a DISCONNECT message toward the calling user with the same Cause to clear the call. The DISCONNECT message shall also contain the Return Result component of the mLPPCallrequest operation in its Facility information element with StatusRequest coded to “failureCaseB”, indicating call failure. + +##### 3.5.2.1.2 Procedure at destination exchange/destination user side + +###### 3.5.2.1.2.1 Normal operation + +Upon receipt of the Setup Indication, the destination exchange that serves the called user shall mark the incoming circuit (identified by the Channel identification information element within the SETUP message) busy at the precedence level and MLPP Service Domain of the MLPP call. Then: + +If LFB Indication was set to “pathReserved”, the network shall stop timer $T_{LR}$ which it had started upon marking a circuit to the called user as reserved (see 3.5.2.2.2.1). Then: + +- If the reserved (or marked) circuit to the called user (as identified by a match between the Calling Party Number within the Setup Indication and Calling Party Numbers of the “reserved” circuits) is found and it is not idle, and if the called user is busy, the procedure in item 3) b) (1) (a) below shall be followed; otherwise, the procedure in item 2) b) (1) below shall be followed. +- If the reserved circuit to the called user is found and it is idle, it shall be marked with the precedence level and MLPP Service Domain of the incoming MLPP call, and the procedure in item 1) b) below shall be followed. +- If the reserved circuit to the called user is not found, the LFB Indication is coded to “lfbNotAllowed”, and the procedure in the items below shall be followed. + +If LFB Indication was not set to “pathReserved”, the procedure in the items below shall be followed. + +- 1) If the called user is idle and an idle circuit to deliver the call to the called user exists, it shall mark the idle circuit busy at the precedence level and MLPP Service Domain of the incoming MLPP call. Then: + - a) If the incoming call is a ROUTINE call, a SETUP message shall be sent to the called user, which contains the Invoke component of the mLPPCallrequest operation in its Facility information element. The called user shall respond with: a CALL PROCEEDING message and mark the idle circuit busy at the precedence level and MLPP Service Domain of the incoming MLPP call or RELEASE COMPLETE message. Upon receipt of a CALL PROCEEDING message from the called user indicating that compatibility requirements have been satisfied, the procedure in item 4) shall be followed; otherwise, upon receipt of a RELEASE COMPLETE message from the called user with cause value #88, “incompatible destination”, indicating that compatibility requirements have not been satisfied, the network shall unmark the previously marked circuit and clear the incoming call with the same cause value. + - b) If the incoming call is a precedence call, a SETUP message shall be sent to the called user, which contains the Invoke component of the mLPPCallrequest operation in its Facility information element. The called user shall respond with: a CALL PROCEEDING message and mark the idle circuit busy at the precedence level and MLPP Service Domain of the incoming MLPP call or a RELEASE COMPLETE message. Upon receipt of a CALL PROCEEDING message from the called user, indicating that compatibility requirements have been satisfied, the following procedure will be followed; otherwise, upon receipt of a RELEASE COMPLETE message from the called user with cause value #88, “incompatible destination”, indicating that compatibility requirements have not been satisfied, the network shall unmark the previously marked circuit and continue the preempting call setup employing the procedure in item 3) b) (1) (b), items 1) through 3). +- (1) If an alternate party is subscribed to, then: + - (a) Upon receipt of ALERTING message, sent by the called user, indicating that the called user has been notified of the precedence call, the network shall start timer $T_K$ . The ALERTING message shall contain the Return Result component of the mLPPCallrequest operation in its Facility information element. Then, the destination exchange shall check the StatusRequest to determine if the called user is an MLPP subscriber. If the called user is *not* an MLPP subscriber (as indicated by StatusRequest coded to “successCalledUserNotMLPPSubscriber”), the destination exchange shall unmark the previously marked circuit for the MLPP call; if the called user is an MLPP subscriber (as indicated by StatusRequest coded to “successCalledUserMLPPSubscriber”), the destination exchange shall retain marking on the previously marked circuit for the MLPP call. If the called user responds with a CONNECT message before the expiry of timer $T_K$ (indicating called user acceptance of preemption), the network shall stop timer $T_K$ and the network shall complete the MLPP call setup, as described in 5.2.7/Q.931. If no CONNECT message + +is received from the called user before the expiry of timer $T_K$ , the network shall stop timer $T_K$ and the network shall divert the precedence call to the alternate party, using the procedures as described in 3/Q.952 for the call forwarding no reply supplementary service. The setup sent to the alternate party shall contain: the precedence level and MLPP Service Domain of the diverted precedence call, LFB Indication set to "IfbNotAllowed", and the reason for redirection = Call Forwarding No Reply. + +- (b) If no ALERTING message is received, the network shall divert the precedence call to the alternate party, using the procedures as described in 3/Q.952 for the call forwarding no reply supplementary service. The setup sent to the alternate party shall contain: the precedence level and MLPP Service Domain of the diverted precedence call, LFB Indication set to "IfbNotAllowed", and the reason for redirection = Call Forwarding No Reply. + +- (2) If no alternate party is subscribed to, then the procedure in item 4) shall be followed. + +- 2) If the called user is idle, but an idle circuit to deliver the call to the called user does not exist, then: + +- a) If the call is a ROUTINE call, clearing of the calling user shall be initiated by sending a Reject Indication to the network with cause value #34, "no circuit/channel available". + +- b) If the call is a precedence call and the existing MLPP call is at lower precedence, then: + +- (1) If preemptable access resources exist, the network shall mark the circuit (carrying the existing MLPP call) with the precedence level and MLPP Service Domain of the incoming call and the network shall send a SETUP message, which contains the Invoke component of the mLPPCallrequest operation in its Facility information element, to the called user. The called user may respond with a CALL PROCEEDING message or a RELEASE COMPLETE message. Then: + +Upon receipt a CALL PROCEEDING message from the called user, indicating that compatibility requirements have been satisfied, the network shall clear the existing MLPP call to the busy user (i.e. "other user") on the called interface toward: (a) the busy user, using a DISCONNECT message and (b) the network with cause value #8 and the preempting call setup continues employing the procedure in item 5). The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitReservedForReuse". + +Upon receipt of a RELEASE COMPLETE message from the called user with cause value #88, "incompatible destination", indicating that compatibility requirements have not been satisfied, the network shall unmark the previously marked circuit and continue the preempting call setup employing the procedure in item 3) b) (1) (b), items 1) through 3) except that the "called user" is to be interpreted as the "other user" under consideration on the called interface. + +- (2) If preemptable access resources do not exist, the network shall continue the preempting call setup employing the procedure in item 3) b) (1) (b), items 1) through 3) except that the "called user" is to be interpreted as the "other user" under consideration on the called interface. + +- c) If the call is a precedence call and the existing MLPP call is at equal or higher precedence, then the procedure in item 3) b) (1) (b) shall be followed. + +- 3) If the called user is busy, then: + - a) If the call is a ROUTINE call, clearing of the calling user shall be initiated by sending an Indication to the network with cause value #17, "user busy". + - b) If the call is a precedence call, then: + - (1) If the called user is busy with a call of lower precedence, then: + - (a) If preemptable access resources exist, the network shall mark the circuit (carrying the MLPP call of the called user) with the precedence level and MLPP Service Domain of the incoming call and the network shall send a SETUP message, which contains the Invoke component of the mLPPCallrequest operation in its Facility information element, to the called user. The called user may respond with a CALL PROCEEDING message or a RELEASE COMPLETE message. Then: + - 1) Upon receipt a CALL PROCEEDING message from the called user, indicating that compatibility requirements have been satisfied, the network shall place the existing MLPP call on hold, using a HOLD message delivered to the called user with cause value #8, "preemption" (in order to notify the called user of intended preemption) and the network shall start the timer $T_K$ . Upon sending the CALL PROCEEDING message, the called user shall mark the circuit with which the called user is busy with the precedence level and MLPP Service Domain of the incoming MLPP call. + +If the called user responds with a HOLD ACKNOWLEDGE message is received before the expiry of timer $T_K$ (indicating the acceptance of intended preemption), the network shall stop the timer $T_K$ and the network shall clear the existing MLPP call to: (a) the called user, using a DISCONNECT message and (b) the remote (to be preempted) user with a cause value #8 and the network shall continue the preempting call setup employing the procedure in item 5). The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitReservedForReuse". + +If no HOLD ACKNOWLEDGE message is received from the called user before the expiry of the timer $T_K$ , the network shall stop the timer $T_K$ . Then, if an alternate party is subscribed to, the network shall clear the existing MLPP call to: (a) the called user using a DISCONNECT message and (b) the remote (to be preempted) user with a cause value #8 and the network shall divert the incoming (preempting) call to the alternate party, using the procedures as described in 2/Q.952 for the call forwarding busy supplementary service. The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitNotReservedForReuse". The setup sent to the alternate party shall contain: the precedence level and MLPP Service Domain of the diverted precedence call, LFB Indication set to "lfbNotAllowed" and the reason for redirection = Call Forwarding Busy. Otherwise (i.e. when no HOLD ACKNOWLEDGE message is received from the called user before the expiry of the timer $T_K$ and no alternate party is subscribed to), the network shall clear the existing MLPP call to: (a) the called user, using a DISCONNECT message and (b) the remote (to be preempted) user with a cause value #8 and the network shall continue the preempting call setup employing the procedure in item 5). The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitReservedForReuse". + +If the called user corresponds with a STATUS message in response to the HOLD message sent by the network indicating that the called user's terminal does not support the Hold function, the network shall clear the existing MLPP call to: (a) the called user, using a DISCONNECT message and (b) the remote (to be preempted) user with a cause value #8 and the network shall continue the preempting call setup employing the + +procedure in item 5). The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to “circuitReservedForReuse”. + +- 2) Upon receipt of a RELEASE COMPLETE message from the called user with cause value #88, “incompatible destination”, indicating that compatibility requirements have not been satisfied, the network shall unmark the previously marked circuit and continue the preempting call setup employing the procedure in item 3) b) (1) (b), items 1) through 3). +- (b) If preemptable access resources do not exist, then: + - 1) If call completion or call offering supplementary services are available, then procedures as defined in MLPP supplementary service interactions with call completion or call offering supplementary services shall be initiated. + - 2) If call completion or call offering supplementary services are not available, but alternate party is subscribed to, the network shall divert the incoming precedence call to the alternate party, using the procedures as described in 2/Q.952 for the call forwarding busy supplementary service. The setup sent to the alternate party shall contain: the precedence level and MLPP Service Domain of the diverted precedence call, LFB Indication set to “lfbNotAllowed”, and the reason for redirection = Call Forwarding Busy. + - 3) If call completion or call offering supplementary services are not available and no alternate party is subscribed to, the network shall clear the calling user with cause value #46, “precedence call blocked”. +- (2) If the called user is busy with a call of equal or higher precedence, the procedure in item 3) b) (1) (b) shall be followed. +- 4) Upon receipt of the ALERTING message from the called user, which contains the Return Result component of the mLPPCallrequest operation in its Facility information element, the destination exchange shall check the StatusRequest to determine if the called user is an MLPP subscriber. If the called user is *not* an MLPP subscriber (as indicated by StatusRequest coded to “successCalledUserNotMLPPSubscriber”), the destination exchange shall unmark the previously marked circuit for the MLPP call; if the called user is an MLPP subscriber (as indicated by StatusRequest coded to “successCalledUserMLPPSubscriber”), the destination exchange shall retain marking on the previously marked circuit for the MLPP call. Then, in both cases above, the network shall complete the MLPP call setup as described in 5.2.7/Q.931. +- 5) Upon sending the DISCONNECT message in case (a), the network shall start the timer TRR to ensure that the circuit reserved for reuse is unreserved at the expiry of timer TRR. Then: + - a) If the existing call is cleared within timer TRR, as indicated by the network receiving RELEASE message from the destination user (called user or other user, as appropriate), which contains the Return Result component of the mLPPCallpreemption operation in its Facility information element, the network shall stop the timer TRR as indicated by the network receiving RELEASE message from the destination user (called user or other user, as appropriate), which contains the Return Result component of the mLPPCallpreemption operation in its Facility information element the network shall continue the preempting call by using the same (reserved) circuit and following the procedure in items 1) b) (1) or 1) b) (2), as appropriate. + - b) If the timer TRR expires and no response is obtained to the DISCONNECT message, from the destination user (called user or other user, as appropriate), the network shall stop the timer TRR, unreserved the marked circuit, and the procedure in this section (see 3.5.2.1.2.1, starting with item 1)) shall be followed, if this was the first attempt to setup the MLPP call; otherwise, the network shall clear the call toward calling user with cause value #46, “precedence call blocked”. + +###### 3.5.2.1.2.2 Exceptional procedures + +- 1) If the called user’s terminal does not support the Hold function, the user may return a STATUS message with cause value #98, “message not compatible with call state or message type nonexistent or not implemented” or cause value #97, “message type non-existent or not implemented” in response to the HOLD message sent by the destination network. Alternatively, the user may return a STATUS ENQUIRY message as described in 5.8.4/Q.931. In both cases, the destination network shall clear the existing MLPP call to: (a) the called user, using a DISCONNECT message and (b) the remote (to be + +preempted user) user with a cause value #8 and the network shall continue the preempting call setup employing the procedure in 3.5.2.1.2.1, item 5). The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to “circuitReservedForReuse”. + +- 2) If the incoming call is a precedence call and the called user is busy with a call of lower precedence and has preemptable access resources, then the following procedure is followed if the called user responds with a HOLD REJECT message within response timer $T_K$ to the HOLD message sent by the network. The network shall clear the existing MLPP call to: (a) the called user, using a DISCONNECT message and (b) the remote (to be preempted) user with a cause value #8 and the network shall continue the preempting call setup employing the procedure in 3.5.2.1.2.1, item 5). The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to “circuitReservedForReuse”. +- 3) An MLPP call may be preempted as a result of preemption in the network or access. In this case, upon receipt of the Release Indication or DISCONNECT message with cause value #8, “preemption” the destination network shall, respectively send the DISCONNECT message toward the called user or Release Indication toward the network with the same Cause to clear the call. The DISCONNECT message shall also contain the Return Result component of the mLPPCallrequest operation in its Facility information element, containing StatusRequest coded to “failureCaseB”, indicating call failure. + +#### **3.5.2.2 Optional MLPP DSS 1 LFB procedure** + +When the LFB option is provided in the DSS 1, then the MLPP DSS 1 LFB query shall be invoked in the DSS 1 environment to continue the network LFB query. The DSS 1 shall employ the Invoke component of the mLPPLFBquery operation contained in the Facility information element of the REGISTER message to invoke the query and the Return Result or Return Error components of the mLPPLFBquery operation contained in the Facility information element of the FACILITY message to return the responses to the query. The signalling association created by the REGISTER message shall be terminated by employing the RELEASE COMPLETE message, as described in 6.3.2/Q.932. + +The optional MLPP DSS 1 LFB procedure is illustrated in Figure 3-4 and described in the following. + +##### **3.5.2.2.1 Procedure at originating exchange/Originating user side** + +###### **3.5.2.2.1.1 Normal operation** + +None identified. + +###### **3.5.2.2.1.2 Exceptional procedures** + +None identified. + +##### **3.5.2.2.2 Procedure at destination exchange/destination user side** + +###### **3.5.2.2.2.1 Normal operation** + +When an LFB option is provided in the DSS 1, upon receipt of the network LFB query Indication, the destination network that serves the called user shall do the following: + +- 1) If the incoming reserved circuit indicated in the network LFB query Indication is available, the network shall mark it (with precedence level, MLPP Service Domain, and Calling party number) reserved for use by the preempting call and the procedure below shall be followed. + +The destination network shall send a REGISTER message, containing the Invoke component of the mLPPLFBquery operation, toward the called user. The called user shall respond to the REGISTER message with a FACILITY message, containing the query response in the Return Result or Return Error + +components of the mLPPLFBquery operation in its Facility information element. The network shall start timer $T_L$ when the REGISTER message is sent. Then: + +- a) Upon receipt of the FACILITY message from the called user, containing the query response in the Return Result or Return Error components of the mLPPLFBquery operation in its Facility information element, the network shall do the following: + +- (1) If the Return Result component of the mLPPLFBquery operation is received with StatusQuery coded to “bearerCapabilityNotAuthorized”, or “bearerCapabilityNotImplemented”, or “bearerCapabilityNotAvailable” and cause value #88, “incompatible destination”, the network shall stop the timer $T_L$ and the network shall return a network LFB query response Indication with the same coding. +- (2) If the Return Result component of the mLPPLFBquery operation is received with StatusQuery coded to “success”, the network shall stop the timer $T_L$ and then the following will occur: + +- (a) If the called user is idle and idle circuit to deliver the call to the called user exists, then the network shall mark a circuit to the called user (with precedence level, MLPP Service Domain, and Calling party number) as reserved for use by the preempting call and the network shall return a network LFB query response Indication, which contains the Return Result component of the mLPPLFBquery operation with StatusQuery coded to “success” and LFB Indication coded to “pathReserved”. + +The network shall start timer $T_{LR}$ after marking the circuit reserved for use to ensure that the reserved circuit is unreserved at the expiry of timer $T_{LR}$ . + +- (b) If the called user is idle, but an idle circuit to deliver the call to the called user does not exist, then the procedure in item 1) a) (2) (c) 1). (if preemptable access resources exist) or 1) a) (2) (c) 2). (if preemptable access resources do not exist) shall be followed. When comparing the precedence levels, the precedence level of the active MLPP call on the called interface instead of that of the MLPP call to the called user is employed and the network shall interpret the “called user” as the “other user” under consideration on the called interface. + +- (c) If the called user is busy, then: + +- 1) If preemptable access resources exist, the network shall compare the precedence levels of the preempting call with the MLPP call with which the called user is busy and do the following: + +- a) If the called user is busy with a call of lower precedence than the calling user, the network shall mark the busy circuit to the called user (with precedence level, MLPP Service Domain, and Calling party number) reserved for use by the preempting call and the network shall return a network LFB query response Indication, which contains the Return Result component of the mLPPLFBquery operation with StatusQuery coded to “success” and LFB Indication coded to “pathReserved”. + +The network shall start the timer $T_{LR}$ after marking the circuit reserved for use to ensure that the reserved circuit is unreserved at the expiry of timer $T_{LR}$ . + +- b) If the called user is busy with a call of equal or higher precedence than the calling user, then the following procedure in item 1) a) (2) (c) 2). shall be followed. + +- 2) If preemptable access resources do not exist, then: + +- a) If call completion or call offering supplementary services are available, the network shall return a network LFB query response Indication, which is coded to “success”. +- b) If call completion or call offering supplementary services are not available, but an alternate party is subscribed to, the network shall return a network LFB query response Indication, which is coded to “success”. +- c) If call completion or call offering supplementary services are not available and no alternate party is subscribed to, the network shall return a network LFB query response Indication, which is coded to “failure”, after unreserving the marked circuit. + +In all above cases, the network shall stop timer $T_{LR}$ when subsequent SETUP for the preempting call is sent. + +- b) If no FACILITY message is received from the called user before the expiry of timer $T_L$ , then the network shall stop the timer $T_L$ and the network shall unreserve the circuit that was previously marked as reserved and the network shall return a network LFB query response Indication, which shall be coded to “success”. + +In all above cases, the destination network shall terminate the signalling association created by the REGISTER message by sending a RELEASE COMPLETE message toward the called user. + +- 2) If the incoming reserved circuit indicated in the network LFB query Indication is not available, then the network shall return a network LFB query response Indication with StatusQuery coded to “pathReservationDenied”. + +###### **3.5.2.2.2.2 Exceptional procedures** + +- 1) When an LFB option is not provided in the DSS 1, then upon receipt of the network LFB query Indication, the destination network that serves the called user shall return a network LFB query response Indication, which is coded to “success” so that the preempting call may subsequently be offered when procedure in 3.5.2.1.2.1 is used. + +## **3.6 Interactions with other supplementary services** + +### **3.6.1 Call Waiting** + +If the incoming call to be delivered to the called user (on the basis of the ISDN Number/Bearer Service) is an MLPP call and the called access is busy (i.e. no access channel is available), then: + +- 1) If the incoming MLPP call is at a higher precedence level than the MLPP call of the lowest precedence level with which the called access is busy, then: preemption of that MLPP call shall occur as described in 3.5.2.1.2, if the user of that MLPP call has not subscribed to the “non-preemptable access resource” option; otherwise the network shall invoke the Call Waiting supplementary service by sending a SETUP message to the called user. +- 2) If the incoming MLPP call is at the same precedence level as that of the MLPP call of the lowest precedence level with which the called access is busy, then the network shall invoke the call waiting supplementary service by sending a SETUP message to the called user. +- 3) If the incoming MLPP call is at a lower precedence level than the MLPP call of the lowest precedence level with which the called access is busy, then the network shall invoke the call waiting supplementary service by sending a SETUP message to the called user. + +NOTE – Based on the precedence level comparison, the terminal may prevent the application of call waiting tone to the called user and may use alternate methods (i.e. out-of-band indication) to inform the called user, if busy, that a lower precedence call is waiting. + +For each of the three cases, the SETUP message, used for invoking the call waiting supplementary service, shall contain the precedence level of the incoming MLPP call in its Facility information element and the Number of Calls per ISDN Number/Bearer Service counter and the Number of Waiting Calls per ISDN Number/Bearer Service counter shall each be incremented. + +### **3.6.2 Call Transfer** + +As specified in 1/Q.952. + +### **3.6.3 Connected Line Identification Presentation** + +No impact. + +### **3.6.4 Connected Line Identification Restriction** + +No impact. + +### **3.6.5 Calling Line Identification Presentation** + +No impact. + +### **3.6.6 Calling Line Identification Restriction** + +No impact. + +### **3.6.7 Closed User Group** + +No impact. + +### **3.6.8 Conference Calling** + +All connections to the conferees on a conference call shall be processed at a precedence equal to the conference precedence selected by the conference controller. + +If a conferee is preempted, then after the conferee has been disconnected from the conference bridge, the network shall include cause value #8, "preemption" in the FACILITY message sent to the conference controller (i.e. served user) for notification, as described in 1.6/Q.954. + +When the served user is preempted, the NOTIFY message sent to all conferees (i.e. remote users) shall contain a Notification indication information element with Notification Description coded to "Conference floating, served user preempted". + +### **3.6.9 Direct-Dialling-In** + +No impact. + +### **3.6.10 Call Diversion services** + +#### **3.6.10.1 Call Forwarding Busy** + +If the called user has subscribed to the Call Forwarding Busy supplementary service, then: + +- 1) If the incoming MLPP call to the called user is a ROUTINE call, the procedure as described in 2/Q.952 shall be followed. +- 2) If the incoming MLPP call to the called user is a precedence call, then: + - a) If the called interface is busy with an MLPP call of lower precedence in the same MLPP service domain and preemptable, the network shall preempt that call to complete the incoming MLPP call to the called user, as described in 3.5.2.1.2. + - b) If the called interface is: (1) busy with: MLPP calls of equal or higher precedence in the same MLPP service domain, non-MLPP calls, and/or MLPP calls in other MLPP service domains or (2) busy and non-preemptable, then: + +The network shall forward the call, in accordance with the procedures of 2/Q.952, whether or not the called user has subscribed to the alternate party option. The destination network shall retain control of the forwarded call and start a timer $T_{MCF}$ when the SETUP message is sent to the forwarded-to-user only if the called user has subscribed to the alternate party option. The SETUP message sent to the forwarded-to-user shall also contain the precedence level (in Prec\_level of its Facility information element) of the call so that the forwarded-to-user may be preempted, as described in 3.5.2.1.2, to complete the call to the forwarded-to-user. + +If no response is received from the forwarded-to-user in the form of a CONNECT message or a Connect Request Indication before the expiry of timer $T_{MCF}$ , or a response is received in the form of a RELEASE COMPLETE message or a Release Request Indication before the expiry of timer $T_{MCF}$ , the network shall stop the timer $T_{MCF}$ and the network shall divert the incoming MLPP call to the alternate party, as described in 3.5.2.1.2. The destination network shall initiate clearing of the MLPP call to the forwarded-to-user, if it has not already occurred. + +If a response is received from the forwarded-to-user in the form of a CONNECT message or a Connect Request Indication before the expiry of timer $T_{MCF}$ , the network shall stop the timer $T_{MCF}$ and the network shall continue to forward the call, as described in 3.5.2.1.2. + +#### 3.6.10.2 Call Forwarding No Reply + +If the called user has subscribed to the Call Forwarding No Reply supplementary service, then: + +- 1) If the incoming MLPP call to the called user is a ROUTINE call, the procedure as described in 3/Q.952 shall be followed. +- 2) If the incoming MLPP call to the called user is a precedence call, then: + - a) On expiry of timer $T_K$ , and if the called user has subscribed to the alternate party option of the MLPP supplementary service, the network shall divert the call to the alternate party, as described in 3.5.2.1.2. + - b) On expiry of timer T-CFNR (see 3/Q.952), and if the called user has not subscribed to the alternate party option of the MLPP supplementary service, the network shall forward the call, as described in 3/Q.952. The network shall include in the SETUP message sent to the forwarded-to-user after the expiry of timer T-CFNR, the precedence level (in Prec\_level of its Facility information element) of the call so that the forwarded-to-user may be preempted, as described in 3.5.2.1.2, to complete the call to the forwarded-to-user. + +#### 3.6.10.3 Call Forwarding Unconditional + +If the called user has subscribed to the Call Forwarding Unconditional supplementary service, then: + +- 1) If the incoming MLPP call to the called user is a ROUTINE call, the procedure as described in 4/Q.952 shall be followed. +- 2) If the incoming MLPP call to the called user is a precedence call, then the call shall be forwarded employing the same procedure as in 3.6.10.1, item 2) b). + +#### 3.6.10.4 Call Deflection + +Not applicable. + +### 3.6.11 Line Hunting + +If no interface is available and one or more MLPP calls are of lower precedence than that of the incoming call, the network shall preempt an MLPP call of the lowest precedence, as described in 3.5.2.1. + +### 3.6.12 Three-Party Service + +When a three-way conversation is established, each connection shall maintain its assigned precedence level. Each connection of a call resulting from a split operation shall maintain the precedence level that it was assigned upon being added to the three-way conversation. In the Three Party supplementary service, when one of two original calls is preempted, the network shall release the three-way connection and apply normal call clearing procedure to the call being preempted. The DISCONNECT message sent to one of the parties of the preempted call in normal call clearing shall contain the Notification indicator information element with notification description coded to “conference disconnected, preemption”. The network shall also send to the other remote user a NOTIFY message, containing the Notification indicator information element with notification description coded to “conference disconnected, preemption”. + +### 3.6.13 User-to-User Signalling + +No impact. + +### 3.6.14 Multiple Subscriber Number + +No impact. + +### 3.6.15 Call Hold + +The network may preempt a held MLPP call due to a lack of resources in the network to complete a higher precedence MLPP call in the same MLPP Service Domain. In this situation, the clearing of the held MLPP call at the served user's (Call Hold subscriber's) interface shall be initiated by the network sending a DISCONNECT message to the served user. The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to “circuitNotReservedForReuse” and cause value #8, “preemption” in order to notify the served user that the held call is preempted. + +The network may preempt a held MLPP call as a result of a lack of channels at the held party's (or remote user's) interface when a higher precedence MLPP call in the same MLPP Service Domain needs to be setup over that interface. In this situation, the network shall preempt the held MLPP call at the remote user's interface by employing the normal call clearing procedures as described in 5.3/Q.931, with the first clearing message containing the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitReservedForReuse" (to indicate that the B-channel of the held call is reserved for reuse.) The channel thus reserved at the remote user's interface as a result of above MLPP procedure, may then be reused by the incoming or outgoing higher precedence MLPP call by the network or user sending a SETUP message containing channel id = "reserved channel's id". The clearing of the held MLPP call at the served user's (Call Hold subscriber's) interface shall be initiated by the network sending a DISCONNECT message to the served user. The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitNotReservedForReuse" and cause value #8, "preemption" in order to notify the served user that the held call is preempted. + +If a multipoint configuration exists at the served user's (user-network) interface, the network or user may use an "idle" or "active" channel that is reserved for a held MLPP call of the served user (Call Hold subscriber) for the incoming or outgoing higher precedence MLPP call to or from the same or another user on the interface. To accomplish this: + +- 1) For an "idle" channel, the incoming or outgoing higher precedence MLPP call may be completed or continued by the network or user sending a SETUP message with channel id = "idle channel's id". +- 2) For an "active" channel, the call on that channel shall be preempted following the normal call clearing procedures as described in Recommendation Q.931, with the first clearing message toward the user containing the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitReservedForReuse" (to indicate that the held channel is reserved for reuse) and the first clearing message toward the remote user of the "active" channel containing the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitNotReservedForReuse" and cause value #8, "preemption" (to indicate that the held channel at the remote user's interface is not reserved for reuse). Then, the incoming or outgoing higher precedence MLPP call may be completed or continued by the network or user sending a SETUP message with channel id = "channel id of the cleared call". + +In both of the above cases, the held MLPP call shall not be cleared. + +### **3.6.16 Advice of Charge** + +No impact. + +### **3.6.17 Sub-addressing** + +No applicable interaction at this time. + +### **3.6.18 Terminal Portability** + +No applicable interaction at this time. + +### **3.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +### **3.6.20 Malicious Call Identification** + +No applicable interaction at this time. + +### **3.6.21 Reverse Charging** + +No impact. + +### **3.6.22 Multi-Level Precedence and Preemption** + +No impact. + +## **3.7 Interactions with other networks** + +### **3.7.1 Interactions with public networks** + +When a public network employing Signaling System No. 7 (SS No. 7) interacts with the DSS 1, the SS No. 7 shall transport: + +- 1) Cause values #8 and #46, respectively to indicate “preemption” and “precedence call blocked” to the calling, called, preempted users, served user of the Conference Calling supplementary service, or remaining parties of a three way conversation when a call is preempted, as appropriate. +- 2) Information to indicate whether the called user of an MLPP call is an MLPP subscriber or not for the DSS 1 exchanges and the calling user. +- 3) Call completion delay indication to the calling user when an LFB query is invoked. +- 4) Conference floating, served user preempted indication to all conferees when the served user of the Conference Calling supplementary service is preempted. +- 5) Conference disconnected, preemption indication to the remaining parties of a three way conversation when the conference is disconnected as a result of preemption of one of the two calls. + +### **3.7.2 Interactions with private ISDNs** + +The procedure at the T reference point to support attached private networks is described in this subclause. + +Normal operation without an optional MLPP DSS 1 LFB query is illustrated in Figures 3-5 and 3-6 and described in 3.7.2.1. + +#### **3.7.2.1 MLPP DSS 1 procedure without LFB option** + +##### **3.7.2.1.1 Procedure at originating private ISDN** + +###### **3.7.2.1.1.1 Normal operation** + +If the originating exchange in the private ISDN is connected to a local exchange in a public network, it shall follow the procedure in 3.5.2.1.1.1, items 1) through 2) It shall then mark the circuit busy with the precedence level and MLPP Service Domain of the outgoing call and send a CALL PROCEEDING message toward the calling user. Then: + +- 1) If there is an idle circuit to propagate the call to the next exchange, then a SETUP message, containing the Invoke component of the mLPPCallrequest operation in its Facility information element, shall be sent after marking the circuit busy at the precedence level and the MLPP Service Domain of the MLPP call. Then the procedure in item 3) shall be followed. +- 2) If there are no idle circuits (i.e. congestion is encountered), the following shall occur: + - a) If the call is a ROUTINE call, it shall be cleared backward (toward calling user) employing the RELEASE COMPLETE message with cause value #34, “no circuit/channel available” and the Return Error component of the mLPPCallrequest operation in its Facility information element with Error “resourceUnavailable”. + - b) If the call is a precedence call and a preemptable circuit is located, then the MLPP call on that circuit shall be cleared: (a) forward (toward public network) using a DISCONNECT message containing the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to “circuitReservedForReuse” and (b) backward (toward to be preempted user) using a DISCONNECT message containing the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to “circuitNotReservedForReuse”. The circuit reserved for reuse is marked with the precedence level + +and MLPP Service Domain of the preempting call. A timer $T_{RR}$ is started upon sending the DISCONNECT message in case (a) to ensure that the circuit reserved for reuse is unreserved at the expiry of timer $T_{RR}$ . Then: + +- (1) If the existing MLPP call is cleared within timer $T_{RR}$ , as indicated by the private network receiving RELEASE message, which contains the Return Result component of the mLPPCallpreemption operation in its Facility information element, the timer $T_{RR}$ is stopped and the same (reserved) circuit shall be used to continue the preempting call using a SETUP message, which shall contain the Channel identification of the reserved circuit and the Invoke component of the mLPPCallrequest operation in its Facility information element. Then, the procedure in item 3) shall be followed. + - (2) On expiry of timer $T_{RR}$ , the marked circuit is unreserved and the procedure in this subclause (3.7.2.1.1.1, starting with item 2) shall be followed, if this was the first attempt to setup the MLPP call; otherwise, the call shall be cleared backward (toward calling user) employing the DISCONNECT message. The DISCONNECT message shall contain cause value #46, "precedence call blocked" and the Return Result component of the mLPPCallrequest operation in its Facility information element with StatusRequest coded to "failureCaseA", indicating call failure. + - c) If the call is a precedence call and a preemptable circuit is not located, it shall be cleared backward (toward calling user) employing the DISCONNECT message. The DISCONNECT message shall contain cause value #46, "precedence call blocked" and the Return Result component of the mLPPCallrequest operation in its Facility information element with StatusRequest coded to "failureCaseA", indicating call failure. +- 3) Upon receipt of the ALERTING message from the network, which contains the Return Result component of the mLPPCallrequest operation in its Facility information element, the originating exchange shall check the StatusRequest to determine if the called user is an MLPP subscriber. If the called user is *not* an MLPP subscriber (as indicated by StatusRequest coded to "successCalledUserNotMLPPSubscriber"), the originating exchange shall unmark the previously marked circuit for the MLPP call; if the called user is an MLPP subscriber (as indicated by StatusRequest coded to "successCalledUserMLPPSubscriber"), the originating exchange shall retain marking on the previously marked circuit for the MLPP call. Then, in both cases above, the MLPP call setup will continue, as described in 5.1.8/Q.931. + +###### **3.7.2.1.1.2 Exceptional procedures** + +As defined in 3.5.2.1.1.2. + +##### **3.7.2.1.2 Procedure at destination private ISDN** + +###### **3.7.2.1.2.1 Normal operation** + +Upon receipt of the Setup Indication, the local exchange in the public network connected to a private ISDN shall set appropriate codes for LFB Indication (LFB\_Indictn = "lfbAllowed" or "lfbNotAllowed") and MLPP Service Domain (MLPP\_Svc\_Domn) in the Facility information element, mark the circuit busy with precedence level and MLPP Service Domain, return a Call Proceeding Indication toward the network, and do the following: + +- 1) If there is an idle circuit to propagate the call to the next exchange, then a SETUP message, containing the Invoke component of the mLPPCallrequest operation in its Facility information element, shall be sent after marking the circuit busy at the precedence level and MLPP Service Domain of the incoming MLPP call. Then the procedure in item 3) shall be followed. +- 2) If there are no idle circuits (i.e. congestion is encountered), the following will occur: + - a) If the incoming call is a ROUTINE call, it shall be cleared backward (toward calling user) with an Indication with cause value #34, "no circuit/channel available". + - b) If the incoming call is a precedence call and a preemptable circuit is located, then the MLPP call on that circuit shall be cleared: (a) forward (toward called user) using a DISCONNECT message and (b) backward (toward to be preempted user) with an Indication containing cause value #8, "preemption". The DISCONNECT message shall contain the Invoke component of the mLPPCallpreemption operation in its Facility information element with Preempt\_params coded to "circuitReservedForReuse". The circuit reserved for reuse is marked with the precedence level and + +MLPP Service Domain of the preempting call. A timer $T_{RR}$ is started upon sending the DISCONNECT message in case (a) to ensure that the circuit reserved for reuse is unreserved at the expiry of timer $T_{RR}$ . Then: + +- (1) If the existing call is cleared within timer $T_{RR}$ , as indicated by the network receiving RELEASE message, which contains the Return Result component of the mLPPCallpreemption operation in its Facility information element, timer $T_{RR}$ is stopped and the same (reserved) circuit shall be used to continue the call using a SETUP message, which shall contain the Channel identification of the reserved circuit and the Invoke component of the mLPPCallrequest operation in its Facility information element. Then, the procedure in item 3) shall be followed. +- (2) On expiry of timer $T_{RR}$ , the marked circuit is unreserved and the procedure in this subclause (3.7.2.1.2.1, starting with item 1) shall be followed, if this was the first attempt to setup the MLPP call; otherwise, the call shall be cleared backward (toward calling user) with an Indication containing cause value #46, "precedence call blocked". +- c) If the incoming call is a precedence call and a preemptable circuit is not located, it shall be cleared backward (toward calling user) with an Indication containing cause value #46, "precedence call blocked". +- 3) Upon receipt of the ALERTING message from the called user side, which contains the Return Result component of the mLPPCallrequest operation in its Facility information element, the local exchange shall check the StatusRequest to determine if the called user is an MLPP subscriber. If the called user is *not* an MLPP subscriber (as indicated by StatusRequest coded to "successCalledUserNotMLPPSubscriber"), the local exchange shall unmark the previously marked circuit for the MLPP call; if the called user is an MLPP subscriber (as indicated by StatusRequest coded to "successCalledUserMLPPSubscriber"), the local exchange shall retain marking on the previously marked circuit for the MLPP call. Then, in both cases above, the MLPP call setup will be completed, as described in 5.2.7/Q.931. + +###### 3.7.2.1.2.2 Exceptional procedures + +- 1) Upon receipt of the Setup Indication, if the private network does not support the invoked MLPP supplementary service, the local exchange shall continue the MLPP call in the private network as if it were a basic call. +- 2) An MLPP call may be preempted as a result of preemption in the public network or private network. In this case, upon receipt of the Release Indication or DISCONNECT message with cause value #8, "preemption" the local exchange shall, respectively send the DISCONNECT message toward the private network or an Indication toward the public network with the same Cause to clear the call. The DISCONNECT message shall also contain the Return Result component of the mLPPCallrequest operation in its Facility information element, containing StatusRequest coded to "failureCaseB", indicating call failure. + +#### 3.7.2.2 Optional MLPP DSS 1 LFB procedure + +When the LFB option is supported by the private ISDN and the LFB Indication in the Invoke component within the Facility information element of mLPPCallrequest operation in the SETUP message or Setup Indication is coded to "lfbAllowed" then the MLPP DSS 1 LFB query shall be invoked in the private ISDN at the preemption initiating exchange when congestion (no idle circuits) is encountered. Note that this query shall also be invoked in the private ISDN to continue the network LFB query. The private ISDN shall employ the Invoke component of the mLPPLFBquery operation contained in the Facility information element of the REGISTER message to invoke the query and the Return Result or Return Error components of the mLPPLFBquery operation contained in the Facility information element of the FACILITY message to return the responses to the query. The signalling association created by the REGISTER message shall be terminated by employing the RELEASE COMPLETE message, as described in 6.3.2/Q.932. + +The optional MLPP DSS 1 LFB procedure is illustrated in Figures 3-7 and 3-8 and described in the following. + +##### 3.7.2.2.1 Procedure at originating private ISDN + +###### 3.7.2.2.1.1 Normal operation + +If the originating exchange is in a private ISDN (connected to a Local Exchange in a public network) which encounters congestion (i.e. no idle circuit) upon receipt of a SETUP message and locates a preemptable circuit and if LFB is being invoked on the call for the first time, then the originating exchange shall mark the circuit, as identified by Channel identification (with precedence level, MLPP Service Domain, and Calling party number), for preemption and reserved for use by the preempting call. Otherwise, the procedure in 3.7.2.1.1.1, items 1) through 3), shall be followed. A timer $T_{LR}$ is started to ensure that the marked circuit is unreserved at the expiry of timer $T_{LR}$ . It shall then invoke the MLPP DSS 1 LFB query with a REGISTER message sent towards the called user. The Invoke component of the mLPPLFBquery operation within the Facility information element of the REGISTER message contains the precedence level (Prec\_level), LFB Indication (LFB\_Indictn), and MLPP Service Domain (MLPP\_Svc\_Domn). Timer $T_L$ is started when the REGISTER message is sent. At the same time the REGISTER message is sent, a NOTIFY message is sent toward the calling user to indicate delay in call completion. The Notification Description field in the Notification indicator information element within the NOTIFY message shall be coded to indicate “call completion delay”. The response to the REGISTER message shall be received in an appropriate component within the Facility information element of the FACILITY message. The following actions then occur: + +- 1) If no FACILITY message is received and the timer $T_L$ expires, LFB Indication is set to “lfbNotAllowed” timers $T_L$ and $T_{LR}$ are stopped, the circuit previously marked as reserved is unreserved, and procedure described in 3.7.2.1.1.1, items 1) through 3) shall be followed. +- 2) If the FACILITY message is received before the expiry of timer $T_L$ , indicating success of the network LFB query, timer $T_L$ is stopped, LFB Indication is set to “pathReserved”, and one of the following will occur: + - a) If the circuit that was previously reserved for use by the preempting call is found and it is not idle, procedure described in 3.7.2.1.1.1, item 2) b) shall be followed. + - b) If the circuit that was previously reserved for use by the preempting call is found and it is idle, procedure described in 3.7.2.1.1.1, item 1) shall be followed. + - c) If the circuit that was previously reserved for use by the preempting call is not found, LFB Indication is set to “lfbNotAllowed”, timer $T_{LR}$ is stopped, and the procedure described in 3.7.2.1.1.1, items 1) through 3) shall be followed. + +In cases a) and b) above, timer $T_{LR}$ is stopped when subsequent SETUP for the preempting call is sent. + +- 3) If the FACILITY message is received before the expiry of timer $T_L$ , containing “pathReservationDenied” indication in StatusQuery, the same action as in item 1) above shall take place. +- 4) If the FACILITY message is received before the expiry of timer $T_L$ , indicating failure of the network LFB query, timers $T_L$ and $T_{LR}$ are stopped, the circuit previously marked as reserved is unreserved, and the incoming precedence call shall be cleared backward (toward calling user) using a DISCONNECT message, which contains cause value #46, “precedence call blocked” and the result of the mLPPCallrequest operation (i.e. StatusRequest coded to “failureCaseA”) in the Return Result component of its Facility information element. + +In all cases above, the originating exchange shall terminate the signalling association created by the REGISTER message by sending a RELEASE COMPLETE message toward the called user. + +###### 3.7.2.2.1.2 Exceptional procedures + +- 1) Upon receipt of the REGISTER message, if the public network does not support the MLPPLFB query, the public network shall return a FACILITY message towards the private network, which contains the Return Error component of the mLPPLFBquery operation in its Facility information element with Error “rejectedByNetwork” and continue the MLPP call as described in 3.7.2.1.1.1, items 1) through 3). + +- 2) Upon receipt of the REGISTER message, if the private network has not subscribed to the MLPPLFBquery, the public network supporting the MLPPLFBquery shall return a FACILITY message toward the private network, which contains the Return Error component of the MLPPLFBquery operation in its Facility information element with Error “userNotSubscribed” and continue the MLPP call as described in 3.7.2.1.1.1, items 1) through 3). + +In both cases above, the private network shall terminate the signalling association created by the REGISTER message by sending a RELEASE COMPLETE message. + +##### 3.7.2.2.2 Procedure at destination private ISDN + +###### 3.7.2.2.2.1 Normal operation + +When an LFB option is provided in the private ISDN, upon encountering congestion (i.e. no idle circuit) after the receipt of a Setup Indication and locating a preemptable circuit or upon receipt of the network LFB query Indication, the local exchange in the public network, connected to the private ISDN, will do the following, if LFB is invoked on the call for the first time; otherwise, the procedure in 3.7.2.1.2.1, items 1) through 3) shall be followed: + +- 1) *For network LFB query Indication receipt*, if a preemptable or idle circuit is not located, then an Indication, coded to “failure” shall be launched toward the network. +- 2) *For either network LFB query Indication or Setup Indication receipt*, preemptable or idle (for network LFB query only) circuit, as identified by its Channel identification, shall be marked (with precedence level, MLPP Service Domain, and Calling party number) for preemption and reserved for use by the preempting call. A timer $T_{LR}$ is started to ensure that the marked circuit is unreserved at the expiry of timer $T_{LR}$ . It shall then invoke the MLPP DSS 1 LFB query, employing the Invoke component within the Facility information element of the MLPPLFBquery operation in the REGISTER message, which is sent towards the called user. Timer $T_L$ is started when the REGISTER message is sent. For the Setup Indication receipt, at the same time the REGISTER message is sent, a NOTIFY message is sent toward the calling user to indicate delay in call completion. The Notification Description field in the Notification indicator information element within the NOTIFY message shall be coded to indicate “call completion delay”. The response to the REGISTER message shall be received in an appropriate component within the Facility information element of the FACILITY message. The following actions then occur: + - a) If no FACILITY message is received and the timer $T_L$ expires, timers $T_L$ and $T_{LR}$ are stopped and the circuit previously marked as reserved is unreserved. Then: + - (1) *For network LFB query Indication receipt*, an Indication, coded to “success” shall be launched toward the network. + - (2) *For Setup Indication receipt*, LFB Indication is set to “lfbNotAllowed” and procedure described in 3.7.2.1.2.1, items 1) through 3) shall be followed. + - b) If the FACILITY message is received before the expiry of timer $T_L$ , indicating success of the LFB query (i.e. StatusQuery coded to “success”), timer $T_L$ is stopped. Then: + - (1) *For network LFB query Indication receipt*, an Indication, coded to “success” shall be launched toward the network. The timer $T_{LR}$ is stopped when subsequent SETUP for the preempting call is sent. + - (2) *For Setup Indication receipt*, LFB Indication is set to “pathReserved” and one of the following will occur: + - (a) If the circuit that was previously reserved for use by the preempting call is found and it is not idle, procedure described in 3.7.2.1.2.1, item 2) b) shall be followed. + - (b) If the circuit that was previously reserved for use by the preempting call is found and it is idle, procedure described in 3.7.2.1.2.1, item 1) shall be followed. + - (c) If the circuit that was previously reserved for use by the preempting call is not found, LFB Indication (LFB\_Indictn) is set to “lfbNotAllowed”, timer $T_{LR}$ is stopped, and the procedure described in 3.7.2.1.2.1, items 1) through 3) shall be followed. + +In cases (a) and (b) above, timer $T_{LR}$ is stopped when subsequent SETUP for the preempting call is sent. + +- c) If the FACILITY message is received before the expiry of timer $T_L$ , containing StatusQuery coded to “pathReservationDenied” the same action as in item a) above shall take place. +- d) If the FACILITY message is received before the expiry of timer $T_L$ , indicating failure of the LFB query (i.e. StatusQuery coded to “failure”), timers $T_L$ and $T_{LR}$ are stopped, and the circuit previously marked as reserved is unreserved. Then: + - (1) *For network LFB query Indication receipt*, an Indication coded to “failure” shall be launched toward the network. + - (2) *For Setup Indication receipt*, the incoming precedence call shall be cleared backward (toward calling user) with an Indication containing cause value #46, “precedence call blocked”. + +In all cases above, the local exchange shall terminate the signalling association created by the REGISTER message by sending a RELEASE COMPLETE message toward the private network. + +###### 3.7.2.2.2 Exceptional procedure + +When LFB option is not provided in the private network, then upon receipt of the network LFB query Indication, the local exchange in the public network connected to a private network shall launch an Indication coded to “success” toward the public network so that the preempting call may subsequently be offered when the procedure in 3.7.2.1.2.1 shall be used. + +## 3.8 Signalling flows + +This subclause contains the signalling flow diagrams for the MLPP supplementary service. They are as shown in Figures 3-1 through 3-8. + +![Sequence diagram showing the normal operation for MLPP without LFB option (originating interface). The diagram involves two entities: 'Calling user' and 'Network'. The sequence of messages is: 1. 'Calling user' sends 'SETUP (CR, FIE{INV, OP=mLPPCallrequest})' to 'Network'. 2. 'Network' sends 'CALL PROCEEDING (CR)' to 'Calling user'. 3. 'Network' sends 'ALERTING (CR, FIE{RR, OP=mLPPCallrequest})' to 'Calling user'. 4. 'Network' sends 'CONNECT (CR)' to 'Calling user'.](55136bc716146672fc680fa05989f1d2_img.jpg) + +``` + +sequenceDiagram + participant CU as Calling user + participant N as Network + CU->>N: SETUP (CR, FIE{INV, OP=mLPPCallrequest}) + N-->>CU: CALL PROCEEDING (CR) + N-->>CU: ALERTING (CR, FIE{RR, OP=mLPPCallrequest}) + N-->>CU: CONNECT (CR) + +``` + +T1 145370-92/d01 + +Sequence diagram showing the normal operation for MLPP without LFB option (originating interface). The diagram involves two entities: 'Calling user' and 'Network'. The sequence of messages is: 1. 'Calling user' sends 'SETUP (CR, FIE{INV, OP=mLPPCallrequest})' to 'Network'. 2. 'Network' sends 'CALL PROCEEDING (CR)' to 'Calling user'. 3. 'Network' sends 'ALERTING (CR, FIE{RR, OP=mLPPCallrequest})' to 'Calling user'. 4. 'Network' sends 'CONNECT (CR)' to 'Calling user'. + +FIGURE 3-1/Q.955 +**Normal operation for MLPP without LFB option +(originating interface)** + +![Sequence diagram for MLPP without LFB option (called user busy).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +sequenceDiagram + participant Network + participant Called user + participant Other user as "Other" user + + Network->>Called user: SETUP (CRp, Ch ID=Ckt of to be preempted call, FIE{INV, OP=mLPPCallrequest}) + Called user-->>Network: CALL PROCEEDING (CRp) + Network->>Called user: HOLD (CRe, Cause #8) + Called user-->>Network: HOLD ACK (CRe) + Network->>Called user: DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) + Called user-->>Network: RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption}) + Network->>Called user: RELEASE COMPLETE (CRe) + Called user-->>Network: ALERTING (CRp, FIE{RR, OP=mLPPCallrequest}) + Called user-->>Network: CONNECT (CRp) + +``` + +Network + +Called user + +"Other" user + +SETUP (CRp, Ch ID=Ckt of to be preempted call, FIE{INV, OP=mLPPCallrequest}) + +CALL PROCEEDING (CRp) + +HOLD (CRe, Cause #8) + +HOLD ACK (CRe) + +DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) + +RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption}) + +RELEASE COMPLETE (CRe) + +ALERTING (CRp, FIE{RR, OP=mLPPCallrequest}) + +CONNECT (CRp) + +$T_K$ + +$T_{RR}$ + +$T_K$ + +T1 145380-92/d02 + +CRp Call Reference of preempting call +CRe Call Reference of preempted (existing) call + +Sequence diagram for MLPP without LFB option (called user busy). + +FIGURE 3-2/Q.955 +**Normal operation for MLPP without LFB option +(destination interface – called user busy)** + +![Sequence diagram for MLPP without LFB option (other user busy).](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +``` + +sequenceDiagram + participant Network + participant Called user + participant Other user as "Other" user + + Network->>Called user: SETUP (CRp, Ch ID=Ckt of to be preempted call, FIE{INV, OP=mLPPCallrequest}) + Called user-->>Network: CALL PROCEEDING (CRp) + Network->>Called user: DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) + Called user-->>Network: RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption}) + Network->>Called user: RELEASE COMPLETE (CRe) + Called user-->>Network: ALERTING (CRp, FIE{RR, OP=mLPPCallrequest}) + Called user-->>Network: CONNECT (CRp) + +``` + +Network + +Called user + +"Other" user + +SETUP (CRp, Ch ID=Ckt of to be preempted call, FIE{INV, OP=mLPPCallrequest}) + +CALL PROCEEDING (CRp) + +DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) + +RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption}) + +RELEASE COMPLETE (CRe) + +ALERTING (CRP, FIE{RR, OP=mLPPCallrequest}) + +CONNECT (CRp) + +$T_{RR}$ + +$T_K$ + +T1145390-92/d03 + +Sequence diagram for MLPP without LFB option (other user busy). + +FIGURE 3-3/Q.955 +**Normal operation for MLPP without LFB option +(destination interface – "other" user busy)** + +![Sequence diagram for MLPP with LFB option at the destination interface.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Sequence diagram showing the normal operation for MLPP with LFB option at the destination interface. The participants are Network and Called user. + +- The Network sends REGISTER (CR, FIE{INV, OP=mLPPLFBrequest}) to the Called user. +- The Called user sends FACILITY (CR, FIE{RR, OP=mLPPLFBrequest}) back to the Network. +- The Network sends RELEASE COMPLETE (CR) to the Called user. + +Timing diagram on the left shows $T_L$ as the time from the start of the REGISTER message to the start of the FACILITY message, and $T_{LR}$ as the time from the start of the REGISTER message to the start of the RELEASE COMPLETE message. + +T1145400-92/d04 + +Sequence diagram for MLPP with LFB option at the destination interface. + +FIGURE 3-4/Q.955 +**Normal operation for MLPP with LFB option + (destination interface)** + +![Sequence diagram for MLPP without LFB option at the originating private ISDN for successful preemption.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +Sequence diagram showing the normal operation for MLPP without LFB option at the originating private ISDN for successful preemption. The participants are Private Network and Public Network. + +- The Private Network sends DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) to the Public Network. +- The Public Network sends RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption}) back to the Private Network. +- The Private Network sends RELEASE COMPLETE (CRe) to the Public Network. +- The Private Network sends SETUP (CRp, Ch ID=reserved ckt, FIE{INV, OP=mLPPCallrequest}) to the Public Network. +- The Public Network sends ALERTING (CRp, FIE{RR, OP=mLPPCallrequest}) back to the Private Network. +- The Public Network sends CONNECT (CRp) back to the Private Network. + +Timing diagram on the left shows $T_{RR}$ as the time from the start of the DISCONNECT message to the start of the RELEASE message. + +T1145410-92/d05 + +Sequence diagram for MLPP without LFB option at the originating private ISDN for successful preemption. + +FIGURE 3-5/Q.955 +**Normal operation for MLPP without LFB option + (originating private ISDN – successful preemption)** + +![Sequence diagram for MLPP without LFB option (destination private ISDN – successful preemption).](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +Public Network + +Private Network + +DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) + +RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption}) + +$T_{RR}$ + +RELEASE COMPLETE (CRe) + +SETUP (CRp, Ch ID=reserved ckt, FIE{INV, OP=mLPPCallrequest}) + +ALERTING (CRp, FIE{RR, OP=mLPPCallrequest}) + +CONNECT (CRp) + +T1145420-92/d06 + +Detailed description: This sequence diagram illustrates the normal operation for MLPP without the LFB option in a destination private ISDN scenario. The diagram shows two vertical timelines: 'Public Network' on the left and 'Private Network' on the right. The sequence of messages is as follows: 1. A message 'DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption})' is sent from the Public Network to the Private Network. 2. A message 'RELEASE (CRe, FIE{RR, OP=mLPPCallpreemption})' is sent from the Private Network to the Public Network. 3. A vertical line with a downward arrow labeled $T_{RR}$ is shown on the Public Network timeline. 4. A message 'RELEASE COMPLETE (CRe)' is sent from the Public Network to the Private Network. 5. A message 'SETUP (CRp, Ch ID=reserved ckt, FIE{INV, OP=mLPPCallrequest})' is sent from the Public Network to the Private Network. 6. A message 'ALERTING (CRp, FIE{RR, OP=mLPPCallrequest})' is sent from the Private Network to the Public Network. 7. A message 'CONNECT (CRp)' is sent from the Private Network to the Public Network. The identifier 'T1145420-92/d06' is located at the bottom right. + +Sequence diagram for MLPP without LFB option (destination private ISDN – successful preemption). + +FIGURE 3-6/Q.955 + +**Normal operation for MLPP without LFB option +(destination private ISDN – successful preemption)** + +![Sequence diagram for MLPP with LFB option (originating private ISDN – successful preemption).](14252bcd35912bd656e98b16b2ee51c0_img.jpg) + +Private Network + +Public Network + +REGISTER (CR, FIE{INV, OP=mLPP LFBquery}) + +FACILITY (CR, FIE{RR, OP=mLPP LFBquery}) + +$T_L$ + +RELEASE COMPLETE (CR) + +DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption}) + +$T_{LR}$ + +RELEASE (CRe, FIE{INV, OP=mLPPCallpreemption}) + +$T_{RR}$ + +RELEASE COMPLETE (CRe) + +SETUP (CRp, Ch ID=reserved ckt, FIE{INV, OP=mLPPCallrequest}) + +ALERTING (CRp, FIE{RR, OP=mLPPCallrequest}) + +CONNECT (CRp) + +T1145430-92/d07 + +Detailed description: This sequence diagram illustrates the normal operation for MLPP with the LFB option in an originating private ISDN scenario. The diagram shows two vertical timelines: 'Private Network' on the left and 'Public Network' on the right. The sequence of messages is as follows: 1. A message 'REGISTER (CR, FIE{INV, OP=mLPP LFBquery})' is sent from the Private Network to the Public Network. 2. A message 'FACILITY (CR, FIE{RR, OP=mLPP LFBquery})' is sent from the Public Network to the Private Network. 3. A vertical line with a downward arrow labeled $T_L$ is shown on the Private Network timeline. 4. A message 'RELEASE COMPLETE (CR)' is sent from the Private Network to the Public Network. 5. A message 'DISCONNECT (CRe, FIE{INV, OP=mLPPCallpreemption})' is sent from the Private Network to the Public Network. 6. A vertical line with a downward arrow labeled $T_{LR}$ is shown on the Private Network timeline. 7. A message 'RELEASE (CRe, FIE{INV, OP=mLPPCallpreemption})' is sent from the Public Network to the Private Network. 8. A vertical line with a downward arrow labeled $T_{RR}$ is shown on the Private Network timeline. 9. A message 'RELEASE COMPLETE (CRe)' is sent from the Public Network to the Private Network. 10. A message 'SETUP (CRp, Ch ID=reserved ckt, FIE{INV, OP=mLPPCallrequest})' is sent from the Public Network to the Private Network. 11. A message 'ALERTING (CRp, FIE{RR, OP=mLPPCallrequest})' is sent from the Private Network to the Public Network. 12. A message 'CONNECT (CRp)' is sent from the Private Network to the Public Network. The identifier 'T1145430-92/d07' is located at the bottom right. + +Sequence diagram for MLPP with LFB option (originating private ISDN – successful preemption). + +FIGURE 3-7/Q.955 + +**Normal operation for MLPP with LFB option +(originating private ISDN – successful preemption)** + +![Sequence diagram showing the normal operation for MLPP with LFB option (destination private ISDN – successful preemption) between a Public Network and a Private Network. The diagram includes messages like REGISTER, FACILITY, RELEASE COMPLETE, DISCONNECT, RELEASE, SETUP, ALERTING, and CONNECT, along with timers T_L, T_LR, and T_RR.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +``` + +sequenceDiagram + participant Public as Public Network + participant Private as Private Network + Note over Public: T_L starts + Public->>Private: REGISTER (CR, FIE{INV, OP=mLPP LFB query}) + Note over Public: T_L ends, T_LR starts + Private-->>Public: FACILITY (CR, FIE{RR, OP=LPP LFB query}) + Public->>Private: RELEASE COMPLETE (CR) + Note over Public: T_RR starts + Public->>Private: DISCONNECT (CRe, FIE{INV, OP=mLPP Call preemption}) + Note over Public: T_LR ends, T_RR ends + Private-->>Public: RELEASE (CRe, FIE{INV, OP=mLPP Call preemption}) + Public->>Private: RELEASE COMPLETE (CRe) + Public->>Private: SETUP (CRp, Ch ID=reserved ckt, FIE{INV, OP=mLPP Call request}) + Private-->>Public: ALERTING (CRp, FIE{RR, OP=mLPP Call request}) + Public->>Private: CONNECT (CRp) + +``` + +T1145440-92/d08 + +Sequence diagram showing the normal operation for MLPP with LFB option (destination private ISDN – successful preemption) between a Public Network and a Private Network. The diagram includes messages like REGISTER, FACILITY, RELEASE COMPLETE, DISCONNECT, RELEASE, SETUP, ALERTING, and CONNECT, along with timers T\_L, T\_LR, and T\_RR. + +FIGURE 3-8/Q.955 +**Normal operation for MLPP with LFB option +(destination private ISDN – successful preemption)** + +## 3.9 Parameter values – timers + +Four additional timers $T_K$ , $T_L$ , $T_{LR}$ , and $T_{RR}$ beyond those specified in Recommendations Q.931 and Q.932, shall be employed with the MLPP operation, as described in this Recommendation. + +Network timer $T_K$ is started when the serving exchange notifies a user of a precedence call. This timer has a range of values from 4-30 seconds. + +Timer $T_L$ is started when the MLPP DSS 1 LFB query is invoked. This timer has an approximate value of 15 seconds. + +Timer $T_{LR}$ is started when the MLPP DSS 1 LFB query successfully locates and marks as reserved a preemptable circuit. This timer has an approximate value of 30 seconds. + +Timer $T_{RR}$ is started when the call is released with the DISCONNECT message and the circuit is reserved for reuse. This timer has a value of 12 seconds. + +## 3.10 Dynamic description + +This subclause specifies actions within telecommunication equipment associated with the user-network access interface to support MLPP in diagrammatic form. It is shown in Figures 3-9 and 3-12. Figure 3-9 covers the Originating Exchange (OE), Figure 3-10, the calling user, Figure 3-11, the Destination Exchange (DE), and Figure 3-12, the called user. + +![Flowchart for originating exchange (OE) procedure without DSS 1 LFB query for outgoing MLPP call. The process starts with a NULL state, followed by a SETUP message. A decision is made on whether Facility IE is present. If not, it proceeds to a 'Formulate Facility IE with PL = ROUTINE' box. If yes, it checks if PL is valid. If not valid, it sends a 'RELEASE COMPLETE' message with Error = 44, 'unauthorizedPrecedenceLevel', and the call setup is rejected. If valid, it sets MLPP Service Domain and LFB indication values, marks the circuit with PL and MLPP Service Domain, and sends a Setup indication. This is followed by CALL INITIATED, a Proceeding request, and a CALL PROCEEDING message. A note indicates that additional checks may be made before sending this message. The process ends at connector A.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +``` + +graph TD + Start([NULL]) --> Setup[/SETUP/] + Setup -.-> Note1[For MLPP call] + Setup --> FacIE{Facility IE present?} + FacIE -- No --> Formulate[Formulate Facility IE with PL = ROUTINE] + FacIE -- Yes --> PLValid{PL valid?} + PLValid -- No --> Release[/RELEASE COMPLETE with Error = 44, "unauthorizedPrecedenceLevel"/] + Release -.-> Note2[MLPP call setup rejected] + Release --> End1([NULL]) + End1 --- T1140660-92/d09 + PLValid -- Yes --> SetMLPP[Set MLPP Service Domain and LFB indication values] + SetMLPP --> MarkCircuit[Mark the circuit with PL and MLPP Service Domain of outgoing MLPP call] + MarkCircuit --> SetupInd[Setup indication] + SetupInd --> CallInit([CALL INITIATED]) + CallInit --> ProceedReq[/Proceeding request/] + ProceedReq --> CallProceed[/CALL PROCEEDING/] + CallProceed -.-> Note3[Additional checks may be made before sending this message] + CallProceed --> A((A)) + +``` + +Flowchart for originating exchange (OE) procedure without DSS 1 LFB query for outgoing MLPP call. The process starts with a NULL state, followed by a SETUP message. A decision is made on whether Facility IE is present. If not, it proceeds to a 'Formulate Facility IE with PL = ROUTINE' box. If yes, it checks if PL is valid. If not valid, it sends a 'RELEASE COMPLETE' message with Error = 44, 'unauthorizedPrecedenceLevel', and the call setup is rejected. If valid, it sets MLPP Service Domain and LFB indication values, marks the circuit with PL and MLPP Service Domain, and sends a Setup indication. This is followed by CALL INITIATED, a Proceeding request, and a CALL PROCEEDING message. A note indicates that additional checks may be made before sending this message. The process ends at connector A. + +FIGURE 3-9/Q.955 (Sheet 1 of 2) + Originating exchange (OE) – Procedure without DSS 1 LFB query + (procedure for outgoing MLPP call) + +![Flowchart for Outgoing MLPP call procedure. It starts with a start symbol 'A' leading to 'OUTGOING CALL PROCEEDING', then 'Alerting request', a decision 'Called Party MLPP User?', and states 'ALERTING', 'CALL DELIVERED', 'CONNECT', and 'ACTIVE'. A branch for 'No' leads to 'Unmark the circuit of PL and MLPP Service Domain marking' before joining the 'Yes' path.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` + +graph TD + A((A)) -- 1 --> B([OUTGOING CALL PROCEEDING]) + B --> C[/Alerting request/] + C --> D{Called Party +MLPP User?} + D -- Yes --> E[/ALERTING/] + D -- No --> F[Unmark the circuit of +PL and MLPP Service +Domain marking] + F --> E + E --> G([CALL DELIVERED]) + G --> H[/Setup response/] + H --> I[/CONNECT/] + I --> J([ACTIVE]) + +``` + +T1140670-92/d10 + +Flowchart for Outgoing MLPP call procedure. It starts with a start symbol 'A' leading to 'OUTGOING CALL PROCEEDING', then 'Alerting request', a decision 'Called Party MLPP User?', and states 'ALERTING', 'CALL DELIVERED', 'CONNECT', and 'ACTIVE'. A branch for 'No' leads to 'Unmark the circuit of PL and MLPP Service Domain marking' before joining the 'Yes' path. + +FIGURE 3-9/Q.955 (Sheet 2 of 2) +**Originating exchange (OE) – Procedure without DSS 1 LFB query +(Procedure for outgoing MLPP call)** + +![Flowchart for Calling User – Procedure without DSS 1 LFB query (procedure for outgoing MLPP call). The flow starts with a NULL state, followed by a SETUP message (with a dashed line indicating 'For MLPP call'). This leads to CALL INITIATED. From there, the flow branches into two paths: one for successful call proceeding (CALL PROCEEDING) and one for release complete with error (RELEASE COMPLETE with error = 44 unauthorized PrecedenceLevel). The successful path involves marking the circuit with PL and MLPP Service Domain, reserving the outgoing circuit, and then proceeding to OUTGOING CALL PROCEEDING, ALERTING, and finally a state labeled 1 (with a 2 below it). The error path leads to a NULL state with reference T1145450-92/d11. A side box contains facility information about MLPP subscribers.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +``` + +graph TD + NULL1([NULL]) --> SETUP[/SETUP/] + SETUP -.->|For MLPP call| + SETUP --> CALL_INITIATED([CALL INITIATED]) + CALL_INITIATED --> CALL_PROCEEDING[/CALL PROCEEDING/] + CALL_INITIATED --> RELEASE_COMPLETE[/RELEASE COMPLETE with error = 44 unauthorized PrecedenceLevel/] + CALL_PROCEEDING --> MarkCircuit[Mark the circuit with PL and MLPP Service Domain of outgoing MLPP call] + MarkCircuit --> ReserveCircuit[..Reserve outgoing circuit after B-channel confirmation from the network] + ReserveCircuit --> OUTGOING_CALL_PROCEEDING([OUTGOING CALL PROCEEDING]) + OUTGOING_CALL_PROCEEDING --> ALERTING[/ALERTING/] + ALERTING --> State1((1)) + State1 --- 2 + RELEASE_COMPLETE --> NULL2([NULL]) + NULL2 --- T1145450-92/d11 + +``` + +-- Contains Facility information element indicating if the called user is an MLPP subscriber or not + +T1145450-92/d11 + +Flowchart for Calling User – Procedure without DSS 1 LFB query (procedure for outgoing MLPP call). The flow starts with a NULL state, followed by a SETUP message (with a dashed line indicating 'For MLPP call'). This leads to CALL INITIATED. From there, the flow branches into two paths: one for successful call proceeding (CALL PROCEEDING) and one for release complete with error (RELEASE COMPLETE with error = 44 unauthorized PrecedenceLevel). The successful path involves marking the circuit with PL and MLPP Service Domain, reserving the outgoing circuit, and then proceeding to OUTGOING CALL PROCEEDING, ALERTING, and finally a state labeled 1 (with a 2 below it). The error path leads to a NULL state with reference T1145450-92/d11. A side box contains facility information about MLPP subscribers. + +FIGURE 3-10/Q.955 (Sheet 1 of 2) +**Calling User – Procedure without DSS 1 LFB query + (procedure for outgoing MLPP call)** + +![Flowchart for Calling User – Procedure without DSS 1 LFB query (procedure for outgoing MLPP call). The process starts with a start symbol 'I' leading to a decision 'Called uer MLPP subscriber?'. If 'No', it goes to 'Unmark the previously marked circuit' and then to 'Alerting indication'. If 'Yes', it goes directly to 'Alerting indication'. 'Alerting indication' leads to 'CALL DELIVERED', which leads to 'CONNECT'. 'CONNECT' leads to 'Setup confirm', which leads to 'Ack option'. 'Ack option' leads to 'ACTIVE'. A 'CONNECT ACKNOWLEDGE' message is sent from 'Ack option' back to 'CONNECT'.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +``` + +graph TD + Start((I)) -- 1 --> Decision{Called uer +MLPP subscriber?} + Decision -- No --> Unmark[Unmark the previously +marked circuit] + Decision -- Yes --> Alerting[/Alerting +indication/] + Unmark --> Alerting + Alerting --> CallDelivered{{CALL +DELIVERED}} + CallDelivered --> Connect[/CONNECT/] + Connect --> SetupConfirm[/Setup +confirm/] + SetupConfirm --> AckOption[/Ack +option/] + AckOption --> Active{{ACTIVE}} + AckOption -- CONNECT +ACKNOWLEDGE --> Connect + +``` + +T1145460-92/d12 + +Flowchart for Calling User – Procedure without DSS 1 LFB query (procedure for outgoing MLPP call). The process starts with a start symbol 'I' leading to a decision 'Called uer MLPP subscriber?'. If 'No', it goes to 'Unmark the previously marked circuit' and then to 'Alerting indication'. If 'Yes', it goes directly to 'Alerting indication'. 'Alerting indication' leads to 'CALL DELIVERED', which leads to 'CONNECT'. 'CONNECT' leads to 'Setup confirm', which leads to 'Ack option'. 'Ack option' leads to 'ACTIVE'. A 'CONNECT ACKNOWLEDGE' message is sent from 'Ack option' back to 'CONNECT'. + +FIGURE 3-10/Q.955 (Sheet 2 of 2) +**Calling User – Procedure without DSS 1 LFB query** +**(procedure for outgoing MLPP call)** + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The process starts with a NULL state, followed by a Setup Indication for an incoming MLPP call. The circuit is marked busy with PL and MLPP Service Domain. A decision is made on 'Path reserved?'. If 'Yes', the timer T_LR is stopped, and a decision is made on 'Is marked circuit found?'. If 'Yes', it checks 'Is reserved circuit idle?'. If 'No', it goes to state O (5). If 'Yes', it goes to state DD (8). If 'No', it sets LFB indication to 'IfbNotAllowed' and goes to state DD (8). From state DD (8), it checks 'Called user busy?'. If 'Yes', it checks 'Is call a precedence call?'. If 'Yes', it goes to state L (6). If 'No', it goes to 'Release Complete Indication, containing Cause #17, "user busy"', then 'Clearing of calling user', and finally NULL. If 'No' to 'Called user busy?', it checks 'Is idle circuit available?'. If 'No', it goes to state P (3). If 'Yes', it goes to state B (2).](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +graph TD + Start([NULL]) --> Setup[/Setup Indication/] + Setup -.->|for incoming MLPP call| MLPP[Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call] + MLPP --> PathReserved{Path reserved?} + PathReserved -.->|"Path reserved" is set in LFB indication| Yes + PathReserved -- No --> L6((L 6)) + Yes --> StopTimer[Stop timer TLR, if running] + StopTimer --> MarkedCircuitFound{Is marked circuit found?} + MarkedCircuitFound -.->|This decision is on reservation Preemption| No + MarkedCircuitFound -- Yes --> ReservedCircuitIdle{Is reserved circuit idle?} + ReservedCircuitIdle -- No --> O5((O 5)) + ReservedCircuitIdle -- Yes --> DD8((DD 8)) + MarkedCircuitFound -- No --> SetLFB[Set LFB indication to "IfbNotAllowed"] + SetLFB --> DD8 + DD8 --> CalledUserBusy{Called user busy?} + CalledUserBusy -- Yes --> PrecedenceCall{Is call a precedence call?} + PrecedenceCall -- Yes --> L6 + PrecedenceCall -- No --> ReleaseCause17[/Release Complete Indication, containing Cause #17, "user busy"/] + ReleaseCause17 --> ClearingUser[Clearing of calling user] + ClearingUser --> End([NULL]) + CalledUserBusy -- No --> IdleCircuitAvailable{Is idle circuit available?} + IdleCircuitAvailable -- No --> P3((P 3)) + IdleCircuitAvailable -- Yes --> B2((B 2)) + +``` + +T1140680-92/d13 + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The process starts with a NULL state, followed by a Setup Indication for an incoming MLPP call. The circuit is marked busy with PL and MLPP Service Domain. A decision is made on 'Path reserved?'. If 'Yes', the timer T\_LR is stopped, and a decision is made on 'Is marked circuit found?'. If 'Yes', it checks 'Is reserved circuit idle?'. If 'No', it goes to state O (5). If 'Yes', it goes to state DD (8). If 'No', it sets LFB indication to 'IfbNotAllowed' and goes to state DD (8). From state DD (8), it checks 'Called user busy?'. If 'Yes', it checks 'Is call a precedence call?'. If 'Yes', it goes to state L (6). If 'No', it goes to 'Release Complete Indication, containing Cause #17, "user busy"', then 'Clearing of calling user', and finally NULL. If 'No' to 'Called user busy?', it checks 'Is idle circuit available?'. If 'No', it goes to state P (3). If 'Yes', it goes to state B (2). + +FIGURE 3-11/Q.955 (Sheet 1 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query** +**(procedure for incoming MLPP call)** + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call).](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + B((B)) -- 1 --> MarkCircuit[Mark circuit to called user +busy with PL and MLPP +Service Domain of +incoming MLPP call] + MarkCircuit -- Yes --> SetupRequest[/Setup +request/] + SetupRequest --> SETUP{{SETUP}} + SETUP -.-> Note[Continue setup of +incoming MLPP call] + SETUP --> CALLPRESENT([CALL +PRESENT]) + + CALLPRESENT --> ReleaseComplete[/RELEASE COMPLETE +with Cause #88, +"incompatible +destination"/] + ReleaseComplete --> UnmarkCircuit[Unmark the +previously +marked circuit] + UnmarkCircuit --> IsPrecedenceCall1{Is call +a precedence +call?} + IsPrecedenceCall1 -- Yes --> T9((T)) + T9 -- 9 --> EndT + IsPrecedenceCall1 -- No --> ClearingUser[Clearing of +calling user] + ClearingUser --> NULL([NULL]) + + CALLPRESENT --> CallProceeding[/CALL +PROCEEDING/] + CallProceeding --> IsPrecedenceCall2{Is call +a precedence +call?} + IsPrecedenceCall2 -- No --> IncomingCallProceeding1([INCOMING CALL +PROCEEDING]) + IsPrecedenceCall2 -- Yes --> AlternatePartySubscribed{Alternate +party +subscribed to?} + AlternatePartySubscribed -- No --> IncomingCallProceeding1 + AlternatePartySubscribed -- Yes --> IncomingCallProceeding2([INCOMING CALL +PROCEEDING]) + + IncomingCallProceeding1 --> CC10((CC)) + CC10 -- 10 --> EndCC + IncomingCallProceeding2 --> Q4((Q)) + Q4 -- 4 --> EndQ + +``` + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). + +T1145470-92/d14 + +FIGURE 3-11/Q.955 (Sheet 2 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query** +**(procedure for incoming MLPP call)** + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts at connector P (1), leading to a decision 'Is call a precedence call?'. If 'Yes', it goes to 'Compare PL of incoming MLPP call with that of existing MLPP call', then to 'Is existing MLPP call at lower PL?'. If 'Yes', it goes to connector M (5). If 'No', it goes to connector T (9). If 'No' from the first decision, it goes to 'Release Complete Indication, containing Cause #34, "no circuit/channel available"', then to 'Clearing of calling user', and finally to a NULL terminal. The reference T1140700-92/d15 is at the bottom.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +``` + +graph TD + P((P)) -- 1 --> D1{Is call a precedence call?} + D1 -- Yes --> P1[Compare PL of incoming MLPP call with that of existing MLPP call] + P1 --> D2{Is existing MLPP call at lower PL?} + D2 -- Yes --> M((M)) + M --- 5[5] + D2 -- No --> T((T)) + T --- 9[9] + D1 -- No --> P2[["Release Complete Indication, containing Cause #34, "no circuit/channel available""]] + P2 --> P3[Clearing of calling user] + P3 --> NULL([NULL]) + +``` + +T1140700-92/d15 + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts at connector P (1), leading to a decision 'Is call a precedence call?'. If 'Yes', it goes to 'Compare PL of incoming MLPP call with that of existing MLPP call', then to 'Is existing MLPP call at lower PL?'. If 'Yes', it goes to connector M (5). If 'No', it goes to connector T (9). If 'No' from the first decision, it goes to 'Release Complete Indication, containing Cause #34, "no circuit/channel available"', then to 'Clearing of calling user', and finally to a NULL terminal. The reference T1140700-92/d15 is at the bottom. + +FIGURE 3-11/Q.955 (Sheet 3 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query +(procedure for incoming MLPP call)** + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flowchart starts with a circle 'Q' with '2, 8' below it, leading to an 'ALERTING' event. A callout box points to 'ALERTING' with the text: 'Called party notified of precedence call. It also contains an indication of whether the called party is an MLPP user or not'. From 'ALERTING', a decision diamond asks 'Called party MLPP user?'. If 'No', it goes to 'Unmark the circuit of PL and MLPP Service Domain marking' and then to 'Start timer T_K'. If 'Yes', it goes directly to 'Start timer T_K'. 'Start timer T_K' leads to a 'CALL RECEIVED' event. From 'CALL RECEIVED', the flow splits into two paths. The left path goes through 'Timer T_K expires' to 'Divert call to alternate party' and then to 'ACTIVE'. The right path goes through 'CONNECT' to 'Stop timer T_K', then 'CONNECT REQUEST', 'Setup complete request', 'CONNECT ACK', and finally to 'ACTIVE'. There is also a 'No ALERTING is received' event that leads to 'Divert call to alternate party'.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg) + +``` + +graph TD + Q((Q)) -- 2, 8 --> ALERTING[/ALERTING/] + ALERTING -.-> Note[Called party notified of precedence call. +It also contains an indication of whether +the called party is an MLPP user or not] + ALERTING --> MLPP{Called party +MLPP user?} + MLPP -- No --> Unmark[Unmark the circuit of +PL and MLPP Service +Domain marking] + MLPP -- Yes --> StartTimer[Start +timer TK] + Unmark --> StartTimer + StartTimer --> CALL_RECEIVED{{CALL +RECEIVED}} + CALL_RECEIVED --> TimerExpires[/Timer TK +expires/] + CALL_RECEIVED --> CONNECT[/CONNECT/] + TimerExpires --> Divert[Divert call +to +alternate party] + CONNECT --> StopTimer[Stop +timer TK] + StopTimer --> CONNECT_REQUEST{{CONNECT +REQUEST}} + CONNECT_REQUEST --> Setup[/Setup +complete +request/] + Setup --> CONNECT_ACK[/CONNECT +ACK/] + CONNECT_ACK --> ACTIVE2{{ACTIVE}} + Divert --> ACTIVE1{{ACTIVE}} + NoAlerting[/No ALERTING +is received/] --> Divert + +``` + +T1145480-92/d16 + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flowchart starts with a circle 'Q' with '2, 8' below it, leading to an 'ALERTING' event. A callout box points to 'ALERTING' with the text: 'Called party notified of precedence call. It also contains an indication of whether the called party is an MLPP user or not'. From 'ALERTING', a decision diamond asks 'Called party MLPP user?'. If 'No', it goes to 'Unmark the circuit of PL and MLPP Service Domain marking' and then to 'Start timer T\_K'. If 'Yes', it goes directly to 'Start timer T\_K'. 'Start timer T\_K' leads to a 'CALL RECEIVED' event. From 'CALL RECEIVED', the flow splits into two paths. The left path goes through 'Timer T\_K expires' to 'Divert call to alternate party' and then to 'ACTIVE'. The right path goes through 'CONNECT' to 'Stop timer T\_K', then 'CONNECT REQUEST', 'Setup complete request', 'CONNECT ACK', and finally to 'ACTIVE'. There is also a 'No ALERTING is received' event that leads to 'Divert call to alternate party'. + +FIGURE 3-11/Q.955 (Sheet 4 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query + (procedure for incoming MLPP call)** + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call).](0b7849dae424b0dd33e6386d2384643a_img.jpg) + +``` + +graph TD + M((M +3)) --> D1{Non-preemptable +access resources +subscribed to?} + D1 -- Yes --> T9((T +9)) + D1 -- No --> D2{Called +user busy?} + O((O +1)) --> D2 + D2 -- Yes --> K6((K +6)) + D2 -- No --> D1 + D1 --> P1[Mark circuit busy with PL +and MLPP Service Domain +of the incoming MLPP call] + P1 --> S1[/SETUP/] + S1 -.-> C1[Continue setup of +incoming MLPP call] + S1 --> P2[/CALL +PRESENT/] + P2 --> D3{RELEASE COMPLETE +with Cause #88, +"incompatible +destination"} + P2 --> D4[/CALL +PROCEEDING/] + D3 --> P3[Unmark the +previously marked +circuit] + P3 --> T9 + D4 --> P4[/INCOMING CALL +PROCEEDING/] + P4 --> D5[/Disconnect +request/] + D5 --> D6{Is +circuit to +be reserved +for reuse?} + D6 -- Yes --> Z7((Z +7)) + D6 -- No --> S7((S +7)) + +``` + +The flowchart illustrates the procedure for handling an incoming MLPP call when the destination is busy. It starts with a decision diamond (M 3) asking if non-preemptable access resources are subscribed to. If 'Yes', it goes to terminal T 9. If 'No', it proceeds to a decision diamond (O 1) asking if the called user is busy. If 'Yes', it goes to terminal K 6. If 'No', it loops back to the first decision. Following the 'No' path from the first decision, the circuit is marked busy with PL and MLPP Service Domain, then a SETUP message is sent (with a dashed line indicating 'Continue setup of incoming MLPP call'), and a CALL PRESENT message is received. From CALL PRESENT, the flow splits into two paths: one for 'RELEASE COMPLETE with Cause #88, "incompatible destination"' leading to 'Unmark the previously marked circuit' and then to T 9; the other for 'CALL PROCEEDING' leading to 'INCOMING CALL PROCEEDING', then a 'Disconnect request', and finally a decision diamond asking 'Is circuit to be reserved for reuse?'. If 'Yes', it goes to Z 7; if 'No', it goes to S 7. + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). + +T1145490-92/d17 + +FIGURE 3-11/Q.955 (Sheet 5 of 14) +Destination exchange (DE) – Procedure without DSS 1 LFB query +(release and preemption of existing MLPP call) + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call).](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +graph TD + L((L)) -- 1 --> D1{Is called user +busy with a call of +equal or +higher PL?} + D1 -- Yes --> T9((T)) + D1 -- No --> D2{Non- +preemptable +access resources +subscribed +to?} + K((K)) -- 5 --> D2 + D2 -- Yes --> T9 + D2 -- No --> P1[Mark circuit busy with PL +and MLPP Service Domain +of the incoming MLPP call] + P1 --> P2[/SETUP/] + P2 -.-> C1[Continue setup of +incoming MLPP call] + P2 --> P3[/CALL +PRESENT/] + P3 --> P4[/RELEASE COMPLETE +with Cause #88, +"incompatible +destination"/] + P3 --> P5[/CALL +PROCEEDING/] + P4 --> P6[Unmark the +previously marked +circuit] + P6 --> T9 + P5 --> P7[/INCOMING CALL +PROCEEDING/] + P7 --> P8[/Hold request/] + P8 --> P9[/HOLD with +Cause #8, +"preemption"/] + P9 -.-> C2[Notification of intended +preemption to the called +user and implicit reservation +of B-channel] + P9 --> N7((N)) + N7 -- 7 --> T9 + +``` + +The flowchart illustrates the procedure for handling an incoming MLPP call when the called user is busy with a call of equal or higher priority level (PL). The process begins at connector L (1) and leads to a decision diamond: "Is called user busy with a call of equal or higher PL?". If the answer is "Yes", the process proceeds directly to connector T (9). If "No", it leads to another decision diamond: "Non-preemptable access resources subscribed to?". Connector K (5) also leads to this second decision diamond. If the answer is "Yes", it proceeds to connector T (9). If "No", it proceeds to a process box: "Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call". This is followed by a "SETUP" process box, which has a dashed line connection to a note: "Continue setup of incoming MLPP call". The process then reaches a "CALL PRESENT" state, which branches into two paths. The left path leads to a "RELEASE COMPLETE with Cause #88, 'incompatible destination'" state, followed by "Unmark the previously marked circuit", and then to connector T (9). The right path leads to a "CALL PROCEEDING" state, followed by "INCOMING CALL PROCEEDING", then a "Hold request" state, and finally a "HOLD with Cause #8, 'preemption'" state. A dashed line from the "HOLD" state connects to a note: "Notification of intended preemption to the called user and implicit reservation of B-channel". The process then reaches connector N (7), which leads to connector T (9). + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). + +T1145500-92/d18 + +FIGURE 3-11/Q.955 (Sheet 6 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query + (release and preemption of existing MLPP call)** + +![Flowchart for Destination exchange (DE) procedure without DSS 1 LFB query. The process starts at connector N (6), leading to 'Start timer T_K'. A decision 'Is circuit to be reserved for reuse?' follows. If 'Yes', it enters a 'WAITING FOR RESPONSE' state. Two parallel paths emerge: one for 'Timer T_K expires' leading to 'Alternate party subscribed to?' (Yes leads to 'DISCONNECT' and 'Divert call to alternate party', resulting in 'ACTIVE'); the other for 'HOLD ACK' (noted as 'Called user acceptance of intended preemption'), leading to 'Stop timer T_K' and connector Z (5). If 'No' to the initial decision, it goes to connector S (5), 'Stop timer T_K', 'Disconnect Indication, with Cause #8', and 'Normal call clearing' to the preempted user, resulting in 'NULL' (E). Both paths from Z (5) lead to a 'DISCONNECT' state (noted as 'Preempted circuit is marked reserved for reuse'), followed by 'Start timer T_RR' and 'DISCONNECT INDICATION' (E), leading to connector R (8).](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +graph TD + N((N +6)) --> StartTK[Start timer TK] + StartTK --> Decision{Is circuit +to be reserved +for reuse?} + Decision -- Yes --> WaitResponse(WAITING FOR +RESPONSE) + Decision -- No --> S((S +5)) + WaitResponse --> TimerExpires[/Timer TK +expires/] + WaitResponse --> HoldAck[/HOLD ACK/] + HoldAck -.-> Note1[Called user acceptance +of intended preemption] + TimerExpires --> Alternate{Alternate party +subscribed to?} + Alternate -- Yes --> Disconnect1[/DISCONNECT/] + Disconnect1 --> Divert[Divert call +to +alternate party] + Divert --> Active{{ACTIVE}} + Alternate -- No --> Z((Z +5)) + HoldAck --> StopTK[Stop timer TK] + StopTK --> Z + S --> StopTK2[Stop timer TK] + StopTK2 --> Disconnect2[/Disconnect +Indication, +with Cause #8/] + Disconnect2 --> Clearing["Normal call +clearing" to the +preempted user at +the far end] + Clearing --> Null{{NULL +E}} + Z --> Disconnect3[/DISCONNECT/] + Disconnect3 -.-> Note2[Preempted circuit is +marked reserved +for reuse] + Disconnect3 --> StartTKR[Start timer TRR] + StartTKR --> DisconnectIndication[/DISCONNECT +INDICATION +E/] + DisconnectIndication --> R((R +8)) + +``` + +T1140740-92/d19 + +Flowchart for Destination exchange (DE) procedure without DSS 1 LFB query. The process starts at connector N (6), leading to 'Start timer T\_K'. A decision 'Is circuit to be reserved for reuse?' follows. If 'Yes', it enters a 'WAITING FOR RESPONSE' state. Two parallel paths emerge: one for 'Timer T\_K expires' leading to 'Alternate party subscribed to?' (Yes leads to 'DISCONNECT' and 'Divert call to alternate party', resulting in 'ACTIVE'); the other for 'HOLD ACK' (noted as 'Called user acceptance of intended preemption'), leading to 'Stop timer T\_K' and connector Z (5). If 'No' to the initial decision, it goes to connector S (5), 'Stop timer T\_K', 'Disconnect Indication, with Cause #8', and 'Normal call clearing' to the preempted user, resulting in 'NULL' (E). Both paths from Z (5) lead to a 'DISCONNECT' state (noted as 'Preempted circuit is marked reserved for reuse'), followed by 'Start timer T\_RR' and 'DISCONNECT INDICATION' (E), leading to connector R (8). + +FIGURE 3-11/Q.955 (Sheet 7 of 14) + Destination exchange (DE) – Procedure without DSS 1 LFB query + (release and preemption of existing MLPP call) + +![Flowchart for Destination exchange (DE) procedure without DSS 1 LFB query. The process starts at connector R (7), branching into two paths. The left path checks if timer T_RR expires; if yes, it unreserves the circuit and checks if it's a reattempt on an MLPP call. If yes, it sends a Disconnect Indication (Cause #46) and follows normal clearing procedures. If no, it goes to connector DD (1). The right path releases the circuit and stops timer T_RR, then checks if the alternate party is subscribed. If yes, it goes to connector Q (4); if no, it goes to connector CC (10).](e8e818455bb0d1a6153299a388b94868_img.jpg) + +``` + +graph TD + R((R 7)) --> Branch1(( )) + Branch1 --> Timer[Timer TRR expires] + Branch1 --> Release[RELEASE] + + Timer --> Unreserve[Unreserve marked circuit] + Unreserve --> IsMLPP{Is this a reattempt on MLPP call?} + + IsMLPP -- No --> DD((DD 1)) + IsMLPP -- Yes --> Disconnect[/Disconnect Indication, containing Cause #46, "precedence call blocked"/] + Disconnect --> Normal[Follow normal call clearing procedures] + Normal --> Null1[/NULL/] + + Release --> ReleaseComp[/RELEASE COMPLETE/] + ReleaseComp --> StopTimer[Stop timer TRR] + StopTimer --> Alternate{Alternate party subscribed to?} + + Alternate -- Yes --> Null2[/NULL E/] + Null2 --> Q((Q 4)) + + Alternate -- No --> Null3[/NULL E/] + Null3 --> CC((CC 10)) + +``` + +Clearing of incoming MLPP call + +T1140750-92/20 + +Flowchart for Destination exchange (DE) procedure without DSS 1 LFB query. The process starts at connector R (7), branching into two paths. The left path checks if timer T\_RR expires; if yes, it unreserves the circuit and checks if it's a reattempt on an MLPP call. If yes, it sends a Disconnect Indication (Cause #46) and follows normal clearing procedures. If no, it goes to connector DD (1). The right path releases the circuit and stops timer T\_RR, then checks if the alternate party is subscribed. If yes, it goes to connector Q (4); if no, it goes to connector CC (10). + +FIGURE 3-11/Q.955 (Sheet 8 of 14) + Destination exchange (DE) – Procedure without DSS 1 LFB query + (release and preemption of existing MLPP call) + +![Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (MLPP call completion options).](0a42e05c07941450f34e4f7117725834_img.jpg) + +``` + +graph TD + T((T)) -- "2, 3, 5, 6" --> A[Continue preempting +call setup] + A --> B{Call completion +or call offering services +available?} + B -- Yes --> C[Interactions with call completion +or call offering services] + C --> D([ACTIVE]) + B -- No --> E{Alternate +party subscribed +to?} + E -- Yes --> F[Divert call +to alternate party] + F --> G([ACTIVE]) + E -- No --> H[/Disconnect Indication, +containing Cause #46, +"precedence call blocked"/] + H --> I[Follow normal call +clearing procedures] + I --- J["Clearing of incoming +MLPP call"] + I --> K([NULL]) + +``` + +T1145510-92/d21 + +Flowchart for Destination exchange (DE) – Procedure without DSS 1 LFB query (MLPP call completion options). + +FIGURE 3-11/Q.955 (Sheet 9 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query +(MLPP call completion options)** + +![Flowchart for Destination exchange (DE) procedure without DSS 1 LFB query (call completion for MLPP call). The process starts with a circle labeled 'CC' with '2, 8' next to it, pointing to a parallelogram labeled 'ALERTING'. A dashed line from 'ALERTING' points to a bracketed note: 'Contains indication of whether the called party is an MLPP user or not'. The flow then goes to a decision diamond 'Called party MLPP user?'. If 'No', it goes to a rectangle 'Unmark the circuit of PL and MLPP Service Domain markings' before joining the 'Yes' path. The 'Yes' path goes directly to an oval 'CALL RECEIVED'. From there, it goes to a parallelogram 'CONNECT', then an oval 'CONNECT REQUEST', then a parallelogram 'Setup complete request', then a parallelogram 'CONNECT ACK', and finally an oval 'ACTIVE'. The document number 'T1140770-92/d22' is at the bottom.](c1df61cc3717e878a48e530218403403_img.jpg) + +``` + +graph TD + CC((CC)) -- 2, 8 --> ALERTING[/ALERTING/] + ALERTING -.-> Note[Contains indication of whether the called party is an MLPP user or not] + ALERTING --> Decision{Called party MLPP user?} + Decision -- No --> Unmark[Unmark the circuit of PL and MLPP Service Domain markings] + Unmark --> Join(( )) + Decision -- Yes --> Join + Join --> CALL_RECEIVED([CALL RECEIVED]) + CALL_RECEIVED --> CONNECT[/CONNECT/] + CONNECT --> CONNECT_REQUEST([CONNECT REQUEST]) + CONNECT_REQUEST --> Setup[/Setup complete request/] + Setup --> CONNECT_ACK[/CONNECT ACK/] + CONNECT_ACK --> ACTIVE([ACTIVE]) + +``` + +T1140770-92/d22 + +Flowchart for Destination exchange (DE) procedure without DSS 1 LFB query (call completion for MLPP call). The process starts with a circle labeled 'CC' with '2, 8' next to it, pointing to a parallelogram labeled 'ALERTING'. A dashed line from 'ALERTING' points to a bracketed note: 'Contains indication of whether the called party is an MLPP user or not'. The flow then goes to a decision diamond 'Called party MLPP user?'. If 'No', it goes to a rectangle 'Unmark the circuit of PL and MLPP Service Domain markings' before joining the 'Yes' path. The 'Yes' path goes directly to an oval 'CALL RECEIVED'. From there, it goes to a parallelogram 'CONNECT', then an oval 'CONNECT REQUEST', then a parallelogram 'Setup complete request', then a parallelogram 'CONNECT ACK', and finally an oval 'ACTIVE'. The document number 'T1140770-92/d22' is at the bottom. + +FIGURE 3-11/Q.955 (Sheet 10 of 14) +**Destination exchange (DE) – Procedure without DSS 1 LFB query + (call completion for MLPP call)** + +![Flowchart for DSS 1 LFB procedure for MLPP call. The process starts with a NULL state, followed by a Network LFB query request. A decision diamond asks 'Is (incoming) reserved circuit available?'. If 'No', it leads to a 'Network LFB query response indicating path reservation denied' message and then back to NULL. If 'Yes', it leads to 'Mark circuit reserved for use', then a 'REGISTER' message, then 'Start timer T_L', then a 'WAITING' state. A dashed line from the WAITING state is labeled 'for response to REGISTER'. The process ends at a circle labeled 'D' with the number 12 below it.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph TD + Start([NULL]) --> Request[/Network LFB query request/] + Request --> Decision{Is (incoming) reserved circuit available?} + Decision -- No --> Denied[/Network LFB query response indicating path reservation denied/] + Denied --> Null1([NULL]) + Decision -- Yes --> Mark[Mark circuit reserved for use] + Mark --> Register[/REGISTER/] + Register --> Timer[Start timer TL] + Timer --> Waiting([WAITING]) + Waiting -.->|for response to REGISTER| Waiting + Waiting --> End((D +12)) + +``` + +T1140780-92/d23 + +Flowchart for DSS 1 LFB procedure for MLPP call. The process starts with a NULL state, followed by a Network LFB query request. A decision diamond asks 'Is (incoming) reserved circuit available?'. If 'No', it leads to a 'Network LFB query response indicating path reservation denied' message and then back to NULL. If 'Yes', it leads to 'Mark circuit reserved for use', then a 'REGISTER' message, then 'Start timer T\_L', then a 'WAITING' state. A dashed line from the WAITING state is labeled 'for response to REGISTER'. The process ends at a circle labeled 'D' with the number 12 below it. + +FIGURE 3-11/Q.955 (Sheet 11 of 14) +Destination exchange (DE) – DSS 1 LFB procedure for MLPP call + +![Flowchart for Destination exchange (DE) – DSS 1 LFB procedure for MLPP call. The flow starts at node D (11) and branches into three paths: 1) Facility (Bearer capability check failure), 2) Facility (Bearer capability check success), and 3) Timer T_L expires. Path 1 leads to 'Stop timer T_L', then 'Network LFB query response (Bearer capability check failure cases)', then 'WAITING' (with a note 'to terminate signalling association'), then 'Release request', then 'RELEASE COMPLETE', and finally 'NULL'. Path 2 leads to 'Stop timer T_L', then a decision 'Called user busy?'. If 'No', it goes to node U (13). If 'Yes', it goes to a decision 'Non-preemptable access resources subscribed to?'. If 'Yes', it goes to node V (13). If 'No', it goes to 'Compare PL of incoming preempting call with MLPP call to the called user', then a decision 'Is called user busy with a call of equal or higher PL?'. If 'Yes', it goes to node V (13). If 'No', it goes to node W (14). Path 3 leads to 'Network LFB query response indicating success', then 'WAITING' (with a note 'to terminate signalling association'), then 'Release request', then 'RELEASE COMPLETE', then 'NULL' (with a note 'Waiting for preempting call setup' and reference T1140790-92/d24).](12c19090355e19922e23044633b9d1ea_img.jpg) + +``` + +graph TD + D((D 11)) --> F1[/FACILITY +(Bearer capability +check failure)/] + D --> F2[/FACILITY +(Bearer capability +check success)/] + D --> T1[Timer TL expires] + + F1 --> S1[Stop timer TL] + S1 --> Q1{{Network LFB query +response (Bearer +capability check +failure cases)}} + Q1 --> W1([WAITING]) + W1 -.->|to terminate +signalling +association| W1 + W1 --> R1[/Release +request/] + R1 --> RC1[/RELEASE +COMPLETE/] + RC1 --> N1([NULL]) + + F2 --> S2[Stop timer TL] + S2 --> D1{Called user +busy?} + D1 -- No --> U((U 13)) + D1 -- Yes --> D2{Non-preemptable +access resources +subscribed to?} + D2 -- Yes --> V((V 13)) + D2 -- No --> C1[Compare PL of incoming +preempting call with +MLPP call to +the called user] + C1 --> D3{Is called user busy +with a call of equal +or higher PL?} + D3 -- Yes --> V + D3 -- No --> W((W 14)) + + T1 --> Q2{{Network LFB +query response +indicating success}} + Q2 --> W2([WAITING]) + W2 -.->|to terminate +signalling +association| W2 + W2 --> R2[/Release +request/] + R2 --> RC2[/RELEASE +COMPLETE/] + RC2 --> N2([NULL]) + N2 -.->|Waiting for preempting +call setup| N2 + N2 --- T1140790-92/d24 + +``` + +Flowchart for Destination exchange (DE) – DSS 1 LFB procedure for MLPP call. The flow starts at node D (11) and branches into three paths: 1) Facility (Bearer capability check failure), 2) Facility (Bearer capability check success), and 3) Timer T\_L expires. Path 1 leads to 'Stop timer T\_L', then 'Network LFB query response (Bearer capability check failure cases)', then 'WAITING' (with a note 'to terminate signalling association'), then 'Release request', then 'RELEASE COMPLETE', and finally 'NULL'. Path 2 leads to 'Stop timer T\_L', then a decision 'Called user busy?'. If 'No', it goes to node U (13). If 'Yes', it goes to a decision 'Non-preemptable access resources subscribed to?'. If 'Yes', it goes to node V (13). If 'No', it goes to 'Compare PL of incoming preempting call with MLPP call to the called user', then a decision 'Is called user busy with a call of equal or higher PL?'. If 'Yes', it goes to node V (13). If 'No', it goes to node W (14). Path 3 leads to 'Network LFB query response indicating success', then 'WAITING' (with a note 'to terminate signalling association'), then 'Release request', then 'RELEASE COMPLETE', then 'NULL' (with a note 'Waiting for preempting call setup' and reference T1140790-92/d24). + +FIGURE 3-11/Q.955 (Sheet 12 of 14) +Destination exchange (DE) – DSS 1 LFB procedure for MLPP call + +![Flowchart for DSS 1 LFB procedure for MLPP call at the destination exchange. The process involves checking for idle circuits, non-preemptable access resources, and comparing priority levels (PL) of calls. It leads to various states including WAITING, Release request, RELEASE COMPLETE, and NULL.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +``` + +graph TD + U((U 12)) --> D1{Is idle circuit +available?} + D1 -- Yes --> P_Mark[Mark circuit +to the called +user as reserved] --> X((X 14)) + D1 -- No --> D2{Non- +preemptable +access resources +subscribed +to?} + D2 -- Yes --> V((V 12)) + D2 -- No --> P1[Compare PL of incoming +preempting call with +the existing MLPP call] + P1 --> D4{Is +existing MLPP +call at equal +or higher PL?} + D4 -- Yes --> V + D4 -- No --> Y((Y 14)) + V --> D3{Call +completion or call +offering services +available?} + D3 -- Yes --> P_LFB1[Network LFB +query response +indicating success] --> PP1((PP 13)) + D3 -- No --> D5{Alternate +party +subscribed to?} + D5 -- Yes --> P_LFB2[Network LFB +query response +indicating success] --> PP2((PP 13)) + D5 -- No --> P2[Unreserve +(incoming) +marked circuitN] --> P_LFB3[Network LFB +query response +indicating failure] + PP1 --> W1([WAITING]) + PP2 --> W1 + P_LFB3 --> W2([WAITING]) + W1 --- Note1[to terminate +signalling +association] + W2 --- Note2[to terminate +signalling +association] + W1 --> R1[Release +request] --> RC1[RELEASE +COMPLETE] --> N1([NULL]) + W2 --> R2[Release +request] --> RC2[RELEASE +COMPLETE] --> N2([NULL]) + N1 --- Note3[Waiting for +preempting call +setup] + N2 --- Note3 + +``` + +T1140800-92/d25 + +Flowchart for DSS 1 LFB procedure for MLPP call at the destination exchange. The process involves checking for idle circuits, non-preemptable access resources, and comparing priority levels (PL) of calls. It leads to various states including WAITING, Release request, RELEASE COMPLETE, and NULL. + +FIGURE 3-11/Q.955 (Sheet 13 of 14) +**Destination exchange (DE) – DSS 1 LFB procedure for MLPP call** + +![Flowchart of the DSS 1 LFB procedure for MLPP call. The process starts with entry points W, Y, and X leading to circuit reservation and LFB indication settings. It proceeds through starting a timer, receiving a network query response, entering a WAITING state, handling release messages, and finally reaching a NULL state. Annotations describe the purpose of the states.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +``` + +graph TD + W((W)) -- 12 ---> B1[Mark busy circuit reserved for use by the preempting call] + Y((Y)) -- 13 ---> B1 + B1 --> B2[Set LFB indication to "path reserved"] + X((X)) -- 13 ---> B2 + B2 --> B3[Start timer TLR] + B3 --> B4[/Network LFB query response indicating success/] + B4 --> W1(WAITING) + W1 -.- A1[to terminate signalling association] + W1 --> B5{{Release request}} + B5 --> B6{{RELEASE COMPLETE}} + B6 --> W2(NULL) + W2 -.- A2[Waiting for preempting call setup] + +``` + +T1140810-92/d26 + +Flowchart of the DSS 1 LFB procedure for MLPP call. The process starts with entry points W, Y, and X leading to circuit reservation and LFB indication settings. It proceeds through starting a timer, receiving a network query response, entering a WAITING state, handling release messages, and finally reaching a NULL state. Annotations describe the purpose of the states. + +FIGURE 3-11/Q.955 (Sheet 14 of 14) +**Destination exchange (DE) – DSS 1 LFB procedure for MLPP call** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts with a NULL terminal, leading to a decision 'Path reserved?'. If 'No', it goes to a NULL terminal. If 'Yes', it leads to 'Is marked circuit found?'. If 'No', it goes to a NULL terminal. If 'Yes', it leads to 'Is reserved circuit idle?'. If 'No', it goes to terminal O (5). If 'Yes', it leads to 'Called user busy?'. If 'Yes', it leads to 'Is call a precedence call?'. If 'Yes', it goes to terminal L (6). If 'No', it goes to 'Clearing of calling user with Cause #17 "user busy"', leading to a NULL terminal. If 'Called user busy?' is 'No', it leads to 'Is idle circuit available?'. If 'No', it goes to terminal P (3). If 'Yes', it goes to a 'SETUP' process, which is annotated as 'Incoming MLPP call', leading to terminal SS (2).](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +``` + +graph TD + Start([NULL]) --> D1{Path reserved?} + D1 -- No --> End1([NULL]) + D1 -- Yes --> D2{Is marked circuit found?} + D2 -- No --> End1 + D2 -- Yes --> D3{Is reserved circuit idle?} + D3 -- No --> O((O 5)) + D3 -- Yes --> D4{Called user busy?} + D4 -- Yes --> D5{Is call a precedence call?} + D5 -- Yes --> L((L 6)) + D5 -- No --> Clear[Clearing of calling user with Cause #17 "user busy"] + Clear --> End2([NULL]) + D4 -- No --> D6{Is idle circuit available?} + D6 -- No --> P((P 3)) + D6 -- Yes --> Setup[/SETUP/] + Setup --> SS((SS 2)) + +``` + +Annotations in the flowchart: + +- Next to 'Path reserved?': "Path reserved" is set in LFB indication +- Next to 'Is marked circuit found?': This decision is on reservation preemption +- Next to 'SETUP': Incoming MLPP call + +T1145520-92/d27 + +Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts with a NULL terminal, leading to a decision 'Path reserved?'. If 'No', it goes to a NULL terminal. If 'Yes', it leads to 'Is marked circuit found?'. If 'No', it goes to a NULL terminal. If 'Yes', it leads to 'Is reserved circuit idle?'. If 'No', it goes to terminal O (5). If 'Yes', it leads to 'Called user busy?'. If 'Yes', it leads to 'Is call a precedence call?'. If 'Yes', it goes to terminal L (6). If 'No', it goes to 'Clearing of calling user with Cause #17 "user busy"', leading to a NULL terminal. If 'Called user busy?' is 'No', it leads to 'Is idle circuit available?'. If 'No', it goes to terminal P (3). If 'Yes', it goes to a 'SETUP' process, which is annotated as 'Incoming MLPP call', leading to terminal SS (2). + +FIGURE 3-12/Q.955 (Sheet 1 of 12) +**Called User – Procedure without DSS 1 LFB query** +**(procedure for incoming MLPP call)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts with a start node 'SS' (1) leading to 'CALL PRESENT'. It branches into 'Reject request' and 'Proceeding request'. The 'Reject request' path leads to 'RELEASE COMPLETE with Cause *88 "incompatible destination"', then a decision 'Is call a precedence call?'. If 'Yes', it goes to terminal 'T' (9). If 'No', it goes to 'Clearing of calling user' and then 'NULL'. The 'Proceeding request' path leads to 'CALL PROCEEDING', then 'Mark circuit to called user busy with PL and MLPP Service Domain of incoming MLPP call, if MLPP subscriber', then 'INCOMING CALL PROCEEDING', then 'Alerting request', then a decision 'Alternate party subscribed to?'. If 'Yes', it goes to terminal 'Q' (4). If 'No', it goes to terminal 'CC' (10).](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +``` + +graph TD + SS((SS 1)) --> CALL_PRESENT{{CALL PRESENT}} + CALL_PRESENT --> Reject_request[/Reject request/] + CALL_PRESENT --> Proceeding_request[/Proceeding request/] + + Reject_request --> RELEASE_COMPLETE{{RELEASE COMPLETE +with Cause *88 +"incompatible destination"}} + RELEASE_COMPLETE --> Is_precedence{Is call a +precedence call?} + Is_precedence -- Yes --> T((T 9)) + Is_precedence -- No --> Clearing[Clearing of +calling user] + Clearing --> NULL{{NULL}} + + Proceeding_request --> CALL_PROCEEDING{{CALL PROCEEDING}} + CALL_PROCEEDING --> Mark_busy[Mark circuit to called user +busy with PL and MLPP Service +Domain of incoming MLPP call, +if MLPP subscriber] + Mark_busy --> INCOMING_CALL_PROCEEDING{{INCOMING CALL +PROCEEDING}} + INCOMING_CALL_PROCEEDING --> Alerting_request[/Alerting request/] + Alerting_request --> Alternate_party{Alternate party +subscribed to?} + Alternate_party -- Yes --> Q((Q 4)) + Alternate_party -- No --> CC((CC 10)) + +``` + +T1145530-92/d28 + +Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts with a start node 'SS' (1) leading to 'CALL PRESENT'. It branches into 'Reject request' and 'Proceeding request'. The 'Reject request' path leads to 'RELEASE COMPLETE with Cause \*88 "incompatible destination"', then a decision 'Is call a precedence call?'. If 'Yes', it goes to terminal 'T' (9). If 'No', it goes to 'Clearing of calling user' and then 'NULL'. The 'Proceeding request' path leads to 'CALL PROCEEDING', then 'Mark circuit to called user busy with PL and MLPP Service Domain of incoming MLPP call, if MLPP subscriber', then 'INCOMING CALL PROCEEDING', then 'Alerting request', then a decision 'Alternate party subscribed to?'. If 'Yes', it goes to terminal 'Q' (4). If 'No', it goes to terminal 'CC' (10). + +FIGURE 3-12/Q.955 (Sheet 2 of 12) +**Called User – Procedure without DSS 1 LFB query + (procedure for incoming MLPP call)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call).](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +``` + +graph TD + P((P)) -- 1 --> D1{Is call +a precedence +call?} + D1 -- Yes --> D2{Is existing MLPP +call at lower PL?} + D1 -- No --> R1[Clearing of calling user with +Cause #34, "no circuit/ +channel available"] + D2 -- Yes --> M((M)) + M -- 5 --> M_END[ ] + style M_END visibility:hidden + D2 -- No --> T((T)) + T -- 9 --> T_END[ ] + style T_END visibility:hidden + R1 --> NULL([NULL]) + subgraph Footer + NULL --- ID[T1145540-92/d29] + end + style Footer fill:none,stroke:none + +``` + +Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). + +FIGURE 3-12/Q.955 (Sheet 3 of 12) +**Called User – Procedure without DSS 1 LFB query +(procedure for incoming MLPP call)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts at a circle labeled 'Q' with '2, 8' below it. It branches into two paths. The left path goes to a rectangular box: 'Call is diverted to alternate party when no CONNECT is received before the expiry of timer T_K or no receipt of ALERTING'. The right path goes to a pentagon labeled 'ALERTING', which has a dashed line to a note: 'Contains Facility information element indicating if the called user is an MLPP subscriber or not'. From 'ALERTING', the flow goes to a rounded rectangle 'CALL RECEIVED', then a parallelogram 'Setup response', then a pentagon 'CONNECT', then a rounded rectangle 'CONNECT REQUEST', then a parallelogram 'CONNECT ACKNOWLEDGE', and finally a rounded rectangle 'ACTIVE'. A line from the left box joins the main flow between 'CONNECT ACKNOWLEDGE' and 'ACTIVE'. At the bottom is the text 'T1145550-92/d30'.](89f8aefc01866631793087542316cef2_img.jpg) + +``` + +graph TD + Q((Q)) -- 2, 8 --> Branch + Branch --> Divert[Call is diverted to alternate party +when no CONNECT is received +before the expiry of timer T_K +or no receipt of ALERTING] + Branch --> ALERTING{ALERTING} + ALERTING -.-> Note[Contains Facility information +element indicating if the +called user is an MLPP +subscriber or not] + ALERTING --> CALL_RECEIVED([CALL +RECEIVED]) + CALL_RECEIVED --> Setup_response[/Setup +response/] + Setup_response --> CONNECT{CONNECT} + CONNECT --> CONNECT_REQUEST([CONNECT +REQUEST]) + CONNECT_REQUEST --> CONNECT_ACKNOWLEDGE[/CONNECT +ACKNOWLEDGE/] + Divert --> J1(( )) + CONNECT_ACKNOWLEDGE --> J1 + J1 --> ACTIVE([ACTIVE]) + +``` + +T1145550-92/d30 + +Flowchart for Called User – Procedure without DSS 1 LFB query (procedure for incoming MLPP call). The flow starts at a circle labeled 'Q' with '2, 8' below it. It branches into two paths. The left path goes to a rectangular box: 'Call is diverted to alternate party when no CONNECT is received before the expiry of timer T\_K or no receipt of ALERTING'. The right path goes to a pentagon labeled 'ALERTING', which has a dashed line to a note: 'Contains Facility information element indicating if the called user is an MLPP subscriber or not'. From 'ALERTING', the flow goes to a rounded rectangle 'CALL RECEIVED', then a parallelogram 'Setup response', then a pentagon 'CONNECT', then a rounded rectangle 'CONNECT REQUEST', then a parallelogram 'CONNECT ACKNOWLEDGE', and finally a rounded rectangle 'ACTIVE'. A line from the left box joins the main flow between 'CONNECT ACKNOWLEDGE' and 'ACTIVE'. At the bottom is the text 'T1145550-92/d30'. + +FIGURE 3-12/Q.955 (Sheet 4 of 12) +**Called User – Procedure without DSS 1 LFB query + (procedure for incoming MLPP call)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). The flow starts with a decision 'Non-preemptable access resources subscribed to?'. If 'Yes', it goes to terminal T (9). If 'No', it goes to a 'Called user busy?' decision. If 'Yes' to 'Called user busy?', it goes to terminal PP (6). If 'No', it proceeds to a 'SETUP' process (labeled 'Incoming MLPP call'), then 'CALL PRESENT', then a 'Reject request' process, then 'RELEASE COMPLETE with Cause #88, "incompatible destination"', and finally to terminal T (9). Alternatively, from 'CALL PRESENT', it goes to a 'Proceeding request' process, then 'CALL PROCEEDING', then 'Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call, if MLPP subscriber', then 'INCOMING CALL PROCEEDING', then 'DISCONNECT', then a decision 'Is circuit to be reserved for reuse?'. If 'Yes', it goes to terminal Z (7). If 'No', it goes to terminal S (7).](a2251e3bbfcd726b68cc50b091e53b02_img.jpg) + +``` + +graph TD + M((M 3)) --> D1{Non-preemptable access resources subscribed to?} + D1 -- Yes --> T9((T 9)) + D1 -- No --> D2{Called user busy?} + O((O 1)) --> D2 + D2 -- Yes --> PP6((PP 6)) + D2 -- No --> SETUP[/SETUP/] + SETUP -.->|Incoming MLPP call| SETUP + SETUP --> CP([CALL PRESENT]) + CP --> RR[/Reject request/] + RR --> RC[/RELEASE COMPLETE with Cause #88, "incompatible destination"/] + RC --> T9 + CP --> PR[/Proceeding request/] + PR --> CPRO[/CALL PROCEEDING/] + CPRO --> MCB[Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call, if MLPP subscriber] + MCB --> ICPR([INCOMING CALL PROCEEDING]) + ICPR --> DISCONNECT[/DISCONNECT/] + DISCONNECT --> D3{Is circuit to be reserved for reuse?} + D3 -- Yes --> Z7((Z 7)) + D3 -- No --> S7((S 7)) + +``` + +T1145560-92/d31 + +Flowchart for Called User – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). The flow starts with a decision 'Non-preemptable access resources subscribed to?'. If 'Yes', it goes to terminal T (9). If 'No', it goes to a 'Called user busy?' decision. If 'Yes' to 'Called user busy?', it goes to terminal PP (6). If 'No', it proceeds to a 'SETUP' process (labeled 'Incoming MLPP call'), then 'CALL PRESENT', then a 'Reject request' process, then 'RELEASE COMPLETE with Cause #88, "incompatible destination"', and finally to terminal T (9). Alternatively, from 'CALL PRESENT', it goes to a 'Proceeding request' process, then 'CALL PROCEEDING', then 'Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call, if MLPP subscriber', then 'INCOMING CALL PROCEEDING', then 'DISCONNECT', then a decision 'Is circuit to be reserved for reuse?'. If 'Yes', it goes to terminal Z (7). If 'No', it goes to terminal S (7). + +FIGURE 3-12/Q.955 (Sheet 5 of 12) + Called User – Procedure without DSS 1 LFB query + (release and preemption of existing MLPP call) + +![Flowchart for Called User – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call).](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +``` + +graph TD + L((L)) -- 1 --> D1{Is called user busy with call of equal or higher PL?} + D1 -- Yes --> T9((T)) + D1 -- No --> D2{Non-preemptable access resources subscribed to?} + PP((PP)) -- 5 --> D2 + D2 -- Yes --> T9 + D2 -- No --> SETUP[/SETUP/] + SETUP -.->|Incoming MLPP call| MLPP[ ] + MLPP --> CP1([CALL PRESENT]) + CP1 --> R[Reject request] + CP1 --> P[Proceeding request] + R --> RC[/RELEASE COMPLETE with Cause #88, "incompatible destination"/] + RC --> T9 + P --> CP[/CALL PROCEEDING/] + CP --> MCB[Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call, if MLPP subscriber] + MCB --> ICP([INCOMING CALL PROCEEDING]) + ICP --> H[/HOLD with Cause #8, "preemption"/] + H -.->|Notification of intended preemption to the called user and implicit reservation of B-channel| N[ ] + H --> BB((BB)) + BB -- 7 --> T9 + +``` + +The flowchart describes the procedure for handling an incoming MLPP call when the called user is busy with a call of equal or higher priority (PL). The process starts with a loop (L) leading to a decision: "Is called user busy with call of equal or higher PL?". If "Yes", it proceeds to terminal T (9). If "No", it checks if "Non-preemptable access resources subscribed to?". If "Yes", it proceeds to terminal T (9). If "No", it proceeds to the "SETUP" process, which is associated with an "Incoming MLPP call". This leads to "CALL PRESENT", which branches into "Reject request" and "Proceeding request". The "Reject request" path leads to "RELEASE COMPLETE with Cause #88, 'incompatible destination'", which then leads to terminal T (9). The "Proceeding request" path leads to "CALL PROCEEDING", which then leads to "Mark circuit busy with PL and MLPP Service Domain of the incoming MLPP call, if MLPP subscriber". This is followed by "INCOMING CALL PROCEEDING", which leads to "HOLD with Cause #8, 'preemption'". This step includes a notification of intended preemption to the called user and an implicit reservation of the B-channel. Finally, it leads to terminal BB (7), which then leads to terminal T (9). + +Flowchart for Called User – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). + +FIGURE 3-12/Q.955 (Sheet 6 of 12) +**Called User – Procedure without DSS 1 LFB query** +**(release and preemption of existing MLPP call)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). The flow starts at connector BB (6) leading to a decision 'Is circuit to be reserved for reuse?'. If 'Yes', it goes to a decision 'Alternate party subscribed to?'. If 'Yes', it goes to 'DISCONNECT', then 'Divert call to alternate party', and finally 'ACTIVE'. If 'No', it goes to 'HOLD ACK' (with a note 'Called user acceptance of intended preemption'), then 'Preempted circuit is marked reserved for reuse', and finally 'DISCONNECTE INDICATION' (E) leading to connector R (8). If 'No' from the first decision, it goes to connector S (5), then 'Normal call clearing to the preempted user at the far end with Cause #8, "preemption"', and finally 'NULL' (E) leading to T1145580-92/d33. A connector Z (5) also feeds into the 'HOLD ACK' path. A note 'Preempted circuit is not reserved for reuse' points to the 'DISCONNECT' step.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +``` + +graph TD + BB((BB 6)) --> D1{Is circuit to be reserved for reuse?} + D1 -- Yes --> D2{Alternate party subscribed to?} + D1 -- No --> S((S 5)) + D2 -- Yes --> DISCONNECT1[/DISCONNECT/] + D2 -- No --> HOLD_ACK[/HOLD ACK/] + DISCONNECT1 -.-> Note1[Preempted circuit is not reserved for reuse] + DISCONNECT1 --> Divert[Divert call to alternate party] + Divert --> ACTIVE{{ACTIVE}} + HOLD_ACK -.-> Note2[Called user acceptance of intended preemption] + HOLD_ACK --> MarkReserved[Preempted circuit is marked reserved for reuse] + MarkReserved --> DISCONNECTE_INDICATION{{DISCONNECTE INDICATION E}} + DISCONNECTE_INDICATION --> R((R 8)) + S --> NormalClearing["Normal call clearing to the preempted user at the far end with Cause #8, "preemption""] + NormalClearing --> NULL{{NULL E}} + NULL --- T1145580-92/d33 + Z((Z 5)) --> HOLD_ACK + +``` + +Flowchart for Called User – Procedure without DSS 1 LFB query (release and preemption of existing MLPP call). The flow starts at connector BB (6) leading to a decision 'Is circuit to be reserved for reuse?'. If 'Yes', it goes to a decision 'Alternate party subscribed to?'. If 'Yes', it goes to 'DISCONNECT', then 'Divert call to alternate party', and finally 'ACTIVE'. If 'No', it goes to 'HOLD ACK' (with a note 'Called user acceptance of intended preemption'), then 'Preempted circuit is marked reserved for reuse', and finally 'DISCONNECTE INDICATION' (E) leading to connector R (8). If 'No' from the first decision, it goes to connector S (5), then 'Normal call clearing to the preempted user at the far end with Cause #8, "preemption"', and finally 'NULL' (E) leading to T1145580-92/d33. A connector Z (5) also feeds into the 'HOLD ACK' path. A note 'Preempted circuit is not reserved for reuse' points to the 'DISCONNECT' step. + +FIGURE 3-12/Q.955 (Sheet 7 of 12) +**Called User – Procedure without DSS 1 LFB query + (release and preemption of existing MLPP call)** + +![Flowchart for Called User procedure without DSS 1 LFB query (release and preemption of existing MLPP call).](51d4540605fdfa2c090638305022143b_img.jpg) + +``` + +graph TD + R((R 7)) --> J1{Is this +a reattempt +on MLPP call?} + J1 -- No --> DD((DD 1)) + J1 -- Yes --> P1[Follow normal call clearing +procedures to clear MLPP +call with Cause #46, +"precedence call blocked"] + P1 --> N1{{NULL}} + R --> R1[/Release +request/] + R1 --> R2[RELEASE] + R2 --> R3[/RELEASE +COMPLETE/] + R3 --> J2{Alternate party +subscribed to?} + J2 -- Yes --> N2{{NULL E}} + N2 --> Q((Q 4)) + J2 -- No --> N3{{NULL E}} + N3 --> CC((CC 10)) + +``` + +The flowchart illustrates the procedure for releasing and preempting an existing MLPP call. It begins with a start node 'R' (7). A decision diamond asks 'Is this a reattempt on MLPP call?'. If 'No', the flow goes to node 'DD' (1). If 'Yes', it proceeds to a process box: 'Follow normal call clearing procedures to clear MLPP call with Cause #46, "precedence call blocked"', which then leads to a 'NULL' terminal. The main path continues to a 'Release request' input, followed by a 'RELEASE' process, and then a 'RELEASE COMPLETE' output. Another decision diamond asks 'Alternate party subscribed to?'. If 'Yes', it leads to a 'NULL' terminal (E), which then connects to node 'Q' (4). If 'No', it leads to another 'NULL' terminal (E), which then connects to node 'CC' (10). + +Flowchart for Called User procedure without DSS 1 LFB query (release and preemption of existing MLPP call). + +T1145590-92/d34 + +FIGURE 3-12/Q.955 (Sheet 8 of 12) +**Called User, – Procedure without DSS 1 LFB query + (release and preemption of existing MLPP call)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (MLPP call completion options). The process starts with a terminal 'T' (2, 3, 5, 6) leading to 'Continue preempting call setup'. A decision 'Call completion or call offering services available?' branches to 'Interactions with call completion or call offering services' (ACTIVE) if 'Yes', or to 'Alternate party subscribed to?'. The 'Alternate party' decision branches to 'Follow normal call clearing procedures' (NULL) if 'No', or 'Divert call to alternate party' (ACTIVE) if 'Yes'. A bracket on the left indicates 'Clearing of incoming preempting call' for the 'Follow normal call clearing procedures' path.](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +``` + +graph TD + T((T +2, 3, 5, 6)) --> A[Continue preempting +call setup] + A --> B{Call +completion or call +offering services +available?} + B -- Yes --> C[Interactions with call +completion or call +offering services] + C --> D{{ACTIVE}} + B -- No --> E{Alternate +party +subscribed to?} + E -- Yes --> F[Divert call +to alternate party] + F --> G{{ACTIVE}} + E -- No --> H[Follow normal call +clearing procedures] + H --> I{{NULL}} + J[Clearing of incoming +preempting call] -.-> H + +``` + +T1145600-92/d35 + +Flowchart for Called User – Procedure without DSS 1 LFB query (MLPP call completion options). The process starts with a terminal 'T' (2, 3, 5, 6) leading to 'Continue preempting call setup'. A decision 'Call completion or call offering services available?' branches to 'Interactions with call completion or call offering services' (ACTIVE) if 'Yes', or to 'Alternate party subscribed to?'. The 'Alternate party' decision branches to 'Follow normal call clearing procedures' (NULL) if 'No', or 'Divert call to alternate party' (ACTIVE) if 'Yes'. A bracket on the left indicates 'Clearing of incoming preempting call' for the 'Follow normal call clearing procedures' path. + +FIGURE 3-12/Q.955 (Sheet 9 of 12) +**Called User – Procedure without DSS 1 LFB query + (MLPP call completion options)** + +![Flowchart for Called User – Procedure without DSS 1 LFB query (call completion for MLPP call). The flow starts with a circle labeled 'CC' with '2, 8' next to it. An arrow points down to a pentagon labeled 'ALERTING'. A bracket to the right of 'ALERTING' contains the text: 'Contains Facility information element indicating if the called user is an MLPP subscriber or not'. An arrow points down to a rounded rectangle labeled 'CALL RECEIVED'. An arrow points down to a parallelogram labeled 'Setup response'. An arrow points down to a pentagon labeled 'CONNECT'. An arrow points down to a rounded rectangle labeled 'CONNECT REQUEST'. An arrow points down to a parallelogram labeled 'CONNECT ACKNOWLEDGE'. An arrow points down to a rounded rectangle labeled 'ACTIVE'. At the bottom, the text 'T1145610-92/d36' is present.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +``` + +graph TD + CC((CC)) -- 2, 8 --> ALERTING{{ALERTING}} + ALERTING --- Note[Contains Facility information element indicating if the called user is an MLPP subscriber or not] + ALERTING --> CALL_RECEIVED([CALL RECEIVED]) + CALL_RECEIVED --> Setup_response[/Setup response/] + Setup_response --> CONNECT{{CONNECT}} + CONNECT --> CONNECT_REQUEST([CONNECT REQUEST]) + CONNECT_REQUEST --> CONNECT_ACKNOWLEDGE[/CONNECT ACKNOWLEDGE/] + CONNECT_ACKNOWLEDGE --> ACTIVE([ACTIVE]) + +``` + +T1145610-92/d36 + +Flowchart for Called User – Procedure without DSS 1 LFB query (call completion for MLPP call). The flow starts with a circle labeled 'CC' with '2, 8' next to it. An arrow points down to a pentagon labeled 'ALERTING'. A bracket to the right of 'ALERTING' contains the text: 'Contains Facility information element indicating if the called user is an MLPP subscriber or not'. An arrow points down to a rounded rectangle labeled 'CALL RECEIVED'. An arrow points down to a parallelogram labeled 'Setup response'. An arrow points down to a pentagon labeled 'CONNECT'. An arrow points down to a rounded rectangle labeled 'CONNECT REQUEST'. An arrow points down to a parallelogram labeled 'CONNECT ACKNOWLEDGE'. An arrow points down to a rounded rectangle labeled 'ACTIVE'. At the bottom, the text 'T1145610-92/d36' is present. + +FIGURE 3-12/Q.955 (Sheet 10 of 12) +**Called User – Procedure without DSS 1 LFB query** +**(call completion for MLPP call)** + +![Flowchart for Called User – DSS 1 LFB procedure for MLPP call. The process starts with a NULL state, followed by a REGISTER event. It then branches into three paths based on bearer capability check results or a waiting state. The central path involves decisions regarding user busy status, non-preemptable resources, and priority levels (PL), leading to connector states U, V, or W.](7e14467740b2570a44379b347a697921_img.jpg) + +``` + +graph TD + NULL1([NULL]) --> REGISTER[/REGISTER/] + REGISTER --- Note1[received when reserved circuit is available] + + REGISTER --> FACILITY_FAIL[/FACILITY +Bearer capability +check failure/] + REGISTER --> FACILITY_SUCCESS[/FACILITY +Bearer capability +check success/] + REGISTER --> WAITING_R([WAITING]) + + FACILITY_FAIL --> WAITING_F([WAITING]) + WAITING_F --- Note2[to terminate signalling association] + WAITING_F --> RELEASE_F[/RELEASE COMPLETE/] + RELEASE_F --> NULL_F([NULL]) + + FACILITY_SUCCESS --> BUSY{Called user +busy?} + BUSY -- No --> U((U +12)) + BUSY -- Yes --> RESOURCES{Non-preemptable +access resources +subscribed to?} + RESOURCES -- Yes --> V + RESOURCES -- No --> PL{Is +called user busy +with a call of +equal or higher +PL?} + PL -- Yes --> V((V +12)) + PL -- No --> W((W +12)) + + WAITING_R --- Note3[to terminate signalling association] + WAITING_R --> RELEASE_R[/RELEASE COMPLETE/] + RELEASE_R --> NULL_R([NULL]) + NULL_R --- Note4[Waiting for preempting call setup] + +``` + +T1145620-92/d37 + +Flowchart for Called User – DSS 1 LFB procedure for MLPP call. The process starts with a NULL state, followed by a REGISTER event. It then branches into three paths based on bearer capability check results or a waiting state. The central path involves decisions regarding user busy status, non-preemptable resources, and priority levels (PL), leading to connector states U, V, or W. + +FIGURE 3-12/Q.955 (Sheet 11 of 12) +**Called User – DSS 1 LFB procedure for MLPP call** + +![Flowchart for Called User – DSS 1 LFB procedure for MLPP call. The process starts with state U (11) and checks if an idle circuit is available. If not, it checks for non-preemptable access resources and existing MLPP calls. Depending on these checks, it either proceeds to state W (12) or state V (11). From state V (11), it checks for call completion or services availability, and if not available, checks for alternate party subscription. Both paths lead to a WAITING state, followed by RELEASE COMPLETE and NULL states, with specific termination and waiting annotations.](5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg) + +``` + +graph TD + U((U 11)) --> D1{Is idle circuit available?} + D1 -- Yes --> W12((W 12)) + D1 -- No --> D2{Non-preemptable access resources subscribed to?} + D2 -- Yes --> V11((V 11)) + D2 -- No --> D3{Is existing MLPP call at equal or higher PL?} + D3 -- Yes --> V11 + D3 -- No --> D4{Alternate party subscribed to?} + D4 -- Yes --> V11 + D4 -- No --> W12 + + V11 --> D5{Call completion or call offering services available?} + D5 -- Yes --> W1112((W 11, 12)) + D5 -- No --> D6{Alternate party subscribed to?} + D6 -- Yes --> W1112 + + W1112 --> W12 + + W12 -.-> T1[to terminate signalling association] + T1 -.-> W12 + + W1112 -.-> T2[to terminate signalling association] + T2 -.-> W1112 + + W12 --> R1[RELEASE COMPLETE] + R1 --> N1[NULL] + + W1112 --> R2[RELEASE COMPLETE] + R2 --> N2[NULL] + N2 -.-> T3[Waiting for preempting call setup] + T3 -.-> N2 + +``` + +T1145630-92/d38 + +Flowchart for Called User – DSS 1 LFB procedure for MLPP call. The process starts with state U (11) and checks if an idle circuit is available. If not, it checks for non-preemptable access resources and existing MLPP calls. Depending on these checks, it either proceeds to state W (12) or state V (11). From state V (11), it checks for call completion or services availability, and if not available, checks for alternate party subscription. Both paths lead to a WAITING state, followed by RELEASE COMPLETE and NULL states, with specific termination and waiting annotations. + +FIGURE 3-12/Q.955 (Sheet 12 of 12) +Called User – DSS 1 LFB procedure for MLPP call \ No newline at end of file